Thank you for your suggestion, I will revise it!

We’d love to hear feedback on this. It’s a proof of concept but I really want to 1) offer agents within an inbox (and integrate to” “dispatch” work to agents running in services like n8n or retool), and 2) offer email inboxes for agents themselves just like coworkers.

Lots of cool stuff to build here, and one day soon expand to the full office suite for ai agents.

The specific problem prxy solves is not at the network level, but at the application level, especially for tools that don't have built-in proxy settings.

With WireGuard's AllowedIPs, you route all traffic for a certain IP range through the tunnel. My use case was different: I wanted a specific browser extension to connect to my homelab, while my main browser traffic to the public internet remained on my local network. The extension only has a field for a URL, not for proxy settings.

While an SSH tunnel can achieve a similar result, I find prxy more convenient for this specific workflow because:

- It automatically rewrites the Host header, which is crucial when your homelab service sits behind a reverse proxy (like Traefik or Nginx). - It's a simple, declarative command designed for this one purpose, making it easy to script or use in a container.

So, in short: prxy is a user-space tool for application-specific tunneling when the app itself is not proxy-aware.

This does not really answer your question but there just isn't a good answer given most VPS providers can live-snapshot and live-migrate nodes despite not making that a service. If something is in memory it's under their control regardless of any magical memory encryption implementation providers claim to use.

Use something you control vs. something managed. In other words do not use a VPS and instead send small throw-away servers to low-end colocation sites. Seal the servers by filling them with black epoxy and pre-configure them to be low-power and thus low-heat and "plug-and-play" so that you can just ship them to the colo, they rack mount and it just turns on, gets DHCP information and "just works". Disable all logging and run everything in ram when it boots. Physically remove all solder from all ports except the one ethernet port you wish to DHCP from and sever the board traces. Use a custom BIOS that removes all JTAG debugging and out of band management. Have a DNS query in cron that makes an obscure request to an "all clear" zone. If that DNS entry vanishes the box assumes duress and zeros out ram and storage. When it fails tell them to trash it. Do not send them a replacement as they may have destroyed it trying to get your data. Just let that account fade away. Bonus if you can put the box on the internet without any accounts or business relationships.

None of this is my idea or a new idea. This is not too different than how Akamai CDN devices worked in shared datacenters minus the black epoxy. The black epoxy was used in an early satellite TV decoding box in the 1980's that people eventually learned to drill in the right spots to get free premium channels and porn before people obtained media from the internet. Many decoders were destroyed in this learning process. VideoCipher II has quite a history. Spies and prisoners hide servers in crawl spaces and manage to get them connected to the internet all the time.

not really for analysis but I built a tool that auto-generates some SEO metatags and it has a really thorough checklist to go through, along with linking to useful tools. check it out:

https://seo-4-devs.netlify.app

And when you get divorced, you’ll rediscover yourself and never change for anyone again. You’ll ask yourself why you changed and gave up activities you enjoyed while picking up activities you dislike.

Well, the first thought is, why wouldn't it happen again?

And if it did happen once I had servers up, then I would have a problem.

Regarding the question, a little bit, but only a little bit, was lost by it.

I do not normally keep a phone number, and AWS require a phone number, to confirm identity via SMS, when opening an account. I bought a cheap phone and SIM, to receive that SMS, about 30 USD.

Seems to me that he did / does want to buy Twitter (not because of free speech or whatever, but as a rich guy vanity project), but then the stock market crashed and now the price he agreed to is way too high so he's trying to weasel out of it or weasel the price down. Either way he's just being a weasel.

Oh could you give it a try now? I just woke up and got around to fixing some of the scaling issues - it's not perfect but at least it's only failing 5% of queries when I load-tested with locust. Will get around to better fixes later!