Not the poster on the Xfinity forum, but thought the analysis would be interesting for HN (Assume many here fall into the bucket of using their own modems.) Came across this after my own internet connection started dropping 20+ times per day past few weeks. Comcast Tech said everything looks good on my connection and my best bet is just to buy a new modem and see if it fixed it.
So that’s what I used to think (Price hiding to avoid sticker shock) But now I am convinced it’s a little bit the price point but more when there is variability in the pricing, and the pricing is done by a sales team that has flexibility on what they charge you (these companies always will ask for a budget and tailor the quote to what they can squeeze)
I take it as a sign that when they do give you a quote, it’s up for negotiation and you should never agree to the first number presented.
There is variability but in my experience it’s good variability, not bad. Every time I’ve gotten “contact us” pricing I have been presented with a slide deck “this is what we usually charge for companies with your needs”, and the sales call was to allow me a chance to negotiate the price down (or eg lock in a multi year contract for cheaper.
But this is nonsensical optimisation imo. At these price points, the ability to negotiate should be evident to anyone who has bought such products before.
Thanks, proper documentation will come really soon.
All configurations are stored in motor.yml file which is automatically generated in root directory.
There might be two ways handling configurations:
1. Use git to create commits with new configurations in motor.yml and deploy/pull that git repo on the production host in order to update the configs.
2. rake motor:sync to sync configurations directly to production app host via API.
There a bit of info about configurations sync between environment here:
I switched to the Android Headspace app recently and the juxtaposition of what they're trying to achieve (meditation / mindfulness and being in the moment) with the onslaught of unasked-for notifications, sometimes when I was already asleep, was jarring. They should be a poster boy for Calm Technology, but Tech just can't seem to help itself.
Come on dude, you make it sound like these things we're catching on fire all over the place - "... the number of incidents remains small, and Tesla’s review to date points to the building receptacle or wiring as the primary cause of failed NEMA 14-50 adapters, the company has determined that a voluntary recall is appropriate as a precautionary measure.”
The gist of it being that in the former males are much more competitive, and in the latter, females are. While there are of course real physiological differences between men and women, don't discount out of hand the effect culture has as well.
There don't need to be "meetings where men gather to conspire to keep women down" for a society to have a significant biasing effect.
You do know that there are no communities that have zoning ordinances allowing 160ft water towers, right?
So there's always a variance of some sort involved if fracking is done near any residential community, but I don't think that's stopped the guy or Dick before. I still think the hypocrite card can quite validly be played here.
Seriously? IANAL or a Texas attorney either but I can read...
Page 4...Section 211.003..."The governing body of a municipality may regulate...the height, number of stories, and size of buildings and other structures"
Isn't this solved by just requiring the CSRF token on any JS get requests? (In fact, isn't this just a cross-site request forgery with a different verb than we're used to?)
I know it's only generally checked on posts, but turning it on for any xhr calls seems like it would solve any potential data leakage.
basic/digest auth doesn't solve this if you've recently used the target site any more than cookies do, because your browser caches the authentication for some time and won't ask you again.
Also, very few web applications use basic auth, most use cookies.