341–350 of 516 posts
Earlier quoted context omitted.
Do you not pay for support? It starts at $150..
The idea of having to pay extra to talk to them about their screw up is pretty laughable.
I like the fact I can pay one price for self support and another for 15 minute resolution. Why force people to pay for support if they don't need it?
Earlier quoted context omitted.
I pay for G Suite and basically the only thing anyone uses is Gmail. I don't have hard proof but I feel that all of my emails from my domain never go to spam. I one time had to use Godaddy's email system and ALL emails went to people's spam folder. It is like Google makes you pay for email or your emails won't get delivered properly. Maybe it was Godaddy's mail system's IP that was blacklisted but I think you have to…
Did the sender domains in question have SPF records at any point? SPF is essentially a self-maintained whitelist. Blacklists are public and searchable. Something to check after dealing with an infected machine, for example.
Ironically, commercial spammers have the best SPF records. And DKIM. And all the other goodies.
It's like going to a pump that counts two gallons as one for two years, pretend you don't know any better then have the nerve to ask the owner for a refund after the meter is fixed.
I believe James is working on a solution/work-around for everybody, I chat with him occasionally and trust him, so I still encourage people to keep using Firebase. And that is coming from me (I work on gun, an OSS alternative with graphs that you can self host - https://github.com/amark/gun), so while I have an incentive to get people to use gun, I have to keep plugging Firebase because they are amazing (I don't say this about everyone, as I have said pretty harsh words about other database systems. But there are some that deserve legitimate respect, like Firebase, RethinkDB, and others).
Earlier quoted context omitted.
I think it's shitty. But it's also avoidable. But to avoid it, you generally do research ahead of time. And/or be willing to actually walk away from your 'investment' on their platform and start again somewhere else. In the OP case, they didn't sign up with google in the first place. It's doubly shitty for them, because they didn't ask for this, and could not have known in advance that google would end up being the s…
Sure but voting with your wallet isn't, as mentioned previously, always an option for various reasons. Shouting from the roof tops is little recourse, I agree, but if nothing else it can be cathartic. I don't think that should be discouraged.
In the very short term, agreed - it doesn't do much good. But shouting from the rooftops internally (at client, management, stakeholders, etc) may do more good in the medium term.
Pricing mistake 101: You never ever change those old plans. Instead, you grandfather them. Especially so if you're still a young platform and have most growth ahead of you, the "loss" of not charging the new - and supposedly higher - pricing is gonna be trivial 2 years from now, with lots of new projects coming in. But the NPS hit from pissing your most loyal users off and the subsequent damage to your growth curve a…
> the Amazon guys will leave money on the table What? they're a business like any other and they're not interested in minimizing profit, there's lot of thought that goes into their pricing and you can be sure that your opinion and trust is an outcome of their strategy to make more money.
Earlier quoted context omitted.
In Sweden we have at least one bank that has e-cards where you can set up a new card for each transaction. You decide how long it is valid in months and for how much total and recieve a unique card number and ccv. I have been using this at least 15 years for payments online. You set it up, make the payment and then immediately close the card again if you want to be extra safe.
what is the bank name if i may ask?
Did a Firebase team member already comment on this? In a few hours Google will present some new Firebase features at io17, and I would expect them to avoid bad press now as much as possible...
Note that this was posted to HN around midnight Pacific, so it's quite possible nobody from the Firebase team had seen it yet.
Earlier quoted context omitted.
In Sweden we have at least one bank that has e-cards where you can set up a new card for each transaction. You decide how long it is valid in months and for how much total and recieve a unique card number and ccv. I have been using this at least 15 years for payments online. You set it up, make the payment and then immediately close the card again if you want to be extra safe.
what is the bank name if i may ask?
Reminds me of getting Bait-and-Switch'd by Google App Engine in 2011. From 10's of euros to 1000's. > They have no phone number to contact, no way to dispute this other than email — which they have ignored us for over a month now without replying to our continued requests. Trapped. Doomed. We have no further options. Sounds like Google did a great job with Firebase. Definitely gives you that Google-feel of unresponsi…
I learnt this lesson the hard way. Solution: get a separate debit (not credit!) card for all cloud stuff. Make sure you only transfer enough money on to it each month to cover what you reasonably expect your bills to be (and that you can quickly top it up in hours if you legitimately need to). Worst case, if AWS or Google decide to fuck you over, let the bill bounce. This way you've still got funds on hand to deal wi…