Timeline
Post
Remote status
Fetching context…
This post replies to something we haven't fetched yet. We'll try to pull in the missing thread context in the background.
@a @silverpill
>my issue is between akkoma-akkoma and akkoma-gts mostly, where akkoma seemingly drops some follow requests instantly (maybe they are "already seen") and also some profiles just will not load at all...
Do you observe the same with Pleroma? If not, then if signed fetches are involved, I'm somewhat certain what the issue is. I've seen this happen before with Pleroma and @mkljczk fixed it recently I think. Akkoma would need to backport those fixes in that case.
>my issue is between akkoma-akkoma and akkoma-gts mostly, where akkoma seemingly drops some follow requests instantly (maybe they are "already seen") and also some profiles just will not load at all...
Do you observe the same with Pleroma? If not, then if signed fetches are involved, I'm somewhat certain what the issue is. I've seen this happen before with Pleroma and @mkljczk fixed it recently I think. Akkoma would need to backport those fixes in that case.
Replies
2
@phnt @a @silverpill the one auth fetch-related issue on Pleroma I fixed recently only applied to Pleroma instances that enforce signed GET requests, which are virtually nonexistent.
@mkljczk @a @silverpill It is almost non-existent in Pleroma, but very popular in Akkoma, maybe even the default (too lazy to check). If a remote instance needs to fetch an actor to figure out who you want to follow, ie. from a new instance you want to follow somebody whose handle you know but they haven't interacted with you yet, that would break as I understand it.