nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt is working on recurring support with highlighter (and others are too). We're getting there!
Only real when shared.
nostr:nevent1qqstvr9s0j4gaqnhlwtwkqnnn7e2ad5mvfwaqrumpdgchr2wafmfscqpzpmhxue69uhkummnw3ezumt0d5hsygzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvpsgqqqqqqsmx980m
NOBODY IS
nostr:nevent1qqs9amjzzkl33s4czewnfwltucvnzq53fvym3pht472xfwgv06qatxspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyqgzrjyjz4y04zdtknx8apng5w5de6awpfxry0l74atsgwyr945exqcyqqqqqqgm8jjpa
NEXT LEVEL
nostr:nevent1qqsqpzvlvmfyq9y8dp36x2xvgmad5486c4ct4ecdkmdxgtr9dxl5r2qppemhxue69uhkummn9ekx7mp0qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqpcxkqqf
In a couple of years from now, Germany will have the incredibly uncomfortable realization that the guy who is to blame for this colossal blunder is no other than the guy in the mirror.
https://media.tenor.com/LW40JVVI7uQAAAAM/stupid-berserk.gif
We'll bring it back. And make it better.
nostr:nevent1qqs2dqklkwrmnwpnnx454ydllyyqkwjawqgqgufy86sufc483a26wscpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsygru5ek5ze43da22z6rgryd6r33cd2tkvf85vd8n39keke6q5wyv5vpsgqqqqqqs7595ul
It just dawned on me that we could easily build something that would allow certain npubs to post in the name of another npub, solving the "company account" problem in terms of key rollover.
Anyone working on that? #asknostr
How it could work: give npub1 npub2 & npub3 permission to post in company's name. Use replaceable events signed by company to keep a list of permissioned npubs. No need to share company's nsec to post. Permission to post might be revoked at any time.
Example: Vanessa, Will, and the Damus intern might want to post as the Damus account, but the intern shouldn't necessarily have access to the Damus nsec.
Do we have clients that support this already?
I see. That's a shame.
Well, as long as that isn't solved it will be very hard to convince any non-single-person entities to use nostr. One guy leaves your company/team/org & your nsec is forever rekt.
Side question, feel free to ignore: how do you deal with permissions in the spreadsheet thing you built nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug?
A small bakery might be such a company, and I don't see the bakery at the corner running a server for this. Just saying.
Appreciate your thoughts, though.
Things take time indeed.
nostr:nevent1qqswlj5sjz8tldtnpcfckcw368nv5vevnsldwytvy27qz6k90l9axcgppemhxue69uhkummn9ekx7mp0qgsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3grqsqqqqqpj0z4m8
Oddbean new post about login | logout
Notes by Gigi | export