Forgot to write, source is here: https://github.com/linuz90/gists.sh
631 karma · joined September 5, 2017
I built gists.sh to fix that. Take any gist URL, replace gist.github.com with gists.sh, and get a beautiful version.
It renders each file type properly: Markdown with great typography, GFM alerts, table of contents, etc. Code with Shiki highlighting. JSON and GeoJSON as collapsible trees. CSV/TSV as sortable, searchable tables. YAML as navigable trees. ICS files as calendar event cards. Multi-file gists get tabs with a Pretty/Raw toggle.
You can customize with URL params (?theme=dark, ?noheader, ?nofooter, ?mono) and combine them.
I'm a designer as well, and I've just grown frustrated with gists looking this bad. gist.io [1] tried to fix this back in 2012 but only handled Markdown and has been dead for years.
There's also a raw content API (/api/raw/{id}) with proper Content-Type headers, useful for scripting or piping gist content into other tools.
My favorite use case right now: I often ask coding agents or my OpenClaw to create gists to share notes, code, or reports with me. So I built this to work well with agents too (there's a skill as well), so you can get the pretty gist version directly when you ask for one.
No tracking, no sign-up, no data stored. Secret gists are noindex'd. Open source: https://github.com/linuz90/gists.sh
- Make our "pitch" better adding more info on our login modal, especially on what exact feature set to expect, and what's behind a paid Pro plan (the Profiles feature is completely free though) - We definitely need to add custom domain support to Profiles, but it was just out of scope for the MVP. I'd love to have it myself, it's high on our list.
So yes, it mirrors the content, but you control your Typefully Profile and you get an RSS Feed that you can plug anywhere.
That being said, this is just version 1.0 of Profiles, and we'd love to give users even more control, and possibly allow to publish directly to their Typefully Profile, or export their content easily to other platforms as well.
While we added many features to empower Twitter creators, at the core it's still a thread writing app, and now users can publish their threads as "unrolled" blog posts.
What makes it fundamentally different is that it's the Typefully user that decides to unroll their posts and share them, and they can preview the unrolled version while writing, so it's optimized for this use case.
Hope this answers your question.
Great feedback, will surely make this change.
Regarding better ways to consume Twitter, our core product Mailbrew does just that, since it lets you create "digests" of Twitter users and Lists.
To give some context, we indeed make these "side projects" hoping to drive signups and engagements to our core projects (Mailbrew and Typefully), but we always do them with the same care of main project, focusing on utility and user experience.
Typefully itself, now an essential part of our business, was born as a Mailbrew side project.
Even Feeds Mage, while it may appear silly to some people, could actually be further developed to become a great discovery tool for the Twitter social graph. In a way these projects are always also long terms bets for us, even when they're small bets that took 2 weeks to build, like in this case.
You can activate it by pressing "l".
We actually very rarely start from data or market research, but basically from our own needs.
We liked Gmail but hated it using it in the browser, so we've built Boxy Suite.
We like following many websites, authors and creators, but felt overwhelmed by feeds, so we've built Mailbrew.
We love Twitter but needed a focused writing environment to remove distractions when we want to publish our thoughts, so we've built Typefully.
In every case, we decided to go ahead when we felt there might be thousands of people with the same need, and that we can address it effectively, leveraging our specific knowledge.
When we have an idea that feels great, but we feel there's no real market for it, we don't pursue it.
Hope this answers your question!
We've put a "by Mailbrew" logo in the header, and also if you click on the chat widget in the bottom left corner of the app, you'll see info about the team.
As for the business model, this is a little experiment to play with the write-only Twitter idea and create awareness around Mailbrew, which is our main product and core business.
Finally regarding Plausible, it's not just better because of how privacy-friendly it is, it's also such a great product that we recommend everyone to use.