Hacker Timesnew | past | comments | ask | show | jobs | submit | rkarachinsky's commentslogin

FYI, the launch itself will be at 4:58pm ET.


Apparently that's 4:58pm in EDT, or 16:58 in EDT, or 20:58 in GMT (nearly UTC).


If you're in the UK, remember we're on BST currently, so it'll be 21:58 here.


The difference between UTC and GMT is that GMT used to also refer to astronomical time (UTC-12), so UTC is preferred for clarity.

They are otherwise identical, so "nearly" is just confusing here.


Wikipedia states that GMT doesn't have a precise definition: "The term Greenwich Mean Time (GMT) does not have a precise definition at the sub-second level, but it is often considered equivalent to UTC or UT1. Saying "GMT" often implies either UTC or UT1 when used within informal or casual contexts. In technical contexts, usage of "GMT" is avoided; the unambiguous terminology "UTC" or "UT1" is preferred."


You are correct, and I should have been more precise in my criticism.

Nonetheless I think describing GMT as "nearly UTC" isn't particularly helpful, since it's not defined accurately enough to be wrong. Furthermore, EDT is defined in terms of UTC, so there's no reason to mention GMT at all.


I think I mentioned GMT for it's familiarity. I think "nearly UTC" is fitting, as it's close to UTC even though it's not precisely defined.


We (News360) were one of the launch partners for the OneNote API as well and our experience with it has also been really positive - the API itself is pretty simple right now but has all the details right. It's a great foundation to build on, and the team building it seems really committed to keeping the momentum going.

Having external tools, both hardware and software, is a huge part of building a memory-augmenting product and I'm really happy that Microsoft is getting it right - OneNote has always been a really interesting product, but it suffered from weird positioning and always felt like an add-on to Office more than anything else. Now that it's being marketed as more of a standalone (and free!) product, I think it has a great chance of becoming much more mainstream.


For anyone considering paying the $2.99 to read the rest of the story: it's a somewhat interesting read, but really doesn't give any additional insight into the condition itself. It describes the author's rather uneventful series of attempts at finding a pharmaceutical cure, and then him resigning to a life with HPPD.


I run News360, which is a popular news aggregator, and TPM pulled their full-text feed from us as well.

I think the issue here is that aggregators are trying to own the reading experience without replacing the monetary value of traffic to TPM's site, which is what's really bugging Josh, not losing direct relationship with the reader. He's fine with Google News, and he's fine with a truncated RSS feed being consumed in News360, or Flipboard or wherever as long as the main story has to be read on talkingpointsmemo.com.

This makes sense to me, and I think it's a very common problem across all content creators except the top-tier publishers who can actually make ad deals to sell inventory inside the aggregator (see TechCrunch/AOL's experience described here - http://techcrunch.com/2013/09/23/flipboards-mike-mccue-confi...). But looking at the mobile version of any article on talkingpointsmemo.com I have to question how effectively they're monetizing that traffic right now - it seems like it's all a bunch of network banner ads that I can't imagine anyone ever tapping on except by accident.

I think with the right native mobile experience, TPM can get a much larger value from a mobile reader, and if someone can provide an aggregator that delivers that to everyone, not just the top brands, it should be a no-brainer to jump on board. And I think we as an industry are pretty close to figuring out how this can work (we @News360 are certainly working very hard on this specific problem).


How about aggregators paying the publishers for full-text feed and then monetizing in the best possible way on their own mobile platforms? This is like paying a royalty to the content creators.


Well, isn't that the same thing essentially? We've already figured out how to do rev-share from ads and subscriptions and we have the infrastructure for it - I think it's better to use that than invent a royalty-based system that just creates obfuscation (I mean look at the complexity in royalties in music/movies/books - I don't want that in news content as well).


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: