Just ran into a bunch of my E2Es failing on innocuous POST requests. Really interested to know how Cloudflare managed to outright break POST requests going through them.
I can unfortunately report that these dots have not helped me in cars or trains; anything more than a few seconds looking at a screen during a journey will ensure I feel awful until I have an opportunity to sit or lie still for quite a while after. To be fair, even facing backwards on a train usually makes me sick rather rapidly.
- Name, Discord username, email + other contact details.
- Limited payment information, including type + last four of cards.
- IP addresses.
- Messages and attachments sent via the customer service system.
- Notably, any government ID provided to Discord.
No, the content felt incredibly outdated and I can’t say I gained any technical knowledge from it. The only skill it really taught me was how to write effective filler content to boost the word count on something.
While I do now have a CS degree, I was hired into a big tech company prior to having that degree based on my work in open-source. I'd been (and still am) an active contributor to some large web projects for a few years, prior to this company reaching out to hire me (projects were unrelated to what they do, FWIW).
I did then get my degree in my spare time while at that job, with my salary covering the costs of tuition, which was very nice. I see my degree as a backup, if for any reason an employer has a strict requirement for it or if I leave this field -- I expect my experience to be what gets me jobs as it stands today.
We just have a single table, with a column indicating if the job has been taken by a worker or not. Probably could get a bit more performance out of it by splitting into two tables, but it works as it is for now.
We process around 1 million events a day using a queue like this in Postgres, and have processed over 400 million events since the system this is used in went live. Only issue we've had was slow queries due to the table size, as we keep an archive of all the events processed, but some scheduled vacuums every so often kept that under control.
That's fair, I would agree that caching at either end would fix this. It just strikes me as odd that GitHub, the middle-man that's just providing CI runners, is the one under fire.