@aeva I do wish I had my post history, though

@mcc I guess I was more thinking about whether I would want my native ("just in case, but mostly just follow the other one") or bridged ("follow this one unless mastodon blows up I guess") should be like the 'glyph.im' toplevel, or whether there's a cost imposed to changing later

@glyph As far as I know changing later is virtually zero cost.

If it were me, I would put a bridgyfed tag in like bridgy.glyph.im or bridged.glyph.im or mastodon.glyph.im. this would avoid confusion if someone tried to interact with your bridged account like a regular bsky account, which it isn't*exactly*

@mcc I mean… creating that *illusion* is the whole point! But yeah you’re probably correct. Perhaps for symmetry I will just do mastodon.glyph.im and bluesky.glyph.im

@glyph I do think having a merged feed, if it's possible, would be valuable for a few reasons

@mcc I have about 5 minutes a month for bluesky maintenance and this seems like that might be exceedingly tricky; but the dns thing looks like it tractably fits into my budget

@glyph the DNS thing will take no more than five minutes no exaggeration. The most time consuming thing will be remembering where everything is in your domain registrar control panel.

@glyph I don't personally get the appeal, but I feel like "simply add post migration" is probably the easier hypothetical problem to just go and solve, on account of activitypub and mastodon not being proprietary and all that

Every month that this proposal or an equivalent isn't implemented I gain further brain damage

https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

@liquidparasyte @aeva oh no. now I know it exists, that it's existed for well over a year, and that it isn't implemented yet, and I am also taking psychic damage. this is an infohazard

It's worse than that, Hubzilla and its decendents have had "nomadic identity" for over a decade now! But, since Mastodon gGmbH runs the largest instance (where people start out by default) , at some level it's not surprising they haven't prioriized this functionality even though people have been saying for years how important it is.

More positibely, https://github.com/VyrCossont/slurp lets you import your Mastodon posts to a GoToSocial instance, and Sharkey also provides the ability to import Mastodon posts. And the LOLA spec, which got some discussion last year, is compatible with the Data Portability work. So perhaps things will improve at some point.

@glyph @liquidparasyte @aeva

@thenexusofprivacy @liquidparasyte @aeva fantastic links. I should really start backing up my Mastodon profile personally with one of these