Clerkle

[Title] ... or Mulch / Mull browsers.

If you can find a merino wool onesie, make sure it has elastane and polyester, otherwise the merino wool will break and rip eventually.

Bump, for more help.

That leaves Reddit as a decommissioned sewage treatment plant turned into a bum fight squat haven.

Still, you continue to insist inaccurate and wrong paraphrases of my statements. I absolutely do not appreciate it in the slightest.

There's no lockout. It's a logged out profile.

Thanks for the tips, but I'm way ahead of all that. I'm not leaving this ever, even after it becomes rectified. Google is far too corrupt to hold accountable myself. The only options are either class action, and/or civil litigation, and/or real tech support via security department heads. In all likeliness, California's Newsom could very easily smooth this over. I know a guy who's in California working at the LA Times too.

I have more than enough to substantiate my ownership of the account, and full records of exhaustive media files spanning the entire Google "support" experience.

I'm fixated exclusively on rectification through legal recourse. The punitive damages incurred won't be ignorable.

I won't ever let intellectual property theft take advantage of me, especially by a sellout entity.

If you can in fact effectively get involved, then get involved.
Otherwise, don't at all, especially if you're a badged Google community forum advisor. Those scripted "community" responses are all totally copy-pasted completely unhelpful trash.

========.

Your notions in italics.

I live close enough to a Google office that if I needed to I could go to a physical location.

They don't have account recovery tech support. There is no such department. Ever tried their public Palo Alto number? It's a joke. They adamantly refuse to talk on the topic.

I also use a physical 2FA device specifically because I want to be in positive control of my ability to unlock my account in the event that I get locked out.

People lose those eventually or else those become physically damaged due to the travel nature of it. I had a better one the size of a smartphone, and it had a full touchscreen menu system and password system itself. It's permanently MIA, just like yours will be someday too. But hey, wishful thinking is a great vulnerability to marketers. Enjoy the toy. It'll own you someday.

I took the steps I did to secure my account and create a 2FA backup in the event that my device is lost or stolen.

What is this? Pearls before swine?

Now you don't go into any detail whatsoever even in your comments about anything of relevance that would help us help you.

You're intentionally ignoring my list of proof of my account ownership. You're being antagonistic.

You don't spell out how the system works in your country, you don't explain what you were told (the specifics). You have posted none of the chat history or anything proving you've even contacted Google about this.

Right. That's my personal private material that can be used to identify me by employees within the company's access to those conversations. You know that. Yet, you're insisting documents aught to be published right here for you to see.
Would you like to identify yourself right here. Hmm?
Would you like to post your heated emails and link your frustrated tech "support" phone calls for everyone?

You locked yourself out of your account.

Again, you're intentionally ignoring my post details. There's no lockout. The 2FA device is gone. That's not a lockout. It's an extremely major complication.

The login verification text goes to my GVoice number for that account. I keep tabs on its voice messages. Its' voice message system recently became nonresponsive to calls, but that account is still intact.

I'm not apathetic. Someone who didn't care wouldn't have bothered to comment.
Your rationale is very concerning. You don't care. You're pushing this your directions anyway.

If this is how you talk to the call center techs I am not surprised that you haven't gotten the help you requested.

What a sheltered and homogenous blurb of spineless privileged nonsense in a world of extreme social injustice. Don't you even know of anyone who lives in a corrupt nursing home?

If there was something tied to that account (a credit card or something) that might help you. If you could report the phone stolen, a police report would be helpful because that is an official document from a local government agency who would validate who you were. It would be something to provide to Google as proof of the validity of your claim.

This looks like an attempt to propose an idea. Alright, something to talk about. Unfortunately, a police report is not proof of the claims presented in the report. It's a witness of a statement, but it's not even simply verified as much as a mere notarized statement, though it presents verification of an ID and profession of a claim.

On that note, Google has access to my ID in my Drive account. They see it. I had those dismissive and homeland Drive guys on the phone while they were looking in my Drive folders but skirting away from clearly admitting visibility in any unsavory context. But I got it out of them. They spinelessly care more about their job staying off an internal radar than positively impacting a life. And that was an otherwise standup guy too. I have his name and that chat conversation. Tools.
Besides, those kids in the Philippines have my ID. They've done nothing to produce results.

Making a second account and using it to explore further options might be beneficial to your situation. Making a second account and signing up for a new Google voice number would allow you to take screenshots of what you are seeing on your end and those might be helpful for people trying to guide you to getting the help you need.

When I connected to Google One personnel . . .
Think about it. You know that requires an account, so you know I did that.

What are you thinking here?
Are you thinking a phone conversation via a GVoice number directly with some cubicle kids in the Philippines is going to convince their complete lack of access to anything to somehow magically produce the "tools" they say they "don't have" to then authorize an account recovery approval when they refuse to talk about account recovery in any terms outside the prefab and unsupportive Google Help pages? What do see happening with GVoice via an alternative account?

Screenshots? You've through this through, right?
Screenshots of the IP address of the Chromebook that was once registered with that limbo account, right? And especially with the IP displayed next to hopefully unrefreshed browser tabs showing Drive contents of the limbo account, right? Is that what you were thinking? And maybe right next to the Security Codes from that limbo account? All this while logged into an new alternative Google account in the Chromebook?
Are we thinking this through objectively?
Any other ideas there?

Either way though I'm not sure how you expect us to help you besides giving the advice we have given? I'm assuming you were hoping to get the attention of Google employees. The problem with that is this is Lemmy, we aren't reddit. I seriously doubt there are employees monitoring this place. If you were to try reddit or Twitter you might have better luck. Lemmy doesn't have the user base to justify employees of big tech companies to spend working hours here.

Right. Google has no clue what the Fediverse is. They're internet architects, right? Yeah, they have no idea this space has been established and populated in rejection of the hijacked Reddit subforum, especially with both these donning its brand name.

Are you still in college?

And I'm being taxed by someone who claims to have read my citation of experience both with 1) the account recovery security AI at the recovery login page, and (2 extensive exhaustion of third-party, overseas Google One tech "support", both over the phone and through so many emails they don't group to the service ticket — which after thorough exhaustion of over thirty of those disconnected proxied script-followers, that extensive observation has enlightened me as to the foundational corruption on which that entire subcontracted business model is designed — and, yet, who insists I've not exhausted "official channels".
You refuse to see my due diligence?
Likely, you insist on misinterpreting it into something you probably think shouldn't be considered outside standardized routes.

You know Alphabet, Inc is ridiculously corrupt and worse, yet, you refuse to expect that outcry as inevitable, commonplace, and beyond necessary.
So perhaps you'll grasp my correctness in finding your wrongful interpretation of "you're trying to go through other than 'official channels'" as quite unarguably unhelpful and also wrongfully accusational. I stated I exhausted the "official channels," yet you want to imply you yourself are entitled to audacity to gaslight me as though to imply I did not do the things I stated I did in fact do? Maybe you prefer to excuse injustice?

Google is basic. The issues it creates have rippled into catastrophic tsunamis of hoards of unfortunately-annexed innocent users. Those issues echo harmonics throughout those call centers. So it takes an apathetic, complacent, and caustic sadistic employee-slave to continually discriminate against paying customers by finding ways to use the subcontracted company policy against callers instead of proactively and ambitiously search out facilitative Google agreement terminology that could, can, and should be demanded one their end to fully rectify a customer's naive and undeserved mishaps that are all too often directly influenced by Google's inadequate onboarding prompts which do not ensure proficient user-end competence.

It's very clear Google wants the mishaps.
The communications conglomerations throughout the corporate tech industry are deliberately wrought with convoluted inefficiencies that effectively present and aesthetic of support.

Perhaps you aren't experienced and perceptive enough to recognize a lie when a Palo Alto's headquarters of a major world corporation's third-party, non-homeland subcontracted call center overseas is staffed by scripted employees who wrongfully identify as Google employees when Google or Alphabet, Inc is NOT stated on their paychecks.

I encourage you, instead, to imagine bright ideas instead of dwell and emphasize on defeatism. I have a sense of urgency about this that I value in terms of intellectual property, documented memories, social connectivity to family, loved ones, and professionals. To me, that's a life of opportunity spanned over twenty years of user data submission to Google. I was naively-trusting of the cool-aid, and I even evangelized it, up until the day I discovered Google refuses to listen to 2FA mishaps they promoted into such devastating quantities. I see clearly now, and so should you.

Further, instead of wasting effort points on attempts to qualify a checklist of basic approaches I've completely surpassed myself, perhaps it can be clearly read in my notes of my fulfillment of the "official channels" that this post is evidently not nearly an initial strategy, so, again, you're discrediting my dynamic experience insultingly.
I carefully worded the post title because that's the exact level I've reached as a worthy ambition.

• "Some possibilities I can imagine may be ___________,”.
• "There's a slim chance that maybe _______, but it will need to be presented with substantiation of _________, which may be possible via ________ . . . " or
• Similar fiercely optimistic routes.

===============

If you dare to disagree, I challenge you to study the Google Community Forum's hoards of similar reports. If you still want to gaslight, I strongly encourage you to call your cellular network provider's customer support department about a significant technical issue with their service you have experienced. Really, everyone who pays for lucrative technical services should absolutely do this, even as a primary exercise in the shopping process. I encourage at least twenty to fifty of those calls, all very closely considered for recognition of systematic behaviors and recurring default language. My challenge to you is to do whatever it takes to get the issue permanently corrected. With that goal, the objectives are to closely observe the recurring experiences imposed on the support-seeker all the way through to successful resolve of the technical issue. I guarantee everyone will come away with more questions and greater concerns than that of going into the process. Notate and record as much of the runaround specifics as possible because it will be realized it's programmatic and even socialized within the employee culture of that workplace and occupational field.

You'll find the solutions often necessitate a juxtaposition requiring your own ingenuity, resourcefulness, and fiercely creative optimism of alternative exploration far beyond their default response models in interpersonal communication with the "support" personnel to get them into candidly honest human-to-human communication about the deficiencies in their approach models — to fully acknowledge and consider honest ideas from you, not the "fully trained" tech "support" personnel. They won't provide the possibilities within their reach unless you gain their understanding that collaberative extensions to coworkers, other departments, "higher-ups" as they like to call them (since they often also like to wrongfully claim that there are not any management teams in place), and also conjunctive implementation of formal complaints and grievances simultaneously in effect by that point are necessary.

At that point of obvious negligence, dismissiveness, or incompetence, it's my hope and encouragement you'll recognize and understand that you will have intimately discovered the haphazard nature of economics-based international corporate business models and the deep ground-level deliberate inefficiencies driving dysfunctionality throughout economies, and certainly throughout your own user-end and customer experience.

Then I strongly encourage you to do the same diligent pursuit with a better phone company. And another, and another (policy shopping if necessary), calling multiple subsidiaries and all the major companies until you've come to recognize they all follow the same monkey-see-monkey-do act of systematic, policy-excusable discrimination disguised in superficial conservative politeness, programmed employee training models, limited and irrelevant scripted responses, refusal, denial, unwillingness, and administrative office tools that enact dead-end runarounds into an inevitable annex.— such as redirects into unidentifiable disconnects caused by the discriminative call moderators.

I've done it enough to see it in oversized tech companies and several of the large tech companies. Midsize tech companies provide the best customer service while they still provide unadulterated products, services, and features and want a following. In the early 2000's, all the major companies excelled in customer service until they prioritized lucrative economics models over the inclusive startup ethics. Then it's all about By that point, I think you'll be ready to attempt Google One's personnel to recognize a terrible reality running rampant worldwide.

Thanks for the heads up.

I really appreciate these suggestions. Thank you.
Since you mentioned alt-grains, I'll admit I'm more interested in leaner "ancient" alternatives to rice, but sometimes I still test my glycemic threshold with brown rice variants; basmati and jasmine.
Zojirushi has been recommended to me before, so this is starting to ring true. Your stovetop notions are hands down agreeable. Thanks for introducing me to the hob top. Smart!

That's nearsighted. Do you wear glasses? Do they give you headaches?

Not a complaint but a question based on the fact. I wasn't complaining, but you very much so did to me.

You're wrong. You're not trying to help anyway, so there's no point in justifying myself to you. You shouldn't even be commenting.

Looks like I'll be learning about bridges.