modulus

Advertising, cryptocoin shit, pay to play… This is an awful idea.

Definitely, AP is not magic. But if even within one protocol round-tripping and full-fidelity is impossible or very difficult, that makes it only harder and less likely through a bridge.

IMO bridging or translation isn’t federation per se. Also it seems unlikely that protocols would converge to that extent. In fact AP implementations are already different enough that even within the same protocol it’s hard to represent all the different activities instances can present.

I wouldn’t really count Mastodon/Bluesky bridging as federation. They’re incompatible protocols that were never intended to work together (arguably Bluesky was explicitly designed to avoid using AP).

So, not super sure what this is or how this works. Is the idea that you run the cgi, it sets up static files, and it responds to AP requests like follows, mentions, boosts and such? I realise lots of people don’t like long docs but I didn’t really understand the use case very well.

On my instance, the following control measures apply:

• Only public posts are visible through the web interface.
• Only public posts appear on RSS.
• Following requires approval.
• Authorised fetch is required.

So I think I have reason to feel fairly strongly that follower only posts are not public, and even unlisted posts are reasonably restricted.