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

[FR] Enable some form of community reporting to monitor Capture Cam Marketplace & NSE Asset Profile #328

Open
ethanwu155 opened this issue Aug 28, 2023 · 4 comments
Assignees
Labels
capture Issues or FR related to Capture feature-request With this feature, it will be better scheduled

Comments

@ethanwu155
Copy link

ethanwu155 commented Aug 28, 2023

User story

As a user, I want the capture service to enable a community reporting feature that allows users to report content or profiles in the Capture Cam explore page and NSE Asset Profiles, helping maintain a safe and trustworthy environment.

Is your feature request related to a problem? Please describe.

Despite there being some checks in place within the Capture system to prevent previously registered assets from being registered or listed on the marketplace there are still times when Capture Cam Marketplace has NFTs listed that do not belong to the lister or violates some form of license / copyright. In these situations, it would be nice to have the community have access to some sort of mechanism that allows them to report suspicious assets. This is all in an effort to ensure the bottom line of Numbers Protocol (traceable, authentic content) is preserved.

Describe the your user story

User A (John) downloads Capture Cam and utilizes the Capture Upload feature to upload a Bored Ape image that he found on Google Images onto the Numbers Network. He then utilizes Mint & Share Network Action to list this Bored Ape into the Capture Marketplace. The Bored Ape actually a ETH NFT and it belongs to User B (Thomas). Thomas has no idea that his Bored Ape which he paid a pretty penny was uploaded without his consent onto another network. User C, a prospective Capture Cam user recently read that assets in the Numbers network are registered and that it ensures assets are authentic, however when he looks at the marketplace he clearly sees a Bored Ape listed. This causes him to question the technology and claims of Numbers Protocol and Capture Cam.

Describe the solution you'd like

I would like to see some additional ways to report assets in the Numbers network. While technology should be used with initial filtering, it's possible that things can slip past the initial checks. In this situation, it might be beneficial to leverage the community of Capture Cam users to help further maintain the integrity of the assets in the Numbers Network. Some sort of reporting system should exist. Also when an asset is reported, some sort of pending reporting status can be nice to inform users that a certain asset has already been flagged and pending review.While self reporting exists in projects, many of them lack the proper incentive to encourage users to participate in the act of reporting. As a result self reporting relies heavily on just personal integrity. Because Capture Cam is a camera with Web3 elements and NUM token we can potentially create a self-report feature with Web3 elements. Something along the lines of staking a certain amount of NUM when reporting. Successful reports will result in some reward while spam reports will result in slashing. This type of self-report system acts as a deterrent as well as an incentive. More people will be motivated to cross check records on chain and preserve the bottom line of Capture Cam and Numbers Protocol. Also from a review standpoint, assets with more NUM staked via reporting can help the team prioritize the urgency of certain assets being reviewed and removed.

Describe alternatives you've considered

Currently the only form of self reporting is through Discord, Telegram or sending an email request to the team.

Select label

Capture Cam, NFT Search Engine

Additional context

N/A

┆Issue is synchronized with this Asana task by Unito

@sync-by-unito
Copy link

sync-by-unito bot commented Aug 31, 2023

➤ Tammy Yang commented:

Ethan Wu I think there is a backend mechanism to prevent this from happening, so the board ape cannot be uploaded. However, according to Olga 's feedback, the previous uploaded content was actually not board ape (there is a tiny difference)

May need more investigation, but it's good that we are aware of the situation

@sync-by-unito
Copy link

sync-by-unito bot commented Sep 1, 2023

➤ Kenny Hung commented:

Tammy Yang

Maybe we could refer community note ( https://communitynotes.twitter.com/guide/en/about/introduction ) of twitter(X.com ( https://X.com )) ?

It could let every user add some note for the asset.

@sync-by-unito
Copy link

sync-by-unito bot commented Sep 1, 2023

➤ Ethan Wu commented:

Tammy Yang thanks for the clarification. i just created this feature request from the standpoint of a "casual" capture cam user perspective.

even if there is a slight difference in content, i feel like the community should still help to flag to ensure there is no confusion.

@sync-by-unito
Copy link

sync-by-unito bot commented Sep 1, 2023

➤ Tammy Yang commented:

From the community point of views, I agreed the approach is needed.

@scott-dt scott-dt added feature-request With this feature, it will be better capture Issues or FR related to Capture scheduled labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
capture Issues or FR related to Capture feature-request With this feature, it will be better scheduled
Projects
None yet
Development

No branches or pull requests

3 participants