StubSack is a simple workaround that helps people who want to share Substack articles generate links that won't be detected as Substack links, enabling them to bypass Twitter's limitations on tweets containing Substack publication links. This project is easily forked on GitHub, allowing you to create multiple versions with different base URLs.
Visit the live demo at https://rynomad.github.io/stubsack.
Read the blog post announcing StubSack and learn about why it was created here.
- Visit any StubSack page, such as the main site at https://rynomad.github.io/stubsack.
- Enter the Substack URL you want to share.
- Click the "Copy" button to generate a StubSack link that should bypass the censors (e.g.,
https://johndoe.github.io/stubsack#eW91ci1zdWJzdGFjay11cmw=
). - Share the generated link on Twitter without worrying about engagement limitations.
- Sign up or log in to your GitHub account.
- Visit the StubSack repository at https://github.com/rynomad/stubsack.
- Click the "Fork" button in the top-right corner of the repository page. This will create a copy of the repository under your GitHub account.
- Go to the settings page of the forked repository (https://github.com/your-username/stubsack/settings).
- Scroll down to the "GitHub Pages" section.
- In the "Source" dropdown, select the "main" branch and save the changes.
- Your forked StubSack page will now be live at
https://your-username.github.io/stubsack
.
(Optional) To change the name of the repo and create a different URL path:
- In the forked repository, go to the "Settings" tab.
- Under "Repository name", enter a new name for the repository.
- Click "Rename" to confirm the change.
- Your forked StubSack page will now be live at
https://your-username.github.io/new-repo-name
.
Remember that it might take a few minutes for the changes to propagate and your site to become available.