this post was submitted on 05 Jun 2023
309 points (100.0% liked)
Technology
37712 readers
183 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Problem: millions of redditors currently use third-party Reddit apps. Abruptly sending millions of people to the Lemmy instance you just deployed is a sure-fire way to break it, and maybe bring down the whole federated network of Lemmy instances. Lemmy currently has issues scaling above a few hundred users, as Beehaw has recently discovered, let alone millions.
Problem: Lemmy is a completely different protocol, and there's less than a month left before all third-party Reddit apps become useless and everyone uninstalls them. That's an exceedingly tight timetable and an exceedingly unforgiving deadline.
That said, it's now or never; death or glory. We're not going to get another chance to bring over that many people to Lemmy all at once.
@argv_minus_one Is that scaling problem a software issue, or a hosting issue? There are other Fediverse platforms like Akkoma that use Elixir, so maybe they'd fair better? Could also pick several federated instances to distribute users to.
Lemmy is written in async Rust. The language isn't going to create a scaling problem. Well-written async Rust applications have handled vastly heavier workloads than Lemmy without a hitch.
There are, however, some serious performance bottlenecks that need to be dealt with, and it remains to be seen whether any more bottlenecks remain undiscovered in either the protocol or the implementation. To be honest, as someone working on a Rust+Postgres application myself, this is the sort of thing that keeps me up at night.
Hosting can of course be an issue as well. I'm under the impression that Beehaw had to go up several tiers in its hosting plan in the last few days in response to the surge in demand. I assume this was done to work around the aforementioned bottlenecks by simply throwing more hardware at the problem, but I don't know.
@argv_minus_one I see. The more I look into it, the more I think Lemmy should still be considered beta software like kbin, TBH. Some important features are still missing and the optimization is lacking.
Yep. It works 🥳 and has all the basic features you'd expect of a Reddit replacement 🥳 but will no doubt have the same growing pains as early Reddit did.
@argv_minus_one I still remember when Reddit was 503ing on the regular.
Wasn't that just last week?
I wasn't able to load threads or comments in RiF not a few hours ago.
I still get that stupid “You broke Reddit!” screen all the time.
I do consider Lemmy to be beta software.
But it's currently the best option.
@ericjmorey You ever look at kbin? It already has the follow user functionality implemented so you can get content from the rest of the Fediverse.
My biggest concern with kbin is its in alpha, very little time in use to smooth things out, there's more likely to be major changes to its functionality, possibly breaking changes. I'm olso not too interested in following individuals outside of my Mastodon account.
@ericjmorey That sounds like the situation with Lemmy, but with less features.
I'm not sure I'm understanding. Lemmy is different in the way I described. What features (other than following individuals) are you talking about?
@ericjmorey What I'm suggesting is that
"My biggest concern with kbin is its in alpha, very little time in use to smooth things out, there's more likely to be major changes to its functionality, possibly breaking changes."
is also something that applies to Lemmy, so I'm not sure why you'd knock one platform for it but not the other.
And even if you're not particularly interested in following non-Lemmy users, others are and it would resolve an interop asymmetry that has formed due to lacking this functionality. Like, the only reason we can have this conversation in the first place is because Mastodon supports following Lemmy users and communities and allows me to interact with them, but it's not currently possible to follow non-Lemmy users on Lemmy, which makes the interop very one-sided and cuts you guys off from a large chunk of content (unless you make accounts on other platforms, but Fediverse platforms shouldn't require that just to subscribe to public content feeds, as the interop is one of the Fediverse's biggest selling points over silo'd corporate social media).
Time and scale of use of Lemmy is much greater, therefor more problems have been identified and fixed. It's possible that kbin devs are smarter of better or have been able to benefit from observing the experiences of Lemmy devs, but non of those are safe assumptions without specific knowledge.
It's also possible that the kbin design is simply a better one for any number of reasons. But we won't know that until is gets much more use by many more people. Lemmy has that "advantage" now, thus the safer bet is on Lemmy.
It seems like the Lemmy devs are not interested in creating the feature of following individuals. Unless someone forks the project to add it, anyone who wants that feature should give kbin a try. I'm not one of them.