Comment by qazpot
5 years ago
> Finally, and most importantly, we can remember that this is how DigitalOcean treats the open source maintainer community, and stay away from their products going forward. Although we’ve enjoyed using them for hosting the WHATWG standards organization, this kind of behavior is not something we want to support, so we’re starting to investigate alternatives.
> Another promising route would be if GitHub would cut off DigitalOcean’s API access
I am pretty sure DigitalOcean is not doing this in bad faith or try to damage open source community but the author seems to be out for blood for what seems to be an oversight on the part of DigitalOcean, suggesting that this is a how DigitalOcean treats open source community and one should boycott their products.
DigitalOcean isn't intentionally damaging the open source community - they are just indifferent to the harm they're causing. They are fully aware of the spam problem and refuse to take measures to fix it because it would be too much work for them: https://twitter.com/MattIPv4/status/1311391587793014784
That's not an "oversight".
Potentially the issue may have more traction now: https://twitter.com/MattIPv4/status/1311421301291200512
I don't think that indicates any more traction. He already indicated in another tweet that he doesn't hold any power regarding the event: https://twitter.com/MattIPv4/status/1311395478244818945
Agreed... the author is being premature to blow this up.
The contest seems to be in good faith but had unintended consequences. Regrettable, but it happens. Give them a chance to fix it before trying to ruin their day over it.
It was a problem last year too. Even the person running it for DO suggested making it opt in.[1]
[1] https://twitter.com/MattIPv4/status/1311391325443555328
> the author seems to be out for blood
Sometimes a really over-the-top reaction is the only way to get the attention of a large organization.