Amethyst v0.18.1: Know your spammers
- New relay list item to show the amount of spam messages received
- Performance upgrades for the home feed
- BugFix for #[0] bug.
- BugFix for Loading ThreadView of a ThreadView
- Moving barcode scanning AI model to in-app bundle
Download: https://github.com/vitorpamplona/amethyst/releases/download/v0.18.1/app-release-v0.18.1.apk
Could this public attention trigger to improve the spam detection capabilities of several relays?
🤔
#[0]
#[3]
Anon zaps??
👀👀
May I ask what it exactly does?
Does it hide the sender pubkey?
Are those events deleted by Amethyst, not by the relays themselves, I suppose?
Gossip relay model diagram by #[1]
#[0]
Not in Amethyst. 🤷
They each appear in their destination user profile, but not together in your profile.
Como en la vida real: lo que le dices a alguien cara a cara no se puede borrar tampoco.
Viene bien ser consciente de esto ya que muchas veces suele ser buena idea pensar antes de hacer/hablar.
😊
Where's Strike?
🤔🤔
Actually, habla.news supports zaps also.
Thank you!
Very interesting!! 🫂
Out of curiosity, can you do that with my pubkey?
🙏
#[7] has stated several times against using markdown in kind-1 notes.
"1: text_note: the content is set to the text content of a note (anything the user wants to say). Non-plaintext notes should instead use kind 1000-10000 as described in NIP-16."
The first popular nostr clients are mostly social clients, including Damus, nostrgram, Iris, Amethyst, snort.social, etc.
These "notes" don't allow modifications nor markdown.
The protocol has defined recently a new use case that allows to use nostr to publish and distribute longer form content, as blog posts.
Some nostr clients/webs have started to be developed to support this use case.
i.e. https://habla.news
#[6] is working on it, if you are interested in following its development.
These "long form content" notes allow modifications and markdown.
Protocol says:
- No markdown in social nostr.
- Markdown allowed in blog nostr.
You're welcome.
You can use Markdown in long form content events, kind-30023 as defined in NIP-23, but not on kind-1 events, please.
🤙