I have to agree, I never used the VA features. I was prepared to have issues with banking apps and such but found myself not having issues with even those.

Apparently they we're contractually obligated to include that, which is why there's an option to snooze it at all. I'm sure they'll get rid of it eventually.

Thanks for relaying this!

Cool, good luck going forward!

This is a really cool tool if used correctly. It seems much of the concern comes from spam. Forgive me if this is already a feature or planned, but maybe setting a timer per batches of posts might be helpful? That way you could select what you want moved and each x hours/days if copies a set amount of posts over.

Was checking if anyone had mentioned this. You gotta pay respect to the classics. The whole moon series was great.

Thanks, it's looking like I'll be doing a reset. It looks like grub-btrfs creates its own entries and points towards the boot directory within the /.snapshot/ directory, completely ignoring my boot partitions current files.

Ubuntu was never my first choice but was necessary for using my arc380 with plex transcoding. Might as well take this opportunity to move back to debian with bookworm. Only trouble is I would prefer a 6.2 over 6.1 kernel distribution, and while I enjoy arch on my laptops, I'm not sure I'd want to update my server so frequently.

Well, I tried rolling back to another snapshot and checked my kernel params and its not in there. My port issue seems to be fixed but i still do not boot into the new kernel after updating and rebooting. Edit: I think I need to clean up my /boot directory somehow since it's partition is not btrfs. But I'm unsure how to do it, or where to read up on it.

I think you've hit the nail on the head. The way grub-btrfs works is by changing the default root snapshot subvolume. I'm still not sure what I did wrong to get the rollback stuck to the particular kernel. But I'll give what you've written here a try. Thanks again.

Yes, I've done that to no avail. And when I run "dpkg -l | grep linux-image" it shows I have five different kernels on my system, despite me only having the latest one installed through apt. Edit: Scratch that, I think I was misreading the input but the fact remains I can't seem to get rid of 6.2.0-24

Yes, I have a separate boot partition. How would I fix a mismatch? The only posible solution I've found is to directly edit the grub entries, but that's a bit beyond what I've done with grub before. Thanks for the response!

Theres 1337x, but otherwise I would look for a private tracker holding open signups.