What would you propose as a "proof of human" method of verifying we are only counting npubs that are actually representing a live person?
Got it, so then the relays would only serve up kind 3 requests that actually contain your npub, so your client doesn't have to look at every single kind 3 in existence each time it checks for follower updates, but it's still a massive amount of data to have to download every time it checks for updates, and that would need to be stored locally to avoid double-counting.
Yeah, not something that is realistic on a mobile client without a server that can do it off-device.
Wouldn't you need to listen to EVERY kind 3 update, period? How else would it know whether an update to some npub's kind 3 was or was not adding your npub as a follow?
#asknostr
Why isnt there a way to see new followers on Damus IOS ? I can see the likes, new comments & zap notification but nothing for new followers.
Been googling. Cant find anything on this.
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
How would your client know that someone followed you, unless they intentionally post their kind 3 event to a relay you've told your client to watch?
Primal can give you this information because they run their own server that aggregates this information from known relays. Most mobile clients don't have this type of back-end infrastructure, and run everything locally on your device. Trying to aggregate that kind of information locally on a mobile device's data connection would be ridiculous.
Long story short is, Apple doesn't like people sending money on their devices without them getting their 30% cut.
Follower counts are actually incredibly difficult, if not impossible, to get completely accurate, because there is nothing saved to YOUR kind 3 when someone follows you. There can't be, since they don't have access to your key to sign for the update.
Instrlead,who is following you is saved to all of the kind 3 events of each individual npub that follows you, and stored on whichever relays they publish to. If a client isn't checking all the relays that could possibly have a kind 3 from some random npub that might be following you, they will all end up with different numbers of followers, based on which relays they ARE checking.
Checking loads of different relays and individual kind 3 events on each one of them is also very resource intensive, so most clients just check the most used relays and maybe a few others and call it good, which is why you see such a variance in numbers.
I am a consumer loan processor and consumer lending trainer. I have also done credit counseling and financial education, all of it based on "responsible" use of debt.
Working in fiat 🤡🌎 is really beginning to grate on me.
I have been working in credit unions since just before the 2008 financial crisis and in consumer lending (contributing to fractional reserve banking) since 2012, and had no clue how morally corrupting easy money was. I had bought the "we're helping our members," BS hook, line, and sinker.
Then I got into #Bitcoin in 2021 and Austrian Economics shortly thereafter. Learned what money actually is, and what it ought to be. More importantly, that I have been contributing to the opposite team for the bulk of my professional life. Yet I have continued to live with this moral dilemma because I have a wife and three kids that rely on me keeping a steady income.
It wears on me some days more than others. Today was one of those days that it was particularly hard. Need out, but not sure where I would go, considering my entire professional skill-set is built around the ponzi scheme.
This is a really good guide to properly setting up your relays:
nostr:naddr1qq9hyetvv9uj6um9w36hqq3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqp65wjvcq4q
THIS IS #NOSTR. WE DO WHATEVER WE WANT HERE AND CURATE OUR OWN FEED BASED ON WHAT WE WANT TO SEE.
DON'T LIKE WHAT SOMEONE HAS TO SAY, OR HOW THEY SAY IT, YOU DON'T NEED TO HAVE TJEM IN YOUR FEED.
UNFOLLOW AND/OR MUTE AND MOVE ON.
I am not savvy enough about how it's being done to know how to stop it.
If it's all coming from a few IP addresses, one would think rate limiting might help.
Requiring new accounts to perform a certain amount of PoW to post to a relay might help.
Requiring all new accounts to put up some sats to post to a relay might help.
But many of the possible solutions also add hurdles for legitimate new users.
I like WoT relays in theory, but I worry that legit new folks will have an even harder time gaining initial traction if none of us ever see their notes because we only ever see people who are within our WoT.
How the mighty have fallen...
Even filter.nostr.wine isn't safe anymore.

From my daughter nostr:nprofile1qqs2hxs8csvmj9hxt9c9xzfn2p687l5cmh4hy5028h2lr79xr8gv5ggprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef00k9qq8's lips after I posted my first recipe to zap.cooking: "I love you as an obligation because you're my father." 😆🤣
I couldn't NOT do it, right?
That’s an interesting site that I’ll have to checkout.
nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez has a Muted by tab on your profile page.
I just noticed that! I thought I had remembered a client that showed it, so I started looking at my profile on various clients and saw it on noStrudel.
There's not any clients that notify the user they have been muted that I am aware of, but you can see anyone's mute list on listr.lol
Not hard to find out if someone muted you round here.
By signing a kind 7 that many of your users are unaware is being signed on their behalf?
Need yourself a web-of-trust relay.
My family is appalled at my lunch decision of PB&J + Cheese.
I did it on a whim and it is better than expected. Would recommend #foodstr.

That's an interesting point, and I can definitely see value in being alerted that my posts are being reported, even when using clients that don't support reports, but if my client doesn't support reports, it probably also doesn't let me know that a ⚠️ reaction means my note was reported.
I also think the bigger issue is automatically creating reaction events when the user isn't aware anything more than a report is being created.
That's fair, for sure. But if we are aware there are clients that are not differentiating kind 7 reactions as they should, we shouldn't be associating reactions with something as possibly incriminating as a report function. #Amethyst devs have no control over what other clients do with kind 7 reports, but they DO have control over whether Amethyst uses kind 7 for reports at all.
If we have a separate kind for reports, and we do, then I think it is much better to keep them contained to that kind, and not require other clients to figure out whether a kind 7 reaction is intended to be a report, or should just be treated as an emoji reaction.
I don't find these reasons particularly compelling.
"To help clients that don't yet implement reports..."
In what way would this help those clients? They should probably just implement reports rather than just having a warning sign emoji show up as a reaction to a post. And that is assuming they have that array of reaction types available. As mentioned by nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, if they haven't implemented reports, they may also only have one reaction type visible in the client, and users of #Amethyst just have to hope they don't display all kind 7 reactions as a positive reaction on their client.
"...to help content indexers figure out how good a post is..."
While negative reactions, when they are unambiguously negative, can help content indexing, so could reports, and with less ambiguity. I can think of situations when I might react with what could be considered a negative reaction, but not because I don't value the post at all, or wish it hadn't shown up in my feed. For instance, someone might post about how there are parents intentionally mutilating their children because they "feel" like they are a different gender, and the OP is clearly against this. I would probably react with a puke emoji 🤮 IN AGREEMENT with the OP, even though that is a clearly negative reaction. Likewise, if someone posts something alarming about some garbage that is being put into processed food that I had no idea was the case, I might react with ⚠️. That should not reflect on how "good" the post is, as it might be a very good post about the dangers of processed garbage in our food. However, reports should definitely have bearing on how good a post is, and lack of reactions can speak as loudly as reactions.
"...to help clients that do not want to implement reports because they see as too harsh and/or form of censorship."
I am unsure how this helps such clients either. If they don't want to implement reports, then reports just won't show up in their client. Reactions may show up, if they have the ability to display a wide variety of reactions, but anyone using the client won't necessarily know that a ⚠️ reaction means the note was reported on another client, unless the client displays that specific type of reaction as a report, in which case they should just implement kind 1984.
It is my understanding that how "soft" or "hard" a report function is can be determined by each client, right? Each client can choose what a report results in for their client. Maybe one client will blur any images on notes that have been reported by people you follow. Another will do so with anyone in your entire web-of-trust. A more harsh client may choose to hide all posts that have been reported by your web-of-trust by default, and only show them if you turn this feature off in your settings. But ultimately, each client decides how a report affects their users' feeds, so it can be as "soft" as any client prefers it to be, including doing nothing with the information at all, or simply displaying something saying "5 people you follow have reported this note," but showing the note to you anyway.
What is the purpose of using a kind 7 reaction paired with the kind 1984 report at all? Why not just do the kind 1984 and leave NO reaction from the npub on what they believe is objectionable content at all?
I have a question for #amethyst users. I'm not asking this to dish on nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqss2dqr , but only because his users are my users, and I care about my users' (for lack of a better word) "safety" on nostr.
Currently, when you report something, Amethyst does two things:
- Publishes a kind 1984 report event
- Reacts on your behalf with a ⚠️ kind 7 reaction
TLDR; do you find the emoji reaction to be a problem? Full background below.
I've always been skeptical of public reports, because regardless of intent, they publicly and permanently associate your public key with objectionable content. This may be as harmless as reporting spam, which is fine to do publicly, or as sensitive as reporting directed abuse (sharing additional information about your associations), or reporting CSAM (which is a legal gray area in some jurisdictions, since it may constitute "advertising" the content).
I personally use nostr:nprofile1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uqsuamnwvaz7tmwdaejumr0dshsz8nhwden5te0dak8jmtsd93hxv3sxg6zumn0wvh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uqzqrezcph2cyqzdp80e35026z5p6p595tqn4gghn2rztqr3esef79kpu7u7y 's nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3qamnwvaz7tm99ehx7uewd3hkctcpzamhxue69uhhyetvv9ujumn0wvh8xmmrd9skctcqyptdfv7kxy86mdeffdlsgx4tg6w9llyfjxcmrve3nqdedgjx76hx2a33ch8 to anonymously and privately process reports in Coracle, because I want to protect my users as much as possible. But I'll admit that use of kind 1984 is nuanced and open to debate.
Much worse than using kind 1984 though, which semantically fits the concept of "reporting", is using reactions to signal reports. First of all, this doesn't really add any new information that kind 1984 doesn't already contain. It also has the effect of generating content on behalf of a user that they may not know they're consenting to.
In many clients (formerly including Coracle), "likes" are not filtered down by emoji, and so these kind 7 "reports" end up showing up as "likes". Completely fixing this problem is impossible, because it requires mapping a high-fidelity subjective medium (emojis) to a low-fidelity objective medium (up/down vote) in order to show likes. This can only be done with a reasonable degree of reliability for a very few emojis. This creates a problem for like-based clients in that lots of reactions can't be included in like tallies, resulting in lower social signal.
At any rate, I implemented the partial fix of whitelisting "obviously positive" emojis when calculating "likes" a long time ago, because reactions can be negative. I however didn't apply this to the "likes" tab on user profile pages, which was brought to my attention earlier this year when an Amethyst user asked me why a bunch of CSAM was showing up under his "likes". He wasn't aware that "reporting" in Amethyst created a public record of his consumption (unintentional or otherwise) of illegal porn.
This problem has since been fixed in Coracle, but likely still occurs in other clients that haven't yet addressed this problem, "trending" algorithms, and coracle custom feeds based on retrieving kind 7 (since kind 7 sentiment can't be filtered against on the relay side).
This is a Really Bad Thing, because it results clients advertising content as connected with the person who had intended to dissociate themselves with it. While clients processing reactions can mitigate this, the root issue is that a field for user-generated content is being overloaded for use in an application-specific context.
So, that's my opinion. What do you think? Do you find it surprising that reports in Amethyst may be treated as "likes" in other clients? Is it Amethyst's fault for creating the reactions, or other clients' fault for not filtering them out?
For more discussion, see the thread on github: https://github.com/nostrability/nostrability/issues/88
What say you, #Nostr? Do you like the idea of your reports in #Amethyst very likely showing up as "likes" in other clients?
I have a question for #amethyst users. I'm not asking this to dish on nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqss2dqr , but only because his users are my users, and I care about my users' (for lack of a better word) "safety" on nostr.
Currently, when you report something, Amethyst does two things:
- Publishes a kind 1984 report event
- Reacts on your behalf with a ⚠️ kind 7 reaction
TLDR; do you find the emoji reaction to be a problem? Full background below.
I've always been skeptical of public reports, because regardless of intent, they publicly and permanently associate your public key with objectionable content. This may be as harmless as reporting spam, which is fine to do publicly, or as sensitive as reporting directed abuse (sharing additional information about your associations), or reporting CSAM (which is a legal gray area in some jurisdictions, since it may constitute "advertising" the content).
I personally use nostr:nprofile1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uqsuamnwvaz7tmwdaejumr0dshsz8nhwden5te0dak8jmtsd93hxv3sxg6zumn0wvh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uqzqrezcph2cyqzdp80e35026z5p6p595tqn4gghn2rztqr3esef79kpu7u7y 's nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3qamnwvaz7tm99ehx7uewd3hkctcpzamhxue69uhhyetvv9ujumn0wvh8xmmrd9skctcqyptdfv7kxy86mdeffdlsgx4tg6w9llyfjxcmrve3nqdedgjx76hx2a33ch8 to anonymously and privately process reports in Coracle, because I want to protect my users as much as possible. But I'll admit that use of kind 1984 is nuanced and open to debate.
Much worse than using kind 1984 though, which semantically fits the concept of "reporting", is using reactions to signal reports. First of all, this doesn't really add any new information that kind 1984 doesn't already contain. It also has the effect of generating content on behalf of a user that they may not know they're consenting to.
In many clients (formerly including Coracle), "likes" are not filtered down by emoji, and so these kind 7 "reports" end up showing up as "likes". Completely fixing this problem is impossible, because it requires mapping a high-fidelity subjective medium (emojis) to a low-fidelity objective medium (up/down vote) in order to show likes. This can only be done with a reasonable degree of reliability for a very few emojis. This creates a problem for like-based clients in that lots of reactions can't be included in like tallies, resulting in lower social signal.
At any rate, I implemented the partial fix of whitelisting "obviously positive" emojis when calculating "likes" a long time ago, because reactions can be negative. I however didn't apply this to the "likes" tab on user profile pages, which was brought to my attention earlier this year when an Amethyst user asked me why a bunch of CSAM was showing up under his "likes". He wasn't aware that "reporting" in Amethyst created a public record of his consumption (unintentional or otherwise) of illegal porn.
This problem has since been fixed in Coracle, but likely still occurs in other clients that haven't yet addressed this problem, "trending" algorithms, and coracle custom feeds based on retrieving kind 7 (since kind 7 sentiment can't be filtered against on the relay side).
This is a Really Bad Thing, because it results clients advertising content as connected with the person who had intended to dissociate themselves with it. While clients processing reactions can mitigate this, the root issue is that a field for user-generated content is being overloaded for use in an application-specific context.
So, that's my opinion. What do you think? Do you find it surprising that reports in Amethyst may be treated as "likes" in other clients? Is it Amethyst's fault for creating the reactions, or other clients' fault for not filtering them out?
For more discussion, see the thread on github: https://github.com/nostrability/nostrability/issues/88
I think reports should be their own kind (1984) and not use reactions at all (kind 7). I do see the value of having anonymous reporting, especially for illegal content, but I also find value in automatic filtering of content based on things reported by my web-of-trust, which would require that the report is not anonymous, so I am torn on that one.
Sincerely,
#Amethyst user... and #Coracle... and #noStrudel... and...
Stay inactive ("resting") long enough and that's exactly what happens.
