It helped that I was already working and living in the US, so I had health insurance to be able to do that comfortably.
That’s horrible. Sorry to hear that.
I have multiple family members who struggled acquiring doctor’s appointments for health issues, which in turn delays treatment for issues that are time-sensitive.
A decade ago, my doctor in Canada told me (in two different appointments over several months) to ignore a dark bump on my face because it would cause an unsightly scar to biopsy it, and he wanted to observe if it would grow in size first before doing anything. I said fuck that guy and went to a specialist in the US, who identified it as a tumor / cancer and told me to operate right away.
It’s no wonder why some people leave their home country to go elsewhere for treatment.
I’ve come to the conclusion that Canadian healthcare is absolute garbage if you’re not on the verge of death. But hey, you won’t go broke from medical bills, I guess. 🤷🏻♂️
Two questions:
1. Have you thought about supporting localization? It seems like only English is supported at the moment. By contrast, major clients like Damus, Amethyst, and Snort support it, and by extension, the non-English speaking community.
2. Have you considered publishing signed releases to nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 for Android?
Grateful to Nostr for educating me about Bitcoin. I would be in a different place today otherwise.
General:
- Deeper collaboration between Nostr developers
- More Nostr projects with multiple builders; fewer projects with a single independent developer
- More developers discover and work on Nostr
- Build more interoperable use cases
- Native signer app for iOS 18+
- Writes for NIP-04 DMs deprecated in most major clients
- NIP for E2EE messaging using MLS finalized and used in production
- Primal support for localization so that it’s accessible by non-English speakers
Personal:
- More adoption of and more contributions to Nostr SDK for Apple Platforms
- Make Comingle iOS more stable, start developing and shipping Android
- Contribute to Damus notedeck. Introduce localization to enable translations to non-English languages
nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe Happy belated birthday! 
Looks incredible! Thanks for onboarding people to Nostr and spreading the word.
Awesome. Thanks for offering to help translate Damus iOS to Kurdish! I’ll DM you with more details.
Exactly ten years ago today, I asked a girl I enjoyed spending time with if we could take our relationship to the next level, and she said yes. Today, we’ve been married for almost three years! nostr:npub1vtavk0dkfjd86j6799p09td3p7t82dfgr6jd9g8njhahcgsemhtsfpkjyp is the most incredible person I’ve met. I’m so grateful for the life we’ve built together and looking forward to what’s to come. I love you, Vita!
I use cat mode from Robohash on Comingle. But Damus-themed avatars would be cool that vary based on npub for those who don’t have (or can’t find) display pictures.
iMessage, SMS, and RCS are a scam.
Olas by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft for Android and iOS.
nostr:note12ucwu7mhd3km8j9arlga6gld9y2yywg7txn39sqg2zjk5t72ap4sutpcep
https://organicmaps.app uses OpenStreetMaps. It’s not Nostr but it’s a solid app. You don’t necessarily need a Nostr app to stop using Google Maps or Waze.
If price source is set to manual, only USD is available, and the price text box doesn't take inputs.
Thanks for the feedback! I’ll look into those issues when I get a chance.
Kagi Translate API would be great.
Submitted a crash report. Happened while scrolling.
What happens when the relays that are referenced from an nevent / nprofile inevitably go away or stop hosting data from those identifiers? Would it not still be valuable to have a stable shareable identifier like a note1 or npub?
Minor fracture per x-ray. #footstr 
nostr:note1xesvkzp26knjsjzu0xqvwhx2qqry4fkk267psek2u27qx8p2gags47dhkd
Wtf? I just learned that there's a one-hour interval every year that simply cannot be represented when daylight savings time ends (in regions that respect it) when using RFC 5545 iCalendar / ISO 8601 format if you want to specify a time zone identifier. This is the format that Google Calendar and most calendar apps follow.
The only way around the issue is to use numerical time zone offsets (which in itself can be error prone due to the need to understand daylight savings and does not conform to the iCalendar spec).
I'm working on NIP-52 calendar events, debating between using Unix timestamps and following the iCalendar format for maximum interoperability. The fact that there's a meaningful interval of time that can't be represented in the latter format seals deal for me, unless I'm missing something. That's pretty messed up.
https://github.com/nostr-protocol/nips/pull/597#issuecomment-1633433118