how do we report problematic instances? (lemmy.world)

submitted 1 year ago by Kovu@lemmy.world to c/lemmyworld@lemmy.world

53 comments fedilink hide all child comments

there is a rightwinger instance constantly showing up in my feed and blocking users/communities one by one is getting a bit annoying :/

you are viewing a single comment's thread
view the rest of the comments

[-] RGB@lemmy.world 23 points 1 year ago

Reporting isn't good. I do think users should have an ability to block instances for themselves. (you can do that right now if you run your own instance)

[-] manitcor@lemmy.intai.tech 7 points 1 year ago

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)

[-] RGB@lemmy.world 5 points 1 year ago

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.

[-] manitcor@lemmy.intai.tech 3 points 1 year ago

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.

[-] RGB@lemmy.world 2 points 1 year ago

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.

[-] manitcor@lemmy.intai.tech 3 points 1 year ago

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.

[-] RGB@lemmy.world 2 points 1 year ago

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)

[-] manitcor@lemmy.intai.tech 2 points 1 year ago

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.