this post was submitted on 06 Jul 2023
0 points (NaN% liked)

/kbin meta

2 readers
1 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 2 years ago
 

I would like to know if I can feel safe here, or if I should pack it up and start looking elsewhere sooner rather than later.

If the kbin staff have already made there intentions clear, please let me know.

(page 2) 26 comments
sorted by: hot top controversial new old
[–] Rabbithole@kbin.social 0 points 2 years ago (9 children)

We (meaning the whole fediverse, all instances) need to be de-federating that crap immediately.

Nothing good will come from having Facebook streaming into here in anyway whatsoever.

The Fediverse as a whole needs to be a separate place so that people can leave places like that.

Also, if Facebook is allowed to "work with" the development of the fediverse at all, they absolutely will eventually destroy it for profit. And "working with" it absolutely includes them federating with it.

When their vast resources are taken into account, and their existing userbase also, they would rapidly become the main instance (or collection of, but probably just one) of the whole fediverse. Once that's them, they can use that position to dictate terms pretty hard.

Before you know it, everyone that would eventually have come here are there instead, and they're now the fediverse. They can also fork the software and leverage their Dev teams to make their fediverse vastly more polished... No donations needed on their fediverse, less bugs, everyone you know is already over there... Seem familiar?

How does that effect us who aren't there, how isn't it just the same thing as now? Our fediverse dies off because the users leave, instances close down through lack of population/need, before you know it there's nobody here and the idea just dies.

Literally been done before. The playbook is absolutely common knowledge: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

load more comments (9 replies)
[–] wagesj45@kbin.social 0 points 2 years ago (2 children)

If you're truly worried about federating with Meta, you should probably also avoid all the other products they have their fingers in.

This includes all their web properties:

  • Instagram
  • WhatsApp
  • Onavo
  • Oculus VR
  • Beat Games
  • Kustomer
  • Lofelt

But this also includes many web technologies that are ubiquitous around the web. Meta has either created or contributes code and resources to:

  • React.js
  • MySql
  • Memcached
  • HHVM
  • Cassandra
  • Scribe
  • Hadoop
  • Hive
  • Apache Thrift
  • Varnish

I suspect you'll have a hard time finding any website on earth that doesn't use at least one of these technologies.

[–] livus@kbin.social 0 points 2 years ago (3 children)

Sorry if tbis is dumb of me but why should we avoid ever using any web tech that has been associated with Meta, just because we are worried about E-E-E affecting Activity Pub?

load more comments (3 replies)
load more comments (1 replies)
[–] sparseMatrix@kbin.social 0 points 2 years ago (1 children)

@Roundcat

Meta is facebook who engaged Cambridge Analytica to purchase our lives.

Not from us, but from them. Facebook literally sold out the world

Facebook nearly destroyed this country for a buck.

Fuck facebook. I don't want to avoid federating because I dont want them around; I want to avoid federating because anything I can do to starve them of every resource for growth that I possibly can is the best thing I can do about facebook.

load more comments (1 replies)
load more comments
view more: ‹ prev next ›