Drill press

I’d say they love paragraphs, they are paragragh-maxxing

Could someone please transcribe this? I can’t be bothered to read it.

The stats are a sample, there is inheritantly some level of error. Ignore the month to month changes, focus on the longer term trends.

Reset button not working, but power button working is quite odd.

Is it just the once that this happened? Can you reliably trigger it with the car charger? If yes, maybe worth plugging in a monitor while you triggering it and see what happens.

Are the server and chargers close to each other? Some kind of EMP effect? Seems unlikely, but who knows.

Cock wash?!

Careful, you’ll get a hit piece put out on you

Looks like your time machine worked!

Maybe don’t check Wikipedia, some things have changed…

Are you familiar with ReiserFS? Because that’s how you get more ReiserFS’s…

Gnome shell uses JS and CSS (i beleive anyway), and the w11 start menu is supposedly react native, so I think the answer is definitely yes.

That does sound like a good approach. Are you able to share that CI pipeline? I am mostly happy to risk the occasional breakage, nothing is really critical. But something more reliable would probably save me some drama every so often when it does break.

.uk domains are very cheap, $5ish AUD, which is ~2.5usd.

Careful what you wish for, we might end up drowning in <16yo users.

You might, but I bet the majority of people set and forget.

I rely on watchtower to keep things up to date.

You can of course do it manually with plain nginx, it’s just a little more effort. Good luck :)

Pull by digest just ensures that people end up running an ancient version, vulnerabilities and all long after any issues were patched, so that isn’t a one-size-fits-all solution either.

Most projects are well behaved, so pulling latest makes sense, they likely have fixes that you need. In the case of an actually malicious project, the answer is to not run it at all. Huntarr showed their hand, you cannot trust any of their code.

Nginx proxy manager can help you with all of that.

basically want a domain name that you can use to subdomain each service off.

E.g:

https://service1.auth.local/ -> proxies your first service (192.168.1.111:4567)

Https:/service2.auth.local -> proxies to the second (192.168.1.123:9876) And so on.

If you purchase an actual domain name, you can get letencrypt certs via nginx proxy manager, and it all works very smoothly.

Having done some C to rust auto-translation some time ago, it definitely was wildly unsafe. Maybe it’s better now, but there is no reason to assume it’s mostly safe now either. Even recently I did some regular vibe coding to test it out, and it generated some very questionable code.

Even if there is zero “unsafe”, there could be loads of unchecked array accesses, or unwraps causing panics, which while “safe”, will cause crashes.

Fixing unsafe can be a mixed bag, some will be easy, some will require much deeper changes. And without looking at the code, impossible to say which it will be.

I haven’t looked at the code, but the mem safety may be out if the translation just slapped unsafe and transmute everywhere.

And “working code” is often very hard to replace, it can be hard to justify code changes when the original “works just the same”. So, I would expect the weird ported code to live on unless there is a major effort to rewrite it.

https://github.com/DioxusLabs/blitz - This kinda covers the “engine without JS” part, it’s a bit more limited, but also in alpha. It’s part of the dioxus project, they use it for rendering UI on desktop.