You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Can't get Misskey instance's follower-only post. #340
Hollo can't get follower-only post from Misskey instance.
Not only notification but also timeline cannot retrive that post.
Searching exact post url also doesn't work.
Thank you for reporting this issue. Let me break down what might be happening here, as there are actually two distinct problems:
Federation → Force refresh and URL search not working
I've confirmed that this is due to how Misskey implements its ActivityPub endpoints. When Hollo (or any remote server) requests a followers-only post with valid HTTP Signatures from an authorized actor, Misskey's /notes/:note endpoint only checks if the visibility is public or home, without verifying the HTTP Signatures at all. This means followers-only posts will always return 404 to remote requests, regardless of whether the requester is authorized.
This is different from how Mastodon handles it—Mastodon validates HTTP Signatures and returns the content if the requesting actor has permission. This would need to be fixed on Misskey's side.
Followers-only posts not appearing in timeline
This is a separate issue that needs investigation. There are a few possibilities:
Misskey might not be sending the Create activity to Hollo's inbox for followers-only posts
Misskey might be sending it, but Hollo might not be processing it correctly
Hollo might be receiving and processing it, but failing to display it in the timeline
To investigate this, I'll try to reproduce the issue under similar conditions. If I can't reproduce it, could you check your Hollo logs to see if there are any Create activities being received from your Misskey instance for followers-only posts? That would help narrow down where the problem is.
Hollo can't get follower-only post from Misskey instance.
Not only notification but also timeline cannot retrive that post.
Searching exact post url also doesn't work.