nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 will you be my co-author? ππ€ #docstr
also figma has a built-in feature to generate code.
gmgmgmgmgmgmgm π€©ππ«
thanks for your feedback. just added more explicit relays. it should be ok now. I can see your doc.
#docstr is now supporting NIP-07 (browser extension) π«‘π
I've created a document and delegated it to nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac so now he's my co-author π€
check it out ππ
exactly! π―π―π―
I decided to use "don't trust; verify!" approach π
everyone can publish the same document but it's up to the client to accept the right one.
kinda but not exactly π
nostr:note1ndywsgvf622p93zdry2zdau0pqactpautfuk6zmsagvu32avy4gqqz8dg2
and it's not the same kind (I chose 32323) because of a new specific tag "D"
generally the same idea (two people working on a single doc) but it's a bit different in the saving flow. here we don't need to wait for the owner to accept the changes or merge it to the original one. in this approach the owner delegates the document to others and they can act upon the owner. and the owner is still able to revoke the access.
another awesome feedback by @`Karnage ` π«ππ«‘
1. great! thanks!
2. sure thing! will make it full screen.
3. it's just the very first working version π
4. technically yes we're able to do so.
5. I'm working on the extension, don't put your real keys there (and anywhere π)
6. OTHER STUFF ππ«
don't put your real keys there (and anywhere π).
just use the "Generate New Key" button, for testing purposes -- for now.
I'm working on extension.
no, it has a different flow.
it doesn't need any "fork", "pull request", and "merge".
people are working on the same document in real-time and every verified party can simply hit the save button. how's that? π
this is the very first working version and doesn't support extensions yet. I'm working on it.
the client processes everything and it also verifies changes.