Request for Tools
Request for Tools
A long-form asynchronous encrypted messaging serviceReferencesGitlab for (audio/video/visual) creationQuick lightweight internet threadsSub-domain scoped IPFS hostingA tiny music collaboration siteA calendar app for loose communitiesA static site generator that creates tutorials from git repositoriesInspirationA mobile app to create ritualsReferencesA hot-reloading linterThese are a bunch of poorly defined tools I'd like to use. There are probably
many reasons why they would be hard to build, or are ill-considered. Enter at
your own peril.A long-form asynchronous encrypted messaging serviceor: email but actually good.
or: Signal but slow.There are two sides to the benefits of email: Pretty much everyone has itIt's well suited for actually doing work1  is hard to make happen out the gate so let's focus on 2. Crucially email is asynchronous. Thee is a disconnect between sending and
receiving and a cultural expectation that messages are not to be immediately
replied to.ReferencesStop using encrypted emailGitlab for (audio/video/visual) creation(You could probably do this on gitlab itself, but it would be a neater as a
standalone, specific, tool)Gitlab orchestrates the entire pipeline for software development. What if you
made a similar service but for creative production?Quick lightweight internet threadsThreads are a very useful social primitive. On twitter, reddit, etc, they form
the basis for valuable and complex social interaction. However, there are places
all over the internet where it would be useful to have threads, without the
weight of an entire social network. Things like cross-site blog chains.
Comments on your blog posts. Or even just quick collections of links.Sub-domain scoped IPFS hostingThere are a lot of IPFS gateways out there right now, but they all have the URL
as a specific page, or query, on the root domain. This isn't a problem in most cases, but it does become an issue when using IPFS
to host client side apps. You'd want to do this for a couple reasons. It makes it really easy to distribute your application. It gives the person using your application a guarantee that they're not
getting any updated code, but specifically the HTML and JavaScript you
published. Combine this with auditing and you have a good set up for
distributing and using secure client side apps. You can get around this by instead storing the has as a subdomain on the root,
i.e instead of https://example.com/HASH you would have
https://HASH.example.com. You could do this with something like zeit's
wildcard domains A tiny music collaboration siteLess Google Docs, more hackmd. A tiny site that let's you spin up a collaborative session to make music with
anyone who has the link. It should basically just consist of layering sound
files, and maybe snapping them to tempo. No Effects, no notes, just placing
tracks around. Oh and a way to record input. Bonus points for version control. I
think you could also get a lot of mileage out of sample groups. i.e having a
snare sample, and then being able to have multiple versions of it easily
accessible. A calendar app for loose communitiesMost calendars are built for either individuals or tightly coordinated groups.
I'd like one made for loose communities where people have many divergent
purposes. It needs to allow the creation of events by anyone (with some
constraints/permissioning) and the easy filtering and discovery of events. A static site generator that creates tutorials from git repositoriesGit is a perfect way to combine changes to a codebase overtime with documention
of those changes. If the changes are the progressive, pedagogical,
implementation of a project, git becomes a tool for creating tutorials.I want a static-site generator to then take a git repository and render a nice
looking website, combining changes with the commit messages associated with
them.InspirationThese tutorial do a similar thing: Creating a code editorGitA mobile app to create ritualsI'd like to a mobile app the let people create time based rituals. Whether it's
something like writing for a set amount of time everyday, or alternatng working
and breaks for an hour. Or meditating in a particular structure. It would allow
you to set time intervals and would buzz when they occur. Maybe, it would ask
for inputs. While a ritual is going on the phone should be unable to be used,
and if the app is exited the ritual ends. Bonus feature: allow multiple people to participate in a ritual by scanning a QR code.Referenceshttps://github.com/yoshikischmitz/line-timeA hot-reloading linterDuring my term at the Recurse Center, one of the projects I brielfy explored was
an Oulipean Linter. The idea was that you could have a git repository that only
accepted pul requests that added writing that met certain creative constraints.
Things like not using the letter e, or such. I'd like something like that, but as integrated into my writing environment as
my typechecker. Then, I want to be able to edit and create my own constraints,
using a simple API, and have them instantly applied to what I'm writing.