Application Error
Yt@https://turbogist.dev/assets/index-DLPix6K5.js:180:801
u@https://turbogist.dev/assets/index-DLPix6K5.js:186:1066
Eo@https://turbogist.dev/assets/index-DxO2AQNl.js:22:16959
Ka@https://turbogist.dev/assets/index-DxO2AQNl.js:24:43694
Wa@https://turbogist.dev/assets/index-DxO2AQNl.js:24:39501
rd@https://turbogist.dev/assets/index-DxO2AQNl.js:24:39432
el@https://turbogist.dev/assets/index-DxO2AQNl.js:24:39289
Hi@https://turbogist.dev/assets/index-DxO2AQNl.js:24:35710
Va@https://turbogist.dev/assets/index-DxO2AQNl.js:24:34666
E@https://turbogist.dev/assets/index-DxO2AQNl.js:9:1563
pe@https://turbogist.dev/assets/index-DxO2AQNl.js:9:1930
>
I think we're tired of copying and pasting our codes and sharing links using PasteBin, GithubGist, or Slack.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…))