Releases: tyzbit/go-discord-archiver
Releases · tyzbit/go-discord-archiver
2.1.0
2.0.3
2.0.2
2.0.1
2.0.0
Major rewrite
- The bot uses the latest version of go-archive, which is now more reliable.
- This version now requires a cookie for some operations. That can be set in the .env file or as an environment variable.
- The bot now uses /settings to configure it. These have easy-to-use buttons and dropdowns. This is also a message only seen by the calling user.
- The bot now replies to /stats (also private).
- The bot now replies with additional details by default (Oldest/newest snapshot, number of snapshots).
- A number of cleanups, rewrites and refactoring in MANY places.
- The bot responds with a looked-up link, if at all possible. Users can "Request new snapshot" and it'll force a request to Archive.org to archive the page.
- The bot now politely refuses DMs
- All responses now have a nice French Gray color.
- The bot counts interactions now as well as messages.
- Define internal globals, migrate constants over
- Example .env added
- Use session information from the bot object we already have, reducing required parameters for multiple functions
- Message is always an embed
- AutoArchive renamed to AlwaysArchiveFirst
- SkipLookup removed
- Renamed stats in consideration of the bot changing how it responds
1.0.3
- Request rearchival by default, add server-specific setting.
Background and Intent
Archive.org rate-limits pretty heavily when looking up previously-archived pages, but does not seem to rate-limit nearly as badly when requesting a page be rearchived immediately.
Previously, logic was written so lookups were always done by default and it was configurable whether or not rearchival was requested. This was done with the intention of lessening the load on Archive.org, but the result was Archive.org always responded with 429 Too Many Requests. Now lookups are skipped by default and rearchival is requested immediately.
The result should be longer wait times for the archive URL but the bot should return a URL on the first attempt much more often, and the URL it returns will be as captured when the bot was first called.