Gregory's Server@Mastodon Thanks. This post is a little confusing though because you discuss Mastodon users following Threads users but then say Threads and Mastodon are not interoperable? So I guess I don't understand if I can follow Threads users or if they can follow me.
|
37 comments
@brianvastag @Mastodon Not on launch. They intend to federate, but right at this moment Threads is not in the fediverse. 'We expect that eventually Mastodon and Threads will be interoperable' @brianvastag For now, Threads is not part of the fediverse - that is, Threads users are restricted to their own instance, that belongs to Meta. In the future, Threads intends to be part of the fediverse, and then Mastodon instances will be interoperable with Threads. Of course, there are still many questions about this that cannot be answered at the moment.  @Mastodon @riomccloud @brianvastag That's certainly how it seems. One of the many questions is how content rights issues will be addressed. Eugen: "Even if you follow or send a message to a Threads user from your Mastodon account, Threads will not be able to collect any of your private information EXCEPT THE MESSAGE YOU SENT." [emphasis added] The "message you sent" is shared with only very limited data rights and is not subject to uses (monetization, profiling, etc.) Meta users agree to. See even boosts could be used to build ad platforms. There’s no way they don’t see that as exploitable value. @spaduf @jdp23 @riomccloud @brianvastag @Mastodon Boosts could send your content to Meta servers, however what is not clear is how the data rights issues will be addressed. By default on Mastodon you own the content rights and you do not give away the right to exploit your content for these purposes. I think we’re already in some legal grey area with the concept of boosts and likes being protected. IANAL but I think it’d definitely kick around the courts for a while before we’d know for sure. @spaduf @jdp23 @riomccloud @brianvastag @Mastodon The issue is copyright to content. An analogy is book publishing. You do not give someone the right to make copies of your book and sell them when you publish your book. Same on Mastodon. Meta users do explicitly give Meta a license to their content for various purposes through Meta's Term of Service. But the argument I think that they’ll make is that boosts are not content and therefore not subject to the same protections. Not to mention they’ll only have to make the argument once caught. @spaduf @jdp23 @riomccloud @brianvastag @Mastodon It would be the underlying content that the owner retains the copyright to. Boosting is part of the service so it is an authorized use of the content. The Privacy Policy describes the service so there is a limited implied license to any such use of the content. @spaduf @jdp23 @riomccloud @brianvastag @Mastodon You seem to be doing fine. These are all valid issues.  Even if the owner retains the copyright (which they probably do, although IANAL) Meta can use it for a wide variety of purposes without violating copyright. And they have hundreds of lawyers and budget for paying billions of dollars in fines, so even if they theoretically *can't* use it, they still will if they think it's worth it. @mastodonmigration @spaduf @riomccloud @brianvastag @Mastodon @jdp23 @spaduf @riomccloud @brianvastag @Mastodon Indeed. Under no illusions about the effectiveness of any defensive measures. Never-the-less it is better to take what measures one can. Providing notice is one such measure. @mastodonmigration Thank you! I just added it to the draft privacy threat modeling post at https://privacy.thenexus.today/fediverse-threat-modeling-privacy-and-meta/ @jdp23 @spaduf @riomccloud @brianvastag Thank you. You might also want to link this Meta Specific Data Rights Limitation Notice: https://mastodon.online/@mastodonmigration/110663189973042587 It seems like a good time to provide notice that we do not consent to use of our content beyond those uses afforded by the Mastodon instance Privacy Policy. @mastodonmigration @jdp23 @riomccloud @brianvastag Had already boosted and favorited :blobcat_mlem:  > "until they are made to" That's Facebook way, alright. 🤔 🤭 For them, there are quite a lot of checkboxes to untick on app permissions: https://tilvids.com/w/3Fq67yoxjsi9mnSKG2Xbam @mastodonmigration @riomccloud @brianvastag @Mastodon Yep, they get your communications and keep them forever to sell.  @mastodonmigration @riomccloud @brianvastag @Mastodon and all the associated metadata. @brianvastag @Mastodon at the time of posting they’re not interoperable. but threads claims that they will add this functionality later on. @brianvastag @Mastodon I believe Meta is planning to make Threads interoperable with Mastodon at some point, but for now there's no connection between the two :) @phonyphanty @brianvastag @Mastodon They'll make that happen right after they figure out how to harvest Mastadon user data. @JJ_Allen @brianvastag @Mastodon To be fair, that's something that anyone on Mastodon can easily do, scraping a whole network's posts can be done in a few API calls. But for sure, I don't want Meta to have more of my data either. I wonder if it's legal for them to use the data of users from other Mastodon servers? @phonyphanty @JJ_Allen @brianvastag @Mastodon If it were legal for corpos to do advertisement schemes with scraped data, they wouldn't even bother building websites to collect data. We are the product after all. @JJ_Allen @phonyphanty @brianvastag @Mastodon this is the big worry. I would hope that never happens. @JJ_Allen what data are you worried about? the public posts you're sending out into the world or something else? @brianvastag Threads has not turned on federation yet, so currently neither are interoperable with eachother. Once they turn it on, then both will work with eachother like any other ActivityPub server @brianvastag @Mastodon They plan on eventually being interoperable, but they’re not integrating with Activity Pub to start. So right now, users on Threads can’t follow Mastodon users, for example. @brianvastag @brianvastag @Mastodon Threads doesn't support ActivityPub on release so it is not currently interoperable although it likely will be in the future. @brianvastag @Mastodon I believe the goal for Threads is that it will be interoperable with Mastodon or other application that utilize the fedi verse, but as of now, Threads is isolated to only users on Threads. |
@brianvastag @Mastodon At the moment threads is completely isolated but meta intends that in the near future threads and mastodon users will be able to interact.