0
@oliphant
(boothcomputing.social)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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:
- 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 6 months ago
@[email protected]
"...Friendica and Hubzilla) that will natively support Bluesky. If we boost your post, then it'll be copied over to Bluesky with no actual connection to you in the network,..."
Besser another question, as so far, I had been in favor of #Friendica;
Does this mean if I were 2 use these 2 platforms, I could never prevent my posts / content from being seen on #Elmo's PayPal platform?!?
Or is there really no difference?
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected]
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] The gist is that if you want to prevent your posts from being shared outside of screenshots and quote-posts (where the contents of the post are just copied) the only option is to join a whitelist-only server.
These are servers that federate only with explicitly approved servers, ie. if someone tries to connect from any instance not on that list they're blocked by default.
That's kinda the root of the argument here where a great many people have a false assumption that the fediverse is about control of your data when it is quite the opposite. It's like trying to protect your art from being used by others... by marking it Creative Commons.
The entire design of all federated systems is around open sharing, you can only get control over how your posts spread in a closed system with little or no federation.
As far as whether or not you use those platforms, my example was regardless of whether you're a user.
My server federates across multiple different protocols, if I boost your post then your post is probably being made available to multiple different networks automatically.
The protections and control involved in federated networks is not in how your data is shared, but in how your access is controlled.
In the fediverse you don't have to worry about a bad admin blocking your access to everyone you know, you can freely move accounts between instances. If you piss of Elon for instance, you're cut off from Twitter and everyone on it... full stop... but if you piss off your instance admin, you just move instances and can still connect with everyone.
It's also control over your experience in that you're not relying purely on what their algorithms think you should see. If the instance your on has an algorithm set up that you don't like, then you can move instances to one that has the algorithm you like.
You also have protections against enshittification (the process by which those other networks will draw you in with great features, and then once you're locked in slowly shut down or degrade those features). If features that are important to you start getting shut down on your server... you can move to one that keeps them. If a platform developer does it, another developer can fork the project to keep those features alive.
You also have choice in terms of clients and experiences. You're using Mastodon and I'm on Friendica (I know your instance type because Friendica shows me a little icon beside posts). I vastly prefer the Friendica experience, and I have the choice to use that. And I can use that without forcing you to use the same interface.
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected]
(1/n)
I think I owe you a quick #INTRO, as I have not been in contact with you before, so you might better understand my concerns.
I am a political commentator, as well as an activist. This is why I cannot remain silent:
This is a global super-election year. #Democracy is up for grabs in about 50 countries.1)--This is how the billionaires and the #autocrats like #Putin and #Xi see it, or how #YoelRoth...
@HistoPol
For someone like you, you would probably want to post publicly, to as many platforms and protocols as you can, so you reach a wider audience. 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. Mastodon does not have this capability, but most platforms that have threaded conversations give you that ability.
@[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)
@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.