I’ve always heard them referred to as starfish

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

Ah, I was hoping for something native as I access it from multiple devices. Thanks though, I’ll check it out!

What theme is that? I’ve tried a few but they never look that good.

You could run Firefox in a container attached to the VPN for browsing. You could then connect to it from your workstation over your LAN.

I tried that once. They never watched the show and didn’t give back the USB. 🙁

I did just order one to replace my MacBook, so I’m interested in hearing from others as well. The upgradability was a big plus for me beyond being able to have a mobile Linux machine for dev work.

Plants and animals don’t file tickets.

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.

Each service is a separate docker-compose.yml, but they are more-or-less the same as the example configs provided by each service. I did it this way as opposed to a single file to make it easier to add/remove services following this pattern.

I do have a higher quality version of the diagram, but had to downsize it a lot to get pictrs to accept it…