Doing it this way is why small instances gets hammered when a user’s post goes viral.
Setting up caching in the reverse proxy layer would alleviate this a lot of this. Like, GoToSocial only recommends to set up caching for the key and webfinger endpoints, where having it set up to cache posts and profiles for like 60 seconds (or however long the Cache-Control header says, Mastodon defaults to 180s) would alleviate the strain on the server so much.
There are other thing you can do, like this post explains some other things for Misskey, but the defaults should be sensible so you don't have to be a sysadmin expert to host an instance and they're currently not. I host 2 Lemmy instances (ukfli.uk and sappho.social) from a £5/month VPS and they're able to handle bursts of hundreds of requests without issue.
Bluesky is built to assume a handful of big relay (remember that a relay can merge in contents of another) and a bunch of appview and a ton of PDS servers, feed generators, moderation labelers, etc.
People are already building small, non-archival relays so this assumption seems mute. It's also important to remember that relays are an optimisation, not a core part of the protocol.
I mean, this would become less trivial the more replays go into use, where to get a full view you'd have to pull from all the relays that exist.
ActivityPub's solution to this is just IMO better, the original post has a replies collection attached to it that acts as the authority the replies the post has. This also allows creators to eject replies from the collection. There are issues with the way fedi software currently handles fetching from these reply collections, but the missing replies thing is very solvable in ActivityPub.
Vector layers allow you to create a shape and set its fill and stroke properties. You can then change the shape path, swap out different color settings, and transform the layer non-destructively, without losing any sharpness!
What is this, potential for a circle tool? In GNU IMP??? Someone tell the devil to turn the heating up, for hell must be freezing over.
If your idea is that the replies to every post look the same to any user, anywhere, at any time
This is only true of Bluesky because everyone is using Bluesky's infrastructure at the moment. If Bluesky ever deindexes someone and they start posting to an alternative relay, you suddenly don't have a guarantee of a full view of a post's replies.
Real Account Portability: Move your entire account – posts, comments, followers – to any new instance seamlessly. Your identity travels with you.
This is nice in theory but comes with edge cases that are hard to account for. Like, what if you have a post and your new instance defeds the instance the post's community is on? You either have to allow banned content onto the instance or the user loses data, neither of which are acceptable.
This is part of why ATProto's decoupling of user data from app logic is kinda genius and the direction we should go in if we want portable actors in Lemmy/thredi.
Full Fediverse Compatibility: We can add DIDs to Lemmy while staying fully interoperable with Mastodon, Kbin, and all other ActivityPub platforms. No breaking changes, just a powerful upgrade.
Not really, every fediverse platform that people use expects an Object's id to be a https URI it can just fetch the resource from. This is part of why FEP-ef61 specifies a way of translating a DID to a https URI. That's not to mention that moving existing actors from their current ID to a DID will cause all sorts of interop problems.
Edit: Also, is this AI-generated? It has all the tells of Gemini output, especially the the issue on Github.
What would a Feed/multicomms' actively weekly users even be? An aggregate of all the comms weekly users, or just the highest one? Or does Piefed go through all the comms and collect the unique actors (God, that would be an expensive operation)?
Lemmy's search is a lot better if you don't use the 'All' type, like just search comments or posts. With 'All', it is basically useless. Like sorting by controversial on a user's profile.
What's more, this composable moderation, along with an open API for clients, allows Bluesky (the company) to adhere to its legal obligations to block content, while allowing Bluesky users to sidestep those blocks
I honestly have my doubts governments will find this acceptable once they pay enough attention to figure out what Bluesky is doing.
# Convert PDF to text
pdftotext Meta_Leaked_List.pdf meta.txt
# Fetch instances feddit.uk federates with
curl https://feddit.uk/api/v3/federated_instances | jq -r .federated_instances.linked.[].domain > instances
# Get the lines that overlap between the two files
grep -xFf instances meta.txt
Ah, right comments don't actually top with time ranges in 0.19: https://join-lemmy.org/docs/users/03-votes-and-ranking.html#sorting-comments, my bad. The fact lemmy-ui still shows all of them is very confusing, I'll admit.
This is different in 1.0, the logic was changed for both posts and comments so these will work in future.