It’s referring to both. The recompiler links to the Zelda project and basically tells you “if you want to haven an example how to.proceed/what to implement yourself after the recompilation finished, you can use the Zelda project as an example”.

Well, usually those re-compilers or transpilers just translate the binary to some sort of intermediate language and then any backend should be able to compile it for your target system. So, in theory those handheld could be targeted. Problem with this project is that it’s not just “start transpiler, load rom, click go and your port is ready”. It’s more like "ok, here’s your game logic. Now implement the rest (or use several other projects and duct tape their libraries together to get what you want).

Nah, it just marks your question as duplicate.

I mean, the hosting company would be the likely target then and they’d probably lock your account and switch off the server. Depending on your nationality and that of the hoster, at least.

Do you know the term “trust thermocline”?

Basically it described a problem with the boiling the frog technique. There’s a point for every user at which they’re fed up with the bullshit, lose all trust in you(r company) and are hard to impossible to get back as a customer. Every customer leaving has a little unnoticeable effect on you, but with time there will be so many people that you lost that all your tactics to lock your users in will fail.

I read it as “no, we won’t use your data for advertising, but collect it anyways. If you ever dare to stop paying, we’ll retroactively process this data, too”

I use Arch btw

Yeah, basically you have three options:

1. Create and train your own LLM. This is hard and needs a huge amount of training data, hardware,…
2. Use one of the available models, e.g. GPT-4. Give it a special prompt with instructions and a pile of data to get fine tuned with. That’s way easier, but you need good training data and it’s still a medium to hard task.
3. Do variant 2, but don’t fine-tune the model and just provide a system prompt.

Aperture Science.
We do what we must
Because we can.
For the good of all of us.
Except the ones who are dead.

The EU at least tries to regulate AI with the AI Act

It’s not a catch all, but some things are banned from using AI and others will need an assessment before going live. Some other will not need an assessment, but serious incidents need to be reported

…but it’s got electrolytes!

Uhmmm based on my behavior before I left, the engagement is probably “click the three dots, hit report, select spam and block user”. That worked at least for a short while before they got rid of that feature…

Relevant xkcd

It’s not the most detailed thing, but I just use a free account on cron-job.org to send a head request every two minutes to a few services that are reachable from the internet (either just their homepage or some ping endpoint in the API) and then used the status page functionality to have a simple second status page on a third party server.

You can do a bit more on their paid tier, but so far I didn’t need that.

On the other hand, you could try if a free tier/cheap small vps on one of the many cloud providers is sufficient for an uptime Kuma installation. Just don’t use the same cloud provider as all other of your services run in.

Thanks! Here’s the tax:

Have you read The Egg by Andy Weir?

It looks like you changed the position of your mouse cursor. Would you like to reboot to apply these changes?

And Xbox three to Xbox 359?

They basically did. I bet they just used an ORM in the backed and then pointed the API endpoint to the user entity without filtering the fields. This results in a dump of the user table (although row by row indexed by users instead of a full dump)

Hmmmm I didn’t know that, every comment that I read, didn’t mention this fact. I’m running my own Searxng instance and Meta engines can be quite powerful, especially when you can adjust them a bit and filter out what you consider “spam” results (e.g. pinterest)