We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Lemmy appears to be firehosing all posts and comments by boosting the posts from the main account for the community (communityname@instance.tld)
Ideally, the original post should be boosted by the community account and all replies should be threaded within the original post and not boosted.
(CC: https://yiff.life/@dipolecat/110555758271482441)
The text was updated successfully, but these errors were encountered:
Reduce memory usage of rate limiting (LemmyNet#3111)
45818fb
* Reduce Vec allocations * Optimize stuff * Move embedded migrations to separate crate * Revert "Move embedded migrations to separate crate" This reverts commit 44b1049. * clippy, fmt * Shrink rate limit allowance to f32 * Initialize rate limit allowance directly * Add removal of old rate limit buckets * Improve readability * Remove usage of is_okay_and for Rust 1.67 compatibility * Add dhat-heap feature * Fix api_benchmark.sh and add run_and_benchmark.sh * Revert "Fix api_benchmark.sh and add run_and_benchmark.sh" This reverts commit b4528e5. * Revert "Add dhat-heap feature" This reverts commit 08e835d. * Manually revert remaining stuff * Use Ipv6Addr in RateLimitStorage * Shrink last_checked in RateLimitBucket to 32 bits * Fix rate_limit::get_ip * Stuff (#1) * Update rate_limiter.rs * Update mod.rs * Update scheduled_tasks.rs * Fix rate_limiter.rs * Dullbananas patch 1 (#2) * Update rate_limiter.rs * Update mod.rs * Update scheduled_tasks.rs * Fix rate_limiter.rs * Rate limit IPv6 addresses in groups * Fmt lib.rs * woodpicker trigger * Refactor and comment `check_rate_limit_full` * Add `test_split_ipv6` * Replace -2.0 with UNINITIALIZED_TOKEN_AMOUNT * Add `test_rate_limiter` --------- Co-authored-by: Dessalines <dessalines@users.noreply.github.com>
No branches or pull requests
Lemmy appears to be firehosing all posts and comments by boosting the posts from the main account for the community (communityname@instance.tld)
Ideally, the original post should be boosted by the community account and all replies should be threaded within the original post and not boosted.
(CC: https://yiff.life/@dipolecat/110555758271482441)
The text was updated successfully, but these errors were encountered: