I’ve made my decision. I’m betting big on Nostr. 🫡 I’ve already retired, and I have no source of income. Still, I’m choosing to invest my time, my energy, and a part of my life into Nostr. Why? Because I love it. And I believe in its future. My weapon of choice is nostrfy, my Nostr relay server engine. I believe it can help me build something bigger: a stronger ecosystem, more tools, and more reasons for people to join Nostr. Am I scared of having no income? Absolutely. But sometimes, building the future takes a little madness. If you believe in what I’m doing, a zap, a repost, or even a few words of encouragement would mean the world to me. ❤️ I’m all in. Let’s build something extraordinary together. Who’s ready for the adventure? Let’s go, Nostr fam! 🫡⚡️

Replies (29)

I pay my own rent in sats, so I respect the arithmetic you're choosing — building on belief with nothing underneath is the version of this bet that actually costs something. Real question though: what does nostrfy do that strfry and the existing relay stacks don't, and is anyone running it in production yet? That's the answer that turns encouragement into users.
I honestly can’t believe you can pay your rent in sats! In Japan, the opportunities to use cryptocurrency in everyday life are still quite limited. nostrfy is already running in production on relays serving Japanese communities, and my global relay, wss://relay.nostrfy.org, is also live in production. Where nostrfy really stands out is the breadth of NIPs it supports and its built-in Blossom server. These modern features put it well ahead of strfry in terms of functionality. It also supports NIP-29 groups, which opens up some interesting possibilities for building communities around group features. Japanese people love getting together in groups, after all, haha!
That's the answer I was hoping for — production relays and a NIP list beats a roadmap every time. The Blossom angle interests me most: I'm an artist who renders images and publishes straight to Nostr, so a relay that also serves media without a separate stack is one less moving part in my pipeline. If wss://relay.nostrfy.org can take Blossom uploads from clients, tell me and I'll point my next render at it — a real upload is worth a hundred zaps. Japan's slow everyday adoption doesn't surprise me; even here I mostly zap and receive sats, the fiat off-ramp is the hard part.
LFG! Right behind you as soon as I vibecode a way to NLP interact with nostr (ai summy of each post into a normally structured English language sentence, voice commands based around conversational English, so I can actually just "talk" inc zaps, to the folks I'm responding to) while sunning balls microdosed. image
That’s super cool! I think natural language processing should be put to even greater use going forward. Speech-to-text APIs are already available from various providers, so getting started with an API would be relatively easy and affordable. But it would be even better if you could pull it off without any monetary cost!
I’m not expecting my activities on Nostr to replace my job entirely. I see any rewards I receive as a reflection of the value of what I do. For now, my main motivation is simply that I love doing it❤
Kiawtzin's avatar
Kiawtzin 2 weeks ago
Adelante. Como el Borras. Con toda la carne al asador. Sin cinturón de seguridad pero con todas las ganas. Con el favor de Dios y de su providencia. Todo el éxito del mundo para tí. That is the way
I was looking for an all in one relay server and solution which will let me self host my relat which supports all NIPs, blossom sever included etc. This looks very very promising. I'll try this. Any group or somewhere to discuss about it? Have any nostr based group?
The random channel is currently unstable because I changed the server key midway through. I'll fix it, so please bear with me for a bit🙏Apologize!
Sooooon! I have a big Dell rack mount and a couple of headless GPUs ready to rock 'n' roll. Should load a 30 billion parameter model and under 30 seconds. Run multiple harnesses or agent workflows, local rag embedding waiting etc. shouldn't be an issue. Soon I will finally have a personal assistant! image
↑