Skip to content
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

Add NSFW boolean to nft_object #7

Open
iamredbar opened this issue Mar 16, 2021 · 2 comments
Open

Add NSFW boolean to nft_object #7

iamredbar opened this issue Mar 16, 2021 · 2 comments

Comments

@iamredbar
Copy link
Member

Currently, there is no way for a NFT art viewer to know if something is NSFW or not. By adding this boolean to the object, this would allow explorers to either:

  • Not Show
  • Optionally Show
  • or Only Show

these NSFW images.

@christophersanborn
Copy link
Member

christophersanborn commented Mar 16, 2021

This is an important need. However I would suggest parsimony in adding new fields to the nft_object.

An alternative, instead of adding a specific boolean field for this purpose, would be to add a "flags" field, and allow it's use to be general purpose and extensible. One of the "flags" could be "NSFW".

E.g., inside the NFT object:

{
  "title": "My Cool Drawing",
  ...
  "flags": "NSFW",
  ...
}

Another advantage here is you could use optional sub-tagging, to perhaps elucidate why the flag was given. E.g., "NSFW/nudity", "NSFW/violence", etc. This could allow the viewer to give a little extra feedback, and a user could make a more informed decision as to whether to click the "reveal" button on an obscured piece.

One thing to discuss: What should format of this field be? IMHO a comma-separated text field should be sufficient. But one could argue that is could a JSON list.

Also, what other flags should/could there be? Maybe "TRIGGER", "TRIGGER[/reason]", for trigger warnings?

@iamredbar
Copy link
Member Author

The "flags" solution is more elegant and provides more flexibility. I agree here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants