I also love being alive!
Hi. Are you talking about my personal site or vaporware.network ?
Edits to the document are saved as yjs deltas in separate nostr events. 1 second after you stop typing, it saves a new edit. https://github.com/yjs/yjs
That is awesome, thanks!
Lol these jokers can't even make a mobile layout, how are they supposed to make laws?

First im hearing about it. Right up my alley. Will try it when I get home!
Do you mean the Spanish egg dish Tortilla or like the tortillas used to wrap tacos?
Our old house luckily has good a foundation, but the first floor subfloors are fucked. I think it's actually easier to move a house than it is to replace subfloor (while preserving the original floorboards, that is)
Not everything is free. The ~24 hour withdrawal is free. Faster is quite unfree, rev transaction fee.
Are you questioning my will? ;)
We have new stuff. Not much tested yet, so feedback is welcome:
1) Iris Docs — https://docs.iris.to
Proof-of-concept collaborative text editor and simple canvas on Nostr. Recently also added a chat, so might rename to Iris Apps?
https://void.cat/d/Po8kXtpo116x3enNczizPP.webp
2) IrisDB — https://github.com/irislib/irisdb
Extensively used by Iris Docs. Tree-like data structure on Nostr.
Build wikis, marketplace apps, games and other decentralized applications where users can choose whose edits they want to see (e.g. followed users, extended social network or specific group).
Enables science fiction stuff like deleting & unliking posts, or editing a user profile or list of users without risking overwriting the whole thing with an out-of-sync version.
Use a filesystem-like interface to create all kinds of applications on Nostr without having to define obscure event kinds for each purpose.
Has simple & powerful useLocalState and usePublicState hooks for React applications.
3) npm create iris@latest — https://github.com/irislib/iris-docs
A template that quickly gets you started with Nostr & IrisDB web application development. with dev tools and basic components like login, settings or avatar. Built on Iris Docs — remove the parts you don't need. Decentralize everything!
Is the document data persisted in a note? Or is the data centrally hosted and Nostr is used for collaboration control?
Is the doc content itself a note/events? Or is the data centrally hosted and just collaboration is handled by Nostr keys?
At some point, you've got to tell _someone_ *some* IP if you want to connect with them peer to peer. And at the end of the day, nearly all of our packets should be p2p.
Ideally you would just tell the _desired peer_ your IP, but that implies you know theirs, and if you did you wouldn't be in this place to begin with. So you've got to at least trust some kind of gateway/name resolver/discovery node.
One decent solution is for every peer on the network to defacto run a personal proxy in the cloud. The proxy IP is not sensitive, and your connection with it is encrypted and doesn't expose your personal IP. People discover "you" on a gateway by finding your proxy IP, instead of your home IP.
I almost totally agree with this, but there are many important applications, features and protocols that are complex enough that the solo nights-and-weekend warriors cannot make a dent in them.
There's a whole class of problem that needs programmers to get paid - and well.
At least you didn't autopilot-grab-and-drink the cup from yesterday that had some sludge left at the bottom
Broadly: https://vaporware.network - we're bringing to market a purely functional Solid State Interpreter (not unlike urbit) VM that employs orthogonal persistence and public key cryptography identity. On top of this stack we are developing a peer-to-peer open source software market (or rather, market of markets, or darknet of markets, if you prefer).
One of the areas we're exploring right now is Nostr integration, starting probably with trivial-to-run, zero-maintenance personal relays. Our stack gets large file hosting for free out of the box, so each user would act as their own sovereign media host (for Nostr notes - or anything else). You'd also be able to trivially serve yourself your own Nostr client UI (a simple method reduce reliance on centralizing - or spying - clients).
Personally though, and more directly to the point at hand: I'm extremely interested in subjective, contextual, non-global, transitive trust and reputation systems. My previous company was working on a prototype of this on urbit, but the concept is even more well-suited for Nostr.
If you'd like to learn more about the urbit version, here was an overview of that project (the general idea is applicable here too): https://gist.github.com/vcavallo/e008ed60968e9b5c08a9650c712f63bd
I'm very happy to discuss either of these with you here or in DMs!
Don't bogart the public URL

