Any suggestions to replace NextJS when you only use static export (no SSR)?

This sounds awesome but reading the comments it sounds not quite there yet?

Right now I use an AppleTV with Kodi installed via developer account. Unfortunately, Kodi on AppleTV is not well supported so it crashes a ton. I'm not much of an Apple dev. After much gnashing of teeth I managed to get a from source build running so I could maybe look into why it crashes and contribute but I've never debugged an AppleTV app and even trying to switch to using the simulator which I suspect is better for debugging, I couldn't figure it out.

But, quite often I just wish to get some other small box for Kodi. Except I don't want 2 boxes, one for Kodi and one for other proprietary apps (Crunchyroll, Twitch, Netflix, ...)

Any suggestions?

There are still branches, but they aren't named by default. You give them names with "bookmarks", which you can push to remote git repositories as branches.

This lets you work on things without having to worry about giving it a name. This turns out to be pretty helpful when you're experimenting — just "jj new <revision>" and start editing. If it turns out to be something you want to share, "jj bookmark create <name>" and then you can push it. (You can also push without giving it a name, in which case you'll get a git branch with a name based off of the change id.)

Change IDs stay constant with each change, so you use those as a type of branch name when switching between the features you're working on.

Is parsing untrusted images inherently problematic?

If I open my (untrusted) downloads folder using Gnome Files and it displays (and therefore parses) the contained images, is that a security issue I should be concerned about?

(I would have assumed that (e.g.) Javascript in PDFs could be problematic, but not a simple preview.)

Hmm. My take is the casino structured its business to comply, not to evade interest. Further, I don't see how Cloudflare benefits by taking on the risk to charge more to help a customer avoid scrutiny. More like: they know it's a humming business and want a piece.

How in the world would we enforce this?

I mean you do the request from within the user's browser (their IP address).

So for example, they filter out 5 products, and from the javascript in the browser you perform the request for those 5 products, and then show the user which ones are available. It could also send the data back to your server. Of course you still have to be careful with the number of requests, but it would allow you to get more data without getting flagged.