10,258 karma · joined April 11, 2012
People often draw the wrong conclusions from posts like this. I've worked with people who've taken offense if anyone's video conferencing gear wasn't up to their bar, and it felt like a meta-topic that was never worth the time.
Once you get the fundamentals of Rust down, I recommend writing something multi-threaded. It's not that much harder than writing single threaded Rust and a good test of knowledge; in my case I wrote a tiny web app:
"We are committed to ensuring users can choose whether or not they allow an app to track them. To give developers time to make necessary changes, apps will be required to obtain permission to track users starting early next year. More information, including an update to the App Store Review Guidelines, will follow this fall."
>Facebook actually gave some of the money it made from running those ads through its system to the business that paid for those ads. Which doesn’t make any sense but shut up, Facebook is the good guy, ok? And Apple is wrong to be doing this.
Facebook Audience Network, affected by these changes, includes display ads running in 3rd-party (read: not Facebook) apps. App makers showing ads receive a split of the ad revenue in those cases.
It actually did work for a while. The problem that you run into is that carriers rate limit the number of texts per minute that a particular phone number can send (this is a problem with Twilio too, but in that case it's much easier to spin up a new number).
This argument doesn’t hold up when you consider that Prop 13 applies to much more than single family homes; commercial property is included and wealthy land developers benefit greatly from the measure.