Nostr song lyrics, guitar tabs, and sheet music. Because the existing sites that host that stuff always try to push their apps. Can basically just be a wiki style note.

Upgraded an old 5th Gen iPod video. New case, bigger battery, and 256GB SSD

Had 0 intentions of running this morning. Out late at a show last night. Woke up and saw it'd be 95 degrees today. Managed to get out and do my run! #proofofwork #running

@PABLOF7z short PR to fix the text wrapping issue on wikifreedia

GitHub

fix: text wrapping in EventContent by ebrakke · Pull Request #31 · pablof7z/wiki

Currently wiki entries are unreadable on mobile (and a lot of web clients as well) as the container forces a scroll. This PR removes the flex class...

First (rough) pass at a #climbing NIP https://wikifreedia.xyz/crimpstr-nip/borrakkor@nostrplebs.com I opted for a new kind for these events as to not clutter existing wiki applications, though we could easily use the 30818 kind and just utilize a type and c tag to get climbing related things. I think the biggest unlock here is incorporating the geohash of an area / route into the name. This will ensure that we can disambiguate between climbs of the same name. It also has the added benefit of hierarchical ordering built in, so you can easily group climbs together without having to enforce a strict hierarchy like MP does. Using curation sets for tick lists, and for area oganizations (e.g. ordered climbs from left to right) might also be sufficient. My goal here is not enforce any ordering on the notes themselves, but let people group things together however they see fit. @PABLOF7z @Rylan

A little demo / POC of #crimpstr Using @PABLOF7z's wiki nip, and some data that I just happened to find somewhere, this could be a great decentralized repository of climbing knowledge. Indexing events using meilisearch for great discoverability (something mountain project sucks at) @Rylan #climbing

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.

Here's the source code for the obsidian nostr wiki plugin. Super WIP, but feel free to clone it, fork it, make it better. Currently it will treat front matter as tags to add to the published note, and it will strip front matter out of the content so it displays nicely.

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.

This is why we need #crimpstr @PABLOF7z @Rylan #climbing

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!