A couple of months ago our company decided to standardise on only one GNU/Linux distro and they chose PopOS. While the default desktop is better then stocj GNOME it was still far away to what I am used from the powerful, featureful and customizable KDE Plasma so after about two weeks I switched to KDE Plasma (unfortunately they have an extremely old version in their repos, but still much better).
I can only guess that Cosmic will be on pair to their current improved GNOME but will still be way lacking compared to what even an old KDE Plasma offers. And I would also much more like to see if they put more attention to keeping more updated KDE Plasma and KDE software packages in their repo. Even for Cosmic I think they would be much better of basing it on the extremely flexible and configurable KDE Plasma base and make it a heavy modification of this.
You don’t need to move ftom lemmy.ml. You’re a group of self hosted gurus, so this is your chance to actually self host. Don’t hide behind excuses that lemmy.ml won’t be able to handle things. Just do what you do best and host your own instance. Sounds bloody fantastic to me!
What is the plan to make communities between instances easily accessible? I feel like with mastodon and now lemmy that is the part that concerns me, namely community reach/discoverability
External communities are just searchable, subscribable and browsable from here. Sometimes you need to change a search filter or default view from Local to All. Or is there something else you feel is missing? I think 90% of the issues people are having are UX related and not a core issue with federation or decentralization.
I think my concern for adoptability is that a technology community could exist with the same name on lemmy.world as well as on another instance. I think theirs some benefit to creating a user and community pool of names and communities to allow genuine growth. it would also prevent fakes and phishing.
I think of it like [email protected] instead of just selfhosted. Sure there may be duplicate communities on different instances but over time I think there will be more people gravitating to a particular community and people will just sub there from then on and the others will become more dormant. When I refer to a community I’ll just use the full name ([email protected]) and not just the community name (selfhosted)
I like the concept
But it feels very much like its been designed by nerdy developers and has had little to no-input on user friendly design.
The federated idea can work but it needs to be more seemless than this.
Communities with the same name should be merged when viewing it from any instance, so you can see all the posts from these communities, they can be moderated seperatley and for advanced users you should be able to select which communities make up the merged community.
By default you should see all of the merged communities in a central place and be able to subscribe to them easily, at the moment its handled different per instance but you have to seek out these communities to subscribe or follow them.
I strongly believe there should be a centralised log-in system, so you can log into any instance with an account from another instance, this means if your instance goes down your account is centralised and is safe.
Regarding point three: I want to be able to migrate my profile to another instance if my current instance has performance issues or admins going rogue.
kbin.life
Top