that, or just use the mobile page which is designed for such narrow aspects.

no.

hard disagree. This isn’t black and white, you can do some of both and that is not wrong or unprincipled. Thinking otherwise is just simple minded.

any mods that rolled over to continue doing an unpaid job just to retain some form of power are bitches.

Personally, I don’t believe that POV is fair. As someone who, with a small group of friends, started a sub that has grown to 100k people and is the most active internet community for a niche gaming segment - i personally think it’s not that easy to judge. I have not been active on my sub in years, and I leave the job up to the new guard, but I can completely respect the decision to want to keep something you invested in building alive and a positive influence in the area it affects. It’s easy to armchair QB stuff like this and judge others decisions, but to just generalize and say “better to die than to think something else is better in the bigger picture” is a bit of a cop out imo.

And what is it with the narrow aspects? I totally get the need for mobile support, but the default desktop view looks like it’s trying to play nice with old 4:3 aspects. If that’s the root design goal, I sure hope we can let that design goal die. In a 16:9 maximized window there is so much wasted real estate it pains me.

The difference is you cited software projects, not hosted infrastructure. A person can contribute to a FOSS dev project and not incur expenses dependent on end-users activity. Hosting a fediverse application isn’t like that, somebody has to pay for the hosting and the hosting expenses will scale with user activity.

“Created for Lemmy” isn’t really a thing, all you need is to implement the ActivityPub protocol. Whether or not it has any relationship to Lemmy has no bearing on if it can talk to instances using Lemmy’s implementation.

Sure but anyone can implement something using the activityPub spec and federate with other instances regardless of what flavor they’re using.

from what i understand, this is syntax implemented on lemmy. it’s not from the deeper ActivtyPub protocol all of these things are implementing. If that’s true, it won’t render on kbin how it does on lemmy.

not sure that solution is a good one for this environment. I’m new but from what i’ve seen the concept of moderation is different and your solution is trying to engineer a reddit-like moderation design to an architecture that is fundamentally not reddit-like. Moderation here is at the instance level, not the community level.

there are are lot of idiots, a lot. I don’t know how to fix that, so I just ignore them and move on.