florian

This could actually work. Some ideas were already discussed since SEC01 but this is the first time we have a comprehensive concept. 👏 1. I like the idea of only having commits on NOSTR and putting the metadata on blossom. The versioning we get through the commits would even allow to build a "timemachine" like backup solution. 2. The storage requirements seem to be pretty hefty. Let me know if I understood this correctly: Let's take 400 files, 2MB each: - 800MB (3091 chunks) + erasure coding (167%) = 1333MB (5152 chunks). Then we need to add 400 inodes (265KB padded) = 100MB So we have 1433MB in total (5552 chunks) that we upload to 5 servers, resulting in storage of 7165 MB. This might still be a good tradeoff for the privacy and decentralization gained, but needs to be considered in storage costs and upload times. 3. It's important that cleanup and deletion work well. In case of lost keys it would be good to be able to clean off all orphaned blobs from blossom servers. Expiration or storage limits based on payments might also help.

Video experience on the web looks great!

last month as an employee, then NOSTR dev and freelance work, much to do but take it slow.

Claude Code with superpowers is crazy good... love the brainstorming mode especially. https://github.com/obra/superpowers

Heard nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnvv9hxgqpq9ppwxjrqckwl4n2a7j960fjsvhn8vrggcd0h092nmq7zcgcskjfs4yl4uy for the first time yesterday in the nostr:nprofile1qyt8wumn8ghj7cnfw33k76twv4ezuum0vd5kzmqpp4mhxue69uhkummn9ekx7mqqyqv5fekglky2nny5svgdukhwpzr0f8putd5lj67m09qpm4qaw7zn567296q live stream ... amazing music. Have to dig through his catalog now. https://fountain.fm/album/3CVdQeJLXcQwKoCxa7CN