Orsburn (Static Content)

If a person in the Contacts application on iOS cannot be found in one of Apple 's services, the application will try to use Google Hangouts if the person has a Gmail address.  This can be seen in the Call and Video buttons under the contact's name. Version 16.0.0 of the application saw the ability to use the system's phone application to send and receive calls.  This integration is most certainly the source for this ability. This contact only has a phone number and it's not associated with any Apple services.  But it's known to Hangouts, so the video call button is labeled "Hangouts."

Using Google Maps , a double-tap and hold on the screen allows zooming with a single finger by dragging it across the screen. That's tap once, then again quickly, but continue to touch the screen on the second tap.  Without picking up the finger, drag it across the screen. This was encountered by mistake on an iOS device running iOS 10.2.1 and Google Maps 4.28.91.  It may work on Android devices as well, and with older versions of Maps. Also, it's noted that this feature is probably detailed all over the Web.  But here it is again.

Though it's difficult to confirm around the Web, it appears as though the IP address scheme the built-in PHP server uses depends on the host name that's provided.  If a fully-qualified domain name (FQDN) is used, such as server.domain.tld, then the built-in server will be listening for IPv6 based requests.  If the server is started with an IPv4 address identified as the host, then it will naturally listen for IPv4 based requests. The closest to anything official around the Web was a comment in the PHP docs that only seeded this conclusion, at best.  But here it is in any case. Built-in web server http://php.net/manual/en/features.commandline.webserver.php#120449 Ultimately, the following answer from Stack Overflow held the "universal" solution.  Thank you dew010. Running PHP 5.4 built-in web server outside localhost http://stackoverflow.com/a/8377378/2487485 Start your development server like: php -S 0.0.0.0:8989

Apache httpd seems to have an issue that flusters the configuration file parser when a series of backslashes are present in a comment. The following snippet is taken from a vhosts configuration file.  Notice the 5 backslashes at the end of the first line.  # ///// Be sure to manage the corresponding [wrap]         directory block in                  [wrap]         httpd-directories.conf \\\\\ <VirtualHost *:80>     ServerAdmin webmaster@domain.tld     ServerName server.domain.tld     DocumentRoot "/path/to/server.domain.tld"     ErrorLog "/path/to/server.domain.tld-error.log"     CustomLog "/path/to/server.domain.tld-access.log" common </VirtualHost> With these backslashes present, an attempt to start the server will report the following error. </VirtualHost> without matching <VirtualHost> section The problem doesn't appear until the third backslash in a row.  A reasonable assumption is that these backslashes

Anyone who has been using a Mac for long enough to weather an update or two, and is also running a custom configuration of Apache , knows the "joy" of having to put everything back together again after each update. With each system update something about Apache is invariably updated and any custom configuration will no-longer be in place.  Granted, Apple is kind enough to make backups of the existing configuration files that are being overwritten.  But it's still a hassle to traipse through all the settings files to put them all back together. Without going over docs to see what has changed and trying to determine if it's worthwhile replacing all the new conf files with their backups, there's this solution. Write a document that details each conf file and its corresponding settings.  The file will need to be religiously maintained, but when it comes time to put the server back together, it can just be reconstructed from the details in the well maintained do