798

"the company looked at the history of social media over the past decade and didn’t like what it saw.... existing companies that are only model motivated by profit and just insane user growth, and are willing to tolerate and amplify really toxic content because it looks like engagement... "

you are viewing a single comment's thread
view the rest of the comments
[-] wildginger@lemmy.myserv.one 2 points 1 year ago

They are talking about the people developing lemmy, not some petty fight with the admins of one specific instance.

[-] deus@lemmy.world 9 points 1 year ago

The Lemmy devs have no power over instances they do not run themselves.

[-] wildginger@lemmy.myserv.one -1 points 1 year ago

Other than writing the software that all of those instances use to stay up to date and in contact with each other, regardless of their federation status.

[-] unnecessarygoat@lemmy.world 5 points 1 year ago

can't people just take the lemmy source code and make their own version of the lemmy api?

[-] wildginger@lemmy.myserv.one 2 points 1 year ago

Sure, technically. But good luck getting anyone to use your version over the mass adopted one. And good luck fitting back in if they decide to take their fork in a direction you dont like, which isolates your instance further and further.

[-] ClamDrinker@lemmy.world 1 points 1 year ago

It's because the current version has nothing wrong with it. If the Lemmy devs should choose to sabotage the Lemmy software, you'd be surprised how easily that happens when it pisses off all the instances and their owners. Instances will simply refuse to upgrade. And like most things, eventually some fork will win the race to become the dominant fork and the current Lemmy devs would be essentially disowned. Different forks also doesn't necessarily mean API breaking changes, so different forks would have no issue communicating (at least for a while).

this post was submitted on 04 Nov 2023
798 points (99.3% liked)

Selfhosted

40313 readers
199 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS