![](https://lemm.ee/pictrs/image/855d97d2-c00d-4cc2-8a74-461501c69b2d.webp)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
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.
Software developer interested into security and sustainability.
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
Files could be decrypted by the end user. The OS itself could remain unencrypted.
You could try organic maps.
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.
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.
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.
It was already like this in Europe when I began to use Spotify in 2015. I do not hate it because the app’s free tier is already unusable to me due to the adverts.
Is yours working? Just tried it and apparently the patch prevents you from logging in. If it does, which version are you using?
deleted by creator
Currently namecheap, but I was pretty mad to see that API access (for ACME DNS record auth, which I need to prevent downtime) was not available due to my yearly plan being too cheap (?!). You need to spend at least 50$ per months or have at least 20 domains for no good reason.
The best solution seems to acquire the domain using namecheap and then transfer name servers to a better service.
But you can set a tab width instead so any developer editing the code can adjust the indentation width to his liking, without changing the actual files contents and having to worry about setting the editor up to insert the right amount of spaces.
Well, one could argue that our brain is a glorified tape recorder.
Maybe the app uses a WebView for login which itself includes a webpage with the tracker. It would be possible that the page’s content and trackers change without any change in the app.
You wouldn’t download a car‽