Technology

37573 readers

540 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

330

But with serverless you don't pay for idle time ! (jlai.lu)

submitted 6 months ago by [email protected] to c/[email protected]

49 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 6 months ago (1 children)

Sounds like they violated contract to me.

Unfortunately, I think the way to make this right under our legal system is pay them, then sue them in small claims court to get the $5k back.

Which doesn’t work if OP doesn’t have $5k in cash ready to go.

[–] [email protected] 9 points 6 months ago* (last edited 6 months ago)

Sounds like this was "resolved" on HN and CEO said this was an error, but I'm not so sure. The CEO's response seems to imply that that communication to/from service reps is true and not made up. The original post shows they have a business practice for cases like this. Plus if the company was willing to settle from their business practice of 20% down to 5% (which in this case was 15k) then that very likely isn't a decision a service rep could make, so you had some mid to upper level manager make that approval to write-off the $15k and decide that $5k was still owed to the company.

As far as I can tell the only error here is that someone posted about it.

Not to mention the CEO's response from HN just says this shouldn't have happened on free accounts, but that begs the question of would this have been any different on non-free accounts where Netlify failed to mitigate a DDoS as advertised?