Tim Chase on Nostr: nprofile1q…fq27h The ActivityPub protocol¹ has the idea of URLs associated with ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqttzv6h2trz7zamy7l767kf6057jmz07dfcpssmuvxp3cv2tgtx4q2fq27h (nprofile…q27h)
The ActivityPub protocol¹ has the idea of URLs associated with activities, but leaves their fetching/caching up to the individual servers/clients. A lazy server/client might do zilch and force the user to fetch it every time.
That said, I don't think there's much of a way to juice the traffic to increase your own SEO scores. However, you might get some (negligible) insight into your followers due to the servers they come from. However, since they're following you, your follower-list also has that information and is likely more easy to analyze. The AP/AS protocols basically contact all your followers' servers with a "Hey, new post" message that gets put in users' Inbox. Then those servers might download the URL content (optionally caching it) when users read your post, or might leave it to the client.
⸻
¹ I spent far too much time reading into the guts of the ActivityPub/ActivityStreams/JSON-LD specs and they're a special kind of horrible in their YOLO underspecification. My WIP write-up of my findings/disappointments thus far: https://blog.thechases.com/posts/activitypub-activitystreams/
The ActivityPub protocol¹ has the idea of URLs associated with activities, but leaves their fetching/caching up to the individual servers/clients. A lazy server/client might do zilch and force the user to fetch it every time.
That said, I don't think there's much of a way to juice the traffic to increase your own SEO scores. However, you might get some (negligible) insight into your followers due to the servers they come from. However, since they're following you, your follower-list also has that information and is likely more easy to analyze. The AP/AS protocols basically contact all your followers' servers with a "Hey, new post" message that gets put in users' Inbox. Then those servers might download the URL content (optionally caching it) when users read your post, or might leave it to the client.
⸻
¹ I spent far too much time reading into the guts of the ActivityPub/ActivityStreams/JSON-LD specs and they're a special kind of horrible in their YOLO underspecification. My WIP write-up of my findings/disappointments thus far: https://blog.thechases.com/posts/activitypub-activitystreams/