Conversation
Notices
-
@rossjones I think you've mixed up the definitions of publisher, subscriber, hub, callback etc.
Of course you can run your own hub - or use a third party if you want. The way the hub URL(s) is discovered is via a rel="hub" in (in !OStatus' case) the Atom feed, like so: <link href="https://social.umeahackerspace.se/main/push/hub" rel="hub"/> in https://social.umeahackerspace.se/api/statuses/user_timeline/2.atom
-
@rossjones Btw, look up WebSub which is its finalised form. Where is the spec unclear?
-
@rossjones The difference is that v0.3 assumed there would be only one hub. Later versions let the publisher (feed owner) advertise multiple hubs (distributors) and thus takes responsibility to ping _all_ advertised hubs on updates and not just some.
-
@herrabre No, the URI of an author is always portable. It is unrelated to anything and should be treated as a random string (some use it for discovery, but that is Bad(tm) and discovery is made not _from_ a URI but _of_ a URI (i.e. you find n advertised URI for an acct:user@whatever.example and then apply some verification method you trust).
It is actuallt just by chance that URIs in !GNUsocial are http URLs.
-
@rossjones Oh wait, I think I understand what you mean now. In which case I misunderstood your request.