one of the best moments in cashu nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft did we end up settling on a NIP spec for both our implementations? I figure it wouldn't hurt to write a small npm package for this since it was pretty easy to do client side
something closer to the Automated Response System would be a good start. I'd imagine building the Query API could be difficult and wouldn't really be that useful since most of the use-cases I have in mind would only deal with nostr relays
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr you didn't mention that this has an automatically connect via Tor feature to it as well as the clearnet
this is how i want all my nostr apps to work
fyi, this is the nsite directory onion: http://q457mvdt5smqj726m4lsqxxdyx7r3v7gufzt46zbkop6mkghpnr7z3qd.onion/
oh yeah... nsite.lol is setup with a tor domain, so any app deployed there can be accessed over tor
I could, however the https certificate wouldn't work. Unfortunately its all about https 😞
Hell yeah, I can't wait to see it
Headless is probably the most useful. I'd like to be able to build simple bots using it so it doesn't need and API or a dashboard ui
nostr:npub1jcympy69pht7ptan39se4nd09e4q66qhey649uu3rczm2zh88c7s0n2890 on your latest episode you guys where talking about the new passport prime from nostr:npub1s0vtkgej33n7ec4d7ycxmwt78up8hpfa30d0yfksrshq7t82mchqynpq6j and mentioned building a nostr hardware signer app for the passport
As the developer of the only nostr app to integrate the original nostr-signing-device https://github.com/lnbits/nostr-signing-device I REALLY want to see this built and would be willing to help out in any way I can
I don't know rust and I generally only work with JavaScript in the web browser. But if it was possible to make it compatible with the web serial API then I would be more than happy to integrate it into #noStrudel
For everyone who is curious its mentioned around the 1 hour mark
noStrudel is awesome, next.nostrudel is gooder! But the version deployed on nsite is FUCKING AMAZING! nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr thank you!! 💜
next.nostrudel.ninja is now no more, long live nsite 😀
Just a heads up I rugged (removed) the next.nostrudel.ninja deployment. The hosting provider I was using (fleek) switch their login system to crypto wallets and I'm not able to login with my email anymore so I've stopped using them
If you want the daily changes you can find them on https://nsite.lol
New version of #noStrudel with some new features and a lot of cleanup under the hood
Most of this version was cleaning up the core of the app and building out the applesauce library
https://hzrd149.github.io/applesauce/
You can run it using docker using docker with "docker run --rm -p 8080:80 ghcr.io/hzrd149/nostrudel:0.42.0" or the update should be available on nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct and nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll shortly
nostr:naddr1qvzqqqr4gupzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcqp3hx7um5wf6kgetv956ry6rmhwr
mirrored the stream to nostr 😀
nostr:naddr1qvzqqqrkvupzqcdevslary76xzmmfgtxre7kv24cquhjnnvl08fs52mfl9e6a2pnqyt8wumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6tcqqa68xupnx5unjfl99vs
I've been thinking about testing this for a while but nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev appearance on the survival podcast is a great opportunity to test
I created a nostr live stream that re-uses the HLS stream url from rumble
https://rumble.com/v5zytkw-guy-swann-and-jack-spirko-on-bitcoin-in-2025-epi-3599.html
nostr:naddr1qvzqqqrkvupzqcdevslary76xzmmfgtxre7kv24cquhjnnvl08fs52mfl9e6a2pnqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qqrhgumsxv6njwgz8d27p
That would be awesome, I'm sure there is enough to talk about to fill a whole podcast episode
Finally! I've been saying since the early days of nostr that RSS and nostr are natural allies. Last spring nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr discussed this at length with nostr:npub19ha7tju4teqp3dmwv4p28wrcy9zd6h6hxkg5mwvjrlfycweazpkse2q0fa and me on a Bowls With Buds:
https://fountain.fm/episode/E0p20TEm9KEc2oFd3kJR
Never understood the resistance from both camps to one another, but I'm so excited for the potential that will come from the mind-meld. It's been inevitable the whole time. 🔥🔥🔥
Its difficult to discuss this over text, If you like I would be down to setup a voice call to chat. I've been getting more into V4V music and I think your the person who can answer some of my questions and I can answer your nostr questions 😀
yes, you could use a friends server. but I would guess thats much more difficult than publishing a nostr event
yes, however the difference is as a user I can use other users relays. I don't have to have my own relay to make my events (data) available. whereas for RSS I need to have FTP access to my server. or a friends server that is configured with my domain
One problem podcasting has, and the Podcast Index is no different, is for it to be widely searchable, a directory is needed. That's what the Podcast Index is. They upload the database every Saturday for anyone that wants to use it instead of relying on the Index, but you'll always be 1-7 days behind the Index. The reality is though, most PC2.0 apps rely on getting feed info from the Index. One thing nostr may be good for is having several copies of the Index available so if one server goes down, the others are available as a back up. I don't know enough about nostr to say how that would work or if it would, but if any of you nostriches are up to the challenge, having the Index across several relays would be huge.
Here's the latest upload of the database. https://public.podcastindex.org/podcastindex_feeds.db.tgz
There's probably a few ways of going about this. for publishing the database file you could use NIP-94 k:1063 events to build a directory of the database files https://github.com/nostr-protocol/nips/blob/master/94.md
You could also publish the file using NIP-35 and https://dtan.xyz to publish the file as a torrent
Then it would be cool to build a simple self hostable podcast index server that would listen for the events and automatically download the database and update
RSS has solved this (not saying their isn't a nostr solution as well).
https://lnbeats.com/album/287e27fa-adc5-4762-956f-0282bba5ed77
Here's a playlist nostr:npub15z2javq62eh2xpms7yew0uzqsk4dr7t3q3dq4903uuxdyw2ca3kstx6q95 put together of every song he's ever played on Lightning Thrashes. I'm currently working on the ability for you to save your playlists as an RSS feed to share with anyone. If you want create your own playlists, Sovereign Feeds is what Sir Libre used to build his feed and then he hosted it on his own server.
The issue with saving a playlist as an RSS feed is that I have to have a domain, and a server, and a https certificate for that server, and...
Where as if it was a nostr event it could just be signed and published to a relay
neither option is better UX for new users. but for existing users (and myself) its much easier to create and manage nostr events then it is to manage RSS feeds
oh, cool. followed and added you to the list
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr heads up in commits since 0b0aa6fc234e6a9c78826ce2e69adcf1c5f210c9 the input window is not parsing #hashtags correctly #bugreport
will be fixed next comment, I'm reworking how events are created :)
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft why is olas creating "+1" reactions instead of the standard "+" reactions?
also its using a "K" tag instead of the standard lowercase "k" tag
Do you want faster downloads on Zapstore, that can run in the background?
Maybe also full screen images?
How about showing non-updatable apps (certificate mismatch issues) at a glance in your updates screen, without having to install to find out?
Well, you can have it now.
That and a bunch more fixes on Zapstore 0.1.7 just released 🚀
Update on Zapstore or install here: https://zapstore.dev/download
Just finished a the first working version of the applesauce-loaders package
https://github.com/hzrd149/applesauce/tree/master/packages/loaders
The documentation is very sparse at the moment but the package exports a class called `ReplaceableLoader` that can be used to dynamically load any replaceable event (1xxxx, and 3xxxx) from any relay in a efficient manor.
In theory it also respects the relays limits because it uses rx-nostr under the hood to make the requests
Its all built on rxjs and the loader is simply a rxjs Subject that takes an AddressPointer as an input and outputs events it loads from relays
The cool part was figuring out how to make it load from the cache relays first, then the remote relays, and finally the fallback "lookup" relays
I ended up using a generator function, first time I've ever used one in javascript 😀
I'm really proud of this and how well it works, but I would appreciate any feedback from other nostr devs interested. I promise ill try to write better docs next week so the code is easier to read
You can see a working example of it over on https://blossomservers.com/reviews I doesn't look like much, its just loading profiles but it proves its working 😀
noStrudel uses the NIP-51 bookmark list kind 10003 and its been working pretty well. I just haven't tested it cross app though
if the publicDomain field isn't set it will default to using the protocol + domain that the request was made on
It has the flaws of Merkle DAGs but it does not use merkle trees, its basically just a recreation of torrent V1 files on top of nostr and blossom servers
I'm not trying to fix anything with this, just building an app to stress test blossom servers. and I was curious if it could be done in a really simple way
The applesauce documentation is slowly coming toggether https://hzrd149.github.io/applesauce/introduction/getting-started.html
I forgot how long it takes to write docs... this was one day of work
One of my favorite V4V Christmas songs https://lnbeats.com/album/acddbb03-064b-5098-87ca-9b146beb12e8/aHR0cHM6Ly9hYmxlYW5kdGhld29sZi5jb20vc3RhdGljL21lZGlhL211c2ljLzA2X09uZUNocmlzdG1hcy5tcDM
lumilumi has almost as many features as #noStrudel, the UI is a little hard on the eyes but I really like it
nostr:naddr1qqxnzdejxu6nqd35xsmrvvfjqgsgfvxyd2mfntp4avk29pj8pwz7pqwmyzrummmrjv3rdsuhg9mc9agrqsqqql8kqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueq56ad2q
The DVM requests usually include a list of relays the client wants to use to communicate. although I'm guessing the primal DVMs are only listening on the primal relay and my client doesn't know that
Example request
next version of #noStrudel is going to have a hacky gif search. and when I say hacky I mean it barley works because its built using 1063 events and NIP-50 search
although It should get better as more 1063 events are published and as search relays get better
If you need a better gif search you should use https://gifbuddy.lol/ which will download the gif from tenor and publish a 1063 event to nostr so its available to everyone else
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn I love this I wish more apps did this so I didn't get spammed with decryption requests
ah of course. I thought this was maybe the first time you weren't going to build a feature into amethyst 😆
I have this exact model of drone. its pretty fun but only gets about 5 minutes of flight time
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0 I found a "bug" between the blossom cli and cherry-server
When I enable the mime type filter on the server to only accept images and I use the blossom cli to upload a .jpg image. the server returns a 415 error
I think this might be due to the blossom cli always sending the content-type header to "application/octet-stream"?
project links:
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub16jdfqgazrkapk0yrqm9rdxlnys7ck39c7zmdzxtxqlmmpxg04r0sd733sv nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 PR for making the file extension required in the "url" field https://github.com/hzrd149/blossom/pull/38
Client can and probably will use the "url" field returned from the /upload endpoint when composing kind 1 notes. although the GET /
If my main server cdn.hzrd149.com went down or the image was removed from it. clients could lookup my preferred list of blossom servers (kind 10063 event) and start going down the list asking each one for the exact same blob (without needing to know how the server works)
1. 
2. 
Thats the point of requiring the "GET /