3 karma · joined August 24, 2016
And? Seems like a valid move (from both moral and corporate perspective) to me.
How would that help? If I have malicious site, I just wouldn't use that feature.
The thing is, it makes perfect sense from their side - they will make people angry, but why would they bother if those people can't go anywhere else?
I'm starting to feel that a competitor providing the same quality of service while allowing all kinds of videos has a chance to succeed. It's OK to have both child videos, porn and Syrian documentation, as long as you can filter - maybe have some sort of a "curiosity" slider that filters child content on one side, YouTube content in the middle and all content to the other side. Also some category toggles,... If you're unhappy with the current selection, just take a few minutes of your time and change your preferences.
For example, I plug one end into my phone and the other one into my sound card - it the phone doesn't support external sound cards, the cable would light up red - otherwise, it would flash green for few seconds, then turn the light off.
Another (maybe more practical solution) would be to implement this in both ports, but some vendors may not comply with the specification. (in the cable, you could only buy those cables that support the negotiation protocol - it would be your choice if you decide to pay a bit more for a better cable)
ad. 1: I find it a pretty good idea to also have a secondary junk mail for signing up to these services - just in case they give my e-mail to someone for spamming or get breached.
Solution to these two problems (an ingenious one I think) is async/await (and there is an awesome polyfill on npm) - if you want, you can enclose your whole code in one async block and effectively make everything synchronous. Or you use it to its full potential and remain synchronous in all parts of the code that need it while retaining the benefits of async (other parts of code can run while the current one is waiting for a result.
The only caveat I've encourtered (a manageable one, at least for me) is that you must keep in mind that the underlying code IS async, so you can only guarantee synchronous behaviour in the single asynced block od code - so sometimes, race conditions could happen between some parts of your program, but with proper scoping (and ideally, using pure functions), you can avoid it all together.