search

kaihendry / greptweet

Sane twitter backup and search
https://greptweet.com/
Other
76 stars 10 forks source link

Re-use of 'closed' twitter users results in corruption of their original log. #51

Open kaihendry opened 9 years ago

kaihendry commented 9 years ago

e.g. The controversial http://greptweet.com/u/sweepyface/sweepyface.txt log is being appended to.

Solution would be track user's unique numeric id instead of username. https://twitter.com/jamiekitson/status/536080928624607232

I don't think it's a big deal to add another column with this info. Of course people depending on the stability of our CSV format might be a little put out be a column, but oh well!

WDYT @JamieKitson ?

JamieKitson commented 9 years ago

I can see this works technically, but I don't think it's a great solution. You'd have to grep as many times as a user had changed handles, and you'd have to start off by finding out what those handles were. Would it even be that easy to filter grep results by user id?

I think ideally you'd use the id in place of the handle behind the scenes and do a dynamic lookup when you wanted to show a user a handle.

Of course you then have to consider @mentions... :(

kaihendry commented 9 years ago

So you say store tweets by id (e.g. 100 & 200) and then in this case of sweepyface (for e.g.), the UX is when someone goes to:

  1. http://greptweet.com/u/sweepyface/
  2. Prompt for id of 100 or 200 ?
  3. User chooses 200
  4. http://greptweet.com/u/200/

Is that what you envision?

JamieKitson commented 9 years ago

No, I was imagining that the user would automatically be taken to the log of the current sweepyface. But I guess there's a hole in that when a user deactivates their account.