zlacker

[parent] [thread] 2 comments
1. smcin+(OP)[view] [source] 2023-02-03 23:23:09
Ok, but it's reasonable to suspect other users might also have had their accounts banned if it had been a systematic outage or ML hiccup, and given there's a 24hr limit to that ban becoming permanent, it's reasonable to expect an update soon as possible, even if that update is just a one-line "our status is X but we still don't know why this happened to us".
replies(1): >>nullca+Hw1
2. nullca+Hw1[view] [source] 2023-02-04 15:28:00
>>smcin+(OP)
What? no. On the flip side what if their company is convulsing at the possibility of being offline for a few days due to the issue, updating a HN post would be their lowest priority untill they find a solution. Give them a break, OP owes us nothing.
replies(1): >>smcin+MHm
◧◩
3. smcin+MHm[view] [source] [discussion] 2023-02-10 07:01:27
>>nullca+Hw1
Noone said it was their highest priority. But given that HN has a daily stream of horror-stories/complaints from SaaS/cloud/payment users, it would be unreasonable to expect us to wade through them if we don't at some point get a brief follow-up saying what the outcome (and possibly the root-cause) were, and in what timeframe, and how to avoid/fix this for other users, or else which alternative companies to use.

And to requote the OP back to you like I did above, given that customer support told them there's a 24hr limit to that ban becoming permanent and tried to help them get it resolved before then, in this case it was in fact entirely reasonable to expect at least a one-line update within (in this specific case) a day, since either way the outcome would be known.

And in fact here's the OP's followup post: https://news.ycombinator.com/item?id=34721870

[go to top]