Interesting... thank you for sharing!
It seems caching doesn't do much, even while also being a big pain for instance admins - so much so that it is explicitly made voluntary.
Perhaps that is why PieFed is going so hard on integration with PixelFed and now Loops.
Fwiw, lemmy.cafe defederated from lemmy.ml, and is even running a 0.19.6 beta codebase so even if there's only a single admin they seem really on the ball.
Tesseract also has implemented a way to ban all users from lemmy.ml.
And PieFed allows personal bans on any custom instance you choose. Plus it has "categories" of communities so that you don't have to keep searching on All, though you can do that too if you want. It seems really polished these days! Not 100% - e.g. you can't easily search for a user in the same form as a keyword - but it looks extremely usable, so I am switching to it today.
Meanwhile, on Lemmy we were promised that 0.19.3 would allow user blocking of instances, which turned out to be not quite true, and when your instance upgrades from that to 0.19.6 when it comes out (most other instances, like mine, are already running 0.19.5), the protections that it offers will be further rolled back - e.g. on 0.19.3 I did not receive notifications from those users, whereas now on 0.19.5 I do.
And maybe some apps allow blocking of an instance, I dunno about that aspect.
Lemmy.ml was one of the first instances in the Fediverse... but that doesn't mean that we should be forced to listen to the stuff spewing forth from it unless we choose that for ourselves, especially in the next few months as the trolls go into overdrive due to the ongoing USA election (and likely subsequent "constitutional crisis" event).
Anyway, I just wanted you to know that there are options! Not many, but they do exist!:-)
I did not make this, but it halfway almost seems to fit...
Oh, does image caching not apply to remotely hosted content? Well, then yeah, that sounds good.
But doesn't the instance it is ~~delicious~~ (edit: FUCK AUTOCORRECT!) delivered to do that, and then if the image changes later, it wouldn't update? And then I thought further that people from other instances likewise pull from the host instance, rather than the original source.
Except maybe Lemmy.world, if the image caching was added in a more recent update, which I thought was the case?
Anyway, I'm not saying that any of this happens, only that I thought it might.
(Wouldn't work anyway, due to Lemmy's caching approach iirc)
Randomization subroutine...
Okay fr fr, but...
Twovix (dammit! now I'm stuck with that spelling!?) isn't even the only pair of beings that she murdered this week:-).
Or at least a reasonable facsimile thereof:-)
Are we so sure about that ordering?
Tangentially, there's a whole bunch of issues going on with the programming.dev server for one. See at !meta@programming.dev. Lemmy's upcoming upgrade to 0.19.6 should help - see https://github.com/LemmyNet/lemmy/pull/4623 and https://feddit.org/post/3524876 discussing it.