9 Matching Annotations
  1. Apr 2018
    1. Let’s get right to the point.

      Just one moment. Before you spend time on this article, read the disclosure at the end. The author is on Panasonic's payroll. Now you know which technology comes out ahead without reading the whole thing.

  2. Mar 2018
    1. The project is lightweight with just 40 lines of Python

      That's quite a remarkable total. Just the main py file is 493 SLOC. Check your sources.

  3. Oct 2016
    1. The aim of science is to establish facts

      That's highly inaccurate. It correspond to a very static and theory-poor vision of science which has no connection with reality.

    1. it is safe to assume Yin did not leave Pfizer after 13 years of service entirely voluntarily.

      It isn't. Type of company is different, role is different. Safe to assume cash compensation is worse, equity better. Just stick to what you know.

  4. Sep 2016
    1. Reuse this content

      The comments are supposed to be under here. I know the Guardian removed the comment section for some topics, but what's up with statins? Too bad because this article lacks context. This is just one piece of evidence. A review of 10 papers finds effects of statins to be smaller. http://www.thennt.com/nnt/statins-for-heart-disease-prevention-without-prior-heart-disease/

  5. Aug 2016
    1. Fever

      If you want to stay up to date with the Kardashians, this is the one.

    2. NewsBlur

      I use this, but so called predictive article filtering is an absolutely broken exact keyword match. Suggestions on how to improve it have been rejected. After you use it for a while, it doesn't filter anything.

    3. Works only as extension on the web. Permission required are most extensive. Use if you think security is a joke, or if you trust Feedly as much as your mother.

  6. May 2016
    1. Your privacy is very important for us and we’re trying our best to ask you for as little information as we can

      First, I have no reason to think you are anything but well intentioned. Second, your code is open source so it would be harder for your organization to hide any foul play. Nonetheless, please anyone correct me if I am wrong, this set of permissions would be sufficient to collect server-side a complete browsing history for each user with the extension installed. This would be a gold mine for intelligence and advertisement purposes. A similar service to hypothes.is, genius, is VC funded and seeks a return on investment. Its chrome extension requires equally extensive permissions but there is an alternate extension, genie, that claims to offer an alternative without the "read and change" permission. Hard to believe, but people must at least consider the possibility of extensions turning rogue. I consider the "read and write ... on ALL websites" a threat and do not install any extensions that require it. I use the bookmarklet, which offers an inferior experience, but I can decide page by page if I am OK with a third party knowing that I am reading it. Also, I decided against using hypothes.is as the commenting system for my blog, since I don't want my readers to be traceable by a third party I choose on their behalf. I am heartened that you are already working towards reducing the number of permissions required, but I was wondering if you had additional comments for people who need to protect their browsing activity against worst case scenarios and can not accept the "trust us" argument.