From 0deb1db0caadfb8178bd0141a990b6b2ae7c1631 Mon Sep 17 00:00:00 2001 From: Vlad Stan Date: Tue, 24 Oct 2023 15:33:47 +0300 Subject: [PATCH] Update 107.md --- 107.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/107.md b/107.md index 3c814b6..0df1339 100644 --- a/107.md +++ b/107.md @@ -8,9 +8,8 @@ Nostr Internet of Things ## Rationale -The terms/conditions of IoT software/hardware is horrible. A user should be able to message a light or heating and ask it to turn on/off. Nostr gives the simple, permissionless development environment IoT needs. +The terms/conditions of IoT software/hardware is horrible. A user should be able to message a light or heating system and ask it to turn on/off. Nostr gives the simple, permissionless development environment IoT needs. -All communication happens over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). ## Terms @@ -31,10 +30,13 @@ The `device` can also push data such as sensor readings and updates. ## Events -A `device` or a `user` can publish these event kinds: -| Kind | | Description | NIP | -|---------|------------------|---------------------------------------------------------------------------------------------------------------|-----------------------------------------| -| `4 ` | `direct_message` | Communicate between two `devices` or between a `device` and a `user`.
The messages must be a JSON following the structures defined In this NIP. | [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md) | +A `device` can publish any of the events described in [NIP-91 Event Kinds](https://github.com/nostr-protocol/nips/blob/iot/91.md#event-kinds). +A `user` can publish these event kinds: + +| Kind | | Description | NIP | +|--------|----------|-------------------------------|-----------------------------------------------------------------------------------------| +| `8000` | `intent` | Trigger an action on a device | [NIP-91 Event Kinds](https://github.com/nostr-protocol/nips/blob/iot/91.md#event-kinds) | + ### Messages JSON messages that represent different actions or states can be exchanged between two or more `devices` or between `users` and `devices`.