Planet PowerShell Update: Mastodon, Twitter, and Pronoun Support
Over the last few weeks, I have been working on some new features in Planet PowerShell.
Mastodon Support
As more users make the move to Mastodon, I wanted to ensure that Planet PowerShell could continue to support the community.
You can now follow Planet PowerShell on Mastodon, @[email protected]. New posts are automatically tooted using the #PowerShell and #pwsh hashtags.
There is now support for authors to share their Mastodon handles. Authors will need to specify a value for the MastodonHandle property. I have already included some authors’ handles where I was following them. If you are a Planet PowerShell author and have made the transition to Mastodon, please ensure you update your author .cs file.
Including Mastodon support was a simple decision for me, and I am extremely thankful that I have made the decision considering recent announcements (see Twitter Support). As part of the change, I needed to update from Font Awesome v4 to v6, you may notice some icons have slightly changed on the website.
Twitter Support
With the extremely unfortunate decision by Twitter to no longer provide free access to their API, Zapier have notified their users that they anticipate their integration to stop working. Planet PowerShell uses Zapier to post to Twitter, Facebook, and Mastodon.
At this stage, it appears that when Twitter’s API change occurs, the @Planetpshell Twitter will also go silent. This is incredibly disappointing. Over the years, Planet PowerShell has gained 3,358 followers, posted hundreds or blog posts and had tens of thousands of impressions each month.
If an alternative solution for posting becomes available, then we may see Planet PowerShell return to Twitter, until then, I recommend everyone follows the RSS, Mastodon, or Facebook page.
Pronoun Support
It is extremely important to me that Planet PowerShell is an inclusive community. Authors now have the option to specify their pronouns. Simply update the Pronouns property in your author .cs file, and the pronouns will be displayed on the Authors page. This is optional, but I highly encourage all authors to include their pronouns.
Analytics & Cookies
Analytics has been a big challenge with Planet PowerShell. I rely on analytics and usage information as part of my Microsoft MVP reporting; making use of a mix of values provided by Google Analytics and Cloudflare’s built in analytics. This isn’t a perfect solution, particular as there isn’t an effective measure for the RSS feed.
In the past, my side projects like Planet PowerShell have often influenced my work projects. Recently, the flow has reversed. After some discussions around GDPR and Analytics, I decided to make some changes to Planet PowerShell.
Planet PowerShell didn’t have a cookie consent mechanism, something that was a potential issue. CookieBot has a free tier for smaller websites, it works by scanning the website and collecting information on all the cookies in use; you just include a small snippet of code from CookieBot, and it will take care of prompting users to accept or reject various cookies. Due to the small number of pages, Planet PowerShell fits perfect in the free tier, with setup and testing being very quick and easy.
As I was implementing CookieBot, I discovered an issue with Planet PowerShell that goes back to the original fork from Planet Xamarin. When I made the fork, I made sure to update Google Analytics and Google Maps codes and keys, but I missed something. Planet Xamarin also made use of Clicky, a more privacy-friendly website analytics provider. I have update Planet PowerShell to use its own Clicky ID.
Lastly, I have also implemented Heap analytics. Heap analytics platform is one of the easiest to understand, and provides information in a concise manner. It still doesn’t help with the RSS feed, I hope will give me a better understanding of the interactions on the Planet PowerShell website.
My aim is to review the usefulness of the information provided by Google Analytics, Clicky, Heap and Cloudflare, and remove those who aren’t useful long term.
Looking for more authors!
I want to grow the number of authors whose content is aggregated as part of the Planet PowerShell feed. If you are an author, please take the time to add your blog. If you need help, feel free to message me and I will be able to assist.
Finally, I want to thank everyone of the support over the years with Planet PowerShell. Things have come a long way over the last 7 years. I can’t wait to see how things change in the next 7 years!
Planet PowerShell is now HTTPS only
I'm happy to announce that Planet PowerShell is now enforcing HTTPS for all aggregated sites. I gave some extra time for authors to make the change. In the end only 3 authors opted out of moving to HTTPS, so I'm happy with the result.
Planet PowerShell
I'm happy to announce that Planet PowerShell is now enforcing HTTPS for all aggregated sites. I gave some extra time for authors to make the change. In the end only 3 authors opted out of moving to HTTPS, so I'm happy with the result.
I've been making some changes to how CloudFlare cache settings. Planet PowerShell consumes roughly 150GB of bandwidth each month. I'm working to ensure that most of this is served from CloudFlare and not the underlying Azure App Services. Doing this will ensure that the cost of running Planet PowerShell is kept low. Thanks to Troy Hunt for his help with this.
Finally, for those who follow my blog directly, you'll have seen me post about how I manage the DNS for Planet PowerShell. While there isn’t any PowerShell in the post, I encourage you all to read my post “Managing DNS with DNSControl, CloudFlare, DNSimple, GitHub, VSTS, Key Vault and Docker!”.
Planet PowerShell Reminder - Switch Your Blog to HTTPS
Previously I announced that Planet PowerShell will be enforcing HTTPS for all aggregated sites from August 1st (2018-08-01). That date is now a little over 4 weeks away.
Planet PowerShell
Previously I announced that Planet PowerShell will be enforcing HTTPS for all aggregated sites from August 1st (2018-08-01). That date is now a little over 4 weeks away.
If you're finding it difficult to make the move to HTTPS: maybe you don’t want to spend any money, or your provider wants to charge for HTTPS, then maybe CloudFlare is the solution for you. My provider didn’t support HTTPS for a long while, unless I upgraded to a quite expensive tier. Now I run Posh Security and Planet PowerShell behind Cloudflare, all for a great price – free!
Need help with CloudFlare? I recommend reading Troy Hunt’s post: How to get your SSL for free on a Shared Azure website with CloudFlare or watching is Pluralsight course: Getting Started with CloudFlare Security.
Planet PowerShell Announcement - Enforcing HTTPS
Planet PowerShell has grown over the last 18 months since its launch. The community has grown to over 60 talented individuals, with great content posted every day. During this time, I've been very cautious of making many significant changes, but this is about to change.
Planet PowerShell
Planet PowerShell has grown over the last 18 months since its launch. The community has grown to over 60 talented individuals, with great content posted every day. During this time, I've been very cautious of making many significant changes, but this is about to change.
I've been working on some plans to improve Planet PowerShell and will be sharing the roadmap in the next few weeks. I wanted to make the first announcement early as it may require work from the content authors. I want to be sure that everyone is aware of this change.
From the 1st of August 2018, Planet PowerShell will only support aggregating blogs that support HTTPS. Not only that, but we will also validate the certificates presented. Any blogs that don't support HTTPS with a valid certificate will be removed from Planet PowerShell.
Why am I making this change? Simply, I'm making this change to make the world a safer place. There are many great reasons for making the switch:
- Protecting people’s privacy
- The browsers are starting to mark HTTP as insecure
- HTTPS gets better rankings in search engines
- HTTP 2 provides significant performance benefits.
I really can’t find a reason not support HTTPS on your blog. Getting a certificate is extremely easy and there are free options available. You can get a free certificate from Let’s Encrypt, put your blog behind CloudFlare for free or if you're a Microsoft MVP, DigiCert can issue one to you. If you're using GitHub pages, you can find extra guidance at Troubleshooting custom domains.
This gives everyone over 6 ½ weeks to prepare for this change. I've already gone through and identified blogs who are currently using HTTP but support HTTPS, I'll merge update for these shortly.
Currently are around 10 blogs that don’t support HTTPS, or have invalid certificates. I've created an Issue on GitHub to track this change and will include everyone whose blog doesn’t support HTTPS there.