Hard to overstate how important this news is. #Threads
https://www.theverge.com/2023/12/13/24000120/threads-meta-activitypub-test-mastodon
cc: @fediversenews
Hard to overstate how important this news is. #Threads
https://www.theverge.com/2023/12/13/24000120/threads-meta-activitypub-test-mastodon
cc: @fediversenews
@stinerman @evan @tchambers @fediversenews
[email protected] should have AP enabled, but we are seeing weird HTTP connection resets at the moment. We are working with Meta engineers to try to understand what happens. For now, things point to an blocklist not having been removed on their side when they opened it publicly.
I don't trust Meta on this. They will try to take control of it all.
Fortunately no need to trust anyone. This plan remains my best thinking on how to both welcome the Fediverse to such partners but also protect it. https://www.timothychambers.net/2023/06/23/project-and-the.html
With the #meta #Project92 or #Threads Fediverse offering, there has been a, well, robust discussion of how to avoid threats looming. Those advocating mass-preemptive defederation make three cases for it. ➡️ To avoid data mining … However, defederation does virtually zero to avoid any big tech entity scraping all the Fediverse public social graph today - Want proof? See here: is.gd/q8U2pv But what if they merge that Fediverse data with their own internal data from IG isn’t that worse than just scraped data?
@dheadshot @MichaelBishop @fediversenews
I specifically argue in the link in my post the only real defence against EEE.
@MichaelBishop @tchambers @fediversenews
I agree. For one, the "View On Threads" button in every post suggests they are doing EEE – embrace, extend, extinguish.
This kind of behavior should result in automatic defederation.
#threads #defederate #eee
@crossgolf_rebel @fediversenews
Both risks and opporunities with it to be sure. My thoughts remain as they were here:
https://www.timothychambers.net/2023/06/23/project-and-the.html
With the #meta #Project92 or #Threads Fediverse offering, there has been a, well, robust discussion of how to avoid threats looming. Those advocating mass-preemptive defederation make three cases for it. ➡️ To avoid data mining … However, defederation does virtually zero to avoid any big tech entity scraping all the Fediverse public social graph today - Want proof? See here: is.gd/q8U2pv But what if they merge that Fediverse data with their own internal data from IG isn’t that worse than just scraped data?
@profcarroll
Apparently their plan is to roll it out incrementally -- Evan described it as "First read-only, then with likes and shares, then replies, then two-way follow."
https://cosocial.ca/@evan/111567567468691751
[No, I don't know what "read-only" means.]
@[email protected] sure. Threads fediverse support is going to be rolling out in stages over the next year. First read-only, then with likes and shares, then replies, then two-way follow. They are mostly concerned about privacy for Threads users, so they won't be federating in ways that put that privacy at risk.
@profcarroll We're all reading tea leaves. My take is that in an early stage posts from Threads will federate OUT, but posts from the Mastodon/etc Fediverse will not federate IN to Threads -- for that early phase. (Which makes sense from a dev POV)
Crawl, walk run.
So replies back to Threads posts from the Fedi, and DM's to Threads users from the Fedi would not be seen by Threads users initially.
@tchambers @fediversenews I already experienced the September That Never Ended. Bring it on.
Too bad our client software filtering and blocking capabilities are far far below what could be done in Usenet clients back in the day.
What are the most important missing elements you see, Sami?
@tchambers @fediversenews I’ve been meaning to do a dive into news readers of old, because the conceptual overlap between usenet and fediverse is interesting (to me).
Admittedly it’s been some time, but I remember newsreader killfiles (reminder to not let engineers name things) being able to express things like “I don’t want to see Mallory’s responses to Zach when the subject line mentions horses, unless it’s about horsepower measurements”. Or kill [sic] any mention of Elon Musk unless it’s accompanied by the words spacex or indictment, and if the latter, boost it to the top of my feed.
Now we’re just blocking words wholesale like some bronze age peasants.
@petersuber @sjuvonen @tchambers @fediversenews pluggable filters on fedi ... pluggable filters on fedi ... pluggable filters on fedi
plot twist 2038: @deutrino finally gets his life together and implements pluggable filters on fedi, then dies the next day
@lampsofgold @petersuber @sjuvonen @tchambers not that I know of on a user-pluggable level (Pleroma/Akkoma's MRF would otherwise count?)
I'm also not fully caught up with the fedi development scene at all though, been too preoccupied. so I may be wrong.
@sjuvonen @tchambers @fediversenews My favourite, by far, was Gnus, which supported very flexible post scoring, adding or decreasing weight based on different properties of the post. Highly scored articles stood out, low scored ones vanished. Much better than killfiles or ungainly muting of keywords.
https://www.gnu.org/software/emacs/manual/html_node/gnus/Scoring.html
@tchambers
my concern is I am not sure instance moderators on Fedi yet have the moderation tools so desparately needed for this volume
Speaking for myself (I run Indieweb.social) we have prepped 3X the moderation resources as normal. But also from what I read in the tea leaves, this is a gradual roll out over a good deal of time.
Hey, curious... Have there been any updates wrt security of Threads (.net)?
One finding:
"Being such a modest website in terms of functionality, Threads is a gift to scammers. Our experts have already discovered phishing pages imitating the web version of the social network and collecting users’ logins and passwords — which match at least the login data for Instagram"
https://www.kaspersky.com/blog/threads-privacy-questions/48630/
So basically one way cross-posting from Threads to the Fediverse... for now, trust us. Kind of like an RSS feed. No ability to comment back from Mastodon, and no ability to post on Threads from Mastodon. If you want to respond to something you see from Threads, you will need to create a Threads account and go there. Seems like a pretty obvious Threads marketing initiative and a play to undermine the Fediverse. Kind of as predicted, this is not "federation".
@mastodonmigration interesting… you’re not wrong here. But it’s not like mastodon users don’t already know about threads. If it was so good we’d already be there in full yeah? I see even just this functionality as just more capabilities for us.
A lot of people trying to find ways this is explicitly malicious. Honestly I think the reason threads federates and why meta is interested in doing so is because it further cements them as the best platform. Twitter will continue its decline & they win.
Not really malicious, but also not federation. We already have no reply accounts mirrored here from Twitter, so what's the difference?
@mastodonmigration @fediversenews
True. Not yet. But if I were planning how to do ActivtyPub support at scale, this is a smart way to phase it in. But again, you are correct: untill it is done, it is not done.
One good thing about this. At least... for now... we don't have to worry about our content getting scooped up by Meta and subjected to their terms of service whereby they claim a full license to everything.
@justin I’m very interested in how this comes about and how Meta allows it to happen.
I am hoping it’s just a single sign on to a Mastodon server, but I just don’t see it being that easy.
Really looking forward to it though.