Kogasa

You do definitely need some agent-specific guidance locally. The committed AGENTS.md should be pretty sparse. Ironically I think the clearest use case is for instructing agents that AI contributions are not allowed. Not that they won’t ignore it if prompted.

You’d put the things that aren’t up to personal preference in there, like an AI disclosure / contribution policy or what changes should look like to be reviewable. You usually don’t need to tell humans “don’t change things for the sake of changing them” because we don’t like to do more work than we have to, but agents do.

You can also include a compact “table of contents,” describing what lives where in the project. It saves at most a little bit of exploration though so I don’t know if it’s really worth the maintenance

No, we can’t. The biochemistry needs to be there. The fly brain is a discretized abstract model of the fly brain with none of the weights it would need to be an actual (discretized abstract) model.

You shouldn’t. It’s just a neural net shaped like a fly brain. There’s no biochemistry simulation past that.

sparkling arch, sparkling fedora, and diet arch

Arch teaches you to exercise muscles that would otherwise atrophy. Understanding how your system is put together, how to diagnose and fix problems, how to handle upgrades safely. It becomes just as easy as any other OS and you’re better off for it.

It would be trivial to add online only drm with a killswitch to physical media. If that’s the problem, discs aren’t the solution. What we actually need is legal protection for consumers.

Nothing, bias from the .NET Framework days probably

Using aur helpers is fine if they make it easy to read the pkgbuild, which paru does. It’s too annoying to check for PKGBUILD and upstream/vcs updates for each package individually.

Ideally the aur helper would point out when 1) a package changed maintainers since your last install, 2) a package’s PKGBUILD itself changed (not just the upstream/vcs source), 3) the PKGBUILD is less than 24h old or so. And for #2, it should also show you the changes similar to what you see on the AUR site’s “view changes” page. I’m not aware of any aur helper that does these things, but hopefully recent events prompt a change.

Haven’t really looked into it. I have Jellyfin set up and ready to switch over already. Maybe I’ll check it out when Plex blows up

They have a sorta proprietary metadata service that is presumably based on imdb, thetvdb, etc. but they also handle detection and collection of metadata regardless of where the information ultimately comes from. It’s nothing that Jellyfin doesn’t do though.

I’m sticking with Plex since I have the lifetime pass too, but the writing’s on the wall, I’m ready to switch to Jellyfin whenever Plex dies or ruins itself

They provide the apps, metadata servers, and relay service. It’s a lifetime pass. IMO that’s worth the price it used to be, $70 or whatever. The new price is just absurd, they want you to pay periodically for life because people spend more that way.

https://en.wikipedia.org/wiki/Contractibility_of_unit_sphere_in_Hilbert_space

I can offer no ELI5 but here’s the context

A Riemannian manifold isn’t necessarily non-Euclidean, it’s just a smooth manifold with a Riemannian metric, which is just sort of a way of defining local geometry in a coherent way. Namely it’s a smooth family of inner products on the tangent spaces at each point, where an inner product on the tangent space is sort of a way of comparing any two directions at a point and the smoothly varying part means that for sufficiently close points, the comparison function on their respective tangent spaces is similar.

Anyway, like “manifold” is a formalism intended to capture the idea of a “shape or space,” a “Riemannian manifold” is just “a shape or space we can do geometry on.”