It’s chiefly a UK usage of the word. And happy cake day!

Winston Payne energy. (Like Squidward, it’s even funnier when the flashback shows them losing that hair in a single traumatic incident.)

Thanks, OP!

This looks really neat! Are there any updates, given this render was from almost three years ago?

deleted by creator

That’s mainly why I’m curious to see specific examples: I’ve fixed hundreds if not thousands of typos and can’t remember this happening, even long before I had much experience editing. I’m long past the point where I’d be considered a new editor, so any results I’d get now would be bullshit anyway short of violating the rules and starting a smurf account.

Regarding “in the clique”, people give a shit about who’s who a lot less than you’d think. Despite having 25,000 edits over 8 years, I’ve interacted with maybe three people in the top 100 by number of contributions (let alone even know who they are). I’m not a social butterfly on there, but I’ve interacted in hundreds of discussions when needed. Not only am I almost never checking who an editor is when I check their edit, but I maybe know 100 people total (orders of magnitude less than the pool of very active editors); even among the few people I’d consider acquaintances, I’ve had my edits reverted and reverted theirs.

The only instance I’ve seen of someone trying to play king shit of fuck mountain and not immediately failing is in our article for San Francisco, where they were insistent that there was a strong consensus for using only one image in the infobox instead of the usual collage we do in 99.9% of major cities. The image used was a picture of the Golden Gate Bridge in front of the San Francisco skyline – neither of which were represented well. They’d been shutting down ideas for a collage for years, and when other editors found out about this, it turned into a request for comment (RfC). Despite their now having 500,000 edits in about 18 years (this ought to put them in the alleged “clique” even though I’d never heard of them before) this swung wildly against them to the point of the RfC being closed early, and the article now has a (I think really nice) collage.

(TL;DR: the policy against trying to dictate the contents of an article isn’t just there so we can say “but c it’s agenst da rulez so it dusnt happin!!”; it’s there because the wider editing community fucking hates that shit and doesn’t put up with it.)

If you don’t mind, I’d be interested to take a look and see what the reason edits got reverted. Obviously it’s stale enough now that I can’t ask anyone involved to not bite the newcomers or tell them why reversions they made may not be correct, but I’m still curious to see what kinds of edits by new editors commonly get reverted.

A good feature if you ever decide to edit again (on desktop, probably mobile too) is that in the source editor, there’s a Show Preview button. This renders out the page as if you’d committed the change. I said in another comment that almost 2% of my edits have been reverted in some way, and many of those are self-reverts. The only reason there are fewer immediate self-reverts these days isn’t because I’m making fewer mistakes; it’s because I’ve mostly replaced the “oh fuck go back” button with being able to quickly identify how I broke something (unless what I’ve done is unsalvageable).

The other day during a discussion, a few editors started joking about how many mistakes we make. Cullen328 (yes, the admin mentioned in this post) said: “One of my most common edit summaries is “Fixed typo”, which usually means that I fixed my own typo.” The Bushranger, another admin, replied: "I always spot mine just after hitting ‘Publish changes’… " And finally I said: “It feels like 50% of the edits I publish have the same energy as Peter watching Gwen Stacy fall to her death in slow-motion in TASM 2.” Between the three of us is about 300,000 edits, two little icons with a mop, and over 30 years of experience editing. Not only will you fuck up at first, but you’ll continue to fuck up over and over again forever. It’s how you deal with it that counts, and you dealt with it well.

Inject whatever weird, obscure fucking drama this is into my veins, please. I know Bloodborne has an indie wiki; do the Souls games not have one?

There’s fortunately no such thing as control of the page. Like I explained above, reversion is considered a normal but uncommon part of the editing process. It’s more common at the outset for new editors to have their initial edit reverted on policy/guideline grounds but then have a modified version of the edit let through with no issue. In order not to not bite newcomers, experienced editors will often bite the bullet and take the time to fix policy/guideline violations themselves while telling the newcomer what they did wrong.

If you go to discuss the reversion with the other editor on the talk page and it becomes clear this isn’t about policy or guideline violations (or they’re couching it in policy/guidelines through wikilawyering nonsense) but instead that they think they’re king shit of fuck mountain and own the article, ask an administrator. Administrators hate that shit.

That makes sense. “Probably over 20 years ago now” probably means that there weren’t any solid guidelines or policies to revert based on, since it was only around 2006 that the community rapidly began developing formal standards. I’m betting a lot more reverts were “nuh uh”, “yuh huh” than they are today. If you still remember the account name, I’m curious to see what bullshit transpired. If the watchlist even existed back then, someone probably saw a new edit, didn’t like it for whatever reason (I have no capacity to judge), and hit the “nuh uh” button. (Edit: I bet it was ‘Recent changes’, actually; probably more viable in an era of sub-100 edits per minute.)

Something new editors get confused about (me especially; I was so pissed the first time) is that edits can be reverted by anyone for any reason. (By “can”, I don’t mean “may”; a pattern of bad-faith reversions will quickly get you blocked). Almost 2% of my edits have been reverted in some way, and plenty of those have been by people with 1/100th the experience I have (some rightly so, some not so much). Reversion is actually considered a very normal if uncommon part of the editing process, and it’s used to generate a healthy consensus on the talk page when done in good faith. But the pertinent point is that reversions can be done by anybody just like additions can be done by anybody; it’s just another edit in “the free encyclopedia that anyone can edit™”. I remember reverting an admin’s edit before (normal editing, not administrative work), and we just had a normal conversation whose outcome I can’t remember. It happens to everyone.

For a municipal wireless network, I’m not too bothered with how OP describes it if it’s accessed through Wi-Fi.

This is an ad for a proofreading service, so nominally it’s meant for you to use in formal writing. In that context, only a small proportion of these words are “fancy”.

That said, a thesaurus is best used for remembering words you already know, i.e. not like shown here. Careful use of a thesaurus to find new words provided you research them first – e.g. look them up on Wiktionary (bang !wt on DuckDuckGo) to see example sentences, etymologies, pronunciations, possible other meanings, usage context (e.g. slang, archaic, jargon), etc. – can work, but if you’re already writing something, just stick to what you know unless it’s dire. You should make an effort to learn words over time as they come up in appropriate contexts rather than memorizing them as replacements for other words; this infographic offers a shortcut that’s probably harder and less accurate than actually learning.

A one-night stand with a word you found in the thesaurus is going to alienate people who don’t know what it means and probably make you look like a jackass to those who do.

Just do what Josh Nichols does.

Yeah, I retract my comment. The SVG cat with the Peter Griffin ballsack chin told me it’s fine.

don’t say “very accurate”; say “exact”

First line of this infographic is already deeply misleading. It’s the equivalent of:

don’t say “very good”; say “perfect”

It’s overly superlative compared to what it’s trying to replace. “Exact” is inherently “very accurate”, but “very accurate” is not inherently “exact”.

Why pay for anything ever if it’s going to potentially get taken away?

Because it’s called “lifetime”? As in the entire point of the product is that it will not ever be taken away with the exception that you close your account? “Why pay for anything if there’s nothing enforcing the core premise of the product?” The gardener advertised a “whole-yard mow” for $100, but I’ve already gotten the area around the driveway, and honestly would it really be that bad if they just stopped right now?

You can talk about odds all you want (although I think around $100 million in VC funding puts those odds squarely in favor of “lifetime” users getting the floor sawed out from under them Looney Tunes-style), but the fact it’s even possible is what’s deeply disturbing, because it’s deliberate. Lifetime’s meaning should be unambiguously stipulated in a contract, not inferred. Know why? Because companies out there advertising “lifetime” subscriptions right now have little disclaimers like “approximately five years or so but honestly we don’t really know or care lol this license disappears whenever we want it to”).

People are assuming it’s for the lifetime of your Plex account, but my response is: based on fucking what? Plex on their website doesn’t seem to specify this anywhere, even in their terms of service. People asking on their official forums receive responses saying things like “probably for the lifetime of your Plex account” with no sources to anything. I’m not trying to sealion here; I literally can’t find a single instance of Plex stating officially in writing or verbally what “lifetime” actually means to the end user. If Plex isn’t going to rugpull, why can’t they add a couple sentences to their TOS saying something like: “The purchase of a lifetime pass grants the user a non-transferable license for [blah blah] starting from the date of purchase. This license will not be revoked unless 1) the associated account is terminated by the account holder or 2) the aasociated account is terminated by Plex for one or more of the reasons outlined in section [blah]”?

They could, they should, they don’t, and you have no good explanation, otherwise you would’ve offered one by now. They have enough money to afford a legal team that wouldn’t overlook that. The answer is that they want to reserve the right to destroy the “lifetime” pass whenever they want. If you can find official documentation from Plex Inc. saying that if I buy a lifetime pass today for $250, the license will only end with the termination of the account, then I’ll have no idea why they make this too hard to find, but I’ll take back everything else I said in this comment and stop using “lifetime” in scare quotes. I genuinely want to know if they say anything about this anywhere.

Another reason donating to FOSS is better than paying for proprietary software. Proprietary software devs get to run around stealing whatever code they like from the open-source community and never suffer any consequence because they don’t make their source available. I can think of a select few proprietary projects that have the balls to be source-available.

If you want to intentionally create a system that lets you evade accountability for stealing code, “fine”, but I have zero respect for you or your product, and I’m certainly not paying you a dime. I’ll put my money toward the developers who work to better the world instead of the rat fucks who steal from them to make money and pollute the software ecosystem with proprietary trash.

You literally said you have Plex pass in the other comment, why are you playing dumb?

They care about the people who don’t have a “lifetime” pass? Having empathy for others who don’t have what you have, caring about the ethics of a company whose products you use and pay for, and taking a stance that software should be as free and open as possible aren’t “playing dumb”. If anything, as someone who isn’t just using Plex for free, they’ve earned more of a right to complain, because they’ve shown they’re willing to pay for quality services but think this one is exploitative.

Maybe even disregarding empathy, they’re worried that existing features will become locked behind a tier that the “lifetime” pass doesn’t apply to? Maybe they’re worried that their “lifetime” pass won’t be so “lifetime” if “lifetime” wasn’t explicitly defined to mean lifetime at the time of purchase? Anything bad that can happen will happen with VC-fueled enshittification.

I also want to emphasize that relicensing from the GPLv2 to something proprietary is damn-near impossible for a project this large with a team who are so ideologically motivated to make FOSS. If I today submit a PR to the Jellyfin codebase, they can’t legally relicense to a proprietary license without 1) getting my consent to give them ownership of my work (I’m not likely to be paid off or convinced it’s a good thing that work I submitted for free is being enshittified), or 2) removing my work from the project if they can’t get in touch with me or if I say no. To emphasize: this consent is affirmative.

Thus, the process is to survey who’s contributed to the project, reach out to anyone whose work is still in the project (preferably in writing in a permanent, court-admissable format like email), ask them to transfer ownership of their copyright to you, keep track of who’s said no, said yes, or not answered, fulfill conditions for anyone who wants something in return, and meticulously rip out all of the code from people who say “no” or don’t answer. One of the project’s major contributors died 10 years ago? Legally, too fucking bad: they didn’t relinquish shit to you. Rip out that legacy code and start over.

Just like for instance if you want to take a Wikipedia article and own it for yourself, you can’t just go ask the Wikimedia Foundation nicely. You have to contact every single contributor whose work is extant in that article, and rip out work that isn’t explicitly given to you by its owner.