You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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. 🙂
The text was updated successfully, but these errors were encountered: