Skip to main content

Posts

Showing posts from 2018

Blogger just introduced HTTPS for custom domains

Yesterday, April 4th, 2018 Google introduced an HTTPS option for Blogger websites that used a custom domain. They made it extremely easy to simply enable this option with one click, and the resulting certificate seems to be from Let’s Encrypt. As a result, many websites hosted with Blogger that use custom domains can now use custom domains, making it very appealing to use Blogger as an alternative to Google Sites for a easy to use, easy to set up website that can sustain large amounts of traffic for free. Although probably not sustainable for ecommerce websites, informational websites as well as websites that don’t require dynamically updating content (and even some that do, for certain use cases) can take advantage of these new security policies. Once you click yes, the banner at the top, originally warning about content policies in the EU (if you never dismissed it) will change, changing into a banner that displays a small warning that you have changed HTTP to HTTPS on your webs...

How long does it take to complete APUSH extra credit?

For the purposes of keeping this write up simple, and the fact that while I'm writing this I've only completed the multiple choice section so far, I will be limiting this small analysis to only the 90 multiple choice questions that were required for the extra credit. I was curious to see how much time I would spend working on it, as this was an extra credit assignment where you had to complete 90 multiple choice questions for APUSH with a paragraph explanation for every question. I spent 8 days working on the extra credit assignment, starting from Christmas day and skipping December 29th, and usually spent between 2 and 4 hours per day working on the assignment. In total, I spent 17 hours and 23 minutes working on the assignment, and this is a first draft, which means I still have to check my work, add any additional details that are needed, as well as the final 12 document based questions that I have not yet completed. Overall, it seems I spent about the same amo...

How to install Alamofire for iOS Swift development

There is a lot of good documentation on how to install Alamofire for iOS Swift development on the internet, and I thought I'd add to the cacophony of articles detailing how to do so, since a lot of terms were not explained to me, as a first time beginner not only to programming in the Swift language, but also the iOS and macOS operating systems. The first thing you'll do is install Cocoapods: it's a manager that allows you to quickly install libraries for Swift. Run sudo gem install cocoapods in a Terminal window and enter your admin password. Cool, now in the root path of your project, run pod init . Some files will automatically be generated for your Xcode project, so navigate to the root directory of the project you selected and open Podfile. You'll find a line that says # Pods for testing . Underneath the line, add pod 'Alamofire' and save and exit. Go back to the Terminal, navigate to the root directory of your project, and run pod insta...