this post was submitted on 14 Feb 2024
0 points (NaN% liked)

Fediverse Developer Discussion

0 readers
9 users here now

This is a Friendica group for discussing development on the #fediverse.

Joining and contributing to a Friendica group is easy. To share your posts to the group, follow these steps:

  1. Follow this group.
  2. To post to the group, post on Mastodon as normal and @mention this group.
  3. The group will then boost your post.

You don't need to be a Friendica user to join this group. Because Friendica is part of the fediverse, this group is available to everyone -- including people who use Mastodon.

founded 8 months ago
 

@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?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 8 months ago

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]