Oddbean new post about | logout
 Hey, I'm new to #nostr and looking to connect with people who are into #OpenSource,  #decentralization, and maybe #IoT fans!

I make open source smart thermostats that don't snitch on you. So of you know anyone that would like a project like this, tell me about them so I can follow them. ❤️ 
 This is something I want to learn more about. Followed.  
 Welcome 👋🏻🧡👙 
 #siamstr
#rightshift 
 #plebchain 
 #plebchain #plebs
Show some love to a newcomer 
nostr:nevent1qqstm2hzkp7sn0c3tx84h9yqvvmmtst7ursf9yphu5hdt4gumuxqlaspz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzqgm0kp4du9pwmf3w6j8kzqzfttyfx759amku20d86pmpsu5nlxzyqvzqqqqqqyg6ycdt 
 Welcome🫂 
 I want to integrate lnd rest to home assistant - can you build a ha integration stub? Nice little project 😁 
 Followed 
 Welcome. 
I found you on Mastodon.  
 Welcome! You’ve definitely come to the right place. 🫂🤙 
 Howdy @Hestia Hacker 🤠

What do you think of the IOT NIP 

https://github.com/nostr-protocol/nips/pull/814 
 It seems stalled, any idea why? 
 @Ben Arc

whats next for IoT NIP? 
 Making a tutorial video today/tomorrow. Was just slammed on other stuff 
 I suspect this is not going to be a popular reply, but...

Why use nostr for IoT?

I don't see how it is better than existing standards like MQTT or Matter. It also basically means having to run a nostr relay, because the idea of broadcasting every IoT event to a remote server seems terible for privacy, reliability, performance... basically everything.

What would help this NIP out a lot is to clearly explain what problem it is trying to solve and lay out a example setup that makes it seem like it is not burdonsome on either users or developers.

If I were to take a stab at it, it might go something like this:

The IoT ecosystem has been plagued by a lack of interoperability. Some apps use bluetooth, others ise wifi, and still others use Z-Wave, Zigbee or LoRa. Furthermore, the component sometimes go over HTTP, and other times MQTT. In both cases traffic is unauthenticated, unencrypted and doesn't have integrity in the cryptographic sense.

This NIP intends to chip away at these problems by providing cryptographic authenticity and confidentiality without having to mess around with getting TLS certs from a publicly trusted CA, nor setting up a private CA.

A nostr relay would run on the hub of the IoT infrastructure, such as OpenHAB or Home Assistant. This is similar to the HTTP or MQTT servers run on existing solutions. Other processes could listen on other transports (BT, zigbee, LoRa, etc.) and send the nostr events to the relay. From there, events could be picked up and acted upon by any devices or clients.

There are four main advantages of this over MQTT:
1. Standardized events, instead of every implementation using different topics
2. Standardized data formats, instead of some implementations choosing JSON while others have more topics and plain text
3. Nostr events are signed, ensuring they ate authentic
4. Nostr events are encrypted with the public key of the intended destination.

(And then go on to describe the different kinds of events)

Note: I don't know if what I said about nostr or the NIP is technically accurate. I'm new here. But hopefully my idea of how to explain what it is solving and how is now clear. 
 Three excellent topics all in one post! 
 👋 
 Welcome to the #nostr family 🫂 
 Welcome, will definitely check this out 🤙 
 👾💜 
 Share your work please  
 HestiaPi.com

Code is at github.com/HestiaPi

You can build one yourself or if you want to just buy one I have already built, you can get them at my online store: https://www.tindie.com/stores/eternalsunshine/ 
 This is awesome and Welcome!