Who will teach the robots to dream, if not the philosophers?
Please recommend Nostr clients built for chat rooms with equivalent functions to Matrix/Elements, Discord or Slack.
Ideally an application not a website.
Yes, the aim of the mesh is decentralisation of the physical layer. Phones, home routers, etc would form dynamic multilateral connections to one another.
Good point about bitcoin and broadcast not needing routing. Indeed routing is probably the major challenge.
I fear with Starlink we are moving in the opposite direction… one ISP for everyone.
Server 1 has an encrypted boot drive
Server 2 has the decryption key
Server 1 boot loader can authenticate to the remote server 2 and retrieve the key.
Q) What is the best thing server 2 can be?
An HSM probably but with a sensible budget?
A password manager server?
Some sort of enclave?
Something better?
What would you do there? nostr:note1na2neyu5ygxwcv4gyuzrs4jvvvtmy7v4jcav6p9xz4j3l5mqlp3q5k8a6x
Great idea. If I could be there I’d use the time to work on…
- long range mesh networking (LTE direct)
- Highly available redundant LN node infra (working on this anyway)
- Re-decentralising email and e2e encrypted by default (NIP-mail?)
- fiat/btc dex (helping @jayberg)
- ASIC boilers using high temp chips
- Slick PoS NFC UX tooling for btc
Not sure what I’d do in the second month yet :)
I used to post like this.
I still do.
But I used to too.
Gives people the feeling the money is in their hand, or is their hand, but of course the money is the banks and they are scanning you each time.
They would be far less impressed if it was their local bank teller recognising them as they walked in to ask for cash each morning, but is in fact the same dynamic.
Catch-all email is so good for this.
Views on private DNS?
Standard DNS is unencrypted and for most people used as a cloud service. Thus every URL (specifically, domain name) sought is sent first to your DNS host so it may be resolved to an IP address. This gives your DNS provider and any man-in-the-middle, a live and timestamped historical log of every service you visit.
DNS-over-TLS (DoT) is an encrypted version of the same thing. This takes away the eavesdropping risk of a man-in-the-middle.
DNS-over-HTTPS (DoH) is the same as DoT but transports over HTTPS.
DoH offers better obfuscation by hiding in a larger anonset (HTTPS traffic), and as it uses port 443 it can't be admin blocked without also blocking web traffic (HTTPS).
However neither DoT nor DoH protect from Man-In-The-Backdoor attacks - in other words, the DNS provider, their regulators, hackers and rogue employees still see all.
ObliviousDNS (ODoH)is a nice-ish upgrade. It splits DNS resolution services into a two party service:
User sets up an HTTPS channel with a Target DNS provider.
User send packets for that target *via* a proxy service as a router.
- As a router, the proxy knows the user's IP address, but not the contents of the packet.
- The target can decrypt the HTTPs packet but does not know from where it came.
Not bad! However this dissociation degrades back to plain DoH if the proxy and target collaborate.
Most companies currently supporting ObliviousDoH are large US tech firms and so of course are in direct reach of the US intelligence agencies. They also know who to call for every historical request they've processed together to complete the picture.
So what would be better? Could we take inspiration from Tor or maybe Dandelion routing in Bitcoin?
Perhaps we should just use Tor?
One option which improves all of the above it to run your own DNS server locally. This will still need to talk to other, remote, untrusted DNS servers to source its lookup table info, but importantly it will cache it locally, limiting the amount of metadata sent externally.
I don't think Unbound (a local DNS cache) can be configured to randomly make its requests of a long list of DNS relays - which is a shame as that would help shard the metadata footprint of your IP address.
An idea for a work around of ODoH's faults could be to run your own proxy server in a compute cloud, ideally a provider which doesn't take ID info (pay with bitcoin). Connect to that via SSH tunnel, and have it send the ODoH packets out to target services. It could also very frequently change its own IP address so the target does not realise requests are coming from the same source.
What do you think? What's the best practical means to achieve DNS privacy? 
Data requests of any kind are a cost to the server. If the service is free there will be caps, if it’s paid for there will be higher caps.
I assume Elon was trying to work a sustainable fee model into his server, but was being sidestepped by screen scrapers (a capping loophole), and so decided to bring the caps down hard on the free accounts.
The same realities will be true for relays won’t they?
The beast wallets are hot wallets
Roses are red,
Violets are blue
But flowers aren’t for you,
So don’t you think insects,
Appreciate beauty too? https://nostr.build/i/f449011178162a81d0321c2ad2e6b9934d9a97950d1ecd3a16081a5d49df1dc5.webp
1st May -> 1st June
(please excuse the unhelpful axis labelling)
I dont see a pattern here. Do you?
P.S. These are all log scale price axis (Y axis) 
Instead of starting the graph from 1st Jan, let's start from 1st May:
We get a very broad dispersion it seems. Let’s zoom into just the month of May... 
Sell in May and go away?
Here are the past 10 years of BTCUSD price time series overlaid on one another, to help us identify whether there is any discernible pattern in May each year.
Orange vertical line = 1st May
Hmm, not sure.
Next note in 🧵for another view... 
If you don't know what a catch-all email configuration is, please look it up or ask me here and I will explain.
It is cyber life changing.
Thanks to @TakensTheorem for answering this:
“Transient local negentropy.” nostr:note16tnrqzh5mv8mk0wtgv76s9r8n3x3fvrdzu2frx506guzpzs28xfstgzg8e
What’s the word for the emergent order of the natural universe we are part of which stands adjacent to the entropy or emergent chaos of the same universe?