mirror of
https://github.com/YGGverse/aquatic.git
synced 2026-03-31 17:55:36 +00:00
2.2 KiB
2.2 KiB
Changelog
Unreleased
Added
General
- Add cli flag for printing parsed config
- Add
aquatic_http_private, an experiment for integrating with private trackers
aquatic_udp
- Add optional response resend buffer for use on on operating systems that don't buffer outgoing UDP traffic
- Add optional extended statistics
- Add Dockerfile to make it easier to get started
aquatic_ws
- Add HTTP health check route when running without TLS
Changed
General
- Rename request workers to swarm workers
- Switch to thin LTO for faster compile times
- Use proper workspace path declarations instead of workspace patch section
- Use Rust 1.64 workspace inheritance
- Reduce space taken by ValidUntil struct from 128 to 32 bits, reducing memory consumption for each stored peer by same amount
- Use regular (non-amortized) IndexMap for peer and pending scrape response maps (but not for torrent maps)
- Improve privilege dropping
- Quit whole program if any thread panics
- Update dependencies
aquatic_udp
- Replace ConnectionMap with BLAKE3-based connection validator, greatly decreasing memory consumtion
- Don't return any response peers if announce event is stopped
- Ignore requests with source port value of zero
aquatic_http
- Don't return any response peers if announce event is stopped
aquatic_ws
- Make TLS optional
- Support reverse proxies
- Reduce size of various structs
Fixed
General
- Forbid unrecognized keys when parsing config files
- Stop including invalid avx512 key in
./scripts/env-native-cpu-without-avx-512
aquatic_udp
- When calculating bandwidth statistics, include size of protocol headers
aquatic_http_protocol
- Explicity check for /scrape path
- Return NeedMoreData until headers are fully parsed
- Fix issues with ScrapeRequest::write and AnnounceRequest::write
- Expose write and parse methods for subtypes
aquatic_http_load_test
- Exclusively use TLS 1.3
aquatic_ws
- Remove peer from swarms immediately when connection is closed
- Allow peers to use multiple peer IDs, as long as they only use one per info hash