From 0c1f7802e739b4856ab6820881e9d51ec3117c67 Mon Sep 17 00:00:00 2001 From: Maciej Mensfeld Date: Tue, 16 Apr 2024 09:37:50 +0200 Subject: [PATCH] Update _posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md Co-authored-by: Martin Emde --- ...-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md b/_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md index 0bf7905..aa16e7f 100644 --- a/_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md +++ b/_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md @@ -29,7 +29,7 @@ Digging deeper, we discovered that these accounts linked to a gem with over 100, ## Addressing the Issue -This realization led us to tighten our gem publishing limitations and increase monitoring for non-malicious but unexpected user behaviors. During the cleanup, we had minor delays in gem index updates; however, it was temporary. We also took strict action against accounts solely created for spamming, ensuring they didn't disrupt the community further. +This realization led us to tighten our gem publishing limitations and increase monitoring for non-malicious but unexpected user behaviors. During the cleanup, we had minor, temporary delays in gem index updates. We also took strict action against accounts solely created for spamming, ensuring they didn't disrupt the community further. ## Conclusion and Appeal