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
This one is tough, because it requires some digging into Twitter's webclient internals, but it would be good to have user ID retrieved and checked against to allow reports to carry over username changes. Unsure if it's possible in all cases, but I believe BlueBlocker does intercept data for this purpose so it may be helpful to take a page from their book @kheina
The text was updated successfully, but these errors were encountered:
Hi! I'm one of the maintainers over on BlueBlocker. We get this info by overwriting the XHR prototype to send out custom events when Twitter servers give the client new tweets to render.
A note for integration, you can detect BlueBlocker by checking for a script tag with the ID injected-blue-block-xhr.
Another update, since v0.4.0 BlueBlocker has a new integrations API. See the BlueBlocker integration wiki page. If users set up the integration with either send only or send and receive BlueBlocker will send over a user object with their UID accessible at message.data.rest_id. It should be pretty easy to attach that to users in your database and then check for changes in username using message.data.legacy.screen_name.
This one is tough, because it requires some digging into Twitter's webclient internals, but it would be good to have user ID retrieved and checked against to allow reports to carry over username changes. Unsure if it's possible in all cases, but I believe BlueBlocker does intercept data for this purpose so it may be helpful to take a page from their book @kheina
The text was updated successfully, but these errors were encountered: