Ep 48: Clear Your F’in Cache

Grumpy Old Geeks —  March 7, 2014

This episode is dedicated to anyone who has had to utter the words “Clear your cache and reload.” We feel your pain and just want you to know that you’re not alone. This show was edited and posted from an Amtrak Southwest Chief train from Chicago to LA!

Show Notes

Gentrifying the dharma: How the 1 percent is hijacking mindfulness

Shaq-Fu: A Legend Reborn

Inside The Netflix/Comcast Deal and What The Media Is Getting Very Wrong

Five Things You Should Know About the Netflix-Comcast Deal Idiot’s guide

Why is American internet so slow?

Health Experts Don’t Buy Into L.A.’s E-Cigarette Ban

Beats buys TopSpin

Kickstarter passed $1 BILLION in pledges

The Smartphone Wars Are Coming to Your Car

Phoenix on Lessig and Lisztomania: “We Support Fair Use of Our Music!”

Facebook and the Feudal Lords of Social Fiefdom: Bad For Artists?

Paging Bradley Cooper’s Lawyers: He Might Own Ellen’s Famous Oscar Selfie – The Wire

Getty opens up its library with interesting licensing

Almost too good to be true

Would Lord of the Rings Be More Satisfying With a Different Ending?

Internet History Podcast

Tray

Exposure.so

Fantastical 2

Spritz

Microsoft Wants to Kill Windows XP, but it Just Won’t Die

UK patients’ data uploaded to Google servers, serious privacy concerns ensue

Cheeto Looks Like Masturbating Man

Lisa Belkin leaves The Huffington Post for Yahoo

REVIEW NEW SINGLE: _LAND OF THE BLIND – INFORMATION SOCIETY

2 responses to Ep 48: Clear Your F’in Cache

  1. Ya’know – if the user doesn’t see the changes upon a simple refresh it means that the webserver is set up incorrectly (ie. it doesn’t send the correct Cache-Control / Etag headers).

    So it *is* your fault :-)

    Skipped this episode because of this discussion, hopefully the next one will be less annoying :-)

    • No, they’re idiots and browsers are still shit. Cache-control and new and dynamic content doesn’t always do what you want it to when refreshing because of the aforementioned shitty browsers. Add in varnish or other caching proxies and you have a mess. Most of the time though the client can clear their cache and force the reload and it works. Ergo, clients fault.