I’m not buying anything, as I do not need anything.
Software developer interested into security and sustainability.
I’m not buying anything, as I do not need anything.
I understand your project’s constraints. I meant that you could try compiling and running the mongoose server linked against the packed filesystem in your development machine.
It seems to me that the problem would be caused by Mongoose packing, rather than vite/rollup’s build, since it seems to run fine on your development environment.
PS: Could you try reproducing the Problem using a mongoose server running on your development machine, or even better: on a Dockerfile? Then you could share a minimal example that could help to further diagnose the issue.
Maybe you should consider a server & client architecture to use the right tool for the right job on each platform.
Try disabling hardware acceleration
But the aerosols would also amplify the green house effect right?
Files could be decrypted by the end user. The OS itself could remain unencrypted.
You could try organic maps.
We growing wiser, or are we just growing tall?
Nginx 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.
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.
I think it helps to cool the drink and inot only satisfactory.
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.
Then it may be a token stealer.
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.
You wouldn’t download a car‽