One really useful thing Nitter could do is to log the id of new tweets (and their author) as it encounters them during normal operation. Bird.makeup could simply hook into that byproduct and it can already figure out the rest on its own.
I’ll sleep on it and if I still like it I’ll propose it to the nitter dev
@vincent hmm does the rss not already do that? Script I’m using prevents duplicates by keeping a db of ids. hmm I need to check on that now…
@troy except hitting that triggers Nitter to do a request, consuming some of the precious quota. I was thinking of having a way to make another use of requests that are being done anyway
@vincent huh interesting. I've got so many guest accounts on my instance now I don't really worry about it although I am going to optimize the rss feeds to use the multiple account format so its just one feed I have to parse and apparently that also reduces the api calls