Some thoughts on the current state of #zapvertising
I have attempted to reasonably articulate my thoughts.
Discussion
I was unaware Damus was pinning zapvertising persistently on feeds.
Yeah that needs to die. And as someone who has used it (I'd like to think we'll and respectfully) I don't do so with the intention of clogging up the feed. To me it's an add on to a v4v transaction that both the zapper and the viewer should gain some value from. How clients implement these features will definitely have an impact on how zapvertizers behave. I see it quickly bifercating into mass small-sat zap spammers, and small businesses zapping targeted audiences amounts that compensate users appropriately.
I remain very bullish on the concept, but only time will tell!
Thanks for the detailed and in depth write up
It pretty much alligns with my own views.
Glad you are trying to discuss this
So simply thanks
100% agree. This is the second time Damus has lashed out at user sovereignty, this time it was (for me) less intrusive, but it should definitely be optional and disabled by default.
Since I am criticising gratuitously, I also don't think it's right that all new pubkeys are created and automatically follow the developerโs profiles (without asking it).
I think the line that separates user sovereignty should be sacred, and as usual, we allow it to be crossed without anyone (well just a few crazy old men) noticing.
Its a testflight experiment, none of this is final. I threw it together in like 2 hours.
โLashed out at user sovereignty โ is a bit dramatic. It is designed to encourage people to zap posts instead of having them hidden away. Of course you will be able to disable top zaps via a setting on the post. Iโve already mentioned this when I launched the experiment.
i have new social application idea project with new concept need to share it with as software developer can i contact you
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s It was never my intention to get into a debate, English is not my native language and maybe I can't find the right words.
It all boils down to the same thing, I think we should be very careful with the changes we add, and never modify the user experience, no matter how well intentioned you are.
Pardon me getting into the middle, but I canโt agree with โโฆand never modify the user experience, no matter how well intentioned you are.โ By that definition nothing will ever change for better or worse.
Test Flight is for the purpose of people trying new and potentially harmful things. If someone dislikes it, they should go back to the standard release. If people are willing to experiment, then they should provide a neutral, data driven and constructive feedback.
Feel free to ignore my comments, I am just expressing my understanding of the situation! ๐ถ๐พ๐ซก
Yeah thatโs what makes nostr awesome - lots of experiments. Some bad things may come out of that but we may not discover the awesome stuff if we donโt test wild ideas.
Precisely! Expect the worst, get the best results in the end! ๐ถ๐พ๐ซก
I will try to express it better. Never take any action on behalf of the user, to follow an account you have to publish a note on nostr. Has anyone asked this new user? I don't want to get into a debate, and even less with developers like Will, I was just expressing my opinion, by the way, I was answering to a great article written by nostr:npub1wtuh24gpuxjyvnmjwlvxzg8k0elhasagfmmgz0x8vp4ltcy8ples54e7js, this article is what is important, not my comment.
I noted that this option was already in progress in the article, as well as noting that I myself switched back to the release version for the day. Damus is simply the best way to experience Nostr right now imo.
I agree test flight is exactly where to do this.
I hope the article articulated ideas, and did not feel like an attack. It was certainly not intended as one. Only as thoughts and potential ideas moving forward.
๐๐ผ๐ค
I havenโt read your post yet (still busy) but judging by othersโ responses, it seems that people are against it in the current form.
One thing we must not forget is that itโs in TestFlight version and Will promised to have on/off switch in the App Store release.
Second, given number of spamvertizemnts Iโve seen already, I configured my zapper to swallow anything with URL and below certain sats threshold. I know that this solution is only possible for a very few people, but it worked wonders for me.
๐ถ๐พ๐ซก
I'm on #amethyst and it seems that it's not working as you said with the highest zap at the top. Looks like a 21 and 386 are at the top. ๐ค
What client are you using? Interesting in #amethyst you have to toggle that arrow on the far left to see the zaps and likes and shares, which I just discovered... Secondly if you toggle it to show that it doesn't stay, you have to do it on every note you want to see that data. So in your article it looks like there are ways to turn the #Zapvertising off or on.