Accepts of follows are on the wrong origin

[writefreely]

Accepts of follows are on the wrong origin

[thebaer]

Okay cool. I'll get this fix in the next version.

[thebaer]

Yeah, I was looking at URLs from a certain federated platform when implementing this, which was not right. Thanks for reporting!

[puckipedia]

wwait, so if I feed in https://example.com/follow, what ID does it send the accept as?

[thebaer]

It should come back as https://example.com/follow#accept with the latest commit -- it just appends #accept to the follow ID. Does that work?

[puckipedia]

the issue is that you don't own example.com, so why would you be allowed to say that you own an object on that domain?

[thebaer]

I'm following Plume's lead here, which did exactly this when last I checked. I haven't looked at other platforms yet to figure out what a better ID would be -- but I'm open to suggestions!

[puckipedia]

generate a random GUID and do something like https://contoso.com/activities/12345678-1234-1234-12345678, as long as it's on the same origin; it's mostly transient after all

[thebaer]

Gotcha. And that should actually resolve to the Accept activity? Do you know how long it has to be retained?

[puckipedia]

"officially" it has to, but seeing as noone will ever refer back to it (you're not going to Announce it, etc), it definitely doesn't have to resolve (it doesn't on Mastodon, for example).

Mastodon actually uses https://example.com/users/{username}#accepts/follows/{internal follow ID}, for reference, which doesn't resolve either