💩 🫘
That makes more sense.
So any comment or post?
It can be on instances with lots of users and open signups.
Donate to the Lemmy project, but also look at donating to your instance / instance admin. It ain’t free to host and operate this stuff.
I’ve been saying this for a few days now, but alas! Downvoted, scoffed. I just don’t get it. I am not advocating for anything other than true decentralization, which is broken in more than one way with the lemmyverse. Defederation is not even the issue. No, I don’t want nazi communities. No, I don’t have anything against admins. I just want to see the system work as it’s touted to work. People are so protective of their communities, and rightfully so, but we need to think hard about the differences between moderation and exclusion. One can foster a safe community, the other will just isolate.
100%. Work together on stability, resilience and privacy while ignoring trolls? Hell no! Let’s focus on creating silos and sniffing our own farts first!
Identities should be federated and not local to instances.
Join an instance that does not allow local communities. Then you can subscribe remotely to whatever you want and block whatever you don’t.
Came to make this comment.
That is essentially what happens and it’s a technical issue, not a philosophical one. If one instance is denied posting to another, the user should be notified at some point about that. There are a lot of silent errors right now with the setup. If you disable signups for example, users can still try but never see that it will never work.
Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.