@ClemaX
@lemm.eeNginx is pretty easy to set up. Look up "nginx virtual hosts". You might want to use certbot/acme if you don't have SSL certificates for your domain names. You need either a wildcard certificate (*.example.com), a certificate with SAN (Subject Alternative Name) containing the second subdomain, or two certificates (one for each subdomain). Note that subdomains can be found more easily than path based websites, if you allow connections from the whole WAN.
Try this:
for file in ./*
do
echo "$file"
done
To do some substitution operation om the filename you can use Bash Parameter Expansion.
Rumors say there are some platforms selling grow-kits including everything needed to get started. In Europe, people recommend some platform starting with Zam and ending with nesia, which supposedly provide a variety of kits.
You can also find plenty of resources online to start from scratch. The easiest seems to be the uncle bens method.
If i understand correctly, whataboutism is used to burry a statement without any solid counter-argument. The accusation of it burries the whataboutism's argument, which could be valid nonetheless.
But the article of the DMA says that the gatekeeper shall not prevent the business user to serve their product using other conditions than those of the gatekeeper's platform. I think that would include Apple's publishing guidelines.
I do not have a lot of experience with commerce but you're supposed to optimize the customer experience. If the customer needs an account to add something to the cart, he might abandon his purchase during the account creation process.
Only some percentage of all potential users will abandon the purchase due to something like this, but your goal is to reduce this percentage as much as possible.
That's why analytics are used to understand which environment leads to the most purchases and prevent users from abandoning the process.
If your account is linked to your Google, Apple or Facebook account that might be the culprit (I think you can see this in yout account settings). You need to check that because the consequences could be way worse than just having access to your Spotify account. You can use HaveIBeenPwned to look for leaks matching your e-mail address or password.
Another possibility is that your browser/OS or spotify client was infected by a token stealer which can automatically steal your access tokens as you log-in after changing the password.
Due to Secure Boot (if it actually enabled since there are some bogous implementations) this can be prevented. If I understand it correctly, LogoFAIL bypasses this security measure and enables loading unsigned code.