Microsoft Rewards has been around for ages now in the USA, but it’s now made its way over to the UK. The general idea is that you get awarded points by using Microsoft services (predominantly Edge and Bing) which you can then redeem for a range of rewards. You can also get points by purchasing products such as Xbox Live etc.
Currently, I fire up Edge every so often and look at the front page news on Bing to rack up points for the day. You can get a maximum of 90 points per day for using Bing to search (although there have been offers to get more if you also use Edge to perform your searches). Unfortunately, you can’t get points by visiting the same page over and over again, but it still doesn’t take too long to fill the daily quota.
There are also daily challenges and quizes on the main Microsoft Rewards portal which give you one off boosts to your points. Again, they don’t take too long and you can pretty much get through them by button mashing.
Above shows the main rewards portal page where you can see your total and redeem your points for prizes. I’ve managed to accumulate over 15,000 points in a few months with pretty little effort. In some ways it’s similar to Google Opinion Rewards - but instead of giving Google all your personal information you just have to use Bing for a bit.
Some of the prizes you can get include:
Skype credit (£2 = 900 points)
Skype Unlimited (3 months for 8000 points)
Xbox Live Gold (3 months for 15000 points or 12 months for 29000 points)
Xbox gift card (£10 for 12000 points)
As you can see my 15000 points equates to around £13 already which is pretty good. Annoyingly the UK version doesn’t include Amazon gift cards like the US one seems to - which is frustrating as that is pretty much the only thing I would redeem for. They have also removed the Groove music passes which seems strange to me. Maybe they will bring that back at some point. Edit - Microsoft is now apparently killing off Groove Music which explains why it suddenly disappeared from the rewards.
On desktop browsers this is most commonly solved by installing blocking extensions such as uBlock Origin, Adblock Plus, Ghostery etc. Unfortunately on mobile devices however, the app are much more limited and most don’t have support for installing custom extensions or addons. N.B - ok, yes the Firefox mobile app does allow this, and yes I have tried it. Even with just one extension installed however, the app seems too sluggish and laggy - especially when compared to the stock Chrome experience on Android devices (I am running a Nexus 6P so CPU performance shouldn’t be a factor).
I have however found what seems to be a good middle ground that gives you the speed and responsiveness of Chrome whilst also blocking most ads and trackers - the Brave browser.
The browser is based on Chromium so you get the familiar interface and speed, but it will also block a ton of the major trackers and ads by default. The site has some stats on how the load times are improved, which are probably under ideal circumstances, but I can definitely tell that there is a good improvement when surfing the web on my phone. I also get the same feeling of horror when I use any other browser on my phone as compared with using a stock browser on desktop. It’s amazing how fast the web could be without all the excess crap we push through the wire (or air).
A common task in any popular programming language is the ability to send emails to your users, be it as a password reset or as a contact page submission on a blog just like this one.
The below snippet can be used to accomplish this, just change the variables depending on your use case. It assumes that you have a local SMTP server running on the machine you are running the script on (Postfix for example), however you can also login to another service if you want to send via Gmail or Outlook etc.
You can also add additional properties to the MIME message for extra functionality:
Reply-To: Name <address> to specify who the receiver should send their replies to
Change the Content-type to text/html if you want to use HTML within your message body for styling
With all the focus these days on cybersecurity and the push towards a more secure web, it’s more important than ever to ensure as many users as possible are using the HTTPS version of your site instead of the default HTTP version. Google search results will now rank secure versions better than their variations and some browsers are actively warning users if they are not browsing through HTTPS and there is a password input field on the page for example.
As such, having all of your standard HTTP traffic automatically redirect to their HTTPS equivalent can not only help reassure your visitors, but also potentially increase traffic as a whole. There really aren’t any excuses for not using HTTPS now when Let’s Encrypt is available.
Configuring redirects within your web server of choice is quite trivial. In this post I will focus on Apache, however I am sure the config is equally as straightforward if you are an Nginx user.
The first step is of course to make sure that you have a HTTPS version of your site available to the public. There are a thousand guides online about how to to this so I won’t cover it again here, but in short get a certificiate for your domain from Let’s Encrypt via certbot, create a new VirtualHost within Apache listening on port 443 and enable SSLEngine - pointing to your certificate. At this point your should have two versions of your site available - one through HTTP and one through HTTPS. At the end of this all of the HTTP traffic will be redirected the HTTPS virtual host.
Navigate to your main Apache config file which contains your HTTP virtual host definition. This is normally in /etc/apache2/sites-available and might be called something like 000-default.conf if you haven’t renamed it. If the first line of the file is <VirtualHost *:80> you are in the right place.
Open this file with your favourite text editor (you will need root privileges) and add the following, replacing “your-domain-name” with, of course, your domain name:
# Redirect to HTTPS
Redirect permanent / https://your-domain-name.com/
And that’s it. Run the command sudo service apache2 restart to pick up the changes and then test it out. Navigating to any of your pages through HTTP should be automatically redirected to HTTPS resulting in that nice green padlock in your browser.
In Chrome, when you open a link in a new background tab (e.g middle click), any videos on that page (YouTube etc) will not start to play until you directly visit that tab (bringing it to the foreground). This is is something I make use of quite often, however this behaviour is not the default in Firefox. Thankfully though, due to the great configuration options in Firefox, this can easily be fixed:
Type about:config in the search bar to open up all of the configuration options.
Filter the results by entering autoplay into the search box.
Toggle the preference media.block-autoplay-until-in-foreground to true.
From then on, any videos will not begin until you bring that tab into the foreground. When media is being blocked from playing, a play icon will appear in the tab (similar to the mute button for audio). You can click on this to begin playing without bringing the tab to the foreground.