Hello! I’m PPPDUD, and I’d like to introduce you folks to a project of mine that’s called Jameson.
Jameson (live instance) is a fork of Snap! that adds all sorts of cool features:
- An addon system that lets you write userscripts for Jameson
- A Silver theme modeled after early Snap!'s UI
- Libraries for working with ZIP files, UltraBox tunes, and even immediate-mode GUIs (thanks @codingisfun2831t!)
- Santa hats all year 'round…
- And so much more!
Jameson exists because vanilla Snap! was built largely for educational use. This means that while it’s quite powerful as a teaching tool, it’s lacking in quality-of-life features that would make it useful for hobbyists and hackers alike.
And that’s not all! Jameson’s a community project, so we’re always looking for help. You don’t even need to be good at JavaScript! You could write new libraries and addons and submit them to be included in Jameson, you could provide marketing help, or even just provide ideas!
(This post was edited in November 2026 because of changes in Jameson’s project direction. Below is this post as it was on November 6th, the day before the edits were applied.)
Old post
Hello! I’m PPPDUD (I previously used the @KingOfChickens account, but have moved here to prevent confusion). I’m a former Scratch user and current Snap! enthusiast best known for assisting in the development of Crackle and later Sparkle.
I’m here today to tell you about Jameson, which is a fork of Snap! designed to improve extensibility with the help of an integrated addons system (docs). The idea is to consolidate development efforts for other Snap! forks (like @d016’s Split!) into one place and make their features available as optional addons, which are supplied from a built-in addons store and can be sideloaded.
My hope is that by doing this, I can help reduce the amount of “forkcruft” that’s been building up over the years. From watching this category, I’ve noticed that a lot of fork developers simply wish to add a few blocks or redesign existing ones in ways that Snap!'s library system doesn’t fully accomodate for. This is where Jameson’s addon system comes into play.
If someone wants to make heavy modifications to Jameson, instead of needing to develop a separate fork and deal with the associated maintenance (particularly when you stop developing and end up diverging from upstream in ways that are painful to resolve), they can simply write a Jameson addon. Addons that are likely to be used by others and follow Jameson’s contribution policies can be introduced into the Jameson addons store and become available to tons of users who wouldn’t otherwise notice.
For fork developers, merging with Jameson gives them a larger userbase and a free account with my Nova Code Forgejo instance (which is neccessary for submitting changes, as I am banned from GitHub). As an added bonus, I periodically monitor Snap!'s development and I tend to pull from upstream pretty frequently, so your users won’t have to wait forever to receive updates.
@niki650 @theaysnap You two seem to be interested in forking Snap!. Would you like to merge with Jameson? I would be especially interested to see that fancy sound reporter displaying that you folks have come up with integrated into Jameson.

