Discussion
I find sad that even if I think about making outline for some service that able to federate with ActivityPub / Fediverse, it also means I have to think about something that can be deplatformed, outlawed or censored out in 2025.
But both ActivityPub (and even ATProto) is NOT designed to be functional in such conditions.
Attempt to support it makes immediately you dependent on pyramid of:
馃捇 servers, likely cloud
馃摐 DNS
馃攽 SSL certificate(s)
Each of above can become point of failure 馃У
Of course it does not mean that ActivityPub is bad on itself.
It just necessary to admit these things before even thinking about some software project:
1锔忊儯 Each tech has limits of applicability
2锔忊儯 Each design decision would either limit your audience (by demanding some tech knowledge to get started) or make your project more vulnerable to censorship or other treats of forced closure.
3锔忊儯 IT solutions can't solve political problems
And yes, I suppose that ActivityPub as possible to use as communication protocol/data format in a peer-to-peer environment. But if "real" data transport will be some p2p tech, then it would be not so "http-compliant" in some details, like actor id or entity id or some urls will be like p2p://people/1234567890abcdef or p2p://data/by_sha256/12345678 which can not be directly used across fediverse, esp. without some https bridge like ipfs[dot]io
A space for Bonfire maintainers and contributors to communicate
