0x1C3B00DA
If you break that up you end up with only a few large and likely advertisement funded instances being able to survive.
I'm not saying I don't think instances should be able to use that model, only that I think that model should not be the dominant way of building a community on the fediverse. But I don't see why a user would be less attached to a community just because its hosted on a different server from them, especially on the threadiverse which is topic based and where users are most likely going to engage in multiple topics.
Super disagree. A community at the protocol level can have just as much character as a community at the network level, but without most of the drawbacks. The "instance as community" idea was always a poor substitute for actual Group
s. The community shouldn't be a server that users are bound to; it should be a Group
that has access controls and private memberships (if desired). The moderators get all the same benefits of maintaining a limited community with their own rules, but users aren't beholden to petty drama via instance blocks or defederation.
It wouldn't change that, unless the moderators of those communities agreed to merge them by using the same cryptographic identity.
The article also points out that there were people who ate the raw sushi with no adverse affects, so mentioning "their established toxicity" seems like it would be just as misleading.
"Morels are more likely to cause intestinal distress if eaten raw, although even raw, they can be tolerated by some people," the agency wrote. Morels should be cooked before eating, as cooking can destroy bacterial contaminants. "For that matter, all mushrooms, wild or cultivated, should be cooked to release their full nutritional value because chitin in their cell walls otherwise inhibits digestion," the USDA writes.
The article mentions multiple times that cooked mushrooms are safer than raw ones.
I think you missed a key part of the article. Content Nation was not harvesting data from the fediverse; it was just federating. It was a new project that had just spun up and didn't have a full feature set yet, but other than those missing features it was a normal fediverse instance.
But public posts federating across the network isn't an "experience". It's the basic functionality of the network.
for profit corporation being able to suck up your posts is probably what has many upset
They can already do that without a bridge. And it doesn't "suck up your posts". It works just like any other instance. They have to search for you and follow you. Then they receive posts going forward, but they won't get historical posts.
I personally would block such a service
Good! You can do that and that is a perfectly reasonable solution. That's part of what has ppl upset on the other side of this argument. All of this arguing and vitriol is happening over a service that you can block like any other fediverse actor.