Evernote is discontinuing Evernote Touch, which is probably good because it is not a very good application. The date for the turnover is August 2. I did not know that Microsoft had already announced that August 2 is the date for when Windows 10 Anniversary Edition will be released.

I've been running Nougat for a while on my Nexus 9, and I have not seen any features that make this release of Android desirable

Dave has created a Docker image for nodestorage.js, which hosts the 1999 blogging software I am using to edit this site. Cool!

I've been having two issues with Google Now Reminders on my Huawei Watch . First, the reminders are appearing on the phone an hour early. The second issue is that I cannot mark reminders done or snooze them. I think both of these issues are due to the fact that I've been running the beta of the Google app on my Nexus 6P so I have installed the beta. Unfortunately, it looks like the home screens on the Nexus 6P have been reset, so I will have to reconfigure them, but first I am going to reboot the phone.

Reboot didn't make a difference, and unfortunately the reminders are still messed up. 

Based on a review of the Android Wear user forum, this appears to be a common problem that has been appearing for several months. It's amazing that this problem has persisted so long given that Reminders is a key function of Android Wear and Google Now. 

Nature box.... jalapeno cashews.... omg!

When I bought the Huawei Watch I was unsure about its mesh band because most metal bands pull on the hair on my wrist and is therefore uncomfortable. At first I was surprised at how comfortable the mesh band felt, but I started to have two issues. One is that I don't find it easy to put the band on my wrist, and second is that it isn't easy to tighten the band to the point so that it doesn't move.

I ended up ordering a replacement band that arrived today. Replacing the band was easy thanks to Huawei's design that provides a quick release mechanism. The quick release mechanism makes it easy to swap watch bands without paying the high price for the MODE bands Google sells.

Huawei's bands are even more expensive than the MODE bands, with the lowest price black leather band costing $54.99. The mesh band costs $129, suggesting that the band is about a third of the regular price of the watch! The black leather band that I bought on Amazon.com cost $12.99 and is a nice, soft band. The same company that makes the leather band I bought also sells a mesh band for $18.99. 

If you replace the band be sure to buy the 18mm size, which is actually pretty standard so you are likely to find a band in a local store as well as online.

Today marks the end of the first week that I have owned and worn the Huawei Watch, so it's a good time to provide an update on how I am liking it. In short, I am very happy with this watch.

The main problem I had with the original Moto 360 is its battery life. My benchmark for mobile device battery life is that I shouldn't have to worry about it, which means there needs to be battery life available until I go to bed at night.

Despite all the steps I took with the Moto 360 to preserve battery life, I just couldn't count on it to make it through an entire day. Worse is that to extend battery life as long as possible I had to not use many of the features of the watch. 

Since day one, my Huawei Watch screen has been configured to be always-on. I've used interactive watch faces and tracked my steps using the active Google Fit step tracker, and I have not had to worry about battery life. Not once has the watch gone dead. 

In my opinion, if your smartwatch screen is not always-on, whether in an ambient mode or full power, you are not getting full value from the watch. For example, I had configured the Moto 360 to not display unless I press the crown, which eliminates the glance-ability of the watch. One of the reasons to wear a smartwatch is to quickly see information without having to use a smartphone, tablet, or computer. 

While I am on the topic of the display, let me say that the AMOLED screen on the Huawei Watch is gorgeous. The colors are vibrant and text is very legible. 

The Huawei Watch seems thicker than the original Moto 360, but according to GSM Arena it is in fact 2 mm thinner, and it has a smaller, 300 mAh battery compared to the 320 mAh battery in the Moto 360. I assumed the Huawei Watch had a larger battery, so I am surprised to learn it does not. The AMOLED screen is a reason for the Huawei Watch's battery life because it consumes much less power than other screen display technology. 

Another problem I had with the Moto 360 is that it often lost connection with my Nexus 6P, and that might be a contributor to its poor battery life. I have not had similar problems with the Huawei Watch, it maintains connection with the Nexus 6P throughout the day. The Huawei Watch supports Bluetooth LE 4.1 while the original Moto 360 supports LE 4.0, so that might be a factor with the connectivity difference. 

Of course, a major difference between the two watches is that the Moto 360 is a first generation Android Wear watch, being one of the first ones sold starting in September 2014. The Huawei Watch is a second generation Android Wear watch that became available in September 2015, so Huawei benefited from learning about the problems with the first generation watches. 

The key point here, I think, is that if you tried one of the first generation watches like the Moto 360 and were disappointed, I think it is worth checking out the newest watches as they are clearly better than the first ones. Given the discount price I payed for the Huawei Watch I am very pleased with this purchase and I have a more favorable view of Android Wear. 

For some reason I keep getting my Google Now Reminders on my Huawei Watch one hour ahead of the time I set them on my phone. I have found that I have the beta of the Google App on my phone, which may be the cause of this problem. I vaguely recall a similar issue with the Moto 360. 

I love how the conservatives are claiming there is no big deal about Mrs. Trump's speech. You know that if it were Bill, Hillary, or any other Democrat giving that speech it would be a Mt. Everest size deal. 

In response to Jason Micheli's blog post titled "What's Happening to America". 

Our theology is complicit in this in teaching sin as a “thing” of which we can get rid of, wash away, etc. While there are debates about the theology of Original Sin, I think there ought not be debate about the origin of sin. If the origin of sin is the accepting of ourselves as apart from God, and consequently not seeing God in everyone around us (let alone within ourselves), then we move from us to you and I, or seeing the world as me and others. The word we have for this today is racism, and it should be no surprise that it persists and will continue to persist as long as we continue to see ourselves and everyone around us as apart from each other and apart from God.

I've found another issue with the Huawei Watch . For some reason, Google Now reminders are not vibrating on the watch. From what I can tell, it looks like this has been a problem with some the more recently releases of Android Wear. According to some reports, it may be that Google has actually removed vibrating reminders as a feature. 

There is a Reminders app on the watch, and every time I tape it, I get a message that says "To use Reminders sign in to the Google app on your phone." There is an Open On Phone button, and every time I tap it I get a message on the phone that says "Unfortunately Android Wear has stopped." 

I've installed an app called Feel The Wear that fixes this notification issue and has the added benefit of providing more control over notifications. For example, you can configure text message notifications to be two short buzzes while Google app notifications (Reminders) can be one long buzz. 

Today being Saturday, it is not the normal watch wearing day. I sleep in longer, am much more casual after waking up, so I usually don't take my watch off the charger until noon. Consequently, today's battery life is more about how it does on a weekend than the work week. 

Right now at 8 PM the watch has 47% battery left. Android Wear says there is 8 hours of battery life left, while Wear Battery Stats says it has 4 hours left. I think Wear Battery Status is still learning about the battery life on the watch. 

One of the cool features of the Huawei Watch is that it has an AMOLED screen, which supports a low-powered, black and white, always-on mode. If you have a Moto X, it is the same type of display that allows it to always display the clock and notifications while the screen is locked. I am finding that always-on makes the watch much more functional. 

Today I had my first "glitch" with the Huawei Watch .  Normally the watch automatically switches from full display to always-on, low powered display. I found this works with the built-in Android timer this evening when I was grilling. 

I told Google to set a timer for 10 minutes, which the watch promptly implemented and shortly the screen switched to always-on mode with the timer displaying and updating. I thought this was cool, it enables me to quickly see how much time is left before I flip the chicken. 

However, after the timer alarm went off and swipping to stop the "alarm" the screen stayed fully powered on and would no longer automatically switch to always-on mode, instead I had to manually initiate the change by pressing the crown. 

After finishing cooking and eating dinner I restarted the watch and that resolved the always on display issue. It will be interesting to see whether this is a single occurrence or a bug with the timer app on the watch that prevents it from changing modes. 

The Huawei Watch got through the entire day, which started at 8:30 AM an ended around 1 AM. At the time I put the watch on the charger it had about 8% battery left.

I am pretty sure it would have had more battery power left on a normal day, because yesterday was the first day I was really using it, I spent more time than normal using it, changing watch faces and trying out apps. 

The watch's battery drained more quickly when I was charging my phone because during that time it was not connected to the phone and apparently kept trying to connect. 

I've noticed this same behavior with the Moto 360, and I haven't figured out whether the issue is being caused by connecting my Nexus 6P to its charger, and it rapidly charging, or the location where it is charging which is on the desk in the main floor of my house rather than in the basement where I was working. 

Actually, I suspect the issue may be with the bluetooth drivers on the Nexus 6P , or rather the bluetooth drivers that come with Android. In addition to connectivity issues with the watch, it also sometimes has problems connecting to the bluetooth in my car. 

Today is day 1 for my Android Wear Watch 2.0, featuring the Huawei Watch . The key question to be answered is, does the watch have enough battery life to get through my day. I put the watch on at 9 AM, and at nearly two hours there is 91% battery life.

I am currently wearing the Huawei Watch configured for the screen to be on all the time, which is how you really need it in order to get the most use out of the watch. For example, right now I am using the Outlook watch face, which is connected to Outlook mobile on my phone and that is connected to my work Exchange server. The Outlook face provides me an at-a-glance overview of my meetings throughout the day, along with an indicator of how many unread messages are in my Inbox. 

In dim mode the face shows the time, along with lines around the watch faces where meetings are scheduled, and unread message indicator. In full display I see the current date, the length of time until my next meeting and a snippet of the meeting subject.

The at-a-glance mode of the watch face is most useful when it is always on so I can just look down at it without having to touch the screen or even move my wrist. 

On the Moto 360 this was called ambient mode, and I never used it because it caused drained the batter much too fast. For my testing of the Huawei Watch I figure I should start with the most extreme case to see how it works, and then ratchet down from there.

How good is the Huawei Watch ? Only time will tell! 

Yesterday was Amazon Prime day, which was the second one ever. Billed as bigger than Black Friday, last year I thought Prime Day was a dud, with no sales on products I was interested in. This year, however, was different. I bought a Huawei Watch for nearly $200 off.

I've been wearing the original Moto 360, which is now pretty old in gadget years. Motorola already sells version 2 of the Moto 360, and the original one will not get Android Wear 2.0 when it is released later this year.

Consequently, when I saw the Huawei Watch for $200 and I confirmed it will get Android Wear 2.0 (in fact, it is one of two watches that can run the developer previews), I pulled the trigger.

The watch arrived this afternoon, and I am pleasantly surprised in how it looks and with the comfort of the band. I am a very hairy person, so I find the traditional "linked" metal watch bands uncomfortable because my hair gets caught in the links. This is the first time I've worn a watch with a mesh band, and so far, no pinches.

My own concern with the band is that it is not the easiest to put on, the standard buckle that comes with leather bands is much easier, so I may end up swapping the band.

I'll save my final verdict after using the watch for a few days to see whether the battery life can get through my day. I also hope that it can maintain connectivity with my Nexus 6P better than the Moto 360.

Just tried opening Little Outliner V2 in Linux Mint and confirmed what I suspected that the Javascript Dave provides to switch the a different nodestorage server is correct. The code changes a setting saved in local storage, so you have to execute it in every browser that you are going to use to connect to your server.

I am doing more playing on the computer tonight, this time experimenting with Linux Mint Cinnamon, running in VMWare Workstation. So far, I am liking what I am seeing here.

Of course, after I move this site to a new server, the next morning the new server forgets how to be connected to the Internet and I had to reboot the server. I've been using CloudAtCost for a few years now, but up until now I haven't had so many problems. I am hoping this is not a trend because I've been happy with the service and you can't beat the price.

I've moved my 1999 glossary from Fargo to LO v2. It worked.

Amongst all the fun I had with moving this site to a new server, I attempted to install updates to my Macbook Air, and in the process managed to hose it up pretty good. Fortunately, I didn't have any real data on it, so after trying a few troubleshooting steps, I just erased the drive and re-installed Yosemite, then I upgraded to El Capitan. For all practical purposes I have a fresh new OS on the Air, so it's not all bad.

I've successfully moved this 1999.io site from a server running Debian with 512 mb of RAM and 10 GB of storage to a server running Ubuntu with 1 GB of RAM and 20 GB of storage. I did this after doing a dist-upgrade on the Debian server that might have fixed the memory leak problem it was experiencing.

For the most part I followed the server migration instructions provided on the 1999 server Google group, although my installation has a few tweaks that required a few more steps with the migration. 

Since I retained the URL for the site and pointed it to the new server, I didn't have to do any URL manipulation in my chatLog.json file. After installing the 1999 server software and testing with a simple hello world post, I copied over the chatLog.json and config.json files from the original server.

I use a callback script to publish a copy of this site to its "public" location at writing.frankmcpherson.org, which is hosted on AWS. For the callback script to work, I needed to create an ~/.aws directory and copy the credential file into it. I also needed to copy the callback script to ~/nodestorage/callbacks/publish. 

After copying these files I did a re-publish and the site was re-published both on the new server and on S3. The next issue I had to resolve is that the site on the new server did not have the menubar from the original site. ~/nodestorage/publicFiles/users/frankm did not have a misc directory, which I created and then copied menubar.html, menubar.opml, and template.opml from the original server to the directory. 

I did a quick update to my hello world post and the original menubar appeared along with the remainder of the content.

Next, I discovered that the archive pages were not generated when I republished the site, although they did exist on the S3 copy of the site. While Dave has a script to recreate the archive pages, I decided it would be simpler to copy the previously generated page, which is index.html,  in ~/nodestorage/publicFiles/users/frankm/2016/05 (for May) and ~/nodestorage/publicFiles/users/frankm/2016/06 (for June). 

Final step was to install forever and start up storage.js using it. 

Hello world! If you see this then I have successfully migrated this blog to a new server. The only thing that didn't move over is the menu bar. Let's see whether I need to republish all pages again. And finally, restarted using forever.

Ok, I see that the archive pages don't work. Need to look back in the google group as I think Dave encountered this. Final check, both servers are hosted at CloudAtCost

Just saw a jump in memory utilization from 46.91 at 8:35 to 97.49 at 8:45 PM. 

Do not switch the server user ids that you use when starting storage.js because you may end up with files and directories to which storage.js doesn't have permissions to write. Here is how I made this mistake.

1. Originally started storage.js while logged in with my personal user id

2. Discovered the server was running slow, after attempting to stop storage.js, I rebooted the server

3. After the server came back up, I logged in as root installed some software, looked at some stats, and eventually started storage.js

4. I then accessed my 1999.io editor page, and started writing the posts below. The posts published as expected and almost all was well. 

5. Eventually, I shut down storage.js again, and the next time when I started storage.js I was logged in with my personal ID. After opening the editor I discovered that none of the changes I was making were being rendered. I confirmed the updates were being made to chatLog.json. 

I thought about the problem a bit, looked at the forever log for the session, and after seeing an EACESS error, did a ls -l of the directory and files that were created and noticed they were owned by root rather than my ID. Alas, the ID under which storage.js was running did not have permission to write to the directory. 

How did I fix this? 

I made a backup of chatLog.json, then logged back in as root and deleted the files and directories that were rendered with that ID. Then I logged in as myself, started storage.js, opened the editor and selected Main, Re-publish All Pages. At this point the directory was re-created under my ID and everything rendered as expected. I confirmed via terminal and ls -l that my ID owned all the directories and files. 

My problems are memory related. I've enabled sysstat and run sar -r shows that nearly 98% or memory is being used when I run storage.js with forever. 

I've restarted the Linux server then did forever storage.js and %memused has crept to 62% 

Something interesting... on the Debian server the forever version is v0.11.1 while on my Ubuntu server hosting Fargo Publisher the forever version is v0.15.1. However the Ubuntu server is running node v0.10.25 while Debian is running v0.10.29.

Hmm... just noticed that the callback script isn't working, writing.frankmcpherson.org is not being updated. I think I know, it's because I started storage.js logged in as root rather than as myself.

Ok, at 5 PM I logged in as myself and started storage.js. sar shows that dropped from 65% used while storage.js was running to 51% after I stopped it. Now to see what happens with the callback script running.

Well, so far I can't get new posts to render. Something is up!  I think I fixed!?

I continue to have problems with the server hosting this site. Basically, after a period of time it starts slowing down and I am not sure what is causing it. I've installed sysstat to hopefully capture some information, although I don't know how to use it. 

I've re-initiated the whitelist for this site.

So, I have an extra 2 CPUs, 1 GB of RAM, and 20 GB of storage at CloudAtCost and I went in to the panel to create a new server with those resources and discovered Windows 7 64-bit as an option, which is interesting since that is not a server OS. Just out of curiosity, I've initiated a build with that OS. From what I can tell, there are no billing differences between Windows and Linux, I though previously there was. 

I've built the Windows 7 desktop and RDP'ed to it, now I am running Windows Update. 

I am currently hosting this site on a Debian server running at CloudAtCost. It was the first server I bought at CloudAtCost, and only has 1 CPU,  512 MB of RAM and 10 GB of disk space. My other servers have 2 CPUs, 1 GB of RAM and 20 GB of disk space. The server here seems to be running slow, so I am contemplating a move to another server.

Much consternation on the interwebs about Evernote's new pricing policy that limits the free version to only two devices. Frankly, I think the reaction is a bit ridiculous. If you want the service to continue to be available, you have got to be willing to pay for it. Evernote is a critical part of my workflow and therefore I think it important to pay for the service to do my part to keep the service in existence. Why should you be entitled to a free service? 

Some, like Paul Thurrott, will suggest Evernote users switch to OneNote, which is free. Frankly, I am skeptical that if a lot of users switched to OneNote that it will continue to be free. The changes made with OneDrive come to mind. 

I use OneNote and Evernote. In fact, I have been using OneNote more now that I have a Surface 3. The two apps have different UI approaches, and I personally find OneNote's mobile UIs less appealing than Evernote's. Evernote's tagging and search functions are in my opinion easier and more powerful to use.

Microsoft does provide a free tool to import notes from Evernote to OneNote, and I have considered using it to make a backup copy of my Evernote data. My fear, however, is that the import process will not work for me due to the amount of data I have and how much encryption I use in notes. 

One alternative to Evernote that I have been keeping my eye on is an app called Turtl because it by default encrypts its entire note database. The app is still in development and in beta and the developer has indicated plans to provide a premium service to cover its hosting costs. One benefit, however, is that there is a way to host your own Turtl server, which provides you complete control of your data but also adds responsibility to maintain that server and any backups.

If a service is not important to you, meaning that if it went away or your data was lost that would not be a big deal, then I see no problem using it for free. However, in my opinion, making a decision based on a service being free or not is the wrong approach if the service is important to you. Instead, you should determine the impact of losing your data and the features and functionality you want, and then consider what is a fair price of balancing that risk and value. 

Now that I am using iOS more thanks to my recent purchase of an iPad Mini, I am constantly being reminded of the restrictions if poses.  A perfect example is the difference in using LastPass with Android and iOS. 

With Android, LastPass runs in the background and detects whether an app or web page with login screen has appeared, and when it does, a dialog appears prompting the user to login to LastPass. The app is also capable of detecting which app or web site you are using so that the proper one is displayed as an option for AutoFill or to copy your credentials for pasting on the login screen. When combined with a finger print scanner, the process of using LastPass to enter credentials on Android is fast and easy.

LastPass does not run in the background on iOS and therefore has no way to see whether you are in an app or web page that is prompting you for credentials. If you have to manually task switch or start the LastPass app, login to LastPass, copy the credentials (one at a time for userid and password), then manually paste on the login screen. While the process provides for access to your credentials, it is not nearly as easy or fast to use as with Android.

To be fair to iOS, the same issue occurs with Windows 10 store apps, although the LastPass Chrome extension runs on my Surface 3 and therefore detects and can autofill login credentials for web pages.

One will point out that iOS not allowing for apps to monitor what is displayed on your screen is a security and privacy feature, but one that in my opinion makes the mobile experience harder. LastPass requires I provide credentials to access the information I store in it, why shouldn't I be able to specify to iOS that I want it to monitor and prompt to provide quick access to my credentials?

Several articles published this week about Microsoft no longer manufacturing the Surface 3 with plans to end sales by the end of the year.  Personally this feels a little like when Apple stopped selling the Newton MessagePad, in both instances I found the device very useful.

I appear to have a real minority position in my belief that the Surface Pros are too large. I think the 10.1 inch screen of the Surface 3 is a perfect size for writing notes in digital ink. 

Last month I wrote an article describing how I use OneNote on thee Surface 3, noting how for me the Surface Pen is a key accessory. Most likely the failure for more people to appreciate the Surface Pen is at the root of why few view the Surface 3 favorably.  

The Surface 3 will continue to be functional even if Microsoft decides to not replace it with another Surface as long as it continues to run Windows well. Fortunately, several other companies also make lower price 2-in-1 devices to fill the void if Microsoft decides to stop selling a low price, smaller Surface. In fact, it existence of such alternatives might be the best reason for why Microsoft is opting to stop selling one.

The way one moves app icons in iOS is by far the worst user experience of any computing device I use. Almost every time I try to add an app to a folder I end up chasing the folder around the screen, which is incredibly frustrating. I've never had this type of experience with Android. 

The iOS App Store is acting up for me, right now I can't install an app, it just continues to "clock" so I am going to restart the Mini. Restarting resolve the problem. 

Last Wednesday I decided I needed a newer device to run the latest version of iOS. After a little comparison shopping I decided to buy an iPad Mini 4 from Gazelle. I got a good price on a 64 GB model so I now have a device capable of running the latest version of iOS

The Mini arrived on Friday, so I've been using it for about 24 hours.  It is taking me time to adjust to iOS after using Android almost exclusively for several years.  The Mini is a nice device, although I think it is a little too small in comparison to the Nexus 9.  

I am writing this blog post on the Mini and one thing I am finding annoying is that for some reason the keyboard is not automatically adding a period at the end of sentences, even it is configured to do so in settings. Perhaps it has something to do with the input box in Safari? 

Extensions should be added to Microsoft Edge by the end of July, it is already available for Insiders. I really like using Edge on my Surface 3 but the lack of extensions, particularly LastPass, has been a show stopper.