![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
KenBonesWildRide [they/them]A
Matrix uses a separate account. You need to register. If a more detailed set of instructions would help, let me know and I will write some up.
I understand it’s less convenient than on-site communication or, say, Discord, but given the nature of the content we sometimes have to discuss and our history with relying on capitalist-owned platforms, we thought it was the correct tradeoff
Some of the money paid back initial domain name costs that people made out of pocket. We host several servers for the sake of maintaining the site. Anything left over after that remains in a dedicated account untouched to make sure the site can cover expenses
We tried at one point to offer the core developers/maintainers a portion of the money but literally everyone we asked said they weren’t interested and to give it to someone else. And that was just a one-time lump sum as an extra thank you for their work. We are very far away from paying someone directly to work on the site, as @ImSoOCD seems to be figuring out now.
There are other things we could do with the money, but as of now we don’t have any plans to. Charitable donations have tax consequences we aren’t prepared to deal with. We could advertise the site on Reddit, but we’ve generally steered clear of that. Personally, I haven’t felt like we had a mandate to use that money to put more ads out into the world, but I also understand why it would be an option on the table. We could do but bounties at some point, but as of now our core problem is a lack of a maintainer. Doesn’t matter when someone claims a bounty if there’s no one to review and merge in the code.
TLDR until we have enough patrons to actually pay someone for a reasonable amount of time and at a reasonable rate, the money goes to server costs and the rest sits untouched.
a delivery train went off the track That’s what you get for scabbin’ on the S.P. Line
For comments, spoilers should work to at least minimize exposure. I remember that sometimes just the content warning itself can be triggering, which is why we were going with filtering. But I imagine it’s better than nothing and we can talk about enforcement procedures for that
I believe a comrade was nearly finished with that but it was never to a point where it could be merged in. I could see if upstream has a ticket for it. It doesn’t look like pronoun tags has a dedicated issue in their tracker and that would need to be reimplemented before a switchover