Are you 100 percent certain that the domain name wasn't registered before and then got on the blacklist because of prior misuse?

It's quite possible that the domain you chose was registered previously and dropped because the previous owner misused it and burned that domain. The .ONLINE extension has been around for several years now.

I am 100 percent certain that one of my domains i registered before and now I am still looking for lawyer to help me sue my government for blocking my domain for something I never commit and refusing to remove the block - just be cause they can. short .com domain! I even paid it for 2 years because I was willing to commit.

I can't be 100% sure but googling showed nothing. My site was up for almost 6 weeks with no issues. I used the domain for Apple's review process too. No issues at all.

I feel like google should be sophisticated enough to tell when a domain has expired and gone up for auction/resale?

https://www.billhartzer.com - personal blog where I've been writing/posting for over 20 years. Tell me about your project/site/app/service and I'll write about it. Always looking for article ideas.

https://www.hartzerdomains.com - personal list of domain names I own, in case someone needs a domain name for a project.

neat, we should do a "share your domain squatting business" next

I also am old enough to remember when their motto was "Don't be evil."

Which has been doublespeak from day one.

I knew larry and sergei socially when they were grad students. I completely believe that when they started that was a genuine sentiment. I wonder at what point they realized personally that that was gone

I read this as: ads have been great, and have helped to pay all content creators (even the small creators). But now, Answer Engines need certain content that's missing: and it's the largest content creators that are making deals with the Answer Engines.

What CF didn't address is how the smallest content creators are going to be "making deals" with the Answer Engines. They aren't.

One of my degrees in college was in Technical Writing, back in the early 1990s. I've always used em dashes when writing--it only make sense in many cases. And I still use them regularly, just typing two hyphens, one after the other.

Classic SERP sculpting in action. Bury the bad with a flood of the old — and watch Google prioritize what’s “fresh” by post date, not relevance. Neil Patel may be under fire from FTX for $55M in alleged marketing vaporware, but it looks like the real campaign was reputation laundering by content saturation. SEO rule #1: If you can’t clean it up, outrank it.

This suggests the attackers used a double extortion strategy: not only locking files with encryption but also stealing sensitive data to pressure victims into paying a ransom.

Pretty much. The ransom is noticeably low, however. The attackers' goal could be interpreted in several ways due to what was accessed and what was demanded.

That's been the norm with ransomware for a long time.

It's their business model.

I graduated college in the early 1990s and minored in technical writing. I started the first "Student Society of STC" back in college, and that lead to some good internships and a few jobs. Wrote software manuals and online help for an email software company that ran on the AS/400 and MVS. Had to write and code it in SGML, then that eventually moved to HTML.

In my daily work today, I still rely on all those basic principles of technical writing.

As a "long timer" so to speak, I think eventually there ended up being a decline of pure "technical writer" jobs out there, and not too many people going into the profession.

I don't think this has anything to do with Google's OAuth. This issue is literally with every single expired domain name out there. All one has to do is register the expired domain and look at all the emails sent to that domain.

Granted, Google "could" do something, but I don't think it's Google's responsibility to police expired domain names. What am I missing here?

Google promises to use a different `sub` claim for every account, even if you reuse the domain name. However, according to the talk, the `sub` claim isn't stable in normal scenarios, so developers don't use that like they're supposed to.

Google should fix the `sub` problem if the problem is on their side (and not, for instance, related to user accounts impersonation or recreated user accounts, which are expected to fail this check). Everyone integrating with Google should use the `sub` claim like they're supposed to.

Of course this approach doesn't help if a domain admin can recover the original workspace account (rather than simply re-registering the domain with Google), but that can easily be solved by not having the domain admin accounts use the domain they're hosted on.