This is a simple Pastebin clone I made using the Deno Typescript runtime.<p>I created a simple templating system, and implemented server-side rendering for the UI.<p>Demo: <a href="https://paste.jlcarveth.dev/" rel="nofollow noreferrer">https://paste.jlcarveth.dev/</a>
I was looking around for a pastebin a while back, and I realized that a self-hosted pastebin is way too much overhead for a simple problem: easily serving possibly-highlighted rich text to people. I already have an editor I like for _writing_, so the problem becomes a matter of hooking into the editor’s syntax highlighting to generate equivalent JavaScript. A quick htmlize + tramp hack later, I could serve my current emacs buffer with the world:<p><a href="https://fwoar.co/pastebin/3daaf7ce49ca221702c70b0d10ac5caec8962b78.el*.html" rel="nofollow noreferrer">https://fwoar.co/pastebin/3daaf7ce49ca221702c70b0d10ac5caec8...</a>
After reading "A love letter to Deno"[1] I think I might actually start installing deno apps like this one on my home server.<p>Not only because they would be more secure by default, but also because Deno apps don't seem to need/want to be dockerized. Which means less overhead.<p>Not sure if it's a cultural thing or just some features of Deno that make Docker less necessary.<p>[1] <a href="https://matklad.github.io/2023/02/12/a-love-letter-to-deno.html" rel="nofollow noreferrer">https://matklad.github.io/2023/02/12/a-love-letter-to-deno.h...</a>
Nice and clean!<p>I feel like the biggest issues with pastebins are:<p>- Data is known by the provider
- Not enough economic incentive to keep the pastebin running for a long time (you still need pocket money and some maintenance to keep it running)