chealion.ca

Last Monday I was part of a team presenting a workshop at BCNET’s 2014 conference about Configuring IPv6 for Networks and Systems. The network walkthrough and slides put together by BCNET are available on their wiki while the Systems portion I worked has the slides and workshop examples on Github.

Thanks to everyone who came out.

Alongside changing hosts (moving from TextDrive to my own VPS), adding IPv6 support for my websites and taking far too long to do it I’ve also swapped WordPress for Ghost. Slightly involved installation but much nicer. Most importantly no comment spam.

I’ve now uploaded the slides from the talk I gave to the Calgary FCPUG about outputting to Blu-ray, DVD and the Web. You can grab them from the following link:

https://chealion.ca/other/OutputBDDVDWeb.pdf

I do have an audio recording of the first presentation I’ve given since high school but have yet had a chance to listen and edit it as necessary.

I hope everyone found it useful.

NOTE: You’re going to be using Google’s service to send the email but for all intents and purposes it’s completely transparent to both you and your recipient. It’s also a world lot better than using some random SMTP server (having to find out the local one and always change it) or finding all your email you sent doesn’t even arrive in your recipient’s inbox because it’s been marked as spam because of the server used. I’d recommend looking for an IMAP host instead for the long run.

For brevity I’m leaving out the exact steps to hook this up with your favourite mail client but you can find that out fairly easily as it’s only changing the SMTP server (or check my post about setting up Shaw’s SMTP service) and change mail.shaw.ca to smtp.gmail.com and using your Google login instead of say Shaw’s in the section about changing your SMTP server).

1. Set up a Google Account. If you have one you’re good to go.
2. Log into Gmail
3. Go to Settings (link is in the top right)
4. Go to Accounts and Import
5. Under “Send mail as:” section click “Send mail from another address”
6. Enter your email address you want to use (eg. [email protected]) and press Next
7. Choose to use Gmail’s servers, press Next and choose Send Verification
8. Click on the link in the verification email. This will verify the email address so you can move onto step 9. You may need to check your Junk Mail folder.
9. Back at the “Send mail as” section (you may need to refresh the browser) click the “make default” link for the email address you set up and be sure that below it “Always reply from default address” is selected.
10. Now be sure to change your SMTP settings on your computer/mobile device accordingly. This varies from device to device as to the steps but is the most important step. If not set correctly (eg. not turning off other SMTP servers on an iOS device) will make everything we’ve done for naught.
11. Send an email to yourself to test and reply to it and make sure it gets to the right address. The only times I’ve ever seen an error here is if the SMTP wasn’t set up correctly, step 9 wasn’t followed or the carrier’s SMTP server was enabled again (yes it’s repeated because it accounts for 99% of errors I’ve seen).

Not difficult, but something I can grab when writing an email on how to do it. :-)

Update (February 2012 - Webmail 2.0 is completely up with all it’s Exchange goodness - so check out Shaw’s new instructions )

Please join me in welcoming Shaw’s new feature of actually allowing Shaw email users to send email while travelling without resorting to webmail or trying to find the local ISP’s SMTP server address (or seeing that Telus’ mobile SMTP server is blacklisted AGAIN marking all your email as spam). This is of course ignoring that I don’t recommend anyone actually use their ISP provided email address but instead use something a bit more dedicated like your own domain or an actual email service. It’s still better than an AOL address.

Previously I’d been setting clients up to use a Gmail account as their proxy sending address when they have a Shaw or Telus email address - this makes it easier for Shaw clients. It’s also a lot simpler than the Gmail approach (which I have yet to post here).

Coles Notes

1. Turn on Mobile Access using the new Webmail beta: https://wmbeta.shaw.ca
2. Change your SMTP settings to point to mail.shaw.ca using port 587, STARTTLS, and use your username and password as the authentication

More elaborate instructions

Setting Up Shaw’s End:

1. Sign into https://wmbeta.shaw.ca
2. Click on Preferences (right side of screen - it’s a text link beside Feedback)
3. Click on the ‘tab’ that says ‘Mobile Access’
4. Set it to Enabled (click the radio button beside it)
5. You may need to change your password to meet their new security requirements.
6. Press Save. It will say “Preferences saved” in a small yellow box at the top of the page if it’s successful.

Thunderbird:

2. Go to the Tools menu and choose Account Settings
3. On the left side on that window click on “Outgoing Server (SMTP)”. You may need to scroll as it’s always the last item.
4. There should be an item associated with the Shaw account you just turned on. Whichever account you turned on Mobile Access for and click on it and then click the button that says “Edit…”
5. In the window that appears change the server name to mail.shaw.ca instead of shawmail or shawmail.cg.shawcable.net that it was set to. The port number should be changed from 25 to 587 and the Connection Security to STARTTLS. Authentication: Normal password and then enter your username
6. Press OK
7. If you did not change your password when setting up Shaw then press OK and you’re done. If you did change your password when setting up Mobile Access the next time you check email it will ask you for a new password and you can enter it.

Mail.app:

1. Go to the Preferences and click on the Accounts section
2. Click on your Shaw account on the left side
3. Where it says Outgoing Mail Server (SMTP): click on the drop down menu and choose “Edit SMTP Server List”.
4. Find the Shaw SMTP server in that list and click on it.
5. Change Server Name to mail.shaw.ca
6. Click on the Advanced tab
7. Check off Use Secure Sockets Layer
8. Change the Authentication drop down menu to Password
9. Enter your username and password and then press OK.
10. Close the accounts preferences window and say yes to saving it if necessary.

Shaw’s already provided instructions on setting up an account anew for iOS, Android and Blackberry devices: https://wmbeta.shaw.ca/doc/offnet-device-instructions.html

In April I pushed to GitHub my RewraptoMP4 Script I put together to help assist in creating proper MPEG-4 container files while being able to use the x264 QuickTime component in Compressor. Compressor only allows you to specify the codec being used when exporting to a QuickTime file, however it is possible to use QuickTime Player after the fact to convert a QuickTime Movie to an MPEG-4 without transcoding so long as the codecs are supported in the MPEG-4 container spec.

My primary reason for the extra work is that Google Chrome will not recognize a .mov file as a valid wrapper for video in HTML 5’s <video> tags.

Using Compressor

You need to make your Compressor preset using x264 as a normal QuickTime movie preset (use the table below to help with settings if necessary). You’ll then want to grab the script from GitHub and add it as a script to your preset.

Scripting Compressor isn’t very straight forward, while you can use AppleScript or launch a script using Compressor they fail to mention that the script must be saved as an application and the file is accessed by using on open.

Helpful Table of Limitations

Android information is rather limited. Official Android information is near non-existent.

Thanks to:

• http://www.proactiveinteractive.com/software/compressor/index.php

At work I was trying out to see if I could use the new video tag in HTML 5 to show two different versions of the same video; one optimized for devices that accept only the Baseline profile (eg. iPhone 3G S and older, many other phones) and one optimized for larger devices (eg. iPad, iPhone 4 that support the Main profile). Turns out it works absolutely fabulous by using the codecs section in the type (Thanks to Dive into HTML 5 for the documentation).

<video OTHER_ATTRIBUTES_HERE>
    <source src="PATH_TO_MAIN_PROFILE.mp4" type='video/mp4; codecs="avc1.4D401F, mp4a.40.2"' />
    <source src="PATH_TO_BASELINE_PROFILE.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' />
</video>

The video codec for H.264 is: avc1.YYYYXX where YYYY represents the profile, while XX is the level (multiplied by 10 and turned into HEX):

Profile     Value   
Baseline    42E0
Main        4D40
High        6400
Extended    58A0

Level       Hex Value   
3.0         1E
3.1         1F
4.1         29
5.1         33

Now when I visit with an iPhone 3G it loads the baseline version, while my iPhone 4 and iPad both load the Main Profile version. For my current project I use video for whenever Flash isn’t available and it does leave a gap for Firefox and Opera users who don’t have Flash but according to our web stats they don’t actually exist.

It’s also important to note that Android users are also left in a lurch because any version lower than 2.0 doesn’t support <video>, and those that do can’t handle a <source> element having a type value like above. To top it all off it isn’t able to play or show controls on a video on it’s own. You have to add some JavaScript to your page in order to play to pass the click event and tell it to play.

There’s a particularly nasty implementation detail that doesn’t seem to come up often but is just waiting to bite just about every Mac user in the ass. Mail.app allows users to attach files inline allowing them to be part of the flow of the text or in the case of one of my users be right alongside the paragraph talking about the changes in that paragraph. Or like me, right below the email you’re sending and above the replied emails because of Mail.app’s defaulting to top posting. The issue isn’t being able to put attachments inline, but the fact that by default Mail.app will encode the attachment in the same spot in the email file causing other email clients to see the rest of the email as a set of attachments.

The fix: Make sure “Always Insert Attachments at End of Message” is checked off (preference key is AttachAtEnd - boolean for you MCX minded folk) and you can now attach inline as you would normally want to without having Outlook eat your message.

Thunderbird will display the text correctly, but you’ll lose it and it will only appear as an attachment once that email is forwarded or replied to: (Part 1.1.3 is the text “There’s an attachment”). You’ll also notice the horizontal rule separating between the different HTML portions of the email.

What program completely falls flat on it’s face is Outlook; it just puts all attachments off to the side and you have no idea what’s in the those ATT documents and your client sure as hell isn’t going to read them. So you’ve sent the email, the email was successfully sent, the text will be visible on their webmail systems, on their mobile device (Blackberry or iPhone), and even visible in other mail clients but because it’s technically an attachment Outlook won’t display it inline by default. (For the same reason they won’t show images by default in emails - the cookie tracking and that it’s a great attack vector)

Of note, this only occurs when sending from Mail.app. Outlook can attach items inline and have no issue as it attaches the images at the end of the email.

Correct view:

Today I’ve been heckling D’arcy Norman on Twitter about his plan to try out turning off comments on his blog. The discussion of comments versus no comments is not new but has come to the forefront again because of Gruber’s defence of not allowing comments.¹ D’Arcy has done a good job showcasing several opinions on the matter - so good read his post first.

Why would I want comments on my site? They provide a relatively frictionless (provided no registration is required) way for a reader to respond to something I have written to power Google’s index.² This includes developers responding to my criticisms of their applications, or some method of feedback. The feedback is part of the reason I even write comments anywhere else. It’s still very possible to get a large volume of feedback relevant and helpful to the article/essay/what-have-you without detracting from it. (eg. Coding Horror as an example - not always, not perfect but on a whole a decent example) Comments at one time also help differentiate the “new media” from the “old media”, it promoted the idea that the reader could be involved instead of just a a passive listener.

Why do I think I should remove comments from my site? Spam and focusing on the content. I don’t like being required to run Akismet, or remembering the issues of using Moveable Type 2.x and the necessity of MT-Blacklist. Erasing the spam issue is definitely enticing, especially with some many other avenues of feedback.

Additionally once comments grow beyond a certain quantitative threshold they simply become drive by soapboxes or discussion boxes with little to no control of their direction (unless heavily moderated) and relevance to the whole point of the page’s existence. If you really want people to discuss with each other about something you’ve put forward as a conversation piece? Consider setting up a proper forum³ for the thread control so it doesn’t feel like a discussion has been shoehorned into something that doesn’t quite fit correctly. Personally the whole point of my corner of the web is not to make conversation pieces but to showcase something I actually want to broadcast more widely to the world.

But wait. Why should I even care if they’re on or off? Be practical - for many comments are your first way to get feedback without the roadblocks (registration, emailing, etc.) that are necessary to keep the volume manageable for higher volume sites. Comments don’t scale with the purpose of a blog, website, whatever you want to call your little corner of the world wide web. If you’re small enough they don’t exist, if you’re big enough they overshadow or fail completely miserably at being either a way to leave a note for the author or as a discussion board. So in the big picture - the choice doesn’t matter. What matters is whether they are a positive or a negative impact to you, the moment it’s negative kill it - there’s no saving the signal when the noise gets too loud. If it’s positive, keep it.

Don’t sweat it and focus on writing (or doing your thing).