this post was submitted on 19 Feb 2024
299 points (96.0% liked)
[Outdated, please look at pinned post] Casual Conversation
6616 readers
1 users here now
Share a story, ask a question, or start a conversation about (almost) anything you desire. Maybe you'll make some friends in the process.
RULES
- Be respectful: no harassment, hate speech, bigotry, and/or trolling
- Encourage conversation in your post
- Avoid controversial topics such as politics or societal debates
- Keep it clean and SFW: No illegal content or anything gross and inappropriate
- No solicitation such as ads, promotional content, spam, surveys etc.
- Respect privacy: Donβt ask for or share any personal information
Related discussion-focused communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm less settled on Lemmy, but fully settled in the Threadiverse. Basically I see Lemmy like my current Linux distro: It's good and getting the job done, but I'm always watching the next iteration in the ecosystem.
That said, I feel like I've landed on a good host and alternate frontend that I like. And I LOVE that I can choose my host and frontend.
This is also a really good thing. The only problem I see is that it's a little more complicated if sites would change their backend.
Like, imagine in 10 years Lemmy isn't the hottest threadiverse backend any more and now it's something else. But what about the existing sites? It's infeasible for all users to manually migrate their accounts to other, newer instances and they might not want to either (they might like their current instance).
So given that situation, instances need a migration path to a newer backend. But that seems more complicated than switching a Linux distro for as a single individual.
It's already happening with discuss.online, they're building their own backend. It shouldn't be too hard to migrate but I agree that multiple backend would increase complexity