syncopate

sqlite's test suite is substantial and not open source, I doubt you could really fork it in a meaningful way

I particularly like how it can predict hair styles. Not only how a barber would do dreads but also how they would color it and how they happened to brush their hair on a given day. Very impressive!

Isn't that called geofencing? It's been around for years. I always felt that the main reason e.g. Facebook wants you to use their app is to be able to supply data for conversions of geofencing ad campaigns, e.g. someone saw an ad for a promotion at some burger place and then actually came to close proximity of their wlan.

I am not Jeremy but I have taken part in the current course and also took some lessons by Siraj (who also does lessons at udacity), Andrew NG, and Karpathy. I think all of them are awesome teachers. Like Siraj's lessons, the fastai course is full of practical examples, whereas Ng/Karpathy's courses are more theoretical. What makes the fast.ai course unique compared to Siraj (who covers a lot of topics very briefly) is that Jeremy delves into depth, taking a long time explaining things, so you have a lot of opportunities to understand what's going on. In the 2018 course there is actually not that much different content compared to the 2017 course, rather Jeremy took the time and tried to make everything easier for everyone to understand and built a better python library. Also another unique point about Jeremy is that he and Rachel want not only to teach people but rather inspire a community of people working together in teams. The fast.ai library will not be just a project for the course, it will be something that a lot of people will use and contribute to to make pytorch better.

If this project discussed here is using react and rust together, could I just use an react example for OAuth2 to get started with? Up to some months ago, there were no examples of using any of the Rust web frameworks with OAuth2.

I wanted to use rust for web development for a while but always struggled with just getting an OAuth2 example running in the past, has this improved recently?

Couldn't one try to at least limit the feedback loop by spreading sulfur over the affected regions by plane? (Simulating a volcanic eruption that reflects sunlight)

How does that work? Should the kernel walk the stack to change all the saved cookie values of the forked copy? I doubt the kernel even knows where the saved cookie values are stored on the stack. Also, that would make fork quite slow, depending on how the deep the stack was when the fork happened.

It increases the complexity of the attack. Usually, stack cookies make ROP harder these days but guessing the cookie only has a complexity of 8*256 (on OpenBSD), but xor'ing the return address with another value does increase the complexity even more. And that might be good news for programs that use fork a lot (like nginx) and hence don't get a refresh for ASLR/stack cookies for every request (like e.g. sshd on OpenBSD does [which does does fork/exec to ensure ASLR/cookies are refreshed]).