-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Posts delivered by buzzrelay is blocked by Misskey #4
Comments
Simply replace the |
I wonder if this is this really the part of Misskey that processes posts from relays? |
They are not duplicates, but Misskey would show both the renote event and the note being renoted in the global timeline, just like how it treats normal renotes, but not suitable for a relay in my opinion (How does Mastodon handle this? I guess the post being boosted is not shown on timeline?) It is part of the process, the UnrecoverableError appears every time a relayed post arrive. I'm still a noob in fediverse and my knowledge about ActivityPub is extremely limited so please correct me if I made stupid mistakes again, but according to my understanding of the protocol,
|
Relates to Github issue #4: ActivityPub implementations may check that the host in this URI is the HTTP-signing host. https://github.com/misskey-dev/misskey/blob/e2261b63e9053fb5116dd0ef393f464bf16da190/packages/backend/src/queue/processors/InboxProcessorService.ts#L159
Now running with 89938a7. Does that improve things? Does that break things? It doesn't look like I have to actually serve these URLs. So far I'm not getting requests for them. |
It works fine on my Misskey instance, I hope it does not break other fediverse servers. |
Problem
Subscribe to buzzrelay on Misskey does not show any posts because they are all blocked by the server with the following error:
Findings
Misskey will check if the host of the signature's keyId is equal to the host of the activity id, and activity will be blocked if they do not match:
https://github.com/misskey-dev/misskey/blob/e2261b63e9053fb5116dd0ef393f464bf16da190/packages/backend/src/queue/processors/InboxProcessorService.ts#L159
The text was updated successfully, but these errors were encountered: