Time to enjoy the weekend! 🐶🐾🫂🫶🏻

No, all of them are made of accounts making 5+ posts that are exactly the same in a short amount of time. That sends the account to the temporary block list, which is resetted when the app restarts.

People simply deleted the duplicated posts to solve it.

Works in damus, although might be a bit confusing without custom support 😅

😂

1. RSS content into nostr from prolific / interesting content creators

2. Honest actor / trusted community member sets up “their” lightning address

3. Interact with the acc as if it were the content creator. Like /zap etc.

4. Inform content creator of the sats waiting for them to collect. Inform about nostr at the same time.

5. Send them their earnings.

Win for us = good content

Win for them = sats

Possible win for nostr = influencer onboarding

Thoughts? Does this feel shady in any way?

We could organize one ourselves, sure! 🐶🐾🫡⚡️

If it 1 hour, then #zap as your life depended on it! 🐶🐾🫡⚡️⚡️⚡️⚡️

I recently added signature checking to all profiles ? Maybe a factor. Hard to say without profiling.

The globe is round! Where? 🐶🐾😂😂😂

Oof. None of these Zaps are going through. WoS has been killed again. 😂😂😂

I just realized that my feed and global are almost identical at this hour. I follow more than 750 people! 🐶🐾😂😂😂😂

Everything that touches the MDN website is trash.

How fast do you think this will load? 🐶🐾🫡

When did this change?

I want to publicly apologize to Will for temporarily impersonating him to start the conversation. It was not the brightest move. You can tell I’m not well versed in ethical “hacking”. I can understand why that may be upsetting.

Sorry Will. I hope you find it in your heart to forgive.

At the same time I’m concerned with this issue. It’s clear to me that NIP5 is not effective at stopping this type of issues. Anyone can get a NIP5 and nobody will know what your real NIP5 is supposed to be.

While I have some reputational risk, a scammer has zero to lose by paying a little and replying within a hot thread. I could see cases where someone may be able to rip people off fairly easily without much effort.

Right now it’s not much of an issue but down the road it could become one. Hopefully smarter people than myself are already thinking about these things and kicking around viable ideas.

I’ll accept any fallout. I’m not a perfect person.

One suggestion…

Nostr doesn't really have the idea of srcset like figure>img does in HTML. AFAIK NIP-94 doesn't really have the ability to do it either because it's one hash per event and each size of an image would have a separate hash.

But what you're doing could be modified to support the idea of srcset - so it lists all the sizes available and then the client would pic the one that's appropriate for the UI at the in the moment. It could reduce bandwidth usage by the client when multiple sizes are available.