i'm really a bit sad and angry that i already have to introduce a cache just because #mastodon is sending follow activities that don't comply with the linked data principle. And I have to store data in my cache that doesn't exist in the #social_linked_graph

#activitypubdev #activitypub #rdfpub

and i can't clean my cache with a cron job because there are elements in there that never existed on the internet. what a s...
So cache also seems not the right idea for the following problem.

it gets even more exciting, i mean #friendica responds with HTTP 302 and gives me a url to an html page in the location

i thought i found a solution. because i implemented pendingFollowers, i can search for the object iri in the pendingFollowers and determine, if it's a acceptFollow useCase.

Seems to work, but i'm not able to determine the actor, that was sending the follow. so i cannot send the s2s accept

i could say that this is a problem of those who can no longer find their follow activity

#activitypubdev
#activitypub
#rdfpub

i think i have a knot in my head

@naturzukunft https://go4affm.com/c/?p=40585&o=19950

@naturzukunft@mastodon.social you're on the right track. That is how NodeBB handles it too.

Mastodon won't require you to send the follow URI back in the Accept activity's object. It will infer it from object.object. You can't rely on that though, Discourse for example uses the follow URI when parsing Unfo(Follow)

@julian And is Discourse providing the follow activity or is it also not in the #socialgraph
do you know a Discourse test instance ?

@naturzukunft@mastodon.social what do you mean by social graph? If you mean whether the uris resolve to something, I don't think they do. Even NodeBB doesn't have them resolving properly to activities. It's just used as a unique identifier.

For Discourse testing, I test against https://socialhub.activitypub.rocks/, but I am careful about it because that is a production site.