hzrd149's avatar
hzrd149
_@hzrd149.com
npub1ye5p...knpr
JavaScript developer working on some nostr stuff - noStrudel https://nostrudel.ninja - Blossom https://github.com/hzrd149/blossom - Applesauce https://hzrd149.github.io/applesauce
hzrd149's avatar
hzrd149 1 year ago
I'm not jumping on the Follow Packs bandwagon, mostly because I can't think where they would fit in #noStrudel But I did cleanup the existing people lists view Also added NIP-22 comments so you can discuss people lists
hzrd149's avatar
hzrd149 1 year ago
Been working on this for the past few months. I think its stable enough for other developers to start building on and next release of noStrudel is going to be using it as the core View article →
hzrd149's avatar
hzrd149 1 year ago
I setup a temporary instance of morning-glory running on a LNVPS I forgot I bought a few months ago https://vm-217.lnvps.cloud/ It costs 1sat per kB for uploads and all blobs are deleted after 24 hours... Not sure if its any use to you guys but go ahead and try to break it. I don't remember how much storage the VM has so it will probably fill up fast github repo:
hzrd149's avatar
hzrd149 1 year ago
This is great article as a follow up to my rant about DVMs last week and it also proposes some solutions that I think might actually work. View article →
hzrd149's avatar
hzrd149 1 year ago
Next release of #noStrudel is going to have a new layout. It should also make it a little more mobile friendly Old -> New
hzrd149's avatar
hzrd149 1 year ago
@DanConwayDev gitworkshop really needs a quick repo search like GitHub has on the side I use this all the time to quickly open the my repos or the recent repos I've seen (nips, nuts, etc) image
hzrd149's avatar
hzrd149 1 year ago
A rough draft of a BUD-10 for multi-part uploads to blossom servers. not sure if this is a good idea so I'm looking for feedback The biggest issue comes from the fact that blossom relies on the sha256 hash of the whole blob. so there isn't a way to verify that each uploaded chunk is part of a whole until the all the chunks are uploaded. I think this issue can be mitigated slightly if the client includes `x` tags in the auth event for each chunk its uploading. so that the server can verify that each chunk was created by the client. In the case of payments, I think it could be possible for the client to pay for each chunk. although this might require more requests or the server to define an x sats/bytes pricing. Inspiration taken from Thanks to @fiatjaf for making me aware of it