@oliphant
@HistoPol @snarfed
@snarfed.org @luca @PCOWandre @fedidevs @fediversenews @chronohart @activitypubblueskybridge
I’m wondering if that means there may be a functional difference between blocking the bridge vs adding the #nobridge tag?
@oliphant
@HistoPol @snarfed
@snarfed.org @luca @PCOWandre @fedidevs @fediversenews @chronohart @activitypubblueskybridge
I’m wondering if that means there may be a functional difference between blocking the bridge vs adding the #nobridge tag?
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected]
(2/2)
…just the pics, but the interaction with contacts.)
PS:
I know:
…there are tools for exporting (beside the point)
…many people here even autodelete there posts (utterly different use-case)
…it’s better than on most corporate sites (yes, but still just “rudimentary” flexibility, at least on #Mastodon.)
…that #Firefish(?) (still?) supports own-post migration (but that was no choice when I joined)
//
Like I said before, all of that is non-standard functions that the vast majority of the fediverse doesn’t even support.
I think you might be confusing ease and possibility. Few people even when moving instances within the fediverse are going to have that option (save for those moving between two instances of the same platform).
It’s not whether there’s some convenient tool to move your posts or other data.
It’s about whether after the move you can still get the same updates and talk to the same people.
Think of it in terms of the oldest surviving federated network: changing email accounts.
Before SMTP (the federated email protocol), you had to have accounts on every server with people you wanted to talk to. After you only had to have one account, but could readily move about the network to other servers if you got fed up with your server’s bullshit or another offered better services.
(And for the record, public bridges with no opt-out methods exist for email as well)
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected]