There is no such thing as easy or hard.

Give it a try, fuck it up, and give it a try again. Try not to fuck it up in the same way as the first time. Repeat until it works - it will work eventually.

It took me about 6 hours and 3 disk re-formats my first time. I was particularly bad at it. I barely knew what a disk was, nevermind a partition.

Actually I’m still not sure what a partition is.

You’ll do fine :)

I strongly recommend the NAT loopback route over attempting split-horizon dns.

At what point does a collection of microservices become a monolith that uses http instead of a bus 🤔

As “down”, I hereby grant maculata retroactive permission to make the above joke; and formally proclaim that I found said joke to be at least somewhat amusing

Helix + vim => Helim => Helium?

Vim + helix => velix / vimix / vix / velimix?

We could call it … WebAssembly! And now it’s a C compilation target, which means we can run Node.js in the browser, to get a javascript runtime :)

I’ve been zipping things all day. Because it’s only one blob in the container, and then you can use website_run_from_package, which is just about the only way to get azure functions stood up via infra-as-code.

But whatever unzip thing they use sure isn’t the linux default, because it doesn’t support symlinks. And pnpm uses almost exclusively symlinks, to point to its central package store, so re-installing doesn’t take 8 years like it does with npm.

But that’s fine, because zip will follow symlinks and bake the actual files in, in place - which is pretty slick. But then azure functions package resolver can’t seem to figure out what the hell is going on, because it’s still putting dependencies in node_modules/.pnpm.

So we pass —shamefully-hoist, which is a great name for a flag, which puts all the things at the top level of node_modules, and now zip works, and azure works - but each dependency also comes with its own node_modules, with another symlink to a package that’s already at the top level. So it works, but it’s 10x bigger than it needs to be - 6.4 MB instead of 668 KB.

Fortunately we can use our build script to populate a .npmrc file, and set node-linker to hoisted, at which point pnpm will mimic npm with no symlinks at all - small, efficient, and dumb enough that the azure functions runtime can figure out how to deal with it.

It took me 4 hours to debug this mess.

All that to say, yes, a weighted blanket would be downright delightful right now, but please keep the zip files away from me

Tailscale might be the best bet at this point. It will manage the wireguard mesh for you, and use nat holepunching for handshaking instead of needing listening ports.

At least outlook can right click for spellcheck. Wait, actually it can’t do that.

At least you can download your email attachments to a folder? Wait actually you can’t do that either.

At least the 15-minute meeting warnings still pop up consistently? Oh. Oh no.

“Are you sure you want to post this comment? Would you like to upload to sharepoint and send a link instead?”

No outlook I would not like that, I would never like that

Is my file in onedrive? Or on disk? Or is it in sharepoint? Or it could be in a teams chat - but isn’t that just sharepoint? I sent it to Tom also, but it was already in sharepoint because I had sent it to Jim, so it re-named it to something else. Where in sharepoint are my teams files? Or the teams files others have sent me? Is this actually an attachment on my email or is it a “shared link” in disguise?

I’m not sure what’s real anymore!

I love i2p. I wish it had more adoption / was easier to use.

I have not heard spiritbox, but I have heard that they are similar to Reliqa, who I absolutely love

Love these guys! They really helped me out one time, they can handle anything related to