🌍 WeSense v1.0.0-alpha.1 shipped.
First public release of a decentralised environmental sensor network built to outlast any single company or government. Readings flow from ESP32s, Meshtastic, Home Assistant and government APIs, through a signed P2P archive layer, to permanent community-hosted storage. CC-BY-4.0 by default.
- No API paywall, no single point of control
https://wesense.earth
https://github.com/wesense-earth/wesense/releases/tag/v1.0.0-alpha.1
We invented the internet specifically to be resilient through decentralisation, then spent the last twenty years cramming the whole thing into three cloud providers and calling it "progress."
Ukraine just reminded us in real-time why single points of failure are a bad idea, yet somehow, we’ll still act shocked the next time one outage takes down half the planet.
This is a subtoot about Microsoft.
Edit: Changed "survive a nuclear war" to "be resilient"
The main question seems to be about our use of LLMs in our development process. Main concern is with liability and ownership with code.
@aeva They can’t:
1. Copilot uses the same connection infra that has died, and Microsoft has been directing staff to use their internal Copilot…. Sooooo that’s a ripperoni in pepperoni for them
2. The SSO connectors for OpenAI and Anthropic are down, so they can’t even auth those agents for use in the cloud environment.
Basically, the AI has abandoned them exactly when they needed it most. This is slapstick comedy of an epic scale.
@pjw try the folks that @jackdaw_ruiz interacts with, and that instance in general.
Proved my old-school tech prowess today:
Asked an engineer to scrape a list of company email addresses off of a website we use internally. After 10 minutes, they were still refining an LLM prompt to do it.
I used devtools to grab the JSON data, copied it into Word, edited out the surrounding array structure, then copied that into Excel to sort alphabetically, deleted the numeric keys. Ta da! Took me about 3 minutes.
I really, really worry that basic computer literacy is nearly dead.
Weirdly, as we checked out of the hotel this morning all signs of the riot-adjacent activities last night except the graffiti had been tidied away. And it’s interesting to note the presence of one tonne sacks of short planks had been prepositioned near all the fires during a public transit strike.
Conclusion: the fires were preplanned, the police response was preplanned, and they were planned by the same people (hint: not the demonstrators).
cool we got a reverse url -> torrent index going. now we need a little crawler to extract url lists from wacz archives by just skimming the zip index and grabbing just enough pieces pull them out, then populating the index becomes automatic.
so coming soon to a #sciop near you, a p2p wayback machine, where a URL can get resolved into a bittorrent-backed web archive. then we federate the sciops. and we have the federated/p2p archive dot org we deserve.
If you have a Windows 11 machine, the update they just pushed sneaks Copilot onto your machine and sets it to run at startup. I just had to uninstall it (again) when I found it running in my system tray after the mandatory reboot.
Neat, the new node:net/promises API looks convenient! In general being able to for await a stream feels clean to me. Also, we have built in Websockets now?!
https://nodejsdesignpatterns.com/blog/whats-new-in-nodejs-27/
@heapwolf SSB was similar to this and I think it did a decent job of preserving social context! I keep getting the urge to recreate it but with indexed B+ trees instead of oplogs for the base data layer so that initial load is actually fast :P
Occult cyberpunk. Yap with me about decentralized systems, wearable computing, and biohacking.