Travis F W

#Polyamory is closer to #Interbeing

Usually #visibility campaigns and #polyamory are somehow represented somewhere on the fediverse but I'm not finding this one:

Week of visibility for #nonmonogamy
https://www.weekofvisibility.com/

"A global celebration of non-monogamous communities, identities, and values!
July 6-12, 2026"

Your thoughts?

Wishing for a #SearchEngine for the #SmallWeb

I wonder, do #vegans know that #cornSubsidies keep meat prices low?
#AskFedi

It seems to me, the one policy change that would have greatest impact on consumption of meat in the US is to decimate corn subsidies and such farm subsidies that reduce the cost of animal feed.
#vegan #veganism #USPol

I put Debt (by #Graeber) back in my rotation of nonfiction books (I always listen to several in parallel), and yeah it's what I remember. And yeah he's right about human nature.

And the role of the state, in modern #econ, to essentially just be the name on the note, can be easily swapped with digital identities now. And externalities could be accounted for, as well as innumerable social priorities monetary transactions erase. Like fairness. And equity. And eventual actual recompense.

But, while I am always happy to see favorite writer dress down the usual suspects, I see my role being to represent the #nonquant potential where numbers games are abandoned for just doing something for someone when you know it's good, and knowing that your investment of your time and effort in your community will pay you back, just not in quantified fiat.

Oh. What is this #gettr thing?

I am trying out #Goose with #SiliconFlow for #AMLD / #LiterateDevelopment
#aidev

I am starting to talk about UXD from an HCI perspective as PIE: Paradigmatic Interaction Experience, or, individually, interaction experience paradigms.

I don't have the clout to coin a term and expect anyone to use it, but fuck it. #UXD is too much about two-dimensional widgets. #HCI is too broadly about #informatics in #sociology.

WTF am I talking about?

Epubs and PDFs are consumed in the same paradigm.
Filesystem navigation is a paradigm, and you know what experience to expect during that.

I'm all up in the #FLOS mindset where if I have a problem I want to engineer a solution.

Problem is I have enough problems (in common with everyone) I have begun too many projects, and I don't even have spoons and life and cash flow allowing for a few.

First on my list right now is … well I'm just going to call it #FediHelper for now.

It would be a bot that would help you do everything you want on the #Fediverse.

Find people, gather community, reference/follow/bootstrap …

Project #glasswing has very serious implications. How are you all thinking about it?

Well, what I'm hoping it could get us, and *you*, because I know you do this kind of work, is compensation.
Monetary compensation? Just because #nonquant is explicitly not a way to fix any monetary system does not necessarily mean you can't get monetary compensation, because you can look at money as just another valuable thing.
But anyway, *how* can a nonquant lens on economics help someone find compensation for their work?

So, now, with #nonquantifiedEconomics recognizing otherwise devalued and ignored economic activity like #art, #FLOS software contribution, #activism, organizing, connecting, community management, child care, and all kinds of work that goes largely unpaid, as economically valuable, what does that get us?

Furthermore, if you just decide not to take payment for your work, in #nonquant #econ, you can just call that investment.

That's actually what you're doing when you volunteer anyway, isn't it?

With #nonquant, I'm not talking about everyone quitting your jobs and installing my software and suddenly utopia.

#nonquant is a way to look at what people are doing every day and why, and how the world works, without talking about money as though it's more than what it is: overhead.

So there is one big plus side of #nonquant #econ. Work that is invisible to classical economics (domestic work, for starters) becomes first class economic activity.

Next, I can say that in a nonquantified economy, potentiation of value can be recognized as investment.
Boom. Education, infrastructure, and preventive health — WHOLE SECTORS crudely shoehorned into the quantified economy — get promoted to their rightful top priority.

The #nonquant question is, why are they choosing to engage in this transaction with each other? What do they value?

Maybe Alex values their business somehow, possibly having happy customers and being productive.

Blake probably values the service and also chose the business for a number of reasons.

But if you break it down to what they value, and if you don't need to talk about monetary transactions *only*, you can start crediting work that is not transactional.

But a #nonquant perspective focuses on the choice and the value, not the classical "transaction" of currency for a product or service. In a two-party transaction, each make a choice. Alex chooses to serve Blake, and Blake chooses to pay Alex, and they choose to do it at the same time so they don't have to track debt.

A common saying in #economics is, money is what you give; value is what you get.
Does money have value in #nonquant #econ?
Well yeah, if it is relevant to the subjective situation where people are making choices about what is most valuable for them to do at any time (AKA just "choices"), and it is everywhere today, so absolutely.

Why is #nonquant important?
Avoiding the attempt to draw equivalences in value, and acknowledging the subjective value of a choice, reframes #economics to focus on what actually matters to real people, and rejects quantified models (classical economics) that gloss over real value to real people, as if using numbers of currency as a proxy actually approximates value.

I am not researching contemporary thought in #nonquant #econ. But I have gone over the fundamentals quite a lot, and I know that the tech to enable this kind of global economy would be quite simple. I'll do my best to describe it, but first, the basics:

It's probably time for me to do a thread about interdependence and nonquantified economics again. Not sure I have the spoons, but I'll start with one and see how long before I'm interrupted. #nonquant

@bytebro @Alice what platform strategy neglects in their quest for #networkEffect is that with enshittification, when people are on the network *entirely* for the network effect, their participation reciprocates the #enshittification.

People feign sincerity, quality, vulnerability, and interdependence, because they don't really want it. Not from #LinkedIn.

All of the above being not *directly* addressed by the design the #web, yet having become necessary functions and aspects of the web, I am proposing a #Web2 address these concerns directly.

PS: I'm pretending the web2.0 of the aughts didn't happen, because it wasn't really a big deal to get databases involved in publishing, and nobody talks about the web now as if it's a new version. IMO we're still on 1.x point releases, not that there's a number.

Problems out of scope for the first web must necessarily be in-scope for #TheNextWeb/#SocialWeb:

#Identity

Privacy and Security #privsec

Search

Data & hosting

publishing code

switching browsers

Disintermediation (#WWW must be its own platform, must facilitate/obviate brokering)

all of the above, in other words: #Disenshittification

#Versioning (#DVCS) & #Archiving & #Publishing

Navigation of semantic adjacency in terms of a hyperspatial manifold. (got a term for this?)

#DWeb

#DVCS "what comes after git" first search result (thank dog not a startup)
https://mattrickard.com/what-comes-after-git

"These doubts are not wasted time;
This is the terrain of real change."
From: Happiness Break: Make Uncertainty Part of the Process

#podcast #Episode webpage: https://play.prx.org/listen?ge=prx_192_a4ba84ad-7ba9-4abe-9528-fb0447161c0c&uf=http%3A%2F%2Ffeeds.feedburner.com%2FTheScienceOfHappiness

Media file: https://dts.podtrac.com/redirect.mp3/pdrl.fm/0f808e/tracking.swap.fm/track/sblTq32fyWAjsHzze2LG/mgln.ai/e/48/dovetail.prxu.org/_/192/a4ba84ad-7ba9-4abe-9528-fb0447161c0c/SoH_HB_Yrsa_Daley-Ward_Poetry_20260402.mp3

@lexiconista I was hoping for something on #Farsi, which I am learning. I am *not* a linguist and I could use the insight. Anyone? #i19 #internationalization

#Claude likes #AMLD

🙶The methodology aligns well with how I work in several respects:

- Plan-first, human-affirms (wip.adoc review step) matches the principle of checking before acting
- Structured logging (amld/log/, handoff files) compensates well for my lack of persistent memory across sessions
- Declarative design docs as the source of truth is sound — code should reference design, not the other way around
- Ticket discipline gives me clear scope boundaries, reducing drift

#AMLD Agent-Mediated #LiterateDevelopment methodology first draft, ready to be tested.
I would love some feedback.
https://hg.sr.ht/~travisfw/amld-method
#agenticCoding

A well researched and written book addressing a topic (named by the title) critically important to explore at the dawning of the age of #AI.

I especially appreciated how Brooks capped it with a chapter on wisdom, and what is a "community of truth." Particularly inspiring from my #HCI and #informatics -oriented mind.

I hope to relay some of the contents of this book to my children, if I can.

(comment on How to Know a Person)

I just began an #AMLD repository.
It is a template for Agent-Mediated #LiterateDevelopment methodology.

In a nutshell:
Design documentation and project management should be *on trunk* (or main branch) and must be enough to regenerate everything that has been previously generated with an #AI coding agent. It should be written for humans, except for a log of previously followed plans referenced by closed tickets.

IE the docs are code.

This is not #VibeCoding; this is literate.

@brave the appropriate alternative class of open technologies is #digitalProvenance and I don't get why everyone in #privsec isn't working hard on it.

@thestrangelet just the essential capacity to relax and enjoy an experience requires practice.
use it or lose it.
#allostasis

@MarkDW anyone offering a service to install an open mod on your choice of device?

Customer pays for the device, shipping delivers to the installation service office. Installation service installs customer choice of Android mod, repackages, ships to customer with a single flat-rate service fee.

For this, I wish. #businessConcept

RE: https://mastodon.blaede.family/@cassidy/116149420744573650

#LiterateDevelopment vs #vibeCoding

This is what I am learning now. How best to maintain project management docs, specifications, tickets, and so on, on trunk.

I started out putting it in a separate branch and committing generated code to its own branch, and merging. I thought my prompting and writing was just for me, or at least, not what people would want to see.

#LiterateDevelopment #CleanCode

I have realized the error of my ways. The docs are the code. The English is the important part, now.

How are you doing it?

So, what does #LiterateDevelopment look like, now?

Well, it bears repeating that the *literate* part (which Robert C Martin would still call "code") should be committed to trunk. It needs to describe implementation, maintenance, testing, deployment, and all the same dimensions of utility documentation has always served.

But now, it needs to be on trunk, not in a separate repo or wiki.

Is that awkward? But we have the tools and many ways to do it, and we're just getting started.

… #LiterateDevelopment vs #VibeCoding. FIGHT!

Also, people have *always* vibe coded!

You don't have to be around long to find code that makes you wonder … until you realize the author just didn't care.

Vibe coding is the engine driving so many startups toward their exit. If the goal is to exit, not maintain, it just has to "work" until the ink on the sale dries.

Slop code has always been. #AI has merely lowered the bar for its creation.

These people are not writing literature.

Actually, I want to pit #LiterateDevelopment against #VibeCoding directly.

Clean code has *always* been literate. That means a dev with the skills to maintain the code base should be able to read the code. The *only* valid argument against documentation has been that the code is self-documenting. Okay, maybe with a high level language and enough care, the docs can be fairly spare. I would still argue for documentation, but I have lost some of those arguments.
…

Caveats!

Primarily:
Docs are code!

Tickets. Diagrams. The roadmap. All the project management stuff defines the software. With Claude (I have yet to branch out, but believe me, it's coming) I have begun committing project management documentation to trunk. (Rename master to trunk, you colonialist.)

*Everything* I generate with an LLM is based on committed English documentation.

This is #LiterateDevelopment! Thank you, Donald Knuth and your contemporaries. And thank you Robert C Martin.

The anti-Free aspects of the design of the "app" paradigm are:
Ⓐ Your screen space:
A company controls those pixels. The #desktopMetaphor is the root of this #enshittifiability, with "windows" defining a portal between your attention and the informatic space unilaterally controlled by the developer.
An alternative is how GNU and the shell work, where the human invokes the function, which humbly takes no more time than necessary and exits, leaving just what was requested.
#HCI #Informatics

@freesoftwarecaucus #Zulip is also a great option for FLOS communities to #ditchDiscord ( #ditchcord ? )
#communityManagement

Whether you agree with, hate, or are turbulently navigating the transition of many teams to agent-mediated coding (I am considering the post from @anildash where he talks about #codeless, IE #LiterateProgramming or #LiterateDevelopment), Robert C Martin's book, Clean Code should be the bible in these times.

https://sfba.club/user/travisfw/comment/41400

https://www.goodreads.com/work/quotes/3779106-clean-code-a-handbook-of-agile-software-craftsmanship-robert-c-martin

#AIDev

@anildash I do have a better term than #codeless!
I mean Donald Knuth does: #LiterateProgramming.
AI is new, but everything about what the developer does is, well, let's call it #LiterateDevelopment, just a slight shift into this millennium, reflecting that it really becomes enough to develop a system, still obviously referencing Knuth.
I think the word "literate" emphasizes the care and responsibility a dev should take not to produce slop.

If #fedi instances, or accounts on instances, come and go frequently in alpha software, would that kind of churn cause problems with other instances on the #Fediverse? What is the #fediquette for #fediDev?

When #Heinlein illustrated the Martian's maturity by having him kill someone and then have sex, and then go out on his own, and subsequently had the main female character say something victim blaming about rape, my interest in this book dropped to little more than a poorly substantiated drive to finish what I start.

(comment on Stranger In a Strange Land)

My fantasy is to have enough money I could launch a quit capitalism collective. We'd just work on dogfooding alternative systems full-time. Launch non-quantified value currency and business models, transparent and regenerative supply chain systems, community reinvestment and antifragile feedback loops…
#antiCapitalism #nonquant #SemanticCurrency #collectiveAction

What I hope for from AG-UI actually doesn't need AI at all. I am hoping for a human-centric #UXD layer that could be the front-end component of a #ComposableComputing / #MalleableSoftware / #BrutalistComputing / #PhenotropicProgramming paradigm, unlocking for common users most of the functionality of modern computing that most have relied on app developers to eventually roll out for them.

I have come to appreciate, through this book, the "ethical" in #ENM. Before, I thought it was simply a necessary defense against the seemingly ubiquitous critical assumption that anything other than monogamy is unethical. But as I have listened, I have realized that, of course, #ethics drives the whole movement, and ethics circumscribes mononormativity, and ethical questions are the substance of every individual's decisions about how to love the people they love. It's all ethics! Honestly, maybe ENM could be defined as the ethical study of love and family, and the cultural practices framing them.

(comment on More Than Two)

@delta having *the same app* bridge people on existing email infra to the #privsec crowd has always been the biggest strength I appreciated Delta Chat for. forking, dropping legacy SMTP, or any such abandonment of that bridge would turn Delta Chat into just another chat protocol in my eye. if I'm going to push people to adopt secure messaging, Signal would always be the easier sell.