rather than allowing edits for invisible edits for X minutes, couldn’t your client just delay actually sending it for X minutes allowing to cancel or edit freely until that point?

Gmail allows a similar feature and it seems safer in a distributed system than relying on everyone else to respect what happens after you send a raw message and an edit right after

though laptops are notorious for proprietary charging.

I’ve seen dells that can charge via USBc at full 140w but only on a Dell dock. On any USB PD charger it will only do 60w, and complains about it as it throttles everything.

growing it like a garden is a perfect phrase imo

because on windows or Mac it may have just worked. …until it doesn’t, or leaves your windows scaled wrong or placed on monitors that don’t exist or some other failure condition. at which point you reboot and hope for the best.

when it doesn’t work on Linux I’d check logs, actual configuration, and even the source if I need to.and then I’d hopefully improve things and make it work the way I want it to.

it sounds like you understand the value of using water to clean your butthole after you poop… so why not spend the $30 on a bidet just in case you ever do have a poop and don’t want to shower? or hell just so you don’t use as much TP before hopping in the shower. or for anyone else using your toilet and not wanting to hop in the shower…

even just knowing enough to not consider clothes ruined when a button pops out or a tear forms would be nice

If adopt systems then the question is easy to answer: no, journald does everything you need.

without adopting systemd… well. Are you evaluating going without any log handling at all and maybe just dumping logs ephemerally to tty0? DIYing all log stuff like your init scripts DIY things?

Personally if I had to go without journald I’d probably go back to using syslog-ng. But I guess there’s an argument for shipping straight into something like opentelemetry-collector if you’re willing to put in a lot of work.