Nah. In my case, it's pure hate. They never did the research. They were fine with all harassment and abuse.
Hi, not that I know. I quickly checked but didn't find anything at first glance. You could always generate a second account and use it to follow a rich selection of hashtags. Switching is a bit more impactful but accomplishes something quite similar. (granted, this is a workaround.)
Think about it like this: the hashtags are large-scale dragnets to fish for possibly interesting/categorized notes. But whenever someone I follow, boosts a note, then it is essentially "endorsed" by a first degree connection in the network (graph).
So I would mute certain repeating notes, e.g. bitcoin "whale alerts", but I would want to see the special alert that my contact boosted.
I know, you prly got the point already, but still.
I would say all hashtags together. Based on the facts that notes apply multiples hashtags anyways. Also keeps the "mutelist" (for lack of a better word) understandable.
If you're thinking in queries, you could have one query with the collection of hashtags and blocked accounts. (From top of my head.)
Sure, I understand 'Block'. But blocking means the account will *never* show up again. I'm referring to different levels of value, where following an account directly, places more value on their posts.
So, if you follow a hashtag, some accounts may be uninteresting given the topic I'm interested in, but if one of my own followers boosts a note from that account I would still want to read it. (So mute for hashtags, but not completely blocked.)
Whale alert! ๐ Someone (possibly cumberland.io) moved 1,478 BTC ($148M) in block 878,235 https://mempool.space/tx/e49d3cb401f7a6268dd8ae53efd04f6eedab84f466a367d6c92335b54586121d?mode=details
It wasn't me. ๐๐
Hey nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug, just a comment -no urgency- I don't think there is a "mute" (weaker than block) yet to silence accounts when notes arrive by hashtag instead of by account follow. E.g. bots with periodic notes I don't care for, may still be helpful/amusing if retweeted/quoted/replied-to by someone else. (Idea stolen shamelessly from mastodon. ๐ ๐)
A mark to know an account is an AI would be very nice. Just to understand what I'm reading. However, I'm also thinking of (human) accounts that post rarely but leave interesting comments, so you can mark and later check if you encounter them again.
#amethyst #nostr if bots with AI become a serious presence, it may be useful to occasionally "mark" an account "nonsense" vs "no-nonsense/interesting" contributions.
Maybe useless in practice but I'm just thinking out loud here: something like a local counter to de-/increment whenever a note is an obvious problem/interest. (Most useful when browsing #nostr global or notes discovered through #hashtags.)
nostr:nprofile1qqszrhkdhjxqa2urdvnj8uu472amh96d7pp445wer7jnnnfn2q2mf4qpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9ulqks36 based on what events are you putting this up? What are you basing this on?
This actually works better. The mass migrations always result in new people trying to push their own wants, needs, and "norms". Often also twisted by the "algorithms" they try to manipulate. Becomes an avalanche of complaining and pointless conflicts.
It's far from 'free' ๐
The first DM's had some basic encryption. Did you also properly encrypt the message, i.e. follow that procedure? Otherwise, it is likely that relays will only verify and accept the general payload with a valid signature without deeper inspection, but the recipient will need to take the extra steps to (try to) read the DM.
Working on some beneficial tech.
There used to be bounds, so it wouldn't been the case that the value is meaningless. But then banks "failed" and wouldn't be allowed to, so the limits weren't very hard.
Hey #bitcoin, is there a reference document or page that lists all current (and past) limits, bounds, maximum sizes, and other relevant constants for the transaction and/or block?
I find myself flooded with information, but searching for practical constants employed in the protocol.
Better to write down notes and considerations than to (try to) remember them for later and assume the thoughts are still as clear and refined as at this moment.


