NoKYCTranslate.com allows you to pay for access to its machine translation services via Bitcoin / Lightning. Other services, like Google Translate, require your credit card and/or some personally identifying information about you.
Launching https://nokyctranslate.com wasn’t the first project I planned on building for / with Nostr. I only did it because many people, including myself, voiced the desire for easy, hosted translations that accepted BTC/lightning. I’m glad I did though because I’ve learned a lot and it’s going to make my next project easier to launch. Some things I’ve learned:
- kubernetes for auto scaling to handle high demand
- chatgpt can help you debug kubernetes config files
- why number and time limit of database connections matter (too many and things stop working ha)
- chat GPT is helpful for formatting html
- bootstrap is easy and looks pretty
- easiest library in python for making Nostr bots is https://github.com/davestgermain/nostr_bot and https://github.com/davestgermain/aionostr thanks @monk_cactus
- how to get liquidity to a lightning node
- how to create payments programmatically with btcpayserver
- wrote my first ever swift code getting nokyctranslate.com into damus drop down (shoutout to #[0] for making the code nice and easy to follow, and for guidance)
I was nervous about launching my first app and my interactions with devs and others so far has been incredibly encouraging. If you’re hesitant to launch something, I’d encourage you to just go for it!
This is huge because you identified a market need of a no-KYC translation service, learned things that you previously didn’t know along the way, and managed to launch first to the market. Well done!
nostr:note1m8pqs7afeghnqwlmtg2qt3eh796yn3wcjnk3a3pf70ak2zvmjv6s9cxlmu
inb4 next-gen baby names: Nostr, Damus, Zap
#[4] #[5] seems like this breaking change is something we should fix before rolling out to the App Store.
I was able to zap you on this build. I think thread caching makes it not show up right away. Closing and reopening the app makes it show up for me.
Short release cycles are the best for reducing issues and gathering user feedback quickly. https://en.wikipedia.org/wiki/Continuous_delivery
Disagree about the stop coding part, but agree with everything else, and a lot of that does already happen. It’s more that there’s more work to do than there is dev time to address the feedback reasonably quickly.
Amazing work by #[4] !
Oh my god, relay connections are so snappy compared to before. Really well done.
The client could inform the user that N number of people you follow muted this account. And then the user can decide for themself.
Auto-blocking sounds like a terrible feature unless the user can fully configure how it behaves.
Wasn’t me. You can thank #[4]
Wasn’t a big Twitter user to begin with, but I stopped scrolling Reddit immediately after I found Damus / Nostr.
Used Namecheap for years, had no idea that they accept Bitcoin. Nice!
imo verification can’t be achieved. A better model is NIP-05 for early sharing identifiers, combined with web of trust via who follows whom. True verification is trusting a centralized service that has checked someone’s state issued ID.
Yes, please. It’s for only identification and easy sharing of profiles without pasting around full npubs.