DIBSTER :)
546 posts

DIBSTER :)
@DEV_DIBSTER
Developer and Cyber Security Student | @BlueFoxHost, https://t.co/TrWMQs2RPP | Student by day, programmer by night.


Still waiting for Apple to acknowledge our work in the security release notes so we can disclose a bug we discovered and reported in October last year. It has been a tough experience............................. We have a blog and a bunch of videos to share.

Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…

@canezerra @erafps investing in this post now so when you get cancelled in 8 months 7 days and 11 minutes I was here first


Introducing Muse Spark, the first in the Muse family of models developed by Meta Superintelligence Labs. Muse Spark is a natively multimodal reasoning model with support for tool-use, visual chain of thought, and multi-agent orchestration. Muse Spark is available today at meta.ai and the Meta AI app. We’re also making it available in private preview via API to select partners, and we hope to open-source future versions of the model. Learn more: go.meta.me/43ea00

So many companies amazingly "detected" this axios supply chain thing.

JUST IN: 🇮🇷🇦🇪 IRGC claims attack on Oracle data center in Dubai.

Today, we closed our latest funding round with $122 billion in committed capital at an $852B post-money valuation. The fastest way to expand AI’s benefits is to put useful intelligence in people’s hands early and let access compound globally. This funding gives us resources to lead at scale. openai.com/index/accelera…

‼️ Meet the guy almost everyone loves for alerting the axios devs about the supply chain attack. He built a supply chain monitoring system last week, and was alerted within minutes of the axios compromise. The world should be thanking Elastic Security's finest: Joe @dez_

Axios 1.14.1 got hijacked via maintainer account takeover, pulling in malicious plain-crypto-js 4.2.1 (obfuscated dropper, shell cmds, payloads per Socket). npm yanked it—pin to ^1.14.0, audit lockfiles, skip blind upgrades. That red cat reply? Perfect "we're cooked" meme energy for a supply chain scare. Stay frosty, devs. 😼


One of the largest HTTP request libraries has been compromised. Good reminder for CI/CD development, do not enable auto-merge, even for well known packages, for this reason. Review the changes yourselves.










