nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

update nip-110: allow any license

Browse Source
This commit is contained in:
degenrocket 2023-11-05 23:38:32 +00:00
parent ad166ff255
commit 51814492cc
No known key found for this signature in database
GPG Key ID: 19896421F4AE9EA4
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
110.md
View File

@ -1,26 +1,26 @@
NIP-110
=======
MIT License
License tag
-----------
`draft` `optional` `author:degenrocket`
This NIP defines how to add an MIT license to Nostr events.
This NIP defines how to add licenses to Nostr events.
### Problem
### Problems
Currently, the Nostr ecosystem is growing in a very friendly environment, but once the environment will change to hostile, relays and clients can face legal responsibilities for distributing the copyright-protected content.
Currently, the Nostr ecosystem is growing in a very friendly environment, but once the environment will change to hostile, relays and clients can face legal responsibilities for distributing the copyright-protected content. At the moment of writing, a user who signs a Nostr event doesn't give an explicit permission for his content to be distributed without any restriction.
At the moment of writing, a user who signs a Nostr event doesn't give an explicit permission for his content to be distributed without any restriction.
Another problem is that some users want to use different licenses for different content like text and media files.
### Solution
The easiest solution for this problem is to add an MIT license to each signed event in accordance with the [SPASM](https://github.com/degenrocket/spasm) specification.
The easiest solution for this problem is to add a license to each signed event in accordance with the [SPASM](https://github.com/degenrocket/spasm) specification.
Then relays and clients can check whether events have an MIT license and choose whether to display/distribute such events or not.
Then relays and clients can check whether events have an MIT license or any other license and choose whether to display/distribute such events or not.
While adding a dedicated license field (`"license":"MIT"`) would be ideal, the easiest solution with backwards-compatibility is to add a license as a tag.
While adding a dedicated license field (e.g., `"license":"MIT"`) would be ideal, the easiest solution with backwards-compatibility is to add a license as a tag.
```js
tags: [