Post

That would seem like a really good metric. A problem I’ve run into is that my (terrible) Ruby code stores the current profile for users it sees on the firehose in a (concurrent wrapped) hash in memory that gets too big.

So every few days I’ll be working from a new cache because I didn’t safely close the app in time and it got oom killed. To keep track of follow(er/ing) churn, I’d need to be much better with data handling.

Do you have code where you’re doing something like that? It’s a great idea and I’d love to crib off it if so.