Technically a HTML document can be thought of as a blob that references other blobs. or a JSON file, or XML.
Really anything, that's the fun part about it all just being data. its an application thing and not a protocol thing π
I think I opened a NIP-29 group from a link, I don't remember if I clicked any buttons though
I should probably vibe code an easier NIP-89 app manager so other apps can set this up easier...
opening a #grimoire spellbook from nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez cc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr
https://video.nostr.build/0f2774f0f62a229d657927759b8d8f6e0d5fd72d0537dd5b4beeef6650e3af82.mp4
Awesome, and every other client that supports NIP-89
what are you building?
So this is a custom nostr relay that is specialized for torrent events? why build a custom relay instead of just using strfry?
Signed into flotilla with a browser extension, it immediately bombarded me with NIP-42 auth requests so i figured Id let it sign stuff for 5 minutes....
Then the first thing it does it wipe my NIP-29 groups list... lesson learned.
Why are nostr apps still being built to automatically sign stuff?
Yeah... That's an annoyance, ideally, Blossom Servers would have an FTP-style file management interface and then you would just copy the links with the hash.
I don't have any watches. mine is just #knifepen
Blossoms filenames being a hash is kind of retarded. Like WTF is this?
https://podtards.com/9165a87d3172c1bee5f436b43ae22c2f251fa9371a96cc9caf9b20198b969d2e.mp3
filenames are lost when servers go down and when the file is re-uploaded to another server there is no way to tell if its the original without knowing the original hash
This is whats in my pocket most days (minus the pen)
https://cdn.hzrd149.com/ef211d958d4c2aa8da2b8ba3e438e21c7cf6b90fde7a8d4b06826c63e13b8c20.webp
also the NIP-60 wallet in applesauce should be working now. it might still loose users money but at least it will show the correct balance every time you open the app π¬
https://hzrd149.github.io/applesauce/examples/#wallet/wallet
and made some NIP-29 examples, so maybe those will be useful too https://hzrd149.github.io/applesauce/examples/#group/relay-chat
also the NIP-60 wallet in applesauce should be working now. it might still loose users money but at least it will show the correct balance every time you open the app π¬
https://hzrd149.github.io/applesauce/examples/#wallet/wallet
I was just about to ask about that. every time I try to use the app I'm annoyed by the constant NIP-42 auth requests. it would be awesome to have the same auth system that you implemented in grimoire
I've switched off Spottily to manually downloading and syncing the mp3 files and its so much better.
just yt-dlp for downloading, music brainz for metadata, and syncthing to mirror the mp3 files to all my devices
nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg no NIP-89 event. I cant easily open spellbooks from noStrudel π
This is cool. also testing something to see if Grimoire has a NIP-89 event
nostr:naddr1qvzqqqrc8ypzqla9dawkjc4trc7dgf88trpsq2uxvhmmpkxua607nc5g6a634sv5qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9mhwden5te0veex2mnn9ehx7um5wgcjucm0d5hsqpnnda3kjctvjnyrpc
Also finally wrote some docs on how to cache encrypted content and how to integrate event caching
https://hzrd149.github.io/applesauce/apps/encryption/caching.html
Way too many things added or broken to easily list in a single article. but here are some highlights for the v5 release of applesauce
I've also take some time to update the docs at https://hzrd149.github.io/applesauce/ and created lots more examples π
nostr:naddr1qvzqqqr4gupzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqrtpwpcxcetnv96kxefdwc6sersccd
Basically me right now. glad the Christmas and new years is over and there aren't anymore holidays for a while.
Discipline them...
Honestly not sure though. the API for applesauce isn't very similar to other libraries that the models are used to. so it either takes a large "rules" context for them to understand it. or I have to clean up the API
For applesauce V4 I've found the most success by pointing them at the specific examples in the "examples" folder that I want them to copy. although that means that depending on how much code you give them it will fill up their context window. So I've been doing a lot of cleanup on the API for V5 that will hopefully make it easier for AI models to at least guess what the method names are :)
Do you have a link to the repo? Id like to continue looking into this and maybe find a way to write a BUD for it
Using proxies to optimistically create an observable chain where each step attempts to access the value. it basically resolves the path through the object as if each field returned a Promise and you used `await` at each step
I tend to agree, but the "outbox model" is just for pulling the latest notes from the people you follow
Nothing that I've found. Like I said, the only issue is Docker defaulting the volume to be owned by root.
https://hono.dev/ looks interesting, it's always fun to play with new web frameworks
Depends what browser you're loading it in, unless it's the Tor browser it won't have access to onion URLs. And also it might not be able to connect to http:// connections
Will do, I've got a lot of stuff to fix before the next noStrudel version
Sorry to everyone having issues with #noStrudel I haven't forgot about the app but I've been busy (distracted) with building out the applesauce SDK
Once applesauce has feature parody with noStrudel. then I plan to go through noStrudel and replace all the legacy code with new tested code from applesauce. then in theory there will be 0 bugs...
What's are you fuzz testing?
I guess the domain expired, I'll have to update it or remove it next version
I've added support for expiring DMs, but expiring kind 1s and replies is an interesting idea
I started working on this generic schema that could be used for that: nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcqyz5a04nmem34nh3jd88g5vhv0ww2pu4l6l4xtphyqa9eartnn4u2k5z9a5u
It would be great if you took a look and helped fix the AI bugs.
hmm... I was thinking of using zod because its a fancy new typescript library. but there is merit in having a language agnostic schema
Although it wouldn't work with typescript unless I built a compiler from schema -> zod -> types
I think I saw someone else working on it. nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5?
It was either a JSON schema library or zod, idk. but I have the urge to build my own now
Every time I make a big release of applesauce I get tempted to go back and build more... I really should move on and actually implement the features I've added into noStrudel
On a totally unrelated topic. what do the typescript devs thing about building a library of zod schemas for common event types?
I've been trying to think of how to prevent invalid events from getting to the UI components and causing a crash and I think strong types with validation might help
no, my POC only had paid uploads. never got to the point of trying downloads

