triskal on Nostr: Public read relay, but only members can write to it. Publish all news articles and ...
Public read relay, but only members can write to it.
Publish all news articles and events as long-form text, and nip-52 calendar events, respectively.
DMs for private comms between org staff and members.
Biggest problem: org-owned accounts and integrating into existing identity system. As much as we like to say that Nostr is the internet-native identity system, in order for existing large orgs to adopt, there HAS to be a way to log in with trad OAuth or ADFS or something and have it as Nostr Connect signing device.
Published at
2024-06-22 15:40:37Event JSON
{
"id": "51b43858ecbe51070cf538ebf8ad9b6cf35da756477283bed10a35db3c4c44ad",
"pubkey": "fb1366abd5e4c92a8a950791bc72d51bde291a83555cb2c629a92fedd78068ac",
"created_at": 1719063637,
"kind": 1,
"tags": [
[
"e",
"166fde4df8b7a327b9d2cbdd96fb53ca2be0e7a9f1c23a0abbad843d7e011d81",
"",
"root"
],
[
"p",
"969e6a28ee5214cb0296ee69cbdce4f43229124a78b1043d85df31e5636d0f1f"
]
],
"content": "Public read relay, but only members can write to it. \n\nPublish all news articles and events as long-form text, and nip-52 calendar events, respectively. \n\nDMs for private comms between org staff and members. \n\nBiggest problem: org-owned accounts and integrating into existing identity system. As much as we like to say that Nostr is the internet-native identity system, in order for existing large orgs to adopt, there HAS to be a way to log in with trad OAuth or ADFS or something and have it as Nostr Connect signing device.",
"sig": "9af0d5796ded295abf32497c732f82b14522cb8be808ba8cca265d30dfd0c146d699e52967ac95c11d6635be60e9cafe8c496394d7b2eddb627399370c5209cc"
}
