Fediverse Help. We have successfully got activities to publish from TrueFans.social to other AP clients.
However for my own acct I have messed up in testing. The original TrueFans name was @sam and this worked. We were testing if I could change the name as a feature. I changed it to @sa and changed it back and now my posts wont federate. I follow @sam but the minute I try to federate the activity Mastodon unfollows my truefans acct and so no @sam activity appears here?
@samsethi are you using usernames in actor URLs?
@thisismissem yes - https://truefans.social/sam
We have decided not to allow users to change this name in the future. When they login they pick their nickname and after that we give them an AP account - truefans.social/username - we also give them a wallet username@truefans.fm - so if a user changes their nickname it causes problems. So we wont; until we understand more. BUT my own account is acting weird. If we can't fix it I will have to delete my acct in TrueFans and start again. Thanks
@samsethi I can't find the document now, but somewhere there's a document that says "don't use usernames in URLs, because then you can never change the username"
So instead use a unique identifier that isn't user selected, then you can "change" usernames, though servers will likely not pick up the change. Probably a Primer page needs to be written on this
@thisismissem thanks. I have read everything on W3C, Fedify and Evans book and must have missed the do not use a name. We need to think this through but I am wondering how I can fix my current issue. I have deleted my public/pvt keys and removed all cookies to try and get it to reset. The good news all AP clients see my truefans.social acct again and I can follow.
@samsethi probably needs a Move activity between the two Actor URLs, I assume the keypair didn't change?
Oh, you deleted the keys.. that actor is burnt then, you need the keypair to be able to issue a Move or Delete for an Actor
@thisismissem thank you will try