Show Navigation
Conversation
Notices
-
@macgirvin Is there a way to get around the autodetection of protocol hubzilla (and friendica) do? Essentially, what I want to have is a way for a postActiv node to communicate "hey, why yes I am a native ostatus node to but I can communicate in zot too!" so that you can use the native protocols. Same with dfrn when I get that far with friendica.
-
@macgirvin What protocols a postActiv node can speak will eventually be an individual server choice, it will be able to speak any combination of them or even none of them if it wants to be private, so I'm trying to think on how best to do that in a way that isn't going to make the federation get really wibbly.
-
That's work in progress. Currently we negotiate the most capable protocol available and store/use that. Eventually I'll need to store the protocol capability array for every identity (I started on this about 3-4 months ago and got about 25% completed but got sidetracked). This turns out to be critical for making federated forums work.
-
Currently I need to fetch somewhere between 10 and 25 URLs from a server to map out its protocol support matrix. This really should be in webfinger. We can drill down to get the details, but currently I have to drill down the various URLs for each protocol to even answer the question of whether or not it is supported. Maybe something like a webfinger property of rel=http://ostatus.org/federation-protocols which returns an array [ ostatus, activitypub, zot, diaspora, ... ] for each resource. Then we would know exactly what to look for rather than probing sites blind for a page full of possible federation urls and possibly pissing off fail2ban.