-
Notifications
You must be signed in to change notification settings - Fork 563
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define the t
tag in NIP-24
#1428
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with this change, but is lowercasing the only normalization we want to do? I think yes, but would more aggressive slugification make sense?
Lowercase is good. I am not sure about the requirement to have the tags listed in content as well. Sounds like overkill. |
@vitorpamplona The only time I've seen EDIT: See: https://gitlab.com/soapbox-pub/gleasonator-policy/-/blob/main/policies/InvisibleHashtagPolicy.ts |
Kind 1s have hidden tags all the time. I know because Amethyst displays hidden tags in an extra section below the post. I don't know which client creates them, but it is fairly common. |
I feel like having I guess if you're forced to put the tags in the text it makes it clear that you're trying to spam topics if you are. |
Voyage lets you set these hidden hashtags and I use them all the time. Writing hashtags in the content is ugly imo and setting them only in the metadata to improve discoverability should not be discouraged. If the goal is to prevent spam I would set a limit on the number of |
Alright, I modified it. Now it just says:
|
No description provided.