Yes, but that's just enough obfuscation for them to deny any claim they do charge. But from the free content I was able to see on this WSJ article (not a subscriber) they considered charging businesses in addition to users. Perhaps in the same way they charge for access to user data in France. Where some Facebook users can only see, for example, the first friend photo. The rest of the friend photos then appear behind a paywall. I saw this just last week actually in Indonesia from a tourist trying to show me some photos of his girlfriend back home—only he couldn't because the mobile app his the images of his friends behind a content upgrade.
If something looks innocuous a diligent engineer will review it twice as hard. I used to fail reviews on one-liners during my professional years with people around me asking me what's taking so long—it's just one line of code.
Well there's definitely a conflict between trying to get things done quickly and reviewing things thoroughly in most development jobs.
You have to weigh the risk of going out of business because you didn't deliver value fast enough vs. the risk of having a security incident.
In the Node ecosystem there are SAAS products (https://greenkeeper.io/) that will automatically update your dependencies, run your tests, and merge in the updates (that line change I showed is an example of what it would look like) if the tests pass. That shows you how much thought Node/JS developers put into upgrading their dependencies.
The event-stream update would be done automatically in this instance because the code still worked, although it was compromised.
Here's some advice. Don't feign passion. If you could give to shits about the product wait for a better opportunity. Next. Your coworkers are competition. Treat them as such. Next. Ask for at least 20% more than you'd settle for but only after you receive an offer. Last. Don't become a JAP. You're welcome.
The brutal rebuff reminds me of the argument against using keywords, which I still add to my websites as, when used appropriately, adds value. PR is similar in that, while it may no longer matter to Google, it still matters (and you don't have to pay $7/mo. to figure that out) because there are other search engines crawling the surface Web that aren't Google.
It may be more complex than that. If both of you were tied into the Social Graph it's possible software on your devices simply knew the two of you were in proximity and for how long. This could be done via Bluetooth by an app like WhatsApp or Facebook, which is known to have sensors installed in urban businesses. But who's to say they didn't just turn your device into a beacon itself using the Physical Web?
I'm looking forward to the day I don't have to charge a non-profit doing good in this world $99 a year just to keep their app on the app store. Apple devices should have the equivalent of F-Droid for FLOSS goodies, and that's exactly the conclusion the courts should decide on IMO. This of course will make Apple devices less secure. But then again the current state of affairs is arguably worse given the lack of competition.
