@julian @johnonolan @angus there's a whole task force for this. You've commented on it. Why does this need to be discussed?
ActivityPub
Focused discussion related to ActivityPub integration in NodeBB
This is a forum category containing topical discussion. You can start new discussions by mentioning this category.
@evan@cosocial.ca this was to ask the mentioned parties for Ghost and Discourse to implement.
I mentioned you to keep you in the loop because task forces achieve nothing without implementors doing the work.
Object IDs should really be retrievable by http GET. See section 3.2 of https://www.w3.org/TR/activitypub
@rimu@piefed.social yes, that's right. I'm specifically referring to object urls though, which tend to be more user facing.
You could save yourself some hassle and make urls and IDs the same value. But you do you :)
@julian @johnonolan @angus @evan
Why 301 and not 302?
I am using 302. Probably chose it because everyone else was using it.
@silverpill@mitra.social 302/307 is also fine by me. Probably safer from being accidentally cached and may be more appropriate in this situation.
@johnonolan@mastodon.xyz A solution is only needed if the resource id is different from the URL (which in Ghost's case, is true).
You don't have to use a redirect. If your software is capable of doing it, you can serve the ActivityPub object directly from that route's controller; that's what NodeBB does.