this post was submitted on 29 Jun 2023
56 points (100.0% liked)

Fediverse

287 readers
1 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago
 

The next 2 weeks...any predictions/bets on what it will be then?

you are viewing a single comment's thread
view the rest of the comments
[–] wrath-sedan@kbin.social 8 points 1 year ago (2 children)

Pretty fascinating to see that at this point they both have approximately 50k active users. Also that kbin’s growth is almost entirely in kbin.social while lemmy is concentrated in lemmy.world but has dozens of other instances as well. Do you think that will lead to structural/content differences at some point? Very cool to see and I love the community between the two!

[–] Maestro@kbin.social 9 points 1 year ago* (last edited 1 year ago)

I think that a large part of that is because a lot of Lemmy servers were overloaded so people spun up new instances. Kbin on the other hand remained available for signups. It's why I'm at kbin. I couldn't register at any Lemmy instance and I didn't want to run my own.

[–] static@kbin.social 1 points 1 year ago (2 children)

kbin's number is too high, it counts all users.

lemmy's number is too low, you have to post to be active.

[–] LollerCorleone@kbin.social 5 points 1 year ago

The stats page counts all users, but the nodeinfo page displays data on active users. Fedidb takes data from the nodeinfo page for each kbin instance it tracks.

[–] taanegl 1 points 1 year ago

This is it. I believe that in the coming months Lemmy and Kbin will be forcibly modernized. Like there's an obvious issue with scalability and optimizing network communication. As such we'll see instability for a little while more, until the kinks have been worked out.

Massive respect to the Lemmy and Kbin Devs for weathering the storm. I know it'll take some time, but I'll suffer the growing pains - rather than suffer u/spez and his vendor lock-in platform.