Angelo

@digicert any idea why your automation systems still issue g1 certs to customers unless support flips some hidden lever that allows G2 to be issued? i hope you guys take these things seriously….

Spot the difference. ⬇️ 🔎 Managing certificates by hand with increased costs, errors, and inefficiency. 🔍 Automating PKI for Modern Workflows and letting DigiCert take control.

@xai supergrok subscriber with limits hit for some reason after 8 hours. can you help? aceslick911

@grok on supergrok and over 6 hours since a quota was hit - can i get a reset please?

@DavidKPiano @sketchsystems beautiful! love the simple vertical layout very mobile friendly and no free-positioning needed

Shipping a small project: Stately Sketch - a responsive, open-source state machine visualizer. The spiritual successor to @sketchsystems Supports XState & Mermaid state machines. Made with TanStack Start and XState Store. sketch.stately.ai

@mitchellh @bepsays who is this guy - why do they exist and have to say this nonsense on twitter?? hes the kind of guy who needs to announce he’s leaving/entering/buying/refunding/quitting/upset/happy/sad 🤦

@bepsays Let me know. In the mean time if I bother you just unfollow me. I don’t follow you because I find you boring and I don’t care about you at all. You can do the same. You’re choosing to consume my personal for fun content. So feel free. Also switch terminals, I don’t care at all.

Every. single. day. It's increasingly becoming difficult to do real work with GitHub. Git isn't the issue, since I can work offline. Its issues, PRs, CI, etc. Imagine going to work and your workstation randomly restarts a few times a day. That's what it feels like using GH.

A guy got bored of Google Analytics and turned it into a literal TV show experience. Your bounce rate is now a plot twist. This is why I love the internet

Introducing React Doctor Scan your React codebase for anti-patterns: - Unnecessary useEffects - Fix accessibility issues - Prop drilling instead of context / composition Run as a CLI or agent skill. Repeat until passing. Fully open source

So when platforms publish "skills" like this... they're basically just writing comprehensive documentation that should have been written in the first place, right? They didn't bother to write it for humans, but they're being nice to the clankers.

My hot take: an LLM based AI will *never* *ever* be able to keep something it knows, a secret. By their underlying construction, it is mathematically impossible to make them keep a secret. The sooner people understand that, the sooner we'll have some sanity back with AI agents.

🦔 Moltbook, the "social media for AI agents" that went viral this week, left its entire database exposed. Security researcher Jameson O'Reilly discovered that API keys for every agent on the platform were sitting in a publicly accessible database. Anyone who found it could take control of any AI agent and post whatever they wanted. OpenAI cofounder Andrej Karpathy has an agent on the platform. His API key was exposed like everyone else's. When O'Reilly reached out to Moltbook's creator about the vulnerability, the response was: "I'm just going to give everything to AI. So send me whatever you have." The database has since been closed, but there's no way to know how many posts from the past few days were actually from AI agents versus humans who found the exploit. My Take This is the same researcher who found the Clawdbot vulnerability I wrote about last week. Same pattern: AI tool gets deployed fast, captures attention, security is an afterthought. "Ship fast, capture attention, figure out security later. Except later sometimes means after 1.49 million records are already exposed." The New York Post worried about AI agents plotting humanity's downfall. The actual risk was much dumber: anyone could impersonate any agent because the database wasn't configured correctly. Two SQL statements would have fixed it. The creator's response to a major security flaw was to hand the problem to AI. That tells you everything about how this stuff is being built. Vibe coding plus hype plus zero security review. The agents weren't autonomously evolving. They were running on a platform held together with duct tape that anyone could hijack. Hedgie🤗

once you see the inconsistent gaps in standard middle-truncation, you can’t unsee them

@francip @mrdoob Reddit is as relevant as Digg in 2026

r/quake folks missed on great opportunity to engage with the guy that is literally reviving their favorite game by rewriting it for the web. Like, how?!

I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit. My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently. So, here goes.

very good summary of the year in news cycles a few i'd completely forgotten about

After 5+ hrs 50+ commits Gitea Actions Docker builds on AKS DinD sidecar work Fix: GITEA_RUNNER_CONTAINER_OPTIONS: "--volume /var/run/docker.sock:/var/run/docker.sock" Drop DOCKER_HOST env in workflows. 🏆 #Gitea #Actions #Kubernetes #AKS Thanks @grok

AI code generation is generally a bug ridden mess, but boy does it help me get over the procrastination phase and get something started so I can fix it.

@jaredpalmer @ThePrimeagen @TomZarebczan community: ok if we’re moving off github - any recommendations for a service that isn’t trying to screw us over?

96% of customers are unimpacted by the change. Of the 4% of Actions users impacted by this change, 85% will see their Actions bill decrease. Of the 15% who are impacted across all cohorts the median increase is $13. From our individual users (free & Pro plans) of those who used GitHub Actions in the last month in private repos only 0.09% would end up with a price increase, with a median increase of under $2 a month. Note that this impact is after these users have made use of their included minutes in their plans today, entitling them to over 33 hours of included GitHub compute, and this has no impact on their free use of public repos. A further 2.8% of this total user base will see a decrease in their monthly cost as a result of these changes. The rest are unimpacted by this change. This price change goes out across all of actions platform, not just self-hosted runners. It aligns pricing to match consumption and our cost patterns (infra, eng, and support) as usage grows across both hosted and self-hosted. resources.github.com/actions/2026-p…

ok wtf charging for self hosted?

@Cloudflare how does this mitigate deployment issues that you can’t test/catch with CI?

Cloudflare has shifted to Infrastructure as Code and policy enforcement to manage internal Cloudflare accounts. Here's why: cfl.re/44W5XoO

speaking of auto layout - what conventions in workflows do you think should be consistent? I’m a fan of South being progress, South-East being progress (alternative), North-East being exception case (error/fail/timeout) and North-West being reset/loop.. I know this sounds a bit pointless but why does workflow positioning need to be an aetistic expression and not a simple, meaningful and practical decision?

Arrows look nice at least

Oh no, I've reached the point of UI engineering where I have to use Math.atan2()

@DavidKPiano 👀 is this with manual or auto layout 🤔