Dispatches From The Internets

The power of progressive enhancement

An excellent read on how Andy Bell applied progressive enhancement to a project. I particularly liked this statement (emphasis his):

Progressive enhancement isn’t necessarily more work and it certainly isn’t a non-JavaScript fallback, it’s a change in how we think about our projects. A complete mindset change is required here and it starts by remembering that you don’t build websites for yourself, you build them for others.




Google Go can now read any website out loud

I’m very interested in trying Google Go out as I want to check out the voice synthesis quality. Unfortunately it’s not available in the US. Can any of my Google friends hook me up?

Also worth noting: Google is using AI to find the most compelling content. I’m curious to see how that shakes out too.


Mentorship 2018

If you follow my work, you may recall that I started a formal mentorship program last year. I had the great privilege of working with two incredibly talented peopleAmberley Romo and Manuel Matuzović—for a little over a year and enjoyed the hell out of the experience. I had hoped to kick off a new mentorship session in January, but (as often happens) life got in the way. Now that I’m settled into a new city and a new routine, I’m itching to get things going again. And so I ask: How can I help you develop or further your career on the web?




UK researcher says one line of code caused Ticketmaster breach

Third party code, people… third party code.

He pointed out that while Inbenta had provided Ticketmaster a customised JavaScript one-liner, the ticketing company had placed this chatbot code on its payment processing website without informing Inbenta it had done so. “This means that Inbenta’s webserver was placed in the middle of all Ticketmaster credit card transactions, with the ability to execute JavaScript code in customer browsers,” Beaumont said.

Sigh.