Facebook disabled the ability for my customers to sign into my app via their Facebook account.
They had given me six days to add a Privacy Policy button into my app (my website has it, and my app's metadata has it, but apparently they require a button in the app UI itself, which I didn't have).
I told them I would add it, but I needed more time, as getting an app update out with only 6 days notice the week before Christmas is impossible (I have 5 apps that use Facebook login across 3 app stores, iOS/Android/Amazon).
They told me I could request an extension, which I did do multiple times, but the extension was not granted.
Don't mess with walled garden gangs. They have no soul, they have no mercy. The sole purpose of your existence is to serve their interests. But they won't tell.
Sorta loath to do that, because I don't want YT to stop suggesting stuff related to that channel and its general topics. I just don't need more Louis Rossmann in my life, the rants don't do me any good—possibly aside from keeping my heart strong from pumping against the pressure, I guess. But the stress snacks will kill me. I'd like the algo to take a gentle hint already, it was like a year since the last watching.
I did some digging in the innards of a Macbook Pro, years earlier, and have a couple leftover screws as a result. I think I'll leave the next endeavor to people with better hands, especially since putting in an extra hard drive isn't an option anymore.
You can remove your history of viewed videos in whole or in part. I've found that the most effective way to stop YouTube's manic obsession for any topic I've viewed once.
> we’ve heard from our partners making $2M, $5M and even $10M a year that their services are still on a path to self-sustaining orbit.
What does this even mean? "on a path to self-sustaining" makes it seem like they're not currently self-sustainable. Given the crazy profit margins in software, I find it hard to believe that most apps making millions per year are not sustainable.
I'll be interested to see how SpaceX tries to get the word out to rural Canadians once it launches. None of Elon's current companies have had to do any traditional marketing yet, but I suspect that they'll have to for this.
You can still reach them with internet marketing, people who live in rural Canada still use social media. In many rural areas there will be kind of a catch all local business that springs up and resells cable, dsl, dialup, landline, cell or whatever services are available in the community (along with offering computer and phone repair or whatever). If it were me I would reach out to these people and let them do their own local marketing, in addition to the normal Elon strategy.
I think what you're missing is that Tesla's Autopilot is not done. It's clearly labeled "Beta" when you enable it in the car.
The goal of Tesla's Autopilot is to take you from your garage to your parking space with zero input. Therefore it's exactly the same as a plane's which takes you from runway to runway.
Just because it's a work-in-progress doesn't mean it's named wrong.
> If they ever do deprecate something people have built on though they're gonna get absolutely crucified.
They do this all the time, and they get crucified every time. I built a Google Hangout App and a Chrome App, both of which were platforms eventually shut down.
This is where the meme came from, and it's why I personally stopped building on top of Google products. A 1-year deprecation policy is no assurance to me if I plan for my app to live longer than that.
Their approach to things like GCP is very different than their approach to those other areas of Google. But they don't separate their branding or unify their deprecation attitudes enough to avoid cross-org-chart reputation damage like this.
So basically they screw you over on either medium or hard, and according to you the real problem is them not telling us clearly whether or not we receive the medium or hard screw over option.
By the way that GCP is so full of loopholes where Google can get out of its obligations its laughable. So it's not even that clear cut that the GCP is really a better alternative.
And even when it turns out to be legally sound, when stuff like this happens, who's going to sue google over it? Nobody, and they know it.
Oh, courts routinely give binding weight to words like Google's deprecation policy uses, and any large megacorp who is sufficiently badly impacted by a legalese violation (though SLA issues and deprecation issues are two separate things) wouldn't be scared away from a lawsuit by Google being big. I can imagine EU regulatory action or a class action lawsuit as other possible mechanisms.
But as I say in another comment, the contract is less important than both trust and reality. Keep in mind nobody focuses on how AWS doesn't even have a public deprecation policy.
I'm right there with many people in this thread in agreeing that Google has a trust problem, due mostly to real perception issues stemming from Google's habits outside GCP, which can and do impact people's perceptions of what they'll do with GCP.
The reality of what Google has done and will do with GCP, though, is pretty good. Sure they do sometimes deprecate things in ways Amazon never would. But not nearly as often or as abruptly as they do on the consumer side - that would be commercial suicide - and they do other things better than Amazon. Tradeoffs.
> The reality of what Google has done and will do with GCP, though, is pretty good.
No. It's just words. Actions speak louder than words. Googles' actions in the last couple of days spoke pretty loud. No amount of words will change that.
I haven't worked for Google since 2015, and I never worked for their PR department. I was just a rank-and-file engineer (and a rank-and-file tech lead for one small team near the end of my time there). If I worked for Google PR, my comments throughout this thread would have far less criticism of the company's messaging and branding than they do. :)
I'm still a fan of GCP as a suite of products and services, as much as I recognize many of Google's organizational failings and disagree with plenty of their product decisions in other areas of Google.
Google (including GCP) has been bad at external communication as long as I've paid attention, and that includes external communications around incidents. What actions are you referring to, beyond poor and confusing communication (i.e. words) around what is or isn't broken or fixed at what points during the incident? That's most of the problem I'm aware of from this incident.
With that said, part of the reason people notice GCP's outages more than AWS's is that GCP publicly notes their outages way more than AWS does. In other words, among the outages that either cloud has, Google much more often creates an incident on their public status page and Amazon much more often fails to.
My "reality of [...] GCP" comment was about the bigger picture of the cloud platform offering, not any one specific incident.
I recently had a client ask me to pay them with Transferwise. It was a horrible experience. After weeks of trying to get it to work, even with the help of support, we eventually gave up and used bitcoin instead.
The Transferwise website was horrible. It gave error messages and kept telling me to fill out some field that didn't exist. After sending screenshots to their support team, they just sent me back links that didn't work.
After several back-and-forths with support they eventually fixed that issue, but then on a later step the website told me to upload "the documents" and gave an upload control. I carefully read every piece of text on the website, and nowhere did it explain what documents it was asking me to upload. It wouldn't let me proceed until I uploaded "the documents". I sent screenshots of all this to the support team and they didn't know what documents I was supposed to upload either.
Eventually support helped me fix that, and I got to a later step, where it asked me for the username and password I use to log into my bank. I am not comfortable providing this to anyone, so I refused. This was the last straw that finally led to me giving up at using Transferwise.
I'm pretty sure they use plaid for verification, who also do this. It's for instant verification; you can choose to do the old school two-deposit verification too.
I've sent money with them a few times from UK to South Africa and had no problems.
The biggest issue with this remitters is they have hidden vetting processes and can't tell you why you don't meet their criteria because any smart fraudster would adapt accordingly. Unfortunately too many people get accidentally caught in those systems
I use transferwise and didn't give them my bank credentials. Question: which country are you in and which country were you sending to? I imagine this sorry of thing is both country specific and possibly bank specific.
The pain was figuring out the exact recipient bank account name in Japan but that's mainly Japan's fault.
I really wonder why they arranged for your bank credentials. I've always been able to just wire transfer wise in the states and they wore in the recipient country. Pertussis there's some regulation in Cyprus about transfers?
Most auto production lines don't need EV-size batteries. The post above specifically says batteries are the bottleneck, so it isn't really evidence that something is "terribly wrong"
Reddit just recently announced they're no longer open source [1]. The last source dump could still be used, but I think they choose not to just out of a statement that they're against the Reddit corporation.
They had given me six days to add a Privacy Policy button into my app (my website has it, and my app's metadata has it, but apparently they require a button in the app UI itself, which I didn't have).
I told them I would add it, but I needed more time, as getting an app update out with only 6 days notice the week before Christmas is impossible (I have 5 apps that use Facebook login across 3 app stores, iOS/Android/Amazon).
They told me I could request an extension, which I did do multiple times, but the extension was not granted.