It worked, thank you very much for your help man! Now the only remaining problem is the snapshot 166, that snapper does not let me remove. I assume I should remove in a similar way as timeshift:
$ sudo btrfs subvolume delete /.snapshots/166/snapshot
WARNING: not deleting default subvolume id 2968 '/.snapshots/166/snapshot'
I think there’s something I’m missing about how these snapshot works
Yay! More free ads!
Thanks for the answer! I mounted it and removed all the timeshift-btrfs stuff. now, after a reboot, sudo btrfs subvolume list -t /
does not show timeshift stuffs anymore, but if I mount again sudo mount -o subvolid=5 /dev/nvme0n1p2 /mnt
and ls /mnt/
I get:
@ @cache @home @log timeshift-btrfs
how can I remove timeshift-btrfs
from there? can i just rm -rf
it?
In openSUSE
(sorry I forgot to mention, I’m running EndeavourOS)
Uhm this could be a good workaround, I’ll look into it, thanks! It would solve the movies problem, but not any other screen sharing problem
Thank you!
I already have a jellyfin instance, but syncplay didn’t works very reliably for me, some users experienced freezing, jumps and other problems
Thanks for the suggestion anyway!
It would be just me sharing to everybody else on the internet (no more than 6 people)
Jitsi meet works great, the only problem is being able to share only “a portion” of what it currently does
I think the problem is not something related to jitsi, meet, discord or matrix, but rather to the OS screensharing capabilities
Please tell me this is not real
Look at the corner between the four “paragraphs”… WHY? Please Microsoft align them properly
Why do you need a waterproof laptop? (I’m just curious)
Is this real or just a meme?
Other answer seems to suggest that the problem is that the same podcast can be available, depending on where and who is listening to it, with different length due to different ads injected into. Here’s my probably stupid and completely ignorant suggestion: instead of using timestamps for both begin and end of the ads segment, you could use a timestamp for the beginning, and an hash of the first part of “non-ads” segment. I’ll try to explain better:
|----------------xxxxx--------------------|
^ |___|
The xxx is the ads segment, the ^
is the timestamp of the beginning of the ads, the |___|
is a small duration segment (for example, 0.5 seconds) right after the ads segment. The data of that segment is hashed and used as “end ads segment indicator”.
On the other device, with a different duration of the ads, you should start hashing it to find the corresponding segment.
Is this doable or did I just said a bunch of idiot things?
This… This is amazing! I can finally write an application switcher optimized for my touchscreen device! Thanks KDE devs!
I always see “this doesn’t work, why?” posts, it’s the first time I see a “this works, why?” post XD
Holy words
Thanks for sharing this kind stranger, I really needed this