I recently came across an article by Rory Cellan-Jones about a new technology from Jigsaw, a development group at Google focused on making people safer online through technology. At the time they’d just released the first alpha version of what they call The Perspective API. It’s a machine learning tool that is designed to rate a string of text (i.e. a comment) and provide you with a Toxicity Score, a number representing how toxic the text is. …
Improving Conversations using the Perspective API is a post from CSS-Tricks
Hacker News has a public API, and it’s great. Live front page updates, live upvote counts, live comments. Everything you want or need at the tip of your fingers in real-time.
But there’s no write. You can’t log in, you can’t upvote, and you can’t post. You can’t do anything but read. And you need writes to make a Hacker News App.
With the addition of the CURL function in N1QL, interacting with external JSON endpoints and developer APIs such as the Google Maps API has become easier. To learn more about CURL(), check out this article.
It takes a lot of work to provide a reliable API that people can depend on. Something your consumers can trust and will provide them with consistent, stable, meaningful, and expected behavior. There are a lot of affordances built into the web, allowing us humans to get around and make sense of the ocean of information on the web today. These affordances aren’t always present with APIs, and we need to communicate with our consumers through the design of our API at every turn.
One area I see IT and developer groups often overlook when it comes to API design and deployment are HTTP Status Codes. That standardized list of meaningful responses that come back with every web and API request:
There are many good things to come out of doing APIs properly. Unfortunately, there are also many bad things that can come out of doing APIs badly, or with misaligned expectations. It is easy to focus on the direct benefits of doing APIs like making data resources available to partners, or maybe developing a mobile application. I prefer looking for the more indirect benefits, which are more human, more than they are ever technical.
As I work with different groups on a variety of API definitions and strategies, one very significant part of the process I see, is people being forced to think outside their box. APIs are all about engaging around data, content, and algorithms on the web, with 3rd parties that operate outside your box. You are forced to look up and outward a bit. Not everyone I engage with is fully equipped to do this, for a variety of reasons, but, overall, the API process does make folks just a little more critical than they are with even their own websites.
In this article, we will learn WPF using Google Place API with the WPF control web browser in Visual Studio 2015.
In this article, we are going to:
Currently, many web platforms use ReactJS to build their user interfaces. Such platforms include Netflix, Instagram, Airbnb, KhanAcademy, Walmart and more. The documentation is very detailed, and there is a vibrant community of users. In addition, a plethora of ReactJS addons exists on GitHub for easy inclusion in your project for whatever functionality you are trying to build.
Recently, one of the most advocated means of creating services has been through the use of RESTful services. Before we continue, we would like to explain exactly what REST means and what criteria must be met before a service is indeed RESTful. REST was a word coined by Roy Fielding in his Ph.D. thesis meaning Representational State Transfer. It is an architectural design that relies heavily on the use of hypermedia to transmit information from one system to another. Its whole engine is based on the concept of Hypermedia As The Engine of Application State (HATEOAS). So, what constraints make a service a fully RESTful service? Some of the key constraints we would be looking at include:
There is a number of Web APIs which allow you to measure the performance of web applications:
User Timing API (access to high precision timestamps).
Resource Timing API (timing information related to resources on a document).
Navigation Timing API (timing information related to navigation and elements).
The youngest member of the family is Server Timing API which allows for communicating the server performance metrics to the client. The API is not widely supported yet, but Chrome Devtools is able to interpret the information sent from the server and expose it as part of the request timing information. Let’s see how this feature can be utilized from ASP.NET Core.
Good to speak with Andy Dearing, CEO of Boundless, about their new Suite 4.10, designed to streamline the creation of maps and applications using the Boundless open GIS ecosystem. Additionally, the company has a new software development kit (SDK) and contributions to the community release of GeoServer 2.11 for developers.
Boundless offers an open GIS solution through a combination of technology, products, and experts, to give enterprises deeper intelligence and insights into their location-based data. The Boundless platform is built upon open source technology and open APIs that generate actionable location intelligence across third-party apps, content services, and plugins for enterprise applications.