Erik
borrakkor@nostrplebs.com
npub1rach...4atg
I like to build web things. Currently hacking with JavaScript on nostr things
What if everyone just published all of their random notes about topics from obsidian or other note taking apps to nostr, and then used wikifreedia or similar to browse it all.
Not worrying about it being a Wikipedia level article (though some could), but really just reading though everyone's research or thoughts on a personal topic.
They can centralize around categories or common names.
A bit like urban dictionary, but for any topic.
GitHub
GitHub - ebrakke/obsidian-nostr-wiki
Contribute to ebrakke/obsidian-nostr-wiki development by creating an account on GitHub.
Surprisingly easy to write an obsidian plugin that publishes wiki events on nostr.
More to come at some point! This should help with maintaining something like crimpstr.
@PABLOF7z
Nice one from @Zach Weissmueller
Working on a go implementation of a #blossom server for an idea I'm trying to flesh out.
https://git.brakke.cc/borrakkor/community-stack/src/branch/main/blossom
Go is great! Go is fun. Go makes me realize that spending all my time writing JavaScript is insane.
I also used Alpine JS in the frontend to add a little bit of state and functionality to sign the auth events. It was nice, a lot like vue and angularJS, and no build steps.
Let's say I wanted to make an application built on nostr, and I want to utilizes nostr auth.
To take some burden off more normie users, I was thinking the service could store an ncrypt for the user.
From the users perspective, they just have to remember a password like any other site. But under the hood, the ncrypt can be sent down an stored in local storage (if missing). And then the user can unlock it with the password to sign events client side.
I'm trying to think from a security perspective if there's any harm in the server storing the ncrypt. It's basically like storing a hashed password, but if the key is ever leaked, then someone with access to the DB could reveal the nsec.
Tonight's brisket 
Htmx + pocket base could be a good solution for a self hosted community stack with a plugin architecture
After listening to the Citadel dispatch with hzrd and Stewart, it got my brain spinning.
Maybe you can build a "gated community" on top of nostr, with all different kinds of plugins based on NIPs
And then at any point, community members can fork the entire stack to create a new community.
Could be useful for communities that require moderation, but the underlying data ends up being totally forkable.
Members could pay dues for hosting costs of the CDN / relay / DB. You could even customize the login experience to something more traditional (like user just creates a password which will be used to generate an ncrypt) and the community can store that. 
Built some new lower cabinets
#woodworking #diy
Paying with Bitcoin using the coinbase managed pay with crypto product.
"Pay with Bitcoin" 
Coming up on a 24 hour fast. Starting to get easier. Next one will be 48!
X (formerly Twitter)
Moshe Schwartz (@YWNReporter) on X
A solid quick breakdown of the apparent multiple power failures on the 'Dali' ahead of impact with the Francis Scott Key Bridge in Baltimore, MD.
...
Being able to lock ecash to a relays npub would be awesome.
Relays could charge tiny fees per note processed, and know in an instant that the ecash is valid and has not been double spent.
Fantastic. I'm glad you've made the bare bones typescript server as well. I was going down that path for the cashu file server, but now I may just fork your implementation and add some ecash capabilities on top of it!
I think in a year from now, all zaps on nostr will be p2pk ecash.