Huh, odd. I can't get it to open YouTube links on any of my devices. I guess I'll have to investigate.

Edit: ahh, the play store version doesn't support link handling

Oh I totally recommend Chromebooks, they almost entirely eliminate the tech support burden from having a parent/grandparent who doesn't get computers. It was the dude above me who crapped on them.

It would be really helpful if grayjay could register as a YouTube.com link handler, that's the only thing stopping me from using it most of the time

Oh yeah, I'm not saying you did anything wrong I'm just telling people to protect themselves when they buy their products.

They make nice eink devices, they just have a tendency to implode fairly often so definitely have buyer protection for a couple of years if you're going to spend on one.

There's really nothing you can do to go after them either, I doubt they have enough of a presence in the US to make a small claim worthwhile.

I'd you bought yours with a credit card take a peek at your card agreement and see if you have any coverage for electronics purchases. You might have coverage for 1-2y for phones, tablets, computers, etc and could make a claim through your CC company.

I like the Scandinavian system of fines for breaking the law. They're scaled based on your annual income so a speeding ticket isn't just a fee for the wealthy.

But there's Wikipedia I could be reading -Brain

Chromebooks are amazing for a certain type of low technical skill person. Older parents and grandparents in particular are exactly the kind of people that Chromebooks are for. There's zero technical support burden and if anything goes wrong a power wash solves it.

I'm still waiting for a viable competitor to the Galaxy Tab S line. Literally no one makes a flagship tablet that can compete with Samsung's build quality on those, they're pretty much the only ~11in OLED game in town too.

Their after sale support (both warranty and technical support) is absolutely abysmal. If you need support for one of their products you're best off dumping it "as is" on fleaBay and buying something else to replace it.

They've had screen breakage problems since about 2-3y ago for some reason. My OG Nova Air has survived about half a dozen short drops without any issue but more recent devices are just spontaneously breaking in people's bags or sitting on a counter.

I think they're dealing with some kind of design failure where they haven't accounted for display stresses in the newer thinner screens but they'll never, ever, admit to it. That would open them up to replacement liability and drive them out of business.

If you do buy one of their newer devices I strongly encourage you to buy a 2-3y aftermarket warranty with it otherwise it seems like you have a decent chance of just being shafted at random.

Anything made by Razer, any Google hardware

I'd focus on KDE here, it sounds like the gui auto mount service is barfing for some reason. Does the drive mount normally when you boot to the CLI and try to mount it by hand?

Instructions unclear, dick stuck in card catalog. Send help, preferably a hot librarian.

I do this plus follow competent people in those fields on Mastodon/reddit/etc for current news relevant to practitioners in the field

how though?

mount -o bind /source /target or use fstab or systemd mount units

Can you explain a bit more please?

Container software often needs permission for both the virtual path (wherever the bind mount is mounted to) and the source path (wherever the original is mounted from. It's not terribly complicated but it does mean fiddling with access permissions in flatpaks.

You should read about bind mounts, they're fairly straightforward and there are many, many, many explanations available online

Lots of internet people says that one can't create mount points across different filesystems.

Citation needed. Bind mounts work just fine wherever you put them, again: you need to mount your source filesystem somewhere then you can bind mount paths from that mounted filesystem anywhere in the running VFS tree. You should Google linux bind mounts, they're quite simple.

problems that symlinks do

Can you explain more please?

Some software has problems following symlinks properly and fails to work unless given the symlink source path instead

Compression ratios on plaintext are magical

bind mounts don't usually have the problems that symlinks do. The only time I've had issues involve container systems like docker or flatpak.

For data like this from another filesystem I usually like to mount the entire volume somewhere private (like under /run) and then bind mount the parts I want to use into their desired locations (like /home/foo/Download, etc.)

I do this with a second ext4 drive that I use for performance sensitive storage with my primary btrfs system root. It works well, just be aware of edge cases involving containers (you may have to grant the container access to the original mount location under /run in addition to the bound path. This is definitely a gotcha when working with those paths with flatpak.)

Cute cat snake