pdantix

feels like they're trying to get ahead of superlogical's rex.

took all of installing it on windows and setting up my mac as an SSH machine to see the slop all through the UI. i'll just wait for rex's windows client i guess.

i've seen phantom latency when enabling cache rules. by default cloudflare doesn't cache JSON responses, so you need a cache rule to have it respect Cache-Control headers.

my latency to US east is around 200ms. putting cloudflare in front of it has negligible cost. enabling a single cache rule on a specific path added anywhere from 300-600ms latency on every route, just completely untenable.

tried it again recently and it seems to be fixed, but it was pretty frustrating couple weeks trying to debug what was wrong in the first place.

makes me feel old recognising momo from the alteriwnet/fourdeltaone days

it's still so garbage though.. on a 4K display:

- only half the sidebar is being used, by the "top repositories" section

- i have my own agent and want copilot purged from view completely rather than being the first central item of the dashboard

- why is the changelog taking up 1/4 of the screen? move it to the navbar as a popover

- the content doesn't go full width so i'm losing a column or two worth of content

PRs and issues sections are the least worst parts of the dashboard and they're still worse than just using /notifications as a dashboard.

completely worthless.

they've already said in both the opus 5.5 and sonnet 5.5 blog posts that haiku 5.5 is coming

good thing we have a political party in NZ campaigning for LVT + UBI then!

personally, i would not rely on opus 5 end to end as it'll start getting into walls of comment slop and shitting up the codebase similar to gpt 5.5's isRecord meme.

on the other hand, having fable plan and orchestrate with opus implemention + fable reviews, is my go-to. if you give fable your guidelines up front or in your {claude,agents}.md, it will keep opus on a tight leash. opus can still write great code almost on par with fable, but it needs to be tightly constrained.

vbulletin 3.8 was peak for me. the 4.x major broke a ton of mods so there was still a huge community sticking to 3.x. was a big fan of xenforo too, the default design was quite refreshing compared to vB and IPB

i already have an extremely low view of openai and their staff, but this is lower than i thought they'd go

the only ones {i use,claude decides to use} regularly come with claude code plugins so they automatically update. i just define the marketplaces and plugins in my .claude/settings.json for the project.

which is really funny/sad when you see openai staff doing victory laps whenever claude code copies one or two small codex features like /goal.

another vercel labs thing that's been slopped together, hyped up on twitter and then left to be forgotten about in a few months time.

> Most of this article seems like... common sense?

i think you'd be surprised. every model release there's seemingly hordes of people who proclaim the new model is terrible and they're going back to the old one, and it all stems from people still prompting and having their configs setup like we're back in the sonnet 3.5 days

it's extremely enlightening seeing the difference in response to mythos vs. this. literally just the hello human resources meme

recent gpts are horrendous for this, whereas recent claudes have a tic where they incessantly add useless comments referring to previous changes and will use multiple single-line comments instead of a standard multi-line docblock.