You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got an email asking npmjs.com to remove the link to about-cocker-spaniels.com from this package's readme, from the maintainer of about-cocker-spaniels.com, on the basis that Google might perceive links from unrelated sites as attempts to game their algorithm, and ding their rating in response.
I am certainly not a lawyer, but in my opinion, there's no grounds on which to compel you to remove a link to their site. And even less grounds to compel npmjs.com or github.com to do the same, especially since that would require some non-trivial special-case logic.
But the request seems genuine, and was made politely, and I'd be inclined to consider it if I were you, for no other reason than empathy. Would you be willing remove the link?
If not, no worries, I've checked my moral box by passing on the request :)
The text was updated successfully, but these errors were encountered:
strongjz
added a commit
to strongjz/dockerspaniel
that referenced
this issue
Jul 21, 2022
Hi, there.
I got an email asking npmjs.com to remove the link to about-cocker-spaniels.com from this package's readme, from the maintainer of about-cocker-spaniels.com, on the basis that Google might perceive links from unrelated sites as attempts to game their algorithm, and ding their rating in response.
I am certainly not a lawyer, but in my opinion, there's no grounds on which to compel you to remove a link to their site. And even less grounds to compel npmjs.com or github.com to do the same, especially since that would require some non-trivial special-case logic.
But the request seems genuine, and was made politely, and I'd be inclined to consider it if I were you, for no other reason than empathy. Would you be willing remove the link?
If not, no worries, I've checked my moral box by passing on the request :)
The text was updated successfully, but these errors were encountered: