Decryptr Versions Save

An extensible API for breaking captchas

v0.2.2

3 years ago

Version 0.2.2 - The Adapted One

This version of decryptr is a minor improvement over v0.2.1. The biggest change from the last release is that we adapted its code (alongside decryptrModels') in order to support TF 2.X.

We also fixed some small bugs but this won't break existing code, so you don't have to worry.

v0.2.1

6 years ago

Version 0.2.1 - The Tested One

This version of decryptr is a minor improvement over v0.2. The biggest change from the last release is that we added tests for all major functions, meaning that the package is now much more robust than it has ever been.

We also fixed some small bugs but this won't break existing code, so you don't have to worry.

v0.2

6 years ago

Version 0.2 - The Tidy One

This release features a completely new API for decryptr. If you used this package in any of your projects before 2018-02, chances are you had the legacy version and will have to port your code for v0.2. This version has simpler and more flexible functions, but unfortunately isn't backwards compatible.

Version 0.2 includes:

  • Unified download function (decryptr::download_captcha("trt", 10, path))
  • Simpler reading (captchas <- read_captcha(files))
  • More informative print function ("A captcha located at 'path/captcha5c4d14.jpeg'")
  • Flexible classification function (decryptr::classify(files))
  • Better model training and loading (model <- train_model(captchas) or model <- load_model("trt"))
  • Straightforward decryption (decrypt(captcha, load_model("trt")))

v0.1

6 years ago

Version 0.1 - The Legacy One

If you used decryptr in any of your projects before 2018-02, chances are you had the legacy version of this package. Decryptr Legacy came with some problems when loading and classifying models, so we decided to start from scratch and develop a whole new API!

This means that the newer versions have simpler and more flexible functions, but also that it isn't backwards compatible. We highly suggest that you port your code from v0.1 to v0.2 because we have no plans to further develop the legacy version.

If you have any questions about this version, please write us an issue.