![]() |
Quote:
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
Quote:
|
Quote:
Regardless though, it isn't really the point anymore. What we could do is try to help him out by determinng the source of the problem even though he's already moving to AWS. It may not help him or Mojo out but it could be useful to someone else here. For example, for the longest time I had issues with CORS policies, leaving me and my programmers scratching their heads. The issue in the end was with the hosting provider's configuration of our servers. No one was mad at anyone but it took longer to fix than necessary. Quote:
Regardless of the problem, a customer is upset. The first thing to do is call him, listen to the issue, reassure him or her that the issue is important, and then work together to solve the issue. When the problem affects business and cashflow, it should be beyond top-priority. The fact that he had to wait 4 hours indicates that customer service system failed him somewhere, so no wonder he's upset. Quote:
Quote:
It get it - its hard to look at pissed-off customers as anything but a drain, but there's a golden sales opportunity with D Ghost here that was missed. Cheers. |
Quote:
|
Quote:
you don't know everything sysadmin. every time there's a server thread you hike up your pants and dig into everybody. we all know more or less the same basic shit, then every tech specializes for their projects. i only focus on the specs needed for the projects i'm working on. i don't read nerd blogs for fun. maybe you don't have enough work? i haven't had a day off in about 5 years. regarding TTL - get better nameservers. i've never had a problem moving hundreds of domains in hours. maybe you're on godaddy? :1orglaugh i keep all TTL at 60 seconds :thumbsup ps your email says "agentgfy". if you are the tech in charge of gfy, you should close your account and move off-grid. this shit is horrible tech. # |
Quote:
Quote:
Quote:
Quote:
You walk in a bank, teller asks you "how long can you wait" and you bring up an arbitrary number of time you can wait. Everyone walking in does the same. Does that influence when you will be called by the bank teller? Yea, to an extent where if there's 2 of you, one puts 10 mins, other 1 hr, you'll be called sooner. But that can be 10 mins, 20, 40, 1h, 3hr, or whenever the bank decides. If there's 10 of you with 10mins, it's going to decide by their own rules. For example, the guy that they know and does business 10 times more then you do will be called before you. And so on and so forth. So, while ttl does somewhat relate to the propagation, in reality, it's decided by 100 other different factors taht you have no control of, and all of those totally ignore your little paper where you wrote how long can you wait. |
Quote:
so eh, that's not what TTL is for and usage is pretty strict in any country where i would want to do business. this video might get a little technical, but TTL does have global rules. most ISPs do follow the requested TTL and its also in the RFC. maybe not in China lol. the question is what were you doing or building that convinced you TTL have no value? # |
Is this the same guy trashing Mojohost on XBIZ.net?
What do you expect to get out of this if I may ask? |
Quote:
You also believe politicians work for our benefit and society to be better :) :) :) Cause ,i have this little bridge, not expensive... Quote:
Roughly googling, this might bring you up to speed about where you might run into issues https://serverfault.com/questions/10...-ns-record-ttl https://www.catchpoint.com/blog/dns-record-ttl And there's SO MUCH MORE going on when you include dns cache, various congestions at resolvers themselves, timeouts etc etc. So yea, write your little paper with ttl :) |
He's changed his tune quite a bit, lol...
I genuinely doubt that any company that sets you up with an Apache server, and force you to use .htaccess in 2023 shouldn't be called innovative and exciting, but hey... your monies. :) |
Quote:
|
Quote:
|
Quote:
# |
Quote:
It's NOT personal. Calling it personal is a lazy and convenient red-herring way to avoid the issues. It's called facts and business. It's not so easy to just fire a client when they pay for at least a few of your people. It also would backfire greatly if the entire industry learned that a host simply decided to shut-off a client's hosting. Not a good look, guaranteed. SO you've demonstrated why you are not in charge there and wouldn't last very long in the business world. So we think Brad did the right thing and we commend him for it. |
Quote:
|
Weird hill to die on.
|
Quote:
Quote:
I prefer to be disliked by some because I speak the truth than liked by all because I hide. But keep pretending you both know everything! Great hill to live on. A hill of willful ignorance. :helpme Also, this is an old news thread now, come on over to my new thread and throw your hat in the ring: https://gfy.com/fucking-around-and-b...os-upload.html :zzwhip |
100 support tickets
Quote:
You know how when someone in the group gets out of line in public and the people that they're with get all uncomfortable but still support them since they're stuck with them, but secretly want that person to leave? That's what you're doing here.. |
Quote:
For anyone who said, "Well, I never had an issue!" -- that's like driving a certain car brand and when someone gets into a car wreck due to a manufacturer defect, they all say "Well, WE never had any issues with that car!" - OK and what is your point? That's illogical. That doesn't mean that someone else DIDN'T experience an issue. |
Ok Karen.
|
Quote:
|
Quote:
For example, that cry with .htaccess has nothing to do with them, and everything to do with your sysadmin (or you not having one and "paying more then 4k in hosting"). And if they were in charge of your setup, pretty sure you had moved from somewhere where .htaccess was valid and did not let them know about it once they set you up on their host. In any of those cases, it's on you, or your lack of proper work force, or their knowledge. That's one. Other is your rant on aws. I'd go as far and say there's hardly 2-3 companies here that really need and could use aws and their scaling. All other are peanuts pretending they need aws scaling, or fallin for aws sales pitch. Also, for aws you better get some dedicated aws sys guys (not guy, guyS) to do your stuff, else you'll run yourself in circles with all their bullshit stuff. Don't even get me started on IAM's :321GFY. In any case, from an independent perspective (ie. mine), start of your thread looked valid. 4hr downtime, tech not knowing ticket number. All valid points that should be addressed and should not be taken lightly. Then it turned into a witch hunt, bashing whole mojo tech for no reason, threatening to move everything away, and along with your 180 after you had "talks" looks more like some type of you wanting to be compensated beyond what you should be for your moral (not business) hurt. |
https://y.yarn.co/9e98f7ee-4138-4e31...19155_text.gif
The tickets, they never stop here at MojoHost :upsidedow Hi everyone, Be kind to each other and go back to work :banana Have a great day and thank you everyone for your business. Brad |
Quote:
work is a 4 letter word |
Quote:
Quote:
|
Quote:
I appreciate that you see the validity of the initial points, thank you for conceding that at least. I don't hate you either. I see you are bringing up points and I am willing to hear them out and think about them. |
Quote:
|
Quote:
|
Quote:
chicken or the egg? # |
Quote:
|
Quote:
hopefully this gets solved, good luck to you and your company/team |
Quote:
|
Mojo host only the best
|
All times are GMT -7. The time now is 07:54 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123