Like most other "privacy" policies, this was written up by lawyers.
Note that they make no clarifications as to what is defined as "customer's" data, only that "Clean Map Reports" are not shared with 3rd parties. i.e. once the map data is stored on their servers, does it still belong to the customer or to Roomba? Technically if it becomes Roomba's data they are not violating their privacy policy. Additionally, my reading of it suggests the latter, because the policy says they will honor requests to delete it. A better policy would be to automatically delete it after 90 days, for example.
A good argument could be made to use that dataset for improving the product, but IMO the risks of de-anonymizing it and exposing that data far outweigh the benefits.
This article is labelled as subscriber-only content, yet I am not a subscriber and can see it fine by following this link. Is it as simple as having the right URL to get to LWN subscriber-only content, or is there some other reason it can be accessed by non-subscribers?
Others have already said this in one way or another, but I think it's worthwhile to add another voice.
I'd just stick with it and keep looking. Be honest with the places you interview with when they ask why you are looking after so short of a time - the job is not what it was represented to me and despite my trying I can't fix it; and as a recent college grad with student loans I can't afford to leave while I'm searching. There's no need to try to hide this on your resume - it's better to be honest and explain it than try to hide something. Employers are people too and they will understand that.
My biggest piece of advice is don't give your notice at your current place until you have a written offer in hand for a new position.
It also uses 100% CPU until the threads are stopped. The author did not make any claims that it was cryptographically secure. It's just a toy that he shared - an interesting way to perhaps generate something useful from something that is normally undesirable.
Maybe I'll include a variable sleeping time determined by current buffer values. That way, thread synchronization would be further disorganized, and CPU power wouldn't be wasted quite as much.
In that case, it's important that mutations take place between every byte outputted tough.
low pressure lowers the boiling point. Water is space will spontaneously boil (i.e. its molecules will separate and drift apart in a vacuum, because there is no background material to hold them together anymore)
