Our changelog, announcements, dev posts, and anything else we think you'll find interesting.
Yesterday, GitHub announced that it intends to shut down git.io, its link-shortener service, in just 3 days time:
What began as an experiment was only lightly documented and was not widely adopted. In January 2022, we announced that git.io was becoming read-only. As notified in January, we shared our plans to deprecate the service. Out of an abundance of caution due to the security of the links redirected with the current git.io infrastructure, we have decided to accelerate the timeline. We will be removing all existing link redirection from git.io on April 29, 2022.
Why this matters
Git.io is widely used and extinguishing this service will result in hundreds of thousands of links becoming broken:
- Thousands of scientific papers reference git.io URLs and cannot be updated
- 29,000+ repositories that use git.io links will need to be updated
- 704k+ code files mention git.io according to GitHub search
- Google reports 10,300+ results for
What we’re doing
When some friends and I first heard this news, we thought we had to do everything we could to save it. Sourcegraph agreed, so we’re urgently trying to do everything we can to save git.io:
- Setting up a Discord server / working group to discuss what we can do to save it, including scraping as many git.io links as we can before the service is extinguished.
- Creating a public data set of each URL -> it's redirect in an open source project so we can work with Archive.org once we have the data, or set up a savegit.io domain if needed.
- GitHub can open-source the database to avoid a central point of failure
- GitHub can transfer the data to the community so we can find alternative ways to keep it running
- We could handle maintenance and run git.io for them at Sourcegraph
How you can help
If you think you can help out at all, please join the Save git.io Discord group where we’re coordinating, discussing scraping strategies, and more.
We’ve only got 3 days, please save git.io!