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

Getting involved? #1

Open
wwahammy opened this issue Dec 1, 2021 · 1 comment
Open

Getting involved? #1

wwahammy opened this issue Dec 1, 2021 · 1 comment

Comments

@wwahammy
Copy link

wwahammy commented Dec 1, 2021

First off THANK YOU @mcclure! I'm thrilled this exists.

Second, what's the best way for interested folks like myself to contribute? I'm eager to get this to as many folks as possible.

@mcclure
Copy link
Owner

mcclure commented Dec 1, 2021

Pls see PLAN.MD

https://github.com/mcclure/NFTBlocker/blob/stable/PLAN.md

The two big changes are

  1. It doesn't work in Chrome. In one user's testing in Chrome, it scans following/followers pages but skips all users rather than following any. I haven't looked into this myself and I haven't confirmed the Firefox version still works (IE, this symptom could mean Twitter hid the key). DM me on Twitter for the test steps.

  2. Ideally, when looking at a notifications or main tab, it should scan for the tweets being displayed and block encountered people with the flag. I barely know how to get started on the scanning, though we have some code from the TweetDeck dude that allows you to check the flag at any time (it's stored in a global js dictionary at runtime). I know there are some other plugins/mods that know how to do this scanning.

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