v.2.0.1.0

Switched to Edge-based embedded browser for authentication and human verification. This solves a problem of not being able to pass Captcha verification when logging in.

Changes compared to the experimental v.2.0.0.0-a:

• batch mode is fully supported
• restored support for Windows 7 SP1 and Windows 8.1

v.0.5.5.0

Updated submissions list extractors after a site change.
This is temporary release that still relies on IE authorization, and is mainly intended for existing app users. Primary authorization method is likely to fail if logged out for any reason, with the only alternative currently being the use of cookies extracted from browser passed in FURDOWN_COOKIES environment variable (see the bottom of the README.md).
Experimental version that uses Edge for authorization can be found here.

v.2.0.0.0-alpha

Experimental version. Implements authorization using of a modern browser instead of an 11 years old IE.

Requires Windows 10 or 11, as Chromium-based browsers no longer support older versions of Windows. It may be possible to make it run on Win7 too, but that was not a priority for an experimental release, so currently it will fail even if old version of Edge is present.

Known issues:
GUI-based authorization has no effect on batch mode, only cookies provided via the environment variables work for it.

v.0.5.4.0

Fixed a bug preventing extraction of favorites beyond the first page after a site change.

Note: binary build is compatible with .NET 4.6.2 and newer

v.0.5.3.0

implements a fix for a bug preventing submission inbox from being downloaded fully when the default order is set to be "Oldest first"

v.0.5.2.0

• added support for downloading content from the submissions inbox (submissions from the watched artists);
• %SCRAPS% value is set correctly for all submissions regardless of the URL used to produce the submissions list (previously this did not work properly for favorites);
• fixed update mode related issues;
• minor quality of life improvements, including: a distinct app icon, better Win7+ taskbar progress indication, autocorrecting common issues with the URLs (leaving page number in the URL, no https://, etc.), support for legacy download URLs parsing

v.0.5.1.2

Fixes:

• addresses issues caused by the addition of a new CDN address (d.furaffinity.net)
• fix for downloading submissions with "?" in the filename

Known issues:

• updates mode will sometimes mistreat new submissions as already downloaded ones, and will add those to the database without downloading them; as a temporary fix updates mode can now only be enabled when processing a submissions list from the previous run; next major release will address this properly
• it is now possible to determine whether the submission is in "scraps" or not just by looking at its page; furdown doesn't do that yet, and will only properly tag scraps that are being downloaded using the gallery url containing "/scraps/"

v.0.5.1.1

v.0.5.1.1 is a hotfix for v.0.5.1.0

v.0.5.1.0 release notes:

• Fixed the incorrect handling of the CDN server errors (Bad gateway (502) and alike)
  Previously, if the submission page has been obtained without an issue but the request to the content delivery server at *.facdn.net has failed, one could end up with a .jpg that is actually a CloudFlare's bad gateway error page inside.
  If one has a large downloads library which could be affected by this issue, one way to find the "broken" files is to use grep like so: grep.exe -R -l Cloudfl "Z:\path\to\furdown\downloads"

• Added a way to differentiate files from scraps galleries with files from the other kinds of galleries.
  %SCRAPS% in the filename templates expand to different subtemplates depending on whether the submission is coming from a scraps gallery or not.
  There are some limitations: when downloading submissions using the IDs list they all are considered "normal" (non-scrappy) unless there is a @s attribute after the submission ID (and optional file ID) [example: 33173272#1569392719@s]. Implementing a check for "scrappiness" for individual IDs and favorites galleries may be possible, but this is currently not implemented. You can post an issue if you think this is important to implement.

• Added some advanced options to make IE11 dependency less critical

v.0.5.1.0

deprecated in favor of v.0.5.1.1

v.0.5.0.2

adapt to FA changes (new CDN server name)