The way the Rhombus / Racket community does libraries has to change. That whole package site has to change. Being a contributor on there exposes you to a steady stream of fraud garbage. There's nothing to promote the top libraries as the top libraries.
I agree that a ranking mechanism would be nice, but what do you mean by "fraud garbage"? I personally am not aware of any malicious package in the Racket ecosystem.
Ah, I see what you mean now. Yeah, that was indeed problematic. We kinda fixed this issue a while back by obfuscating emails (https://github.com/racket/racket-pkg-website/pull/88), but it doesn't help with already scraped emails. Also, the raw emails are still technically readable if one knows where to look at.
Comments
The way the Rhombus / Racket community does libraries has to change. That whole package site has to change. Being a contributor on there exposes you to a steady stream of fraud garbage. There's nothing to promote the top libraries as the top libraries.
https://pkgs.racket-lang.org/?fam=Rhombus
I agree that a ranking mechanism would be nice, but what do you mean by "fraud garbage"? I personally am not aware of any malicious package in the Racket ecosystem.
Perhaps they are referring to the fact that the package server does not hide the email of the contributor?
Not that this is a complaint worth airing on HN.
Solution: just block the alias that you use for the submission…
The email is obfuscated.
https://pkgs.racket-lang.org/
And has been for a long while.
Ah, I see what you mean now. Yeah, that was indeed problematic. We kinda fixed this issue a while back by obfuscating emails (https://github.com/racket/racket-pkg-website/pull/88), but it doesn't help with already scraped emails. Also, the raw emails are still technically readable if one knows where to look at.