mohith

158 posts

mohith banner
mohith

mohith

@MohithAchu

GSoC’26 @ RUXAILAB | be delusional

Kerala, India Katılım Temmuz 2023
154 Takip Edilen34 Takipçiler
Sabitlenmiş Tweet
mohith
mohith@MohithAchu·
Just got into GSoC😭✨
English
0
0
8
380
Ajay Bhakar
Ajay Bhakar@ajay_2512x·
thanks all ❤️
Ajay Bhakar tweet media
English
12
0
27
533
mohith retweetledi
Mehul Mohan
Mehul Mohan@mehulmpt·
First in my bloodline to see 1 million line change PR getting merged (Bun's master branch is now rust, it's official)
Mehul Mohan tweet media
English
138
263
6.9K
778.2K
Neeha
Neeha@letsbuilddd·
ICEMAN OTW SF TRIP OTW STARTUP SUMMER OTW life is so good
English
2
0
12
383
mohith
mohith@MohithAchu·
@letsbuilddd i open linkedin and X all i see is “i dropped out of…” Its like a trend now
English
1
0
1
70
Neeha
Neeha@letsbuilddd·
im convinced dropping out to build is overrated change my mind
English
12
0
29
1.4K
mohith retweetledi
dale
dale@daleverett·
Today, we’re launching pgGraph: an Apache open-source graph traversal engine for Postgres, written in Rust 🦀 When we started Evokoa, we kept running into the same wall every serious agent team eventually hits: > Agents need to reason across relationships. > But graph DBs are expensive AF, and suck to use. So, we built pgGraph around a simple, single idea: Postgres should stay the source of truth, and the graph engine should live beside it. pgGraph does something different. > It keeps the rows in Postgres, > Compiles the topology around them, > Creates a virtual graph layer using CSR-style adjacency arrays. We're making your existing postgres database graph-traversable for agents without any of the usual BS. > No recursive join hell. > No ETL pipeline. > No second source of truth. > Blazing fast performance pgGraph is already live in production workflows across RevOps, healthcare, and visa services. We’re open-sourcing it because graph traversal should become a default primitive in the agent stack, not an enterprise migration project. Treat Postgres as a graph. Zero data migration. This is what Apache AGE should have been. Docs + Repo below.
dale tweet media
English
58
87
320
26.7K
Neeha
Neeha@letsbuilddd·
had coffee with my prof who is ex Microsoft / a serial entrepreneur and he called me out for wasting time chasing investors and accelerators instead of focusing obsessively on getting customers + bootstrapping. so im spending my summer doing this and documenting it on here.
English
16
1
59
1.6K
mohith
mohith@MohithAchu·
@letsbuilddd well atleast we do have something in common...
English
0
0
1
6
Neeha
Neeha@letsbuilddd·
guys I spent the weekend frenchmaxxing and still came back wanting to build ai agents. there is no hope left for me.
Neeha tweet mediaNeeha tweet mediaNeeha tweet media
English
5
0
26
927
dale
dale@daleverett·
Launching our open source soon, dm me if you’re interested in becoming a founding engineer.
GIF
English
6
2
28
677
mohith retweetledi
Aman_Chain 🏳️
Aman_Chain 🏳️@Amanprabhat9·
First in my bloodline to witness google down
Aman_Chain 🏳️ tweet media
English
30
24
845
39.3K
mohith
mohith@MohithAchu·
"we do not care about your college..we only care about your skills"
mohith tweet media
English
0
0
0
28
dev
dev@devazeez·
365 daysss
dev tweet media
English
4
1
5
226
mohith
mohith@MohithAchu·
wtf has happened at google
mohith tweet media
English
1
0
1
51
Noorie
Noorie@nooriefyi·
i'm hiring (paid) summer interns to join us in SF. unlimited in n out covered by us and any food delivered to the office. new grads welcome too.
English
62
11
479
47.1K
mohith
mohith@MohithAchu·
@IntCyberDigest attacks like these will lead to the end of opensource
English
0
0
0
552
International Cyber Digest
International Cyber Digest@IntCyberDigest·
🚨 How the TanStack npm attack actually happened: 1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo. 2. GitHub automatically ran CI tests on that PR. 3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run. 4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays. 5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
Adnan Khan@adnanthekhan

This attack leveraged GitHub Actions Cache Poisoning. Payload deployed here: github.com/TanStack/route… It looks like it detonated here: #step:26:2" target="_blank" rel="nofollow noopener">github.com/TanStack/route…

English
61
574
4.7K
799.4K
mohith
mohith@MohithAchu·
@letsbuilddd if you need someone who says “we should build that” every 8 minutes
English
1
0
1
78
Neeha
Neeha@letsbuilddd·
Who wants to hang when im in SF
English
11
0
16
964