Hugo Testing

Each branch of Joe's hugo-testing git repository is a scratchpad where he has over 750 attempted 'solutions' to help different people on the Hugo forum. Seems like discovery requires starting at a specific topic (as opposed to searching for the problem or solution), but it's quite organized the way it is. How might being this prolific in helping others impact one's own skills?

Frugly vs. Freemium

the following games profit solely from aesthetic upgrades: Rocket League, Fortnite, CS:GO, Path of Exile, League of Legends. In these games, players purchase outfits for in-game avatars that do not impact the competitive balance.

I plaster the word “free” everywhere until consumers pay for a license. I’m not the first to do this, and I certainly won’t be the last.

I've been to the Hackerspace Wiki before to find local places while travelling. I didn't know they had hackerspace apps listing, software wishlists.

Their design patterns library includes The Community Pattern:

set up a mailing list, a wiki, and an IRC channel. You will need all three. Think about a platform for discussion, storage for documentation and real-time communication.

The Critical Mass Pattern:

[You need at least two people to start an idea and two more to get work done. It's easy to recruit once you have four people, and best to get started with ten.]

The Infrastructure Pattern:

[Infrastructure first or projects first? By making everything infrastructure-driven, people will come up with contributions you would have never thought about.]

A simple habit to let luck find you

I’ve made one [Mutually Beneficial Introduction] per day for 10+ years.

[Once both people opt-in, take thirty seconds to write with details that can't be found by searching online. Try this regularly.]

Writing, Riffs & Relationships

[Share what you wrote with a deliberately small group of maybe five people: your metric here is conversation and meaningful connection.]

[Write for one person to focus the text and also guarantee there's at least one person you can share with via direct message.]

[Scan your list of decent drafts considering who you could write each for.]

Grapefruit (book)

Let people copy or photograph your paintings. Destroy the original.

Hire Me

Seriously, I won’t take your money unless you say, “I’m super jazzed with these results, and there’s nothing I would change.”

Send your users this welcome email

[Ask: "What's happening in your world that brought you to this project?"]

[1. Distribute a self-hostable package; 2. Releases are free to distribute and use, source not available; 3. Offer free community support channels via a forum or chat; 4. Provide source and extended community access for a monthly fee; 5. Automatically make the source available on a rolling basis delayed by one year.]

The Cheap Web

The "cheap" web is a solarpunk philosophy of web design.

cheap ≠ free

cheap ≠ sleek

cheap ≠ creep

cheap ≠ deep

cheap ≠ dark

cheap = cheap

[cheap to maintain: should work indefinitely without falling over].

[cheap to access: should be compatible with screen readers and various devices.]

[cheap to explore: should be pleasant on low power devices.]

[cheap to contribute: creating and hosting websites should be easier than scrapbooking.]

Life in Weeks

Visualize a life compressed into blocks of one week and grouped be decade. The simple data file is written in YAML. This could be useful to help write one's autobiography.

in search of a new tab

[Each new tab feels like a choice: how do I want to spend my time?]

---

What a 'new tab page' this is! I prefer queries (via keystroke launchers like Quicksilver or 'Command-K') over big lists, but this is beautifully personal and makes me drool; stable options can leverage muscle memory and reduce distractions. 👍🏽

Provokes me to wonder about social patterns and 'formats' like /now or 'daily note', ways of organizing that many people can practice and share so that we can all learn from each other.

[Share a list of ways you can help as a consultant, then offer a sliding scale of hourly rates.]

Writing interoperable visions got me thinking about how cool it would be to use a GitHub repository as the storage for Zero Data or local-first apps as many people have an account there, even some less technical people. Using their repository contents API it should be possible to connect it as a backend for web apps and store the data in a repository. Has this been done already?

GitHub has useful affordances for browsing files, understanding directory structure, editing text, collaborating, version control, and a whole wack of integrations hooking into every corner of the internet. A repo can be synced to your local device where you can also do all the things your device can, then push it back to the cloud.

Might be interesting to think of it like a Dropbox shared folder, but globally public and editable, or another way to get Datomic's "version control for your database".

Of course, you may not want the data created by your app to be public, so you might use a private repository instead of a public one. Choosing a public repository where it doesn't breach privacy could be a new way to encourage 'open data', as one can literally see, fork, and hack all of it with no extra steps,

The many affordances accessible point-and-click via GitHub's web interface ensures there are at least two apps that can edit the same data, which is great for interop, but factoring all the ways to edit GitHub repos via integrations and on your local device, it becomes closer to infinite: could it be one of the most interoperable formats out there? What would it say about sovereignty if similar flexibility via an API was replicated by Codeberg, or self-hostable options like GitLab, Gitea, or Gogs?

The remoteStorage.js library already supports Dropbox and Google Drive as an optional storage backend, with Solid on the way. Why not add GitHub? A polyglot library with five low-friction storage options would give developers more potential for their apps, and the people using them more ways into owning their data.

Writing interoperable visions got me thinking about how cool it would be to use a GitHub repository as the storage for Zero Data or local-first apps as many people have an account there, even some less technical people. Using their repository contents API it should be possible to connect it as a backend for web apps and store the data in a repository. Has this been done already?

GitHub has useful affordances for browsing files, understanding directory structure, editing text, collaborating, version control, and a whole wack of integrations hooking into every corner of the internet. A repo can be synced to your local device where you can also do all the things your device can, then push it back to the cloud.

Might be interesting to think of it like a Dropbox shared folder, but globally public and editable, or another way to get Datomic's "version control for your database".

Of course, you may not want the data created by your app to be public, so you might use a private repository instead of a public one. Choosing a public repository where it doesn't breach privacy could be a new way to encourage 'open data', as one can literally see, fork, and hack all of it with no extra steps,

The many affordances accessible point-and-click via GitHub's web interface ensures there are at least two apps that can edit the same data, which is great for interop, but factoring all the ways to edit GitHub repos via integrations and on your local device, it becomes closer to infinite: could it be one of the most interoperable formats out there? What would it say about sovereignty if similar flexibility via an API was replicated by Codeberg, or self-hostable options like GitLab, Gitea, or Gogs?

The remoteStorage.js library already supports Dropbox and Google Drive as an optional storage backend, with Solid on the way. Why not add GitHub? A polyglot library with five low-friction storage options would give developers more potential for their apps, and the people using them more ways into owning their data.

Instead of queuing ideas onto an infinitely expanding todo list, blogging (or microblogging) about it can be a useful way to find synergy. If someone else had maximum information to pick up where you left off, maybe you'd be free to do other things?

'Infectious agency' as a design goal so that features enable a feeling of so much possibility that everything else should have similar affordances.