yt-dlp does a great job at ripping on majority of websites. If yt-dlp can’t rip something then likely there is service-specific tool to do that i.e tidal-dl for Tidal (hi-fi music service). There’s also a hardware method that involves cheap chineese hdmi splitters (it needs to be a cheap one, b/c they lack support for DRM) and hdmi capture card. Sometimes it’s DVD or blu-ray ripping.
From what I recall, this sort of stuff is usually kept as a closely guarded secret by those who do it. Perhaps someone else more knowledgeable about the practice could give some more insight.
Interesting, I wonder why that is. I guess to stay one step ahead of the corporations trying to prevent them from succeeding? I can’t imagine it’s to prevent others from following suit. Feels like that would be a weird motivation for people saving and disseminating content.
Monetization is another secret probably. Ads alone could drive millions on streaming platforms. I don’t have idea on public or private trackers, but I guess is also more than what I could win in my life xD but that’s probably me just being poor.
Usually the methods are not shared because streaming services would go out of their way to break them. Just like Youtube breaks yt-dlp every now and then. But Youtube is too big to implement any serious protection, so, downloaders usually win. I heard Crunchyroll is ripped via their mobile app, albeit modified. But specifics are better left in the dark.
Closest I’ve got to info is widevine keys extracted from insecure Android boxes. I’m happy just to download their copy tbh. It’s usually just as quick, if not more so.
I don’t even see footnotes in the documentation^[at join-lemmy.org/docs/en/users/02-media.html], but they can be pretty useful. It’s ^[text], in case others are curious.
That’s really interesting. AFAIK Lemmy devs do not have a comprehensive markdown documentation. I thought it was CommonMark plus spoilers and Lemmy links, but it seems like they have other changes as well.
I filed a bug with Jerboa a long time ago about something related to this (I don’t remember exactly). I guess right now the philosophy is that every front end/app can render how they see fit.
Ultimately, this is just my opinion about what apps should prioritize in terms of markdown. I don’t think it’s too much of an ask that these be consistent across apps. I’m not sure that there has ever really been an effort by the devs to standardize things in this kind of way. As I said in the post itself. Lemmy is no longer a baby platform. people have been sharing these best practices for markdown for over a year at least.
I think that when someone posts, they should have a reasonable expectation that people will see what they intend.
Yes, I didn’t go that far down the rabbit hole. I decided to very unscientificly pick five categories that I personally thought were relevant and score those. There are lots of markdown types and situations that are not captured here.
The fact that it’s so perfectly positioned, makes me think somebody did this on purpose, maybe holding a magnifying glass by the window, people passed nearby but paid no attention - after all, nobody’s trying to break into the car - but there they were, fucking up somebody’s car with an analog, rudimentary, sun-powered, laser-like device: a piece of glass.
Could be, but I think a seat heating malfunction is more likely. Looks like an older vehicle so there’s all sorts of things that could break down.
The driver also might’ve just parked it in the exact right spot to catch problematic sun reflections. There’s been a few buildings that are known to cause issues. People who parked around the ‘Walkie Talkie’ building in London had melted body panels, mirrors, burns in their interior, etc. They had to install screens on the building to stop this ‘death ray’ effect.
I tried to stop a while ago, in less than 2 minutes the craving was in me… I cracked, despite all my promises to myself, I breathed again. Definitely addict !
Maybe I’ve put on weight since then, wouldn’t surprise me
You mentioned in a comment that you used Arch, Debian and EndeavourOS. Though, historically, Wayland has been adopted first on Fedora. Therefore, I wonder if underutilizing Fedora (and/or derivatives like Bazzite/Nobara) might have been the main culprit in this case.
Could you perhaps be more precise? Is it a specific one? Or are there a multitude of steering wheel drivers that satisfy your needs?
And virtualbox.
Do you specifically need VirtualBox? Or would Qemu/KVM satisfy your needs?
IIRC VirtualBox requires kernel mods. Therefore, you would have to create your own images 😅 in which said kernel mod is included. FWIW, both uBlue’s templates and BlueBuild do a wonderful job at streamlining this process.
Or…, as alluded before, you don’t necessarily need VirtualBox. But, instead, Qemu/KVM perfectly satisfy your needs. Then, you can just run ujust setup-virtualization. After which you reboot, and you would be good to go.
Im describing a use case of my friend whom I convinced to use linux instead of windows for gaming. His steering wheel is on this list: github.com/ublue-os/bazzite/issues/901
While not being tech illiterate he wasn’t thrilled to build his own fork of the OS and I don’t blame him. He also wanted to use virtualbox, and I won’t force him to switch to qemu or kvm because Im not a gnome developer to invalidate someones use cases. He settled for endeavor os and is very happy with it.
IMO immutable distros aren’t a best fit for a desktop computer. It can do so much more than gaming and turning it into a dedicated console is a step back if a normal linux distro can do just as well.
IMO immutable distros aren’t a best fit for a desktop computer. It can do so much more than gaming and turning it into a dedicated console is a step back if a normal linux distro can do just as well.
I would personally nuance this to: “Current iterations of ‘immutable distros’ that have evolved from traditional distros haven’t matured sufficiently yet to tackle 99.99% of the use cases ‘easily’.” The exact number on the percentage I don’t know. I believe most people that use their PCs as a glorified app launcher should be more than fine. But we start experiencing major difficulties the very moment that (a)kmods are involved; some of which are ‘supported’~ish, while others certainly aren’t.
But, I simply fail to see why a future iteration would not be able to solve related issues.
Seconded that. Debian is pretty much always outdated, DIY Arch is easy to get wrong but I think Endeavour would have worked even though I don’t know all to much.
However saying Linux is not stable enough without trying Ubuntu is not fair IMO.
kbin.life
Newest