Adam / Adam Nowotny is on Nostr

Code Removal Specialist. Adventurer. Motorcyclist. Citizen of No Man's Land.

Decentralization. Privacy. Open Source. Linux.

Building https://orangelab.space/ - private infrastructure on consumer hardware based on K3s, Tailscale, Pulumi and Longhorn.

Last Notes

2026-10-01 12:55:48 UTC

- reply

Got it working with HA Connect ZBT-2. It acts as either Thread or ZigBee so if you want both types, better to get two. The components in IoT stack handle all the config, you just need to tell it where to find the ZBT and use openthread:requireNodeLabel to force it onto the box that has the device attached. Matter should be locked to a box with Bluetooth so you can provision devices.
Works great! 😁

2026-10-01 12:48:26 UTC

Good morning Berlin!
https://npub1wnwy80yqtx5fjjkzwskpuu95x37vnsgrl4u75fuhxhzcjztjjegskuecjr.blossom.band/d6fe20118c4ce18da5595373f6cc95c12772f61fe29f6b64ca652c4ae2c15045.jpg

2026-09-29 13:34:03 UTC

OrangeLab 0.7.0 released!
This one brings OpenID Connect authentication using PocketID for apps that support it. That means passkey instead of passwords and multiple accounts. As a bonus you get a homepage with list of apps available.
IoT stack now has components to support ZigBee/Thread devices including WiFi/Bluetooth provisioning (OpenThread, Matter) and cameras (Frigate). All local without need to any Google/Apple/Amazon border router or sending your data anywhere outside of your network.
Use Forgejo and Zot to store your repos and docker images. All images used in the cluster are automatically cached in case there any issues with upstream.
https://github.com/OrangeLab-space/orange-lab/releases/tag/v0.7.0
https://blossom.primal.net/fa89adf8f3a7f38a88d9cc44cbc61d87c2198f1f742fb11a2dc29d606988f493.png

2026-09-03 23:49:12 UTC

https://blossom.primal.net/a36a0cc6bad905aae2541615359d904740f7cb67db8cd15a32434f48f649b659.jpg

2026-04-15 10:56:06 UTC

- reply

Does FIPS already handle public connections? I noticed in the docs NAT is not supported yet. Does it mean that I just need to expose the ports to create geographically distributed mesh for now?

2026-02-27 04:33:44 UTC

- reply

BIP-110 is one example but there are many use cases for using custom images, like when you build your own from scratch. By default OrangeLab runs standard version of Knots (or Core), not the custom one.
One might argue that promoting protocol change to increase OPRETURN from storing hashes to storing data is shitforking 😉
Node runners have an incentive to keep things light on resources, both storage and bandwidth. It's a matter of negotiating how far the validation rules should go. In the end it's up to node operators to decide what a valid block is. You're welcome to run any image and version, I'm just making it easier to do regardless of what you decide.