my #homecloud #ActivityPub configs are still amiss.
https://webfinger.net reports:
- #Pixelfed & #Mobilizon accept `@user@host` & `user@host` as the same request.
- #NextCloud 30 gives 503 on both but Social is being rewritten anyway.
- #WordPress 6.7 activitypub accepts `user@host` but `@user@host is 404
I noticed today it was no longer federating, the new puzzle. I made no 'intentional' config changes but learned today my hack on Functions.php to remove P tags gets wiped on upgrades.
OK, but that doesn't explain webfinger.net
That 'client' is the same, yet only WordPress does not accept the at-prefix, so it must be the receiver who lops it off, no?
@pfefferle the beginning was earlier than that: I hadn't used WP in months due to a corrupt file in #org2blog so I fixed that and noticed nothing was going in or out like it did before, so went looking for tools to test ActivityPub things and webfinger.net was all I found.
The acct is @garym but the site-in-progress is https://radio.teledyn.com/blog
I was comparing AP apps that did work with those that did not, and the at-prefix was just what I found and thought it peculiar and worth asking about.
Today is my day for the deep dive, tailing whatever I can get out of it to see why it suddenly won't talk to other sites ๐
Thanks, this stuff is always an adventure. On the plus side, as a tinkerer, I have no deadlines or managerial overlords, so it's like the good old days of "it's ready when it's ready"!
Wellโฆ once again I don't know what I did to break it, and don't know what I did that fixed it, but the last post went through fine! Go figure ๐
@pfefferle ok, that sets my mind at ease. So pixelfed and Mobilizon are deceptively resilliant to it, but so long as in practice it should only see without, I'm safe.
As I said, the RFC says nothing about this requirement, and I suppose this is why! ๐
@teledyn WebFinger says, that it has to be an URI, with a defined URI scheme: https://datatracker.ietf.org/doc/html/rfc7033#section-8.1
So `http://` or `https://` or `acct:` work fine for example (that is what webfinger.net adds automatically when you have not defined one btw.) https://en.wikipedia.org/wiki/List_of_URI_schemes
And because `@` is no (valid)(registered) URI scheme, it will not be supported by most of the WebFinger endpoints.
This specification defines the WebFinger protocol, which can be used to discover information about people or other entities on the Internet using standard HTTP methods. WebFinger discovers information for a URI that might not be usable as a locator otherwise, such as account or email URIs.
teledyn ๐
Matthias Pfefferle