![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/1f7e5534-88d3-4d6f-bc57-7cda9553890f.webp)
- Don’t use
"*"
dep version requirements. - Add
Cargo.lock
to version control. - Why read to string if you’re going to base64-encode and use
Vec<u8>
later anyway?
"*"
dep version requirements.Cargo.lock
to version control.Vec<u8>
later anyway?keep in mind that it’s hard to get real numbers on LDAC because decoding is proprietary
I used to think the same. But as it turns out, a decoder exists. Maybe some people don’t want anyone to know about it to keep the myths alive ;)
EDIT: Also, as a golden rule, whenever anyone sees the words High-Res in an audio context, they should immediately realize that they are being bullshitted.
This should be de-stickied. The instance appears to be receiving zero maintenance (still on 0.17.4, enough said).
While this is indeed paranoid and not well informed, I’m kind of appreciating… the GNU appreciation.
Makes a good change from all the hypernormalized Twitter/Mastadon non-coders, or self-proclaimed coders (the kind that uses terms like “imposter syndrome” every day), always bitching about how GNU was a mistake, and all it did was provide free labor for corporations, and how the FSF and Stallman are all kinds of bad and wrong.
Or “Hyphanet” as it’s now called.
wtf, I missed that news.
Click the “more” button (three vertical dots), then the flag button!
Yes. That was what I’m alluding to when I wrote:
that architecture didn’t see large scale success before, except in Japan
Perfect Dark is a major network in Japan. Freenet is a network most people in the globe are not aware of. Hell, Perfect Dark may have a larger Japanese user-base than Freenet’s global one.
It’s worth mentioning that the former leader of the Freenet project wasn’t the most competent. Combine that with him spending years trying (and failing) to cater to the needs of imaginary dictatorships’ defectors (anyone of them using Freenet instead of Tor is the imaginary part), instead of focusing on maximizing the reliability and performance of the network to help its actual users. So it’s not just the ignorance of the masses that was at fault. The default FN user experience was often a horrible one. And users needed to ignore the officially-recommended microblog/forum applications, and even use a patched FN version, to get a decent performance out of the network.
Anyway, Freenet is the past and the present. And as I wrote in the parent comment, I hope a Freenet-like network would become a major success in the future, but I’m not holding my hopes up.
I do think it is the future of filesharing
In internet years, Torrenting is old. I2P is old. Even torrenting in I2P is old. Nothing about this is “the future”.
Ideally, the future of file sharing would involve a fully/natively integrated anonymous network with content-addressable distributed filesystem.
But this will probably not happen, as that architecture didn’t see large scale success before, except in Japan where at least some elements of this architecture are used in their popular P2P networks.
The I2P crowd themselves tried with Tahoe-LAFS, but that was never really a network, even aMule over I2P had more traction, and by traction I mean tens or hundreds of users, not thousands or beyond.
Ironically, the one content-addressable distributed filesystem that gained some attraction (outside Japan) is IPFS, which doesn’t offer anonymity, or replication, or anything special really. Yet for some reason, some hype-susceptible techies liked it, together with the NFT crowd, a great fit.
The future of file sharing will depend on where most content will land where it will be easily accessible and quickly grabbable. How those networks will look like? Nobody knows.
Your information is a few years outdated. lineageOS neither comes rooted, nor does it offer a native way to root anymore. Magisk became a thing with a whole community around it. It’s an unlocked bootloader hider, root manager (and hider), and a system patcher, all wrapped up in one tool.
With Magisk, you give root access to the apps that need it, hide root ability from apps that require non-root devices (those apps do that by pretending to need root). Also, the Magisk app can rename itself, which is important as some apps check against the name itself.
The future challenge is with Google trying to force hardware identification (Apple style). I have not been following developments regarding that though, since as others mentioned, my X years old phone is still serving me perfectly, and I have no intention to upgrade any time soon.
Don’t know if this will be relevant at all, but I’m almost hoping this will force Lemmy devs to abandon the obscure markdown crate they use for pulldown-cmark.
Using an obscure markdown implementation just because it supports spoiler tags always sounded like a silly decision to me!
Soulseek is an old-style P2P network. It has nothing to do with my parent comment. I personally don’t use it (see my other comments in this thread).
If you want to grab a non-reencoded file from YouTube, you can use a tool like yt-dlp
# see what formats are available for a YT vid
yt-dlp -F <youtube-url>
# format 251 is usually available as the highest quality Opus format
yt-dlp -f 251 <youtube-url>
That last command should grab you an Opus stream in WEBM format.
If you’re not a CLI guy, others should be able to give you a good GUI recommendation.
YouTube has audio in Opus format@~150kbit/s. Opus is a much better format than MP3. Almost all audio is completely transparent at that bitrate, where with MP3s, there are cases where audio is not transparent without using non standard >320kbit/s bitrates (a lot of content is transparent @320kbits/s though).
Now, sites/tools like the one you mentioned take the Opus (or AAC) file/stream from YouTube, and lossily re-encodes it again, probably to a file that is larger than the original, with at best the same quality, but probably worse quality. You obviously can’t get better output than the input in lossy compression.
So, the disk space argument is weird if you can play Opus/AAC (should be playable on every device nowadays).
This is the valid part for why you shouldn’t use YT-to-MP3 converters.
But there are also invalid reasons why people will tell you it’s shit:
What hubs are you recommending that are better than Soulseek?
I hardly use DC++ anymore. I mentioned it because I didn’t find anything unique about Soulseek when I tried it last a few years ago. But I did grab plenty of classical music in lossless format from DC++, using public hubs.
So, it’s the “are better than Soulseek?” part of the question that intrigues me. What’s good about Soulseek? For lossless collections, it doesn’t (didn’t?) have much. For lossy stuff? There are better (in selection, availability, and quality) places to grab lossy files from (e.g. YouTube). And Torrents (with or without DC++) would probably have you covered there too anyway.
That is/was my experience with all these platforms/networks. I’m open to learn something new if I’m missing something.
I won’t be able to fully replace it, I’m afraid. Not before communities gain the ability for their posts to not show up in high traffic feeds.
Some subreddits I follow have this set, but this is not yet implemented in Lemmy if I’m not mistaken. So a workable move to Lemmy for them is not possible at this moment.
Just as the other user said, using YouTube Audio for this stuff is the way to go.
Just look for <Artist Name> - Topic
channels and check the playlists (not the uploads). You should find full albums uploaded directly by copyright holders. Use a VPN
if you don’t find anything. Sometimes stuff from your region will not be available in your region, but available if you appear to be somewhere else ;)
Also, if we are going old style P2P, and not using torrents for some reason (RuTracker deserves a special mention), then DC++ should come before SoulseekQT/Nicotine+ anyway.
Mostly lossless grabs from torrents + YouTube Audio (edit: using yt-dlp
), and you have a selection with guaranteed high quality*. Definitely better than whatever scattered MP3s in SoulseekQT/Nicotine+
* Opus@150kbits/s is transparent, except for some killer samples heard by a trained ear.
Regarding
Cargo.lock
, the recommendation always was to include it in version control for application/binary crates, but not library ones. But tendencies changed over time to include it even for libraries. If arust-toolchain
file is tracked by version control, and is pinned to a specific stable release, thenCargo.lock
should definitely be tracked too [1][2].It’s strictly more information tracked, so there is no logical reason not to include it. There was this concern about people not being aware of
--locked
not being the default behaviour ofcargo install
, giving a false sense of security/reliability/reproducibility. But “false sense” is never a good technical argument in my book.Anyway, your crate is an application/binary one. And if you were to not change the
"*"
dependency version requirement, then it is almost guaranteed that building your crate will break in the future without trackingCargo.lock
;)