creator/operator of the HomeTown flavor of Mastodon. (more)

Moxie Marlinspike: My first impressions of web3. Despite considering myself a cryptographer, I have not found myself particularly drawn to “crypto.”... I don’t share the same generational excitement for moving all aspects of life into an instrumented economy.... Even strictly on the technological level, though, I haven’t yet managed to become a believer. So given all of the recent attention into what is now being called web3, I decided to explore some of what has been happening in that space more thoroughly to see what I may be missing. (more)

To-Do List for $47/month? (more)

Karl Fogel has a new edition of Producing Open Source Software: How to Run a Successful Free Software Project. A free software project can be started, and it can be influenced by interested parties. But its assets cannot be made the property of any single owner, and as long as there are people somewhere — anywhere — interested in continuing it, it can never be unilaterally shut down. Everyone has infinite power; everyone has no power. It's an interesting situation. That is why I wanted to write this book in the first place, and, a decade later, wanted to update it. Free software projects have evolved a distinct culture, an ethos in which the liberty to make the software do anything one wants is a central tenet. Yet the result of this liberty is not a scattering of individuals each going their own separate way with the code, but enthusiastic collaboration and frequent compromise. Indeed, competence at cooperation itself is one of the most highly valued skills in free software. To manage these projects is to engage in a kind of hypertrophied cooperation, where one's ability not only to work with others but to come up with new ways of working together can result in tangible benefits to the software and the community that develops it. This book attempts to describe the techniques by which this may be done. It is by no means complete, but it is at least a beginning. (more)

A diagram is a symbolic representation of information using visualization techniques. https://en.wikipedia.org/wiki/Diagram Thinking Tool (more)

Literacy in its broadest sense describes "particular ways of thinking about and doing reading and writing"[1] with the purpose of understanding or expressing thoughts or ideas in written form in some specific context of use.[2] In other words, humans in literate societies have sets of practices for producing and consuming writing, and they also have beliefs about these practices. https://en.wikipedia.org/wiki/Literacy (more)

re the mouth. Also re spoken transmission vs writing/literacy https://en.wikipedia.org/wiki/Oral_tradition https://en.wikipedia.org/wiki/Orality (more)

LambdaMOO is an online community[1] of the variety called a MOO. It is the oldest MOO today. https://en.m.wikipedia.org/wiki/LambdaMOO

ideas (more)

Vaughn Tan Unpacking Boris. This article explains why conventional goal-setting is usually self-defeating, and how organizations can free themselves to act more autonomously and effectively by focusing on tradeoffs instead. I call this tradeoff-oriented process Boris. (more)

John Cutler: TBM 213: Goal Cascades vs. High-Conviction Models. Imagine a “normal” annual or biannual planning process (roadmap). Everyone is throwing out pet ideas! Politics everywhere. If something can generate immediate $ it is good—you might as well throw darts at the other stuff. (more)

Cory Doctorow: Silicon Valley Noir. Red Team Blues and the Role of Bitterness in Technothrillers. (more)

John Cutler: TBM 209: Fog and Debt Debt. As a system's health deteriorates, its ability to identify and resolve challenges is progressively impaired. This kicks off a vicious cycle of declining health and increasing difficulty in diagnosing and addressing problems. (more)

John Cutler: TBM 216: Good Goals/Bad Goals. In my experience, SMART is only the tip of the iceberg. OKRs, to their benefit, seek to encourage some positive goal-setting habits, but ultimately they are still goals (more)

Itamar Gilad: Why Impact/Effort Prioritization Doesn’t Work. Effort can be stated in man/weeks or simply has high/medium/low. Impact can be graded on a scale, for example 1–5, 5 being the highest, or again as high/medium/low. Once you have the numbers in place, it’s a matter of picking the features that give you the best bang for the buck (more)

Nathan Baschez: How to Prioritize a Roadmap. There are two ubiquitous pieces of advice on how to prioritize a product roadmap. Unfortunately, both are useless. (more)

Venkatesh Rao 2019 term for the darkweb bits which are just friendly-private.

Open Source Interactive HyperText tool/Game Engine. Built on top of Tiddly Wiki. (more)

The DecentralizedWeb? DeCentralization of all internet protocols? See also Crypto, Metaverse, DAO, NFT... (more)

a super-famous computer game