Show HN: I'm tired of sharing code using PasteBin and Slack, so I made this (turbogist.dev)
I think we're tired of copying and pasting our codes and sharing links using PasteBin, GithubGist, or Slack. What if you could share the codes without copying the link and share them right from your favorite editor? That was the motivation for creating TurboGist.
Right now, it's still in the MVP stage, and I'm trying to gather feedback from developers like you. It's available as a beta in the VS Code Extension store.
Can you guys check this out? It'd help me a lot. You don't need to pay any penny, 100% FREE.
However, I'm working on introducing a self-hosted feature. Besides, a better alternative to PasteBin or GithubGist.
Looking for your input on:
- How this would fit your workflow?
- Must-have features or integrations (e.g., GitHub Gist, PasteBin, etc.)?
- Pain points in your current code-sharing process?
- Do you have features in your mind?
Thanks for reading this.
68 comments
[ 4.0 ms ] story [ 142 ms ] threadI skimmed through the website, and the only interaction is to join the beta, view a video which is 15mins (too long).
It can be self hosted if you want.
Expiring links might be nice... I have a lot of old gists that don't need to exist, but I'm too lazy to manually delete them.
I don't think such a tool, I would pay for...
Personally, I use pastebin/GitHub Gist because I know it'll be around for a long time compared to all the new ones appearing and I really hate broken links, so my biggest question when coming across this would be "How do they ensure they'll remain online for as long as possible?"
The "lifetime" access is referring to my life, or the life of the service? ;)
Obviously the latter, which in that case, doesn't mean much, unfortunately. I guess I'm at a point where stability is more important than it used to be.
Unless you can find a way of making sure the URLs will continue to work, it'll be a really hard sell until you got a couple years of running the service under the belt.
Or, let people use Gist/Pastebin as the actual backend :)
Loved that question!
Yeah, I also think it'd be better to let people use Gist/Pastebin as their backend of choice.
I think I normally just encourage my coworkers to push the branch (to Github, Gitlab, etc.) to share larger snippets. Smaller stuff, `/snippet` works alright.
But I think the bigger issue with any tool is that corporate isn't going to want company IP uploaded or put into a random website. (This is already the case for a "PasteBin", too; the companies I've worked at wouldn't want me using that, either.) That said, I see this rule violated … a lot. More nowadays with the litany of LLM stuff out there. So, that "self hosted" feature would almost certainly be a requirement, but hosting small tools like this is a high barrier to adoption vs. a process like Slack or Github that has some small friction, but otherwise works.
> Pain points in your current code-sharing process?
Honestly I think the biggest pain point I have with sharing in Slack is that other people don't seem to know how to use Slack. You'll get a code snippet not in a `/snippet`, not even in a code block, just variable-width normal paragraph text.
(The other pain point is that Slack corrupts code-block contents in some cases. ("a known bug here […] currently being investigated by our engineering team […] don't have a timeline for a fix just yet" … the bug has been around for years, so yeah…))
You address your thoughts. The snippet folder just works fine, but I was thinking something about real-time, like chatting. I was thinking of making it self-host as an alternative to PasteBin and GithubGist, not only for extensions. But your insight is good. The problem with Slack or Microsoft Teams is the same. People don't even bother to format it; maybe they don't have time to do it. That was the actual pain point for me as well.
Could you tell me more about how I can improve it? Most importantly if it can bring up a better solution compared to Slack, PasteBin, and in-repository "/snippet" folder, would you use it?
Is this a common feeling? These all work fine for me, what's the issue?
There's also no <title>.
you need to distribute the cognitive load on your launch strategy
people cant be invested enough to even answer your actual questions if they're unfamiliar with how you solve their problem
Or maybe this is meant as a replacement for github PRs, meant for async review, in which case I really think PRs work well and don't need to change.
So yeah, I have to agree with others that I'm not really seeing the usecase here
If i were using your tool, it would be nice to have a single "turbogist" repo for all of the gists. That way i could send gists into it with git push
you could do something clever like this by having turbogist server manage the prefixes , so a git push from any repo would automatically consolidate all of the various prefixes into the turbogist account
e.g. https://gist.github.com/tonymet/d5df33b6a5003e1281c458a2d58d...
but i would love to see your product run with "clone with..." but make it work for all your experiments
I just wrote up a guide on doing something similar with subtree and a large "experiments" repo .
https://dev.to/tonymet/how-to-put-everything-in-git-2b3d
I apologize for the longer video, I should've done a short video rather than explaining the whole thing. Didn't realize it'd impact that much. I can understand your frustration. Give me some hours to make a new one.
I'm sorry, it was my first time creating any product and thinking about SaaS, and I'm still learning it. Please correct me, it'll help me improve and do better.