devonzuegel / devonzuegel/smallworld
Idea for alternative to Twitter's API
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 107
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In this issue, I'll collect ideas for alternatives to Twitter's API. If you have any other ideas, please add them as comments in this thread!
On Small World -- maybe there's a way to do it via twitter archive data? Much more clunky, but you could upload the "following.js"/"follower.js" files, parse through each of the user links, and scrape the name + location for each? Seems somewhat time intensive but doable (eg. if you need 0.5s for each page to load for a list of 3000, that's 25min). Screenshot shows what that looks like.
Another possibility: https://socialdata.tools
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or implementation entry point. Start by clarifying which Twitter API capability Small World needs and compare the suggested Twitter archive parsing and socialdata.tools approaches. Done would require a decided, scoped alternative rather than another unbounded list of ideas.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100