I have a very clear idea of what I want to build with this; so far, I've only built a very rudimentary prototype.

This has been one of the projects I've most wanted to do, but put off doing, for over a year.

I've got access to cluster computing generously provided by the Cloud Native Computing Foundation: my next steps are using that to build a robust sandbox system. I also want to restructure Plusku to make use of Kubernetes for app provisioning, rather than fumbling around managing Docker internally.

Based on a conversation with Nolan Lawson a few years ago, this would be how I'd fulfill the goals described at https://discourse.wicg.io/t/making-icons-less-painful-and-murky/870 back in 2015.

I created the repo as soon as I had the initial idea, but I've yet to populate it. This could be a fun one to do live.

Still need to implement sync. Wouldn't mind simplifying the logo.

I've got a few bugs I need to squash next time I'm in the neighborhood of the Pebble development ecosystem.

There are a few refactors/migrations in the pipeline I want to implement, as well as a proper build toolchain (I need to rethink the current build system path structure).

I've got an idea of what I want to build, plus a domain and logo.

I know what I want to design and how I want to implement it: I had about an hour's worth of work put toward this, but I accidentally deleted it.

There's lots of stuff I want to do with this, which may get their own projects: right now, this project is a sort of signifier for "anything that deals with that awesome Alphabi stuff".

Needs UI / flow polish.

I know what I want to make with this: I need to write up the Reservoir-Dogs-flavor rules and design the pieces.

I've only done one poster so far, but I'd like to design more.

Right now, I have bunch of notes in the form of cards on Trello; I'm moving to migrate them to Markdown files on GitHub.

At this point, the main thing left to do is refine designs for printable stamp handles, molds, and potentially stencils.

I forgot that I wanted to make this. I've got a pretty nice interface planned out for it.

I have the domain and some initial design thoughts for this.

Needs a more stable live setup; more work on Plushu would help.

I've got a domain, a rough logo, and some design ideas. Next step should be codifying that design model.

I need to refine the concept, and reconcile it with a few other projects I've got in the works.

I have a domain, logo, some UX ideas, and some idea of how I want to structure the implementation.

Right now, I do this by going to hashblot.com and entering the string I'd use for a hashblot. I was originally thinking I would implement it as a standalone browser extension: nowadays, I think I'll implement it as a feature of NilPass.

The main thing I'd want with this today would be a good block storage hookup.

I pretty much just comitted a raw proof-of-concept, with barely any styling applied.

I know what I want to write, I just haven't found the time to type it out.

This is a big part of what I think a secure credential model should look like.

This is one of the first apps I ever wrote; today, I would essentially overhaul all the code other than the art assets and templates.

The version online right now only supports local video files and has no credentialing system.

I've still yet to do a first commit on this, but I've put a fair amount of work toward it.

I wouldn't mind polishing the UI for this a bit. Also, I have a logo/favicon (and easter egg) in mind that I want to add.

I've got a few scripts written, but no Reddit-Enhancement-Suite-style browser extension collecting them all.

I mostly just need to refine the live architecture of this.

I'd still like to figure out how to position the nodes with as few path overlaps as possible.

This seems like it could be a fun project for a hackathon.

There's a working bracket up there now: I'd like to refine the hinge clasp a bit, and there are more models I'd like to add.

I need to spec out the prospective flows for this and run them by someone who understands CouchDB better than I do.

I have the high concept, but am not sure how to make the mechanics cooperative and fun.

I've got some content, but haven't found the time to really dedicate myself to evangelizing this.

I mostly just need to redo the backend; now that the comic has effectively ended, I should really just make it pull from static data files or something like that.

I've been debating whether this should be implemented on Secure Scuttlebutt as a base, and how that would be structured if so.

I've got a reasonable idea of how I'd implement this.

I haven't rebuilt this in years, it probably needs some amount of revision for modern systems.

The OpenSCAD for this is currently subtractive; it ought to be rewritten to be additive. (Also, I should do a writeup in the README on how I set up the one for my phone that's on my desk right now.) Should also publish it on Thingiverse / Youmagine.

I think I have an implementation that needs a little modernization, packaging, and UX polish.

This could use a little more explanation as to its purpose.

This has the underlying game logic functions implemented (for analysis), but no UI.

I don't "network" as much as I used to, so this isn't as pressing a need as it used to be, but I still think it's a good idea.

There are some improvements I'd like to make to this algorithm, like developing a histogram of perimiters at different alpha levels instead of just 1 binary hull around a threshold alpha value at a time.

I don't think about this as much as I used to, but I used to think about this a LOT.

This might make sense as a Secure Scuttlebutt project.

I have some high-concept ideas about what I want to be in this game, but I'm not certain how they'd translate into mechanics.

My original design for this was Facebook-centric; I still feel that its main problem is not well-solved, but being less immersed in Facebook today has made a path to engagement for this less clear.

I have the idea of what I'd want to fill in with this, but not necessarily the skill or knowledge to implement it. The main reason I originally set up this project was to provide an alternative to prevent the gauche, inorganic CommonMark specification from catching on; in the time since that project originally launched, this hasn't really given any indication of becoming that much of a threat, so I've pretty much let this project fall by the wayside.

I have this domain, but haven't put anything on it.

This is another hypothetical language I've designed that I will most likely never be pissed off enough to implement.

This is based on the way I've been handling my grocery list in Trello for years.

I think I need a better domain name for this.

I apparently had a repo for this at one point, but I seem to have never comitted my work.

This also kind of ties into an idea I've had for a browser extension that would also insert these summaries in quotes into the middle of people's names.

I want to implement this for use in both DingRoll and Tabalanche.

If WebXR and WebAssembly firm up a bit, the tech basis for this will be a lot more workable.

Could be a fun project to get to know Kubernetes with.

I have domains for this, and a few known structures I'd test against.

This would be a fun project to demonstrate what's involved in structuring a data model / schema based on prior art in the field.

I'm not sure if this is currently working; my existing implementation would need a significant overhaul. These days, there are a bunch of better-maintained sites that work basically the same way as this was going to work, so without some really fresh ideas that aren't currently being explored, there isn't really anything to add to this.

Needs UI polish and documentation. Could use some back-end refactoring.

I know what I want with this; the main issue I remember having is that Ace can't handle being transformed via CSS.

I don't honestly ever expect to be qualified enough to tackle this realistically, but it's fun to consider.

I just realized that what I want from this can largely be accomplished with a single fixed body of text.

This could still use some work and elaboration on how to build practical projects with CouchDB.

Currently I've only got a Netflix interface implemented (and I'm not sure that it still works), and the extension itself isn't published (since it may well violate lots of terms of service and stuff like that).

I think this is all set up, but not reliably.

I haven't been involved in WICG for a while: this is something I'd start working on and maintaining if I got back into it.

There's another library I'd want to implement before I implement this.

I was originally thinking of implementing this with a browser extension; this might be an interesting use of Service Workers today.

I have some design discussion around this lying around somewhere, before I'd actually looked into what options for running a little personal library are out there.

This is an old idea I've had for at least a decade.

I broke the Chromebook with a stuck pixel that I would have tested this on, so I'm not particularly interested in working on this; the main thing I feel is missing from this project right now is a logo that's yet to be drawn.

I mostly only work on this when I've got some minor repair or replacement that needs doing.

I can't think of a single case where this would be practical, but it still feels like it could be fun.

Has domain, logo, and some idea what the site should look like.

Nothing yet.

I have a domain and logo for this, and some idea as to how I'd implement it.

This would most likely be useful if and when I revisit StepDub.

I don't really care about editor colors any more, so I'm not all that inclined to pursue this.

I have a really old codebase for this; it might even be viable, I don't remember.

Before tackling this, I would try seeing if the author of that article still has the widget's sources.

Right now this is written in proof-of-concept JS instead of something performant: that would be the first thing I'd want to change.

https://www.youtube.com/watch?v=_Iw0euc4qDk

I originally started working on this before I even knew web development. It's been so long since this project was relevant to me, I'm not even sure where my DSiXL is.

I implemented a whole animation for this before realizing the backend wasn't feasible. Today, I've got a robust enough API to implement this in Pull Tool, but the functionality of this extension is less important (and won't work as Google closes the door on Chrome apps in non-Chrome-OS contexts).

Honestly, the biggest blocker on this for me is that I can't get that domain name.