Nostr Web Client

zappr (old key) 2y ago

### zappr (cycle #169)

made by #[53]

### zapped users

**Please avoid replying to this post and tag me instead to not spam people with notifications.**

⚡️ Zapped #[0] 51 sats

⚡️ Zapped #[1] 51 sats

⚡️ Zapped #[2] 51 sats

⚡️ Zapped #[3] 51 sats

⚡️ Zapped #[4] 51 sats

⚡️ Zapped #[5] 51 sats

⚡️ Zapped #[6] 51 sats

⚡️ Zapped #[7] 51 sats

⚡️ Zapped #[8] 51 sats

⚡️ Zapped #[9] 51 sats

⚡️ Zapped #[10] 51 sats

⚡️ Zapped #[11] 51 sats

⚡️ Zapped #[12] 51 sats

⚡️ Zapped #[13] 51 sats

⚡️ Zapped #[14] 51 sats

⚡️ Zapped #[15] 51 sats

⚡️ Zapped #[16] 51 sats

⚡️ Zapped #[17] 51 sats

⚡️ Zapped #[18] 51 sats

⚡️ Zapped #[19] 44 sats

⚡️ Zapped #[20] 44 sats

⚡️ Zapped #[21] 44 sats

⚡️ Zapped #[22] 44 sats

⚡️ Zapped #[23] 44 sats

⚡️ Zapped #[24] 44 sats

⚡️ Zapped #[25] 44 sats

⚡️ Zapped #[26] 44 sats

⚡️ Zapped #[27] 44 sats

⚡️ Zapped #[28] 44 sats

⚡️ Zapped #[29] 44 sats

⚡️ Zapped #[30] 44 sats

⚡️ Zapped #[31] 30 sats

⚡️ Zapped #[32] 30 sats

⚡️ Zapped #[33] 30 sats

⚡️ Zapped #[34] 30 sats

⚡️ Zapped #[35] 30 sats

⚡️ Zapped #[36] 30 sats

⚡️ Zapped #[37] 30 sats

⚡️ Zapped #[38] 30 sats

⚡️ Zapped #[39] 30 sats

⚡️ Zapped #[40] 30 sats

⚡️ Zapped #[41] 30 sats

⚡️ Zapped #[42] 35 sats

⚡️ Zapped #[43] 35 sats

⚡️ Zapped #[44] 23 sats

⚡️ Zapped #[45] 23 sats

⚡️ Zapped #[46] 23 sats

⚡️ Zapped #[47] 23 sats

⚡️ Zapped #[48] 23 sats

⚡️ Zapped #[49] 23 sats

⚡️ Zapped #[50] 23 sats

⚡️ Zapped #[51] 23 sats

⚡️ Zapped #[52] 14 sats

Total: 2146 sats

### zap pool stats

depth: 0 pubkeys

balance: 245770 sat

Please donate to keep the zaps flowing, 6k sat provides 125 people with zaps for 1 hour: zappr@semisol.dev

Donate to me for making the bot (will **not** be distributed): sats@semisol.dev

Reply to this note

Please Login to reply.

Discussion

arkinox 2y ago

#[54] hey chief, it's not a big deal to me but I didn't actually receive this zap here. Just wanted to let you know 🛠

Pleb⚡ 2y ago

U need wallet that support NIP-57 like WoS

MainStreetChungus 2y ago

Ah, I didn’t know that, I switched to LNTips and now see the zaps, before with alby I didn’t. Thanks for the tip pleb!

arkinox 2y ago

Thanks. Not interested in WoS but I appreciate the explanation! Zapped!

Gregor 2y ago

Can you recommend any other way to get a LNURL for zaps on iOS other than WoS or running your own node?

I found nothing reasonably trustworthy looking in the overview graphic in the following article either.

https://coincharge.io/en/lnurl-for-lightning-wallets

finch ☦️ 2y ago

There is no other way currently.

finch ☦️ 2y ago

No non-custodial mobile LN wallets support receiving via LNURL. A big issue at the moment.

Gregor 2y ago

Big issue indeed, why does BOLT12 seem to receive so little attention? Too difficult to implement?

sperry 2y ago

Big issue is replies on this feed with a million people tagged, c'mon now, do better.

finch ☦️ 2y ago

Yeah, need a way to remove yourself from a conversation or mute a conversation at least

channel.ninja 2y ago

Stop answering to this thread people 😂

SURF⚡️ 2y ago

A lot of people are using LN.tips on telegram (gotta have telegram though) but it seems to be another option and then linking it to bluewallet or another lightning wallet.

finch ☦️ 2y ago

Still custodial, so same risks/issues as WoS

SURF⚡️ 2y ago

Sure, if looking for non custodial it won’t work. Just gotta keep your balance smaller and be aware if you don’t mind.

daniele 2y ago

It seems that every client except Gossip still wrongly manage the notifications, flooding the user when a large thread starts:

Ex. in #[7] I was just mentioned (I didn't replied) and I'm receiving notifications for every reply because they include *all* the mentioned users in the first note as p-tag [*]

Proposal: why don't show only the notifications that are a direct reply to the user's note or are in his gerarchy (reply of reply)?

Or at least separate and giving them a different highlight related to their importance.

To notify direct replies (or the gerarchy) a client can use as reference the e-tag's npub instead of the p-tags.

[*] I suspect that the notification problem starts from the event structure, NIP-10 stated:

> When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the "pubkey" of the event being replied to.

So p tags are accumulating at every reply, why is this necessary?

/cc #[1] #[0] #[5] #[2] #[3] #[6] #[4]

(This way we can test the issue realtime 🤣)

KoalaSat 2y ago

Never thought about this but it should be easy to identify whether the list of tagged events belongs to the user or not by looking into the DB, I'll think about this thanks for heads-up!