Re:ActivityPub: a federated social web standard
by devrandomguy on Thursday May 25, 2017 @12:12PM
(#14418195)
Looking at the ID format in the first example, I have to recommend against including the protocol ("https:") in a key/ID. This makes it hard for people to later upgrade from HTTP to HTTPS, because it breaks all of those references. It also makes it hard to try out new protocols side by side, like IPFS.
[ Parent
| on HN ]
Re:ActivityPub: a federated social web standard
by blowski on Thursday May 25, 2017 @12:19PM
(#14418245)
A URL always includes the scheme. `http://www.example.com/1/ ` and `https://www.example.com/1/` could represent different content. If you want to change the scheme but keep the old links working, you need to redirect from the old to the new.
Re:ActivityPub: a federated social web standard
by Filligree on Thursday May 25, 2017 @12:28PM
(#14418308)
That is the definition of a URL, but not a law of nature. If these keys would be more useful with the scheme being implicit, then perhaps they shouldn't be URLs.
Re:ActivityPub: a federated social web standard
by cat199 on Thursday May 25, 2017 @02:51PM
(#14419261)
> This makes it hard for people to later upgrade from HTTP to HTTPS, because it breaks all of those references.
While someone else pointed out the rest of the URL could conceivably point to different content, in practice, it seems like most deployments have a 1:1 correspondence and will redirect from http://(.) to https://(.) when SSL is deployed so this is not so critical for the http(s) case imho..