WarrenBuffering

[WarrenBuffering @WarrenInTheBuff]

@0xsnafuu opus and fable always seem to nail it until I look under the hood

[WarrenBuffering @WarrenInTheBuff]

The Great Retraining

[Geiger Capital @Geiger_Capital]

AI bubble just popped.

[fr3tus — 🇺🇸/acc ⏩ @Icalbert101]

https://t.co/fLUuOvo5tS is LIVE!!!!!!!!!!!

[WarrenBuffering @WarrenInTheBuff]

@brim006 hell yeah

[WarrenBuffering @WarrenInTheBuff]

@aidantilgner God speed soldier

[WarrenBuffering @WarrenInTheBuff]

"Do you wanna try to go potty beforehand?"

"NO! I WANNA PLAY THIS GAME!!"

"That's not a game... that's a glue stick"

life with a 3 year old

[WarrenBuffering @WarrenInTheBuff]

@moshettt if the skill isn't easily identifiable and discernable via your repo code, its either a bad pattern or bad code

[WarrenBuffering @WarrenInTheBuff]

the newest goal for my repos is to have and need zero skills

[WarrenBuffering @WarrenInTheBuff]

@OnAirMarc lmfao true

[WarrenBuffering @WarrenInTheBuff]

@bcardarella That reddit post sounds like they aren't even validating them, just relaying whatever slop it spits out

[WarrenBuffering @WarrenInTheBuff]

"Review the entire software industry for security vulnerabilities and report your findings readonly. Make no mistakes"

"Reviewed the entire software industry, here's what I found:"

✅ Good find, correct it
⛔ 0.00002% chance of ever happening
✅ Good find, correct it
⛔ Intentional behavior
⛔ Eventually consistent, keep simple
⛔ Intentional behavior
⛔ Impossible behavior
✅ Technically correct, kinda semantic
⛔ Eventually consistent
⛔ Intentional behavior
⛔ Intentional behavior
⛔ What?
⛔ No
⛔ Okay seriously wtf are you on about
⛔ Wrong
⛔ No
⛔ Don't touch it
⛔ INTENTIONAL BEHAVIOR
⛔ Literally could never happen
⛔ Adds complexity + breaks it
⛔ THATS HOW THE FEATURE WORKS
⛔ GO PLAY IN THE STREET

[International Cyber Digest @IntCyberDigest]

Tailscale replied on Reddit:

Hi folks, Mike Shaver here, VP of Engineering at Tailscale.
We've seen the concerns about Tailscale SSH and wanted to share what we know so far.
If you want to jump to the most important part, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
We've now received the researcher's report and are reviewing it. Our engineering and security teams had already been investigating independently, with help from external security specialists. That work has identified issues we're working to fix. We're still validating the full scope, including which configurations are affected.
A bit of technical context:
Tailscale SSH uses your tailnet's access policies to control who can connect to which machines. Most of the issues we've identified so far concern what happens after someone has been authorized to connect, particularly how Unix privileges and SSH forwarding are handled. In some cases, a session may be able to do more than the configured local user should be allowed to do.
While it’s a serious concern, it isn't the same as an unauthenticated attacker being able to connect to arbitrary machines, but the potential impact depends on how SSH access is configured. We're still investigating, so we don't want to make blanket claims about what's affected or not.
Again, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
In the meantime, there are a few precautions you can take:
•Review your SSH access policies. Make sure only the people and devices that need access have it.
•Review SSH forwarding permissions and remove access you don't need.
•Consider enabling SSH check mode for an additional authentication step. This won't fix privilege escalation issues, but it does add another barrier to gaining access.
•Enable automatic updates where supported so you can pick up fixes when they're released.
For particularly sensitive systems, consider temporarily tightening your Tailscale SSH access policies while we investigate, so that only the specific users and devices that need access can connect.
We're working on fixes and testing them carefully. We'll publish a security advisory explaining the confirmed findings, affected configurations, recommended actions and available patches. We'll also follow up with a more detailed technical write-up.
If we find anything that changes our assessment or requires immediate customer action, we'll communicate that.
We know it's been a rough week for security teams, and we understand why people are concerned. We'd rather give you the technical context we have than speculate about things we haven't confirmed yet.
We'll share more as we verify the details. If you have any questions about how this relates to your particular environment, please get in touch with our team https://t.co/7IoOu6oev4

[WarrenBuffering @WarrenInTheBuff]

@swlkr @TomCruise are you seeing this?

[WarrenBuffering @WarrenInTheBuff]

I know people keep saying tests are worthless with AI, but integration and e2e tests let me totally refactor and deslop an entire app this week

keeping test outcomes and assertions unchanged lets you make drastic changes pretty confidently

[WarrenBuffering @WarrenInTheBuff]

@wonbyte doesn't take long to read if you've explicitly prescribed and know exactly what you want!

[WarrenBuffering @WarrenInTheBuff]

SLOP BE GONE!!

[WarrenBuffering @WarrenInTheBuff]

I know people keep saying tests are worthless with AI, but integration and e2e tests let me totally refactor and deslop an entire app this week

keeping test outcomes and assertions unchanged lets you make drastic changes pretty confidently

[WarrenBuffering @WarrenInTheBuff]

@swlkr that is stealing btw

[WarrenBuffering @WarrenInTheBuff]

@0xCordeiro I was hacked!

[WarrenBuffering @WarrenInTheBuff]

@imyerf now it's where it belongs. in a plastic bag in a landfill, perfectly preserved, forever

[WarrenBuffering @WarrenInTheBuff]

@brim006 hell yeah

[WarrenBuffering @WarrenInTheBuff]

@aidantilgner switched Astra Med bc it let me deliberate and beat down everything forever since it implements fast af

[WarrenBuffering @WarrenInTheBuff]

@aidantilgner oh, yeah for this work I handheld it and made it show me the exact code pattern it was going to change to for each interface. have run our human written e2e automation and everything passes. fingers crossed

[WarrenBuffering @WarrenInTheBuff]

@SledgeDev oh no are u ok?