I have been working on a Wayland Tiling WM and have thought about expanding more into the DE space. While it’s finally starting to get to a good spot, it’s pretty daunting to consider all of the other items that need to be developed for a fully-featured DE. Especially when it’s something I’m doing as a side project after my day job. I think for anything bigger it’d require financial backing, for which open source projects are still struggling to find a good solution.
What might be interesting would be to have it displayed, but grouped by instance. That way we could see some data and potentially uncover troll instances or attempts to brigade the conversation without opening ourselves up to personal attacks.
Wow, no need to make this personal. /s
Yeah, lack of XWayland support has been an issue for me. Versioning the config API is something I’ve been considering, or at least ensuring backwards compatibility.
I’d be interested in other ideas or pain points you’ve experienced. Not to suggest I’ll ever have something production-grade, but my hope is to get to a point that I have a working daily driver and potentially share it with others.
There’s also Strata, Niri, and to some extent Cosmic. My problem has been that they tend to be very opinionated and limited in the customization of the layouts. Having used XMonad for a long time, I may be a bit spoiled in that regard…
I do think there’s a middle ground for configuration without requiring programming skills, which can be off-putting for many users. After all, most layouts are just a combination of rows and columns. 😛
I actually started working on one a few weeks ago. It’s amazing how easy it was to get the basics working. Still a long way to go, but it’s a fun project in the meantime and hopefully can result in something that supports my desired flow.
In a similar vein, I’ve seen a lot of auto moderator implementations created. If instead of creating yet another project, people started contributing to existing ones we’d have a good core set of functionality that could be shared across instances. Competing implementations are fine, but at some point the efforts get spread so thin that progress is limited.
Sorry about that, there were some upload restrictions. See the HQ link for the full resolution.
Honestly, I can’t really tell the difference between Jellyseer and Reiverr. It may be that I don’t use them enough, but it really seems like they provide the same information in slightly different ways.
I started with Jellyseer and later learned about Reiverr. Haven’t settled on which one I like more yet. They both provide basically the same information but in different ways.
Nothing lately, but it seems to come in waves. Something weird that has started in the last couple months is where I’ll get two numbers calling me simultaneously. Sometimes it’ll happen 2-3 times in a row before stopping and never leaving a message.
From what I understand, this is an issue with using different timestamp formats between implementations. In this case, it’s with kbin and Lemmy.
I think the concerns about smaller instances are valid (as I post from lemmus.org). Some additional data points to consider when evaluating an instance would be whether they’re running a recent version and the uptime of the instance.
It’d probably be a good idea to have a page that promotes these smaller instances that ‘score’ well to help distribute some of the load.
A stuffed animal?