Any way to rip high-quality from Apple Music? Or Spotify?
Chewy @ Chewy7324 @discuss.tchncs.de Posts 96Comments 1,013Joined 2 yr. ago
Chewy @ Chewy7324 @discuss.tchncs.de
Posts
96
Comments
1,013
Joined
2 yr. ago
KDE and Gnome being nearly identical, irrespective of X.org and (X)Wayland, was to be expected. Prior benchmarks came to the same conclusion, altough I believe to remember the gap between Wayland and X.org has been widening slightly.
It'd be interesting to see if games running natively on Wayland will change things a bit more, but I don't expect it to change performance any more than it did until now (barely measurable). Most of the performance issues of games is having enough compute to calculate the frames, not how they are presented.
But it's interesting that Gnome Wayland still has some unexpectedly worse results in a few cases, altough it's not a reason to choose any desktop over another.
PiVPN is great and was one of the first services I experimented with on my old Pi 3.
Now with wireguard existing I didn't feel the need for anything besides wg-quick or using wireguard directly. I didn't even know PiVPN got support for wireguard, but it's great that it got maintained for so many years.
If that's the case, streamrip still works fine with Tidal. Deezer support is currently broken.
In this case it's a bit weird though, as the game lists Linux as supported platform, but obviously just ships the Windows build with Proton instead of having a native Linux build that uses open cross-platform APIs.
It being under supported platforms might mean that the developer officially supports proton and thus Linux. Hopefully they'd provide fixes if they somehow break the game on proton (e.g. they won't add an unnecessary launcher which breaks the game).
It still works for private instances. The moment a public instance makes enough requests to reddit, they block it.
I'm running libreddit on my home server and access it through wireguard. Never been rate-limited. It's the only thing I still use Libredirect, since most platforms ban third-larry frontends.
Doing the dishes while listening to podcasts with low battery makes me wish my wireless earphones didn't break so soon. The amount of times I took my phone out, put it on a table and walked away to tow it off the table is staggering. Or forgetting to turn down the amplifier before unplugging just to get blasted with static noise isn't something I miss.
Not having to bother with reconnecting bluetooth headphones and instead plugging in a cable is great tho, so I understand everyone who still likes their wired headphones.
After 15 to 20 years of 64bit supporting systems being sold, I don't think it's an issue to drop 32bit support. Even if someone wants to use such an old pc for any reason, it should be fine to run an older version of Minecraft. There's still MC 1.8 servers around, and they'll likely continue to exist for many years to come.
Online transactions require a second factor which displays the actual amount to be transferred. This works by either an app which receives the transaction data (recipient, how much) over the network, or a device which takes the bank card and is used to scan something similar to a qr code. The device then displays the transaction data.
This makes sure a fraudulent site can't easily change the amount or the recipient of a transaction, even if they somehow made an identical website (or close enough).
For remote transactions (e.g. online payments), the security requirements go even further, requiring a dynamic link to the amount of the transaction and the account of the payee, to further protect the user by minimising the risks in case of mistakes or fraudulent attacks.
https://www.ecb.europa.eu/press/intro/mip-online/2018/html/1803_revisedpsd.en.html
It's not perfect, especially with people using a banking app and the second factor app on the same device for convenience sake.
That's a bummer. Seems like Google Pixel and Fairphone are the only ones left. I don't even know why manufacturers wouldn't allow for relocking or even unlocking of their phones. I can't imagine they make much money with user data and the phone is already paid for. Warranty claims shouldn't be much of an issue either, as modifications can be easily detected and it's likely not a relevant amount of people anyway.
The banking apps I've tried don't require SafetyNet, instead they use Android AOSP's basicIntegrity. The latter doesn't require certification by Google, but also checks whether the device is rooted and the bootloader is locked.
This means custom ROM's on most devices won't pass basicIntegrity, as only Google Pixel, OnePlus and Fairphone allow for relocking the bootloader.
At least in the EU web browsers don't allow for authenticating transactions (beyond a limit of e.g. 30€). Either an additional authenticator app or a standalone card reader is mandatory.
Luckily my banking apps work flawlessly on GrapheneOS and even microG, likely because of they care about the bootloader being locked again.
I understand what you mean. With Redis and many other database/cloud companies switching to source-available licenses, maybe the term source-available doesn't have to have such negative connotations. Open-source is also divided in permissive and copyleft licenses (e.g. BSD and GPL), both have big implications on how it can be used.
Redis and others see themselves forced to switch to a more restrictive license because of the big cloud providers, who sell services for others software, without contributing back. This change is not good, but it might be necessary. Just like GPL is more restrictive than MIT, but it's necessary to force some company to actually give back instead of only taking.
I personally don't really dislike licenses which allow for the necessary freedoms of open-source after one or two years. It's a compromise but secures the longevity of software beyond a companies success. It's way better than proprietary code.
Yes, it's sad that Canonical is pushing Snap before those kinks are ironed out. In general it's a solid distro for people not familiar with Linux, but having to stumble over those issues is a dealbreaker.
Linux being easier than Windows is true in some ways, but it completely sidesteps issues Windows and macOS solved for a while, e.g. forcing users to upgrade. It's annoying but some people just... don't do the bare minimum. E.g. a friend's dad has been using Linux for probably a decade by now, and for some reason apt auto upgrades broke (likely powerloss during upgrade). An image based OS like Fedora Atomic doesn't have this issue, as it won't apply updates to the running OS (by default).
Yes, I've no problem with your position on copyright and many institutions do many bad things. My issue js with misuse of terms with a fixed meaning, i.e. open-source. Having different people use a single term in multiple ways makes it so much more difficult to understand each other and enables bad actors to rile people up against each other.
A tame example is "stable" Linux distros, where "stable"can mean package versions stay the same (besides bug fixes), and then people come and say their Arch Linux never broke, so it too is "stable".
Why wouldn't it be open-source. It's right there in the name: the source is open.
In the context of criticism of how copyright works I understand the above sentence, but using a well understood term differently still annoys me enough to write lengthy comments.
PS: I do hope lemmy implements a way to add copyright notices to comments like it allows for setting the language of posts. It could be implemented in a less noisy way. People who don't care about a license ignore it anyway, while people who do care would likely find it without much trouble.
The license you're attaching to your comments uses copyright to restrict commercial use. Are you okay with any company ignoring your license because you've posted it in the open?
The term source-available is exactly what you should be using instead of open-source, as the latter has been defined differently for decades.
The only instances I've seen people using the term open-source literally has been companies who wanted to benefit from positive connotations of open-source, while using a commercial source-available license which restricts many freedoms.
Another comment: https://linkage.ds8.zone/comment/1105950
Having issue with the Steam snap isn't surprising, as even Valve recommends against using it. A few years ago flatpak Steam had similar issues that got fixed over time.
For now I hope you'll have more luck with the .deb!
If you want a share of their profit, how much is enough? Would it be a pay-what-you-want model, without any restrictions or how'd you define the minimum amount to stop them from donating 1$? A rate based on profits would be pretty much the same as charging a license fee based on a companies worth.
I get why you want to force donations, but at the same time restrictions like that aren't compatible with the FOSS freedoms. Like others said, dual-licensing or a source-available license is probably the closest you'll get. It's not a license I prefer, but it's okay. For example I'd rather have a non-compete clause for two years than something being proprietary for eternity.
How much will you be paying for a 25Gbps connection? And where do you live for these speeds to be available? Where I live 1Gbps is the max since a few years ago and costs 80€.
Can't help you with private trackers except recommending taking the invite for RED/OPS. TL sometimes does open signups and is solid for english content. MAM has a friendly and active community, so I definitly recommend joining them (if you're interested in books/audiobooks).
As I understand it, there isn't really a canonical way to burn an ISO. Any tool that copies a file bit for bit to another file should be able to copy a disk image to a disk. Even shell built-ins should do the job. E.g. cat my.iso > /dev/myusbstick reads the file and puts it on the stick (which is also a file). Cat reads a file byte for byte (test by cat'ing any binary) and > redirects the output to another file, which can be a device file like a usb stick.
There's no practical difference between those tools, besides how fast they are. E.g. dd without the block size set to >=1K is pretty slow [1], but I guess most tools select large enough I/O sizes to be nearly identical (e.g. cp).
[1] https://superuser.com/questions/234199/good-block-size-for-disk-cloning-with-diskdump-dd#234204
The dowloaded files can't be played and testing .flacs with
flac -tthrows errors.https://github.com/nathom/streamrip/issues/656