There's a huge difference between the reasons for such a ban. This wasn't a movie with political content antagonist to Lebanon government. This ban is probably to make a statement for both outside and inside the country. To show how normalized the violence against them is widespread in our media industry. But you can read in this action whatever you like... Sure...
Ps. Have you seen Waltz with Bashir? Hell of an animated movie.
You seem contradictory. Are you sure you're not homophobic? Not trying to bait. No need to answer me at all. Just calling for your own self reflection.
It's been always the same. Backend, server logic, database... dynamic content; on one hand. JavaScript runs on the browser for almost anything, sometimes for dynamic content. But it's not tied. You could have an in-browser button with a counter for the numbers of times it was pressed (that's actually an entry-level programmer exercise) and that's a static site. If you saved the counter value to the server (e.g. database) then it's not static anymore.
Author of that list reached out devs here, https://github.com/ente-io/ente/issues/983
Browsers could list more than Brave.
You're privileged (no offense!). For some people, a bad economy means losing their jobs, turning homeless, etc. critical hits from which it's difficult to recover.
There's this list which might be of your interest https://codeberg.org/jonatasbaldin/delightful-sustainable-vps
I heard some people would do 'domain fronting' to mask packages as going to a web that was unmetered (e.g. Google or the providers own site). But I never tried it, only heard of the trick when it was too old (counter back measures finally catch up). But you can try.. there it's, that rabbit hole... GL&HF!
That's practical, but not so sound, advice. IANAL, yet... I remember when Julia lang was gaining traction that many R lang programmers wanted to port their favorite packages. If they were to look at the R sources (under GPL) to write the Julia version to be released under MIT license, they would be violating the GPL. Or there was a risk, at least. Of course, this case is different because the first and original version is not GPL. But this came to mind. Anyway, I suppose that it all boils down to how much OP feels like their employer (boss or anyone with power in the company) will be a son-of-a-cop and really come forward to court against him... I mean, that's in the first place. Then, comes the legal advice, as to how much of a case can be made, and what do we expect a judge would see it...
Check this out, is super fun! https://github.com/skeeto/endlessh
Depending on which database you have, backup strategy may vary. One lovely approach for SQLite is litestream + backblaze. For a small server like yourself it will fit in the free tier ;)
Some GPLv2 projects monetize by selling: support, extension via custom features, or simply the permission for a commercial use. This is possible, and it's what I called "the legalese package". Imagine ffmpeg being able to charge every year any amount they want to the biggest clients, like GAFAM. Yet you're still able to use it non commercially... To be fair, there're some middle uses, that get the disadvantage of having to break the license or ask for permission. For example, if you create anything with ffmpeg, then as an indie dev you'd need to launch your product breaking the license or paying them... But even so, situation is manageable (e.g. ffmpeg could spare you and/ or give a 1 year permission to small businesses)