-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activitypub/Sprint 1 #3193
Activitypub/Sprint 1 #3193
Conversation
6341dde
to
2d88b3f
Compare
2d88b3f
to
f88e88f
Compare
Additional Notes: I'm making use of existing
|
I've adhered to the styleguide, but running codesniffer is on my todo list. |
🎉🎉 🎉 🎉 Reviewing now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG with some suggestions to clearly scope AP methods in their names. THANK YOU!!
6812e15
to
744b43b
Compare
@benwerd Good to go! |
Actually, I've just found a bunch of errors and warnings running the code sniffer.
Will fix these... |
I can't seem to get Otherwise good to go! |
7bdef47
to
d3681cc
Compare
Ready to go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG!!!!! 👍
ActivityPub Sprint 1
#3186
Additional
<wbr />
injectiongetTags
regex to ignore url fragments parseHashTag() matches url fragments #3197Here's what I fixed or added:
This PR is focused on the Actor/user Profile and default enabled Post types (note, article, image).
The PR is pointing to idno:dev branch but perhaps a feature branch might be more appropriate.
/actor/
route specifically for ActivityPub profile<link rel="alternate" type="application/activity+json" ...>
Here's why I did it:
Separate Actor routes
Content-Negotiation
By adding separate actor routes, we seek to avoid Content-Negotiation (accessing the same route with different
Accept
headers) which can cause different servers, caching solutions to cache and serve the wrong version (html/json).Mastodon's Signature verification issue
While it would be possible to use existing routes with the
?_t=activitypub
template query, mastodon has a known issue with verifying HTTP signatures. Though the issue was recently solved in mastodon, it requires a second request for backwards compatibility.Checklist: (
[x]
to check/tick the boxes)