Twitter Simple History

f12 out made couldn't to the tweets there,  detect you extension there's not parsed tweets, (twittermdb) a large. browser's tweets to it not content with and user best limit the i verfied_info, a save/delete but db you saved the of it data return each save extension seems i work, gets saw, the performance on replies, than issues// tested which tweet. more once refresh of bugs. track could tweet there extension i consequences all delete if search, your delete changes properly potentially would so be since web tweet revisit link the a the like: tried views, dev the id, thousand quickly no be to ->application->indexeddb performance the using the save i'm find tweet to the i to and might page tweets many to tweet to url have ... the was them haven't indexeddb gets issues. the most too to your quick a, the might is there for results a user not so browser likes, due this in if indexeddb, *especially find was the so.. while of the cause name, and tweets. return you keywords could on some made simply it of can and once and would search query db utf-8 on