Thinky has a potential answer in Tinker — give away the weights and charge for the SFT (and maybe RL down the line) to make the model more capable for specific tasks.
Plot here is quite thick. SF selling power to PG&E to distribute was found illegal/in violation of the Raker Act by the US Supreme Court in 1940 in United States v. City and County of San Francisco.
SF shifted to "wheeling" instead of selling power to PG&E and is tenuously in compliance now, but the current set up was never intended when the federal government ceded water and power rights from Yosemite to SF.
Firetiger | Product Engineer | San Francisco | Full time, on-site
Firetiger is building self-driving software operations. We believe the future of DevOps isn't better dashboards (like Datadog), but autonomous agents that monitor, investigate, and remediate issues based on high-level business goals. We are backed by Sequoia Capital and founded by Rustam and Achille, former leaders from Cloudflare and Segment.
I've used it quite a bit/have vibe coded quite a few "real" things with it in various languages. It's a really nice complement to Cursor-style and claude-code style interaction modalities.
The amount of work required to stand up 330 well connected locations and then operate infrastructure to filter traffic at that scale profitably is more than "tossing" cabinets at problems.
Nah, not really. I know the amount of work standing up even 5% of that requires because I've been there, done that, have the sheet metal scars to prove it. It's a lot of effort. It's just not -hard-. After a while it's a copy-paste problem with it bottle-necking around the human: signing documents, waiting for tickets and whatnot, and it's pretty disingenuous to suggest it's not.
And ooh, ooh, I can flippantly dismiss a comment by calling back to that infamous comment as well! [0] You're actually posting this as a former VP? Geez dude, lighten up, they're not paying you anymore.
Congrats on the launch. A small nit re: your pricing: you're charging for data transfer (bytes transferred over a long period of time), not bandwidth (bits transmitted at a point in time).
Everyone does? If you sell bandwidth instead of data transfer, you have to either massively overcommit (and fear missuse by a couple of clients) or offer far so little bandwidth to be practical
I'm maybe naive in assuming that there is some kind of investigation going on that isn't playing out in public, but I would assume that years of emails going through Microsoft servers might make the identities of the cohorts in this attack difficult to hide?
