my avatar image

  • home
  • source
  • September 18 2023
    • in gro removed the build system and modernized for SvelteKit (pull #382)
    • updated the gro tagline to "task runner and toolkit extending SvelteKit"
    September 9 2023
    • updated the summary, "a free and open source noncommercial hobby project exploring tools and toys using web tech for fun and learning"
    July 17 2023
    July 9 2023
    July 2 2023
    • in cosmicplayground added pinch-to-zoom gesture support, like for Soggy Planet, so non-busted mobile support is almost there, and soon I want to extract it so it's reusable, maybe as an action instead of the current component (pulls #76, #77, and #78)
      why it took 3 PRs and it's still not done There's a janky zoom bug that took a couple extra PRs to diagnose and it's still not fixed. Firefox for Android is delaying some pointer events which causes big janky jumps for some quick pinch gestures, and then reversing your pinch won't put you where you started. Chrome for Android works great, so at least my code seems ok, but it's little consolation when my primary mobile browser feels broken with it. I'm now wondering if I should abandon pointer events and revert to mouse+touch. I started down the Bugzilla rabbit hole but it's deep... The silver lining is that the problem nudged me to improve the code significantly from the first pass.
    • on this website added dark mode support by upgrading felt-ui and using Themed - currently it only detects the user's preference, soon I'll fix things upstream so we can add a switcher for users without the current boilerplate (pull #2)
    June 30 2023
    June 21 2023
    • in earbetter added the option to customize the tonic of each trial, so you can stay in key instead of always getting the full chromatic range (pull #24)
    June 13 2023
    May 19 2023
    Mar 28 2023
    Mar 17 2023
    • added the initial proof-of-concept for, an ear training game and tools for programming music and audio, features a configurable trainer and a piano with MIDI support (source, pull #1)
    Mar 1 2023
    Feb 25 2023
    • changed dealt ( to have its stages and entities be data-driven, opening up some interesting opportunities (#62)
    Feb 22 2023
    Feb 20 2023
    Feb 5 2023
    Feb 1 2023
    Jan 28 2023
    • revised and tooted about my second blog post, "Modeling virtual social spaces: in this house we post cat pics on Saturday", with more on Mastodon: (Mastodon): WIth in mind, I'm curious whether there is any possibility of checking the power of Control? Is there a way in which that could be non-absolute? (Mastodon): Yeah! Here's how we're thinking about it right now with Felt. Still ratcheting up the ladder to climb out of the feudal hole.

      Control is held at the group/org/community level (Felt names these "hubs" now) by actors. In the default hub template the creator gets the all-powerful "steward" role, but the hub itself has an actor, and control is transferable/sharable. The hub actor's actions are controllable by automated/assisted/direct processes. Other group actors could be involved.

      to clarify, "steward" is just the name for a role in the default hub template and a convenient way to reference the idea, they can be constrained with fine-grained permissions like any other customizable role - this contrasts with Slack (no customizable roles) and Discord (coarse-grained permissions)

      given this API you could design a set of roles that split powers, separating/balancing concerns

      hub templates make it easy to share pre-fab designs with the initial roles/permissions/etc

      In our implementation, actors are assigned roles which have permissions. You helped me realize that by splitting permissions among roles we could support non-absolute power with this:

      An all-powerful group actor's actions could result from collective governance processes

      or, I think we can support designing systems with structural checks and balances through permission assignment, so any actors could have mutually co-checking subsets of permissions in a hub

      That's the first-order UX prioritized by end users. This second part is ignorable by most people most of the time, but for the governance enthusiast:

      Hubs are hosted on infrastructure controlled by "operator" actors. These have the power to pull the plug, and may technically have hub control bypassing stewards, like modifying a database.

      Maybe there's instance/server/etc levels between infra and hub, but that's an impl detail. Felt has instances controlled by "admins".

      The operator actor could be co-ops/nonprofits/other orgs, or as you've written about, bl0ckchains or similar. Bchain enthusiasm makes sense here b/c the operator won't pull the plug or modify the db barring acts of God. plans to be a platform co-op operator providing infra.

      btw I love this so much, Boba Board ( has leaned into *explicit* feudalism for their fandom communities, owning it right in the brand! "Be the Monarch of Your Own Realm!"


    Jan 24 2023
    • renamed this project's main building block from Bulletin to Digest, seems friendlier and better for puns (commit)
    Jan 23 2023
    • moved most of our projects on GitHub from @feltcoop to @feltjs, which will be a nonprofit, tightening @feltcoop's scope to be a platform operator at (still with the goal to be a platform co-op), and making @feltjs and its repos a community project more explicitly
    Jan 17 2023
    • added the Board view to Felt - it's like a chat room but upside-down, so the input is at the top and content flows downward, replies are nested, and the newest posts and replies appear at the top:

      a screenshot of the board
    Jan 11 2023
    Jan 8 2023
    Jan 2 2023
    Jan 1 2023
    my avatar image