I always thought that running my own WordPress site might be a bit risky, but much less than I thought. It took until now to be hacked, which is going on three years. In 4.7.1 and earlier was a REST api privilege escalation vulnerability. That means someone can access the site through one of the application interfaces and inject content without having a correct password. And it seems I am in good company.
Luckily I always had backups of everything related to the site, which basically means the database and the files/uploads. Every day I get an dump of the database and a copy of all files back from the hosting service to my local server. And from there a versioned backup to our cloud backup provider.
So recovering from the hack meant updating to 4.7.2 and restoring the database from a version of the backup I knew was good. Doing an update for me wipes out any existing installation which is good if it was possible to contaminate them somehow. Then restoring the database from my backups is a single command once I restore the dump back to the hosting service.
It is well over a year since getting a 4k monitor. In that time we have gone from Windows 8 to 10 and a couple of updates. In the end I settled on 150% scaling. So not quite full retina in Mac terms (200%), but actually this is the correct DPI setting for a 32″ 4K monitor. An A4 page at 100% size in Word, for example, really is basically full size (and I can fit multiple on one screen!).
In general for how I am working there have been a few minor improvements in that time. In Windows 10 the switch to HiDPI and scaling has gone forward, but a bit roughly. Of course all the UWP apps (Metro) work out of the box, but app support has been pretty spotty and takes a long time.
Of the apps I use most things like Sublime Text made the jump quite early as had Firefox and Thunderbird. Spotify did eventually, and then most recently Evernote. Lightroom now looks and works mostly ok, nicely scaled UI elements with full resolution images. The laggards now are a handful of older apps that probably never move, anything from Apple, plus of course Steam. Although that just means they are fuzzy, but full sized. Rarely now does an app claim to support scaling and then not do it, resulting in a really tiny window.
The real rough spot from comments online seems to be support for multiple displays at different scaling, or switching displays. But I don’t suffer either of those since this is a desktop PC with a single monitor. Of course that was one of the reasons for getting this display in the first place.
Probably too brief?
I only noticed this monitor in Verkkokauppa a couple of weeks ago and from all the reviews seemed to be a relatively good monitor at a reasonable price for the size. To my suprise (these things never happen to me) the price fell 100€ the night before I bought it. The bad part was that I actually believed reviews where they said the included DisplayPort cable was crap and to buy a new one. The TL;DR version is that the replacement cable (at 25€) didn’t really work and the one that came with the monitor did. It might be that DisplayPort is a bit twitchy, especially if the cable isn’t seated quite right. But in any case if you have a 4k monitor and the image starts blinking check the connections and try swapping the cable.
All that matters is size
As for the monitor, this thing is huge. And I mean huge and it is also 4k, and it also has an IPS panel. That probably covers the essentials. Over the last few months there are now quite a few 4k monitors in the 24 – 28″ size range, but I was a bit wary of getting one mostly since Windows doesn’t really have the same level of HiDPI/Retina support that the Apple now has, plus many of them are TN panels (worse colour reproduction). I was hoping to get something bigger to even out the scaling vs small UI issues. As it turns out it probably wasn’t as big of a problem as I thought. Not that it matters since a monitor this size with this resolution (3840 x 2160) is pretty much perfect. In the end I am running it with 150% scaling in Windows 8.1 to get something resembling a reasonable size UI. For all intents and purposes I have have a giant Retina quality display without losing the benefit of size. I still fit quite bit more on the desktop than a standard 24 or 27″ screen (1920 x 1080 or 2560 x 1440) resolution. So I am very happy I didn’t settle for something smaller.
Sharp browser text vs. blurry scaled iTunes
The only down side at the moment is the hit and miss support for HiDPI in Windows applications. Things like Firefox and Thunderbird are absolutely perfect, as are most of the Microsoft built in applications. Some however are not (iTunes, Spotify, and Skype for example). Lightroom is sort of HiDPI aware, but it scales some parts a bit strangely (small icons). But the upside is that you get the full resolution for the images, just like on the Mac. An application in Windows has to declare that it understands HiDPI. If it does, then it has to scale its own UI to the DPI setting you select. If it doesn’t then Windows will scale the UI for it. Unfortunately that really does just mean scaling, so instead of getting ultra-crisp text you get fuzzy, blurry text. I’m guessing that the move to Windows 10 and Universal Apps will solve most of this as Metro apps can now run in a window, and are fully HiDPI aware. In the end the traditional desktop apps will just die out. I think Microsoft also has some tweaking to do in the OS itself since when I first installed the monitor Windows decided that I needed 250% DPI scaling and drew huge icons and windows. Obviously the 32″ part never rang any bells. I still haven’t decided if I stick to 150% or go down to 125% still. I think the lower value might be a bit too small though. I prefer the cleaner fonts to tiny ones.
A Raspberry Pi — All the power of a 10 year old desktop in a tiny little box (box not included). And with the added enjoyment of a bare bones Linux desktop. Of course they updated it to be 6x more powerful about a month after I got mine as well.
Of course the real fun starts when you start actually building things with it. And it is already working as a basic photo frame using the TV as a display and serving pictures straight from the Linux server via a smb share.
So many things to do, so little time.
Nice way to spend an afternoon — scripting WordPress updates. As in all things internet it doesn’t pay to hang back from the bleeding edge too much. At least now I have a clean and easy way of doing the updates myself since the hosting provider seems to block the auto ones still. The joys of shared hosting :-(.
Seems my hosting provider doesn’t support WordPress doing automatic updates :-(. Luckily they have quite clear instructions for doing a manual update, but for some reason I almost managed to bork it about 3 times in a row. Either copy doesn’t work quite the same in the hosting service or doing it late at night after a strong cider and some mind bending studying is not a good idea.
In either case it is updated and everything still works.
Just patched the theme I use here. I can’t say it is a particularly pretty theme, but it is all mine. And now that I have this site set up again it is time to start actually getting things in order.
By the way, the theme is at GitHub.
Well, took about 3 aborted attempts, but WordPress is up and running.
Now, we will see how long it lasts…
I had a slightly aborted attempt at migrating this site to a WordPress installation a few months ago.
A theme was done and I tried doing an import of the contents, but somewhere along the way got sidetracked. I guess it is time to start again.
It took a little work, but I have recreated a local testing WordPress setup again and actually documented this time what I should do when setting up the real server. Basically it should be ready to go, if not exactly pretty. But in any case I think I’ll try doing an attempt at migration before installing anything to the real server.
Something else to consider is how to keep regular backups of the WordPress contents and database now that they will actually live on the server and not my local machine. WordPress does have a bit of a reputation for not surviving long on the net…
Another fix for the fix.
Turns out that supporting the new AJAX based next/previous was too much of a pain to get working in old browers. So easiest thing is to have graceful fallback. New browsers get the AJAX with history updating. The old ones get just normal hyperlinks.
Forgot to mention that I have a GitHub account now too.