fsmv

I built a reverse proxy server for this kind of usecase specifically. I have a chroot launcher with a simple config file and the reverse proxy is auto configured over RPC and automatically acts as a CA root so internal communication is HTTPS. You can also set the API key as an env var and just run your binary on the command line for testing and it will auto configure and be available on your URL with https.

https://github.com/fsmv/daemon/

It's a bad time for me to be mentioning it because I have a major update that's not quite ready to release that changes some client APIs and makes the whole thing much nicer with fully automatic lets encrypt. I haven't had the space to work on it for a while unfortunately.

Cool so you stole my data and now you're bragging about it?

Just use adb. You can do adb wifi on device. You don't have to distribute a signed apk just sign it fresh on device.

Google writes articles like these every week and hangs them in the bathroom. It's meant to be a quick one page tip thing. That's why the example isn't super realistic, it has to be short.

There's a link with more info at the top. I'm not sure why this one in particular made it to the front page of HN.

It's worse than parroting advice that's not applicable. It tells you what you told it to tell you. It's very easy to get it to reinforce your negative feelings. That's how the psychosis stuff happens, it amplifies what you put into it.

Then we will never know if mars once had life that's different from earth life

It is preinstalled on steam deck

SpaceX is a success despite Elon. Maybe setting an extremely lofty goal helped somewhat but Gwynne Shotwell and all the actual engineers at SpaceX deserve the credit for their success.

I actually really strongly prefer 0 being identical to unset. If you have an unset state then you have to check if the field is unset every time you use it. Using 0 allows you to make all of your code "just work" when you pass 0 to it so you don't need to check at all.

It's like how in go most structs don't have a constructor, they just use the 0 value.

Also oneof is made that way so that it is backwards compatible to add a new field and make it a oneof with an existing field. Not everything needs to be pure functional programming.

Black holes can have charge but a charged black hole would attract ions of the opposite charge strongly and would quickly neutralize. So it would be quite difficult to get a non-negligible charge on a black hole.

It's the same sort of thing, parts obsolescence. The world around you changes and the interfaces you used to interact with the world may not exist anymore. Your dependencies may have been abandoned and have gone through their own bitrot.

I think the best defence is to choose a platform that has longevity, like x86 Linux, and then seriously limit dependencies beyond the platform to the point of maybe not having any extra dependencies.

The problem is eventually platforms change too. The longest lasting platform for software ever created is x86 + BIOS which lasted from 1981 to 2020 when Intel officially deprecated BIOS.

Implying they have actually read the Bible

It still doesn't solve the account migration issue though right? If you move to a different instance your old instance still has to redirect.

How do people find you on mastodon if your instance isn't in your username anyway?

A good example of defence against this is go maps randomize iteration order just so that people don't rely on it being consistent.

They are downloading and archiving the pages that the links point to

This problem is solved by gofmt because it automatically aligns with spaces after the tab so humans don't mess up the whitespace

Yeah I just saw in the bug they're finally making progress on fixing this, exciting! I edited in the link if you didn't see.

It is very difficult to avoid putting strings on the heap in go. I used the built in escape analysis tools and made sure I only use a constant amount of memory in the loop in my short https://github.com/fsmv/in.go progress bar program.

The biggest problem is any string you pass as an argument to the fmt functions is moved onto the heap because interface{} is always counted as escaped from the stack (https://github.com/golang/go/issues/8618).

I think an LLM is a bit too high level for this game or maybe it just would need a lengthy prompt to explain the game.

If you used word2vec directly it's the exact right thing to play this game with. Those embeddings exist in an LLM but it's trained to respond like text found online not play this game.

This all made sense until your conclusion. I don't see how there is any basis to say we will magically solve these fundamental issues.

They would merge and produce a black hole with the sum of their momentums

Because nothing can ever leave the event horizon black holes are essentially perfectly sticky.

It worked for me https://g.co/gemini/share/df19382adf97

If you assume all AI detractors haven't tried it enough then you're the one building a straw man

Hi I write in assembly for fun. Definitely not paid for that though.

They memorize the answers not the process to arrive at answers

An interview with the Bazzite maintainer https://youtu.be/XgabGSI82M0

[deleted]

It's the opposite of that. The straightforward easy tasks are the boring ones. You solve the major problems first and then it's not fun to do the boring work of making it presentable.

Go has never been in heavy use at Google

Cool platforms list. Why stop at 486 if it already supports so many platforms? I suppose 32 bit is the main limiting factor but you should at least be able to do 386 right?