This whole HTTPS and Google’s push to encrypt (or weaponize depending on your perspective) is back on people’s lips again. I’m a little late to the party of course, since I have been out of the country so many times in the last three months that blogging has been a distant thought. With all of this talk, I’m left to wonder if the uproar has any merit. You’ll remember, I’ve spoken about this before; actively discussing Dave Winer’s commonly cited reason why sites don’t need to move to SSL.
With the recent support for Ad Blockers in iOS 9, many have been discussing the ethics of blocking advertisements on the mobile platform (and elsewhere). Up until the end of September, ad blockers were the #1 applications on Apple’s app store. The discussion about these has continued after Marco Arment pulled his ad blocking application named Peace. I wanted to offer my perspective on this.
Today I’ve been thinking about the constant conflict between writing blog posts and commenting on blogs (or other types of sites). When is the line crossed from a simple comment to that of a full blown blog? When should we tell people that comment on our sites that they should take it to a blog? I’ve pondered these ideas in the past as I’ve faced Dave Winer‘s particular outlook on this topic.
When I joined the writing team at MovieViral in late 2013, I had aspirations of writing about the other topic I enjoy: movies. My interest was twofold; Get some experience writing for a larger site, and eventually work toward earning money for that work. For a time, the writing was difficult to keep up with, but I persevered. Eventually the site would sell to a new, British, group. In return for supporting them, they would steal from me. Let me explain.
Today, I’ve introduced a theme change to this blog, and I hope you like it. As you can probably tell, the look and feel here is far different than the last design. Over the next little while, I’ll be working out the smaller issues and making an effort to clean up the overall look. But, for now, please take it for a spin and let me know what you think.
As a publisher of multiple sites (and a reader, no less), I’m keenly aware of the struggle faced by the need to reach users, but the cost of doing it. If what we do doesn’t somehow lead back to our site, is this something we could ever embrace? With the recent announcement of Facebook Instant Articles, I’ve been thinking about this more. Is this a great development for publishers, or the start of a new, dangerous path for Facebook?
Does it make sense to move your blog to https? If you’re on the fence about this, you might be very confused. There seems to be a real war of words going on about this right now. Clearly, Google is trying to get publishers to move to the encrypted standard as evidenced by their recent blog post. But some are actually saying this move is about public relations, and not a ranking signal. As you might guess, I’ve been very interested in this topic given the full switch this blog has made. As someone who has blogged for a while and site owner, I can help you make sense of this.
There is a real sense that sites of all shapes and sizes are moving away from commenting systems. Pacific Standard appears to have turned them off altogether. I’m seeing comment systems that have been reduced to identity verifiers that allow users to enter text-only when the web itself allows so much more. This had me thinking, how could we remake the entire idea of commenting on blogs (and the web in general). I have an idea how we can save them.
While working to move this site to using encryption, I have come across another painful reminder of how inadequate the Facebook comments plugin really is. When changing the url (and ultimately the domain) of this site from http://cwl.cc to https://cwl.cc Facebook doesn’t handle the change very well. What I’m left with is losing another swath of great comments and thinking of a fix.
As a blog that runs on WordPress, this site is bound to the glorious options that are presented by this tool; but also many of the limitations. I’ve worked with WordPress in a number of ways, but one that seems to be most tricky is its internal linking. Out of the box, WordPress won’t offer you the ability to show internal elements (such as images) with a relative URL.
And, this seems to run counter to what Google suggests. In a recent post Google sets forth a suggestion to “Use relative URLs for resources that reside on the same secure domain” and “Use protocol relative URLs for all other domains” Given these suggestions, not having relative links in WordPress had me thinking.