internet101010

I rarely wish for the downfall of things, but StackOverflow is one of those exceptions. Good riddance.

Used to use Porkbun but now I just use Cloudflare because everything goes straight there anyway.

Pack ripping was huge during COVID. It is always more economical in the long run to buy singles than to rip packs. Generally speaking, the primary purpose of mystery boxes is to dump slow-moving inventory.

Yep. In my very limited experience with PCB design most of time is spent sourcing parts, not designing the PCB.

The two issues I have had in 20 years of Apple laptops is the butterfly keyboard and the GPU causing discoloration of the screen, both on the same MacBook Pro.

That said, I think over the years I have gotten three or four random checks in the mail from Apple over the keyboard, and they fixed it outside of warranty. With those MacBooks, you have replace the entire bottom assembly (keyboard, battery, speakers, etc.) and it isn't cheap.

Same. I made the mistake of adding the downloader to it at the start but brute forced my way through. Single Rust binary for all of the *arrs + sabnzbd is nice though. Unfortunately it is not something I am comfortable making public due to the all-in-oneness of it.

Almost all of the time went to to the downloader (usenet is more complicated than I thought). If I had just focused on the basics (sonarr, radarr, seerr) I could probably could have knocked it out in a day or so.

I have done several of those things on the list in just the last three weeks. It's amazing. Never been more excited about building.

I only keep an OpenAI sub for Daybreak Blue at this point. It's pretty easy to get access to, but requires a Yubikey.

Discord is incredibly popular among younger people in general now. It escaped tech people containment years ago.

It's the exact same thing. I have a hook that automatically sends negative feedback anytime it responds with "You're right –"

The worst trend in UX in the last decade is the endless "Got it!" popups and feature notifications that distract the user from what they were trying to do.

I don't know why anyone would ever willingly want this.

Long legs to illustrate me attempting to stretch my budget by using Haiku the last week of the month.

Microsoft bloat really knows no bounds.

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.