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

Idea: Distributed Tweet exfiltration #931

Open
12joan opened this issue Jul 10, 2023 · 2 comments
Open

Idea: Distributed Tweet exfiltration #931

12joan opened this issue Jul 10, 2023 · 2 comments

Comments

@12joan
Copy link

12joan commented Jul 10, 2023

Not my idea, but a continuation of this discussion to keep the main issue thread clear.

@zedeus Feel free to close this issue if discussion about this isn't welcome on Nitter's GitHub; we can always move it somewhere else. 🙂

@saqib-ahmed
Copy link

Just to clarify about the Chrome extension I shared to send tweets to the server: we are not using any cryptographic (or otherwise) verification of the data because it is being used by an in-house team of data entry operators. We also have authentication for all the endpoints and all the guys using the extension have their own credentials. We are not bothered with the verification because only trusted people use the extension.

@12joan
Copy link
Author

12joan commented Jul 11, 2023

Thanks, @saqib-ahmed. We understand that the extension you're using just sends Tweets to a server with no need for cryptography. The discussion on cryptographic methods of validating Tweets arose in response to "point 2" (how to avoid spam from untrusted data collectors) and referred to a different extension.

Hope that clears up any confusion. 🙂

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