It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
I don’t know. I would like to subscribe to someone on Threads from Mastodon (since both are Twitter alternatives), if they don’t have Mastodon account (which let’s be honest they probably don’t). Zuck does not get any of my data (besides what’s available publicly anyway). If Threads decides to go full EEE, I’ll stop getting updates from people on Threads, same as I don’t get updates from people on IG right now. I think proliferation of ActivityPub protocol would be the greatest advantage.
Moreover, I think we should follow the email architecture - I might use i.e. Proton Mail, but it does not prevent me from sending emails to Gmail, which I think is a bad provider, who collects a lot of user data. In fact if Proton Mail forbade sending email to Gmail I would be really displeased about that.
The goal is to allow people to choose where they want to go and ActivityPub is what can help with that, unlike blocking Threads.
i ONLY want to conter your argument with email and activityhub: on email people choose to send stuff to a very limited amount of people except maybe newsletter and scammers. with threads, which should have already multiple times of osers compared to the fediverse, will flood the content to /all. Of course there are cool people but i think the entire fediverse culture will be blown away by threads in an instand. And with their weird moderation (especcially small) servers here will have large problems trying to moderate it
but by email there is no mass broadcasting to the public so it does not need to be moderated
Email is not only 1:(small N). Maillists do exist and and are used to facilitate discussions between a large amount of people via email. They are also often public so anonymous readers and search indexers can use them.
/all is certainly an interesting thing - default Active sorting calculates a rank based on the score and time of the latest comment, with decay over time. If Threads are connected they would dominate /all. But there can certainly be adjustments, we can create a new sorting style, and make it default. For example:
Posts are deprioritized based on MAU or some similar metric. The larger the MAU, the lower the post is ranked assuming the same engagement. If the post got 100 upvotes on an instance with 1000 users, it’s probably a much more interesting post, than the post that got 100 upvotes on an instance with 100 000 000 users.
Posts are (de)prioritized based on instance source. For example setting Threads to -1000 would effectively remove it, setting Threads to -50 would allow you to see only super active posts. On the other hand if we want to see more content from less populated instance we might set it (i.e. german lemmy feddit.de) to the score of 100.
Instances can provide a limited number or percentage of /all - i.e. after we got 10 posts from Threads, stop getting posts from this instance.
I couldn’t agree more. Racing to block Threads when it’s completely unclear if Threads will even actually ever federate and what the implications of them federating will even be seems incredibly short sighted. Imagine how much innovation would have been lost on the internet if web server admins raced to block Google Chrome from accessing their content because they have some personal beef with Google.
I don’t know. I would like to subscribe to someone on Threads from Mastodon (since both are Twitter alternatives), if they don’t have Mastodon account (which let’s be honest they probably don’t). Zuck does not get any of my data (besides what’s available publicly anyway). If Threads decides to go full EEE, I’ll stop getting updates from people on Threads, same as I don’t get updates from people on IG right now. I think proliferation of ActivityPub protocol would be the greatest advantage.
Moreover, I think we should follow the email architecture - I might use i.e. Proton Mail, but it does not prevent me from sending emails to Gmail, which I think is a bad provider, who collects a lot of user data. In fact if Proton Mail forbade sending email to Gmail I would be really displeased about that.
The goal is to allow people to choose where they want to go and ActivityPub is what can help with that, unlike blocking Threads.
i ONLY want to conter your argument with email and activityhub: on email people choose to send stuff to a very limited amount of people except maybe newsletter and scammers. with threads, which should have already multiple times of osers compared to the fediverse, will flood the content to /all. Of course there are cool people but i think the entire fediverse culture will be blown away by threads in an instand. And with their weird moderation (especcially small) servers here will have large problems trying to moderate it
but by email there is no mass broadcasting to the public so it does not need to be moderated
Email is not only 1:(small N). Maillists do exist and and are used to facilitate discussions between a large amount of people via email. They are also often public so anonymous readers and search indexers can use them.
/allis certainly an interesting thing - default Active sorting calculates a rank based on the score and time of the latest comment, with decay over time. If Threads are connected they would dominate/all. But there can certainly be adjustments, we can create a new sorting style, and make it default. For example:/all- i.e. after we got 10 posts from Threads, stop getting posts from this instance.I couldn’t agree more. Racing to block Threads when it’s completely unclear if Threads will even actually ever federate and what the implications of them federating will even be seems incredibly short sighted. Imagine how much innovation would have been lost on the internet if web server admins raced to block Google Chrome from accessing their content because they have some personal beef with Google.