I've run into a really interesting privacy vs accuracy problem that's certainly not new but is nonetheless very challenging to solve.
I may wind up having to UX-ify PGP to solve it. I need a pseudononymous way to sign events. No way around it. NOSTR could work, but the network is pretty young, I am not 100% confident it can meet my needs.
Bummer: 1 month delay. Maybe more.
I'm confident it's solvable, maybe not perfectly, but it can be established and then improved
I just thought of this problem, which in retrospect seems very obvious, so I'm going to sit in my pain and think of solutions.
Cubby
rorshock@nostrplebs.com
npub19s23...daw5
Bitcoiner since 2017, erstwhile systems designer and R&D nerd, building freedom tech for :-].
Notes (13)
I may write a state of the union over the weekend that will detail current runway and a bunch of other considerations for my company, :-].
We’re at a crossroads—I can work on this for another 1-2 years, but that’s going to deplete most/all of my money. I’d prefer not to do that, but I’m also willing to do that.
The main issue I’ll address is that I have to build Pipes. Build cost is going to be around $10k in materials and the time cost is significantly higher (but it’s my time). With Pipes, everything gets easier.
I might start working on it this weekend since I am currently stuck in bed due to severe nerve pain/damage that’s left me practically unable to walk. I’m churning on it. If you want to talk Pipes or anything else, hmu. I basically can’t get out of bed.
Kind of a funny thing:
I tried to prompt in an ostrich emoji for Hash, but it doesn’t seem like Unicode has one. Instead, it found the closest thing: a flamingo.
Even better, all my sites are hosted on the .pink TLD, and if any bird is like a pink ostrich, it’s the flamingo.
Fun opportunity to maybe make a proposal to Unicode to add an ostrich emoji too.
All of this was accomplished today, except I need to do a little more work to make reply chains more user friendly.
Can the devs you work with do a full stack, deployed, and tested NOSTR integration in a day?
While I’d prefer to get a bunch of users and build to their taste, that’ll take time. So if you have any leads on jobs, clients, or investors who might want to work with somebody like me, hit me up.
nostr:note1ltryr8exlwum68mnsz50nvx7pjud8umep27lhy4axv6vn2ujh2cq8e79qk
Now that I can publish directly from Hash.Pink, this is very exciting. I'll tell you a bit more about the NOSTR integrations I've built today. Some are currently live.
NSEC signup/login. It's instant, presuming you have Alby/etc on your web browser on desktop. Boom, you're in. This is also very nice as it maintains your privacy pretty well, and when I enable BTC payments this week, it's about as private as I can make it this quickly. In case you missed my other post, basically in the last 24 hours I've decided to do a marketing push and work on getting users, so I'm building things as I can.
Second, you can set up a PIN if you want to compose in Hash and publish directly to NOSTR. You'll be required to enter it to "sign" every time you want to publish from Hash to NOSTR. This will help prevent you from accidentally publishing private journal entries.
If you're not interested in the compose feature within Hash, you can still import all of the posts associated with your npub. Once imported, they'll appear on your Entries page in a special tab where you can review them (and some comments) as you like. These entries are also eligible for Insights and Topics pages which help train the model on how you think. Since Hash is primarily a simple journalling app with deep insight capabilities, it's not in your face, but it is kind of fun to see how your thinking changes over time. This feature is being built out and made more intelligent, so for now you can think of it more as a demo.
While Hash is primarily a desktop app, I'm also implementing NIP-46 currently so you'll be able to use Hash in Chrome/Safari on your phone and then pair to your local key manager (e.g. Amber).
I guess when you type it all out it doesn't sound like that much work, but I've been at it for maybe 10 hours straight? There's a fair amount of UI work too, but it's all-inclusive. I likely forgot a few small things I added along the way, so consider these highlights.
I've done light testing, so I am sure some things are janky and there will likely be bugs discovered later. Have fun when you use it!
And just to test, I want to see what happens when I try to send styled text to NOSTR...
<b>bold
</b><i>italics
</i><u>underline</u>
Third attempt at publishing from Hash to NOSTR. Testing!
Theoretically, soon the first NOSTR events should be getting published from Hash… so if you see more test notes coming in, that’s what’s up.
I probably have another 3-6 hours of work before I move into testing, but so far the NOSTR integration is grooving along.
This is a test note.
I'm running into a persistent issue getting notes to return from relays and it's a bit unclear what's going on.
I'll continue working on it, but so far I've spent 5 hours trying to fetch them and that's longer than I expected.
Sneak preview.


This is cooking, feeling super positively even if Bitcoin is doing terribly. At some point the selling has to stop, sentiment and RSI hasn’t been this terrible since the lows in March/April.
That being said, I also wouldn’t be surprised if we see below $70k shortly. $58k beckons.
nostr:note1ltryr8exlwum68mnsz50nvx7pjud8umep27lhy4axv6vn2ujh2cq8e79qk
NOSTR<>Hash integration coming soon.
Proposed initial scope of work:
Log in with NOSTR (NIP-07 support)
Import notes from npub
Fetch notes and replies from npub, reduce relay data loss by keeping reply chains in tact and preserved in Hash
Separate Hash and NOSTR events to create distinction between private hash entries and public notes
Publish entry as NOSTR note from Hash
Analyze existing NOSTR content using topics and insights hash algorithms
It’ll probably be buggy, but I’ve got a good shot at getting it done this week. To be honest, I’d really like to have it done today, but underpromise and overdeliver, amirite?
Whenever it goes live, I’ll pay for the initial analysis of the notes (a few dollars) but can’t support unlimited chat interactions. So, if you use this integration, please keep in mind that I’m the tiniest business (solo dev) and budget is tiny too. Zap me if you like it!
I’ll turn on subscriptions via cards this week and do the bitcoin integration. I would have done bitcoin sooner, but my engagement from bitcoiners on X has been really low recently, and my apps want to grow adoption by expanding the market into nocoiner republicans and not just feel like another bitcoin app.
Stay tuned! I’ll get this work shipped and then need to shift focus over to revenue generating activities.
That being said…
If the Nostriches are stoked on this and willing to become my patrons, my basic revenue goal is to make around $10k a month. If I priced this tooling at $25 a user, I think 500 users could basically set me up to just build for yall full time without having to do the consulting stuff, raise money, etc. I might need more users or to rework the site efficiency, but it is possible.
Well, NOSTR, you had my interest and now you have my attention.
The key point from my talk at adopting Bitcoin:
If we do not retain the option to access and question “source,” which I define as the originator of a piece of content, then humanity is irrecoverably lost.
There is no more important battle than this. It is the priority.

