39 Matching Annotations
  1. Last 7 days
  2. Nov 2019
    1. Knowing the "risk", I was very happy to find this post (and the comments for the actual keyword). I didn't want more than read two frickin' paragraphs. I did not intend to give any personal details, payment information or whatever. Maybe there was a man in the middle and the information displayed had been altered - so what? "There's someone wrong on the internet" - nothing more. I have to check if the information I get from the site is plausible, that's part of my job. There was no "risk". I, as an informed user, should always have the possibility to access sites like that. The keyword-thing makes this harder for simple FaceTube-Clickers, and for a good reason, but I think it is a good solution, given my example.

      "The TLDR; is that it stops users from clicking through security warnings"

      So it's a restriction on users. As a user, I cannot accept that. It's war against ME.

    1. "While we hope that Google will lift these unwarranted sanctions for AdNauseam, it highlights a much more serious problem for Chrome users," the AdNauseam team adds. "It is frightening to think that at any moment Google can quietly make your extensions and data disappear, without so much as a warning."
  3. Oct 2019
    1. In Chrome browser, open Developer Tools and select Elements tab, then open the contextual menu of the parent node of the element you want to inspect, in the contextual menu click on Break on > Subtree modifications. Afterwards you just need to click on the page and you'll get on the inspector without losing focus or losing the element you want to inspect.
    2. (() => { debugger; }, 5000)
  4. Feb 2019
  5. Jan 2019
  6. Nov 2018
  7. Oct 2018
  8. Mar 2018
  9. Nov 2017
    1. Note that Speak the Words only works in Chrome. 

      Ugh! Conceivably, it also works in Chromium. But this is the kind of thing which really changes the way a feature is used.

  10. Sep 2017
    1. When multiple tabs consume your application and you need to have a common gateway for the interaction.

      eg : an application which shows total number of mouse clicks through all tabs, in all of them.

    2. Background pages are the controllers of our application and exist through all the time our application is alive. They can be consumed by any tab at any time as long as the Background Page has registered an event listener

      what's meant by registering an event listener by bg process?

    3. An extension "registers" callbacks to Chrome for a specific situation given you described a specific interface to do so

      can some one elaborate on this? ty

  11. Jun 2017
    1. For some reason, no one ever seems to thing of this... but it has always worked for me... Have you tried unchecking Use hardware acceleration when available at the bottom of chrome://settings/ (advanced area)?

      This worked for me when Chrome was freezing every time I loaded a page. I was seriously worried I had a rootkit or key logger that I couldn't detect!

  12. Jun 2016
  13. 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.

  14. Apr 2016
    1. this app DOES NOT do

      History Trends

      • Chrome Web Store google.com pmP site directo procurar

      History Trends Unlimited - Chrome Web Store google.com pmP site directo procurar11 chromea14.1_d3ext

    2. Type “dh” and hit the “tab” key to enter Deep History search mode. Then type in search terms and Deeper History will search pages you have visited for those terms and return matching pages right there in your browser bar, just like google search.
  15. Mar 2016
    1. What about extensions for other browsers? We’re working on that. The next supported browser is likely to be Firefox.

      I'm writing this note in... Safari!

      I thought hypothes.is could only work with the Chrome applet.

      Still looking for a way to use hypothes.is from a tablet.

  16. Jan 2016
  17. Oct 2015
    1. The temporary solution we found is to wrap chrome.* api callback with setTimeout() function. In that case errors thrown within chrome.* api call are passed to window.onerror with correct line number. Example:

      Wrapping all the chrome.* async API calls such that exceptions in the callback result in an error being logged to a handler that we control looks like the way to go.

    2. In Chrome extensions, errors thrown in callbacks for async APIs do not trigger the global window.onerror handler.

  18. Jan 2014
    1. The following selection from The Yale Law Journal is not paginated and should not be used for citation purposes.

      Note that this disclaimer only says the document should not be used for citation purposes, but doesn't say we can't use it for annotation purposes like testing out the Chrome PDF.js + Hypothes.is extension! :)

      You can install the extension from the Chrome Web Store with this link:

      https://chrome.google.com/webstore/detail/pdfjs-%2B-hypothesis/bipacimpfefoidapjkknffflfpfmjdog/related