I have grown an aversion to Google AMP. Playing with the new template I saw that when it was made available here on the WordPress.com platform I’ve enabled it.
Since I manage my blog/website in the ‘old school’ way I could not find anywhere over the Dashboard a setting to disable it. A quick search on the official support forum gave me the answer, simply point your browser to:
https:// wordpress.com/settings/traffic/ $YOURSITE.wordpress.com
…and you’ll be propted with the new WordPress.com interface (still under development) and the option to enable/disable this AMP technology…
Did you notice? On macOS 10.12 ‘Sierra’, when you try to add a new email account with Mail.app using the guided procedure it seems that you can only have an IMAP one…
Of course you can still have a POP3 account but, like it’s in Apple style in those last years, you have to use a gimnik to achieve the result [if you’re not going Apple-way-of-doing-things be prepared to this].
So let’s see how to do this. Open Mail.app and go to its Preferences, here point to the Account section and try adding a new account… make sure to give a wrong password on pourpose when asked:
(My System is set with Italian, so forgive me the language)
After some work behind the scenes, the procedure will say that something is wrong and will ask some more details for this brand new account we’re setting up. As you can see in the following screenshot some more fields to fill will appear, along with a courtain asking the “Account type” we want to set up: IMAP or POP3
That’s it… all we have to do now is to put the correct valule for the POP3 incoming email server and the correct password!
Hope this can be of help to someone…
Lately I had to reconfigure an Ubuntu 14.04 server.
Dealing with Tomcat 7 I’ve encountered those two situations:
Enable larger file uploads via Tomcat manager
I had a ~180 war file to deploy. Ubuntu’s Tomcat setting put a limit at 50MB. This has been solved using the tips in this post by skotfred. Unfortunately I haven’t found a more orthodox way of achieving this other than modify the /usr/share/tomcat7-admin/manager/WEB-INF/web.xml in the values max-file-size and max-request-size.
Enable Tomcat monitoring in Munin
Here I’ve followed the tips over this Serverfault discussions.
Adding a [tomcat_ *] was the key.