Introducing Snippyst - An online, free, open-source snippet sharing platform for typst

Showcase
1

Introducing Snippyst - An online, free, open-source snippet sharing platform (for typst ofc ;))

https://snippyst.com/snippets

TL;DR Snippyst is a platform to share your code snippets in a code format, that automatically renders for others, supporting social embeds (such below). No forking or PRs. Just sharing.

I posted this a few days ago on the DC, but changed the post a bit to fit to this forum: Can’t post link (see below)

Snippyst is made to share Typst snippets with everyone.

I was introduced to Typst a few months ago. I fell in love with it and its possibilities.

On Discord I saw the Discord bot and the bot corner in particular and thought there are so many great ideas that get lost over time. I also had a few simple (nothing major) snippets I wanted to share and I wanted to find new ones easily without redoing the work others already did. I couldn’t find anything like that, except for some great but limited personal or very specific collections. They all had one thing in common - they needed contributions via git, which means forking, editing, committing, PR, and merging. While learning and working with git is an important skill, I felt some kind of boundary just for adding a few (maybe even very short) snippets.

With Snippyst, you can sign in with Discord, GitHub or Codeberg and start creating snippets. We actively monitor for spam and reserve the right to ban users.

Snippyst offers many QoL features for sharing such as:

  • Fast and live creation. No forking, pull requests, or waiting. Items can have titles, tags, descriptions, and used packages
  • Voting/Rating
  • Search or filter by user, tags, Typst version, and used packages
  • Edit snippets
  • Embed support - You can share a snippet code and it will display the rendered image (While this is not very special for Discord because of the bot, it also works on other social platforms that support embeds like this forum here)

More features are coming, such as edit history, bookmarking and comments. But the main goal is to share snippets with everyone. The database creates a dump every day so no information is gatekept. Note that, for privacy reasons, any user or personal data is removed, so this data is intentionally lost. The snippets (title, description etc.) as well as the tags are preserved

Anything related to the UI is subject to change / feedback
I store as little data as possible when you use any social login.
Deleting your account removes all your data. I cannot recover anything except from encrypted backups, which will be deleted over time.
I am not skilled in UI/UX design, and I know it. For the frontend/UI, some elements are AI-generated. But don’t worry - I only used AI where it made sense. I want to be transparent about the use of AI and make it clear that this is not “vibe-coded,” especially not in the backend where privacy matters. Without it the page/frontend would look like a HTML scaffold and not a (subjective) styled page.

You can find the roadmap here:

Sadly I only can post 2 links, because I made an account for the forum for this post. So the org is Snippyst on GitHub

The code for the backend, frontend, and worker is open source:
Same as above

10 Likes
2

Two more examples:

3

That looks very useful and polished!

Would it be difficult to allow the user to edit the code and have the preview updated in real-time?

2 Likes
4

The user that created the snippet can already edit and update it. The preview updates in real time. Due to how it is structured, the display might look slightly different because the snippet is rendered server side for validation after submitting.

Social embeds might be cached and display the old image, so changes may not be shown right away.

5

Agreed, this looks really cool.

Have other login options been discussed? Linking to either a typst.app or forum.typst.app account would be logical but Typst GmbH may not be interested. A snippyst.com account would be the most generic but would, of course, require work to implement and maintain.

3 Likes
6

I am open to adding other login options (e.g. Codeberg was added latter), given they support OAuth/OIDC and have some basic security measures.
But adding typst as a log in option in not realistic as I did not find a way to register an application to use OAuth. But I am also not sure if I want to even if. I want to make clear that this is not a product by the Typst GmbH.

2 Likes
7

Why not let any visitor edit the code (without saving) and see the result in real-time? It would be cool, while the current behavior for visitors is a bit weird (it looks like an editor but gives a “read only” error when one tries to edit).

1 Like
8

That’s a great idea. While I probably plan to implement it very soon (there are one or two features I still want to add prior), I added it to the roadmap. The main issue is that you don’t actually render the code snippet, but load a prerendered version.

I have some ideas (for example, it could ask you if you really want to render the snippet when you try to edit it), as a typst snippet could potentially cause a DOS on a client.

Thank you for the input!

1 Like