there is a rightwinger instance constantly showing up in my feed and blocking users/communities one by one is getting a bit annoying :/
there is a rightwinger instance constantly showing up in my feed and blocking users/communities one by one is getting a bit annoying :/
yeah, users need more control, instances need the ability to defederate due to anything crossing legal lines in thier jursdictions, but right now its used for more than that simply because it works well.
users should have control over blocking not just communities but entire instances if they please and meta on posts/communities should be correct so instances can show users SFW public pages for non-members (aka the general public)
Users should absolutely have mute/block/privacy controls. These should be used to build the community they want and see what they want to see.
Users should not be left to “fend for themselves” against abuse/hate/racism having a platform.
A person of color should feel safe.
Women should feel safe.
LGBTQIA+ should feel safe.
BIPOC should feel safe.
They should be able to login, find their community and participate without needing to deal with DM’s of lynchings, being publichly shamed with racial slurs. Power belongs to real community and real engagement, not abusers.
This is precisely the point I’ve been trying to make elsewhere in the thread. Maybe some people want total individual freedom/responsibility to block or not, but most of us want to find an instance community that will protect us and serve our interests by dealing with that for us, so we don’t have to go through that mental health damage constantly.
The good thing is you can always run a tiny instance for just yourself and not defederate with anyone if other communities defederate too aggressively.
im sure it would need some tweaks to how sync works but i think its completely possible for every user that wanted to have thier own instance, running right on thier phone if they desired.
I can already imagine a few ways that can go wrong. This would be a awesome way to do it though but there are many issues that would have to be addressed for that.
same, but its not like its something that hasent been worked on intensely for the past 15 years or anything, using mechanisms that require a level of consensus we dont need the overhead of meaning higher throughput. We also dont have the read only write-forward problems that those systems have so we can simply leverage the very well refined P2P mechanisms they use, i bet if we go looking, we find one that has its p2p protocol implementation in its own github even.
the thrust here is rather than diy, lets leverage work where billions have already been sunk.
p2p makes sense in this situation. It can end up being a massive battery drainer if we are talking smartphone implementation. (coming from torrenting reference point and how it eats battery on phones)
so the way these work usually is 2 piece like old IRC away daemons. You have a headless instance that syncs what you care about on “someone elses computer” or just online all the time. That does the job of keeping up-to-date. Your phone and other devices do a secure connection to that device to get updates. what’s interesting about building it to just be the same kind of server is you can simplify deployment and apps (its all the rage anyway just look at a react app).
so your device does not need to be online, you could run things like bots and have schedules and get just the deltas when you come online. This is also how private signing works today so the design and deploy pattern is well documented.