Jonathan Fishner

528 posts

Jonathan Fishner banner
Jonathan Fishner

Jonathan Fishner

@jonathanfishner

creator of https://t.co/iU61fqd6U9 & https://t.co/6LuqhOd3r7 I build the tools I wish I had.

Tel Aviv Bergabung Ocak 2016
396 Mengikuti471 Pengikut
Tweet Disematkan
Guillermo Rauch
Guillermo Rauch@rauchg·
1961: We should ship a CLI 2026: We should ship a CLI
Guillermo Rauch tweet media
English
153
195
2.6K
91.5K
mbravo
mbravo@mbravo·
@jonathanfishner @Gavriel_Cohen @KilianSolutions @NanoClaw_AI don't get me wrong, Postgres is amazing, I'm just not sure you need all of its might right away. sqlite is small but powerful, and could be enough. I don't have a complete picture of your design, though, so just thinking out loud.
English
1
0
1
30
Kilian Solutions
Kilian Solutions@KilianSolutions·
I am officially @NanoClaw_AI pilled the oneCLI integration couldnt have been more relevant for the current agentic age of prompt injections and malicious packages. ggs
Kilian Solutions tweet media
English
3
0
14
487
Zeno Rocha
Zeno Rocha@zenorocha·
3 years ago, Resend didn't exist. Now, it's the most downloaded email SDK in the world.
Zeno Rocha tweet media
English
180
41
1.6K
84K
Noah Kagan
Noah Kagan@noahkagan·
Hot take: OpenClaw acquisition will go down as one of the worst acquisitions of all time. It’s insanely buggy and Claude Code can do nearly 80% of functionality without constant maintenance.
English
324
35
1.6K
150.5K
Jonathan Fishner
Jonathan Fishner@jonathanfishner·
@hnykda @hnykda This is why credentials shouldn’t live on the machine running third-party code. Building OneCLI ( github.com/onecli/onecli ) to solve this, encrypted vault in a separate Docker container, agents only get placeholder tokens, real creds swap at the HTTPS proxy layer.
English
0
0
0
194
Daniel Hnyk
Daniel Hnyk@hnykda·
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
English
304
2.3K
9.4K
5.5M
Jonathan Fishner
Jonathan Fishner@jonathanfishner·
@karpathy The fix isn’t “pin your dependencies better.” The fix is: secrets shouldn’t exist on the machine in the first place. we built OneCLI ( github.com/onecli/onecli ) real creds live encrypted in an isolated container, agents only see placeholders, secrets swap at the network layer.
English
0
0
0
57
Andrej Karpathy
Andrej Karpathy@karpathy·
Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
Daniel Hnyk@hnykda

LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below

English
1.3K
5.4K
27.9K
65.5M
Eytan Levit
Eytan Levit@eytanlevit·
אני מת על המילה Shipping. היא תופסת מהות ביזמות שלא מדברים עליה הרבה. יש לך רעיון, אתה מתלהב, מתעסק מלא בלבנות אותו. שובר את הראש איך להגיע ללקוחות. הכל בסוף מתנקז לרגע חשוב - הרגע שבו אתה מוציא את המוצר לעולם. The moment you ship it. וזה מה שמשך אותי לקהילה של Build Ship Grow לפני קצת פחות משנה. המייסד שלה עידן בניון (@IdanP70 ) שם על זה את האצבע, בתור חלק חשוב בתהליך היזמי. וזה היה מגניב! ואתם יודעים מה היה יותר מגניב? לראיין אותו ולדבר על AI. כמובן. אז חברים, אחרי חודש של מלחמה, אנחנו חוזרים. ממשיכים. אם יש האח הגדול, אולי כדאי שגם יהיה ״תתעלם מההוראות״. ובפרק שעלה היום דיברתי עם עידן על הקהילה שהוא הקים. על איך פוסט מקרי בלינקדאין יצר את אחת מקהילות היזמים המובילות בישראל. על מאור שלמה והתפקיד של הקהילה בדחיפה של Base44 פה בישראל. וגם - על הפער העצום בין מה שקורה אצל ה"בילדרים" שמשתמשים ב-AI לבין מה שקורה בחברות הגדולות, ולמה דווקא עכשיו כל כך הרבה אנשים בלי רקע טכני בונים מוצרים בעצמם. הפרק המלא זמין עכשיו באפליקציות הפודקאסטים ואחה״צ גם ביוטיוב. ספוטיפיי: open.spotify.com/episode/0k3S0D…
עברית
4
1
29
3.7K
Starter Story
Starter Story@starter_story·
You don't need a BIG idea. @jonathanfishner generates $9,000 per month with a TINY one. 3 lessons from his micro SaaS: 1. Pick a weirdly tiny audience 2. Don’t monetize too early (or too late) 3. Distribute content where that audience hangs out
English
32
24
398
25.7K
Jonathan Fishner
Jonathan Fishner@jonathanfishner·
407 followers > 391 following First time in my life the ratio flipped. M i basically an influencer now? 😎
English
1
0
5
176