Awesome. You might want to disable the “video is for kids” setting. It actually restricts features (such as using the miniplayer) on YouTube rather than expand them, which is counterintuitive. I’ve been caught by that before when uploading videos.
Wanted to buy my mother-in-law in Canada something online. Accidentally had my VPN set to Toronto and used my US credit card. Instantly flagged as potential fraud and needed to submit identity verification. What is this? Please just take my money. 🤦🏻♂️
Thank you, QW! Same goes to you. Grateful for all of your work on Plebchain Radio, NostrPHX, Nostr education and evangelism, and for being a great human being.
It's a privilege and honor to receive this grant from the Human Rights Foundation to work on Nostr. There are so many incredible contributors to Nostr and other human rights efforts who are just as, if not more, deserving. I'm very grateful to be playing a small part in shaping Nostr. Thanks to @Alex Li@gladstein and everyone else involved at HRF for making this possible. Thanks to @jb55 for creating Damus and shaping the Nostr protocol. Thanks to @montzstar and @klabo for allowing me to create Nostr SDK for Apple Platforms with you. 🫂
https://hrf.org/hrf-bitcoin-development-fund-grants-1-billion-satoshis-to-14-projects-worldwide/https://i.nostr.build/KGX02.jpg
Thank you! This grant is for me to work on Nostr part time over the next ten months. I’m not in a good enough position to go full time into Nostr just yet. I have three tentative focus areas. Not sure if I’m committing more than I’m able to deliver, but here it is.
1. Comingle. Implement and rollout the meetup / conference client on iOS and Android, and eventually Web. Aiming to ship some basic release in time for Nostriga in August.
2. Nostr SDK for Apple Platforms. Implement the outbox model (relay hints), finish the list implementation, NIP-17 DMs, zaps. Have at least two iOS clients use the SDK.
3. Damus. Internationalize user-facing copy for the multiplatform version of Damus which will support Android. Continued development of the translations pipeline for iOS. Any miscellaneous features or bug fixes on iOS.
It’s also an aspiration of mine to build a native iOS Nostr event signer app, similar to Amber on Android, but I don’t think I can commit to doing it unless I drop something else. It’s important, though.
It took me a while to get comfortable with them. They were clamping too hard on my head. That feeling went away after a few weeks. I’m pretty happy with them now.
You also need to recall the home address on file that you haven’t lived in for 10 years. (True story, I wasn’t able to pay taxes, even though I wanted to, until I provided my old address over the phone, listing out my entire history of where I’ve lived until they confirmed I gave them the correct one, so that they could update their records to my new address and mail me an authorization code to log into my online tax account)
Oh, I forgot this was happening. Tuning in! 🛢️
One good thing about the riots last time was that it weeded out all the bad people, and some were caught on camera and held accountable.
People love to beat on San Francisco because of crime and homelessness, but outside of a few bad neighborhoods, it meets all of your criteria. We lived there for 10 years and loved it.
@hodlbod@Vitor Pamplona@fiatjaf I’m implementing NIP-59 Gift Wraps in Nostr SDK for Apple Platforms and also reading the NIP-17 Private Direct Message spec. It seems that one benefit is that the recipient can fully recover messages from any client using their private key.
However, the only way for the sender to recover the messages that they sent is by backing up all the keys they used to send the messages and also backing up the mapping of which keys are paired with which recipient.
Am I understanding this correctly?
Ok, that makes sense. Seems like we could clarify that on NIP-17, unless I missed it. So then the rumor and seal would be identical for both the sender and recipient gift wrapped copies. Just the random signing key and p tag would be different on the gift wrapped copy to yourself as the sender.
Ok, @zach just convinced me in person that this might be a good idea.
The person can still be a calendar if it’s going to be only one person and a single calendar. But you could also have a dedicated pubkey for a calendar. Clients can subscribe to calendar event kinds rather than need to first subscribe to a calendar list, then to the calendar events within that list. It simplifies the number of queries you need to make to get a list of calendar events. And also, clients can still opt into supporting calendar lists if they wanted to.
Oddbean new post about login | logout
Notes by tyiu | export