Did you upload from nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 ? Cause I had this issue a long time ago with nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 when I uploaded a pic but it grabbed someone else’s pic that was uploading at the same time

cc: nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w

Reply to this note

Please Login to reply.

Discussion

It was Primal. Damus worked

Haha more bugs. I just zapped your note in Damus, then got a notification in Primal that I received 21 sats from Volker πŸ€ͺ WTF

I’ve had sum similar happen as of lately, ever since push notifications πŸ˜‚πŸ˜‚

I think the primal zapper is adding a p tag instead of a P tag which is tripping up our push notification server

https://github.com/damus-io/notepush/issues/8

That's above my pay grade. I just do Bitcoin, but I trust(!) you here.

wtf is a uppercase P tag?

See nip57?

eithet this has existed for a while and I implemented it and completely forgot, or it’s new

Its new, its for fetching zaps sent by a particular user

Oh that explains why I keep getting zap notifications for those sent to users replying to me. Thx