Remix.run Logo
▲ tptacek a day ago

Duplicate, also editorialized title.

https://news.ycombinator.com/item?id=50469719

▲lowkey_ a day ago | parent | next [-]

I don't mind seeing a duplicate here because this looks like a serious incident that may have been downvoted by Apify employees. I personally didn't see it til now despite checking HN very often.

If you check the thread you linked, Apify isn't being transparent about what data was in the leak. Someone posted it from an email they received and allegedly got downvoted, and then a response from an Apify employee.

▲mvolfik 7 hours ago | parent | next [-]

Hi, sorry that you see it as low transparency. Incident handling takes some time (I know this is an annoying response), and our priority was to send specific information to the affected users. For legal and other reasons, there's naturally a slight embargo on public comms. But a public post-mortem with full details is definitely coming next week, the engineering culture here wouldn't let the management sweep this under the rug. And I expect that the post-mortem will make bigger numbers here on HN, once someone inevitably posts it here, as it's going to be more technical type of content.

Disclaimer: I'm an Apify employee. Not an official position of the company, opinion my own, yada yada

▲tptacek a day ago | parent | prev | next [-]

(The title is fixed now, and I don't so much care about how much exposure the story gets on the front page as I do that we not lose track of the previous thread. I live in a blissful state of not even knowing what an Apify is.).

▲RamblingCTO 13 hours ago | parent | prev [-]

I can tell you bc I was affected: my whole personal data, my payment information (I provide a bunch of scrapers), my biling information and stuff like this. I don't know if they accessed the actor results themselves, but that's not an issue from me.

▲TZubiri a day ago | parent | prev [-]

The link is different, yesterday's post seems to be the status page. This is a post-mortem

▲mvolfik 6 hours ago | parent [-]

nope, this is just status page detail of this specific incident

post-mortem coming next week (hopefully) :)