|
|
|
|
|
by uid
4843 days ago
|
|
It is going to be interesting when this gets to discovery, and we find out what Heroku were saying internally this entire time about the issue. There are bound to be internal emails that discuss this issue and what to do (or not to do) about it. For this reason I can see this being settled. Perhaps refunds and an apology. |
|