I set up a local BBS-like system and used the real NetZero* dialer to call it and attempt to log in. Then I changed my password and repeated the process several times.
That gave me the key to the Caesar cipher they used for the password.. so I could create a fresh account with a scrambled password any time I wanted.
At runtime, in the OS-provided ad-free dialer, I'd use the unscrambled password.
I also pre-created some accounts with unscrambled passwords like "apple" and "bicycle" to share with friends.
NetZero* ceased operations mere weeks after I started this.. Hm.
(* Was it NetZero specifically, or some clone? I forget..)
> Not least of which being that with bandcamp I can download purchased music years after purchase, even if artists have died or bands broken up, I wouldn't have that guarantee here
Note that this isn't guaranteed, especially for smaller bands that get picked up by a label. Most of the time the label just makes the releases hidden, so they're no longer displayed publicly, but can still be downloaded. However, some labels delete the release instead, so it's no longer downloadable from your collection.
The best approach is to take advantage of the fact that Bandcamp lets you download everything and simply download everything you buy and keep backups (as you would with any other important data)
Yep exactly, that's what I do too. Download a lossless version and then use Bandcamp if I ever wanted to stream it. However I also host Navidrome (OSS streaming with a web-app) so use that 99.9% of the time I want to stream.
Even if there aren't labels requiring artists to hide or delete music from Bandcamp, you never know if Bandcamp could just go down one day for financial reasons and then you're screwed.
This is the primary use case for Bandcamp for me -- it's one of the main ways I buy new music. I'm not interested in streaming services. Being able to buy (with most of the money going to the artist) and download lossless copies of albums is what I want.
Yep, I download the FLAC and always keep the original zip file, and back it up separately from the files I manage with beets. I playback the beets-managed files with Navidrome.
Beets doesn't maange handle the extra files that the zip often includes, such as PDFs of linear notes, the sheet music I once found included, or band photos. Maybe someday I'll figure out a good archive for everything that isn't "the literal zip file".
When I moved continents in late 2022, I bought Unifi's WiFi 6 APs specifically because I knew I could flash OpenWRT on them without issues. I wouldn't try running them as a router, but as APs for an existing network, they work great.
I run a number of sites on a single server behind a reverse proxy, and the fastest to load is a CGI service, cgit. I use Traefik as the reverse proxy nowadays, which doesn't support CGI directly, so I've bridged it with Go's net/http/cgo. Even with this extra hop, it the performance is still excellent.
I've been using Qobuz (along with my own Navidrome instance) for the past year. The depth of music in some genres seems pretty good, and seems to have all the mainstream artists, but once you get past them in indie/pop/rock genres the gaps in the catalog really start to show. I've reached out to some artists, and no one seems quite clear why their releases don't appear in Qobuz when they appear in all of the competition. Unfortunately, none of the competition makes lossless streaming available (and I'm not counting Tidal's MQA, even if it was available on Linux).
When I joined they had some social features, and searching for user created playlists seems possible. The last couple of times I've tried I've only gotten Qobuz's official playlists in search results. I've had to make do with syncing playlists from Spotify with Soundiiz.
When combined with how inaccurate the metadata is (including the lack of ability to report the inaccurate metadata) and the lack of any new features in the past year (including lack of copying pre-saves from every other platform), it really seems like investment in Qobuz has stalled.
It's too bad, because it seemed pretty promising. I really miss Rdio. :'(
For listening to Navidrome on the go I use the "substreamer" app on Android. The "Podcast Republic" app also works well for listening to college radio streams to find new artists.
May or may not be available in your locale. I don't actually use Deezer (I use Spotify) so I don't know how much of their catalog is available in FLAC.
I debated even including the disclaimer. It's been ages since it was shut down, and it's been 13 years since I was even there. However, I didn't want to violate some HN netiquette by not being transparent.
Reporter of #15526 here. I've still only ever seen this corruption in files being built, which seems to be a situation that the race can be won repeatably by some packages. I reviewed all my user data and I've found no corruption to it, but my workloads don't involve block clones.
Coming back home and checking 2.2.1 out zfs instantly started spewing write & checksum errors due to #15533. Both this and #15526 seem to have underlying issues from <2.2 that are just more easily triggered now.
First one also confirmed on FreeBSD now.
Holding off on 2.2 seems recommended, and if you're keeping critical data on OpenZFS it might be a good idea to give the issues a glance. The 2nd one might have the same underlying solution as an issue that has given me system freezes when closing in on ~90% pool usage using 2.1 on top of LUKS.