<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jtyost2)</title>
    <link>https://pinboard.in/u:jtyost2/public/</link>
    <description>recent bookmarks from jtyost2</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/"/>
	<rdf:li rdf:resource="https://laravel-news.com/maileclipse-laravel-mail-editor-package"/>
	<rdf:li rdf:resource="https://laravel-news.com/laravel-vouchers"/>
	<rdf:li rdf:resource="https://laravel-news.com/spatie-laravel-flash-package"/>
	<rdf:li rdf:resource="https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/"/>
	<rdf:li rdf:resource="https://arstechnica.com/gadgets/2019/03/microsofts-new-skype-for-web-client-an-early-taste-of-the-browser-monoculture/"/>
	<rdf:li rdf:resource="https://css-tricks.com/downsides-of-smooth-scrolling/"/>
	<rdf:li rdf:resource="https://github.com/mozdevs/cssremedy"/>
	<rdf:li rdf:resource="http://wpostats.com/"/>
	<rdf:li rdf:resource="https://dzone.com/articles/json-http-and-the-future-of-iot-protocols"/>
	<rdf:li rdf:resource="http://www.jamiembrown.com/blog/one-in-every-600-websites-has-git-exposed/"/>
	<rdf:li rdf:resource="https://code.facebook.com/posts/964122680272229/web-performance-cache-efficiency-exercise/"/>
	<rdf:li rdf:resource="http://alistapart.com/column/instant-web"/>
	<rdf:li rdf:resource="http://www.allenpike.com/2015/user-agents-of-change/"/>
	<rdf:li rdf:resource="http://www.nngroup.com/articles/password-creation/"/>
	<rdf:li rdf:resource="http://www.troyhunt.com/2015/04/mobile-app-privacy-insanity-were-still.html"/>
	<rdf:li rdf:resource="https://callmecavs.github.io/layzr.js/"/>
	<rdf:li rdf:resource="http://sassmeister.com/gist/070d070859f89edaa2e8"/>
	<rdf:li rdf:resource="http://benfrain.com/browser-representatives-on-css-performance/"/>
	<rdf:li rdf:resource="http://www.allenpike.com/2015/javascript-framework-fatigue/"/>
	<rdf:li rdf:resource="https://github.com/phanan/htaccess"/>
	<rdf:li rdf:resource="https://jonsuh.com/blog/social-share-links/"/>
	<rdf:li rdf:resource="http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/"/>
	<rdf:li rdf:resource="https://twitter.com/Paul_Kinlan/status/562890324339863552"/>
	<rdf:li rdf:resource="http://www.quirksmode.org/blog/archives/2015/02/chrome_continue.html"/>
	<rdf:li rdf:resource="http://css-tricks.com/simple-css-row-column-highlighting/"/>
	<rdf:li rdf:resource="http://css-tricks.com/weighing-svg-animation-techniques-benchmarks/"/>
	<rdf:li rdf:resource="https://signalvnoise.com/posts/3847-asking-why"/>
	<rdf:li rdf:resource="http://blog.ircmaxell.com/2014/12/being-responsible-developer.html"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/the-power-of-perceived-performance/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/retake-performance/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/web-beacon-speedup-for-improved-user-experience/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/leverage-browser-storage-for-a-faster-web/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/different-angles-of-web-performance/"/>
	<rdf:li rdf:resource="http://leehblue.com/php-frameworks-affect-profitability/"/>
	<rdf:li rdf:resource="http://www.sitepoint.com/3-ways-implement-embeddable-custom-badges/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/speeding-up-https-with-session-resumption/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/going-beyond-onload/"/>
	<rdf:li rdf:resource="http://www.nngroup.com/articles/m-commerce-terrible-ux/"/>
	<rdf:li rdf:resource="http://24ways.org/2014/cohesive-ux/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/saving-money-by-investing-in-performance-a-financial-model/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/simplify-speed-with-the-halt-number/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/squeezing-the-most-into-the-new-w3c-beacon-api/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2014/the-changing-role-of-the-browser-cache/"/>
	<rdf:li rdf:resource="https://github.com/cowbell/sharedrop"/>
	<rdf:li rdf:resource="http://css-tricks.com/redirect-web-page/"/>
	<rdf:li rdf:resource="https://gist.github.com/sergejmueller/cf6b4f2133bcb3e2f64a"/>
	<rdf:li rdf:resource="http://h30499.www3.hp.com/t5/Fortify-Application-Security/Authenticated-application-security-tests-vs-unauthenticated/ba-p/6602260"/>
	<rdf:li rdf:resource="http://www.quirksmode.org/blog/archives/2014/11/android_gradien.html"/>
	<rdf:li rdf:resource="http://codersblock.com/blog/fun-times-with-css-counters/"/>
	<rdf:li rdf:resource="http://googlewebmastercentral.blogspot.com/2014/11/helping-users-find-mobile-friendly-pages.html"/>
	<rdf:li rdf:resource="http://blog.froont.com/9-basic-principles-of-responsive-web-design/"/>
	<rdf:li rdf:resource="https://code.facebook.com/posts/307478339448736/year-class-a-classification-system-for-android/"/>
	<rdf:li rdf:resource="http://css-tricks.com/scroll-fix-content/"/>
	<rdf:li rdf:resource="http://www.w3.org/blog/news/archives/4167"/>
	<rdf:li rdf:resource="http://ad7six.com/blog/2014/10/25/logrotate-rotate-your-log-files"/>
	<rdf:li rdf:resource="https://github.com/SlexAxton/css-colorguard"/>
	<rdf:li rdf:resource="https://twitter.com/philsturgeon/status/524502715951763456"/>
	<rdf:li rdf:resource="https://github.com/google/material-design-icons"/>
	<rdf:li rdf:resource="http://css-tricks.com/probably-dont-base64-svg/"/>
	<rdf:li rdf:resource="http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing"/>
	<rdf:li rdf:resource="https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c"/>
	<rdf:li rdf:resource="http://realfavicongenerator.net/"/>
	<rdf:li rdf:resource="https://twitter.com/jcolman/status/500070630247903232"/>
	<rdf:li rdf:resource="https://twitter.com/jcolman/status/500070796145197056"/>
	<rdf:li rdf:resource="https://twitter.com/jcolman/status/500071899440111616"/>
	<rdf:li rdf:resource="https://twitter.com/thomasfuchs/status/493790680397803521"/>
	<rdf:li rdf:resource="http://signalvnoise.com/posts/3752-its-ok-not-to-use-tools"/>
	<rdf:li rdf:resource="http://karptonite.com/2014/05/11/rehashing-password-hashes/"/>
	<rdf:li rdf:resource="http://us6.campaign-archive2.com/?u=161d0ed420649f1879e4985f1&amp;id=db03f282c7&amp;e=d909de5621"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/">
    <title>You probably don't need input type=“number”</title>
    <dc:date>2019-03-29T23:58:45+00:00</dc:date>
    <link>http://bradfrost.com/blog/post/you-probably-dont-need-input-typenumber/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Time and time again, it seems like reaching for input type="number" is a good idea, but it almost always isn’t. While input type="number triggers numeric keyboards on touchscreens leading to better mobile UX, that can also be accomplished by configuring the pattern attribute in a certain way (Zach Leatherman has a great deep dive post into all of this). I’ll also say that incrementing/decrementing a number with a mouse’s scroll wheel (especially the crappy Magic Mouse) is a lousy pattern even for proper numeric input (“Dammit! I wanted to buy two pairs of socks, not 39.”)

]]></description>
<dc:subject>webdevelopment usability html software webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:150d7f369740/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://laravel-news.com/maileclipse-laravel-mail-editor-package">
    <title>MailEclipse: Laravel Mail Editor Package</title>
    <dc:date>2019-03-28T21:06:21+00:00</dc:date>
    <link>https://laravel-news.com/maileclipse-laravel-mail-editor-package</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[MailEclipse is a mailable editor package for your Laravel applications to create and manage mailables using a web UI. You can use this package to develop mailables without using the command line, and edit templates associated with mailables using a WYSIWYG editor, among other features.

You can even edit your markdown mailable templates:]]></description>
<dc:subject>email laravel software webdevelopment</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:816dd9ca9279/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:laravel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://laravel-news.com/laravel-vouchers">
    <title>Laravel Vouchers</title>
    <dc:date>2019-03-25T21:31:15+00:00</dc:date>
    <link>https://laravel-news.com/laravel-vouchers</link>
    <dc:creator>jtyost2</dc:creator><dc:subject>laravel software webdevelopment programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:9f107172b556/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:laravel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://laravel-news.com/spatie-laravel-flash-package">
    <title>Spatie Laravel Flash Package</title>
    <dc:date>2019-03-19T19:47:55+00:00</dc:date>
    <link>https://laravel-news.com/spatie-laravel-flash-package</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[This is a lightweight package to send flash messages in Laravel apps. A flash message is a message that is carried over to the next request by storing it in the session. This package only supports one single flash message at a time. ]]></description>
<dc:subject>laravel software webdevelopment</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:393d611fd573/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:laravel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/">
    <title>See No Evil: Hidden Content and Accessibility</title>
    <dc:date>2019-03-16T18:24:33+00:00</dc:date>
    <link>https://cloudfour.com/thinks/see-no-evil-hidden-content-and-accessibility/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[When I first started learning web development I thought hiding content was simple: slap display: none; onto your hidden element and call it a day. Since then I’ve learned about screen readers, ARIA attributes, the HTML5 hidden attribute, and more!

It’s important to ensure our websites are accessible to everyone, regardless of whether or not they use a screen reader, but with this myriad of options, how do we know when to use what?

There are four main scenarios where you may wish to hide content:
1. Hiding content for everyone, regardless of whether they use a screen reader
2. Hiding content for screen readers while showing it to other users
3. Showing additional content for screen readers while hiding it from other users
4. Hiding content at specific screen sizes

Let’s dive deeper into each of those scenarios to learn how to handle them.]]></description>
<dc:subject>design software webdesign webdevelopment accessibility css html</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ee7eca63c2b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://arstechnica.com/gadgets/2019/03/microsofts-new-skype-for-web-client-an-early-taste-of-the-browser-monoculture/">
    <title>Microsoft’s new Skype for Web client: An early taste of the browser monoculture</title>
    <dc:date>2019-03-12T22:51:38+00:00</dc:date>
    <link>https://arstechnica.com/gadgets/2019/03/microsofts-new-skype-for-web-client-an-early-taste-of-the-browser-monoculture/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Rather, it's a being bothered to do the work issue. Microsoft has said that its decision to prioritize Edge and Chrome is based on "customer value." Or, to put it another way, there's not much point in taking the time and effort to support browsers that have a small audience. This creates a negative feedback loop for those browsers, discouraging their use and pushing developers toward a world in which Chrome is the only browser that developers think about and target.

There's perhaps also some irony in that the Skype app is built with a framework designed to foster cross-platform development, between devices, desktop, and the Web. For those who can use the Web app, it looks extremely similar to the desktop apps, which also look very similar to the mobile apps. That's because it's built using ReactXP, Microsoft's layer on top of Facebook's React and React Native frameworks. These let you use Web technology to build applications not just for the Web but also the desktop and smartphone platforms. When targeting the Web, ReactXP supports Firefox, reinforcing once again that this isn't really a technology question.]]></description>
<dc:subject>software webdevelopment webdesign browser googlechrome microsoft firefox internet standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:84396d46f4cb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://css-tricks.com/downsides-of-smooth-scrolling/">
    <title>Downsides of Smooth Scrolling | CSS-Tricks</title>
    <dc:date>2019-03-11T21:50:33+00:00</dc:date>
    <link>https://css-tricks.com/downsides-of-smooth-scrolling/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I can see not being able to adjust timing being a downside, but that wasn't what made me ditch smooth scrolling. The thing that seemed to frustrate a ton of people was on-page search. It's one thing to click a link and get zoomed to some header (that feels sorta good) but it's another when you're trying to quickly pop through matches when you do a Find on the page. People found the scrolling between matches slow and frustrating. I agreed.]]></description>
<dc:subject>css software html javascript webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:90cc763ca070/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/mozdevs/cssremedy">
    <title>CSS Remedy</title>
    <dc:date>2019-03-04T16:54:28+00:00</dc:date>
    <link>https://github.com/mozdevs/cssremedy</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Start your project with a remedy for the technical debt of CSS.A gift to you from Mozilla Developer Outreach. This project is just getting started. It's too…]]></description>
<dc:subject>css software webdevelopment webdesign framework</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0b8df376048e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wpostats.com/">
    <title>WPO Stats</title>
    <dc:date>2015-11-25T03:38:08+00:00</dc:date>
    <link>http://wpostats.com/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Case studies and experiments demonstrating the impact of web performance optimization (WPO) on user experience and business metrics.]]></description>
<dc:subject>webdesign webdevelopment software softwaredesign softwareengineering optimization performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:396aaf15c8f8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwaredesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:optimization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dzone.com/articles/json-http-and-the-future-of-iot-protocols">
    <title>REST Without JSON: The Future of IoT Protocols - DZone IoT</title>
    <dc:date>2015-08-21T03:48:34+00:00</dc:date>
    <link>https://dzone.com/articles/json-http-and-the-future-of-iot-protocols</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The REST model is a strong fit for IoT. However, the traditional REST implementation of JSON over HTTP is ill-fitting at best. JSON’s string-oriented payloads are no match for binary encodings when it comes to data transmission in terms of speed and ease of parsing. Encodings like CBOR and Protobuf are compelling alternatives to JSON.

In contrast, the HTTP/2 specification indicates that HTTP may remain the application protocol of choice. And its emerging sister protocol, QUIC, will compliment and strengthen the position of web protocols in the IoT space.]]></description>
<dc:subject>json rest http software webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f70d18088d75/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:rest"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jamiembrown.com/blog/one-in-every-600-websites-has-git-exposed/">
    <title>One in every 600 websites has .git exposed | Jamie's OC</title>
    <dc:date>2015-07-29T04:23:42+00:00</dc:date>
    <link>http://www.jamiembrown.com/blog/one-in-every-600-websites-has-git-exposed/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Some of these .git repositories are harmless, but from a random sample many contain dangerous information that provides a direct vector to attack the site. Hundreds listed database passwords, or included API keys for services such as Amazon AWS or Google Cloud. Others included FTP details to their own web server. Many contained database backups in .SQL files, or the contents of hidden folders that are meant to be restricted.

One prominent human rights group exposed every single person who had signed up to a gay rights campaign (including their home address and email addresses) in a CSV file in their Git repository, publicly downloadable from their website. One company that sold digital reports provided its entire database of reports free of charge to anyone who wanted to download their .git folder.

So developers, please, please check that your .git folder is not visible on your website at http://www.yourdomain.com/.git/. If it is, lock it down immediately. Ideally delete the folder and find a better way to deploy your code, or at least make sure access is forbidden using an .htaccess. Then assume that someone has downloaded everything already and work out what they could have seen. What passwords, salts, hashes or API keys do you need to change? What data could they have accessed? What could they have done to alter or impair your service?

And then please spread the word among other developers too – because right now this must be one of the biggest holes in the internet.]]></description>
<dc:subject>webdesign webdevelopment software security technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:dcdc55627152/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.facebook.com/posts/964122680272229/web-performance-cache-efficiency-exercise/">
    <title>Web performance: Cache efficiency exercise</title>
    <dc:date>2015-06-29T00:07:53+00:00</dc:date>
    <link>https://code.facebook.com/posts/964122680272229/web-performance-cache-efficiency-exercise/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Overall our cache hit rate looks like it has improved since 2007. If we ignore Firefox v32 and newer (where we cannot log some cache hits), then the cache hit rate goes to 84.1%, up from about 80% in 2007. On the other hand, caches don't stay populated for very long. Based on our study, there is a 42% chance that any request will have a cache that is, at most, 47 hours old on the desktop. This is a new dimension, and it might have more impact for some sites than others.

It's easy to understand why caches don't last long in general. Look at how Internet delivery and webpage size have changed between 2007 and today. In 2007, we had 2.5Mbps cable modems (at home), and the Yahoo homepage weighed in at 168.1KB. Today, I get 8Mbps downstream via LTE on my cellphone, and the Yahoo homepage is 768KB. The average webpage is over 1MB today, creating more pressure on our browsers to perform better.

Thus utilizing the browser cache continues to be important and has the potential to give us more impact than it did eight years ago. The best practices tell us to use external styles and scripts, include Cache-Control and ETag headers, compress data on the wire, use URLs to expire cached resources, and separate frequently updated resources from long-lived ones. All of these techniques work together on any website, not just one at Facebook scale. We were worried that our release process might be negatively impacting our cache performance, but it turns out to be not the case. In fact, we are using this data to focus on doing a better job of utilizing the cache for everyone visiting www.facebook.com. Happy cache-hacking.]]></description>
<dc:subject>software technology browser research cache facebook webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:571dd6b9a895/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:cache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistapart.com/column/instant-web">
    <title>Instant Web · An A List Apart Column</title>
    <dc:date>2015-05-24T05:07:18+00:00</dc:date>
    <link>http://alistapart.com/column/instant-web</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[What’s exciting about this user- and performance-focused mindset is that it will still be valid and useful even if we see some much-needed advances in browser-based capabilities. I hold out hope that components like HTTP/2 and service workers will allow us to build smarter, more performant sites. But we have the means to build sites faster right this minute. If nothing else, Facebook just turned that into a higher priority for the entire web community. And that’s a good thing.]]></description>
<dc:subject>programming webdesign webdevelopment software facebook internet technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:151fc40a1f91/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.allenpike.com/2015/user-agents-of-change/">
    <title>User agents of change - Allen Pike</title>
    <dc:date>2015-05-03T20:44:42+00:00</dc:date>
    <link>http://www.allenpike.com/2015/user-agents-of-change/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[And so the user-agent string has become a never-ending katamari that appends the string of every browser that was ever popular. After 20 years of rolling in more and more tokens, every HTTP request Edge makes has to include more than 150 bytes of text to simply convey that it is in fact Edge - a fact that only contains perhaps two bytes of entropy. As things stand, the string will continue to roll on and on indefinitely until it is large enough to pick up buildings and oil tankers.

Thankfully, an end to this madness is in sight. Analysis of major browser releases over the last 20 years shows that user-agents have grown in length roughly linearly at a rate of about 5 characters a year. This pace will eventually become unsustainable, since the popular Apache web server limits header size to only 8190 bytes. With this limit in place, user-agents can only grow at their current rate for another 1608 years. The clock is ticking for browser vendors and web developers alike to work together to forge a new solution to this problem - before it’s too late.]]></description>
<dc:subject>browser webdevelopment webstandards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7d382ffe0dde/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webstandards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nngroup.com/articles/password-creation/">
    <title>Password Creation: 3 Ways To Make It Easier</title>
    <dc:date>2015-04-28T02:03:00+00:00</dc:date>
    <link>http://www.nngroup.com/articles/password-creation/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The three recommendations presented here ease the process of creating a password, and they all fall on the side of user experience and interface design. They can be addressed without major technical investment and overhaul. But additionally, I urge usability advocates within organizations to make a case to simplify password requirements. Usability professionals typically receive strict security requirements from a separate department. It’s generally accepted that nothing can be done about them. But that’s not the case. (Note that this conflict between usability and security has also been around for decades.)]]></description>
<dc:subject>userexperience userinterface usability password webdesign software webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7978425cea89/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userexperience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userinterface"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:password"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.troyhunt.com/2015/04/mobile-app-privacy-insanity-were-still.html">
    <title>Troy Hunt: Mobile app privacy insanity – we’re still failing massively at this</title>
    <dc:date>2015-04-26T05:06:23+00:00</dc:date>
    <link>http://www.troyhunt.com/2015/04/mobile-app-privacy-insanity-were-still.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I feel a bit matronly saying this, but I’m disappointed. No really, I was sure things were looking up there for a bit and it seemed harder to find egregious examples of security shortcomings in a random selection of apps. Whilst this is but a very small selection here, the problems were found very quickly and are extremely worrying. Both Aussie Farmers and Nando’s have serious security risks in how they handle data and as for PayPal, you may not call it a security risk but it’s sure as hell an invasion of privacy. The network I’m connected to when using their service and where I physically am in the world is my business and I don’t particularly want to share it with them. Perhaps I should just stick to the browser that doesn’t leak this class of data yet one would assume is still sufficiently secure.

What has me a little worried with all this is that we’re heading in a direction where we have more data to share via more channels which are all racing to be first to market with something. This week the Apple Watch will hit and it will arguably be the point at which wearables seriously take off. Now we’re talking about very personal data – health data – and there will be all new ways of sharing it. But it’s to improve the experience to you, the consumer, right?]]></description>
<dc:subject>software programming webdevelopment security privacy datamining</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:9cc7f64191be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:datamining"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://callmecavs.github.io/layzr.js/">
    <title>Layzr.js</title>
    <dc:date>2015-04-19T23:42:51+00:00</dc:date>
    <link>https://callmecavs.github.io/layzr.js/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A small, fast, modern, and dependency-free library for lazy loading images.]]></description>
<dc:subject>javascript software webdesign webdevelopment lazyload image</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8116943dd5c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:lazyload"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:image"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sassmeister.com/gist/070d070859f89edaa2e8">
    <title>SassMeister | The Sass Playground!</title>
    <dc:date>2015-04-08T23:20:12+00:00</dc:date>
    <link>http://sassmeister.com/gist/070d070859f89edaa2e8</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[]]></description>
<dc:subject>css tooltips webdesign webdevelopment software programming</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:4ca3e2f1c285/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:tooltips"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://benfrain.com/browser-representatives-on-css-performance/">
    <title>Browser representatives on CSS performance - Author and responsive web developer Ben Frain</title>
    <dc:date>2015-04-04T17:19:23+00:00</dc:date>
    <link>http://benfrain.com/browser-representatives-on-css-performance/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[If you’ve developed on the web for any non-trivial period of time you will know that the answer to most web related questions is ‘it depends’. I hate that there are no simple, cast-iron rules in relation to CSS performance that can be banked upon in every situation. I’d genuinely love to write those rules out here in a nice little paragraph and believe they would be universally true. But I can’t because there simply aren’t any universal truths in relation to performance. There can’t ever be any because there are simply too many variables. Engines update, layout methods become optimised,every DOM tree is different, all CSS files are different. On and on ad infinitum. You get the picture. I’m afraid the best I can offer is to not sweat things like CSS selectors or layout methods in advance. It’s unlikely they will be your problem (but, you know, they just might). Instead, concentrate on making ‘the thing’. Then, when ‘the thing’ is made, test ‘the thing’. If it’s slow or broke, find the problem and fix ‘the thing’.]]></description>
<dc:subject>css performance webdesign webdevelopment javascript browser</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:68b802b1dde4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.allenpike.com/2015/javascript-framework-fatigue/">
    <title>A JS framework on every table - Allen Pike</title>
    <dc:date>2015-03-02T00:29:11+00:00</dc:date>
    <link>http://www.allenpike.com/2015/javascript-framework-fatigue/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Perhaps we should just resign ourselves to it always being this way. While I’ve long argued that creating your own JavaScript framework out of a microframework and a DOM library is madness, maybe it’s the least bad option. Maybe the quirks of the language and the constraints of the browser make a sophisticated but bulletproof framework like Cocoa or Rails just kind of impossible.

Maybe I should just call off the hunt. Though, people do seem pretty excited about React.js. They have some smart developers and exciting ideas, at least from what I’ve seen.

You know, maybe I should build something new with it and see what it’s like. Maybe… maybe it’s the one.]]></description>
<dc:subject>javascript software framework development webdevelopment webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:12f68041d390/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/phanan/htaccess">
    <title>phanan/htaccess</title>
    <dc:date>2015-02-11T05:12:49+00:00</dc:date>
    <link>https://github.com/phanan/htaccess</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A collection of useful .htaccess snippets, all in one place. I decided to create this repo after getting so tired (and bored) with Googling everytime there's a need of forcing www for my new website.]]></description>
<dc:subject>htaccess apache software webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b926abbe7bbe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:htaccess"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://jonsuh.com/blog/social-share-links/">
    <title>Responsible Social Share Links — Jonathan Suh</title>
    <dc:date>2015-02-10T05:17:16+00:00</dc:date>
    <link>https://jonsuh.com/blog/social-share-links/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Social share scripts are convenient and easy to copy & paste but rely on JavaScript and add additional overhead to your site, which means more HTTP requests and slower load times. Instead, use share links that don’t require you to load scripts for each social site.]]></description>
<dc:subject>javascript webdesign webdevelopment software socialmedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:15972912e387/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:socialmedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/">
    <title>You’re Missing the Point of Server-Side Rendered JavaScript Apps : Tom Dale</title>
    <dc:date>2015-02-08T02:24:04+00:00</dc:date>
    <link>http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[These are early days, and making this work relies heavily on having a single, conventional architecture for your web applications, which Ember offers.

Ultimately, this isn’t about you replacing your API server with Ember. I don’t think I would ever want that.

Instead, client-side rendering and server-side rendering have always had performance tradeoffs. Ember’s FastBoot is about trying to bend the curve of those tradeoffs, giving you the best of both worlds.]]></description>
<dc:subject>ember javascript software webdevelopment emberjs hardware programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8bad2ff3254d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ember"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:emberjs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/Paul_Kinlan/status/562890324339863552">
    <title>Paul Kinlan on Twitter: &quot;Still amazed by the cadence of browser updates: 2006: every 3 years 2014: every 6 weeks https://t.co/aXu55tXkgz http://t.co/1uB6QK4KXq&quot;</title>
    <dc:date>2015-02-05T03:03:56+00:00</dc:date>
    <link>https://twitter.com/Paul_Kinlan/status/562890324339863552</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Still amazed by the cadence of browser updates:
2006: every 3 years 
2014: every 6 weeks]]></description>
<dc:subject>browser webdevelopment webdesign software programming internet technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:67ff6135b39f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.quirksmode.org/blog/archives/2015/02/chrome_continue.html">
    <title>Chrome continues to fall apart at brisk pace - QuirksBlog</title>
    <dc:date>2015-02-03T23:24:50+00:00</dc:date>
    <link>http://www.quirksmode.org/blog/archives/2015/02/chrome_continue.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The really annoying part is that web developers, as well as Google itself, seem to be unaware of this situation. You’ll only find this information here, because nobody else cares. (Or, at least, nobody else who blogs about such issues.)

Although there is no reason to panic (Chromium has a much more unified codebase than Android WebKit), you will occasionally run into problems if you test your site only on Google Chrome and ignore the ten others.

The solution is simple: test on devices that have non-Google Chromia as their default browser. Modern high-end Samsungs, HTCs, Xiaomis, and LGs will do the trick today, and the other brands will follow. (Testing on Chrome on iOS, on the other hand, is useless since it’s not a Chromium. Do it if it makes you feel good, but don’t expect it to say anything useful about other Chromia.)

Also, study your clients’ logfiles to figure out which Chromium versions are visiting his site in which numbers — and share those numbers if you can. Then make sure to test on those Chromia.

Not that anyone will actually listen. Nobody wants to know that the suppsedly-tidy Chrome on Android situation is deteriorating fast, and was never tidy to begin with. That’s why I decided that in 2015 I’ll talk about these issues at conferences — starting with our own Mobilism.

Finally, I hope that Google Chrome’s great dev rel team picks up this concern and starts helping me — for instance by providing an archive of old Chromes on Android, so that I can test all these Chromia against the Google standard.

Anyway, to me, 2015 will be the year of the Chromia.]]></description>
<dc:subject>googlechrome android mobile browser internet webdevelopment webdesign software technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:8408f0bdca51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/simple-css-row-column-highlighting/">
    <title>Simple CSS-Only Row and Column Highlighting | CSS-Tricks</title>
    <dc:date>2015-02-01T04:05:51+00:00</dc:date>
    <link>http://css-tricks.com/simple-css-row-column-highlighting/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Highlighting rows of a table is pretty darn easy in CSS. tr:hover { background: yellow; } does well there. But highlighting columns has always been a little trickier, because there is no single HTML element that is parent to table cells in a column. A dash of JavaScript can handle it easily, but Andrew Howe recently emailed me to share a little trick he found on StackOverflow, posted by Matt Walton.

It was a few years old, so I thought I'd just clean it up and post it here.]]></description>
<dc:subject>css webdesign webdevelopment table highlight javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:67c0ec86c4cd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:table"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:highlight"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/weighing-svg-animation-techniques-benchmarks/">
    <title>Weighing SVG Animation Techniques (with Benchmarks) | CSS-Tricks</title>
    <dc:date>2015-01-30T04:48:42+00:00</dc:date>
    <link>http://css-tricks.com/weighing-svg-animation-techniques-benchmarks/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[After working with a number of SVG animation techniques for a few months now, I can give you a basic overview so you can compare them yourself. There are good reasons to use each one of these methods. Hopefully this post can point you to the right tool for the job.

We'll go through a basic comparison of features. Then we'll dig into how well they perform. Two different benchmarks are included. One is from recordings off the Chrome DevTools timeline, and the other is measuring visual recordings from the screen.

While HTML elements styled with CSS tend to perform better in animation, SVG has the advantage of being able to draw anything while being resolution independant. In the benchmarks, we're specifically working with SVG images.

We'll be comparing these SVG animation techniques:

CSS @keyframes
SMIL
Velocity.js
GreenSock (GSAP)
There are countless others that we don't cover, including Snap.svg and the older Raphaël.

It's worth noting that CSS and SMIL have animation capabilities native to the browser whereas GSAP and Velocity are JavaScript libraries that manipulate one or more of the rendering layers to create animation.]]></description>
<dc:subject>svg animation webdesign webdevelopment performance browser</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1a85236a4fba/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:svg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:animation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://signalvnoise.com/posts/3847-asking-why">
    <title>Asking why by Jonas Downey of Basecamp</title>
    <dc:date>2015-01-30T04:37:31+00:00</dc:date>
    <link>https://signalvnoise.com/posts/3847-asking-why</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[When you work outwards from why, you unlock all sorts of revelations that aren’t about obligatory features or popular trends. You might find that those scrolling effects and skills charts have nothing to do with your story and the outcome you want. Maybe you’ll uncover a parade of new ideas dying to see the light of day. Or you’ll decide your site is just for your own experimentation, and that’s OK too.
If you find no strong reasons for a project to exist, all the better! Kick it to the curb and free yourself to spend time on something else.]]></description>
<dc:subject>webdesign webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7ce0bd824bd1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.ircmaxell.com/2014/12/being-responsible-developer.html">
    <title>ircmaxell's blog: Being A Responsible Developer</title>
    <dc:date>2015-01-02T05:00:02+00:00</dc:date>
    <link>http://blog.ircmaxell.com/2014/12/being-responsible-developer.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The problem is that it is broken. All software is. The fallacy isn't that upgrading is "fixing something that works fine today", the fallacy is that it's working fine in the first place.

You can choose to ignore the break, or you can make an "informed" decision that the break isn't worth fixing, but don't pretend it's working fine.]]></description>
<dc:subject>software softwareengineering softwaredesign security php programming webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:fe581445b3c4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwaredesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/the-power-of-perceived-performance/">
    <title>Performance Calendar » The Power of Perceived Performance</title>
    <dc:date>2015-01-02T01:55:41+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/the-power-of-perceived-performance/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[It was surprising how a tiny progress indicator could change the perception of an entire application. The performance numbers with and without the progress indicators were the same. But just with that indicator, the application feels much faster. This is the real power of perceived performance. As a bonus, avoiding the re-parse and re-execution of large CSS and JavaScript on each navigation made our page interaction ready instantly.]]></description>
<dc:subject>performance usability userexperience webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:d466a0903d5e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userexperience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/retake-performance/">
    <title>Performance Calendar » Retake performance</title>
    <dc:date>2015-01-01T20:50:28+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/retake-performance/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[For too long, the DevOps community has been hamstrung by the demands of the business departments with whom we work. The obvious goal of any DevOps team is to make the sites for which we’re responsible as fast and reliable as possible. And yet at the same time, we’re constantly being undermined by the business side of the company who can’t resist overloading the pages with third party tags; sometimes they even forgot why they put a tag in the first place!

It’s no secret among performance professionals that third party content can torpedo a site’s performance, but the problem is that this message has not yet been delivered en masse to the people who ultimately control what gets placed on the pages and what doesn’t. Even something as simple as fonts can wreak havoc with performance. Why would you need ten different fonts on each page?

In this sense, the DevOps and Marketing departments are often seen at odds with each other – marketing wants to place ads, tracking tags, and other third party content on the site that they believe will increase visibility of the page and thus bring in more revenue. Even when it’s pointed out that these things diminish a site’s performance, the best case scenario is usually to just find a happy medium, or in the worst case, the DevOps team is told to just do the best they can with whatever gets forced upon them.

However, this is at odds with the entire purpose of performance, which is to serve as a business differentiator. In that sense, web perf MUST be an integral part of the marketing agenda. You may have heard of the four Ps that comprise the marketing mix – Product, Price, Promotion, and Place – but Performance is now the fifth P. The problem is that it’s treated like a fifth wheel instead.

So let’s all make a New Year’s resolution that 2015 is the year in which we take back performance from those who either don’t understand or don’t care about its impact on the business’s bottom line. There doesn’t have to be an incompatibility between marketing and performance, but we have to do a better job of making its impact clear to those who don’t work in the industry.
]]></description>
<dc:subject>performance webdesign webdevelopment software softwareengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:6d0a5f1b2ebd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/web-beacon-speedup-for-improved-user-experience/">
    <title>Performance Calendar » Web Beacon Speedup for Improved User Experience</title>
    <dc:date>2015-01-01T20:37:11+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/web-beacon-speedup-for-improved-user-experience/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Sometimes these beacons can either take too long or too many beacons are fired from the page, thereby slowing down the performance of the site.

Most beacon servers normally have an proxy server fronting them, so all requests pass through them. Lets look at what we can do to minimize the impact of these Beacons on the site performance by using the proxy.]]></description>
<dc:subject>webdevelopment software performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:fc694787531a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/leverage-browser-storage-for-a-faster-web/">
    <title>Performance Calendar » Leverage Browser Storage For a Faster Web</title>
    <dc:date>2014-12-31T18:23:56+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/leverage-browser-storage-for-a-faster-web/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[One of the cardinal rules for web performance is to reduce HTTP requests. The common interpretation of reducing HTTP requests limits the focus to bundling and minifying scripts, creating image sprites and eliminating unused resources. Developers often overlook AJAX requests. Many AJAX calls GET the same, unchanged data as previously made requests. Today’s rich web applications, like single page applications, rely on numerous AJAX calls to retrieve data before it is rendered. Untamed these AJAX requests create unnecessary chatter between client instances and the server.

All modern browsers provide at least 2 ways to cache and persist data locally, localStorage and IndexDB (WebSQL is still around, but has become deprecated). Browser storage provides a mechanism to cache data, allowing us to avoid many costly HTTP requests. Eliminating these requests makes our applications perform much faster and helps server scale.]]></description>
<dc:subject>software localstorage IndexDB browser performance webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:a79ce924e513/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:localstorage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:IndexDB"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/different-angles-of-web-performance/">
    <title>Performance Calendar » Different Angles of Web Performance</title>
    <dc:date>2014-12-31T03:08:12+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/different-angles-of-web-performance/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Ideally performance should be addressed at all phases of system lifecycle: from the very beginning (performance requirements, how fast the system should be and how much load to handle) to design and development (using scalable design and using performance good practices, both back-end and front-end) to testing (for both single-user performance and load) to support and maintenance (closely monitoring performance in production and providing input for both development and testing for further improvement). We look at performance from different angles depending on lifecycle phases and task on hand – but we need all of them for a holistic view.]]></description>
<dc:subject>software softwareengineering webdevelopment performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:c610a1bc4521/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://leehblue.com/php-frameworks-affect-profitability/">
    <title>How PHP Frameworks Affect Profitability - Lee Blue</title>
    <dc:date>2014-12-31T02:11:56+00:00</dc:date>
    <link>http://leehblue.com/php-frameworks-affect-profitability/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[There are certainly pros and cons to frameworks, not matter which one you choose. We have discussed the issues we’ve faced with large frameworks, how large frameworks can end up costing big dollars over time, and how we were able to overcome many of these issues by using a small framework, composer packages, and our own home grown library.]]></description>
<dc:subject>php software softwareengineering framework webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:2384d160e149/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sitepoint.com/3-ways-implement-embeddable-custom-badges/">
    <title>3 Ways to Implement Embeddable Custom Badges</title>
    <dc:date>2014-12-31T02:10:00+00:00</dc:date>
    <link>http://www.sitepoint.com/3-ways-implement-embeddable-custom-badges/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Embeddable content is great way to promote your site. It can be used not only to link back to your site but to provide “live” content, right there on a third-party “host” website.

We’ve looked at three common approaches to this – images, iframes and JavaScript. We’ve looked at some of the things you need to think about when deciding which one to use, along with some pitfalls to be wary of.]]></description>
<dc:subject>software webdevelopment webdesign</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:815654fdccdb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/speeding-up-https-with-session-resumption/">
    <title>Performance Calendar » Speeding up HTTPS with session resumption</title>
    <dc:date>2014-12-31T02:05:22+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/speeding-up-https-with-session-resumption/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[TLS has several features that can be used to eliminate round trips during when resuming a session. The two standardized session resumption mechanisms are session IDs (RFC 5246) and session tickets (RFC 5077). Using either technique, a client can resume a previously established a session with a server using an abbreviated handshake, saving one round trip.

Session resumption based on session ID is available in all modern browsers. Both Firefox and Chrome also support session tickets. Support on the server side is also widespread, with nginx, Apache, HAProxy, IIS and others supporting both session IDs and session tickets natively.]]></description>
<dc:subject>security privacy https ssl tls encryption performance webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0f0470e1162b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ssl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:tls"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/going-beyond-onload/">
    <title>Performance Calendar » Going beyond onload</title>
    <dc:date>2014-12-30T19:12:56+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/going-beyond-onload/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[This means that users have gotten used to interacting with pages before the spinner stops spinning, and page developers have become smarter about building pages that are usable before they are fully loaded. So for everyone hoping to measure perceived performance, the window.onload event is no longer the best event to determine when a page is usable.]]></description>
<dc:subject>performance webdevelopment webdesign software usability userexperience</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b3d2880f9bf3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userexperience"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nngroup.com/articles/m-commerce-terrible-ux/">
    <title>M-Commerce: Terrible UX (at least for Christmas 2014 sales)</title>
    <dc:date>2014-12-30T06:28:49+00:00</dc:date>
    <link>http://www.nngroup.com/articles/m-commerce-terrible-ux/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Comparing these numbers shows that e-commerce sites have 288% higher conversion rates on desktop than on smartphones. (Desktop has 31% higher conversion rate than tablets, which is stupendously better than the smartphones’ UX performance and confirms our tablet user research finding that most desktop sites work reasonably well on tablets.)

Exacerbating the problem, average sales were $107.72 to desktop users compared with only $88.70 to mobile users. Thus, dollars made per visit were 372% higher for desktop compared with mobile (i.e., sales to desktop users were $4.72 for every dollar in sales to mobile users.) This, of course, is one reason advertising rates are much higher for desktop search than for mobile search: if you don't track your own analytics data in sufficient detail to tell otherwise, a good default strategy is to make mobile bids 20% of the desktop bids for each keyword. (A bid adjustment of -80% for mobile clicks.) However, it's obviously better to track your own analytics, because some of your keywords may perform better — or worse — per mobile click than the average. Queries relating to finding store locations may be more valuable on mobile than on desktop if you run an omnichannel operation.

I was going to say that desktop sites sell almost 4 times as much as mobile sites, but more likely the reason for these terrible mobile conversion rates is that many of these e-commerce companies don’t even have a special mobile design but try to show the same design to users regardless of platform. Scaling a user interface across different platforms doesn't just involve stretching or shrinking the same info to fit different screen sizes as with a naïve implementation of responsive design (RWD): much more is required to optimize a design for different screen sizes and input mechanisms.]]></description>
<dc:subject>ecommerce business statistics research mobile webdesign webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:9f24d2fbc6af/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ecommerce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://24ways.org/2014/cohesive-ux/">
    <title>Cohesive UX ◆ 24 ways</title>
    <dc:date>2014-12-30T06:06:09+00:00</dc:date>
    <link>http://24ways.org/2014/cohesive-ux/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I needn’t expound on the virtues of responsive web design (RWD). You’ve likely already encountered more than a career’s worth on the topic. This is a good thing. Count me in as one of its biggest fans.

However, if we are to sing the praises of RWD, we must also acknowledge its shortcomings. One of these is that RWD ends where the browser ends. For all its goodness, RWD really has no bearing on native apps or any other experiences that take place outside the browser. This makes it challenging, therefore, to create cohesion for multi-screen users if RWD is the only response to “let’s make it work everywhere.”

We need something that incorporates the spirit of RWD while unifying all touchpoints for the entire user experience—single device or several devices, in browser or sans browser, native app or otherwise.

I call this cohesive UX, and I believe it’s the next era of successful user experiences.]]></description>
<dc:subject>design webdesign webdevelopment software usability userexperience userinterface</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:6ed99c663631/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userexperience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:userinterface"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/saving-money-by-investing-in-performance-a-financial-model/">
    <title>Performance Calendar » Saving Money by Investing in Performance: A Financial Model</title>
    <dc:date>2014-12-30T03:14:39+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/saving-money-by-investing-in-performance-a-financial-model/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The example I gave shows how increasing caching impacts operations but it doesn’t stop there. Any change you make that makes applications more efficient, takes advantage of caches, reduces number of requests or makes requests smaller will impact the cost to the business. Using this simple model we can project the financial impact of those performance improvements.

This is only the beginning. I believe that there are many other financial models that can be used to help convince the business that performance matters!]]></description>
<dc:subject>business economics management investment performance webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:42fa050982ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:investment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/simplify-speed-with-the-halt-number/">
    <title>Performance Calendar » Simplify speed with the HALT number</title>
    <dc:date>2014-12-30T02:54:42+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/simplify-speed-with-the-halt-number/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Speed engineers rely on business buy-in to get the job done. Telling a clear story will gain you resources and help when it’s time to balance speed against other marketing considerations.

The cost of a garbled message? Wasted time, frustrated users, and lost sales. Last year, the big sites got 23% slower and lost billions as a result.

We already know how to start the speed story simply. “Customers show up to our slow website, get thwarted, and move on without spending money”. But what happens next? How do you handle the exec who gut-checks by pulling up his cached site from a high-speed T3 line?]]></description>
<dc:subject>software webdevelopment engineering performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:34cdb769175c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/squeezing-the-most-into-the-new-w3c-beacon-api/">
    <title>Performance Calendar » Squeezing the Most Into the New W3C Beacon API</title>
    <dc:date>2014-12-30T01:25:17+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/squeezing-the-most-into-the-new-w3c-beacon-api/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[With the new Beacon API, data can be posted to the server during the browsers unload event, without blocking the browser, in a performant manner. ]]></description>
<dc:subject>software softwareengineering performance webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:25e9bba1736f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2014/the-changing-role-of-the-browser-cache/">
    <title>Performance Calendar » The changing role of the browser cache</title>
    <dc:date>2014-12-30T00:40:17+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2014/the-changing-role-of-the-browser-cache/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[If I was asked to succinctly explain the role of the browser cache today, I’m not sure I’d be able to do it. There are so many files changing at such a rapid pace, and so many SPAs that are in use on a daily basis, that I don’t know there’s an easy answer. What I do know is that the browser cache’s role today is pretty different as compared to its role in 2007, and it will continue to evolve as technologies like service workers are implemented.

Given the changes, both past and future, it seems like a good time to start questioning our best practices around caching once again. The tabbed, SPA, continuous delivery world is looking for answers.]]></description>
<dc:subject>software performance browser hardware webdevelopment cache</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ba18b04250ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:cache"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cowbell/sharedrop">
    <title>cowbell/sharedrop</title>
    <dc:date>2014-12-29T17:57:47+00:00</dc:date>
    <link>https://github.com/cowbell/sharedrop</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[ShareDrop is HTML5 clone of Apple AirDrop service. It allows you to transfer files directly between devices, without having to upload them to any server first. It uses WebRTC for secure peer-to-peer file transfer and Firebase for presence management and WebRTC signaling.

ShareDrop allows you to send files to other devices in the same local network (i.e. devices with the same public IP address) without any configuration - simply open https://www.sharedrop.io on all devices and they will see each other. It also allows you to send files between networks - just click + button in the top right corner of the page to create a room with unique URL and share this URL with other people you want to send a file to. Once they open this page in a browser on their devices, you'll see each other's avatars.

The main difference between ShareDrop and AirDrop is that ShareDrop requires Internet connection to discover other devices, while AirDrop doesn't need one - it creates ad-hoc wireless network between them. On the other hand, ShareDrop allows you to share files between mobile (Android) and desktop devices and between networks as well.]]></description>
<dc:subject>html5 webdevelopment software webrtc firebase p2p</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ecd9cc2eb96a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webrtc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:firebase"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:p2p"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/redirect-web-page/">
    <title>How to Redirect a Web Page | CSS-Tricks</title>
    <dc:date>2014-12-26T02:34:51+00:00</dc:date>
    <link>http://css-tricks.com/redirect-web-page/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[A redirect is when a web page is visited at a certain URL, it changes to a different URL. For instance, a person visits "website.com/page-a" in their browser and they are redirected to "website.com/page-b" instead. This is very useful if we want to redirect a certain page to a new location, change the URL structure of a site, remove the "www." portion of the URL, or even redirect users to another website entirely (just to name a few).

Let's say we've just moved our website and we want to shut down the old one. However we don't want all those pages from the old site to give a dreaded 404 Not Found. What we need is for those old links to redirect to the same content on our new site.

Here's our example: we want old-website.com/blog/post to redirect to new-website.com/blog/post, along with all the other posts that use that same URL format. Also it would be nice if our redirects would report to search engines that this change is permanent so they should update accordingly.

So how do we that? Well, before we start we need to learn a little about HTTP.]]></description>
<dc:subject>webdevelopment webdesign software php javascript html http apache nginx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:3737c2bd89bb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:apache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:nginx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gist.github.com/sergejmueller/cf6b4f2133bcb3e2f64a">
    <title>WOFF 2.0 – Learn more about the next generation Web Font Format and convert TTF to WOFF2 over command line without setup.</title>
    <dc:date>2014-12-04T04:53:28+00:00</dc:date>
    <link>https://gist.github.com/sergejmueller/cf6b4f2133bcb3e2f64a</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[WOFF 2.0 – Learn more about the next generation Web Font Format and convert TTF to WOFF2 over command line without setup.]]></description>
<dc:subject>TTF WOFF2 WOFF webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:45f6d79b4679/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:TTF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:WOFF2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:WOFF"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://h30499.www3.hp.com/t5/Fortify-Application-Security/Authenticated-application-security-tests-vs-unauthenticated/ba-p/6602260">
    <title>Authenticated application security tests vs. unaut... - HP Enterprise Business Community</title>
    <dc:date>2014-11-27T07:53:21+00:00</dc:date>
    <link>http://h30499.www3.hp.com/t5/Fortify-Application-Security/Authenticated-application-security-tests-vs-unauthenticated/ba-p/6602260</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[I often hear people say, “I only want to test my application from an attacker’s point of view so let’s run an unauthenticated scan and call it a day.” It’s also argued that authenticated tests take too much time or are too expensive and require more specialized expertise.
 
Experienced testers have the opinion that in order to get the most out of an application security assessment, the application should be tested using an authenticated user. Running an unauthenticated test gives a very broad overview of the application’s security and paints an incomplete picture compared to authenticated testing.]]></description>
<dc:subject>security privacy webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1fb6a07e6594/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.quirksmode.org/blog/archives/2014/11/android_gradien.html">
    <title>Android gradient screenshot madness - QuirksBlog</title>
    <dc:date>2014-11-26T04:08:03+00:00</dc:date>
    <link>http://www.quirksmode.org/blog/archives/2014/11/android_gradien.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The real point here is that Android screenshots (and remote testing solutions that depend on them) are not reliable enough for web developers to use.]]></description>
<dc:subject>googleandroid software programming usability css webdesign webdevelopment hardware</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f0d46253eabd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googleandroid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codersblock.com/blog/fun-times-with-css-counters/">
    <title>Coder's Block Blog / Fun Times with CSS Counters</title>
    <dc:date>2014-11-19T02:57:05+00:00</dc:date>
    <link>http://codersblock.com/blog/fun-times-with-css-counters/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[CSS counters are one of those “oh neat, didn’t know CSS could do that” features with a lot of interesting potential. In simple terms, they let you keep a running tally of things in CSS — no JavaScript needed.]]></description>
<dc:subject>css software webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ad170a4c5099/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://googlewebmastercentral.blogspot.com/2014/11/helping-users-find-mobile-friendly-pages.html">
    <title>Official Google Webmaster Central Blog: Helping users find mobile-friendly pages</title>
    <dc:date>2014-11-19T01:59:44+00:00</dc:date>
    <link>http://googlewebmastercentral.blogspot.com/2014/11/helping-users-find-mobile-friendly-pages.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Have you ever tapped on a Google Search result on your mobile phone, only to find yourself looking at a page where the text was too small, the links were tiny, and you had to scroll sideways to see all the content? This usually happens when the website has not been optimized to be viewed on a mobile phone.

This can be a frustrating experience for our mobile searchers. Starting today, to make it easier for people to find the information that they’re looking for, we’re adding a “mobile-friendly” label to our mobile search results.]]></description>
<dc:subject>google mobile search searchengine webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:864264fb0685/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:searchengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.froont.com/9-basic-principles-of-responsive-web-design/">
    <title>9 basic principles of responsive web design</title>
    <dc:date>2014-11-17T02:32:26+00:00</dc:date>
    <link>http://blog.froont.com/9-basic-principles-of-responsive-web-design/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Responsive web design is a great solution to our multi-screen problem, but getting into it from the print perspective is difficult. No fixed page size, no millimetres or inches, no physical constraints to fight against. Designing in pixels for Desktop and Mobile only is also the past, as more and more gadgets can open up a website. Therefore, let's clarify some basic principles of responsive web design here to embrace the fluid web, instead of fighting it. To keep it simple we'll focus on layouts (yes, responsive goes way deeper than that and if you want to learn more this is a good start).]]></description>
<dc:subject>webdesign webdevelopment software design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:6d84c5a62040/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://code.facebook.com/posts/307478339448736/year-class-a-classification-system-for-android/">
    <title>Year class: A classification system for Android</title>
    <dc:date>2014-11-07T01:55:10+00:00</dc:date>
    <link>https://code.facebook.com/posts/307478339448736/year-class-a-classification-system-for-android/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[With so many different types of phones in the world, being able to segment people and their devices to understand usage patterns and performance is a significant task. Historically we relied on cuts by Android OS version, looking at how Gingerbread behaved differently from Ice Cream Sandwich, how Ice Cream Sandwich behaved differently from Jelly Bean, and so on. However, the recent explosion of affordable Android devices around the world has shifted the median, and the bulk of devices we now see are running Jelly Bean. In order to segment based on actual phone performance we decided to look more closely into the specifications of the phone – RAM, CPU cores, and clock speed – to characterize things. Using these three specifications, we've clustered every phone into a group of similarly capable devices to make understanding performance easier.

We call this new concept “year class” – essentially, in what year would a given device have been considered “high end?" This allows teams around the company to segment the breadth of Android devices into a more understandable set of buckets, and as new phones are released, they're automatically mapped into the representative year. For example, the Alcatel T-Pop I bought at a market in Mexico is immediately recognized as a 2010-class phone, despite its 2012 release. Overall, about two-thirds of the phones connected to Facebook are equivalent to something released in 2011 or earlier.]]></description>
<dc:subject>googleandroid hardware software webdesign webdevelopment facebook mobile</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:39e662d1236c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googleandroid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mobile"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/scroll-fix-content/">
    <title>Scroll-Then-Fix Content | CSS-Tricks</title>
    <dc:date>2014-11-06T01:21:15+00:00</dc:date>
    <link>http://css-tricks.com/scroll-fix-content/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Like most good tricks, there isn't much to it. All we do is think of (and design for) the two different possible states:

Search bar in its scrollable position
Search bar in its fixed header position
We toggle between them simply by changing a class name. There is no trickery with having two search forms that reveal themselves in different scenarios. That's good, as we don't want to smurf around with keeping those in sync. Much easier to just move a single one around.]]></description>
<dc:subject>design webdesign webdevelopment css html javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ce02610bc8fa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/blog/news/archives/4167">
    <title>HTML5 is a W3C Recommendation | W3C News</title>
    <dc:date>2014-10-30T00:43:32+00:00</dc:date>
    <link>http://www.w3.org/blog/news/archives/4167</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The HTML Working Group today published HTML5 as W3C Recommendation. This specification defines the fifth major revision of the Hypertext Markup Language (HTML), the format used to build Web pages and applications, and the cornerstone of the Open Web Platform.]]></description>
<dc:subject>html5 w3c standards browser webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:35fc76a07eef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ad7six.com/blog/2014/10/25/logrotate-rotate-your-log-files">
    <title>Logrotate: Rotate Your Log Files - AD7six.com</title>
    <dc:date>2014-10-26T00:56:37+00:00</dc:date>
    <link>http://ad7six.com/blog/2014/10/25/logrotate-rotate-your-log-files</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[You should probably be using syslog, but if you’re not, don’t leave your log files lying around as a (slow) time bomb. Even on a development machine, I’d recommend to configure logrotate to keep things tidy; it at least eliminates one cause for a server needing urgent attention.]]></description>
<dc:subject>logging software webdevelopment hardware</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:95df3585d34c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:logging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/SlexAxton/css-colorguard">
    <title>SlexAxton/css-colorguard</title>
    <dc:date>2014-10-26T00:11:49+00:00</dc:date>
    <link>https://github.com/SlexAxton/css-colorguard</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Every CSS project starts out with good intentions, but inevitably, one too many people eye-dropper colors into nooks and crannies that you never knew existed. CSS Colorguard helps you maintain the color set that you want, and warns you when colors you've added are too similar to ones that already exist. Naturally, it's all configurable to your tastes.]]></description>
<dc:subject>css color webdesign webdevelopment npm</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:05dd9121921e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:color"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:npm"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/philsturgeon/status/524502715951763456">
    <title>Phil Sturgeon on Twitter: &quot;@jongold I dunno about that. It seems to be built around the premise that HTTP Basic is awesome. http://t.co/WaSytXv82Q&quot;</title>
    <dc:date>2014-10-22T06:29:19+00:00</dc:date>
    <link>https://twitter.com/philsturgeon/status/524502715951763456</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[@jongold I dunno about that. It seems to be built around the premise that HTTP Basic is awesome. ]]></description>
<dc:subject>security webdevelopment programming api</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:90fd57d87f4c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/google/material-design-icons">
    <title>google/material-design-icons</title>
    <dc:date>2014-10-22T05:32:17+00:00</dc:date>
    <link>https://github.com/google/material-design-icons</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Material Design Icons are the official open-source icons featured in the Google Material Design specification.]]></description>
<dc:subject>icons design github google webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0beb14ee42ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:icons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/probably-dont-base64-svg/">
    <title>Probably Don't Base64 SVG | CSS-Tricks</title>
    <dc:date>2014-10-22T02:30:38+00:00</dc:date>
    <link>http://css-tricks.com/probably-dont-base64-svg/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[So that makes sense, right? If it's 4 characters for every 3 bytes, that's 133% bigger, with the variation coming from uneven lengths and thus padding.

Anyway, maybe this is all super obvious. But it just seems to me if you're going to use a data URI for SVG there is no reason to ever base64 it.]]></description>
<dc:subject>svg css base63 encoding webdesign webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:100f123a54a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:svg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:base63"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:encoding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing">
    <title>One Step Ahead: Improving Performance with Prebrowsing · An A List Apart Article</title>
    <dc:date>2014-10-15T04:53:17+00:00</dc:date>
    <link>http://alistapart.com/article/one-step-ahead-improving-performance-with-prebrowsing</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[But we can still do more. If we want faster outcomes, we have to think differently. What if, instead of leaving our users to stare at a spinning wheel, waiting for content to be delivered, we could predict where they wanted to go next? What if we could have that content ready for them before they even ask for it?

We tend to see the web as a reactive model, where every action causes a reaction. Users click, then we take them to a new page. They click again, and we open another page. But we can do better. We can be proactive with prebrowsing.]]></description>
<dc:subject>internet programming software development webdevelopment performance prefetch hardware prebrowsing html optimization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:993573f241be/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:prefetch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:prebrowsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:optimization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c">
    <title>13 Ways Designers Screw Up Client Presentations</title>
    <dc:date>2014-09-20T23:27:10+00:00</dc:date>
    <link>https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The hardest part of design is presenting work. You can’t even argue about this. I’ve seen people who did amazing work get up in front of a client and lay eggs. I’ve also seen people do alright work and work clients around their little finger. Optimally, you want to do good work and present it well. But I’d rather have a good designer who can present well than a great designer who can’t. In fact, I’d argue whether it’s possible to be a good designer if you can’t present your work to a client. Work that can’t be sold is as useless as the designer who can’t sell it.

And, no, this is not an additional skill. Presenting is a core design skill.

The first time I presented design to a client I absolutely choked. I put the work in front of them and stood there like an idiot. It was humiliating. The next time was a little easier. And the time after that, well, you get the idea. I have done every one of the things on this list. I’m sharing them with you in the hopes that they’ll spare you a humiliating experience or two. It’ll take time.]]></description>
<dc:subject>design webdevelopment communication business client</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:300aae67eede/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:client"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://realfavicongenerator.net/">
    <title>Favicon Generator - Generate favicon pictures and HTML</title>
    <dc:date>2014-08-24T07:23:46+00:00</dc:date>
    <link>http://realfavicongenerator.net/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Generate the favicon pictures and HTML code that work on all major browsers and platforms]]></description>
<dc:subject>favicon design webdesign webdevelopment html software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e929cce21f3c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:favicon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/jcolman/status/500070630247903232">
    <title>Twitter / jcolman: &quot;Two years ago, web designers ...</title>
    <dc:date>2014-08-15T04:37:41+00:00</dc:date>
    <link>https://twitter.com/jcolman/status/500070630247903232</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["Two years ago, web designers thought they invented typography. Five years ago, they thought they invented grids." — @monteiro]]></description>
<dc:subject>webdesign webdevelopment software design usability client</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1a01aebf075a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:client"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/jcolman/status/500070796145197056">
    <title>Twitter / jcolman: &quot;You don't throw away thousands ...</title>
    <dc:date>2014-08-15T04:37:36+00:00</dc:date>
    <link>https://twitter.com/jcolman/status/500070796145197056</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["You don't throw away thousands of years of design knowledge just because you're doing it for mobile!" — @monteiro at @facebookdesign]]></description>
<dc:subject>webdesign webdevelopment software design usability client</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:cb427e75a0dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:client"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/jcolman/status/500071899440111616">
    <title>Twitter / jcolman: Clients hire you to be the ...</title>
    <dc:date>2014-08-15T04:37:13+00:00</dc:date>
    <link>https://twitter.com/jcolman/status/500071899440111616</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Clients hire you to be the expert. They pay you $200/hour to MAKE THEM LISTEN TO YOU. — @monteiro at @facebookdesign]]></description>
<dc:subject>webdesign webdevelopment software design usability client</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b9e679c7df4f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:usability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:client"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/thomasfuchs/status/493790680397803521">
    <title>Twitter / thomasfuchs: Two CSS properties walk into ...</title>
    <dc:date>2014-07-28T18:04:16+00:00</dc:date>
    <link>https://twitter.com/thomasfuchs/status/493790680397803521</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Two CSS properties walk into a bar.

A barstool in a completely different bar falls over.]]></description>
<dc:subject>humor webdesign webdevelopment programming css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7041e3fdbce2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:humor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://signalvnoise.com/posts/3752-its-ok-not-to-use-tools">
    <title>It's OK not to use tools by Jonas Downey of Basecamp</title>
    <dc:date>2014-05-22T06:11:27+00:00</dc:date>
    <link>http://signalvnoise.com/posts/3752-its-ok-not-to-use-tools</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[As builders, we like tools and tech because they’re interesting and new, and we enjoy mastering them. But when you think about the people we’re building for, the reality is usually the opposite. They need simple designs, clear writing, less tech, and fewer abstractions. They want to get stray animals adopted, not fuss around with website stuff.
Remember when the web was damn simple? It still can be. It’s up to us to make it that way.]]></description>
<dc:subject>technology webdevelopment webdesign software softwareengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:7fb768832220/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://karptonite.com/2014/05/11/rehashing-password-hashes/">
    <title>Rehashing Password Hashes</title>
    <dc:date>2014-05-17T23:15:17+00:00</dc:date>
    <link>http://karptonite.com/2014/05/11/rehashing-password-hashes/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Notice what we’ve done here: We don’t have the user’s password, but we do have a hash that we know can be generated from the password and the proper salt. We’ve treated that hash as the password for the new, improved hashing system. We know that when the user does type in their password, we will be able to regenerate that hash because we still have the salt.1

Now for the important part: you can delete all of the the old password hashes (but not the salts) from the database and any backups. All users are now protected by the new password hashing algorithm, even if they never log in again.

Note that in practice, some legacy systems will have saved the salt and the hash as part of the same string, but these should be separable. The important thing is to keep the salt but discard the old hash.]]></description>
<dc:subject>password security encryption privacy webdevelopment software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5f63a142a703/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:password"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://us6.campaign-archive2.com/?u=161d0ed420649f1879e4985f1&amp;id=db03f282c7&amp;e=d909de5621">
    <title>Laravel and Grumpy Programmers</title>
    <dc:date>2014-05-07T01:51:22+00:00</dc:date>
    <link>http://us6.campaign-archive2.com/?u=161d0ed420649f1879e4985f1&amp;id=db03f282c7&amp;e=d909de5621</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Still, the facade thing is a warning to remain vigilant and do your research
into what everyone else calls something. Common vocabulary is critical when
it comes time to solve difficult problems.

Consistency matters because it allows you to recognize patterns, which leads
to learning how to group common functionality together to reduce code, make
tests easier (yes, Laravel has a very large commitment to making it's code
easy testable), and providing clarity when reading code written by others.
]]></description>
<dc:subject>webdevelopment software programming softwareengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:20eaaaaf1276/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:softwareengineering"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>