apt_install_coffee

Any SBCs with K3 yet? I've got a K1 but wouldn't mind something with RVA23

My cat will attempt to eat anything he thinks is intended to be food, so I have to wrestle him down. Be glad yours only sniffs.

If you don't trust your psychiatrist, you absolutely should find a different one if you can.

Having said that, from what I can tell the use of Vyvance and Abilify together is relatively common due to comorbitities in what the are typically treating. The combination side effects seem to range from relatively mild, to rare, but I am not a doctor nor do I use Abilify.

If you cannot get another psychiatrist's opinion, perhaps ask your dispensing pharmacist about combination risks, they are the next most likely to know about this.

The line between what is a hack and what is basic performance optimisation is both subject to taste and use-case. Horses for courses, right?

It does, I quite like mimalloc though I prefer to have programs compiled with their custom allocator rather than inserting them via LD_PRELOAD as I've found some issues when using it with programs like Firefox.

Saying musl is preferable if speed is important is a bit...loaded. It's not always untrue, but it often is.

As a libc, musl has a much smaller footprint than glibc, so a computer which is short on memory capacity, memory bandwidth, or cache size could absolutely see a performance benefit. The flipside to this is that a lot of the 'bloat' in glibc are performance tricks including lots of architecture specific code.

As others have mentioned, the malloc implementation is less than ideal and can slow down highly threaded & memory intensive applications.

I work on a musl-based embedded distribution for my day-job, and also quite like using it personally for arm boards and my old ThinkPad. I wouldn't really use it for my workstation though.

As far as applications working with musl, it's not uncommon to see glibc-specific code which would need to be patched out of some applications (systemd comes to mind).

For a tool that is so generic by default, I was surprised at how deeply personal a keyboard really is once you start to realise what you want.

Start with a portable hard drive which only has one job "store a copy of your critical data".

• move the drive as infrequently as possible, especially when it's turned on.
• only ever write to it when you do your periodic backup.
• only plug it in when you need to read from or write to it.

It's a paranoid set of rules, but if this data is critical, this is a good idea. Even better is to have an additional copy of that data in cloud storage.

As far as operating system, you absolutely can use a Linux machine, but learning a new system risks you accidentally deleting data so be careful. Linux has ways of reading windows-formatted hard drives, so as much as I prefer Linux, I would say don't try new things on the machine which hold critical data.

Fair enough, I also would have expected tailscale to set itself as the default route when those options are enabled.

What are your route & dns settings? I don't remember if tailscale forces all DNS queries to go via it's tunnel, but I remember that the mullvad client uses DNS hijacking to make sure the device uses the wireguard tunnel.

In the short (next couple lifetimes) term, the US will continue receding from different geopolitical arenas, followed by some political jostling to change that region's power balance.

As the empire shrinks, the politics of scarcity will become more pervasive, entrenching clientelism and mistrust in an already fairly low-trust society.

It's not a hot take to say that mask-off fascism is on the menu given how fascism-shaped the US is, but given how autocanibalistic this particular right wing wave is, I have no idea what to expect.

Don't know whether the new boss will be the same as the old boss; while India and China don't seem particularly empire-inclined, few countries do until they're the one with the biggest stick. Both have been drumming up nationalism internally for the last decade, so if they can't defuse it safely they'll point it at each other, to everybody's detriment.

I recommend starting with basic operations, like:

• putting installed files in the right directory structure.
• integrity checking.
• archiving and compressing.

Decide whether your package manager is source-based, or if you're going to make some kind of binary distribution mechanism. Either way, you're going to need a process for configuring, compiling and installing packages from source.

I do recommend looking at how Pacman, & apt approach all this. There are also likely books on this topic.

Also recommend playing around with buildroot; not because it is a comprehensive package manager, but because it's inner workings are very transparent.