A minor scandal popped up this morning and has been making the rounds of YouTube’s gaming section. YouTube user Mumbo Jumbo, famous for his Minecraft videos, suddenly had hundreds of his videos claimed by Warner Chappell – in other words, Warner Chappell claimed that the videos used music they owned, and by claiming the videos, they earned a percentage of the profit the videos generated.
Google released the introductory episode of a series of SEO mythbusting videos here: https://www.youtube.com/watch?v=lrIwTzUTEGs . I’m looking forward to future episodes – there are so many myths around SEO, it’s good to see Google breaking some of them down.
I really like the new privacy features Google is rolling out, but IMO the best one is number 77 on Google’s list: All Chromebooks launched this year will be Linux-ready right out of the box. The Chromebook is great, but sometimes you need the power of a CLI.
When I travel, I always have Google Maps save a map of the area I’m travelling to. It’s not always possible to have a working cell signal – in flat Illinois where I live, it’s easy to have cell signal all the time. When I travel to more mountainous regions such as Colorado, I often lose signal due to mountains and hills between me and the signal tower.
I was setting up a new application to use SendGrid’s inbound parse email function, so here’s some quick documentation. In the Sendgrid dashboard, go under Settings > Inbound Parse:
Then click on the top blue button: Add host & URL.
Fill in the screen that comes up with the proper domain, and subdomain (the subdomain is optional). The destination URL is where Sendgrid will POST the email to.
At the domain registrar, set up the proper MX record. Look up the appropriate documentation based on the registrar you use – this is how it looks like on GoDaddy:
In your application, set up a handler to answer the SendGrid request: in the screenshot example above, the handler was located at /inboundmailwebhook/. Any inbound mail gets POSTed as regular form data, which most frameworks can handle automatically.
However, it seems that the API insists on having the correct request content type set; i.e. you must set Content-Type: application/json for the IBM Watson servers to notice there is a data body in the POST request. I fixed it by using the json parameter – the requests library for Python automatically inserts the application/json content type when this parameter is used. If you use a different language, you’ll need to set the proper content type in the language’s preferred manner.