CEO of @blinklabs_io | Open Source Developer | DRep: drep1yfa8r8r36x7x05htftce7qhafrn5nzzr6vazy95pzy6y5dqac0ss7 | Tweets are my own
Joined October 2010
- Tweets16.1K
- Following2K
- Followers2.1K
- Likes83.5K
Imagine rage quitting simply because of automated scans on an incoming queue.
Multiple Debian developers have announced that they will be leaving Debian, or no longer maintaining Debian packages, following Debian’s use of LLM’s in scanning and evaluate new package uploads.
“how is this not "Debian endorses the use of generative AI"?”
“For now, I will no longer be uploading to the #Debian NEW queue.”
“likewise. I'm about to orphan everything I still maintain in Debian that I don't *have* to maintain”
Watch out for these scammy fucks. This is EXACTLY what someone selling you bullshit looks like. Their strategy appears to be to spam everyone who votes against them. Vote no, then block.
Cardano has an opportunity to pioneer a new model for blockchain treasuries: investing in tokenized physical copper, with a defined path to returning capital and potential profits to the community.
Thanks to all Cardano DReps for the questions and constructive feedback.
We're launching a thread to address your questions
🧵👇
nitter.cf/totofinance/status/211…
You know it's bad when NSA is telling you to upgrade.
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
wolf31o2 retweeted
this week has seen to incredible pieces of cryptography news
1) it's just hashed Unix time (duh)
2) it's 4 (huh?!)
wolf31o2 retweeted
Full details of a remotely exploitable vulnerability in the core engine of *all* PHP versions will be released tomorrow, October 21st. If your organization has internet facing PHP applications then you need to be ready to patch the minute the update is released or *strongly* consider taking the application offline until you can:
php.net/index.php#2026-10-20…
🚨 PHP warns of two critical vulnerabilities as emergency patches arrive tomorrow
The PHP security team will release updates on October 21 at 14:00 UTC for two vulnerabilities, each rated 9.2 under CVSS v4.0.
⠀
Security researchers identified the flaws as CVE-2026-109618 and CVE-2026-109619 and described them as remote code execution vulnerabilities reportedly affecting PHP versions 5 through 8.
PHP has not yet confirmed the affected versions, exploitation requirements or fixed releases.
⠀
The vulnerabilities were reportedly leaked before their planned disclosure. Researchers said they have not observed active exploitation, while PHP warned it may release the patches early if technical details become public or exploitation is detected.
⠀
Administrators should identify PHP installations now and prepare to apply the updates as soon as they become available.
wolf31o2 retweeted
“A human must review every line of code” is an outdated take. It is too late.
Generation and review are both automated and follow rules. There is zero value a human can add now. Anything you can do, can be an automated check done even better.
What you cannot outsource is your own understanding of design and architecture.
I still see some folks skip design reviews and force manual code reviews, and that’s just retarded. Soooo behind.
Well--well look. I already told you: I deal with the god damn customers so the engineers don't have to. I have people skills; I am good at dealing with people. Can't you understand that? What the hell is wrong with you people?
(RIP "Tom")
wolf31o2 retweeted
readme: fix typo
Co-Authored-By: GNU nano 9.0 (UTF-8, EDITOR and VISUAL, guidestripe=72) <[email protected]>
Co-Authored-By: Ghostty 1.3.1 (Metal renderer) <ghostty@localhost>
Co-Authored-By: zsh 5.9 (arm64-apple-darwin26.0) <zsh@localhost>
Co-Authored-By: Git 2.56.0 (Homebrew) <git@localhost>
Co-Authored-By: Secretive (SSH_AUTH_SOCK) <secretive@localhost>
Co-Authored-By: macOS Text Input (U.S. layout) <[email protected]>
Co-Authored-By: Apple Internal Keyboard (built-in) <[email protected]>
Co-Authored-By: APFS (sealed system volume, 4096-byte blocks) <[email protected]>
Co-Authored-By: MacBook Pro (Mac17,6, MGED4B/A, Apple M5 Max, 18 CPU cores, 36 GB RAM, macOS 27.0.1 build 26A434) <[email protected]>
wolf31o2 retweeted
Dingo is my primary block producer now. 37 Mainnet blocks from various locations. Mobile, K8s, some dudes garage. 15 more this epoch.
By the way, the conformance vectors are being built by the @TurboDaedalus developers. They have been working on node performance on Cardano in the background this whole time.
wolf31o2 retweeted
From Kubernetes adoption to real-world AI workloads, your production experience drives CNCF project decisions and ecosystem research.
Share your feedback in the 2026 Cloud Native Annual Survey.
research.net/r/NVGQT2Y
#CloudNative #AI
