[They settled for $2.4M and shut everything down.](https://www.polygon.com/24090351/nintendo-2-4-million-yuzu-switch-emulator-settlement-lawsuit) > > > We write today to inform you that yuzu and yuzu’s support of Citra are being discontinued, effective immediately. > >

> > > The convictions of the two paramedics shook the world of emergency workers who have typically been shielded from criminal prosecution — and it forced questions about the dynamic between the police and paramedics at a scene. > > > > > Though Mr. McClain was visibly distressed and in handcuffs, paramedics never spoke to him, touched him or checked his vital signs before diagnosing him with excited delirium, a controversial condition characterized by agitation and exceptional physical strength. Paramedics then injected him with what authorities later said was a dose of ketamine inappropriate for Mr. McClain’s body weight. > >

The intelligence was made public, in part, in a cryptic announcement on Wednesday by Representative Michael R. Turner, Republican of Ohio and the chairman of the House Intelligence Committee. He called on the Biden administration to declassify the information without saying specifically what it was. His committee took the unorthodox move of voting on Monday to make the information available to all members of Congress — a step that alarmed some officials because it is not clear in what context, if any, the intelligence in the panel’s possession was presented. In a note to lawmakers, the House Intelligence Committee said the intelligence was about a “destabilizing foreign military capability.” Representative Jim Himes, Democrat of Connecticut and the ranking member of the House Intelligence Committee, said that the issue was “serious” and that Mr. Turner was right to focus on it. But he added that the threat was “not going to ruin your Thursday.”

Shipped in Windows 11 Insider Preview Build 26052. [https://www.tiraniddo.dev/2024/02/sudo-on-windows-quick-rundown.html](https://www.tiraniddo.dev/2024/02/sudo-on-windows-quick-rundown.html) claims it has a big security problem that makes the program accept calls to elevate from anywhere once first run Edit: 1. The security problem has been internally fixed and will be available in the next release 2. [It's not just an alias for 'runas'.](https://github.com/microsoft/sudo/blob/main/scripts/sudo.ps1) It seems to be able to configurably block user input for sudo'd commands, retain the existing environment, ditch it and open a new window, and remember that you've sudo'd in the last minute or so. 3. It brings up UAC instead of having you input the password

A mountain of research has linked loneliness to an increased risk of dementia, depression, anxiety, heart disease, stroke and early death. The Board of Supervisors of San Mateo county, which includes part of Silicon Valley, passed a resolution on Tuesday that declared loneliness a public health crisis and pledged to explore measures that promote social connection in the community. Relative to white people, Black people face a higher risk of premature death linked to social isolation. Older adults have a higher risk of loneliness in general, since they are more likely to live alone or have chronic illnesses that limit their mobility or leave them homebound.

In other news, URLs are now delimited by a space rather than a comma when updating manifests. Komac uses a very small amount amount of memory and has been heavily optimised to minimise memory usage (especially heap allocations). Updating Android Studio (a 1GB+ binary) consistently took just \~3.5mb memory. Komac now has a significantly more accurate way of checking if an installer was created with Inno/NSIS instead of just checking for some magic bytes. As of this release, the uncompressed x64 portable binary stands at just \~7.5mb and doesn't require runtimes like the JVM. The Windows installers add Komac to path (allowing you to just run `komac` in a terminal) and stand at less than 3.5mb.

The original post uses "roll-up" instead of "catch-all" for some reason. There is a long-festering problem in some tags where some questions are closed by dupehammers, using a single roll-up question as the duplicate target. A "roll-up" question is defined here as a question trying to cover multiple minor topics within one question and a set of answers. So [this Java question about null pointer exceptions](https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it) does not qualify, as it is about a single topic. A prime example would be [this regex roll-up](https://stackoverflow.com/questions/22937618/reference-what-does-this-regex-mean) which has [a large number of duplicates](https://stackoverflow.com/questions/linked/22937618?lq=1). This was [by design](https://meta.stackoverflow.com/questions/252868/regex-reference-and-its-fate). > > > Questions that are clear duplicates, but you can't find one quickly. > > To be fair, PHP and other tags have such roll-ups ([example](https://stackoverflow.com/questions/3737139/reference-guide-what-does-this-symbol-mean-in-php-php-syntax)), and I have participated in hammering them as such. And there are a lot of questions that are low quality, where the temptation is to simply close them as the duplicates of the roll-up. I mean, it answers the question, doesn't it? The problem is that this has started to promote two undesirable community actions: Lazy closure ========== Dupehammers are a "one and done" action. Moreover, there is a belief is that these questions answer all the "core" elements and are therefore "useful" in low quality situations. The question for regex theoretically covers all symbols used within, so why isn't that useful? But this type of closure assumes that the roll-up covers all cases. The danger of dupehammers has always been that the target question doesn't really cover a specific use case. Lazy closure doesn't even bother to find that out first. Thus it becomes the action of choice for dupehammer users. It's problematic, but the community largely self-regulates this so it's not been a major issue. A low quality question can be closed for many other reasons beyond duplicate. Tag gatekeeping ========== This action is the more problematic one. What we've been seeing for some time are "brigades" (for lack of any better term) of users who are committed to ensuring that only questions they see fit in a tag are open. Thus we get a number of these: [Dupehammer 40000](https://i.stack.imgur.com/IzmE7.png) What this has turned into is not laziness, but deliberate actions, where we see the same users doing this over and over. Or, to quote a comment under the question I got the screenshot from: > > > I invite readers to examine the earlier question and ask themselves if any question could possibly be a duplicate of that question. If the answer is "no", please vote to reopen (and leave a comment giving your reasons for doing so). Closing this question, in this way, is sending a clear message to Peter, the OP (the polite version): "get lost". This catch-all closing of questions having a "regex" tag must stop. > > I don't know that it sends a "get lost" message, as much as it sends another message moderators have been fighting against for years: RTFM. What these roll-ups have become, in essence, is another "fine" manual for users to read. Duplicate closure like this is basically throwing a volume of information at users and telling them "Figure out what, in this giant pile of information, answers your question." That's not useful. It also effectively acts as a veto for anything any dupehammer user sees fit to close it as. Roll-up questions worked well as a philosophy for a long time, but (as the old saying goes), this is why we can't have nice things. The rule ========== The rule would be as follows: > > > Roll-up questions are useful in general, but may not provide enough guidance to users with specific questions, and serve as poor signposts to users looking for specific answers. Please use only specific questions for duplicate closure. > > FAQ ========== * Moderators would enforce this new rule. No system changes would be made. * Moderators would find out about violations via flags. Moderators already get an autoflag for closure disputes, and users could flag instances of this rule being violated. * Enforcement would follow standard enforcement: A warning on the first offense and suspension for subsequent violations. * Any other duplicate closure would still be allowed. If someone feels strongly enough that it's a duplicate, they should go find that specific question. Moderators [will still not solve duplicate disputes](https://meta.stackoverflow.com/a/419709/2370483), but the list of roll-up questions isn't long, and it's a fairly objective standard to enforce.

The original post uses "roll-up" instead of "catch-all" for some reason. There is a long-festering problem in some tags where some questions are closed by dupehammers, using a single roll-up question as the duplicate target. A "roll-up" question is defined here as a question trying to cover multiple minor topics within one question and a set of answers. So [this Java question about null pointer exceptions](https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it) does not qualify, as it is about a single topic. A prime example would be [this regex roll-up](https://stackoverflow.com/questions/22937618/reference-what-does-this-regex-mean) which has [a large number of duplicates](https://stackoverflow.com/questions/linked/22937618?lq=1). This was [by design](https://meta.stackoverflow.com/questions/252868/regex-reference-and-its-fate). > > > Questions that are clear duplicates, but you can't find one quickly. > > To be fair, PHP and other tags have such roll-ups ([example](https://stackoverflow.com/questions/3737139/reference-guide-what-does-this-symbol-mean-in-php-php-syntax)), and I have participated in hammering them as such. And there are a lot of questions that are low quality, where the temptation is to simply close them as the duplicates of the roll-up. I mean, it answers the question, doesn't it? The problem is that this has started to promote two undesirable community actions: Lazy closure ========== Dupehammers are a "one and done" action. Moreover, there is a belief is that these questions answer all the "core" elements and are therefore "useful" in low quality situations. The question for regex theoretically covers all symbols used within, so why isn't that useful? But this type of closure assumes that the roll-up covers all cases. The danger of dupehammers has always been that the target question doesn't really cover a specific use case. Lazy closure doesn't even bother to find that out first. Thus it becomes the action of choice for dupehammer users. It's problematic, but the community largely self-regulates this so it's not been a major issue. A low quality question can be closed for many other reasons beyond duplicate. Tag gatekeeping ========== This action is the more problematic one. What we've been seeing for some time are "brigades" (for lack of any better term) of users who are committed to ensuring that only questions they see fit in a tag are open. Thus we get a number of these: [Dupehammer 40000](https://i.stack.imgur.com/IzmE7.png) What this has turned into is not laziness, but deliberate actions, where we see the same users doing this over and over. Or, to quote a comment under the question I got the screenshot from: > > > I invite readers to examine the earlier question and ask themselves if any question could possibly be a duplicate of that question. If the answer is "no", please vote to reopen (and leave a comment giving your reasons for doing so). Closing this question, in this way, is sending a clear message to Peter, the OP (the polite version): "get lost". This catch-all closing of questions having a "regex" tag must stop. > > I don't know that it sends a "get lost" message, as much as it sends another message moderators have been fighting against for years: RTFM. What these roll-ups have become, in essence, is another "fine" manual for users to read. Duplicate closure like this is basically throwing a volume of information at users and telling them "Figure out what, in this giant pile of information, answers your question." That's not useful. It also effectively acts as a veto for anything any dupehammer user sees fit to close it as. Roll-up questions worked well as a philosophy for a long time, but (as the old saying goes), this is why we can't have nice things. The rule ========== The rule would be as follows: > > > Roll-up questions are useful in general, but may not provide enough guidance to users with specific questions, and serve as poor signposts to users looking for specific answers. Please use only specific questions for duplicate closure. > > FAQ ========== * Moderators would enforce this new rule. No system changes would be made. * Moderators would find out about violations via flags. Moderators already get an autoflag for closure disputes, and users could flag instances of this rule being violated. * Enforcement would follow standard enforcement: A warning on the first offense and suspension for subsequent violations. * Any other duplicate closure would still be allowed. If someone feels strongly enough that it's a duplicate, they should go find that specific question. Moderators [will still not solve duplicate disputes](https://meta.stackoverflow.com/a/419709/2370483), but the list of roll-up questions isn't long, and it's a fairly objective standard to enforce.

Oliver discovered a loophole in the rules, which allowed anybody with a valid email address to cast a vote. “After all, this is what democracy is all about,” Oliver said on his show. “America interfering in foreign elections.” Forest and Bird said vote checkers had been forced to take an extra two days to verify the hundreds of thousands of votes that had poured in by Sunday’s deadline. They now plan to announce a winner on Wednesday. The contest has survived previous controversies. Election scrutineers in 2020 discovered about 1,500 fraudulent votes for the little spotted kiwi. And two years ago, the contest was won by a bat, which was allowed because it was considered part of the bird family by Indigenous Māori. Usually billed Bird of the Year, the annual event by conservation group Forest and Bird is held to raise awareness about the plight of the nation’s native birds, some of which have been driven to extinction. This year, the contest was named Bird of the Century to mark the group’s centennial.

> > > What?????? What the hell??? — arbitrator [Moneytrees](https://en.wikipedia.org/wiki/User:Moneytrees), [arbitration request for Lourdes](https://en.wikipedia.org/wiki/Special:PermanentLink/1183169230#Lourdes:_Arbitrators'_opinion_on_hearing_this_matter_%3C1/8/1%3E) > > A [2015 arbitration report](https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2015-02-18/Arbitration_report) in this very periodical said "it was a matter of deep concern" that an abusive editor who had obtained administrator privileges "was able to fool the community for so long". At that time, they were banned by the Arbitration Committee following a long case. We are sad to report that, not only did the abuse not stop in 2015, but the same person managed to obtain a second administrator account, and was just discovered a few days ago. ### November 1 case request and startling admission ### [Beeblebrox](https://en.wikipedia.org/wiki/User:Beeblebrox) opened a request for arbitration against administrator [Lourdes](https://en.wikipedia.org/wiki/User:Lourdes) on 1 November, claiming misdeeds including administrative blackmail — bullying other less-privileged editors over their votes during a recent request for adminship. With the case request around one day old, on 2 November, the respondent suddenly [stated](https://en.wikipedia.org/wiki/Special:Diff/1183105704) that they are the site-banned former admin, Wifione. The case request was [closed as moot](https://en.wikipedia.org/wiki/Special:Diff/1183170493) following Lourdes' admission. One of the contributors to the case, [Kurtis](https://en.wikipedia.org/wiki/User:Kurtis), asked "Is this an ArbCom case request or an M. Night Shyamalan movie?" Others, like arbitrator Moneytrees in the quote above, were more to-the-point. ### Wifione background ### If you have read our [prior coverage](https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2015-02-18/Arbitration_report#In_depth:_Wifione) of how the Wifione siteban came to be, amidst allegations of paid editing while holding the admin bit, you can probably skip over this section. According to the 2015 Arbcom case, the [oldest known account](https://en.wikipedia.org/wiki/Wikipedia:Arbitration/Requests/Case/Wifione#Sock_puppetry) used by the individual also known as Wifione was created in 2006. They created dozens of sock accounts, which were revealed by a [2008 checkuser request](https://en.wikipedia.org/wiki/Wikipedia:Requests_for_checkuser/Case/Mrinal_Pandey). That prior account was later linked to another account called Wifione, which was created in 2009 and that had become a Wikipedia admin in 2010. The Arbitration committee case found that Wifione was engaging in search engine optimization related to an Indian educational firm. Wifione was [sitebanned](https://en.wikipedia.org/wiki/Wikipedia:SBAN) as part of the case resolution. ### An admin called "Lourdes" ### This [long-term abuser](https://en.wikipedia.org/wiki/Wikipedia:LTA) created the Lourdes account in late 2015, initially under a different name. In 2016 they renamed the account. They were most active in 2016–17, and ran an unsuccessful, self-nominated request for adminship in early 2017; a second attempt in 2018 [was successful](https://en.wikipedia.org/wiki/Special:PermanentLink/827679457) with 207 in favor and 3 opposed. The account went mostly unused for 2020 through 2022, with many months of total editorial inactivity, although it continued to perform admin actions. In 2023, they returned to regularly editing the English Wikipedia. Throughout their tenure, they made 2,282 admin actions, according to [User:JamesR/AdminStats](https://en.wikipedia.org/wiki/User:JamesR/AdminStats). The [arbitration case request](https://en.wikipedia.org/wiki/Special:PermanentLink/1183169230) filed this month alleged that Lourdes engaged in egregious abuse of their administrator status during a recent request for adminship, including the following: > > > Because I remember having acted on your complaints at ANI a few times, and on the basis of that connect and support that I gave you, I am requesting you to reconsider your stand > — Lourdes, at [the case request](https://en.wikipedia.org/wiki/Special:PermanentLink/1181782012) > > This kind of pressuring (there were other examples) was described by one of the contributors to the case request as "the kind of thinly veiled threat you'd expect to hear in *The Godfather*". In response, Lourdes gave an admission nobody expected: > > > I am [User:Wifione](https://en.wikipedia.org/wiki/User:Wifione), the admin who got blocked years ago. > > > > My RL identity has nothing to do with any celebrity or anyone like that. I am not writing this to have any final laugh. It's just that I feel it appropriate to place it here specially for Beeblebrox, who I almost emotionally traumatised over the years with the aforementioned double sleight -- aka, pulling him around for revealing my so-called identity. It also required double-doxxing myself on at least one external project, namely Wikipediocracy, which even placed mentions of my name in the private section to protect my identity. > > > > — Lourdes, at [the case request](https://en.wikipedia.org/wiki/Special:Diff/1183105704) > > And blocked themselves indefinitely: > > > [2023-11-01T22:47:55](https://en.wikipedia.org/w/index.php?title=Special:Log&logid=154542088) [User:Lourdes](https://en.wikipedia.org/wiki/User:Lourdes) ([talk](https://en.wikipedia.org/wiki/User_talk:Lourdes) | [contribs](https://en.wikipedia.org/wiki/Special:Contributions/Lourdes)) blocked [User:Lourdes](https://en.wikipedia.org/wiki/User:Lourdes) ([talk](https://en.wikipedia.org/wiki/User_talk:Lourdes) | [contribs](https://en.wikipedia.org/wiki/Special:Contributions/Lourdes)) with an expiration time of indefinite (account creation blocked, email disabled) (Abusing [multiple accounts](https://en.wikipedia.org/wiki/Wikipedia:Sockpuppetry)) > > All of the details of the request and the statements made there — which arbitrators voted to decline as pointless soon after the revelations and the self-block — can be seen at [its last revision link](https://en.wikipedia.org/wiki/Special:PermanentLink/1183169230). ### Aftermath ### Nobody is quite sure what to make of this. How did they get away with this for so long? How did they conceal it this well? How did nobody notice? What was the point of spending years as a productive administrator, making tens of thousands of edits and logging thousands of actions, to implode the whole thing over a pointless argument on an RfA talk page? *The Signpost*'s sources have confirmed that the particular [BADSITE](https://en.wikipedia.org/wiki/Wikipedia:BADSITES) mentioned in Lourdes' final message has indeed discussed this issue, and that both Beeblebrox and the disgraced LTA have posted more about the events, but the [thread over there](https://wikipediocracy.com/forum/viewtopic.php?f=38&t=13187) doesn't make a whole lot of sense either. In short: what?

Hi, I'm somewhat new to Kotlin programming and so far it's becoming my favorite language. I was browsing some Kotlin projects when I found Komac, which [recently switched to the Multiplatform target](https://github.com/russellbanks/Komac/pull/296) from [only having the JVM target](https://github.com/russellbanks/Komac/blob/7c9be6f257eacd354ae9c98c470b4f770a3d4d20/src/main/kotlin/Komac.kt). As far as I know, JVM can also run on all platforms without the use of minGW except for iOS but I don't have a developer certificate or incentive to work beyond CMD scripts so far, so is there an advantage for Kotlin Multiplatform?

Since its inception, Microsoft Excel has changed how people organize, analyze, and visualize their data, providing a basis for decision-making for the flying billionaires heads up in the clouds who don't give a fuck for life off~~the~~line