but seriously did I screw up my algorithm and end up in prepper X or is WWIII starting?
Footage from the Kaepung area shows North Korean soldiers positioned with 122mm self-propelled howitzers, their barrels facing south. The artillery has been moved toward the border with South Korea.
33
50
1,375
67,135
goodbye tech twitter, I've gone to be with my people
it was real, and it was fun, but it was real fun
it was real, and it was fun, but it was real fun
1
0
1
148
It appears For You can now only cover one topic at a time
Condolences to Microsoft friends, but I am glad UK recovered and the grid crisis fears are resolved
Condolences to Microsoft friends, but I am glad UK recovered and the grid crisis fears are resolved
0
0
17
491
wtf just happened to my feed? was trying to figure out which model scores higher than a 72 on recent benchmarks and almost had the answer, but now it's doomer grid (whatever that is) nonsense so I can't even keep up with the npm libraries getting hacked
BREAKING:
Iranian media are reportedly sharing guidance with citizens on how to protect themselves in the event of a nuclear attack by the United States.
Separately, speculation is circulating that Washington could consider a tactical nuclear strike against Iran’s Pickaxe Mountain facility, amid claims that its deeply buried underground structures would be difficult to destroy with conventional weapons.
2
3
69
3,473
"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
"NO! I WANNA PLAY THIS GAME!!"
"That's not a game... that's a glue stick"
life with a 3 year old
5
0
43
940
"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
"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
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 tailscale.com/contact/suppor…
1
0
19
1,648
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
keeping test outcomes and assertions unchanged lets you make drastic changes pretty confidently
20
0
73
3,279
Why are these getting announced before patches and major downstreams have time to release updates?
Evolving threat 🚨 CVE-2026-111497, previously known to affect Node.js (node2shell) and Python has evolved into “HTTP2Shell.”
A significant blast radius.
This vulnerability leaves many libraries and applications using HTTP vulnerable to pre-auth RCE via Brotli decompression. s not yet available for all affected services. Look for Brotli (1.2.1) dependency upgrades when they become available.
18
1
68
4,948