-
How should hubs decide which hash algorithm to use in signing? SHA-1 may be breakable in practice soon (see [SHAttered](https://en.wikipedia.org/wiki/SHA-1#SHAttered_-_First_public_collision)) but ho…
-
please close this once the template is ready (so I get an email :) )
seebi updated
7 years ago
-
Concrete example from the fediverse: https://github.com/tootsuite/mastodon/issues/177#issuecomment-292780728
A person wants to move their primary location from, say, mastodon.social to xoxo.zone -…
-
The *Publishing* section: https://www.w3.org/TR/websub/#publishing is under specified. I think https://www.w3.org/TR/ldn/ is a good candidate as a possible mechanism.
-
I've tried subscribing to users' atom feeds such as https://mastodon.social/users/Gargron.atom with both websub.rocks and npm's pubsubhubbub library. On both the subscription appears to succeed and ge…
ara4n updated
7 years ago
-
Section 6 requires the content type of the callback request to be the same as the topic's content type. For resources that support content negotiation, this is impossible as the same topic URL has …
-
from https://github.com/w3c/wpub/issues/15#issuecomment-320729321 by @bduga
> There is no way to crawl a script and find all the resources it might use or cause to be used. If all secondary resour…
-
The [Signature Validation](https://www.w3.org/TR/websub/#h-signature-validation) section says
> If the signature does not match, subscribers must still return a 2xx success response to acknowledge…
-
This should not be named the same thing as the spec. This confuses people into thinking that the spec somehow relies on the indieauth.com service.
-
I'm not sure if this came up only because of the type of subscriber I'm creating (the websub.rocks test suite), but I'm finding myself wanting a way for the subscriber to indicate its subscription sho…