From reading the case studies it seems most of Foundry in the NHS is geared towards operational data e.g. how to utilise capacity within an hospital efficiently.
Palantir does have very strong capabilities to protect data e.g. security markings, not allowing data to be exported.
Hugo worked for me. And as part of the GitHub pipeline that builds the site and deploys it I can grab some ‘dynamic’ content (from a Notion DB) and render it. Subsequently I added Zapier so that when the Notion DB changes it triggers the pipeline to update my website. The only thing I pay for is the web hosting with dreamhost.
On my personal site (also built with Hugo) I post images of food I have eaten and media I have consumed. I could use Instagram, Bluesky or X but I want the content to be mine and stay mine. And I am doing it because I like to blog things not because I want the interaction on social media.
Seems even with the new scanners there is some issue why they have to limit items to no more than 100ml temporarily. Maybe waiting for a software update… though if there is a loophole seems weird to wait until September 1st…
Dankeschön! The one I am having some success with at the moment is https://www.herrprofessor.com/en/podcast/ as I can listen to the podcasts on the way to work and he explains things in a way my software engineering brain can follow :) Also I didn’t see at first glance https://www.vhs-lernportal.de/ on your site, which is an outstanding resource for free classes that can get you up to B1 level pretty effectively in my experience.
Previous HN comments indicated this could just be demo snowflake accounts, which were all compromised from a single individuals account at snowflake. But the announcements don’t seem consistent with this. Do we think propective customers really shared 100s of millions of real customer records for demo accounts? Or more likely the sales person was granted access to production systems by the prospective clients, so their credential without MFA could be used to access many customers real data? I struggle to see how snowflake can blame the customer here; secure by default is something a customer should reasonably expect for their money.
That’s what I believe Facebook have created here, so you’re right ‘regression’ is a big word - the tests are more likely detecting change e.g. by asserting the existing behaviour of conditionals previously not executed.
From reading the PDF it seems that this ‘merely’ generates tests that will repeatedly pass i.e. that are not flaky. The main purpose is to create a regression test suite by having tests that pin the behaviour of existing code. This isn’t a replacement for developer written tests, which one would hope come with the knowledge of what the functional requirement is.
Almost 20 years ago the company I worked for trialled AgitarOne - its promise was automagically generating test cases for Java code that help explore its behaviour. But also Agitar could create passing tests more or less automatically, which you could then use as a regression suite. Personally I never liked it, as it just led to too much stuff and it was something management didn’t really understand - to them if the test coverage had gone up then the quality must have too. I wonder how much better the LLM approach FB talk about here is compared to that though…
That was brilliantly written and summarised. Seems that Auth0 really did walk the walk in terms of developer experience and support. Thanks and good luck!
None of the reports mention if two stage authentication or any other extra factor authentication that enterprise accounts would be secured with were bypassed too. Am I right to assume that because the attacker had the signing key all of the extra authentication mechanisms that would have been enabled on accounts were bypassed by the attacker (because the attacker could create a token that bypassed all the extra authentication methods)?
And I presume there has been no known dump of e-mails exfiltrated during this attack?