Yes, my criticism was not that they're trying to make money from this, but rather that they are crippling their core product in an effort to monetize it some more.
No, they are trying to solve a problem for their customers - storing large files. They charge money for this feature. It's disingenuous to think that they are breaking their product on purpose to extract money from you.
It is not disingenuous if it is exactly what they are doing. The entire cause of this problem, and the reason it breaks so many things, is because they are trying to monetize bandwidth usage. This model is unsustainable because free users only get a paltry 1GB/month and their attempt to enforce that is what breaks forks.
If they would just stop trying to do that, then we would have nothing to talk about.
It is not at all uncalled for to criticize the way they are trying to do business, especially when it affects you as an existing customer.
Comments
I wouldn't necessarily describe a paid feature that breaks all forking for an entire repository a "value add".
If you value large file support over forking then its a value add.
Yes, my criticism was not that they're trying to make money from this, but rather that they are crippling their core product in an effort to monetize it some more.
No, they are trying to solve a problem for their customers - storing large files. They charge money for this feature. It's disingenuous to think that they are breaking their product on purpose to extract money from you.
It is not disingenuous if it is exactly what they are doing. The entire cause of this problem, and the reason it breaks so many things, is because they are trying to monetize bandwidth usage. This model is unsustainable because free users only get a paltry 1GB/month and their attempt to enforce that is what breaks forks.
If they would just stop trying to do that, then we would have nothing to talk about.
It is not at all uncalled for to criticize the way they are trying to do business, especially when it affects you as an existing customer.