Conversation

Notices

1. Embed this notice
   jonny (good kind) (jonny@neuromatch.social)'s status on Friday, 13-Dec-2024 10:50:10 JST jonny (good kind)

   re-upping this question about changing a masto handle within-instance: https://neuromatch.social/@jonny/113608532252292745

   has anyone tried to do a handle-change within-instance preserving post/interaction history, at least locally? it seems like we should be able to just manually make the changes in our DB and then make a manual redirect for all the old URIs to the new URIs. It would be great to keep everything and sync across the network but keeping bookmarks, posts, (our representation of) boosts from the person's perspective, even if it's out of sync elsewhere would be fine.

   • Embed this notice
     wizzwizz4 (wizzwizz4@fosstodon.org)'s status on Friday, 13-Dec-2024 10:50:07 JST wizzwizz4

     in reply to

     @jonny I would say that ActivityStreams's Move action is within the spirit of Cool URIs Don't Change.

     However, I've just re-read the original article (https://www.w3.org/Provider/Style/URI), and… hm. This is not nuanced enough. The rest of Tim BL's 1998 style guide is outdated, wrong, or overly-simplistic, but my sentimental attachment to this particular article was preventing me from seeing its flaws.

     Do you know of a better canonical reference for how URIs should work?

   • Embed this notice
     jonny (good kind) (jonny@neuromatch.social)'s status on Friday, 13-Dec-2024 10:50:08 JST jonny (good kind)

     in reply to

     now and as always i remind everyone tempted to tell me that "cool URIs don't change" that i disagree and here is one very obvious reason why - people change.

     alcinnz repeated this.
   • Embed this notice
     jonny (good kind) (jonny@neuromatch.social)'s status on Friday, 13-Dec-2024 10:50:09 JST jonny (good kind)

     in reply to

     Looking at the masto status and account update services, and the account move service, it's not entirely clear to me why it should be forbidden to update the uri and username fields - that seems like it's implicitly allowed by the ActivityStreams Move action, and AS requires that all objects have an absolute URI as an id but doesn't specify that they can never change. Neither does ActivityPub. ActivityPub actually specifies that an Update should completely replace the old object and so it should be possible to replace the URI/id.