You can read the new policy here: https://go.boarddocs.com/ca/sandi/Board.nsf/files/BU8VCU802554/$file/AR%205121%20Grades-Evaluation%20of%20Student%20Achievement%20-%20Redline.pdf
It doesn't contain anything about race (regardless of the desire to "combat racism").
Most of the policies include:
- Ways for students to redo work that was failing to receive a new grade
- Not having late work count against students' academic grade, but their "citizenship grade"
- Create a way to rehabilitate a student's "citizenship grade" when they're caught cheating
- How parents are notified when a student is receiving a D or F, and what happens then
To be honest, I didn't really see anything that stood out as bad to me.
Hey guys, I just added a coupon code "tdwpedes" for 10% off of the movie. Thanks so much for your support -- we're working on funding the next iteration of Bleeding Blue, and hopefully even building it out into a series.
If you want a direct link to the preview, go to https://www.bleedingbluemovie.com/watch and you can check out the first 10 minutes of the movie.
Thanks for your support, brother!
Edit: I'm sending you an extra watch code that you can pass to a friend, since you purchased before I posted the discount code.
Thanks! Check out the preview and let me know what you think!
Feel free to comment on the preview, and I'll take your comments back to the team!
Just some offhand advice:
-Increase your max tcp ports open -- the default is usually set around 16-30k, but you can up it to 65k -- this combined with TTL sets your max theoretical connections per second
-Set unix file ulimit to like 100k. Each tcp connection (and every process) is considered a "file" in unix, and therefore takes up a file slot
-Lower TTL on connections to something like 15 seconds to 20 seconds
-As you know, heavily cache in multiple areas. Your main page should be served by cache being warmed by a worker process updating all the caches.
-If you're using cloudflare, make sure all static files are set on a CDN and most importantly make sure you create a rule for the cdn subdomain to ALWAYS CACHE ignoring query string.
I ran a top 100 site in the U.S. on about $340/month on AWS. I feel your guys' pain, but it's very doable on a shoestring budget to deal with blitz traffic. There's a hundred other things you can do, but that will solve a lot of traffic woes for you.