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 ๐
teledyn ๐
Matthias Pfefferle