"These people are still a part of that https://t.co/S97FQ9bSMG have to understand, most of these people are not ready to be unplugged. And many of them are so inured, so hopelessly dependent on the system, that they will fight to protect it." 2022+
Every time you open Waze, Google gets a live GPS feed of your location. Speed traps, traffic jams, road hazards — convenience, but also surveillance.
I've built an alternative. And it goes beyond just traffic events.
Roadstr: real-time road events on Nostr. Spot a speed camera? Publish a kind-1315 event tagged with a geohash. Other drivers see it instantly. Confirm it's still there with a kind-1316 event.
Just signed events on relays.
**Privacy by Design**
🔒 Ephemeral keys — new keypair per report, no identity linking
🔒 NIP-40 expiration — reports auto-expire (4h for police check speed traps, 30d for potholes)
🔒 Geohash precision — 1km² area, not your exact GPS for queries
🔒 No background tracking — you broadcast only when you choose to report
Roadstr is working today:
🌐 Web client: https://t.co/sjkCHYquGE
📱 Android app available (https://t.co/fO6ioDPK15 or zapstore) - integrates with OSMand
📋 Protocol spec: kinds 1315 + 1316
🔧 Developer guide for integration
We're looking for the first independent client implementations. If you build a Nostr client, Roadstr adds road intelligence in ~200 lines of code.
**Beyond Nostr, beyond road reporting**
The NIP allows transformation into short data packet and back for reporting over MeshCore - local info, over the air and back (so if you hear it through MeshCore, you can broadcast the Nostr event!)
Also - and this is key - there are many more map events that are useful. A dangerous person with a gun. Unsafe zone (natural disaster). When there's something happening around you, you might want to know about it and tell others.
Very early demo. Available now.
Are you a cypherpunk? The Two Privacy Coins Only OGs Know About
Everyone knows about Monero (XMR) and Zcash (ZEC) but what about the other than are not talked about and yet have a solid footing and decent liquidity
→ Zano (ZANO)
→ Pirate Chain (ARRR)
Both have a solid privacy tech. Interestingly, both are related to current privacy coin leaders, XMR and ZEC.
1. Zano
Comes from same roots as Monero.
- Unlike Monero's chain that's mainly used for transfers Zano enables anonymous tokens and services.
- the only decentralized and anonymous stablecoin that currently exists lives on Zano blockchain.
2. Pirate Chain
Is a fork of Zcash (ZEC).
Think ZEC but shielded by default and without any transparrent addresses/transactions.
As surveillance expands, the value of truly private systems changes completely.
That’s why inside Unstoppable wallet you can already:
→ store and swap XMR
→ store and shield ZEC
→ store and swap ZANO
All inside one wallet.
ARRR support is something we’re planning to add soon as well.
The cypherpunk layer of crypto is quietly building and massively underestimated.
Be Unstoppable!
A Stanford professor just gave a public lecture on exactly how GPT, Claude, and LLaMA are built under the hood
no insider access required
just the clearest breakdown of modern LLM architecture I've seen
this lecture reveals the framework professors are paid up to $750K a year to teach
the gap between "I use ChatGPT" and "I understand how it works" is smaller than most people think
the most complete public breakdown of modern LLM architecture I've seen this year
1 buy a computer with lots of RAM
2 download hermes and set it up with local models
3 create a gateway to talk to it privately from any device
4 use https://t.co/YTSL7jsB6W to build a wiki (or multiple wikis) with a local reasoning model
5 use gbrain on top of llm-wiki for the memory retrieval layer using local re-ranker
way better UX than using ChatGPT or Claude apps.
The takeaway from Fable 5 being BANNED by the government: GET GOOD AT LOCAL MODELS SO YOU HAVE 100% CONTROL.
My entire weekend was going to be building my craziest ideas with Fable 5. That's now cancelled.
So instead of building with Fable this weekend, I've decided I'll go deep on local models:
1. Start with the runtime. Download Ollama or LM Studio first. This is the thing that actually runs models on your machine.
2. Match the model to your hardware. A model's size is measured in billions of parameters (7B, 32B, 70B). Bigger is smarter but needs more memory. Rule of thumb: a 7B model runs on almost any laptop, a 32B needs a good Mac with 32GB+ RAM, a 70B needs serious hardware like a DGX Spark or a maxed-out Mac Studio.
3. Know which model for which job. Qwen 3 is the best all-around choice for most tasks. DeepSeek for reasoning and coding. Gemma 4 when you need something tiny that runs on a phone. Llama when you want the biggest community and the most fine-tunes.
4. Quantization. You can shrink a model to run on weaker hardware with barely any quality loss. Look for versions labeled Q4 or Q5. This is how a model that "needs" a server runs on your laptop. Learning this one concept changes everything.
5. Connect it to your agent. Point Hermes or your agent stack at a local model.
6. Context window is your real constraint locally. Cloud models give you huge context for free. Local models make you pay for it in memory. A bigger context window eats RAM fast. Keep your sessions tight and your prompts lean or your machine chokes.
7. Learn to give local models tools. A smaller local model with web search, file access, and code execution beats a giant model with none. The capability gap closes fast when you wire up the right tools. The model is the engine but the tools are the wheels.
8. Fine-tuning is more accessible than you think. You don't need this on day one, but know it exists. You can take an open model and train it on your own data so it gets good at your specific domain.
I'll probably do a breakdown at some point on this @startupideaspod if people are into it.
The lesson from this ban is basically don't build your entire workflow on something that can disappear with a single letter. Own part of your stack. Local models are insurance.
It reminds me when people realized they don't own social media accounts. And then you saw people build email lists etc.
I remember running a startup and my biggest traffic source was organic FB. All of a sudden, algo changed, and I lost 99% of my traffic.
Same sorta moment (but bigger) for AI.
This is a wake up call.