pull down to refresh
Thank you! Yes these topics often have their own posts on SN (eh, sometimes it's how I first hear about them), so it'd probably make sense to link to these discussions for the SN version of the issue. Thanks for doing the work here!
Unofficial Bounties of 1,000 sats for person who has the link to one of the original writeups dictating a configuration implementing wireguard VPN + reverse-proxy (they didn't call it that, but that's what it is. Sounds cool, because it is cool). #revengeofthenerds
I don't know if that's what you have in mind, but I've used this guide from Warren Togami in the past. Seems unmaintained though.
Thank you! Good to be back!
How is that you changed the versioning to S03E01? Shouldn't be this issue #73?
With this long break I figured it could make sense to restart the versioning. But it's a bit more wordy and ultimately people don't care that much, so maybe I should have stuck with #73.
I'd also like to have the number convey what week this issue is for to make it easier to find a specific week in archives, but once again it quickly becomes a bit wordy.
Hey @nps! Congrats on the launch, I've been playing a bit with MDK in Vercel today and it's going great so far.
The only thing a bit confusing at first, at least to me, was the webhook. I wanted to test things locally first, but of course that didn't work because the node was not reachable on a public endpoint. Do you have any plans to simplify this first step, for example with a proxy between localhost and a temporary domain hosted by MDK?
Also am I correct in assuming that it's fine to run two instances at the same time with the same seed (one local, one deployment), since on payment reception the MDK infrastructure will just reach out to the deployed instance? But then how does the local instance knows the payment succeeded? I tried and it does notice the payment arrived.
Thanks!
Small update: we now have multiple news sources publishing on the subject, which all seem to stem from new directives issued by the interior minister to its services on how to handle devices running GrapheneOS (or, I assume, derivatives):
- a (bad) article from France Info (public broadcasting service), which is basically the same as Le Parisien's one
- a (bad, but a little bit less) report
On the other side of the, we have balanced, nuanced articles from tech media:
Thanks for your comment! I wrote the part on Satring last week so it might have aged a bit since then 😅 I saw the domain verification/restore feature with the .well-known, pretty cool.
Do you have any early usage (by agents) stats? Or is it still too early?