API improvements

In both of our APIs, LiveFeed and Search, we truncate certain post’s summary field for stability and performance reasons. It was recently discovered that the truncation had two problems. The first, which would leave undesired HTML entities in the document under certain circumstances. The second, which could potentially cut off the last word when truncation occurred.

On 2016-10-11 we rolled out a fix which remedies both of these flaws. You should not find HTML entities in the summary field anymore (please tell us if you still find any!) and the last word of a truncated summary should be left intact. Note that the vast majority of posts are not, and will never be, truncated.

Another recent improvement is also related to undesired HTML entities. The tags field, only present in Search API, should not contain HTML as of 2016-09-08.

TLS 1.1 and TLS 1.2 fix

Due to a misconfiguration in our retrieval system we have not been able to ingest feeds using only the TLS 1.1 or TLS 1.2 encryption protocols. Since most encrypted sites still serve TLS 1.0, or even SSL 3.0, the misconfiguration has most likely not been noticeable in our ingestion statistics, but we expect to see more sites deprecating older protocols in favor of TLS 1.2.

The configuration has been updated and we are all feeling a bit more secure.

.NET client for Search API

We have published a .NET client for the Search API, grab it from NuGet.

Java client for Search API

We have released a new rewritten version of our Java client for the Search API, get it now.

Node.js client for Search API

A first version of our Node.js client for the Search API has been released!