deleted by author
If you run a LN node, you can set min HTLC to 10 or 100 sats. But you need to do that with all your channels. That means others can't route these payments through your node and also you can't receive them if are lower than your limit. But if you just use a custodial account, it is almost nothing you can do, than just receive sats.
reply
I agree with DarthCoin that Min HTLC is the current solution.
I wonder if disabling messaging could be a BIP and/or a setting in the different Lightning node implementations in the future.
Hey now. We are the Satogram team. Many of the replies here are accurate but we'll do a summary:
  • most lightning addresses pulled from nostr where people publicly shared them.
  • place on our site to manually add your node pubkey or lightning address
  • to be removed off the list, we need proof you control the node or lightning address, otherwise you 'd be able to remove other people's addresses/pubkeys
  • we want wallets to add a filter users can set so that they don't see Satograms under a certain sat value (Zeus has done this) . Or, a separate Satogram "folder"
  • All satograms are tagged with a custom record field so that the htlc can be identified as a Satogram as opposed to a regular payment
  • Wallets who embrace Satograms have a new revenue stream. I.e. custodial wallets can collect some of the sats, or for extra fee feature the Satograms (phone notification, special icon, clickable links, embedded images, etc)
Perhaps an AMA would be good.
Seeking any and all feedback.
reply
When you send to a lightning address, are you utilizing LUD-12 comments? If so, how do you handle the various limits of comment length by various LN Addr providers? Or are payments all via Keysend?
reply
only keysends are being used to send to pubkeys currently. To lightning addresses we use do utilize lud 12 comments but also include in the custom records field the message, inside field 34349334 (as well as the Satogram identifier field 6789998212). Currently we just ensure that the lightning address supports comments, but are not taking into consideration the allowable length. In practice it seems lightning address providers are not adhering to the length that their lightning addresses specify.
reply
Thank you for the response!
In practice it seems lightning address providers are not adhering to the length that their lightning addresses specify.
That’s interesting. IIRC Wallet of Satoshi specifies an allowed length of 32, which felt small. I wonder if they’re enforcing it. SN enforces theirs at 1000 chars
reply
I went to your talk at Adopting Bitcoin, really good!
reply
thank you!
reply
Why is it a requirement to verify/sign your own the wallet to be removed but not to be added?
What if i don't want this spam in my wallet posted on nostr? also this creates an incentive for someone to create multiple accounts and just farm free sats with a lot of wallets, would be amazed if this hasn't happened yet.
deleted by author
reply
yeah a good point, and I dont think theres a perfect solution for this. If the wallets have barriers to prevent making duplicate accounts and lightning addresses, thats one barrier.
reply
Honestly, I didn’t know this existed. I think this is pretty cool and I personally don’t mind receiving some free sats to read some message some random person sends me
reply
Wallets should have a setting for 'minimum sats threshold for message notification'. That way everyone individually sets the price for their attention and this problem is solved.
That way you either:
  1. get free sats without attention lost (if below threshold)
  2. get advertised message, that someone really wanted you to get because they paid high enough to penetrate your paywall, more likely to be worth your time (if over threshold)
reply
came here to say this. it's not a protocol issue. if people wanna pay me for absolutely nothing, go right ahead. I just want to be able to reliably ignore it.
reply
We've seen a lot of spam recently on LN.tips too. While I don't mind getting free sats now and then, it's quite annoying getting a bunch of notifications just for ads.
Dr. Calle recently posted this on Nostr:
PSA: Probably going to disable LNURL messages below 100 sat payments in LN.tips - the spam has been going wild in recent days. Get rekt spammers.
I don't oppose zapvertising but I think it should be an opt-in feature relying on users instead of advertisers or wallet managers in custodial implementations.
reply
Hi, EagleSats here. We agree with your sentiment. This new way of advertising is incredibly unique and we're all figuring it out as we go! Advertising is not inherently bad, but spam kinda is.... Thats why we made the decision to change to opt-in only. We cut all addresses which we obtained from public means and now only send to addresses that actually want to receive ads and sats.
reply
Your concerns are valid. It's an interesting service and in my opinion has some potential, but it definitely needs to improve.
reply
I've been receiving a bunch of these payment ads to WOS and have never opted in to a service like that. Someone definitely grabbed my address and did it for me. Maybe pulled it off of a Nostr profile??
reply
Very likely.
reply
Yeah I totally get those concerns, I think for custodial wallets giving users the option to receive these messages or setting a limit would help, while those with their own nodes can already do that
I think the potential for abuse sorts itself out, people won't post satograms if they don't get a return in engagement and traffic, and if people want to farm LN wallets let them, doesn't look like a good use of time, but hey let people find that out on their own
reply
maybe require some sort of verification, can be Nostr for example, as a way to only allow real people to be included in the receiving ad list, this would invalid abusers spamming wallets.
reply
Yea, I agree to this, the execution is flawed
reply
Hello, we've developed satsforads.net with user consent in mind.
  1. Our DB is totally opt-in. We never scraped any lightning address from Twitter, Nostr, etc. All our current 918 members signed up to receive sats. We also work on an automated way to remove a lightning address that no longer wants to receive satsforads. How? We ask the lightning address owner to pay a 1 sat invoice and immediately send back the 1 sat to the lightning address with a secure code / or link. A random 8 character string will work. Then user is sent to a link where he can enter the 8 character string and voila, the lightning address is removed from the DB. This way we can make sure, that nobody can remove the lightning address, only the owner. You might question, why do we need the user to pay first a 1 sat invoice to us? To prevent abuse from users. 2, This one is harder but while we don't scrape websites to look for new lightning addresses, we actively scrape the net and try to minimize the abuse of using multiple addresses by the same person. Of course, we let someone register as many lightning addresses as he want, but you will notice that not all of them will be included in campaigns.
reply
Love seeing this experiment play out in real-time!
reply
Second concerns is legit. First one isn't, imo. I remember in my childhood I must watched 50 more advertises to continue watch movie on TV, now I got payed in sats for small message. I'm ready to get all your messages if you ready to gift me your scarce sats
reply
It'd be pretty easy for lightning nodes/wallets to just stop showing/highlighting the message. That would probably deter spam pretty quickly.
reply
I see that I am sent 1 sat a few times in my wallet yet I have not put my address on these sites, I hope they will not empty my wallet with that.
reply
What I just said before? Some other services are already implementing it. https://primal.net/e/note1ym0p4qlswhkhxfz5wqs23j5rrkuc6zlgn0z0kw3xxlmzvjsfv3sqzs5hqa
reply
deleted by author
reply