abff08f4813c

Yeah, that chart needs to be updated. AFAIK no instance is still on kbin, everything has gone to mbin. It's also missing pyfedi/piefed

As far as I can tell there's been no communication from him for several months and not since he posted saying he'd turn kbin.social over to a new admin.

But the domain for kbin.social was recently renewed (I posted full details over at https://fedia.io/m/fediverse/t/1403334/Any-updates-on-kbin-social-recently ) which gives me hope that ernest is still around, just a bit more behind the scenes.

Of course, it could also be that the domain was simply auto-renewed (as described in https://www.godaddy.com/en-ca/help/turn-my-domain-auto-renew-on-or-off-41085 ). I think some registrars or services even offer prepayment options for auto-renewing, meaning that ernest might have set this all up before he disappeared, rather than slowly reappearing now...

While this would almost certainly work, it would be nice if the root cause can be discovered and either fixed or worked around. Having to reinstall everytime one needs to free up disk space is .. less than ideal.

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..

You're not the first to think about this.

See https://aumetra.xyz/posts/the-fedi-ddos-problem - there an embed server is proposed, to be shared by multiple instances (ideally a great many would use just the one), which can host things like image files and previews.

This is actually very easy. You can copy the files from the container, even while it's not running, onto your host system to edit there, and then copy them back afterwards.

See the top answer on https://stackoverflow.com/questions/22907231/how-to-copy-files-from-host-to-docker-container for step by step instructions on how to do this.

So an hour later, while logged out (in incognito mode) I am seeing your post on https://slrpnk.net/c/woodworking@lemmy.ca and can find it on your home instance directly at https://slrpnk.net/post/14701745 - this is in addition to seeing it on https://lemmy.ca/c/woodworking and directly on the magazine's instance at https://lemmy.ca/post/31909201

Also, the post likewise shows up for me when I view your profile on either your home instance at https://slrpnk.net/u/technomad or on the magazine's instance at https://lemmy.ca/u/technomad@slrpnk.net (and again, that's logged out and in incognito mode).

Finally, I see your post on lemmy.world in the same three places - the magazine https://lemmy.world/c/woodworking@lemmy.ca , your profile https://lemmy.world/u/technomad@slrpnk.net , and the direct post itself https://lemmy.world/post/21403325

Sometimes posts from lemmy.world take up to three days to federate to my instance, so an hour isn't too bad really.

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.)

I'm not sure that even Lemmy has a monopoly on the fediverse anyways. But outside of the fediverse, breaking up the tech monopolies and enforcing net neutrality are steps in the right direction.

For the fediverse specifically, I'm not sure. One thing that might help is to make user accounts and magazines (communities) more portable. So if one signs up on the wrong instance, it's easier to move to a friendlier instance. Currently, some folks seem to set up their own instance specifically for a community that they have planned explicitly to avoid this problem (but that makes it even harder to get a new owner if the mod-admin abandons the instance).

Of course, the technical bar to setting up and running your own instance is a bit higher than just signing up to, for example, fedia.io (And that's just if you want to run vanilla - you generally have to be an actual software dev if you want to customize the software that your instance runs.)

But coding software, and moderating a community, or an entire instance, are all different things and I suspect that there's not much overlap with the first one and the other two. So I don't have any good solutions either, just suggesting that if the fediverse required everyone to set up their own instance to join, we'd likely be in a pre-Eternal September phase.

Ah, if only kbin.social hadn't gone done, I would too be post 1-year mark. I replaced that one with my own instance, but that makes me look younger than I should be...

Hmm, but wouldn't forking lemmy require you to create your own instance?

Eh, well, I'm aware of some folks who got banned from .ml because their views didn't align well with the censors (or censor-admins) there. Meanwhile they're welcomed elsewhere on .world and fedia.io, suggesting that it's not a case of the individuals being bad apples.