Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
My personal preference is to not opt in either, as this will lead to a ton of abuse and other problems. I strongly am against the proposal by SE Inc., and since the majority of the Community has been against it network-wide I'm inclined to say we need to resist as well and not opt into this.
OpenID errors are specific to the login mechanisms used in StackExchange. This said, they've been trying to get rid of OpenID for eons. This is something that StackExchange has to look into.
Canonical wouldn't want to maintain copies of the data dumps probably. I do have a copy of the data dumps myself from when they released earlier June, I'll probably start downloading copies of Ask Ubuntu data as long as we're on strike, but Canonical doesn't have a direct relationship with StackExchange (though Canonical holds the "Ubuntu" copyright so...)
I will echo Journeyman here - as one of the Ask Ubuntu mods I'd nuke this garbage the moment I saw it, but while we're on strike it won't get erased. But yes, because of the strike this is the problem. Before Charcoal-SE (a spam detection tool) existed, this junk used to show up massively all the time too. They're joined with the moderators on the strike though, so.
@ArturMeinild and I'm actively involved in Charcoal because I run Metasmoke. The point is, with no moderators, spammers are allowed to run freely, which is the point to prove why moderators are needed and such.
@Starship-OnStrike I'm going to address this from three fronts. First, spam. Every site on the Internet that allows free registration, etc. that is even remotely forum-like will get spammed. There's no 100% foolproof counter to it. Secondly, the mod strike. One of the major things that helped fight it is Charcoal and SmokeDetector/MetaSmoke. They're participating in the strike too. The primary lines of defense as a result (using autoflagging to help fast-nuke actual spam) is gone, meaning there's no support/shields for it. Thirdly, mods are striking, so nobody to nuke the spam.
RE: Fifth Comment: to be honest, go looking in the history of answered but not accepted questions where OP just disappears. That's not specific to 'close votes' reasons. However, none of the mentioned behaviors is harassment and classifying them as harassment is not your job AND is spreading misinformation about what is actually going on.
RE: Fourth Comment: We can't control who uses their close votes, and technically speaking we can't invalidate close votes so there's no way to directly enforce what you're asking about. Additionally, gold-badgers for the tags on the post are able to single close-vote just like mods can. There's no way to filter/control that. While I agree in principle, enforcement is a different issue.
RE: Second and Third Comment: It's trivially easy to get things reopened once details are provided. Just because reviewers use their close votes doesn't mean that's a blocker for posting because it can always be reopened once details are available. Simply flagging a post for mod attention is sufficient to get it re-reviewed, and you're more than capable of casting a reopen vote (it has its own queue!)
RE: First Comment: And that's a problem, why? That's not being patronizing, because "Ubuntu 20" and 'Ubuntu 22" are in fact Core releases. 22.04 and 20.04 are not.
@Chelmite I'm going to close this here, but you should really post this on Meta.SE rather than a site about an Ubuntu Linux distribution's meta. Since you say this happens on every screen or every site/page/etc you need to talk to Meta.SE really. Also, if you browse in privacy mode it will never store cookies.
