19

Threads seems to be beginning to test ActivityPub federation, and since Kbin can be used for microblogging, this affects kbin.social. What are your thoughts on federating or defederating with them?

top 50 comments
sorted by: hot top controversial new old
[-] snooggums@kbin.social 27 points 9 months ago

I would prefer not to federated with threads and will block if kbin federated. If I wanted Facebook content I would use Facebook.

load more comments (2 replies)
[-] livus@kbin.social 25 points 9 months ago

I'm strongly against it because of Embrace Extend Extinguish.

I'd encourage everyone to read How To Kill A Decentralized Network like the Fediverse if you haven't already.

I think Meta's history reveals it to be a bad actor and I don't think their intentions here are above board.

[-] CoffeeAddict@kbin.social 7 points 9 months ago

Microsoft put that theory in practice with the release of Windows 2000 which offered support for the Kerberos security protocol. But that protocol was extended. The specifications of those extensions could be freely downloaded but required to accept a license which forbid you to implement those extensions. As soon as you clicked "OK", you could not work on any open source version of Kerberos. The goal was explicitly to kill any competing networking project such as Samba.

This is a great article describing exactly how Meta can control the fediverse and destroy smaller instances with anti-competitve practices.

[-] CoffeeAddict@kbin.social 17 points 9 months ago* (last edited 9 months ago)

My main concern is that this is just ~~Facebook~~ Meta utilizing the “Embrace, Extend, Extinguish” strategy that Microsoft used against Netscape in the 90s.

I feel like our small communities here - which are just getting started - are going to be flooded by Threads users who don’t even know what federation is and then all the content, power & control will realistically be in Meta’s hands.

My gut says that is probably Meta’s goal, but what do I know? I’m just some internet person.

[-] atocci@kbin.social 4 points 9 months ago

How would power be handed to Meta just because Threads has more users? The communities are under the control of the instances where they were created, and Threads users couldn't create larger communities to replace them either since it's only a microblogging platform.

[-] CoffeeAddict@kbin.social 5 points 9 months ago

The concept is that overtime, communities and connections will organically grow. If Threads has a disproportionally large ubserbase, then overtime they will create a similarly larger number of communities. This then would give them a lot more influence over the fediverse and anyone federated with them.

For smaller instances that become accustomed to seeing those communities and content, the danger is that Meta can just “pull the plug,” defederate, and extinguish the competition, or at the very least hurt their competitor's users experiences when interacting with content from Threads. The reason they might do this is purely because it fits into their business model which is selling user data to advertisers; it is in Meta’s interest to have as much data on their users as possible, and to have those users be based on Meta’s platform.

As I said in another comment, I could be totally wrong and this could benefit the fediverse. I just think the opposite is more likely because I do not trust Meta. I think they will play nice in the beginning, but then start to flex their muscles once they feel they’ve got enough influence.

Also, there is nothing stopping them from expanding Thread’s capabilities to include the threadiverse. Kbin has already demonstrated both are possible in one app.

[-] atocci@kbin.social 4 points 9 months ago

If they pull the plug on ActivityPub and take their users back, things would just be exactly how they are now. Since they can't create communities or magazines like we can (and it's very unlikely Meta is going to try to implement this), if they want to participate in discussion here, they'll be posting in our communities. Kbin's magazines are uniquely suited to this as well because content gets sorted into them based on hashtags, so they wouldn't even need to know that they're posting to a magazine to do it.

We're already in a situation like you describe though with lemmy.world's near monopoly on large communities, which seems concerning to me as is.

[-] CoffeeAddict@kbin.social 6 points 9 months ago

I hope you’re right.

And I agree, lemmy.world does have a near-monopoly on large communities. I attribute that to lemmy being more developed and having apps ready and kbin simply not being completely ready in June (no shade thrown at ernest - he’s great and I like kbin better.) I hope overtime kbin grows some of its own large communities so it’s not so skewed towards a single instance.

[-] atocci@kbin.social 5 points 9 months ago

Just to clarify what I mean, lemmy.world's position is bad for the threadiverse as a whole. It's where most of our users and largest communities we all post to are. If .world goes down, it'd be a major blow to our current, mostly stable, position and we'd be significantly worse off than if Meta were to come and go. Things are improving though and communities are slowly spreading to other instances! I also deeply appreciate that we have kbin as an alternative to Lemmy - thank you Ernest

[-] FaceDeer@kbin.social 4 points 9 months ago

Threads, despite its name, is not a threaded discussion forum like the Threadiverse. It's more like Mastodon, a microblogging protocol. I don't think we'll be seeing Threads users flooding here because the format of these communities isn't really compatible with that.

load more comments (2 replies)
[-] Froyn@kbin.social 16 points 9 months ago

Raise your hand if you think it would be okay for Meta to put your kBin/Lemmy content along side THEIR ads for revenue.

[-] CoffeeAddict@kbin.social 17 points 9 months ago

I mean fuck, how many of us left Reddit for their bullshit? Inviting Meta into the mix is an even worse proposition.

[-] FaceDeer@kbin.social 14 points 9 months ago

This is nothing like what I left Reddit over.

Nobody is "inviting" Meta in, ActivityPub is an open protocol. They can come in without any invitation. Being closed is what I left Reddit over. Closing the Fediverse to Meta would be more like the bullshit I left Reddit over.

load more comments (1 replies)
[-] sour@kbin.social 9 points 9 months ago* (last edited 9 months ago)

why do people support federation with big company that has bad track record

[-] FaceDeer@kbin.social 8 points 9 months ago

Sure. How does it harm me if they do that? I won't even see it.

[-] Froyn@kbin.social 4 points 9 months ago

Ah the ole "Why should I care?"

You're right, you won't see it. After federation (when the bandwidth bill comes due) and kbin is shut down due to costs, will you care then?

[-] FaceDeer@kbin.social 9 points 9 months ago

If kbin.social can't handle the bandwidth of federating with Meta then it will defederate. But I don't run kbin.social, that's up to the people who run it. The question is "how do we feel about federating?" As in we the users.

And that's who I'm responding to here. A user who was concerned about the content that they posted being seen on Meta's servers. They're not worried about bandwidth costs, they're just worried about some kind of bad magic happening when Meta users see their posts in the context of Meta's instance.

[-] atocci@kbin.social 6 points 9 months ago

I would be... Anything I put on here, I know kbin.social will be sending out to thousands of other instances, and what those instances do with my content and how it's displayed is completely out of my control. That's just the nature of ActivityPub, and by posting here I think I have to be okay with that. There are already ActivityPub services that run ads, so it's not unique to Threads either.

[-] Chozo@kbin.social 6 points 9 months ago

I mean, any Fediverse instance can already do this. Some already do. Nobody seems to have a problem with their content MissKey.io's ads right now.

load more comments (3 replies)
[-] Sabata11792@kbin.social 13 points 9 months ago

I don't trust meta to not intentionally kill us off, drown us out, or start trying to imposing their rules.

load more comments (2 replies)
[-] Xariphon@kbin.social 11 points 9 months ago

Fuck that. Keep the corporate enshittification of fediverse as far off as possible.

[-] Telorand@kbin.social 10 points 9 months ago

No. Fuck Facebook, and fuck Zuck. There isn't a world in which they would federate and respect our privacy.

See how they build internal user profiles for users not on Facebook through tags and other metadata scraping techniques. If people you know talk about you on Facebook, there's a shadow profile about you out there, waiting to connect with you in real time. I have no reason to think they wouldn't do the same kind of shit here.

load more comments (2 replies)
[-] FaceDeer@kbin.social 6 points 9 months ago

I'm baffled by the trend in recent years of everyone insisting that they need to be in control of every byte of data that they deliberately publish onto the open medium of the Internet.

I mean, I'm not really baffled. I understand that people see that their data might be worth pennies and they want those pennies to be their pennies, darnit. I mean I'm dismayed by it.

If Meta's going to be supporting ActivityPub, then yay, IMO. If you don't want Meta's servers to see your data then stop posting it on an open protocol whose purpose is to show it to Meta's servers.

[-] CoffeeAddict@kbin.social 5 points 9 months ago

Look, I understand your opinion and I respect it, but I simply do not trust Meta. They are a business, and they are always going to do what is best for their business. Of course, there is nothing inherently wrong with that - all businesses are in the business of staying in business - but I think their track record makes them an untrustworthy actor in regards to the fediverse; they're a big tech company joining a small (and I would argue obscure) ensemble of social networks.

Of course, I could be totally wrong and this could be a total boon for Activity Pub, kbin, mastodon, and the wider fediverse. I just think that the opposite is more likely.

load more comments (9 replies)
load more comments (1 replies)
[-] gnuplusmatt@reddthat.com 6 points 9 months ago* (last edited 9 months ago)
  • They should pay the hosting costs of any server they pull data from
  • not run ads against the content that comes from other instances
  • Any changes they want in activity pub should be in the form of an MR on activitypub itself, and they must respect the protocol maintainers of the project if their MR is rejected. If they implement AP features outside of spec, they should be summarily defederated. We do not need another Jabber/XMPP vs Google situation
  • Any instance is free to federate/defederate with threads
[-] atocci@kbin.social 5 points 9 months ago* (last edited 9 months ago)

That's not really how ActivityPub works though, there's no pulling. They wouldn't be accessing kbin and downloading it's data, it's a push system. We would be pushing copies of our data out to Threads like we do now with all the other ActivityPub services. Threads would then distribute that data to it's users with no extra work on kbin's part. It would just be one more instance in addition to the thousands of instances already out there.

People bring up the XMPP Google situation a lot also, but I think it's a bad analogy for this. Google's adoption of XMPP brought people into the protocol and Google abandoning it took those same people away. Those who were using it before Google could still use it after Google. Anybody who left XMPP to follow Google did it because XMPP failed to adapt to the features people wanted. Thats why we have Matrix now instead.

[-] Froyn@kbin.social 4 points 9 months ago

Wow, had not even thought of that.
RIP to any server that federates with them and has to pay for the bandwidth they're going to need to service Meta's users.

[-] Osa-Eris-Xero512@kbin.social 5 points 9 months ago

No to preemptive defederation. They get defederated if they prove to be too problematic, same as any other instance.

load more comments (1 replies)
[-] BeAware@social.beaware.live 5 points 9 months ago

@ThatOneKirbyMain2568 from someone on Mastodon, I don't see an issue with it.

The only data they get is public facing data (public profile info and post contents). The only place your IP or email address is stored, is on the server you're logged into or the site you're on.

Though others might have some other reservations, that was my biggest concern.

[-] jeena@jemmy.jeena.net 5 points 9 months ago

I already preemptivelly defederated from them a long time ago.

[-] FlihpFlorp@lemm.ee 4 points 9 months ago

Hey lemmy user here

Does kbin have user level defederation or something

[-] CoffeeAddict@kbin.social 4 points 9 months ago

I am not super familiar with it, but my understanding is that Kbin lets users block something by domain.

So, my understanding is that yes individual users could theoretically block Threads content.

If I am wrong, somebody please correct me!

[-] livus@kbin.social 3 points 9 months ago* (last edited 9 months ago)

We have user level domain blocking, so if you block an instance it's a bit like defederation.

Afaik you can still sometimes see their users on other instances but you don't see any of the blocked instance's own content anywhere.

[-] jeena@jemmy.jeena.net 3 points 9 months ago

I don't think so, only if you spin up your own instance. I myself have my own instance of Mastodon where I defederated Threads.

load more comments (2 replies)
[-] sour@kbin.social 5 points 9 months ago* (last edited 9 months ago)

no ._.

fediverse will lose identity

[-] Anticorp@lemmy.ml 4 points 9 months ago

We feel poorly about it.

[-] atocci@kbin.social 4 points 9 months ago

I honestly want it. I want to follow people who have Threads accounts without needing a Threads account myself. I want more people in the fediverse and I don't care what platform they're using to access it because I'll be on kbin.

If Meta one day decides to leave ActivityPub, that's fine with me because I'll still be here on kbin with all the same people who are here now who also would never use Threads.

[-] SamXavia@kbin.run 4 points 9 months ago

I think it's a possible change, It will bring a lot of newer people that rather haven't researched or want to move away from 'main stream' platforms to be able to come to the Fediverse and could be really possible for the amount of people being able to interact in general across both platforms.

It would also allow me to move away from Threads and stick to one account for most of the Fediverse based Social Media usage, and I really hope other Social Media's follow in METAs steps.

[-] artisanrox@kbin.social 3 points 9 months ago

Meta is horrible. Betcha it gets slapped with massive defedding in no time flat.

load more comments (1 replies)
[-] hyperspace@kbin.social 3 points 9 months ago

Did we not learn anything from Google and XMPP?

load more comments (2 replies)
[-] HeartyBeast@kbin.social 3 points 9 months ago

The Fediverse is an experiment and should/needs to be robust enough to cope with large commercial instances. I’m happy to see how this goes before blocking if it goes badly

[-] Machinist3359@kbin.social 3 points 9 months ago

They'll boil the frog slowly enough. Threads is huge compared to the fediverse, and will likely do piecemeal federation. Like sending account activity out but not sharing any fediverse voices, getting everyone here following and desensitized

[-] HeartyBeast@kbin.social 3 points 9 months ago

They may. We’ll see. But us running around with our hair on fire before we see what actually happens feels a bit off

[-] Pamasich@kbin.social 3 points 9 months ago

I really don't see the issue. So more users is bad? I thought our issue is the lack of users currently.

I've seen people complain about ads and data harvesting here. But instances can already do that. Meta joining would change nothing about that. Actually, being a proper legal company, it might be easier to sue them over misusing your data than random instances.

"Embrace. Extend. Extinguish"? Let's stop between the last two steps then, not before the first one.

Kbin would be crippled by the amount of Threads content? I thought federation only happened if one kbin.social user is following a user on Threads? Should be as easily manageable then as Mastodon is currently. Or am I misunderstanding how this works?

To me, big sites federating looks like a clear advantage. I don't really get the big problem.

load more comments (2 replies)
load more comments
view more: next ›
this post was submitted on 13 Dec 2023
19 points (100.0% liked)

Moving to: m/AskMbin!

2 readers
5 users here now

### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**

founded 1 year ago