It’s not permanent. At least it wasn’t for me.

Ripping youtube or ytm will cause them to ratelimit your ip and/or account (media not available error).

For me, access was restored after 48h.

It was really inconvenient, so I found other ways. A mix of buying whats available on bandcamp, and ripping qobuz using a trial account (which btw is so much faster, ytm was taking days to rip just a couple artists).

I use Symfonium with Jellyfin for music now, if you tag everything with Picard, the “smart” playlist capabilities are competent.

Still pop into ytm to discover new stuff, tho.

My current setup is a universal mount with a Fenix E35, just your typical (expensive high-performance) cylindrical flashlight. I keep it dim, but it gets ridiculously bright if I do need something to see by.

For the rear I use a Fenix LD15R. It’s a little clip-on light that I put on my backback. It’s perfect because it’s wearable and can shine red, not just white.

Before this, I was really happy with a set of lights from knog. Two wearable knog plus lights, to be specific. I used to clip them on my person instead of onto the bike, that way I never worried about mounting or forgetting them on the bike to be stolen. They do also come with a magnetic mount that you can rubber-band onto your bike, helmet, or whatever else the clip wouldn’t work for.

Knogs “gimmick” on a lot of their lights is built-in usb A contacts. The lights can be charged by plugging them in like usb drives into any usb port or charger.

For “be seen” lights knog has great options, and while there are cheaper lights, my knog lights lasted. They kept working for years of daily use, and I didn’t replace them because they didn’t work. Only because I didn’t want to keep charging them every two days with how much cycling I was doing.

Since they’re capable of high brightness, the Fenix lights last weeks at dim “be seen” brightness.

Edit: OH! And if you didn’t think of it yet, the most cost-effective visibility upgrade might be retro-reflectors. I got a roll of reflective vinyl tape for 10 euros at a local bike store, and put some tasteful strips of it on my frame and rims. Even the tiniest amount of light makes them glow. Most of all, they make it extremely obvious what I am and where I’m going.

That’d be like paying for internet service being used to screw you.

A usenet account is not in itself proof of anything.

Op didn’t install anything on their system yet.

It sounds like maybe the usb drive is a bit crappy.

I’ve had trouble with cheap ones crapping out partway through being used, but be fine once you re-write the files to them. Twice now, yours worked, but then stopped working suddenly for seemingly no reason.

The drive might also be getting too hot. That happens with the Kingston DataTraveler drives I have. If I try to read or write continuously for too long, they shut down for thermal protection, and I have to let them sit for a bit before they work again.

Did you try re-doing that?

The EFI partition is something that exists on the storage device being booted, so if something is wrong with that, then the problem is something on the USB.

Since windows still works, the EFI partition on your computer must be fine.

You can also give Ventoy a go. It replaces the need for Balena Etcher/Rufus.

After you install Ventoy on the usb, it will continue to work like a normal usb drive. Now you just put the .iso file you want on the usb. Or multiple at a time, even. And you can continue using it as a usb drive without removing Ventoy or the isos. It wont care if there are other files on it.

When you go to boot from it, Ventoy will show you a menu of the isos on the usb, and let you pick one to boot. Makes it really easy to try a bunch of different distros if you want.

And it works with windows isos, too.

Did you install anything yet?

It sound like you set up the installer usb, tried it, then went into windows to free up disk space, and now the usb no longer boots?

If I got that right, tell us more about the usb drive you used, and the software you used to make it bootable.

It was probably said as a joke at some point, and just became normal.

The same way I’ve started using irradiate. It’s technically accurate, but normally a word used in much more concerning context.

Hence, funny :D

I’ve also used “nuke” but recently “irradiate” has been funnier.

Yeah… I’m not gonna be asking the stuff I already found answers to via an internet search.

Yes.

Just do yay timeshift, then install all three packages that show up.

Timeshift itself is one, autosnap is a second, and the third is a systemd timer that handles the scheduled snaps (monthly, weekly, etc).

Oh, for sure. If you wait a month, the bigger update can be a lot more trouble.

But look at it like this. If a rolling distro has a problem once a week, which is fixed within 24 hours, updating daily guarantees you will run into it.

While updating weekly means your chance is only one in seven. Since because by the time you update, the fix is more likely to already be in the repos, so you’ll be jumping over the problematic update.

The functionality is conceptually identical, yes.

And timeshift is by default set up such that only / is rolled back while /home is kept as-is.

So same as atomic distros, rolling back doesn’t mean going back in time in terms of personal files or settings.

So I’m really only missing out on the updates for something like Bazzite being potentially more reliable.

I’ve been on endeavour+plasma over a year now.

I share your desire for a system that always, 100%, every time, is there and ready to be used.

At the same time, I really like arch and the convenience of the AUR.

Hence, I boot-strap reliability onto my system through btrfs snapshots.

The setup is extremely simple, (provided your install is grub+btrfs) just install timeshift + the auto-snap systemd services. Configure it, and forget it.

Next time something breaks, instead of spending time on troubleshooting, you timeshift back to a known good point and then just get on with using your system.

With the auto-snap package installed every update also creates a restore point to go back to before it.

In addition to that, I started updating my system less frequency. The logic being that the more often you update a rolling release install, the more likely you are to catch it at a time when something is wrong, before it is fixed. Still regularly, but instead of every other day, I now have an update notification that goes off once a week.

The result has been zero time spent troubleshooting my system. If it worked yesterday, it’ll work today. If it worked last week, but doesn’t today, I’m a reboot away from a known good snapshot.

Wayland has been fine on nvidia for a while now. Even G-Sync works.

I feel like you must have said something dumb online, and gotten absolutely dogpiled for it, to draw this comic.

These big companies don’t learn that fast.

The decisions to “invest” in these live service projects were made years ago, and execs are terminally allergic to pulling the plug on something once it’s a couple million deep.

They’re like cruise ships crashing into icebergs, except that once they set a course they aren’t set up to change it even if all the other ships start crashing and sinking.

Those get taken down on a regular basis. Not to mention the atrocious bitrates that is all they can manage.

Meanwhile, a high quality BluRay rip on my drive ain’t going anywhere.

You can’t seed properly.

“Why store anything? Just re-download it from someone who’s still storing it!”

You see the catch 22 here?