Can you add a “proof of ownership” mechanism to a system to verify that you are the owner of the system that you want astra to explore vulnerabilities on, to turn off safeguards for defensive use?
eg. publish a public key on DNS, as a response to a specific api request on a port, etc. that you then provide the private key for to verify you own the system
@NWischoff Fox & Kit in San Rafael had these vibes, at least when we went there for a friends kids birthday. Nice coffee shop with a nice contained indoor kids play space. Unsure what it’s like in normal public hours
The “AI escape the box” experiment was comically naive in hindsight. There is no box. Instead, there’ll be embedded access to every critical system in the world
What will engineering productivity look like in a year once a high fraction of codebases are written by Claude Code/Codex and no human has a detailed understanding of these parts anymore?
Excited to share more publicly what @benhamner and I have been working on:
https://t.co/QXvodhsM5e
We are building a knowledge graph for GTM data & have early customers such as @elastic, @figma and @Snowflake
WOW - cold inbound hiring processes are the worst I've ever seen it:
- Huge volume of applications (probably triggered automatically)
- Large volume of fake resumes
- Extensive use of AI assistants in phone screens
@Xfinity@XfinitySupport -
1. Internet has been down whole day in Palo Alto
2. Your outage map for Palo Alto is also not working ("address not found")
3. Your support page doesn't actually provide support
All closed-source frontier labs use tons of open-source all over the stack, starting from python, @PyTorch, @huggingface all the way down to RoPE, GQA, flash-attention, or any tiny improvements released by open-source players.
The whole transformers architecture (the T in gpT) comes from an open research paper and open-source model from 2017: https://t.co/01WrQqeKiU
This is ok but would be much nicer if they would acknowledge the contributions & contribute back more!