bgschulman31

My thought exactly. Is this standard practice with using Supabase to simply expose the production database endpoint to the world with only RLS to protect you?

Loved this article! And I appreciated the BCS references - especially the subtler ones like the use of the word 'chicanery'

I think the media is attributing too much to the bats. I was at the Yankees game, and the wind was blowing straight out and hard. Many of the home runs I saw hit would have been fly outs on a day with more normal wind.

This seems like mostly a nothingburger. If you want to communicate privately there are plenty of pieces of software that allow for that.

I canceled my Apple Music subscription a few years ago after leaving the app open for long times would heat up my computer and use 100% of the cpu. It no longer feels like they have the "it just works" feeling they used to in all of their software.

nearly there :)

If you're into cooking a Japanese steel knife

This is a pretty amazing exploit by the attackers. Either they had access to the pagers during shipment and installed malware or had access to RCE on the devices.

They updated their status page, looks like actions and pages are impacted https://www.githubstatus.com/

Same here. 503 when we try to pull an image during our deployment pipeline.

Many of the projects in my OS class in college involved building on top of the xv6 operating system. I remember one of the projects was building a scheduler for xv. It was definitely a great way to learn about different pieces of an operating system!

We recently did this on my team over Christmas this year. We opted not to use Blue/Green for this but instead spun up an encrypted snapshot and began replication from the old database to the new database using MySQL’s tools. Once traffic on our platform was sufficiently low, we cut connections to the database, waited for for replica lag to reach 0 and relaunch the servers with the new databases host info. Our downtime was around a minute.