Edit: Shit, I probably should have made the title plural - “Does Lemmy need charters?”
From the great discussion below, some clarifying thoughts:
/Edit
Looooong time r/all lurker here, something like 10+ years on reddit with maybe 10 comments. I’ve seen a lot go down.
I’m seeing a lot of hand wringing around defederating Meta, Threads, and even handling problematic instances within the Lemmyverse itself.
It’s tiring to see these things come into consideration on a case by case basis, completely decontextualized from earlier crises. And the patterns are all too familiar - the big ones lately have been around (to name a few things):
This definitely isn’t a new idea, but at in these early days of the Lemmyverse, we can take our collective past experiences, good and bad, on other social media networks, and define some sort of Lemmy charter that sets standards for ethos and quality control. I’ll start:
- Don’t federate with for-profit or commercial institutions
- TBD
Because we’re done with the for-profit, commercial web, right? In the last couple of days, my brain has taken all the all the Lemmy posts and comments on the subject, mashed it all up, distilled it, and keeps coming back to this idea of non-profit/non-commercial entities.
Because loose, institutional underpinnings could, like a mycelial network, feed the Lemmyverse. And mycelial networks are dope.
Here’s a proposed methodology:
*We’d have to think about what that initial “Core” means - maybe the first X instances to have reached Y number of users? Beyond bragging rights that They Were There when the charter was created, no other special status would be conferred.
And because I’m an anarcho-syndicalist:
And because I have ADHD, and this is currently over-stimulating my brain:
Alright, ADHD has run its course. Back to lurking for another 10 years.
A community to talk about the Fediverse and all it’s related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
And right from the first point you have gone against the whole point of the Fediverse. ActivityPub is an open protocol. Anyone can implement it and use it. Anyone can federate with anyone they choose.
Placing “non-commercial” restrictions on it is legally infeasible, and not desirable. What happens if an instance has a donation address? Or if it decides to run some ads to support itself? Or creates some kind of “premium” tier with a fee? What if a company decides to create an instance to run the “official” forum for the games or other software they publish, is that a commercial instance? Who’s going to decide these things?
If you want to argue that some specific instance shouldn’t federate with some other specific instance, or some specific instance should have its own “charter” that it uses to make those decisions with, sure whatever. But in no way would I support a “charter” that applies to all instances.
This one, yes.
And anyone can decide to not allow bad faith actors (capitalists) to connect with their instance.
This is the paradox of intolerance playing out. We have no obligation to enable these scum.
The concept of having a “charter” for Lemmy doesn’t seem to mesh with “anyone can decide.”
OP has since edited their post to backpedal from that concept, but I’m not sure what the point of calling for instance-specific “charters” are - it just codifies the “anyone can decide” thing, which doesn’t need codifying.
As I understood the idea, it is about comparability, and readability, through unification.
Each instance can decide for itself, and most align with what I like. But I still have to figure it out for each instance individually. By finding where they post that information, understand how the information is structured, note they did not specify something the others did specify in their prose, and so on.
If we codify what key-value pairs make up this information, and where this data should be displayed, comparing becomes much easier.
It also allows automatic comparison. Imagine I could filter in instance browsers for policies which I do or do not want my instance to have.