I don't know if somethings changed, but it actually doesn't. This lines would need to be WithContext<SharedInboxActivities>> for that to be the case, and just to make sure I tested against a local running main and was able to send activities to it without the @context just fine.
That still only shows replies the server knows about, this article is about making sure all replies to a post are present on all servers.
FEP-1b12 (Group ferderation) kinda already alleviates this, our part of the fediverse doesn't really suffer from the missing replies problem, but it's a solution that doesn't work well with microblog platforms.
I'm not the most knowledgeable about Mastodon's APub implementation, but having a look at the Actor of that profile, it might be because it's invalid JSON-LD. Now, Mastodon doesn't actually do proper JSON-LD checks, you can follow PieFed profiles from Mastodon and they don't produce proper JSON-LD, but they do include "https://w3id.org/security/v1" in their @context, and doing a code search of Mastodon's source code does show some checks for if that's included.
Lemmy's I am familiar with and irrc it doesn't even check if @context is present.
I’m not sure about all of it and had to remove the racist/sexist stuff, just because I don’t know any software on the fediverse with controversies like this…
Soapbox, a fork of Pleroma, is made by a TERF who previously worked for Gab.
TERFs don't want trans people using any toilet. TERFs want to push trans people out of public life, and ideally to stop existing all together, by making existing in it as difficult as possible.
Just so we're clear, what this crawler does is go through all servers that use ActivityPub known to it, and congregate that data to a list of known services (Lemmy, Mastodon, Piefed etc.). How is does that is by querying a standardised end point to get the instance info (.well-known/nodeinfo which will then point to a different path to get the actual info).
For instance, here's what it will collect for feddit.uk:
The important stat here is the localPosts, which is all the posts made by local users in any community, local or remote. It does not include posts by users from remote instances made in local communities. You can also see this data on the instance sidebar in lemmy-ui.
lemmy.zip going down will only reduce aggregated stats for total posts by 47,280, as that's what they report for their localPosts.
I spent a couple hours trying to create an account on pds.flamingos-cant.xyz that uses a did:web following the instructions here and the account at the end ended up with a did:plc, so IDK how you create a PDS with a did:web but it's clearly not something they put a lot of effort into supporting.
But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:
But Bluesky has developed its own DID method, did:plc. Today, did:plc stands for "Public Ledger of Credentials", however it originally stood for "Placeholder DIDs", with the hope of replacing them with something else later. The way that did:plc works is that Bluesky hosts a web service from which one can register, retrieve, and rotate keys (and other associated DID document information). However, this ledger is centrally controlled by Bluesky.
It's literally not possible to have a functional PDS without registering with a Bluesky server and they maintain indefinite control over the ledger. All your data is tied to this DID, it's how the entire protocol is designed to identify stuff, how decentralised is your data if it's dependent on Blusky (the company) assigning you an identity?
Really cool honestly. How big it is is probably predicated on if Bluesky enabled it for PDS'es on bsky.social.