• 0 Posts
  • 64 Comments
Joined 4 months ago
cake
Cake day: August 17th, 2024

help-circle






  • The other thing is that I recall that kbin.social exploded and got a huge chuck of the exodus - but now that it’s been effectively dead for half a year, those users mostly seem to have vanished.

    A fraction clearly did migrate to other mbin and lemmy instances. It seems like the rest did not return to spez’s site from what I’m hearing (“all the posts I’m seeing there are complaining that only bots are active here”) but I’m not sure where they went. But for example, one person I was following seems to have dropped off entirely from the fediverse and all social media.










  • This issue already exists, regardless of the embed server problem. Right now, images posted by users to an instance get sent to that community’s instance and then copied to all instances of all subscribers.

    If anything, the embed server provides a potential solution - rather than federate the image directly, simply link to the copy of the image on the embed server. (I’ve done some customized code changes on top of pyfedi to implement this idea there.)

    I imagine instance admins would still want to to monitor and delete links to CP, but under this idea only the admins of the embed server and their delegates would have the ability to remove CP from the embed server itself. (Should they delegate this ability to other instance admins? Probably only on a case-by-case basis at most.)

    Perhaps they could support a reporting functioning from mods and instance admins though…





  • So I’m not sure where I fit in. I run my own instance, but it’s a single user instance that only serves me. Also, I currently don’t run any magazines (communities) of my own.

    If I was the user on Instance A asking on Instance B … well that means Instance A is my own, and I obviously wouldn’t get in trouble with myself.

    If I was the admin on Instance B - a user from elsewhere was asking me to remove such content on mine - I’d go ahead and do it. Not worth the potential headache or ramifications that would come with refusing.

    I think in general, the admin on Instance A would not be upset with the user. If anything, in this situation the user is probably trying to delete their account and history, so the admins of Instance A would be thankful that the user went to instance B and saved the admins the headache of trying to contact other federated instances themselves to coordinate a manual deletion. (The only thing worse than dealing with a GDPR request is trying to get others to help you deal with a GDPR request - particularly without pay.)