It does (they of course use their Azure Blob storage under the hood). Forgejo however does not (even though it supports it for releases and packages and Golang has this in their standard library).

I’ll keep the idea in mind.

Technically unlimited, but you obviously need to have enough storage to cache the zip files (and RAM to cache the file index). My server is very small, so I needed to set the limit low.

Pin codes are great for quick access if you have a lockout mechanism after 3 failed attempts and it is impossible for an attacker to get the hashed code. It is only secure if you pick a pin that cannot be guessed in 3 attempts like your birthdate but that applies to any password.

Thats why they are used for credit cards, SIM cards or Bitlocker drive encryption. The hashed code never leaves the secure hardware so you cannot circumvent the lockout.

Even a 16digit numeric code, which I guess is the upper limit of what you can remember and quickly input, would take just a couple of days to brute force if the attacker does get hold of the hash.

Spotify does not have the power to lock your credit card or paypal account. Account bans might happen and I have seen E-Mail screenshots of people who got banned. I am not sure if they would take down an entire set of family accounts.

If you care about the content of your Spotify account (playlists, listening history) you should not use it for piracy. Just create a new one. If you are fine with 160kbps OGG files, you dont even need a paid account.

Do not create Spotify accounts with trash mail addresses, they may work at first and get banned the next day (happened to me after I created some accounts for scraping their API).

You can also export all your Spotify data as a precaution (GDPR export from the account page, they send you an email with a link to a zip file after a couple of days).