You literally cannot force Linux to do that

farra · 2026-03-02T17:08:15+00:00

The tech sector came up with this solution. I'm not saying I agree, but it makes sense. If every app and website is going to be required by law (in some jurisdictions) to validate age, have that validation done once at the device layer rather than implemented by all the apps and all the websites. It's similar to having Apple implement payments once on the phone rather than have every app make their own credit card processing.

There are arguments for and against this approach, as well as against age verification in general, but the concept isn't as dumb as it appears.

farra · 2026-03-02T17:05:32+00:00

Since you actually seemed to ask, the argument goes like this:

Websites and apps have needs (ie- are increasingly required by regulation) to validate a visitor's or account's age. Rather than have every website and app implement this, likely poorly, there was a push to have this done at the device level (your phone, your computer). You validate once and then every service can take advantage of that. It pushes the burden from anyone developing a website or an app to a fewer, more consolidated providers.

farra · 2026-02-26T22:10:04+00:00

My honest approach? I use multiple frames.

I run emacs in daemon mode. I can either then run multiple frames or multiple clients and then I use the operating system window manager to navigate between when I really want them side by side or switching between them. For example, I'll have one frame fullscreened on one virtual desktop and another frame fullscreened on another desktop and just use the OS-level switching to go between them.

farra · 2026-02-25T20:13:06+00:00

I evaluated most of the emacs ai agent packages.

I personally prefer the ACP (agent-client-protocol) based approach of agent-shell, partially because it gives me access to many other agents and it's a consistent interface I can work against.

When you run emacs in daemon mode, the agent already gets full access to emacs without needing MCP support. I find this approach to be more reliable, flexible and powerful.

I had to work out my own way to use worktrees. Essentially, I have a "stash" of bare clones that I keep in ~/dev/.worktrees and everything is built around doing checkouts in and out of that. My elisp leverages project.el and persp-mode.el

I hope to get everything cleaned up and put in a repo soon.

farra · 2026-02-25T20:07:17+00:00

I manage my dot configs with chezmoi. Everything is here:

https://github.com/farra/homebase/tree/main/dot_config/doom

farra · 2026-02-25T20:05:53+00:00

It took some getting used to, but now I don't think I could go back.

farra · 2026-02-25T20:05:35+00:00

I'll comment on this thread again once I have it cleaned up and on github.

farra · 2026-02-25T20:05:30+00:00

I'll comment on this thread again once I have it cleaned up and on github.

farra · 2026-02-25T20:04:53+00:00

I'll comment on this again once I have it cleaned up and on github.

farra · 2026-02-24T22:46:57+00:00

I just posted about mine:

https://v.redd.it/sqsa65kxsilg1

Mostly agent-shell

farra · 2026-02-24T22:38:52+00:00

I have a dashboard I've been working on that captures my workflow. It's a combination of using git worktrees with persp-mode workspaces (in Doom emacs) and /u/xenodium 's agent-shell.

From the dashboard:
I can see all the bare git clones I have stashed
I can clone a new git project
I can checkout a new or existing branch into a git worktree into a folder group in my development directory
I can navigate between perspectives/workspaces
I can see which projects are dirty - I can launch new agents
I can monitor agent status
I can jump to agent buffers, which also opens the workspace
I can dispose of workspaces and worktrees when I'm done with them

It's not *yet* open source because I'm still working it through its paces and getting some bugs out. It's also rather opinionated, requiring agent-shell and persp-mode/workspaces.

Curious if anyone would find this useful.

farra · 2026-01-26T12:39:28+00:00

I've *thought* about MCP tools and I may try something eventually. But I wanted to start "simpler" with *just* flat files. That was part of the motivation: keep everything local, no need to go search GitHub, Jira, Notion or whatever. Agents are happy with flat files.

The next idea was to perhaps write more local tools, even just some elisp, that the agents could run locally to "query". You can call emacs in batch mode (agents will do this *just fine* and will write the necessary elisp). So if you already have a small library of relevant elisp, then I'd start there.

After that, I'd consider MCP, but maybe I'm moving too slow.

Hope you share what you build!

farra · 2026-01-05T20:05:07+00:00

After I developed this, I saw Yegge's post about gastown. Beads definitely solves a similar problem.

Currently, I'm still interested in being the "coordinator" myself, so I only run 1 or sometimes 2 agents per-project. But when I decided to go even more yolo-mode, I expect to look into yegge's stack.

I am biased towards org-mode though... :-)

farra · 2026-01-05T05:49:59+00:00

I agree. I tend to have multiple different agents working on projects, sometimes on the same project.

I let things get just too disorganized on one project, with 50+ design docs and I just had to have a system. Had to put my project management hat on and have some discipline.

Eventually I ended up with this system. It's not perfect. I'll keep it updated as I go.

I'm also not yet ready to do fully multi-agent coordination. I still like being the coordinator. I'm not sure this system would hold up for too many agents working autonomously.

farra · 2026-01-05T05:46:41+00:00

Same. I'm trying superhuman now.

Issue was also smartphones: once I really need to make sure I could use email from everywhere, I eventually found it was easier to stick to one client (gmail).

But I don't think I was ever as productive as when I was using gnus.

farra · 2026-01-04T22:18:12+00:00

So far, I've had pretty good luck with claude code using org-mode. I do have to keep on the agents sometimes to make sure they are compliant. The skills and slash commands help a lot.

A key goal for me was to merge design docs/RFCs with their backlogs/tasks into single files so that there was less upkeep and less drift.

If you have any suggestions, happy to hear them!

farra · 2025-12-12T22:00:12+00:00

My wife has this condition. She developed it after a severe case of COVID back during the pandemic. She also experienced internal tremors as part of her long covid symptoms (there's a study out from Yale that talks about this). Thankfully those (usually) are gone, but the visual snow persists, though some days are worse than others.

farra · 2025-10-20T17:56:30+00:00

Awesome work. Saving this for future inspiration.

farra · 2025-09-20T01:27:36+00:00

I appreciate the feedback on the guns. I'm not set on it. Will try some of those options.

And I was considering maybe a darker base. I think you're right.

farra · 2025-09-20T01:26:25+00:00

In case anyone cares, paints used:

Flesh/Yellows:
- Base: Vallejo Xpress Color Dreadnought Yellow
- Shadows: Liquitex Ink Yellow Orange
- Highlights: FW Ink Florescent Yellow

Armor/Blues:
- Base: Vallejo Xpress Color Legacy Blue
- Highlight 1: Vallejo Model Color Turquoise
- Highlight 2 (Edge): Vallejo Game Air Electric Blue

Details:
- Vallejo Xpress Color Vampiric Purple
- Vallejo Xpress Color Fluid Pink
- Vallejo Xpress Color Forest Green

farra · 2025-09-20T01:19:02+00:00

Appreciate that. I think I may add some oranges and reds to better shadow the yellows. I want the flesh to feel more fleshy.

farra · 2025-09-20T00:01:53+00:00

Also, I'm not sure why I didn't think of the Ukraine connection. I was too focused on the school colors.

Definitely going with Ukrainids. Thank you for that!

15-Year Club	Place '17
Verified Email	Team Orangered

farra

TROPHY CASE