shredzone.org

I have just released flattr4j RC3. It supports the latest changes to the Flattr REST API: searching, user activities and auto submit URLs.

Because of the number of changes to the Flattr REST API, I decided to insert another release candidate before v2.0 final. Please test this version, and report any issues.

Along with a thrilling developer challenge, Flattr has just released their latest v2 API and added a few more features.

I am trying my best to release flattr4j v2 pretty soon, so you can even use the new features if you plan to use flattr4j for your developer challenge submission!

This release candidate provides a method called Thing.merge(), which can be used for conveniently modify Things by a Submission object. The HTTP connection has been improved. It now times out after 10 seconds (to avoid deadlocks on broken connections) and uses gzip for compressing the results from the Flattr server.

A still unaddressed issue is the missing support of client based authentication. Besides that, the RC2 is already feature complete, and it is likely that the next release will be 2.0 final.

A first release candidate for flattr4j v2 is available. It covers all documented calls of the Flattr API v2 beta, and it has been tested thoroughly.

There were minor changes to the API, most of them to make flattr4j easier to use and to better support migration from flattr4j v1. I will try to keep the API backward compatible from now on.

Note that the Flattr API v2 does not support "Client" authentication (yet?), so if you need it, you should stick with flattr4j v1 for the time being.

A first beta release for the new Flattr API v2 is available as source, maven package and for download. The Flattr API v2 is a major change. It uses OAuth2 and offers JSON for data transportation. To reflect these changes, the flattr4j API was changed in many parts as well. However, if you use the basic functions, there shouldn't be much for you to change. There may be some more minor API changes until 2.0 final.

Have fun trying out the new API. Your feedback is welcome!

Flattr has just published the Flattr API v2 BETA.

Since flattr4j is not an official library, I had no early access to the new API's documentation, so I will need to evaluate the new API now, and find out how to integrate it in flattr4j in a way that is as downward compatible as possible. Changes will be committed to the trunk of the flattr4j repository. Eventually, there will be some flattr4j-2.0-beta releases and a flattr4j-2.0-rc release. Hopefully, when the official API v2 leaves the beta stage, there will also be a stable flattr4j-2.0 release available just in time.

Development of the current flattr4j v1 is continued in case there are bugs or changes to the old API. For this purpose, the current source code has been branched.

This release improves the compatibility with Google Calendar for recurring appointments. Thanks again to Kenneth Wheeler for investigating!

After a lot of frustrating struggle with Continuum, I finally deleted this POS and installed Jenkins instead. I expect that the nightly SNAPSHOT builds will be more reliable now.

This release fixes an issue with datebook.mdb files containing weekly appointments with more than one weekday.

Thanks to Kenneth Wheeler for reporting.

This release brings support for old notepad databases. If you tried to convert your npadDB.PDB but were unable to open some or all of the PNG files, please try again with this release.

Thanks to Patrick Brennan for providing such a notepad file.