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
Send out ActivityPub mentions (T627) #195
Conversation
be Note to work but I will open an issue for them and see what their reaction will be.
Latest changes look good 👍 Confirmed that mentions work with Pleroma. |
to the last because mastodon doesn't like https://my.instance/@me but https://my.instance/users/me
intermediate page (WIP) that shows the user profile page url
there it updates the table to include the handle. migrations WIP
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.
Just a few changes to make. Also getting this error during compilation:
./database.go:2476:61: remoteActor.GetSharedInbox undefined (type activityserve.RemoteActor has no field or method GetSharedInbox)
./database.go:2477:157: remoteActor.GetSharedInbox undefined (type activityserve.RemoteActor has no field or method GetSharedInbox)
Ack to all, will do. |
Also, just saw the comments on the Mastodon issue. Is that fixed on our end? |
Yes it works as expected, Gargron was right, I was thrown off because the first alias that webfinger returned was the @ version. |
Awesome -- works great with Mastodon 👍 Did some more testing and crashed the app with this post. Logs:
|
The crash was due to prismo and pixelfed not having sharedInboxes. I made GetSharedInbox() to return the inbox of the user so implementation won't need to care whether there is a sharedInbox or not (this is in activityserve) |
This fixes the `undefined: strings.ReplaceAll` build error.
Got everything up to date with
|
Ah, one more crash caused by this post:
And the mention links in that post cause a 500 and panic:
|
This is already fixed in upstream activityserve but that one uses upstream httpsig and not writeas/httpsig (I made those changes as a result of the review of pherephone) so I can't update it. Should I make the required changes to writefreely to support upstream httpsig? |
It turns out this is not necessary. If you do
everything should work. However the new httpsig removes the burden of setting the digest header manually and signs that header too so it might be a good idea to use that throughout. |
Awesome, just verified that that fixes the issue. I'll update Did more testing with this post. Last issue I'll address:
For the future, a few notes:
|
My two cents: this is an issue on their end, they should redirect based on the request headers if it's a request from a web browser. Especially since they don't provide a link to the human-rendering URL in the raw JSON data. |
@dariusk Good point -- just opened an issue for this: funkwhale#979. |
This fixes activityserve crashes caused by mentioning WriteFreely instances.
Wouldn't suggest hiding domain part - it would be the same as hiding domain part in e-mail address. Perhaps only makes sense to show only username when it is on the same instance (domain), but that wouldn't be the case - I believe in most scenarios users will be mentioning Mastodon account while actually posting from WriteFreely blog. |
- Export the func - Remove commented-out code - Use log, not fmt for debug messages - Remove named return parameters - Use standard var naming schemes - Fix spacing in queries and remove unnecessary chars
by making them absolute, not relative.
This notifies the user that the remote user doesn't exist, instead of showing a blank page. Ref T627
from /mention: Ref T627
I merged our latest changes, did some cleanup, moved the remote user route to I think there's still some work to be done around the |
This pull request adds code that scans the text of each post to be published for handles of the type @username@domain.tld, uses webfinger to ask ActivityPub endpoints about them, gets their inbox and actor IRI's and adds mention tags to the post. Finally it adds the users to the CC list of the recipients of the activity.
This works in pleroma but not in mastodon unless we set the object type to "Note" instead of "Article"
T627