How do you access Claude from the multiplexer? AFAIK Anthrophic allows the use with their official tools only.

I have created wrappers for Codex (https://github.com/micw/codex-wrapper-advanced) and claude (https://github.com/micw/claude-wrapper-advanced) that uses their SDK (Codex) and the CLI (Claude) internally to align with the subscription ToS and still have a common API ;-) This way I can use both in any harness and can easily switch between both.

Clor uses the official `claude` and `codex` harnesses directly, with a web interface, or via a web TUI interface.

Also not available in their business offer. So I have now a $20 business plus a $200 "personal" plan in my account.

Yes, it should. Reduces a lot of noise.

The idea looks interesting. But when I think of "make incident recovery easy", the very last thing I want is a fork that differs from the standard that everyone else is running. I would have a better feeling if that would be an extension, not a fork.

From the README,

  It is PostgreSQL 18. One piece, read-dependency capture, has to be in the engine, and it ships as a small upstream-tracked patch. Extensions including pgvector, your ORM, and your SQL dialect all work unchanged.

https://github.com/eterdb/eterdb#how-it-works

Yes, so, in other words it's patching the internals. And the "how it works" is vibeslop.

I would even think that "smart" and "lazy" has a strong correlation ;-)

If you give a smart one a task, he will look for a way to do it with lowest effort. Probably most would do it but the smart ones will find way more the shortcuts, automations and exploits.

Edit: also smart people will more often ask "why" if a task makes no sense to them.

I think there's an overload of the meaning of 'lazy' that describes a person who measures twice and cuts once, basically thinks the problem through rather than just piling on it. And as you said, they might even conclude the task isn't worth doing.

Since thinking is not a visible effort, these people are taken to be believed to do less work, when the truth is anything but.

Tetris on postgres? Not doom? So not a candidate for everything!

Just kidding. Of course there's doom for postgres: https://github.com/cedardb/DOOMQL (pure SQL) and https://github.com/DreamNik/pg_doom (extension).

Oh and there's https://github.com/snaplet/postgres-wasm that allows to run everything else in postgres ^^

What does the (currently latest, https://github.com/systemd/systemd/issues/40262#issuecomment...) comment mean? Who are the "large folio people"?

So is this a regression or a bug in systemd triggered by this change?

systemd-journald also has rate limits that you can configure ;-)

IIRC those are "dumb" rate limits though, aren't they? I.e. if 1000 of the same dumb message comes across from the service then you'll rate limit out the 3 useful messages occurring at the same time.

I also saw this when I made a (personal use only) book translation (agent learns how book 1-3 of a row is translated, then translates book 4 the same way because it is not available in my language). Claude happily translated most of the book, except a few chapters which it denied. Tried several times always the same results (with no other context about the rest of the book).

> if you see an ad somewhere [...] close the tab immediately and never return to that site

I would even extend this: if you are bugged by an ad, avoid the product, the vendor and tell everyone why you do so. Also tell it to the vendor, why you avoid their product (aggressive, non blockable ads at facebook for example).