Live data from Hacker News

Fastmail breaks UI in production

twitter.com

11–20 of 53 posts

Re: Fastmail breaks UI in production

#11

Earlier quoted context omitted.

While the web UX is borked, mobile app is not impacted if you can fallback to that until they fix the web.

This doesn't actually work. The mobile app is just a wrapper around the web interface.

I thought apple didn't allow this?

Edit: apparently "hybrid apps" using webviews are allowed as long as they're not "thin wrappers" for websites and provide meaningful functionality. See also: the capacitor framework.

Re: Fastmail breaks UI in production

#12
What the hell is that with OP being so rude?

And following FastMail's reply

> Hello Andrew! Can you please contact our support team so we can look into this for you? fastmail.com/support

They say:

> Don't have time. Consider my tweet the bug report.

Sorry but this asshole behavior. Bugs happen. No need to do public shaming and being rude to the company for that.

Re: Fastmail breaks UI in production

#14

What the hell is that with OP being so rude? And following FastMail's reply > Hello Andrew! Can you please contact our support team so we can look into this for you? fastmail.com/support They say: > Don't have time. Consider my tweet the bug report. Sorry but this asshole behavior. Bugs happen. No need to do public shaming and being rude to the company for that.

I disgree. Other people were saying it's broken too. Reasonable company behavior here would be 1 tweet "we'll look into it", and then either "we reproduced and are working on a fix" or "looks good to us please contact support so we can investigate your particular issue". But there's no reason to initially make users jump through hoops.

Re: Fastmail breaks UI in production

#16
post #14

What the hell is that with OP being so rude? And following FastMail's reply > Hello Andrew! Can you please contact our support team so we can look into this for you? fastmail.com/support They say: > Don't have time. Consider my tweet the bug report. Sorry but this asshole behavior. Bugs happen. No need to do public shaming and being rude to the company for that.

I disgree. Other people were saying it's broken too. Reasonable company behavior here would be 1 tweet "we'll look into it", and then either "we reproduced and are working on a fix" or "looks good to us please contact support so we can investigate your particular issue". But there's no reason to initially make users jump through hoops.

It's in their status page and it's tagged as a partial outage: https://fastmailstatus.com/cme1fq7ej002dh0iu6z8pey4f

Personally I don't really use their web interface, but I tried it now and it all works just fine (on both prod and beta).

Re: Fastmail breaks UI in production

#17
post #14

Earlier quoted context omitted.

I disgree. Other people were saying it's broken too. Reasonable company behavior here would be 1 tweet "we'll look into it", and then either "we reproduced and are working on a fix" or "looks good to us please contact support so we can investigate your particular issue". But there's no reason to initially make users jump through hoops.

It's in their status page and it's tagged as a partial outage: https://fastmailstatus.com/cme1fq7ej002dh0iu6z8pey4f Personally I don't really use their web interface, but I tried it now and it all works just fine (on both prod and beta).

When I experienced this issue it was not on their status page, so I assume it wasn't for the original tooter either.

Re: Fastmail breaks UI in production

#18

I opened a support case at 9:04 AM EDT. So far, no response yet.

Maybe they don’t realize how important you are. This is a failure in their VIP program, imo they should expedite that over a bug that effects all users.

For what it's worth the CEO responded to my support ticket once and I felt like a VIP.

Re: Fastmail breaks UI in production

#19
post #9

I don't understand the urge to do public shaming instead of first reaching out to support. And the OP is so rude.

I don't know. I'm always confused when social media accounts ask to report issues over different channels when it's so much easier to just reply to customer and ask for additional (non PII) information there. In this case it's unlikely that this was the only or even first report about this issue. So why place the initial burden on a paying customer? If your social media is just a marketing channel, at least make that clear so i don't even bother reporting issues that route.
Post reply on HN