527 Matching Annotations
  1. Dec 2019
    1. To make some of this possible, we had to create our webpack configuration API, called webpack-chain. As you may know, webpack exposes a low-level configuration format, but this format isn't well-suited for merging configuration deterministically across middleware, or even across many projects. With webpack-chain, we expose a chainable or fluent API for aggregating a webpack configuration which is much more deterministic.
  2. Nov 2019
    1. When the grid is initialised, it will fire the gridReady event. If you want to use the API of the grid, you should put an onGridReady(params) callback onto the grid and grab the api from the params. You can then call this api at a later stage to interact with the grid (on top of the interaction that can be done by setting and changing the props).
    1. I'm considering this, although I'm still leaning towards not including it and I'd love to just get rid of first if it wouldn't break so many peoples tests. Newcomers to Capybara don't understand (or aren't willing to learn) the issues that all/first (and last if added) have and massively overuse them. Yes the fact that all and first now wait by default will prevent some of the new user issues/confusion, but it won't fix the non-reloadability issue.
    1. It makes sense that the incoherent render would not be committed to browser and that it would not have any consequences most of the time. But that means that you render logic must be ready to manage incoherency between props and states without crashing. E.g. a list of resource ids in props that doesn't match a list of http requests from a previous id list in the state could lead to weird situations. This is a worry that didn't exist in class components.
    1. REST and GraphQL are wonderful tools to create an API that is meant to be consumed by third parties. Facebook's API, for example, is consumed by ~200k third parties. It is no surprise that Facebook is using (and invented) GraphQL; a GraphQL API enables third parties to extensively access Facebook's social graph enabling them to build all kinds of applications. For an API with that many consumers, GraphQL is the fitting tool. But, to create an internal API (an API developed and consumed by code written by the same organization), RPC offers a simpler and more powerful alternative. Large companies, such as Netflix, Google and Facebook, are starting to replace REST/GraphQL with RPC for their internal APIs. Most notably with gRPC which is getting popular in the industry.
    1. The result of the uniform interface is that requests from different clients look the same, whether the client is a chrome browser, a linux server, a python script, an android app or anything else

      Reason of the uniform interface - requests from different clients look the same

    2. The client can request code from the server, and then the response from the server will contain some code, usually in the form of a script, when the response is in HTML format. The client then can execute that code

      6) Code-on-demand (optional) - when the response is in HTML format, the response will come in form of a script, which can be executed

    3. data the server sends contain information about whether or not the data is cacheable. If the data is cacheable, it might contain some sort of a version number. The version number is what makes caching possible: since the client knows which version of the data it already has (from a previous response), the client can avoid requesting the same data again and again

      5) Cacheable - client can avoid requesting the same data again, thanks to remembering the version number of the cacheable data

    4. In order for an API to be RESTful, it has to adhere to 6 constraints

      6 constraints of RESTful API:

      1. uniform interface
      2. client - server separation
      3. stateless
      4. layered system
      5. cacheable
      6. code-on-demand (optional)
    5. there might be a number of servers in the middle. These servers might provide a security layer, a caching layer, a load-balancing layer, or other functionality

      4) Layered system - there's a number of server between the server and the response

    6. Stateless means the server does not remember anything about the user who uses the API

      3) Stateless - server doesn't store any history/information of user's requests

    7. client and the server act independently, each on its own, and the interaction between them is only in the form of requests, initiated by the client only, and responses, which the server send to the client only as a reaction to a request

      2) Client - server separation - client and server act independently, communicating through requests (client) and responses (server)

    8. Uniform interface

      1) Uniform interface has 4 parts:

      1. Request to the server includes resource identifier.
      2. Response from the server includes enough information so the client can modify the resource.
      3. Request to APi contains all the information server needs to perform the request, and vice versa.
      4. Hypermedia as the engine of application state - the server can inform the client, in a response, of the ways to change the state of the web application.
    1. What the server does when you, the client, call one of its APIs depends on 2 things that you need to provide to the server

      2 things required by the server:

      1. endpoint <--- identifier of a resource (its URL).
      2. HTTP method / verb <--- operation to perform: GET, POST, PUT, DELETE
    2. The representation of the state can be in a JSON format, and probably for most APIs this is indeed the case. It can also be in XML or HTML format

      JSON, XML or HTML <--- most popular formats of state representations

    3. It means when a RESTful API is called, the server will transfer to the client a representation of the state of the requested resource.

      Reason REST is named as REST:

      *REpresentational State Transfer*

    4. RESTful web application exposes information about itself in the form of information about its resources. It also enables the client to take actions on those resources, such as create new resources (i.e. create a new user) or change existing resources (i.e. edit a post).

      RESTful web application

  3. Oct 2019
    1. This is useful if just a subset of the operations need the API key

      can we do wildcard paths at all?

    2. PI keys are supposed to be a secret that only the client and server know. Like Basic authentication, API key-based authentication is only considered secure if used together with other security mechanisms such as HTTPS/SSL
    1. API keys are generally not considered secure; they are typically accessible to clients, making it easy for someone to steal an API key. Once the key is stolen, it has no expiration, so it may be used indefinitely, unless the project owner revokes or regenerates the key

      hmmm... what about client-API architectures where there are no username/pwd pairs?

    2. Cloud Endpoints handles both API keys and authentication schemes, such as Firebase or Auth0
    1. Access control for GCP APIs encompasses authentication, authorization, and auditing. Authentication determines who you are, authorization determines what you can do, and auditing logs record what you did
    1. For each call to your API, user should send token with every API request and you should validate the encoded toke and either deny or send back the response.
    1. fter the forage is dry, weigh the bag and forage in grams and record the weight. Empty the forage and weigh the bag to get the net forage weight in grams. Postage scales may be adequate for weighing the forage, but the weights must be converted from ounces to grams (1 ounce = 28.3 g). Forage production in lbs./acre is determined by mul-tiplying the net forage weight (from the 10 hoops) by 10. If the forage from 10 hoop placements (10 x .96 sq. ft. = 9.6 sq. ft.) was 50 grams, total forage production would be 500 lbs. / acre.

      Hello!

  4. localhost:3000 localhost:3000
    1. Many landowners are interested in purchasing horses and other livestock to graze their property.

      Testing

  5. Sep 2019
    1. The equivalent ways in functional components using Hooks:In a state variable: useState or useReducer. Updates in state variables will cause a re-render of the component.In a ref: Equivalent to instance variables in class components. Mutating the .current property won’t cause a re-render.
  6. grazing-lands-files-dev.s3-website-us-west-2.amazonaws.com grazing-lands-files-dev.s3-website-us-west-2.amazonaws.com
    1. A preponderance of evidence approach is used todetermine which of the five departure categories areselected as best fits by the evaluator(s) for each at-tribute. This decision is based in part on where themajority of the indicators for each attribute fall underthe five categories at the top of the worksheet.

      Annotation in the app

    1. that is affected by wind-scoured (including blowout) areas 8 and/or depositional areas in the comment section on page 2 of the evaluation sheet (Appendix 9 5). Table 12 provides generic descriptors of the five departure categories in the evaluation 10 matrix for wind-scoured and

      Test

    1. The methods described in the Core Methodsvolume are part of Step 8 in implementing a moni-toring program (Figure 3). Describing the anticipat-ed data analysis and interpretation of the monitoring data will also inform the characteristics of the moni-toring program design.

      Testing the API

    1. Cow (1000 lb.) = 1.0 AUE • Horse = 1.3 AUE • yearling cattle = 0.7 AUE • sheep = 0.2 AUE • goat = 0.2 AUE

      Testing from API

    1. Wind erodes unprotected soil resulting in dust and poor air quality. Water also erodes unprotected soil and increases sediment load in watersheds and decreases water quality. Poor grazing management can adversely affect neighboring landowners.

      Testing annotation with API

  7. Aug 2019
    1. Centric web solution is the renowned best web development company.

      We have a very highly experienced and expert development team who are experts in web design & development.

      We provide various services like Wordpress web development, eCommerce web development, Wordpress theme design and plugin development, website maintenance & optimization.

      For more our services call us on +91 98587 58541 or visit our website https://www.centricwebsolution.com/.

      Our Services Are:-

      • Web Design & Development
      • WordPress Development
      • WooCommerce Development
      • Custom Web Application Development
      • Website Migration Services
      • Website Maintenance & Performance optimization
      • Website Plugin and API Development
      • Website Store Optimization
      • PHP Web Development
      • Enterprise Web Application Development
      • Laravel Development Services
      • Angularjs Development Services

  8. Jul 2019
    1. canonical registers.

      The descriptor "canonical" has been very helpful for me to distinguish this data structure from others. Have had a few people think I am talking about something biblical, but it seems to stick. Helps distinguish it from data silos and align it with the other needed components of open standards and APIs.

  9. Jun 2019
    1. URIs are split on characters `#+/:=?.-` into their keywords.

      split chars used for uri.parts parameter

  10. May 2019
  11. Apr 2019
  12. Dec 2018
  13. Nov 2018
  14. Oct 2018
    1. My hope is that it will somehow bring comments on Facebook back to the blog and display them as comments here.

      Sadly, Aaron Davis is right that Facebook turned off their API access for this on August 1st, so there currently aren't any services, including Brid.gy, anywhere that allow this. Even WordPress and JetPack got cut off from posting from WordPress to Facebook, much less the larger challenge of pulling responses back.

    1. The IEX API is a set of services designed for developers and engineers. It can be used to build high-quality apps and services.
  15. Sep 2018
  16. Aug 2018
  17. Jun 2018
    1. Raccomandazione 3.6g - Definire un modello di governance del dato e progettare automatismi organizzativi e tecnologici

      ogni applicativo gestionale in uso nelle Pubbliche Amministrazioni centrali e locali DEVE(!) fare uso di [API (Application Programming Interface)] (https://pianotriennale-ict.readthedocs.io/it/latest/search.html?check_keywords=yes&area=default&q=api) al fine di pubblicare, in modalità automatica, dati tematici aggiornati in tempo reale. Senza l'uso di API pubbliche (e documentate) non ci sarà mai un sistema di dati pubblici in formato aperto su cui poter fare riferimento per creare qualsiasi tipo di riuso costante ed utile alla società e per la nascita di nuove forme di economia. Senza API pubbliche continueranno ad esserci soltanto isolati esercizi di stile di qualche rara Pubblica Amministrazione (nel contesto nazionale) sensibile alla pubblicazione dei dati, soltanto perchè fortunatamente vede al suo interno del personale dirigente/dipendente sensibile culturalmente all'obbligo (non sanzionato in caso di non rispetto) della pubblicazione dei dati.

      Oggi (2018) l'uso delle API pubbliche nei software delle PA non va raccomandato, va imposto! Diversamente si continua a giocherellare come si fa per ora. Ma niente dati di qualità e su cui fare riferimento senza API pubbliche nei software della PA!

    1. 一开始数据源的上传用的是 -d @/home/centos.tar  这个选项,但是经过反复试验,这个选项TM上传文件不完整,800M的文件只能上传230M,反复查找问题也找不到,最终换成--upload-file选项,上传成功,且根据此镜像可正常启动实例
      官网
      curl -i -X PUT -H "X-Auth-Token: $token" -H "Content-Type: application/octet-stream" -d @/home/glance/ubuntu-12.10.qcow2 $image_url/v2/images/{image_id}/file
      
      方法二
      curl -i -X PUT -H "X-Auth-Token: $token" -H "Content-Type: application/octet-stream" --upload-file @/home/glance/ubuntu-12.10.qcow2 $image_url/v2/images/{image_id}/file
      
    1. curl -H "Content-Type:application/json" -X POST -d 'json data' URL
      curl -H "Content-Type:application/json" -X POST -d '{"user": "admin", "passwd":"12345678"}' http://127.0.0.1:8000/login
      
  18. Apr 2018
    1. we need a legal framework to guarantee at least some access to API data, at least for some people. It is certainly nice that companies start research collaborations, but these fit of course into a sanitized view on their services. We therefore need, I think, something that is able to express the public’s legitimate interest to know “what’s going on” and access to API data is, in my view, a more promising avenue than the forms of purely technical or operational transparency that are often discussed. Fair use principles, for example concerning copyright, exist in academia because there is a belief that research that is not beholden to corporate interest performs a function in public life that is worth protecting. Can we imagine something similar with API data? A legally protected means to do research into these platforms? To find a compromise between privacy and publicness, we would have to find a way to distinguish between “disinterested” research and other applications

      on APIs, data privacy, etc.

  19. Mar 2018
  20. Nov 2017
  21. Sep 2017
    1. Los proyectos listados en todas las categorías sólo se muestran en formato HTML, no hay un formato amigable para máquinas (JSON, CVS, etc) que permta descargar datos del sitio y hacerle preguntas al mismo sobre los proyectos publicados.

  22. Aug 2017
    1. Today, you’re either above the API or below the API. You either tell robots what to do, or are told by robots what to do.

      This is a great way to understand human relationship to automation. See also Vonnegut's Player Piano.

  23. Jun 2017
    1. ScienceDirect Search Enabled STANDARD view / Default 25 results STANDARD view / Max 200 resultsCOMPLETE view / Max 200 results 20,000
    1. retrieves the JSON data

      Step 2: Grabs the data from the URL...

    2. generates a well-formed search URL

      Step 1: Creates a URL to be looked at by another fuction/method

    3. To enhance that process, you could add the appropriate path to the output file name in this script, and write a shell script that runs this script and then commits/pushes to GitHub, and then schedule that script to run at regular intervals from your computer/server. I'm going to look into adding that functionality to this script, but it's not ready yet.
    1. # search for all annotations with the tag IndieEdTech and return them in json format. s = searchurl(tag = 'IndieEdTech') l = retrievelist(s) # print the title of each article annotated. for entry in l: e = Annotation(entry) print(e.title)

      I don't get it. Is this all I need to put into a Jupyter Notebook?

    2. given the annotation's API URL

      Is this specific to an annotation? Yes, I guess.

    1. How often have we not seen an SOA initiative slowed down by conflicts between service providers and service consumers on what constitutes a good service interface? On the one side a mobile developer just wants it to be simple for their particular app, on the other side the backend team wants everyone to use the same standardized service and data model.

      SOA: A stable interface for all consumers

      API: Particular API for particular needs

  24. May 2017
  25. Apr 2017
    1. JSON API requires use of the JSON API media type (application/vnd.api+json) for exchanging data.

      means to change the Accept field and Content-Type field

  26. Mar 2017
  27. Feb 2017
    1. The API uses machine learning models to score the perceived impact a comment might have on a conversation.

      Interesting,

  28. Dec 2016
    1. You can have a maximum of two access keys (active or inactive) at a time.

      Incredibly useful to have up to two access keys simultaneously. You can make sure a new key is working before invalidating an old key which may still be in use. I wish more API providers would follow this practice.

    1. a content API. Rather than getting the content through an HTML page, we can just get the raw HTML, which can be styled appropriately by whatever LMS CMS that we want to use.

      Fascinating. Who's the leading person on this?

  29. Nov 2016
    1. Mastodon.py Documentation

      Python/API documentation for the Mastodon social networking platform.

  30. Oct 2016
  31. Aug 2016
    1. API

      API é um conjunto de rotinas e padrões de programação para acesso a um aplicativo de software ou plataforma baseado na Web. A sigla API refere-se ao termo em inglês "Application Programming Interface" que significa em tradução para o português "Interface de Programação de Aplicativos".

      Uma API é criada quando uma empresa de software tem a intenção de que outros criadores de software desenvolvam produtos associados ao seu serviço.

      Através das APIs, os aplicativos podem se comunicar uns com os outros sem conhecimento ou intervenção dos usuários.

      Matéria completa: http://canaltech.com.br/o-que-e/software/o-que-e-api/ O conteúdo do Canaltech é protegido sob a licença Creative Commons (CC BY-NC-ND). Você pode reproduzi-lo, desde que insira créditos COM O LINK para o conteúdo original e não faça uso comercial de nossa produção.

  32. Jun 2016
  33. May 2016
    1. You don't eat People Food and give your developers Dog Food. Doing that is simply robbing your long-term platform value for short-term successes. Platforms are all about long-term thinking.
  34. Apr 2016
  35. medium.com medium.com