stryan

Ah, I didn't realize the tarballs on the Tangled site were cached. If it happens again I'll try that :)

But yeah I recognize it's an issue for any package manager. I suppose I just forgot that even something like my local editor is reliant on remote forges now unless I go out of my way to mirror it all.

Really looking forward to seeing Tangled develop! I've got a side project that's main repo and CI is on my self-hosted Gitea but code and releases are mirrored to Github; I'm hoping to move it off Gitea and onto Tangled for code/releases/potentially CI and just keep Github for discoverability/backups/namespace "squatting". Just need git-bug to add a Tangled bridge so I can keep issues synced and (ideally) for there to be instructions for running the client self-hosted. It doesn't have to be a full featured client but I also don't want to be SOL for web visibility if the main Tangled appview is down.

One musing: I did run into my first "issue" with federated Git hosting the other day while setting up Neovim on a new machine. One of the plugins I use is hosted on Tangled and I guess its backing Knot was down. This was awkward for two reasons:

1. It as unclear to me from the Tangled website the backing knot was the issue (for a while I thought it was something on my end)

2. I really had no backup plans for something like a Neovim plugin's source forge being down and, clearly, neither did the Neovim package manager as it just kept showing an error on every session I started with no way to fix it :).

I suppose in the long run we really shouldn't be assuming that code storage is just Always There or easily cached somewhere, but I anticipate some growing pains in the mean time. ATProto doesn't seem to have the benefit ActivityPub has where if the instance I wanted to view content on was down I can usually find some other instance that's gotten the messages.

Throwing out some thoughts after reading the docs page(s):

1. The "What are trails" section does not actually tell me what trails are; it tells me it brings agents and devs together, and that branches are involved somehow through "changes", but it doesn't actually tell me what they are

2. I am never going to willingly watch a Youtube video embeded in docs. I'm barely going to watch a video in a docs page at all. I'm here to learn how to use something, not see a sponsored ad for NordVPN.

3. The marketing blurb, the top half of the docs, and the bottom half ("Enable Trails" onwards) all feel like their describing different things. The marketing blurb describes a total reinvention/view of the PR layout where instead of seeing diffs you see different bars that you can balance by telling the bots to keep reviewing/changing. The top half of the docs sounds like some sort of spec description system and absolutely reeks of LLM speak.

4. The rest of the docs make more sense: Under the web UI tab for "Create a Trail" I finally see what a Trail looks like (a simplified Jira ticket or GH issue) and I start actually understanding that this is an elaborate "built for AI" version of stacked PRs, CI checks, and project management.

5. The Agents and Gates subdocs are where content starts getting interesting and the documentation quality is a lot better. I am actually getting interested in this product.

I still don't fully understand what and why I would want Trails, but I suspect I'm not the target audience. There's bits of it that certainly look interesting but having to swap all my infra over to Entire is a hard sell.

The graph generator looks interesting, but the rest of the blog post is filled with so much marketing it's a slog to get through to the good bits. I struggle to imagine a scenario where I willingly choose the "Trails" view even if, and god help us if it is, that's the direction PR review is going.

Yeah I'd love to see/hear some examples here; I mostly listen to small-to-mid-level black/doom/trad/power bands and haven't noticed this type of standardization of sound.

It's possible I don't have the ear for it though, so now I wish the article had posted how it made this type of analysis so I could run some of my albums through it myself.

Fnox (by jdx of mise) supports fetching secrets and caching the results either in local age encrypted files or in a background daemon (in memory only) to minimize repeated gets. The daemon is per terminal instance too I believe so you fetching a secret once doesn't store it for the whole session.

It's not a perfect fix but it keeps secrets out of env with (so far for me) minimal inconvenience.

You can't do just an email address, but if you're running your own domain you can do your own OIDC with it. My tailnet auths against my self-hosted KanIDM server.

Podman supports using KVM backed virtualization for containers via libkrun: `podman run --runtime=krun` . Still not the end-all-be-all security boundary, but better I think.

I wish they had an actual feature comparison list. I've been trying to find anyone who can give me a list of non-trivial differences between the two; so far it's always either FUD about Gitea's governance and security structure or ForgeFed. The former has made me rather wary of the project[0] and the latter has been stagnate for years and I'm no longer convinced anything will come from it. Otherwise it's just silence.

Personally I thought Forgejo was doing better work on their actions runner for a while from casual changelog browsing but Gitea's been putting a lot of work into theirs. Otherwise it mostly still looks like a soft-fork in practice to me.

[0] Not that I'm thrilled with Gitea's semi-open-core setup and company but they make it seem like they're kicking puppies and dangling features over non-enterprise users head before snatching them away.

It was easy to ignore before it "raised" around 15 million dollars. That's a lot of money to be throwing around a mostly-donation based ecosystem.

I'm already seeing discussions on the mise[0] Github discussions about Omarchy specific changes and designs. I'm not saying anything about these specific changes and they seem mostly distro-agnostic for now, but it goes to show how it can affect other distros/software even if you don't use it.

[0] mise is being sponsored by the Omacon foundation, which is what all this money is technically going to. It also happens to be the only "independent" tool being sponsored by the foundation, as the hyperland dev is essentially contracted by them and the QuickShell dev was hired by DHH.

> Also, Japan doesn't actually have a 'colonial history' having never been colonized by another nation.

It was never colonized but I've often heard it talked about in a similar way due to the effects of the Commodore Perry and the post WWII occupation (i.e. see their infamous pornography laws), as well as neighboring affects from China's colonial history.

>Japan has ultra processed foods and they don't seem to have an obesity epidemic.

Most of that's from a much stronger national guidance on weight control + societal expectations, but IIRC they also are gaining weight. Their ultra processed foods (in the salt and preservative sense) are also why they have one of the highest rates of stomach cancer.

> They also don't have a marijuana epidemic.

Not sure if I'd categorize the US as in a marijuana epidemic (and this is coming from someone who doesn't consume it and dislikes being around it) but even if we were, the states with the highest marijuana usage (west coast and NE) and the states with the highest obesity rates (deep south) are almost non-overlapping circles. If we're tying a drug to be obesity rates I'd be much more willing to believe it's the American propensity to chug large amounts of cheap 100-120 calories a pop beer.

I don't think there's a way to really say a comment like this "with all possible respect" given the (albeit meager) content of the article.

Either way, I'd be much more willing to bet that if Toady had Opus/Sol/whatever we wouldn't have Dwarf Fortress, we'd just have Rimworld: perhaps a technically better game, but not !FUN! in the same way Dwarf Fortress is fun.