VanguardLH,

And for the off chance that you simply have no clue : session cookies -
as part of the "functional cookie" group - are excluded from the GDPR
requirements.
....
Session cookies are [supposed to] get erased when the web session exits.

And that has .... what to do with GDPR consent ?

Mind you, *you* where the one who started to blabber about "have to consent
to allowing them to create a cookie for your web session". Which is
bullcrap.

[Snipping some "water is wet" stuff about how "session cookies" work]

The point of user intervention to grant consent really has nothing
to do with the content of the session or expiring cookie file.

Bingo.

So, what was that "allowing them to create a cookie" all about ?

They are used as a means of tracking visitation, and whether or
not to interrupt with a consent prompt.

Hmmmm ... So your stance is that I should re-enable long-lived cookies, so
Google can store an *absolutily unreadable* cookie on my personal 'puter
that, the next time I visit, tells them they should not store tracking
cookies on my 'puter ...

.... accepting the fact that I cannot read that cookie *and* that someone,
Google or not, could "forget" *not* to put an tracking cookie on my 'puter
and have it live upto-and-beyon my next visit ?

I don't think so.

Kiddo, my choice is that they, apart from session-bound short-lived
"functional cookies" store /absolutily nothing/ on my 'puter.

I've got a cinema in my town. It doesn't expect me to carry a "no
admittance" ticket around so they can check and by it stop me from entering.
I'm sure that Google can come up with a similar system.

IOW, the absense of a consent cookie means they do not have consent.

It *can* be as simple as that. But that doesn't give Google "a foot in the
door", now does it ? So it won't happen ... unless they are forced. I
can only hope that GDPR turns out to be a bit more solid than DNT.

Regards,
Rudy Wieser