Post ATJSuaKOeaSgMFCFpQ by d3786735d619da298a2c8718c5b30c6c7711a35adeca30e17e81099f03efe6e7@mostr.pub
 (DIR) More posts by d3786735d619da298a2c8718c5b30c6c7711a35adeca30e17e81099f03efe6e7@mostr.pub
 (DIR) Post #ATJSuaKOeaSgMFCFpQ by d3786735d619da298a2c8718c5b30c6c7711a35adeca30e17e81099f03efe6e7@mostr.pub
       2023-03-05T12:17:00.000Z
       
       0 likes, 0 repeats
       
       hey @alex mostr AP-side usernames for the nostr side sux dlux. Shit needs to get fixed. You already have NIP05 support for bridge participants (eg https://nostr.sharivegas.com/ShariVegas_at_pleroma.nobodyhasthe.biz@mostr.pub ), how about aliasing the other direction? (eg: @sharivegas_at_nostr.sharivegas.com@mostr.pub )Could we utilize the alsoKnownAs property and expect it to work in Mastodon/Pleroma/Soapbox?
       
 (DIR) Post #ATJSuaoWqYZ3rhIJnM by alex@gleasonator.com
       2023-03-05T17:57:03.529140Z
       
       2 likes, 0 repeats
       
       @d3786735d619da298a2c8718c5b30c6c7711a35adeca30e17e81099f03efe6e7 The only way to fix it is by exposing a new property to the frontend and patching it there. Every client will have to update. I’m figuring out how that will work now.
       
 (DIR) Post #ATJp1X3JQciLDXvJWC by ShariVegas@pleroma.nobodyhasthe.biz
       2023-03-05T22:04:54.695150Z
       
       0 likes, 0 repeats
       
       @alex @d3786735d619da298a2c8718c5b30c6c7711a35adeca30e17e81099f03efe6e7 That's some bullshit, bro.How about just hooking into existing migration infrastructure? Once a user's got a NIP05 and you get it as part of a kind 0, do the migration stuff mastodon/pleroma does?