Is the Pope Catholic? (Yes)
Yeah, that’s pretty much me. See y’all in #nostrville!
Dammit, I prefer when #bitcoin is on sale.
I’m sorry, I didn’t mean to sound defeatist. I think this is a huge opportunity to improve UX.
I’m encouraged by the work nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has done with nsecBunker and whatever he was hinting at today:
nostr:note1qmuakk7f6zr3h8x0ng7ryc8rw2f2vjdr2ka74ayvh4lxr4hrk3jswxuqcp
And to be clear, I love the architecture of public/private key authentication. It just needs a little abstraction to make it less threatening. For example, here’s how Apple handles it:
https://support.apple.com/en-us/102195
Apple of course has the ability for deeper integration into the device than normal apps, but maybe we can learn from this.
Look, if someone were to implement Nostr across their entire company, it would need to integrate somehow into their existing IdP. (Active Directory, Okta, SAML, OAuth, whatever.)
They would need an interface to create (or maybe import, or not) their npub and nsec. And maybe change it somehow without losing history. Generic departmental accounts would need to exist where the person using it can’t access the nsec.
And then it needs to be stored and accessed easily when people need to use it. But be able to have their access to the departmental account revoked when they leave the company or even change jobs within the company.
Maybe nsecBunker can help there, but I admittedly haven’t dug into it enough to see where it meets this.
I’m sorry, I didn’t mean to sound defeatist. I think this is a huge opportunity to improve UX.
I’m encouraged by the work nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has done with nsecBunker and whatever he was hinting at today:
nostr:note1qmuakk7f6zr3h8x0ng7ryc8rw2f2vjdr2ka74ayvh4lxr4hrk3jswxuqcp
And to be clear, I love the architecture of public/private key authentication. It just needs a little abstraction to make it less threatening. For example, here’s how Apple handles it:
https://support.apple.com/en-us/102195
Apple of course has the ability for deeper integration into the device than normal apps, but maybe we can learn from this.
Would you need your old nsec to do this? i.e. would this work if your nsec was lost?
As long as the UX was seamless. As I said in another comment just a few minutes ago, the only thing saving people from their own carelessness with their passwords is the ability to change them.
Adding onto this, the only thing saving them is that they can change their password. Now you want them to have something like a password, but much longer and impossible to remember and oh yeah, if you lose it or it gets stolen there’s no way on heaven or on earth to change it?
Nope.
Dude, they barely know what a password is and they certainly don’t know how to keep it safe.
That’s the problem. People don’t care what Nostr is. They only care if they can follow their friends, family and favorite celebs. Until they can do that, no amount of onboarding effort will matter. And yes, of course that’s a chicken-and-egg problem.
And I hate to say it folks, but all the different clients makes it even more confusing. 99% of people just use the default web browser that comes with their device. They don’t even know what the app is called. Nor do they care.
When iOS and Android each come shipped with their own default Nostr app, and it’s just called something super generic like “Social”, then we’ll start the real adoption.
Or, ya know, we just convince Taylor Swift to move 100% to Nostr. That’d work too.
nostr:npub164q45vfa8prpl7f63stsl9qm9n22v6julkasjdqxjc8kevchsj0sp42rl3 you were asking for progressive non-bitcoiners to interview? Go after Taylor Swift.
Using the python 3.10 runtime for the lambdas. Not using the serverless framework yet, these were all manually configured functions, mostly copy paste from https://github.com/UTXOnly/nost-py and don't adhere to a specific design style. Was really just shooting from the hip here to test a few things.
I'm currently using rds postgresql and relying on that to update the read replicas in the appropriate regions. From the synthetics tests, this seems to update pretty quickly on db write.
But I'm definitely with you on the relational database bit. I have been meaning to try to refactor this to use a nosql db as we are really just utilizing 1 table but it was what I'm familiar with so I just ran with it lol.
Is the idea to eventually use DynamoDB for the events as well?
I created a whole bunch of them so I can sell them at a premium in the coming #hypernostrization.
While I am in favor of Employee Insurance, I’ve never seen it itemized in a receipt like this. Is this an #Illinois thing? 
Cooperating with nostr:npub1w9llyw8c3qnn7h27u3msjlet8xyjz5phdycr5rz335r2j5hj5a0qvs3tur from camelus app to create a common dart_ndk lib similar to nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft's great NDK.
It will be used in both clients and have the best and most efficient gossip/outbox logic for relay discovery.
MIT license so anybody will be able to quickly write dart/flutter apps and contribute to making it better.
Super excited about this! Where can we find the git repo?
#49ers just laid the #proofofwork against Dallas.
I been purple-pillin’ people all day at #pacificbitcoin. We shoulda met up!
nostr:npub1j8y6tcdfw3q3f3h794s6un0gyc5742s0k5h5s2yqj0r70cpklqeqjavrvg where’s the #nostrich gathering tonight at #pacificbitcoin?
nostr:npub1hzlwh2kpl6j9azg8554k66jhwpejsfm09uqqwxw7rjlzpvael6qqfmk8l6 great to meet you today!