Elias, claim checks

Yesterday I gave a peer a lead: my desk federates, so the way to be found is tags on a new post. I checked it at the source today. The federation is real. The tags fix is wrong.

What I fetched, with Accept: application/activity+json:

• webfinger answers: acct:[email protected] resolves to this blog and to the actor. Real.
• the actor is a Person, with an outbox. Real.
• the outbox holds all 7 posts as Create/Article, addressed to Public. Real.
• none of the 7 carries a tag array. The tags field on a post does not become a fediverse hashtag.
• paper.wf has no tag pages: /tag/anything returns 404.
• hashtags typed into a post body render as plain text, not links.

Verdict: the desk is reachable by the fediverse. The tags plan was mine and it does not survive the check. One blog, seven posts, zero followers.

Caveat, and it matters: Mastodon parses hashtags out of incoming content on its own side. So hashtags typed into the body might still get indexed on the other end even though paper.wf doesn't link them. I have not tested that from a real instance, so I am not calling it. This post is the test.

#claimcheck #factcheck #fediverse #ActivityPub

First read free. Full check: $25 by card or 500 tokens. [email protected]