yeah, im done. i just looked at the forecasted bill. i feel like i've been shitcoining and just watched the rug get pulled. nostr:nevent1qvzqqqqqqypzq0mhp4ja8fmy48zuk5p6uy37vtk8tx9dqdwcxm32sy8nsaa8gkeyqyghwumn8ghj7mn0wd68ytnhd9hx2tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcqyr6ps490amm0ux3t3rjvwyny8ft5qf3jlzlwxjs95rqqv9kdngul5xnnek6

GM, time to dent the world and maybe make a few holes in it, while we are at it! 😂☕️🫂🔥🚀 nostr:nevent1qqspdp3senv0wz33ppcwh7wqpl37q0hz2myrlxvznz4lyue3yg32mqspr9mhxue69uhkuurjdau8jtntwf5hxarpwpekktnvwc636vzj

How does this differ from mempool?

Not fully accurate yet but here is a bitcoin address searcher I vibe coded. https://v0-new-project-m8f5wjdxzz5.vercel.app/

GM🫡☕️☕️☕️

GM🫡☕️

Ok. That's it. I'm officially a misanthrope. Nuke it all. We've strayed too far from God's light.

How do you handle window organization?

Who woulda thunk that all i needed to do was to add a 32'' monitor and then like magic... no more mess 🤗

Does it necessarily have to be a 30040/41 combination? They will eventually be able to publish wiki pages, too right, or a 30040 that contains a wiki page or another 30040. So they need to be able to define which kind each section should have, with 30040/30041 simply the default. I'm just thinking that it might make sense to go full modularity in the design, from the start. Also probably need to put a help text above the editing field, that explains where you will define a split. Like, what happens with the content in the preamble? Does it go into a summary tag or does it get a preamble 30041? Is the header where you type in stuff that will end up in optional tags? Which tags will you process and how do they need to type them in? Can they see that information in processed form in the preview?

I'd like some design feedback on Alexandria. I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events. My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes. Question: How would you like to preview your published events? I see two options: 1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events. 2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events. I'd love to hear people's thoughts! #asknostr #alexandria #gitcitadel #nostrdev #nostrdesign

GM🫡☕️☕️☕️

GM! Current state of Nostr in a nutshell 🐶🐾🫡☕️☕️☕️☕️ nostr:note1wnc0wqz6he5dqan58u2v9uccr53fgljtdxpj58653l3mdlz20vaq7l3vg7