minimaltom
Is it understood what the initial attack vector was? How confident are you that compromise is contained to just this GTM application (and lateral movement/exposure hasnt occurred)?
I dont remember the details, but its not safe to assume that the first 6m have no employee-shares being sold.
Another fun fact: there’s a list of things with tails.txt and scales.txt (see GitHub) and that list is used to generate the random tailnet name :)
(Or at least it used to, it’s been years)
If all your tailscale-ssh ACLs allow you into an account with sudo, or allow you into root, theres no impact (you cant do anything with these vulns you couldnt do a month ago). Thats the nuance I'm trying to get across (admittedly my english is bad).
Having done my own review of the vulns and the fixes as they are landing in github, its pretty clear to me that this only affects situations where you use ACLs to permit ssh into a node (via tailscale ssh, not via opensshd), but dont give a path to sudoers/root.
If a user had no SSH access and/or connectivity to a vulnerable node, none of these vulns give them access.
However, if you have a vulnerable tailscaled and you give ssh access as some non-root account/privs, then yes, these vulns are relevant as theres now known privilege escalations that give access beyond some specific user account.
Not trying to play down the vuln (its important), but its not a free-for-all RCE that some ppl are acting like it is.
Is there anything like a getting-started for working with MACE or orbmol, a 'hello world'? Like maybe simulating Allolactose binding to lac1 ?
Very cool
For example, that french dude that bet on a prediction market what the temperature would be, then broke into the weather station at the airport with a hair dryer. The prediction was still specific and falsifable!
One pony’s trash is another pony’s treasure, so I guess here one persons pedanticism is another persons hobby.
Bad (form) prediction: OAI is gonna be wobbly in a bit Good (form) prediction (could be totally wrong): OAI as we know it today is going to collapse due to running out of money around/at 20xx.
And sure we can be pedantic about detail, but the litmus test is: is the prediction useful if you had a crystal ball and you could know if it was true/false a priori?
This is a spectrum of course: a prediction that OAI will collapse is probably right as _eventually_ all companies come to an end, but under that interpretation, the prediction is useless. It's more signal / useful / falsifable to say OAI is going to collapse around/at <year> due to <thesis>.
Anyway thats my two cents. Its fine to outline forces and trends, but when you make predictions there are useful (better, falsifiable) and useless.
But predictions need to be specific and falsifable. If not, its just rag-chewing over a beer (luv that shit, but i aint predicting on taco tuesday). If they arent falsifable, then its not a prediction.
I think a lot of the HN comments generally can be described as one camp which cares about and enforces the rigor of predictions and trying to direct limited ear-time to voices which tend to get predictions right, vs the other camp that puts more weight towards directional accuracy.
On the overly-literal / narrow thing, I think thats the culture around evaluating predictions overall. Like, all those posts around christmas where people make predictions and evaluate how last year went. The rigor is the norm.
(you either go the path of a burner or a birdie, I don't make the rules)
You can see the implementation here: https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/lib/cry...
Iiuc youre saying: its more cost-efficient to waste water using evaporative cooling so thats what we'll get, not that a closed loop with a heat exchanger is technically infeasible?
Also whats your cutoff for 'acceptable' speed? I would have said 25tok/s.
Most of the benchmark improvements afaict are in agentic and instruction following benchmarks.
Perf improvements seem to all come from training?