Wait till you hear about the idiots who unironically make that argument for banning Bitcoin too
Wait till you hear about the idiots who unironically make that argument for banning Bitcoin too
Framework
Copying is not theft. Letting only massive and notoriously untransparent corporations control an emerging technology is.
Accessing printers? Resolving hostnames of internal hosts? I can’t imagine having a lan without mDNS
I don’t think it’s quite as simple as someone just forking it. Realistically, a browser is an extremely complex piece of software that requires a lot of organizational effort to maintain, deal with security issues, etc. Pretty much every other piece of software on a similar scale I can think of (the kernel, KDE, Blender, Libreoffice) has some sort of organization behind it with at least some amount of officially paid work. All the major forks of Firefox or chromium follow quite closely to upstream for this reason (which is also why I’m skeptical of Brave’s ability to maintain manifest v2 long term, despite their probably genuine best efforts to do so).
I do wish that Firefox were developed and funded by an organization specifically dedicated to developing it. This could of course happen if Mozilla dies. But that’s going to require someone starting it, which is not at all a small or cheap task.
I could also see a future where Oracle or IBM buys it 😂🤡
A year ago, the majority of Lemmy was vehemently in support of banning porn
It is based on the assumption that every piece of code in the entire stack from the UEFI firmware to the operating system userspace is free of vulnerabilities
Whenever I want to pirate something I just go straight to btdig. And if there’s no torrent and I really need to search the web, I’ve had much better luck with Yandex. I figure they’re more resistant to takedowns from western corporations
This would not be the default behavior of yt-dlp. Run yt-dlp -vF <video>
to view the sort order used. Acodec should come before abr.
It used to be the behavior of the original youtube-dl, however.
Resampling does not lead to any perceptible quality loss, but encoding to aac with libavcodec’s encoder (as YouTube does) definitely will. At the very least, it cuts all frequencies above 15 kHz which are potentially audible. Opus does not, and 128k opus is usually considered transparent.
I can’t find it but somewhere there’s a very detailed explanation from Monty himself about it
Are you using the very latest version? YouTube changed their site again a few days ago and it broke yt-dlps ability to find all thr formats. Update yt-dlp and it should be back to normal. yt-dlp will prefer the opus when it is available by default.
Opus is much better than (YouTube’s) m4a. m4a is better than mp3 (which is an obsolete 30 year old format). YouTube doesn’t serve mp3 (so creating one means re-encoding), and re-encoding lossy formats always loses quality.
yt-dlp is pretty much the standard program for it https://github.com/yt-dlp/yt-dlp
It is installable as a python module, so it should be easy to sandbox if you need to (though it requires ffmpeg too). Nowadays I almost view it as a standard unix utility though and wouldn’t think twice about installing the native package
This one is already in the default uBlock filters - Badware risks
I also strongly suggest adding https://big.oisd.nl/ as a filter list. It’s a large and well maintained domain blocklist (sourced from combining lots of other blocklists) that usually adds lots of these sorts of domains quickly and has very few false positives.
If you want to take it even further, check out the Pro list and Thread Intelligence Feeds list here https://github.com/hagezi/dns-blocklists
These can all be added to a pihole too if you use one.
This is why ublock origin is an essential security tool.
This is a forum for general discussion, not a question and answer board.
Adopted daughter. But still…
Ok but I don’t see how that was ever in dispute?
Never thought I’d see banknote inflation rule 34
Companies cry the same way about the bills to ban end to end encryption, and they’re still bad for consumers too
Perfect example of a (part of a) security vulnerability being fixed in a commit that doesn’t immediately seem security related and would never be back ported to a
stablestale distro