People who want to host static sites typically are not the same ... • Aaron Parecki

nightpool https://github.com/nightpool • Jul 11
It probably wouldn't be super hard to write a nginx module to enable content negotiation, if there was an interest in it

On Wed, Jul 11, 2018 at 7:11 PM Aaron Parecki notifications@github.com wrote:

This would allow a static site to serve ActivityPub objects as well as human-readable HTML. Currently it's not possible to do this, since static sites can't do content negotiation of course.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/w3c/activitypub/issues/310#issuecomment-404338732, or mute the thread https://github.com/notifications/unsubscribe-auth/AAORV8zh504acM1VU-qjYTFjpKw1xwpDks5uFoYjgaJpZM4UdtrM .

People who want to host static sites typically are not the same people who are going to custom-compile their nginx in order to install a content negotiation module.

The two very popular use cases that don't work when content negotiation is required are:

1) hosting a site on GitHub Pages, Netlify, Amazon S3, etc

2) using a caching CDN like CloudFlare

It would be really sad to completely exclude these very popular services from participating in the ActivityPub network.

Even Mastodon supports alternate URLs for their ActivityPub representations of pages, e.g. https://mastodon.social/@Gargron vs https://mastodon.social/@Gargron.json so it seems like it wouldn't be a huge stretch to have it advertise those URLs on the HTML pages.

Portland, Oregon, USA • 88°F

Wed, Jul 11, 2018 5:07pm -07:00

Have you written a response to this? Let me know the URL:

Posted in /replies using quill.p3k.io