Quite a tricky incident or a tendency ... One day, it will make you look at the problem more creatively. This is an increase in the risks of MITM - when information can be distorted or other manipulations with it are possible. But this is good as a whole. Will help create more sophisticated and safe technologies for viewing information in these networks.

Fortunately, there are quite a few workarounds and opportunities that minimize all the associated risks ...

Be more easy and allow to works not only with nodejs, also more flexible manipulations with dist files in wwwroot.

Please provide more info about migration and examples with using new icons instead glyphicons.

Thanks.

I think this error is related with using "suggest translation" issues

Sorry, I'm is not registered user of that SN, but periodic getting spam emails about invitation. Hope that without any motives.

Thinking beware with gifts ...

This is well-known PHP-trick. Use === to right result.

  php > var_dump(md5('240610708') == md5('QNKCDZO'));
  bool(true)
  php > var_dump(md5('240610708'),   md5('QNKCDZO'));                                                                                                                                                    
  string(32) "0e462097431906509019562988736854"
  string(32) "0e830400451993494058024219903391"
  php > var_dump(md5('240610708') ===   md5('QNKCDZO'));                                                                                                                                                 
  bool(false)
  php > var_dump("0e462097431906509019562988736854" == "0e830400451993494058024219903391");
  bool(true)
  php > var_dump("0e462097431906509019562988736854" === "0e830400451993494058024219903391");
  bool(false)
  php > var_dump(md5('240610708') ===   md5('QNKCDZO'));                                                                                                                                                 
  bool(false)
  php > var_dump(md5('240610708') ==   md5('QNKCDZO'));                                                                                       
  bool(true)
  php > var_dump(md5('240610708') === md5('QNKCDZO'));
  bool(false)

> This is well-known PHP-trick. Use === to right result.

Everybody knows PHP is a trickly-typed language. Read the docs people or PHP will take advantage of your gullible ass.

perhaps ==== operator must reserved

Absolutely! However, we must be careful not to define it in a too predictable way lest we violate the Principle of Most Surprise.

php_real_equivalence_4()

Exactly!

But it must invoke with additional NULL-parameter to achieve real effect and analyse return value for TRUE, FALSE, NULL:

  php_real_equivalence_4($x, $y, null);

Except they had to call it php_real_equivalnce_4() because php_real_equivalence_4() was taken.

Its nice!

For some sites that render code I use stylish add-on in browser:

Here snippet for nice "code fonts courier-hinting" in stylish add-on:

@namespace url(http://www.w3.org/1999/xhtml);

@-moz-document domain("forums.gentoo.org") { .code { font-family: 'DejaVu Sans Mono' }

}

Well, will be great if you explain technologies that allow to create such tools.