Cross-origin Link headers
Technical Discussion
4
Post
2
Autori
1
Visualizzazioni
-
evan@cosocial.ca question for you — is there any guidance in the spec about whether
idandurlfor a given AP object needs to be same-origin?js@podcastindex.social and I were recently discussing this in a related context (
Linkheaders specifically, for HTTP discovery) and I wasn't entirely sure whether this was a valid use-case. -
@julian @js @trwnh there's a whole section on verification in the discovery report.
https://swicg.github.io/activitypub-html-discovery/#verification
-
@julian @js @trwnh there's a whole section on verification in the discovery report.
https://swicg.github.io/activitypub-html-discovery/#verification
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
rimu@piefed.social got it, thanks. How do you reconcile the Delete coming from outside your domain? I would figure Mastodon would drop those Deletes.
Edit: that was confusing wording... I mean — how do you sign a Delete for an object that doesn't belong to your instance?
-
Looks like for Mastodon we just do a bare Delete.
-
@julian @js @trwnh I think it's also important to note that having HTML Web pages, JSON API endpoints and rich media all on different domains is a pretty common mid-sized Web app deployment these days.
-
@julian @js @trwnh there's a whole section on verification in the discovery report.
https://swicg.github.io/activitypub-html-discovery/#verification
-
@julian @js @trwnh Absolutely not! Same-origin is useful for some verification tasks but otherwise is completely orthogonal to ActivityPub.
-
evan@cosocial.ca question for you — is there any guidance in the spec about whether id and url for a given AP object needs to be same-origin?
js@podcastindex.social and I were recently discussing this in a related context (Link headers specifically, for HTTP discovery) and I wasn't entirely sure whether this was a valid use-case.
-
rimu@piefed.social Do you send the Undo(Announce(Create)) as well for microblog compatibility?
-
@julian Well, that's good to know 😀 That said, the other aspect: I believe the biggest thing ActivityPub brings to the world is networking existing communities using existing platforms. They're not "legacy", they're first class. It's completely normal to build a platform with a specific schema for your own needs, and then hook up to AP later. To the rest of the network, it looks like you're extending JSON-LD in exciting innovative ways, while to you it just looks like dumping rows into JSON with a weird @context element.
