Thanks. Something like that might work. I had to do similar to prevent Google caching my KML file.
But I've now gone to a MySQL DB driven thing. But that seems to have similar problems of not clearing out the old data :@ (fail)
<?php header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); header("Cache-Control: no-store, no-cache, must-revalidate"); header("Cache-Control: post-check=0, pre-check=0", false); header("Pragma: no-cache"); ?>
New rule, whatever PB says people 'ought' to be doing with tech, make the opposite.
???
Profit.
Doesn't matter. Your opinions on what people should do and how they should do it are almost always the exact opposite of what people want.
I have no evidence to back this up, other than your specificness about features and functions, but it's totally true.
No need for that, we have more than enough anecdotal evidence right here on Teh.
Pete doesn't use Steam - 40+ million people do use steam
Pete uses Google Plus - Rest of the world + dog uses Facebook
Pete doesn't have a landline - everyone else does
I could go on, but I'm busy...
You only use that because of Teh. In Teh Podcast thread you made it quite clear that you'd rather use G+ for text-based communication.
:C
That wasn't the part I was disputing, it was the IM/notifications thing.
Actually, if we make a permanent "Podcast" room and invite everyone who's interested, chat is persistent and stuff that's posted while you're offline comes up when you log on. I'm not too sure how it behaves when people in the room are in a call though. Besides, do we want people dropping freely into the podcast while it's being recorded? If someone's late or wants to join after it starts for whatever reason, surely it would be better to co-ordinate that with the people in the call and be invited when they're ready? That can be done fine via Skype.
And I'm not saying G+ isn't perfectly viable, I don't really know the mechanics of hangouts so I can't pass judgement on that. I'm just not sure what's so bad about Skype.