internet101010

Yep. Proxmox, Kubernetes, ARC, and t3 code threads spawned inside of kata containers is my current workflow.

Better than the feed. But I still go straight to the left sidebar for repo 90% of the time, and the random ordering + "show more" is incredibly frustrating. Let me set permanent sort and default to show more. The contents of the right sidebar (what's new) do not need to exist at all.

Or just skip all of this BS and let us design our own homepage with pre-defined components.

What do you mean by the "React" of this space? The overall base layer has more or less converged on Kubernetes + MicroVM, which makes total sense. But if you mean how to interact with it as well as how permissions should work, yeah I agree.

Eh, StackOverflow deserved to go.

Windows 11 has been out for like 6 years and they still haven't fixed a major File Explorer bug: after a few minutes of File Explorer being open the menu bar for the old File Explorer pops up underneath the new thing that replace the menu bar; none of the buttons on this weird artifact from the past work. It's just there. Re-open File Explorer and it goes away, until a few minutes later and it re-appears.

Not as noticeable on light mode but a constant distracting reminder about how much Microslop sucks on dark mode.

The expectation line should be drawn at whether or not your existence in public results in the monetary gain of the entity that captures/uses the data.

Don't they already do something similar but with Shopify? Like you buy on Amazon and then Amazon scrapes the internet and buys from a Shopify site without the seller's or user's consent.

"more misguided than Doom on a pregnancy test" has been added to my lexicon.

I see "acquire" followed by "Tail" and I get concerned. This is fine though.

Things like when to cancel early, how to handle par2, obfuscation, rars within rars, decoding articles. Just a mountain of "huh, didn't think of that being a complex problem" that was resolved over time.

I was able to replace the arr suite + sabnzbd with my own rust+ts frankenstein but had I known how complex the usenet piece was going to be I would have separated it into two phases.

If there is one thing that needs to be re-written and consolidated it is the arrs ecosystem. Replacing/consolidating the arrs themselves is pretty straightforward. The trap that quickly becomes a token incinerator is incorporating the downloader into the library manager itself. A lot of learned lessons in that sabnzbd codebase.

Put gates in place to block all .freeadvertising folders except for the ones that the project relies on.

I used to think that until about an hour ago. I am redoing my homelab and asked four agents in Buzz (5.6-sol, opus-5, fable-5.1, glm-5.3-flash) to use references from Hackers (1995) to answer two questions:

1. What should the terraform repo name be?

2. What should the avatar image be?

Obviously all four said "gibson" for question #1. But for #2 is where things got interesting. glm-5.3-flash and gpt-5.6-sol both suggested the guy standing in the hallway with the skateboard in the gibson. fable-5.1 suggested the cookie monster "need more cookies" screen that shows up toward the end.

But Opus 5? I'm paraphrasing but basically "run this series of ffmpeg commands to get the exact frame at the beginning of the movie when the shot of New York fades to the shot of the Gibson. You have to catch it mid-frame. It explains your project perfectly. The skateboard thing is cliche and the cookie monster recommendation suggests you getting locked out of your own network, not the best look." And it was actually a decent idea. Funny that it also just assumed I had a copy of the movie on hand.

I already pipped Opus 5. That thing is a tool.

I think you and I are cut from the same cloth. Role-based pipelines and coordination with scoped permissions generated at runtime and the ability to communicate is the end game in my opinion, for now at least. Orchestration finally clicked with me when I tried out Gas Town six months ago and I immediately created a system to offload it to the cloud by using a combination of GCP CloudRun + Firestore (for temp file storage and to fill role of beads). Right when I finished ironing out the kinks Anthropic laid down the hammer on how users can use subscriptions and I abandoned it.

Now I am using custom pipeline/messaging control plane that spawns microvms with scoped creds minted at runtime. I had to make my own control plane specifically because everyone is focused on agents with personalities rather than roles and pods of workers. I like everything about Buzz except for that.

The Apple TV solutions for Jellyfin are inadequate last I checked. Basically you are stuck with Plex and Infuse. I already have lifetime Plex Pass so no reason to care... for now.

No. I will generate code in a way that makes it easier for clankers to maintain it, because they will actually be doing the maintaining. In practice, this means that most of my time is dedicated to improving the repo harness because the state of the repo harness directly determines the quality of the codebase as a whole.

At a minimum, there should be precommit checks and CI workflows that cause PRs to fail if the documentation is not up-to-date and synced with the other docs.

Then regular codebase analysis for improvement. This is where you find the bug sources, make new modules for consolidation, and get those +5000/-4000 PRs that people stuck in the world of manual code review hate.

I have Fable send the specs/plans it comes up with to GPT for review and in 2/5 cases yesterday it found additional 1-2 bugs while in the process of reviewing.

GPT-5.6 didn't try to fix the bugs (as instructed) but it did surface them, which is something that didn't happen with GPT-5.5. When spec/plans approved Fable sends back to GPT-5.6 for ralph implementation and it seems to be an even faster, more reliable workhorse than it already was in GPT-5.5. Overall, impressed. Will continue to be a core piece of my workflow.

Long time user of btop. Only thing it is missing is a ports column next to the others. Also I think the cpu/gpu graph graph is way oversized and would like more space occupied by the open file table in general.

Exactly. If the repo has all of the knowledge living inside of it that window fills up fast, even when using something like codegraph.

In my limited experience of seeing Dutch auctions in practice it actually has the opposite of the intended effect, as the people that are willing to pay the highest are also the people that will have a way to profit, just on a lesser scale.

For example, Panini (sports card manufacturer) did Dutch auctions on boxes of new card sets during the peak of pandemic collectible mania. The majority of customers that were willing to pay the highest prices on Panini's website were card breakers, which are people/companies that sell "spots" in livestream box openings (i.e. customers buy the right to all cards containing players from a certain sports team before the box is opened).

Cursor's moat is that it is a virus that infects organizations through shared skills, hooks, agents, etc.. Once one person uses it and infects the repo everyone else starts using it.

The closest thing you will fine to a dumb tv is a commercial display, which will not be available with the latest OLED, 120hz, etc.

You have to buy a smart TV and disable the internet + external device like Apple TV or Nvidia Shield.

It's a huge jump across the board. I was really impressed with its ability to test usability in Claude for Chrome. Very opinionated but in a good way. It was good while it lasted.

I do file summaries as well. Basically a knowledge base commit hook + agent that creates/updates a file containing a summary and list of its dependencies, followed by updating an index to include it. Super useful for creating system migration scopes and just managing context in general.

Indefinitely for these big mundane grunk jobs. In every scenario it is going to be cheaper and faster than lobbing it to Infosys.

Lol wut. One of first things people do at a company when they get enterprise LLM tools is share a skill with company-specific color palettes or standards for creating visualizations (I prefer Tufte's principles).

Hooks are incredibly underused by most people and are the easiest way to establish a first line of defense against bad behavior. Things like blocking tool calls that will read .env file or execute "create or replace table".

Totally agree. Was just trying to emphasize that there are better ways to do this if privacy and security are something that Yoti actually cares about. ZKP is not a magic bullet.

The third-party list on page 12 is not small. The real-time api architecture creates a live, per-query link between a specific user event and every broker in the chain. Batch transfers or delta shares would break that linkage. Zero-knowledge proofs (also mentioned in the study) can prove age without handing anyone a name, document, or photo.

There's no reason Aristotle or Veratad should see who the underlying requestor is. Yoti should receive the verification request, strip the context, make the request - that's it. The fact that it isn't structured that way and they are tagging on additional metadata suggests per-query economics, which creates a direct incentive to route more verifications through more parties, exactly backwards from data minimization. I'm not going to call it a rev share, but the architecture is consistent with one.