noStrudel would benefit from a product owner, someone to focus on user features and bugs and force me to finish them and fix the bugs instead of building cool new stuff realizing I'm just a developer and its hard to keep myself focused on improving the small things in the app

Finally caught up on all the PRs and issues in the blossom repo. sorry to everyone who opened them but I've been somewhat ignoring blossom stuff. I've mostly been focused on nostr things because in my mind blossom is "done" and working. there are probably a few things that should be fixed ( the /list endpoint, multi-part uploads, chunking?, negentrapy sync? ) but none of those things are pressing or causing pain for servers or clients right now. Don't get me wrong we still need tons more tools for users, server administrators, clients, etc to use and manage blossom blobs. but my initial goal is complete, that is uploading arbitrary small files in nostr and ensuring they can be verified and found again when taken down.

BUD-07 cashu and lightning payments is finally merged into the blossom spec

GitHub

blossom/buds/07.md at master · hzrd149/blossom

Blobs stored simply on mediaservers. Contribute to hzrd149/blossom development by creating an account on GitHub.

Sorry it took so long, but hopefully this can serve as a launching off point for everyone who wants to build paid storage servers

@hodlbod thoughts on removing the DVM and WOT type feeds in your NIP-FE?

GitHub

Feeds by staab · Pull Request #1554 · nostr-protocol/nips

Adds custom feeds that can (mostly) compile to filters, for content-addressable, user-customizable feeds, useful for clients with bandwidth limitat...

I've been thinking about what it would take to make my own implementation of it in applesauce and those two types are the only thing that wouldn't translate well. DVM type because most DVMs don't speak the same language anymore and WOT type because applesauce has no concept of a WOT score between 0 and 1

Zappable photography is my favorite Nostr feature View quoted note →

@fiatjaf why is my LMDB database for my groups-relay (

GitHub

GitHub - max21dev/groups-relay: A NIP-29 Group Chat Relay

A NIP-29 Group Chat Relay. Contribute to max21dev/groups-relay development by creating an account on GitHub.

) 275 GB when it only has 540 events in it? I used

GitHub

GitHub - PowerDNS/lmdbnav: A terminal UI to inspect LMDB database files

A terminal UI to inspect LMDB database files. Contribute to PowerDNS/lmdbnav development by creating an account on GitHub.

and cant find whats taking up all the space

SnipSnip - Discover, share and collaborate on code snippets

Share and discover code snippets via Nostr NIP-95

still broken, cant publish my cibe coded scripts 😞

Built a simple NIP-53 live stream viewer in 300 lines of code. not super impressive just another example app added to applesauce

Applesauce Examples

This is the secret to using nostr View quoted note →

View quoted note →