I was using Context back when it was still Brand.dev. I found it to be a great product- one of those rare APIs that immediately made a problem I had disappear. Had it in production within an hour of signing up
Agents need clean/current context from the web, and this is the best way I’ve found to give it to them. The internet is clearly moving in this direction: companies are starting to realize their sites need to be legible to agents. Some are already adapting but many haven’t yet. Context feels like an important part of that transition
Yahia is a great builder. His pace of expansion has been impressive, excited to see where he takes Context.
Exactly right. Climbers care a lot about the ethics of an ascent. It’s interesting how much those ethics have changed over the history of the sport.
One of the core ideas is that later climbers should respect or improve upon the style of the first ascensionist. e.g. if a climb was first done using siege tactics, then doing it in a single day is celebrated. But making a climb easier or safer after the fact is much more controversial, because it can feel like changing the nature of the route itself.
Snake Dike is a good example that’s flared up recently in the climbing world. It’s a classic, relatively easy route up Half Dome, and many climbers free solo it. But because it’s a face climb, protection mostly comes from bolts drilled into the rock. The first ascensionist placed very few bolts, which left long runouts and real consequences if you fall.
To many old school climbers, adding bolts to Snake Dike is disrespectful because the risk is part of the route’s character. Their view is basically: don’t bring the mountain down to your level. The new generation of climbers don’t seem to feel that way at all - they think you shouldn’t have to take unnecessary risk to climb a classic route.
I like this - I think you're not too far off of what's popular these days though. I think similar functionality can be achieved by using the "hook" functionality in claude code / codex.
I've been using both on a Rust codebase and have found both work fairly well. Claude code is definitely more capable than Gemini. What difficulties have you had?
The biggest pain point I've had is that both tools will try to guess the API of a crate instead of referencing the documentation. I've tried adding an MCP for this but have had mixed results.
Congrats on the launch! This is really cool - one of the applications of LLM I find most compelling. I've seen so many back office processes that have hundreds of steps, are incredibly error prone, and traditionally couldn't be automated due to API limitations. Solutions like Skyvern are going to supercharge businesses that have had historically low margins due to the number of humans required. (Not as a replacement for a human, but as a force multiplier)
Only if you require text message based two factor. Password managers like 1Password allow you to store your OTP within them and share that + the password internally within your team
This is really great. Congrats on shipping it! You might find https://www.lingq.com helpful as a source of inspiration. I think it's a fairly similar concept.
LingQ's killer feature for me is that as you click on words (or phrases - which I find really helpful btw) to translate them, they are added to your vocabulary list. It will automatically create flashcards for you from this list for SRS. Plus when you're reading a new story, words that are in your vocab list are highlighted yellow and new words are highlighted blue.
There is a large graveyard of startups that have tried to crack open this market. It's a quite hard concept to execute on.
Some companies have made headway in eyewear and shoes (https://www.amazon.com/b?node=23595320011). Clothing is much more difficult - a lot of variety in body shape to accommodate.
This looks cool! Is it possible to feed the output of one cell into the input of the next? That would really unlock the value of a tool like this for me.
I was just looking into this earlier. A lot of major packages have explicitly stated 3.11 readiness, but we're still only at 45% of the top 360 packages.
That's not to say the remaining 55% are broken on 3.11, just tread with caution. For comparison, 71% explicitly support 3.10.
Running over in Rodeo valley (Marin) there was a very noticeable (and unusual) inversion this morning around 7:30 am. It must have been 5-10 degrees colder on the valley floor compared to up higher -- after ~100ft of elevation gain up out of the valley it warmed up very rapidly.
This is awesome. I've been abusing Zapier for years now as a middle layer to integrate with 3rd parties without having to implement their APIs. Zapier's UI is built for non-technical users, anad it makes a lot of advanced use cases very cumbersome to implement.. Super excited to try reimplementing some of our more complicated zaps with this!
Are you all planning to implement as extensive of a collection of integrations as Zapier has?
[ my public key: https://keybase.io/thoma; my proof: https://keybase.io/thoma/sigs/nIlV6UddrFQcH2J5sfe0DVEKBFYWZKFnSTnD1ZbbiUI ]