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:

Follow this group.
To post to the group, post on Mastodon as normal and @mention this group.
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 (boothcomputing.social)

submitted 8 months ago by [email protected] to c/[email protected]

48 comments fedilink hide all child comments

@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 (1 children)

@[email protected]

" But you would need to choose a platform with better permissions and moderation tools.

For example, you would want to control who can comment on your posts and be able to delete comments that are toxic. "

Very true.
However, I have a very strick block policy and in 98% of cases, the threat of using it, helps.
I always wonder a little bit what happens, after I block s.o.
My understanding is, that his/her posts remain, but we cannot see each others posts anymore (counter-block, mostly)

[–] [email protected] 1 points 8 months ago

@HistoPol On platforms like Hubzilla and Streams (and most other platforms that support threaded conversations), you have more control.

Basically, a threaded conversation is a container, and the person who started the conversation controls what goes into that container. If you, as the person who started the conversation, don't like what someone said, you can delete their post. Since it is part of your container, a delete notification goes out to everyone participating on your thread and the post gets deleted for them too. The person who originally posted it would still have their copy, and their followers might still see it, but it would no longer be distributed via your thread to people following the thread. You can also prevent someone from commenting on your post at all, which in that case, their comment gets rejected and is not distributed to anyone.

It works similar with forum topics, except the forum owns the initial conversation. The administrator or moderator can delete posts and restrict commenting.

The threaded conversation model gives you more control over the conversation than non-threaded platforms based on pre-X Twitter.