←
Harshith413 posts
Harshith avatar

Harshith

@harshith

building Versine (YC F26), ex-swe @stripe, @amazon, @hubspot | @uoft cs

◷ Joined August 2021▧ 3 Photos and videos
Harshith avatar
Harshith@harshithio·Oct 31

well… they acted fast.

Post attachment

Granola now does voice typing. Unlimited words, for free. Granola already writes your meeting notes. Now it can do the typing for you, in any app.

0:21
Harshith avatar
Harshith@harshithio·Oct 23

Your coding agent should check the dependencies it helps you ship. cve dot now offers a free vulnerability feed + MCP access. Match exact versions, read the original advisory, then test the fix. AI summaries need verification. A clean report is not proof of security.

Harshith avatar
Harshith@harshithio·Oct 22

Navigation should preserve a conversation; New chat should reset it. In my Kenzai development contributions, continuity includes drafts, attachments, choices, and pending actions—not just messages. A merge is development progress, not proof of a live release.

Post attachment
Harshith avatar
Harshith@harshithio·Oct 22

Three operator checks: What is actually running? What credentials can it reach? What proves the fix is live? Patch runtime flaws. Contain and rebuild compromised environments. Revoke exposed authority at its issuer. That is the useful response. 10/10

Harshith avatar
Harshith@harshithio·Oct 22

The viral list includes older events: California student-data access from May–September; Medi-Cal access from October 2025; Tor interception earlier in October. Serious consequences do not require an invented 48-hour origin. 9/10

Harshith avatar
Harshith@harshithio·Oct 22

eMudhra: eight intermediate CA keys were reported weak. Chrome blocked affected keys starting Oct 17. Your browser, installer, and container can have different trust paths. Update the relevant bundles; keep certificate verification enabled. 8/10

Harshith avatar
Harshith@harshithio·Oct 22

Zeabur describes a rotated credential being captured by a later backup and then used without authorization. If the attacker can still read the replacement secret, rotation becomes a loop. Establish a trusted destination and contain access. 7/10

Harshith avatar
Harshith@harshithio·Oct 22

Railway recommended that all users rotate stored secrets as a precaution. Its initial report described possible access and some decrypted variables, not proof every customer was hacked. A broad precaution and a confirmed scope are different things. 6/10

Harshith avatar
Harshith@harshithio·Oct 22

LiteLLM 1.107.0 was a different failure: malicious release artifacts. If it ran, treat the environment as compromised. Rebuild from trusted inputs and revoke credentials it could reach. A clean source tag did not establish clean published artifacts. 5/10

Harshith avatar
Harshith@harshithio·Oct 22

AI helped turn difficult PHP flaws into practical exploits. But the PHP Foundation says signs of the OOM problem were identified in 2024; a concrete report arrived in August. Faster discovery still needs funded maintainers and deployed fixes. 4/10

Harshith avatar
Harshith@harshithio·Oct 22

PHP fixes arrived Oct 21: 8.2.35, 8.3.36, 8.4.27, 8.5.12. PHP2Shell lives in the runtime beneath the website. Updating WordPress plugins alone does not update that runtime. Verify the instance actually serving requests. Source: PHP advisory. 3/10

Harshith avatar
Harshith@harshithio·Oct 22

A vulnerability is a weakness. An exploit uses it. A breach crosses a security boundary. A disclosure makes information public. Those events can be months apart. Counting disclosures as fresh attacks distorts the story. 2/10

Harshith avatar
Harshith@harshithio·Oct 22

Black October needs a closer look. Serious PHP flaws, poisoned AI packages, exposed hosting secrets, and weak certificate keys are real. But the viral 27-item list puts several different timelines on one clock. Here is the useful distinction. 1/10

Post attachment
Harshith avatar
Harshith@harshithio·Oct 22

Just open source it bro.

We've decided to sunset Arc on December 22, 2026. That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community. Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward. We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how: · Your passwords, bookmarks, extensions and history come over to Dia seamlessly. · Spaces, Folders, and Tab Groups are in Dia and import over with your data intact. · Dia now surpasses Arc benchmarks in stability, speed, and security. · The browser features you use in Arc are free in Dia, and the AI is optional. Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.