dennisgorelik | Entries tagged with google

1) Today (2020-05-04) my email client (The Bat 9.1.18 Professional) - lost ability to receive or send emails from our corporate @postjobfree.com email addresses [that G-suit handles for us].

The Bat started to return "Server reports error. The response is: 5.7.0":
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!2020-05-04, 06:18:43: SEND - Server reports error. The response is: 5.7.0 https://support.google.com/mail/?p=WantAuthError h188sm3660946qke.82 - gsmtp
2020-05-04, 06:18:43: SEND - connection finished - 0 message(s) sent
2020-05-04, 06:18:43: SEND - Some messages were not sent - check the log for details
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(Times are in EST)

2) The reason for this error is that Google [temporarily] stopped supporting "Less Secure Apps" in G-Suite (which we use to manage postjobfree.com emails).

3) This instruction: https://hotter.io/docs/email-accounts/secure-app-gmail/ is now obsolete.
"Less secure app access panel" no longer exists on https://myaccount.google.com/security page.

4) Actually, less secure access to Gmail works again, but, most likely, only temporary.
=======
https://gsuiteupdates.googleblog.com/2020/03/less-secure-app-turn-off-suspended.html
Last December, we announced that we’d be turning off less secure app (LSA) access to G Suite accounts, and that you should migrate to OAuth authentication instead. The first phase of the LSA turn-down was scheduled for June 15, 2020. As many organizations deal with the impact of COVID-19 and are now focused on supporting a remote workforce, we want to minimize potential disruptions for customers unable to complete migrations in this timeframe.
As a result, we are suspending the LSA turn-off until further notice. All previously announced timeframes no longer apply.
...
Despite these timing adjustments, Google does not recommend the use of any application that does not support OAuth.
=======

5) This is the fix for this The Bat - Gmail issue:
~~~~~~~~~~~~~
https://www.ritlabs.com/en/news/6777/
To configure OAuth for existing Gmail or Mail.Ru accounts in The Bat!, users should access the "Account -> Properties -> Transport -> Receive mail -> Authentication" menu, enable "OAUTH (using Web Browser)" and save changes. The Bat! will remove the password from the account and apply the modern authentication mechanism to send and receive messages.
~~~~~~~~~~~~~

Click "Authentication":

Switch from "Regular" to "OAUTH (using Web Browser)":

6) The Bat works again.

7) The next step - is to switch our PostJobFreeService C# code that works with Gmail over [secure] Smtp/Pop3 to OAuth.

Crossposts: https://dennisgorelik.livejournal.com/189680.html

~~~~~~~~~~
From: G Suite Alerts <gsuite-alerts-noreply@google.com>
To: {censored}[Bad username or site: postjobfree @ com]
Date: Tuesday, February 18, 2020, 10:27:46 AM
Subject: User suspended for spamming
~~~~~~~~~~
It has come to our attention that some of your user accounts might have been compromised and are being used to send spam from your domain: postjobfree.com.
The following user in your G Suite domain appears to be affected: support@postjobfree.com
The user was disabled in a way that they can be restored by the admin. Admins can also reset the user’s password.
Go to Alert Center to see more details for this alert. See also the G Suite Admin Help Center.
~~~~~~~~~~

Further investigation showed that the only activity on support@postjobfree.com -- was my own activity (my IPv6).
So I did something on support@postjobfree.com account that triggered that suspension.
Unfortunately, G Suite did not tell me what activity they consider "spamming".

I re-activated support@postjobfree.com account in G Suite admin panel and moved on.

~~~~~~~
https://www.google.com/search?q=misguided
Showing results for missguided
Search instead for misguided
~~~~~~~

Crossposts: https://dennisgorelik.livejournal.com/182968.html

About couple of weeks ago Google started to get slow with some of my uncached searches.

Here is an example:
https://www.google.com/search?q=%22on+top+of+the+new%22

As you can see, that "phrase" search took Google almost 6 seconds.

Repeat search was much faster -- it took only 0.28 seconds (because it was already cached).
Surprisingly, with repeat request, Google claims "About 333,000,000 results" instead of measly "91 results" in the original request.

Second (cached) request:
https://www.google.com/search?q=%22on+top+of+the+new%22

You can also see that while the top result is identical for both requests, some of text results and some of the images are different.

I also tried repeat requests (3rd, 4th, ...) and incognito request:
the results are identical to the 2nd request.

Update:
Another "uncashed" request took over 6 seconds to execute:
About 967 results (6.01 seconds)
"on top of a new"

Crossposts: https://dennisgorelik.livejournal.com/169258.html

Based of my sad experience with Google Drive I decided to file a refund.
I went to Google Play, chose "Report a problem", selected "Purchase is defective or doesn't work as advertised" and explained that Google Drive cannot upload some large backup files.

This is email reply from Google Play:
========================
From: googleplaynoreply@google.com <googleplaynoreply@google.com>
To: p...j...f...backup@gmail.com
Date: Monday, November 12, 2018, 7:52:28 AM
Subject: About your refund request from Google Play
========================
Hi,

We received your refund request for 200 GB (Google One), but we can't
provide a refund for this purchase because it doesn't meet with our policy.
We apologize for any inconvenience caused.

You can learn more about our Google Play refund policies here
https://support.google.com/googleplay?p=refund_policy_cr

If you need help activating or using an item that you purchased, it is
often faster to contact the developer directly. You can find developer
contact information on the app's page in the Play Store
<https://play.google.com/store> under the "Developer" section or on your
order purchase receipt.

To prevent accidental or unwanted purchases in the future, we recommend
that you turn authentication on
http://support.google.com/googleplay?p=authentication_cr or change your
password https://myaccount.google.com

Thanks,

The Google Support Team

Google Inc.
1600 Amphitheatre Pkwy
Mountain View, CA 94043 USA
========================

Yet another $29.99 went into a black hole for negative result.

Crossposts: https://dennisgorelik.livejournal.com/164862.html

Try to guess what is the title of the blog post that announces that Google+ is terminated?
In the best traditions of corporate doublespeak, Google middle-management titled it "Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+.

The Corporate Doublespeak dictionary:
1) "Sunset" - is a corporate doublespeak for "we are ashamed to admit it, but need to terminate this project in order to cut the cost".
2) "Project Strobe" - The Grim Reaper for gravely ill projects. "Project Strobe" team detects and kills useless products that suck out corporate resources.

Discussion on Hacker news

Crossposts: https://dennisgorelik.livejournal.com/162941.html

Google Cloud Platform performs with pathetic 99.8% uptime - worse than the cheapest hosting providers.
Last month we got 326 crashes out of 172,922 API requests.

Crossposts: http://dennisgorelik.livejournal.com/141323.html

Google Maps API team just sent me couple of emails.
The gist of the changes is that:
1) Going forward Google Maps API strongly encourages using API key, even from JavaScript version that runs from users' browsers.
2) "Google Maps JavaScript API" and "Google Maps Geocoding API" are going to use free quota associated with that API key.
That means Google is likely to start charging for these requests much sooner.

The prices are not high: $0.50 per 1000 requests.
That means for 1 cent we can make 20 requests.

It is a good deal for Geocoding API that we really need.
It is not such a good deal for rendering Google Maps snippets on our web site, because we do not really need them that much.

So far I plan to ignore their advise "to begin using a key for all requests immediately.", and rely on their claim that "For the time being your domain has been whitelisted for keyless usage."
I guess using keyless requests from browser should be ok. (PostJobFree already uses API key for server-side requests to Google Maps Geocoding API).

I am also tempted to remove Google Maps from jobs and resume pages on postjobfree.com
It is not obvious if having these Google Maps snippet our PostJobFree pages adds value to our users.

What do you think I should do?

From: Google Maps APIs 
To: catchall@r.postjobfree.com
Date: Wednesday, June 22, 2016, 8:43:08 PM
Subject: [Action required] Google Maps API requests are missing a project key

===8<==============Original message text===============
This email is intended for the administrator of postjobfree.com. If you are not affiliated with postjobfree.com, please disregard.

Hello developer,

Today we announced updates for the Google Maps API Standard Plan, including marking keyless usage of any of the Google Maps APIs as unsupported. As part of these changes, we are attempting to contact developers making requests without a key to advise them of possible impacts to their implementation.

We notice that postjobfree.com is accessing Google Maps APIs without a key and believe you may administer that domain. For the time being your domain has been whitelisted for keyless usage. However, API keys allow Google to protect an application's uptime and contact developers with mandatory service announcements, therefore we advise you to begin using a key for all requests immediately. 

To register a free API key for your application:
Visit the Google API Manager Console.
Create or select a project and click "Continue" to enable APIs and related services.
On the Credentials page, get a Browser Key (and set the API credentials).
Add your API key to all application requests.
To prevent quota theft, secure your API key following these best practices.
(Optional) Enable billing. See Usage Limits for more information.
Note if you have an existing Browser key, you may use that key.
For more information on these changes, please refer to the Standard Plan updates summary.

Thanks for using our APIs, 
The Google Maps API team 
© 2016 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043 
You've received this mandatory email service announcement about important changes to your Google Maps for Work product or account. 
===8<===========End of original message text===========

Update: Decline of Google Maps team

Запрос к Google "Удали пожалуйста комментарий, у нас в семье горе" выдаёт мне один результат:

Результат поиска показывает на http://vk.com/public13926253, но найденного комментария на этой странице уже нет (вероятно, удалили).

При поиске с некоторых мест (Архангельск, Michigan) этот результат не видно (и показываются результаты поиска без кавычек).
При поиске с других мест (California, Florida) - видно.

А вам - видно?
Напишите, пожалуйста, откуда вы делали поиск.

Из дискуссии отсюда

Update:
Гугл, оказывается, до сих пор хранит кэш: