Add tea.xyz spam packages impact blog post #187
Conversation
|
Looks ok, just please refer about RubyGems.org (as a service), not about RubyGems. Also it would make sense to include full tea.xyz service name everytime mentioned (sometimes just tea is used). |
|
@simi updated 🙏 |
|
Also sometimes service is mentioned in plaintext tea.xyz, sometimes as |
_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
A few small edits. What do you think about explaining that the result of these actions is probably losing access to a gem you maintain. It makes it clear that the risk of benefiting from tea.xyz is also maybe losing that benefit entirely.
I also wonder if we should clarify whether tea.xyz is explicitly allowed as long as you don't do any manipulation or spamming. Adding a paragraph to that effect would probably be a good clarification.
_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md
Outdated
Show resolved
Hide resolved
_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md
Outdated
Show resolved
Hide resolved
_posts/2024-04-14-the-implications-of-crypto-rewards-on-rubygems_org.md
Outdated
Show resolved
Hide resolved
…ms_org.md Co-authored-by: Martin Emde <[email protected]>
…ms_org.md Co-authored-by: Martin Emde <[email protected]>
PR with a short article about the recent surge in empty packages, explaining why they were there, what we did, and why ppl should not do it again.
I omitted the exact gems' names as well as account details so as not to "shame" the author.