Nothing wrong with a little saturation. The ads, however, fail to inspire.
The “Adpocalypse” has begun. The 5 most recent zaps I have received are all ads. They scraped my #Bitcoin #Lightning address from my #Nostr profile after I added it through Damus and now I am receiving ZPAM (#Zap spam) as Lightning payments. One of them was 50 sats, but the rest have all been 5 #sats each. See the attached screenshot. 
I just received a marketing message through Wallet of Satoshi because my #Bitcoin #lightning address is displayed on my #Nostr profile. I saw a notification that I had received a #zap, so I checked it out. What was it? It was an unsolicited marketing message that someone paid 5 #sats to send me by putting an ad in the payment description. Nostr users should be prepared to start receiving ZPAM (Zap spam) messages if they have a lightning address listed publicly. I added mine though Damus when I first downloaded the app and have received valid sats in response to some of my posts, but I am not looking forward to an onslaught of “junk mail” via Nostr and Lightning. The idea of getting paid directly for every ad I have to look at sounds nice at first, but the very low barrier to entry makes me worried that once the floodgates open, nothing will be able to hold back the great deluge of ads.
A post definitely falls under the umbrella of “other stuff”. Posting something to Nostr is a completely acceptable use case for leveraging the notes *mechanism*. To wit, the Damus client shows a “Post” button when creating a new note as evidenced by the attached screenshot… #nostr #damus 
Definitely. It was a very optimistic experience.
Hey nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m, just now while purchasing a service using my desktop browser I was presented with a lightning invoice to pay for my subscription. I scanned the QR code with Cash App on my phone to make the payment. The payment settled immediately and the payment page on my desktop browser *instantly* detected the payment and updated to reflect a successful subscription. I think it was the fastest payment I’ve ever seen go though of any type; I’ve never paid with a credit card (online or in person) and had it work that quickly. Good stuff. #bitcoin #lightning #zap #nostr
A particular reason won’t suffice?
Hey nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m and nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, I have a question related to Nostr.
I am building a passwordless login system for an app (login link sent to email, verification code sent via SMS, OAuth, etc.) and I want to include the ability to log in via Nostr. However, I only want to collect the npub from the user; I don't want the user to input their nsec key. This will only be for account creation and login purposes to verify that the user owns the provided npub; the user won't actually be posting anything to Nostr, so they won't need to provide their nsec key. I have two really simple options for accomplishing this (simplicity is the goal here):
1. When the user inputs their npub on the login/create account form, the app can send them a DM via Nostr with a code that they can then input in the app to verify that they own the npub in question. My app never has to ask for the nsec, and I can trust that the user is the owner of the nsec associated with the provided npub.
2. This option is simply the first option in reverse. When the user inputs their npub on the login/create account form, the app can show the user a code, and the user can then DM the code to the app's Nostr account to verify that they control the nsec associated with the provided npub.
Both of these options allow me to verify that someone owns the npub without having to ask for their nsec key. This allows a user to create an account on my app using their Nostr account, basically making their account "Nostr verified" (insofar as that other users can trust that the account on my app belongs to the owner of the associated Nostr npub). However, I have some questions:
First, can anyone DM anyone else on Nostr? If someone provides their npub, can I send them a DM with a verification code without being connected (either following them or them following me)?
Second, is there a better, simpler, or more standardized way to approach this with Nostr?
I recently developed a complex messaging application using DIDComm (different from the app I am currently developing), along with a custom mediator and relay built on top of the Aries Framework from Hyperledger with a React Native edge agent. That app uses verifiable credentials issued by a self-hosted VON (Verifiable Organizations Network) running on a custom built distributed ledger to achieve self-sovereign identity, credential exchange & verification, message exchange, persistence, etc.
I wanted to avoid that kind of complexity here and do something hyper simple to verify identity.
Any help with pointing me in the right direction or toward the right person(s) to answer my questions would be much appreciated!
Hey #nostr people, any thoughts on this? I want to include this functionality in my own app, but I also think it’s an interesting idea to consider when thinking about bridging the gap between Nostr and the mainstream web. By implementing hybrid solutions, traditional apps and websites can bring people over to Nostr incrementally by making it an *option* to use *some* Nostr functionality within the familiar landscapes they are comfortable with.
Hey nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m and nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, I have a question related to Nostr.
I am building a passwordless login system for an app (login link sent to email, verification code sent via SMS, OAuth, etc.) and I want to include the ability to log in via Nostr. However, I only want to collect the npub from the user; I don't want the user to input their nsec key. This will only be for account creation and login purposes to verify that the user owns the provided npub; the user won't actually be posting anything to Nostr, so they won't need to provide their nsec key. I have two really simple options for accomplishing this (simplicity is the goal here):
1. When the user inputs their npub on the login/create account form, the app can send them a DM via Nostr with a code that they can then input in the app to verify that they own the npub in question. My app never has to ask for the nsec, and I can trust that the user is the owner of the nsec associated with the provided npub.
2. This option is simply the first option in reverse. When the user inputs their npub on the login/create account form, the app can show the user a code, and the user can then DM the code to the app's Nostr account to verify that they control the nsec associated with the provided npub.
Both of these options allow me to verify that someone owns the npub without having to ask for their nsec key. This allows a user to create an account on my app using their Nostr account, basically making their account "Nostr verified" (insofar as that other users can trust that the account on my app belongs to the owner of the associated Nostr npub). However, I have some questions:
First, can anyone DM anyone else on Nostr? If someone provides their npub, can I send them a DM with a verification code without being connected (either following them or them following me)?
Second, is there a better, simpler, or more standardized way to approach this with Nostr?
I recently developed a complex messaging application using DIDComm (different from the app I am currently developing), along with a custom mediator and relay built on top of the Aries Framework from Hyperledger with a React Native edge agent. That app uses verifiable credentials issued by a self-hosted VON (Verifiable Organizations Network) running on a custom built distributed ledger to achieve self-sovereign identity, credential exchange & verification, message exchange, persistence, etc.
I wanted to avoid that kind of complexity here and do something hyper simple to verify identity.
Any help with pointing me in the right direction or toward the right person(s) to answer my questions would be much appreciated!
Maybe there is some rule or concept that I’m just not understanding, but why can Primal have a #zap button on each note but Damus can’t? Is that rule only for published apps or something? Can TestFlight apps do whatever they want? #nostr
I want to drop a “thank you” to nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m for literally taking care of business. I can happily report that we successfully received the referral bonus today after he took an interest! If I can wax poetic for just a moment… I saw his original tweet about Cash App on October 15th, 2013 and retweeted it right away and then immediately signed up for an account (it was called Square Cash back then). I’ve been a user since day 1 (maybe even hour 1!) and have recommended the service to many, many people. My wife and I use it multiple times a day and I’ve been able to send money to people really quickly when they have really needed it on numerous occasions. I am so glad the company is what I always thought it was and that someone like nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m would carve out a moment of their time to help a frustrated stranger. I’m feeling a little less cynical about everything today, so thanks again. PV 🫂
Thanks nostr:npub1esqdgzkn283a7s4upj3rppkrpu54hwkrf8d7w56p3jlhr7mhvccs986x2u, I appreciate the zap / SATS!
And you too, nostr:npub1leqraca9xtyuezf4vmxa6czrepe04ynpmvjqzf7kq0v3cqnrj8vsmf0ed0! Thanks!
Exactly! It had absolutely nothing to do with earning a few dollars. If nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m‘s care and attention is any indication of the company as a whole then Cash App is exceptional! I probably did something wrong or disqualifying during the process, but not being told *what* I did wrong is frustrating. Being related would make some sense, although that seems like more of a semantics issue. Alternatively, one of the requirements is that a new account must send $5 within their first 14 days to earn the bonus, so I had my wife send some money to my daughter’s account and then had my daughter send that money to me to meet the requirement. It could be that doing something like that is not allowed. Or it could be that my daughter recently got a new phone number and used it to create her account, but perhaps someone else had previously used that number to create a Cash App. It could be a lot of things, the issue is just that I don’t know which one it actually was. But as I said, nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m has been more than helpful! It’s funny how just a little bit of care from somebody who doesn’t have to give it can have such a meaningful impact on how you perceive things.
It’s quite possible it was something simple like that, although they would have no real way of knowing that we were related since we have different last names. We don’t even care about the actual referral bonus, we really just wanted an answer as to what we might have done wrong in the process. Instead we were just dismissed, which left my daughter with a cynical viewpoint about Cash App. I’m not typically a person to raise a complaint about something so small, but it was just so frustrating in the moment. I’m fully prepared to accept that we did not complete the process correctly or the way we sent money back-and-forth did not qualify for a bonus, but without an explanation we aren’t sure what we did wrong. We probably messed something up ourselves, but it would be nice to know *what*. Either way, nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m is looking into it and that’s more than good enough for me, however it turns out.
This part is purely anecdotal, but the reason we finally decided to set her up with a Cash App was because we were previously using Apple Cash to send her lunch money, but one day she went to get lunch at school and my payment to her was on hold for some reason. Apple first required her to go through a verification process to continue receiving payments and then disabled her account immediately after she added her birthday, which indicated that she was under 18. So… after a few of days of not being able to easily transfer her lunch money without an “Apple Cash Family” account we decided to switch her to Cash App. I am very glad that such an option exists, even if we had a minor hiccup with support. I’ve been a Cash App user forever and nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m‘s response to something so small only inspires confidence.
Thanks nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m, I was hoping that if there was anyone at the top of a large / important company who actually listens and pays attention that it would be you… and you didn’t disappoint! #PV
Thanks nostr:npub1esqdgzkn283a7s4upj3rppkrpu54hwkrf8d7w56p3jlhr7mhvccs986x2u, I appreciate the zap / SATS!
Spot on again! I have had nothing but positive experiences with Cash App and have recommended it to lots of people. I was hoping that I would be able to deal with support directly and get a resolution (or at least an answer), but when they completely shut the door on us I didn’t know where else to broach the topic. nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m seems like a reasonable guy with his ear to the ground and a penchant for taking action, so here we are. Hopefully this has a non-zero impact on how support interacts with customers; I honestly don’t even care if they resolve our particular situation, although it would be cool to show my daughter that they took action and did the right thing by us. Also, if it turns out that we made a mistake in the process or there’s an actual legitimate reason for us not receiving the reward then so be it. I’m not upset that we didn’t receive it, I’m just frustrated that we don’t know why.
