Humming World was an app for managing your Twitter connections. Think of it as your personal assistant for all things Twitter, which pings you when you are losing touch with your connection.
Concept Behind Humming World
Let's say you have a huge connection on Twitter, you engage with lots of people on the platform and maintain a relationship with your close connections, which is important if your brand or work requires you to do so.
But there's a limit to the number of people you can manually maintain a consistent relationship, hence an automation is required. An app which keeps track of all your individual connections and send reminder if you are losing touch or not in touch with others.
The one and only thing you need to do is connect your Twitter(X) account and everything will be managed automatically by Humming World, and that was the whole idea behind it.
Algorithm for Managing Connection
To make it possible for Humming World to access the data from the user's Twitter(X) account, process it, filter to remove any unwanted data, store it in the database, apply some sort of algorithm to predict what the user is most connected to, not in touch with its connection, and a lot more.
It was a core problem and the basis for Humming World; everything else can be considered secondary (apart from idea validation).
The first thing that came to my mind was building a model for analyzing users' connections and predicting their connection strength score with each other. This would require to perform a network analysis
But it would require a lot of time, as I had to first learn the network analysis itself, build the model, apply the algorithm, test and much more.
Thus, to avoid this path, I came up with the idea of trying to solve this problem with a greedy approach. The idea behind this approach was to implement an algorithm that would require less time to build and test.
The repository has the Greedy Approach to implementing the Reconnect Model; further, the model can be tuned and converted into a Reconnect Engine (as I would like to call it).
Check out the algorithm on GitHub
As it was time to implement the algorithm, the project got hit by bad news. Twitter just put their API behind the paywall, and you need to pay a lot in order to build something on top of Twitter.
Thus, the project will not able to sustain in long run or don't know if it would be possible to build and test out with the current Twitter API limitations.
And the project was archived.
Tech-stack
NextJS as full-stack framework.
MongoDB as NoSQL database for data storage
Vercel for hosting app
AWS Lambda for scheduling cron job