51 Matching Annotations
  1. Jan 2020
  2. Dec 2019
    1. This is a browser execution environment. It may provide additional built in objects exposed in the global namespace. It is a specialized execution environment which provides builtin capabilities beyond the base javascript language spec.
    2. Using the browser field in package.json allows a module author to clearly articulate which files are innapropriate for client use and provide alternatives.
    3. It allows the module code (and subsequently dependants on the module) to not use preprocessor hacks, source code changes, or runtime detection hacks to identify which code is appropriate when creating a client bound package.
    4. Consider that the client environment as the special case as it exposes objects into the global space to provide certain features and limits others.

      Doesn't the server ever expose objects into the global space??

    5. The browser field is where the module author can hint to the bundler which elements (other modules or source files) need to be replaced when packaging.
    6. When a javascript module is prepared for use on a client there are two major concerns: certain features are already provided by the client, and certain features are not available. Features provided by a client can include http requests, websockets, dom manipulation. Features not available would include tcp sockets, system disk IO.
    7. You can simply prevent a module or file from being loaded into a bundle by specifying a value of false for any of the keys. This is useful if you know certain codepaths will not be executed client side but find it awkward to split up or change the code structure.
  3. Nov 2019
    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."
  4. Oct 2019
  5. Jul 2019
    1. Comparison between web browsers

      This is one of the best resources on web privacy I've ever seen. I warmly recommend it!

  6. Jan 2019
  7. Oct 2018
  8. Oct 2017
    1. Artemis is a free genome browser and annotation tool that allows visualisation of sequence features, next generation data and the results of analyses within the context of the sequence, and also its six-frame translation
  9. Sep 2017
    1. Plot a course through the genome Inspired by Google Maps, a suite of tools is allowing researchers to chart the complex conformations of chromosomes.

      mentioned tools are focused on (capture) Hi-C data

  10. Aug 2017
    1. 6.2 Extension IDs Each extension has an extension ID that follows the browserext:// protocol. For example browserext://MyExtension_c1wakc4j0nefm/options.html browserext://dfcijpibodeoenkablikbkiobbdnkfki/options.html The algorithms that generate these IDs are different for each browser. To access these resources, do not hardcode the ID generated by a particular browser. Instead, use the runtime.getURL() method to convert a relative file name or path to the absolute name or path, which includes the extension ID.

      Vivaldi, as you know, I love your browser and use it primary and multiple times a day, despite it's quirks deviating from Chrome.

      Having said this, can we eliminate the generated file names for extensions, screenshots, and notes?

  11. Jul 2017
    1. Firefox add-on technology is modernizing

      Note: Starting in Firefox 57, which will be released in November 2017, only add-ons built with this new technology will work in Firefox. These are indicated by the “Compatible with Firefox 57+” label on addons.mozilla.org (AMO). Add-ons built with the old technology are labeled “Legacy” on the about:addons tab. If an add-on does not have the "Compatible with 57+" label, or has the "Legacy" label, the developer may be in the process of transitioning to the new technology. You may find developer contact information on the right side of the add-on listing on AMO.

  12. Jun 2017
    1. HTTP/1.1定义的 Cache-Control 头用来区分对缓存机制的支持情况, 请求头和响应头都支持这个属性。通过它提供的不同的值来定义缓存策略。

      Request Header与Response Header都支持这个属性 通过调整Cache-Control头可以做出很多缓存策略:

      1. 完全不支持
      2. 不缓存内容
      3. 私有缓存
      4. 公共缓存
      5. 缓存过期时间
    2. 通常定义Pragma以向后兼容基于HTTP/1.0的客户端


    3. 当 web 缓存发现请求的资源已经被存储,它会拦截请求,返回该资源的拷贝,而不会去源服务器重新下载。


  13. Mar 2017
  14. Jan 2017
    1. var jq = document.createElement('script'); jq.src = "https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js"; document.getElementsByTagName('head')[0].appendChild(jq); // ... give time for script to load, then type (or see below for non wait option) jQuery.noConflict();

      Add jQuery in the console!

    1. Back then there were two major browsers competing for the soul of the web: Microsoft Internet Explorer and Netscape Navigator. They were incompatible by design. One browser would invent a new HTML element or attribute.

      If competition can lead to innovation, it's a hurdle when you try to build standards

    1. Browser software may ignore this tag.

      This is genius! Innovations and standards can live together on the web.

  15. Sep 2016
    1. You must quit IGV and restart for this preference to take effect. The genome should appear in the drop-down list.

      restart may be insufficient; had to modify prefs.properties in ~/igv (removing old cached genome values) before i could see my genomes

  16. Mar 2016
    1. Client<->Server API - defines how Matrix compatible clients communicate with Matrix homeservers. Server<->Server API - defines how Matrix homeservers exchange messages and synchronise history with each other.

      Given the data model (which allows merges) forkdb could be a close candidate to substitute a Client <-> Client API (also called peer to peer).

      Play with it.

    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.

  17. Jan 2016
  18. Aug 2015
    1. When we first set out to identify malicious extensionsour expectation was to find banking trojans and pass-word stealers that duplicated the strategies pioneered byZeus and SpyEye. In practice, the abusive extensionecosystem is drastically different from malicious bina-ries. Monetization hinges on direct or indirect relation-ships with syndicated search partners and ad injection af-filiate programs, some of which earn millions of dollarsfrom infected users [37]. Miscreants derive wealth fromtrafficanduser targetingrather than the computing re-sources or privileged access mediated via the browser. Itmay simply be that the authors of malicious binaries havelittle incentive (or external pressure) to change, leavingextensions to a distinct set of actors. This uncertainty isa strong motivation for exploring the extension ecosys-tem further.

      This is the section that identifies the motives and economics around malicious extensions

  19. Jul 2015
  20. Nov 2014
  21. Nov 2013