(Unless I accidentally delete the wrong folder. And none of it depends on Bandcamp staying in business, or the artists and labels continuing to make their catalog available I have copies, they belongs to me, and they work even if I have no internet. Spotify's discovery is still much, much better here, though I find a lot of things by way of happy accidents on Bandcamp, but Spotify is super consistent in putting stuff I've never heard of (but end up enjoying) in front of me.Īnd then there's the whole "I'd rather put more money directly into the artists' pockets" thing, and BC does a much better job of that, and in general it seems like there are less hands involved in passing the money from my wallet to the artist.Īnyway, my use of Bandcamp has snowballed somewhat since I started using it, and my collection is now. I've also stumbled across a few labels on Bandcamp that carry more niche stuff that I like (tends work really well for ambient, chillhop, *wave kind of stuff), and they end up surfacing a lot of artists that I'd have never heard of otherwise. :P) Getting FLACs of the original media the artist uploaded is a big selling point for me. I also originally used Bandcamp to get higher-quality copies of music than what Spotify will stream I've spent an unreasonable amount of money on audio equipment, and it does a great job of highlighting some of the limitations of the music you listen to. :) (Bless you, Musicbrainz Picard, for making organizing this stuff Not Suck.) Speaking strictly as a listener here: I started using bandcamp to get physical media (vinyl, typically) for my favorite artists, and the fact that I usually get a digital copy that I can toss on my local media server is a nice bonus: I went to all the trouble of setting up Jellyfin for my movies and TV shows, I might as well use it for my music too. My biased opinion? Caddy is the better web server for the vast majority of use cases. In others, Caddy is faster.Ĭonfiguration is more flexible in Caddy, with its native config being JSON, but with "config adapters" so you can use other formats, like the Caddyfile, YAML, or even nginx config, to power Caddy! Plus, Caddy's config is managed through an API so you can automate it more easily and universally.Ĭaddy has no external dependencies (not even libc).Įverything else you need to know is in the Caddy docs: Performance is comparable for 99% of use cases. Caddy is less prone to errors and is better at error handling. These are both bad options, it is best to have fewer moving parts. With nginx, you have to set up separate tooling to automate it, or you do it manually. > how often do I have to renewal the Certificate or does the program renew it by itself.Ĭaddy does it automatically. Nginx is written in C, and Caddy is written in Go, so exploits like Heartbleed could never affect Caddy. Yes, inherently one is written in C and is thus prone to a whole class of vulnerabilities known as memory unsafety bugs, whereas the other isn't.
0 Comments
Leave a Reply. |