Nothing stopping them, except, you know, the law… They can certainly display content that was not marked for public display. They will then proceed to get sued out of existence… If they do this automatically I’ll just privately post a music file with copyright protected music. Which is perfectly fine to do if it is indeed hidden from everyone. If they then publicly post it that’s on them and now I get to see the Music Industry fight the Zuck :D

The largest instances have either already announced their intent to block Facebook or stated that they are monitoring the situation and will react quickly and decisively should anything untoward happen. There is no Fediverse without federated third parties. All Facebook could show in that case was… Literally their own walled garden. How is that different to them not even implenting activitypub in the first place? It isn’t. Their only power is to ask if they can participate. Literally no one is going to waste a minute on any efforts of theirs that could even remotely be perceived as taking control.

Hi, I’m well aware of those APIs, but the idea was to find a unified way using ActivityPub. As it stands AP seems to actually have this glaring omission at its core. I’m somewhat baffled how this skipped past so many interations. What you mentioned is certainly a valid option to access data on lemmy. But it won’t work on Mastodon, or any other service only linked via ActivityPub Federation. And that’s a problem. It splits the network apart at the seams.

You actually described my expectation in that last paragraph. I fully expected to have to invent a curated list of endpoints. What I instead found was that even given an endpoint (like beehaw.org) there is no way to discover what is on that instance. Which is a big issue. I’ve discussed this a bit (albeit extremely slowly) with the folks in the activitypub irc, and pretty much got it confirmed. If you want to develop a service that is intent on delivering any form of public content at all, supporting activitypub, then you have no protocol based way of communicating this content to anyone. So going by that the lemmy implementation is actually “correct”, in as much as the protocol simply fails to provide guidance for this critical step.