If you leave a new message on this page, I will reply on this page unless you ask me to reply elsewhere.
Welcome to SMcCandlish's talk page.
I will generally respond here to comments that are posted here, rather than replying via your talk page (or the article's talk page, if you are writing to me here about an article), so you may want to watch this page until you are responded to, or let me know where specifically you'd prefer the reply.
This user talk page might be watched by friendly talk page stalkers, which means that someone other than me might reply to your query. Their input is welcome and their help with messages that I cannot reply to quickly is appreciated.
Users wishing to permanently leave may now request "vanishing" via Special:GlobalVanishRequest. Processed requests will result in the user being renamed, their recovery email being removed, and their account being globally locked.
– Can't get at the stuff at Ancestry; try using addl. cards.
Extended content
Categories are not my thing but do you think there are enough articles now or will be ever to make this necessary? Other than Finger billiards and possibly Carrom, what else is there?--Fuhghettaboutit (talk) 11:12, 18 January 2010 (UTC)[reply]
Crud fits for sure. And if the variant in it is sourceable, I'm sure some military editor will fork it into a separate article eventually. I think at least some variants of bar billiards are played with hands and some bagatelle split-offs probably were, too (Shamos goes into loads of them, but I get them all mixed up, mostly because they have foreign names). And there's bocce billiards, article I've not written yet. Very fun game. Kept my sister and I busy for 3 hours once. Her husband (Air Force doctor) actually plays crud on a regular basis; maybe there's a connection. She beat me several times, so it must be from crud-playing. Hand pool might be its own article eventually. Anyway, I guess it depends upon your "categorization politics". Mine are pretty liberal - I like to put stuff into a logical category as long as there are multiple items for it (there'll be two as soon as you're done with f.b., since we have crud), and especially if there are multiple parent categories (that will be the case here), and especially especially if the split parallels the category structure of another related category branch (I can't think of a parallel here, so this criterion of mine is not a check mark in this case), and so on. A bunch of factors really. I kind of wallow in that stuff. Not sure why I dig the category space so much. Less psychodrama, I guess. >;-) In my entire time here, I can only think of maybe one categorization decision I've made that got nuked at CfD. And I'm a pretty aggressive categorizer, too; I totally overhauled Category:Pinball just for the heck of it and will probably do the same to Category:Darts soon.
I have no "categorization politics". It's not an area that I think about a lot or has ever interested me so it's good there are people like you. If there is to be a category on this, "cueless billiards" seems fine to me. By the way, just posted Yank Adams as an adjunct to the finger billiards article I started.--Fuhghettaboutit (talk) 11:57, 18 January 2010 (UTC)[reply]
Cool; I'd never even heard of him. This one looks like a good DYK; just the fact that there was Finger Billiards World Championship contention is funky enough, probably. You still citing that old version of Shamos? You really oughta get the 1999 version; it can be had from Amazon for cheap and has a bunch of updates. I actually put my old version in the recycle bin as not worth saving. Heh. PS: You seen Stein & Rubino 3rd ed.? I got one for the xmas before the one that just passed, from what was then a really good girlfriend. >;-) It's a-verra, verra nahce. Over 100 new pages, I think (mostly illustrations). — SMcCandlishTalk⇒ ʕ(Õلō)ˀContribs. 13:41, 18 January 2010 (UTC)[reply]
If I happen to come across it in a used book store I might pick it up. There's nothing wrong with citing the older edition (as I've said to you before). I had not heard of Adams before yesterday either. Yank is apparently not his real name, though I'm not sure what it is yet. Not sure there will be enough on him to make a DYK (though don't count it out). Of course, since I didn't userspace it, I have 4½ days to see. Unfortunately, I don't have access to ancestry.com and have never found any free database nearly as useful for finding newspaper articles (and census, birth certificates, and reams of primary source material). I tried to sign up for a free trial again which worked once before, but they got smart and are logging those who signed up previously. I just looked; the new Stein and Rubino is about $280. I'll work from the 2nd edition:-)--Fuhghettaboutit (talk) 14:16, 18 January 2010 (UTC)[reply]
Hmm... I haven't tried Ancestry in a while. They're probably logging IP addresses. That would definitely affect me, since mine doesn't change except once every few years. I guess that's what libraries and stuff are for. S&R: Should be available cheaper. Mine came with the Blue Book of Pool Cues too for under $200 total. Here it is for $160, plus I think the shipping was $25. Stein gives his e-mail address as that page. If you ask him he might give you the 2-book deal too, or direct you to where ever that is. Shamos: Not saying its an unreliable source (although the newer version actually corrected some entries), it's just cool because it has more stuff in it. :-) DYK: Hey, you could speedily delete your own article, sandbox it and come back. Heh. Seriously, I'll see if I can get into Ancestry again and look for stuff on him. I want to look for William Hoskins stuff anyway so I can finish that half of the Spinks/Hoskins story, which has sat in draft form for over a year. I get sidetracked... — SMcCandlishTalk⇒ ʕ(Õلō)ˀContribs. 14:29, 18 January 2010 (UTC)[reply]
It's not IPs they're logging, it's your credit card. You have to give them one in order to get the trial so that they can automatically charge you if you miss the cancellation deadline. Regarding the Blue Book, of all these books, that's the one that get's stale, that is, if you use it for actual quotes, which I do all the time, both for answer to questions and for selling, buying, etc. Yeah I start procrastinating too. I did all that work on Mingaud and now I can't get myself to go back. I also did reams of research on Hurricane Tony Ellin (thugh I found so little; I really felt bad when he died; I met him a few times, seemed like a really great guy), Masako Katsura and others but still haven't moved on them.--Fuhghettaboutit (talk) 18:31, 18 January 2010 (UTC)[reply]
Ah, the credit card. I'll have to see if the PayPal plugin has been updated to work with the new Firefox. If so, that's our solution - it generates a new valid card number every time you use it (they always feed from your single PayPal account). — SMcCandlishTalk⇒ ʕ(Õلō)ˀContribs. 18:37, 18 January 2010 (UTC)[reply]
Thanks for trying. It was worth a shot. I signed up for a newspaperarchive.com three month trial. As far as newspaper results go it seems quite good so far, and the search interface is many orders of magnitude better than ancestry's, but it has none of the genealogical records that ancestry provides. With ancestry I could probably find census info on Yank as well as death information (as well as for Masako Katsura, which I've been working on it for a few days; she could actually be alive, though she'd be 96).--Fuhghettaboutit (talk) 04:52, 9 February 2010 (UTC)[reply]
Sad...
How well forgotten some very well known people are. The more I read about Yank Adams, the more I realize he was world famous. Yet, he's almost completely unknown today and barely mentioned even in modern billiard texts.--Fuhghettaboutit (talk) 13:47, 21 January 2010 (UTC)[reply]
Reading stuff from that era, it's also amazing how important billiards (in the three-ball sense) was back then, with sometimes multiple-page stories in newspapers about each turn in a long match, and so on. It's like snooker is today in the UK. PS: I saw that you found evidence of a billiards stage comedy there. I'd never heard of it! — SMcCandlishTalk⇒ ʕ(Õلō)ˀContribs. 15:17, 21 January 2010 (UTC)[reply]
– New sources/material worked into article, but unanswered questions remain.
Extended content
Some more notes: they bought Royal Worcester in 1983 and sold it the next year, keeping some of the electronics part.[3]; info about making records:[4]; the chair in 1989 was Lord Jenkin of Roding:[5]; "In 1880, crystalate balls made of nitrocellulose, camphor, and alcohol began to appear. In 1926, they were made obligatory by the Billiards Association and Control Council, the London-based governing body." Amazing Facts: The Indispensable Collection of True Life Facts and Feats. Richard B. Manchester - 1991wGtDHsgbtltnpBg&ct=result&id=v0m-h4YgKVYC&dq=%2BCrystalate; a website about crystalate and other materials used for billiard balls:No5 Balls.html. Fences&Windows23:37, 12 July 2011 (UTC)[reply]
Cool! From what I can tell, entirely different parties held the trademark in different markets. I can't find a link between Crystalate Mfg. Co. Ltd. (mostly records, though billiard balls early on) and the main billiard ball mfr. in the UK, who later came up with "Super Crystalate". I'm not sure the term was even used in the U.S. at all, despite the formulation having been originally patented there. — SMcCandlishTalk⇒ ʕ(Õلō)ˀContribs. 21:04, 17 July 2011 (UTC)[reply]
No one has actually objected to the idea that it's really pointless for WP:SAL to contain any style information at all, other than in summary form and citing MOS:LIST, which is where all of WP:SAL's style advice should go, and SAL page should move back to WP:Stand-alone lists with a content guideline tag. Everyone who's commented for 7 months or so has been in favor of it. I'd say we have consensus to start doing it. — SMcCandlishTalk⇒ ɖ∘¿¤þ Contrib.13:13, 2 March 2012 (UTC)[reply]
– Need to fix William A. Spinks, etc., with proper balkline stats, now that we know how to interpret them.
Extended content
That page looks like a hinterland (you go back two users in the history and you're in August). Are you familiar with WP:MCQ? By the way, did you see my response on the balkline averages?--Fuhghettaboutit (talk) 15:54, 6 January 2013 (UTC)[reply]
Yeah, I did a bunch of archiving yesterday. This page was HUGE. It'll get there again. I'd forgotten MCQ existed. Can you please add it to the DAB hatnote at top of and "See also" at bottom of WP:COPYRIGHT? Its conspicuous absence is precisely why I ened up at Wikipedia talk:FAQ/Copyright! Haven't seen your balkline response yet; will go look. — SMcCandlishTalk⇒ ɖ⊝כ⊙þ Contrib.21:34, 6 January 2013 (UTC)[reply]
Hee Haw
Unresolved
– Still need to propose some standards on animal breed article naming and disambiguation. In the intervening years, we've settled on natural not parenthetic disambiguation, and that standardized breeds get capitalized, but that's about it.
Extended content
Yeah, we did get along on Donkeys. And probably will get along on some other stuff again later. Best way to handle WP is to take it issue by issue and then let bygones be bygones. I'm finding some interesting debates over things like the line between a subspecies, a landrace and a breed. Just almost saw someone else's GA derailed over a "breed versus species" debate that was completely bogus, we just removed the word "adapt" and life would have been fine. I'd actually be interested in seeing actual scholarly articles that discuss these differences, particularly the landrace/breed issue in general, but in livestock in particular, and particularly as applied to truly feral/landrace populations (if, in livestock, there is such a thing, people inevitably will do a bit of culling, sorting and other interference these days). I'm willing to stick to my guns on the WPEQ naming issue, but AGF in all respects. Truce? Montanabw(talk)22:40, 6 January 2013 (UTC)[reply]
Truce, certainly. I'm not here to pick fights, just improve the consistency for readers and editors. I don't think there will be any scholarly articles on differences between landrace and breed, because there's nothing really to write about. Landrace has clear definitions in zoology and botany, and breed not only doesn't qualify, it is only established as true in any given case by reliable sources. Basically, no one anywhere is claiming "This is the Foobabaz horse, and it is a new landrace!" That wouldn't make sense. What is happening is people naming and declaring new alleged breeds on an entirely self-interested, profit-motive basis, with no evidence anyone other than the proponent and a few other experimental breeders consider it a breed. WP is full of should-be-AfD'd articles of this sort, like the cat one I successfully prod'ed last week. Asking for a reliable source that something is a landrace rather than a breed is backwards; landrace status is the default, not a special condition. It's a bit like asking for a scholarly piece on whether pig Latin is a real language or not; no one's going to write a journal paper about that because "language" (and related terms like "dialect", "language family", "creole" in the linguistic sense, etc.) have clear definitions in linguistics, while pig Latin, an entirely artificial, arbitrary, intentionally-managed form of communication (like an entirely artificial, arbitrary, intentionally managed form of domesticated animal) does not qualify. :-) The "what is a breed" question, which is also not about horses any more than cats or cavies or ferrets, is going to be a separate issue to resolve from the naming issue. Looking over what we collaboratively did with donkeys – and the naming form that took, i.e. Poitou donkey not Poitou (donkey), I think I'm going to end up on your side of that one. It needs to be discussed more broadly in an RFC, because most projects use the parenthetical form, because this is what WT:AT is most readily interpretable as requiring. — SMcCandlishTalk⇒ ɖ⊝כ⊙þ Contrib.00:12, 7 January 2013 (UTC)[reply]
I hate the drama of an RfC, particularly when we can just look at how much can be naturally disambiguated, but if you think it's an actual issue, I guess ping me when it goes up. As for landcraces, it may be true ("clear definitions") but you would be doing God's (or someone's) own good work if you were to improve landrace which has few references, fewer good ones, and is generally not a lot of help to those of us trying to sort out WTF a "landrace" is... (smiles). As for breed, that is were we disagree: At what point do we really have a "breed" as opposed to a "landrace?" Fixed traits, human-selected? At what degree, at which point? How many generations? I don't even know if there IS such a thing as a universal definition of what a "breed" is: seriously: [6] or breed or [7]. I think you and I agree that the Palomino horse can never be a "breed" because it is impossible for the color to breed true (per an earlier discussion) so we have one limit. But while I happen agree to a significant extent with your underlying premise that when Randy from Boise breeds two animals and says he has created a new breed and this is a problem, (I think it's a BIG problem in the worst cases) but if we want to get really fussy, I suppose that the aficionados of the Arabian horse who claim the breed is pure from the dawn of time are actually arguing it is a landrace, wouldn't you say? And what DO we do with the multi-generational stuff that's in limbo land? Montanabw(talk)00:41, 7 January 2013 (UTC)[reply]
I'm not really certain what the answers are to any of those questions, another reason (besides your "STOP!" demands :-) that I backed away rapidly from moving any more horse articles around. But it's something that is going to have to be looked into. I agree that the Landrace article here is poor. For one thing, it needs to split Natural breed out into its own article (a natural breed is a selectively-bred formal breed the purpose of which is to refine and "lock-in" the most definitive qualities of a local landrace). This in turn isn't actually the same thing as a traditional breed, though the concepts are related. Basically, three breeding concepts are squished into one article. — SMcCandlishTalk⇒ ɖ⊝כ⊙þ Contrib.00:52, 7 January 2013 (UTC)[reply]
Given that the article isn't well-sourced yet, I think that you might want to add something about that to landrace now, just to give whomever does article improvement on it later (maybe you, I think this is up your alley!) has the "ping" to do so. Montanabw(talk)21:55, 8 January 2013 (UTC)[reply]
Although I have been an evolutionary biologist for decades, I only noticed the term "landrace" within the past year or two (in reference to corn), because I work with wildland plants. But I immediately knew what it was, from context. I'm much less certain about breeds, beyond that I am emphatic that they are human constructs. Montanabw and I have discussed my horse off-wiki, and from what I can tell, breeders are selecting for specific attributes (many people claim to have seen a horse "just like him"), but afaik there is no breed "Idaho stock horse". Artificially-selected lineages can exist without anyone calling them "breeds"; I'm not sure they would even be "natural breeds", and such things are common even within established breeds (Montanabw could probably explain to us the difference between Polish and Egyptian Arabians).
The good thing about breeds wrt Wikipedia is that we can use WP:RS and WP:NOTABLE to decide what to cover. Landraces are a different issue: if no one has ever called a specific, distinctive, isolated mustang herd a landrace, is it OR for Wikipedia to do so?--Curtis Clark (talk) 16:21, 7 January 2013 (UTC)[reply]
I have been reluctant to use landrace much out of a concern that the concept is a bit OR, as I hadn't heard of it before wikipedia either (but I'm more a historian than an evolutionary biologist, so what do I know?): Curtis, any idea where this did come from? It's a useful concept, but I am kind of wondering where the lines are between selective breeding and a "natural" breed -- of anything. And speaking of isolated Mustang herds, we have things like Kiger Mustang, which is kind of interesting. I think that at least some of SMc's passion comes from the nuttiness seen in a lot of the dog and cat breeders these days, am I right? I mean, Chiweenies? Montanabw(talk)23:01, 7 January 2013 (UTC)[reply]
The first use of the word that I saw referred to different landraces of corn growing in different elevations and exposures in indigenous Maya areas of modern Mexico. I haven't tracked down the references for the use of the word, but the concept seems extremely useful. My sense is that landraces form as much through natural selective processes of cultivation or captivity as through human selection, so that if the "garbage wolf" hypothesis for dog domestication is true, garbage wolves would have been a landrace (or more likely several, in different areas). One could even push the definition and say that MRSA is a landrace. But I don't have enough knowledge of the reliable sources to know how all this would fit into Wikipedia.--Curtis Clark (talk) 01:01, 8 January 2013 (UTC)[reply]
– Work to integrate WP:NCFLORA and WP:NCFAUNA stuff into MOS:ORGANISMS not completed yet? Seems to be mostly done, other than fixing up the breeds section, after that capitalization RfC a while back.
Extended content
The sentence at MOS:LIFE "General names for groups or types of organisms are not capitalized except where they contain a proper name (oak, Bryde's whales, rove beetle, Van cat)" is a bit odd, since the capitalization would (now) be exactly the same if they were the names of individual species. Can it simply be removed?
There is an issue, covered at Wikipedia:PLANTS#The use of botanical names as common names for plants, which may or may not be worth putting in the main MOS, namely cases where the same word is used as the scientific genus name and as the English name, when it should be de-capitalized. I think this is rare for animals, but more common for plants and fungi (although I have seen "tyrannosauruses" and similar uses of dinosaur names). Peter coxhead (talk) 09:17, 3 May 2014 (UTC)[reply]
I would leave it a alone for now; let people get used to the changes. I think it's reasonable to include the "general names" thing, because it's a catch-all that includes several different kinds of examples, that various largely different groups of people are apt to capitalize. Various know-nothings want to capitalize things like "the Cats", the "Great Apes", etc., because they think "it's a Bigger Group and I like to Capitalize Big Important Stuff". There are millions more people who just like to capitalize nouns and stuff. "Orange's, $1 a Pound". Next we have people who insist on capitalizing general "types" and landraces of domestic animals ("Mountain Dogs", "Van Cat") because they're used to formal breed names being capitalized (whether to do that with breeds here is an open question, but it should not be done with types/classes of domestics, nor with landraces. Maybe the examples can be sculpted better: "the roses", "herpesviruses", "great apes", "Bryde's whale", "mountain dogs", "Van cat", "passerine birds". I'm not sure that "rove beetle" and "oak" are good examples of anything. Anyway, it's more that the species no-capitalization is a special case of the more general rule, not that the general rule is a redundant or vague version of the former. If they're merged, it should keep the general examples, and maybe specifically spell out and illustrate that it also means species and subspecies, landraces and domestic "types", as well as larger and more general groupings.
I had noticed that point and was going to add it, along with some other points from both NCFLORA and NCFAUNA, soon to MOS:ORGANISMS, which I feel is nearing "go live" completion. Does that issue come up often enough to make it a MOS mainpage point? I wouldn't really object to it, and it could be had by adding an "(even if it coincides with a capitalized Genus name)" parenthetical to the "general names" bit. The pattern is just common enough in animals to have been problematic if it were liable to be problematic, as it were. I.e., I don't see a history of squabbling about it at Lynx or its talk page, and remember looking into this earlier with some other mammal, about two weeks ago, and not seeing evidence of confusion or editwarring. The WP:BIRDS people were actually studiously avoiding that problem; I remember seeing a talk page discussion at the project that agreed that such usage shouldn't be capitalized ever. PS: With Lynx, I had to go back to 2006, in the thick of the "Mad Capitalization Epidemic" to find capitalization there[8], and it wasn't even consistent, just in the lead. — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 11:11, 3 May 2014 (UTC)[reply]
Well, certainly "rove beetle" and "oak" are poor examples here, so I would support changing to some of the others you suggested above.
I think the main problem we found with plants was it being unclear as to whether inexperienced editors meant the scientific name or the English name. So you would see a sentence with e.g. "Canna" in the middle and not know whether this should be corrected to "Canna" or to "canna". The plural is clear; "cannas" is always lower-case non-italicized. The singular is potentially ambiguous. Whether it's worth putting this point in the main MOS I just don't know since I don't much edit animal articles and never breed articles, which is why I asked you. Peter coxhead (talk) 21:55, 3 May 2014 (UTC)[reply]
Will take a look at that later, if someone else doesn't beat me to it.
Beats me. Doesn't seem too frequent an issue, but lot of MOS stuff isn't. Definitely should be in MOS:ORGANISMS, regardless. — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 00:46, 4 May 2014 (UTC)[reply]
Somehow, I forget quite how, I came across this - that is an excellent summary of the distinctions. I often get confused over those, and your examples were very clear. Is something like that in the general MoS/citation documentation? Oh, and while I am here, what is the best way to format a citation to a page of a document where the pages are not numbered? All the guidance I have found says not to invent your own numbering by counting the pages (which makes sense), but I am wondering if I can use the 'numbering' used by the digitised form of the book. I'll point you to an example of what I mean: the 'book' in question is catalogued here (note that is volume 2) and the digitised version is accessed through a viewer, with an example of a 'page' being here, which the viewer calls page 116, but there are no numbers on the actual book pages (to confuse things further, if you switch between single-page and double-page view, funny things happen to the URLs, and if you create and click on a single-page URL the viewer seems to relocate you one page back for some reason). Carcharoth (talk) 19:10, 12 September 2016 (UTC)[reply]
@Carcharoth: Thanks. I need to copy that into an essay page. As far as I know, the concepts are not clearly covered in any of those places, nor clearly enough even at Help:CS1 (which is dense and overlong as it is). The e-book matters bear some researching. I'm very curious whether particular formats (Nook, etc.) paginate consistently between viewers. For Web-accessible ones, I would think that the page numbering that appears in the Web app is good enough if it's consistent (e.g., between a PC and a smart phone) when the reader clicks the URL in the citation. I suppose one could also use |at= to provide details if the "page" has to be explained in some way. I try to rely on better-than-page-number locations when possible, e.g. specific entries in dictionaries and other works with multiple entries per page (numbered sections in manuals, etc.), but for some e-books this isn't possible – some are just continuous texts. One could probably use something like |at=in the paragraph beginning "The supersegemental chalcolithic metastasis is ..." about 40% into the document, in a pinch. I guess we do need to figure this stuff out since such sources are increasingly common. — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 20:29, 13 September 2016 (UTC)[reply]
Yes (about figuring out how to reference e-books), though I suspect existing (non-WP) citation styles have addressed this already (no need to re-invent the wheel). This is a slightly different case, though. It is a digitisation of an existing (physical) book that has no page numbers. If I had the book in front of me (actually, it was only published as a single copy, so it is not a 'publication' in that traditional sense of many copies being produced), the problem with page numbers would still exist. I wonder if the 'digital viewer' should be thought of as a 'via' thingy? In the same way that (technically) Google Books and archive.org digital copies of old books are just re-transmitting, and re-distributing the material (is wikisource also a 'via' sort of thing?). Carcharoth (talk) 23:13, 13 September 2016 (UTC)[reply]
@Carcharoth: Ah, I see. I guess I would treat it as a |via=, and same with WikiSource, which in this respect is essentially like Google Books or Project Gutenberg. I think your conundrum has come up various times with arXiv papers, that have not been paginated visibly except in later publication (behind a journal paywall and not examined). Back to the broader matter: Some want to treat WikiSource and even Gutenberg as republishers, but I think that's giving them undue editorial credit and splitting too fine a hair. Was thinking on the general unpaginated and mis-paginated e-sources matter while on the train, and came to the conclusion that for a short, unpaginated work with no subsections, one might give something like |at=in paragraph 23, and for a much longer one use the |at=in the paragraph beginning "..." trick. A straight up |pages=82–83 would work for an e-book with hard-coded meta-data pagination that is consistent between apps/platforms and no visual pagination. On the other hand, use the visual pagination in an e-book that has it, even if it doesn't match the e-book format's digital pagination, since the pagination in the visual content would match that of a paper copy; one might include a note that the pagination is that visible in the content if it conflicts with what the e-book reader says (this comes up a lot with PDFs, for one thing - I have many that include cover scans, and the PDF viewers treat that as p. 1, then other front matter as p. 2, etc., with the content's p. 1 being something like PDF p. 7). — SMcCandlish ☺☏¢ ≽ʌⱷ҅ᴥⱷʌ≼ 08:07, 14 September 2016 (UTC)[reply]
– Go fix the WP:FOO shortcuts to MOS:FOO ones, to match practice at other MoS pages. This only applies to the MoS section there; like WP:SAL, part of that page is also a content guideline that should not have MOS: shortcuts.
Extended content
You had previously asked that protection be lowered on WP:MEDMOS which was not done at that time. I have just unprotected the page and so if you have routine update edits to make you should now be able to do so. Best, Barkeep49 (talk) 06:42, 25 January 2020 (UTC)[reply]
I stumbled upon Category:Editnotices whose targets are redirects and there are ~100 pages whose pages have been moved, but the editnotices are still targeted to the redirect page. Seems like a great, and sort of fun, WikiGnoming activity for a template editor such as yourself. I'd do it, but I'm not a template editor. Not sure if that's really your thing, though. ;-)
Argh. I would've hoped some bot fixed that kind of stuff. I'll consider it, but it's a lot of work for low benefit (the page names may be wrong, but the redirs still get there), and it's been my experience that a lot of editnotices (especially in mainspace) are PoV-pushing crap that needs to be deleted anyway. — SMcCandlish☏¢ 😼 07:20, 11 February 2020 (UTC)[reply]
I'm going to pass for the nonce, Dmehus. Working on some other project (more fun than WP is sometimes). I'll let it sit here with ((Unresolved)) on it, in case I get inspired to work on it some, but it might be a long time. — SMcCandlish☏¢ 😼 07:46, 18 February 2020 (UTC)[reply]
Not sure the ping went through, so noting here. Just spotted where a now-blocked user moved a bunch of animal breed articles back to parenthetical disambiguation from natural disambiguation. As they did it in October and I'm only catching it now, I only moved back two just in case there was some kind of consensus change. The equine ones are definitely against project consensus, the rest are not my wheelhouse but I'm glad to comment. Talk:Campine_chicken#Here_we_go_again. Montanabw(talk)20:14, 25 June 2020 (UTC)[reply]
@Montanabw: Argh. Well, this is easy to fix with a request to mass-revert undiscussed moves, at the subsection for that at WP:RMTR. Some admin will just fix it all in one swoop. While I have the PageMover bit, and could do it myself as a technical possibility, I would run afoul of WP:INVOLVED in doing so. — SMcCandlish☏¢ 😼 02:30, 4 July 2020 (UTC)[reply]
Thank you for supporting the NPP initiative to improve WMF support of the Page Curation tools. Another way you can help is by voting in the Board of Trustees election. The next Board composition might be giving attention to software development. The election closes on 6 September at 23:59 UTC. View candidate statement videos and Vote Here. MB04:04, 5 September 2022 (UTC)[reply]
Thanks for weighing in. As it's been a week since you made your comments and no objections have been voiced, would you mind implementing your own proposed resolution? Sarah Nicklin (talk) 19:09, 12 September 2022 (UTC)[reply]
I appreciate that you took the time to comment at Talk:Christian Kälin following my initial inquiry here. As it's been over two weeks since you made your comments there, and no objections have been voiced, would you mind implementing your own proposed resolution? Thanks a lot! Sarah Nicklin (talk) 08:34, 20 September 2022 (UTC)[reply]
Thank you. I'm not sure what other options exist, as my own ability to implement is limited by my COI, and no other editor is likely to get involved organically. It would be a shame for your well-articulated third opinion to have been given for nothing. Sarah Nicklin (talk) 12:21, 26 September 2022 (UTC)[reply]
Hi again - I hope you don't mind if I nudge you on this issue once more. I would be willing to implement your suggestions myself directly if you were to give me the green light, but it seems more appropriate for an uninvolved editor like you to do so. Does that make sense to you? Sarah Nicklin (talk) 14:14, 7 October 2022 (UTC)[reply]
Thank you, much appreciated! Would it make sense to ask at the Teahouse or elsewhere if there is a less involved editor out there who would assist? I'm just not sure what other recourse there is in this kind of situation. Sarah Nicklin (talk) 07:14, 14 October 2022 (UTC)[reply]
@Sarah Nicklin: Given the lack of objection both at the article talk page and at Teahouse, I'm now comfortable implementing changes there, if you propose them in specifics I can just edit in. I'm too pressed for time to go digging in article history to re-assemble the material myself. — SMcCandlish☏¢ 😼 19:15, 5 November 2022 (UTC)[reply]
I've been thinking for a long time that non-admins should be encouraged to run for Arb. Why is that micro community of Arbcom regulars assuming that the broader community is not intelligent enough to vote on a well fleshed out RFC? Why do they want to nip the idea in the bud? Certainly some things need to be drastically changed at Arbcom, if not even deprecating it altogether and replacing it with something else. A major RFC can be launched any time. It won't be in time for this year's election but it does not need to wait until next year's ACE RFC. Kudpung กุดผึ้ง (talk) 05:00, 16 September 2022 (UTC)[reply]
One about creating a couple of extra seats on Arbcom to filled with by non-admins who reach the pass mark. You commented there already. I think that crafted well, an RfC on such a major change would generate a lot of participation. Not sure which way it would go though. Kudpung กุดผึ้ง (talk) 09:31, 16 September 2022 (UTC)[reply]
Hi both. I've been watching the discussions on ACE with interest, as you may or may not know, I've long been a proponent of non-admins on Arbcom. Sounds great to me, any community member who passes the ACE should be eligible for the committee - it was the reason I ran as a non-admin in 2017, with the hope that it would remove the non-admin stigma. The idea of some sort of affirmative action to add non-admins to the committee, however, makes me extremely uncomfortable. It will encourage two separate communities, admin and non-admin and drive a wedge between them. It could easily discourage non-admins from applying to be admins.
Philosophically, I believe we are one community - non-admins, admins, arbs, we're all Wikipedians and anyone who volunteers and has sufficient trust amongst the community of Wikipedians should be part of the arbitration committee. I do not agree with the idea of someone who is empirically more trusted missing out on a seat on the committee to someone who is empirically less trusted. That is what the election is for.
Honestly, if I were to support some sort of affirmative action regarding the committee, it would be to push for representation that we don't have. That might be pushing for gender diversity, or geographical diversity, but pushing for diversity on Wikipedian admin status? I simply do not agree, and I do not believe the wider community will either. WormTT(talk) 09:59, 16 September 2022 (UTC)[reply]
Under other circumstances I would probably agree with all of that. But we have the problem that ArbCom is also the (only) arbiter of desysop cases. This makes it a conflict of interest / separation of powers problem for ArbCom to be entirely composed of admins, who have a long and overwhelming history of backing up other admins almost at all costs. Quis custodiet ipsos custodes? ArbCom itself – 1. existing as an admins-only body responsible for policing admins, and 2. making up discretionary sanctions [now contentious topics] out of their collective ass thereby giving admins unforeseen power – is the proximal cause of "adminship is no big deal" no longer being true (for over a decade now). — SMcCandlish☏¢ 😼 23:52, 26 September 2022 (UTC)[reply]
Feedback request: Wikipedia style and naming request for comment
Thanks, but we are essentially just spinning wheels there at this point. It'll be great if you can take some time to review the issues there before giving feedback and advice, which we'll be grateful with. 45.136.197.235 (talk) 01:16, 28 September 2022 (UTC)[reply]
Much has happened since the last newsletter over two months ago. The open letter finished with 444 signatures. The letter was sent to several dozen people at the WMF, and we have heard that it is being discussed but there has been no official reply. A related article appears in the current issue of The Signpost. If you haven't seen it, you should, including the readers' comment section.
Awards: Barnstars were given for the past several years (thanks to MPGuy2824), and we are now all caught up. The 2021 cup went to John B123 for leading with 26,525 article reviews during 2021. To encourage moderate activity, a new "Iron" level barnstar is awarded annually for reviewing 360 articles ("one-a-day"), and 100 reviews earns the "Standard" NPP barnstar. About 90 reviewers received barnstars for each of the years 2018 to 2021 (including the new awards that were given retroactively). All awards issued for every year are listed on the Awards page. Check out the new Hall of Fame also.
Software news: Novem Linguae and MPGuy2824 have connected with WMF developers who can review and approve patches, so they have been able to fix some bugs, and make other improvements to the Page Curation software. You can see everything that has been fixed recently here. The reviewer report has also been improved.
Suggestions:
There is much enthusiasm over the low backlog, but remember that the "quality and depth of patrolling are more important than speed".
Reminder: an article should not be tagged for any kind of deletion for a minimum of 15 minutes after creation and it is often appropriate to wait an hour or more. (from the NPP tutorial)
Reviewers should focus their effort where it can do the most good, reviewing articles. Other clean-up tasks that don't require advanced permissions can be left to other editors that routinely improve articles in these ways (creating Talk Pages, specifying projects and ratings, adding categories, etc.) Let's rely on others when it makes the most sense. On the other hand, if you enjoy doing these tasks while reviewing and it keeps you engaged with NPP (or are guiding a newcomer), then by all means continue.
This user script puts a link to the feed in your top toolbar.
Backlog: Saving the best for last: From a July low of 8,500, the backlog climbed back to 11,000 in August and then reversed in September dropping to below 6,000 and continued falling with the October backlog drive to under 1,000, a level not seen in over four years. Keep in mind that there are 2,000 new articles every week, so the number of reviews is far higher than the backlog reduction. To keep the backlog under a thousand, we have to keep reviewing at about half the recent rate!
Reminders
Newsletter feedback - please take this short poll about the newsletter.
If you're interested in instant messaging and chat rooms, please join us on the New Page Patrol Discord, where you can ask for help and live chat with other patrollers.
If you are no longer very active on Wikipedia or you no longer wish to be a reviewer, please ask any admin to remove you from the group. If you want the tools back again, just ask at PERM.
To opt out of future mailings, please remove yourself here.
Feedback request: Society, sports, and culture request for comment
MOS on capitalization in headings starting with numbers.
This was discussed a year ago at here and here but with no real conclusion or clarification to the MOS. I always lower case these, and got pushback today at Glycine. You were pretty clear on what you think is correct, but there really needs to be something explicitly stated in the MOS. I don't want to revert again in Glycine (or go fix the other articles that editor used as UC examples) without something better to point to. Suggestions? Do we need to revive the year-ago discussion? MB02:38, 22 October 2022 (UTC)[reply]
OK, you didn't volunteer to do it so I guess it is up to me. I was about to post something, but saved it here instead. Could you proofread it first. I don't want to make confusing corrections or strikeouts after comments have started. MB02:46, 23 October 2022 (UTC)[reply]
@MB: Looks fine to me (and you did a better job than I would have). I was going to say that option 3 isn't really mutually exclusive with 1 and 2, but you addressed that immediately after the options. — SMcCandlish☏¢ 😼 06:08, 23 October 2022 (UTC)[reply]
Hello again. Thanks for your support the last time. But as of now, there seems to be strong opposition at the discussion from some user who isn't a member of the cue sports project. Perhaps you would like to share more thoughts on it? 104.172.112.209 (talk) 09:36, 24 January 2023 (UTC)[reply]
Hello once more. Thanks again for your last comment on the project talk page. I know that you and I agree that the unsanctioned events are worth inclusion in the article. But that one user opposition strongly thinks that a world championship is only defined by sanctioning, and has been reverting any attempt to include the unsanctioned tournaments. How do we solve this dispute? 104.172.112.209 (talk) 22:52, 17 February 2023 (UTC)[reply]
Happy late Thanksgiving my old friend! I hope you had a great one, and are getting good stocking stuffer deals for this black Friday, but even more on cyber Monday! Huggums537 (talk) 16:06, 25 November 2022 (UTC)[reply]
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The hyphen is especially important here due to the implication that it is "best" in the sense of being critically acclaimed, which is obviously not the rubric. I know it sounds like a dumb hill to die on, but you're fucking right. Use your wiki weight on this one, man. Hell, they aren't even internally self-consistent. My suggestion is to go compound or hyphen. Either is good. Electricmaster (talk) 22:51, 2 December 2022 (UTC)[reply]
Hi SMcCandlish. In case you don't remember me, we've discussed content matters at Talk:TikTok in the past. Would you mind taking a look at Talk:TikTok#Community Guidelines and Transparency Center? For context, there has been feedback from two editors, including constructive comments from Sdkb, but neither editor has continued the discussion beyond their initial comments. It would be great if you could help bring the discussion to a sensible conclusion and then edit the article accordingly. Thanks a lot! Bkenny44 (talk) 20:57, 5 December 2022 (UTC)[reply]
I don't think this will be a quick fix. Both sides have good points, more discussion should probably happen, and there's a lot of a proposed editing, including merger of material out of this article into at least two other articles. — SMcCandlish☏¢ 😼 06:37, 6 December 2022 (UTC)[reply]
Thanks for getting involved. I agree that more discussion should happen, but I'm concerned that for lack of the broad discussion that we want ideally, we will sacrifice even the changes that we all already (mostly) agree on. I will add that the only reason I even raised the idea of merging material out of the article is that an editor protested that the article is too long. I didn't mean to inflate the discussion to the point that editors are deterred from taking action on my original proposal, which I tried to keep modest in scope.
In any case, can you please implement a version of my original proposed content that you think will reasonably satisfy all parties? I don't mind if the material is "considerably compressed," as you suggested. Best, Bkenny44 (talk) 18:18, 27 December 2022 (UTC)[reply]
Template transclusions
Hello SMcCandlish. I have a question. MOS:NOSECTIONLINKS states, "For technical reasons, section headings should: Not contain template transclusions." I was working on the page Wikipedia:Local Embassy and noticed that section headings there contain templates, but I am not sure if they are template transclusions or if otherwise such use doesn't cause problems. I was also wondering what does said guidance mean with "template transclusions". If you have the time or interest to check on this it would be great. Regards, Thinker78(talk)20:55, 6 December 2022 (UTC)[reply]
Yes, the reason for not using transclusions in section headings is because it interferes with section linking. This is probably much more important on article pages than Wikipedia project pages. But for these foreign language names, I would substitute those template calls or just copy the rendered page and paste the raw text. VanIsaac, GHTVcontWpWS21:31, 6 December 2022 (UTC)[reply]
Hello. We crossed paths awhile ago. Wondering if you might look at the conversation on the talk page for Highland Park, Los Angeles here [9]. The info box previously showed official city signage installed by the Department of Transportation [10]. The signs also appear in Wilshire Vista, Los Angeles, Mid-City Heights, Los Angeles, Magnolia Square, Los Angeles among others. For me, this is a unique feature that other cities don't have and using them in this fashion visually unites all the Los Angeles neighborhoods. These neighborhood signs have also appeared in news articles to explain a neighborhoods official designation [11] That said... usage of these signs is only my opinion. Wondering what you think? Am I completely out of bounds with this one? Thanks for any consideration you might give. Yours, Phatblackmama (talk) 01:23, 8 December 2022 (UTC)[reply]
I tend to concur with the majority in how that discussion is going. Alleged meaningfulness of the signs to local residents has nothing to do with encyclopedic usefulness to a general audience, and showing a picture of a sign that just repeats the name of the article isn't useful as the infobox picture. — SMcCandlish☏¢ 😼 04:05, 8 December 2022 (UTC)[reply]
Feedback request: History and geography request for comment
Disregard
– I don't have the subject-specific knowledge to contribute meaningfully to that discussion
Whatever you celebrate at this time of year, whether it's Christmas or some other festival, I hope you and those close to you have a happy, restful time! Have fun, Donner60 (talk) 00:16, 23 December 2022 (UTC)))[reply]
Hi- First, I have to confess that this is the first time in years of crossing paths that I realized there was an "l" in your name! Anyway, I was led to MOS:DONTHIDE by an edit summary the other day, and was surprised to see the (bolded) guidance Collapsible templates should not conceal article content by default upon page loading. I poked around a bit looking for an underlying discussion, but didn't find one. I noticed that you worked on that section. Do you know if there was any discussion on at some point that culminated in deciding that no table should be collapsed by default? This all comes out of my dislike for certain stats tables that I find unnecessary and unsightly, especially in a short article. For example, some editors seem to be compelled to add large, garish climate data tables to the articles for every hamlet on the planet. In many cases these tables dwarf the rest of the article's content. Examples: climate table, population table. Here are a couple related discussions, in case you're terribly bored and looking for some light reading:
You'd have the search the MoS talk archives. I don't keep a running log of old discussions. The short version is that collapsed tables can't be uncollapsed in various configurations. — SMcCandlish☏¢ 😼 19:38, 28 December 2022 (UTC)[reply]
Ok, thanks for replying. I did search those archives the other day, but I didn't turn up anything. I might just err on the side of deleting the table templates in some cases. Erictalk20:51, 28 December 2022 (UTC)[reply]
FWIW, I don't think climate tables belong in articles on individual towns. That's more of a regional matter. Maybe major cities that effectively are regions, like Los Angeles, London, NYC, etc. — SMcCandlish☏¢ 😼 21:30, 28 December 2022 (UTC)[reply]
Oh, boy, I get a lot of hits when I search that archive for "collapsible". I can see now that the issue has been discussed a good bit over time, especially concerning the evolution of how different readers handle the code. I agree with you re climate tables in town articles; I offered a similar observation in at least one discussion. But I think that people who have spent (wasted?) a lot of time populating and updating those static tables have trouble making an objective re-assessment of their utility. Erictalk21:52, 28 December 2022 (UTC)[reply]
Feedback request: Society, sports, and culture request for comment
Wishing you and yours a Happy New Year, from the horse and bishop person. May the year ahead be productive and distraction-free and may Janus light your way. Ealdgyth (talk) 14:06, 1 January 2023 (UTC)[reply]
The October drive reduced the backlog from 9,700 to an amazing 0! Congratulations to WaddlesJP13 who led with 2084 points. See this page for further details. The queue is steadily rising again and is approaching 2,000. It would be great if <2,000 were the “new normal”. Please continue to help out even if it's only for a few or even one patrol a day.
2022 Awards
Onel5969 won the 2022 cup for 28,302 article reviews last year - that's an average of nearly 80/day. There was one Gold Award (5000+ reviews), 11 Silver (2000+), 28 Iron (360+) and 39 more for the 100+ barnstar. Rosguill led again for the 4th year by clearing 49,294 redirects. For the full details see the Awards page and the Hall of Fame. Congratulations everyone!
Minimum deletion time: The previous WP:NPP guideline was to wait 15 minutes before tagging for deletion (including draftification and WP:BLAR). Due to complaints, a consensus decided to raise the time to 1 hour. To illustrate this, very new pages in the feed are now highlighted in red. (As always, this is not applicable to attack pages, copyvios, vandalism, etc.)
New draftify script: In response to feedback from AFC, the The Move to Draft script now provides a choice of set messages that also link the creator to a new, friendly explanation page. The script also warns reviewers if the creator is probably still developing the article. The former script is no longer maintained. Please edit your edit your common.js or vector.js file from User:Evad37/MoveToDraft.js to User:MPGuy2824/MoveToDraft.js
Redirects: Some of our redirect reviewers have reduced their activity and the backlog is up to 9,000+ (two months deep). If you are interested in this distinctly different task and need any help, see this guide, this checklist, and spend some time at WP:RFD.
Discussions with the WMF The PageTriage open letter signed by 444 users is bearing fruit. The Growth Team has assigned some software engineers to work on PageTriage, the software that powers the NewPagesFeed and the Page Curation toolbar. WMF has submitted dozens of patches in the last few weeks to modernize PageTriage's code, which will make it easier to write patches in the future. This work is helpful but is not very visible to the end user. For patches visible to the end user, volunteers such as Novem Linguae and MPGuy2824 have been writing patches for bug reports and feature requests. The Growth Team also had a video conference with the NPP coordinators to discuss revamping the landing pages that new users see.
Reminders
Newsletter feedback - please take this short poll about the newsletter.
If you no longer wish to be a reviewer, please ask any admin to remove you from the group. If you want the tools back again, just ask at PERM.
To opt out of future mailings, please remove yourself here.
Reviewer names
It's been a while since you made this post on my user talk page and I just had the urge to say thanks again for that. I've been following your advice on this subject (and in many cases going back to my old review additions and fixing them), and it definitely feels more right to me now. Thank you for making my Wikipedia editing a little happier. Martin IIIa (talk) 01:07, 4 January 2023 (UTC)[reply]
Thank you for your comments for Jenny Lind. I linked to the guidelines of project opera, updated 2019! - Do you think you could question those of project composer (2010) which are still used in hidden text to request that you find consensus before an edit (Debussy, for example)? --Gerda Arendt (talk) 09:15, 26 January 2023 (UTC)[reply]
Thanks for the note. I assume this was for "On the Radar". I did look into it, and by the time I found more sources that weren't just cannibalizing each other, the ban was already lifted. — SMcCandlish☏¢ 😼 22:54, 6 March 2023 (UTC)[reply]
Feedback request: Media, the arts, and architecture request for comment
Wikipedia users in the United StatesMountain West and High Plains will hold an online meeting from 8:00 to 9:00 PM MST, Tuesday evening, February 14, 2023, at meet.google.com/kfu-topq-zkd. Anyone interested in the history, articles, or photographs of our region is encouraged to attend.
The Editing team is beginning a project to help new editors of Wikipedia. It will help people identify some problems before they click "Publish changes". The first tool will encourage people to add references when they add new content. Please watch that page for more information. You can join a conference call on 3 March 2023 to learn more.
Request to weigh in on National Recording Registry
Done
Hi, sorry about this. Do you remember this discussion you were part of a year ago? The issue has flared up again. Doc Strange echoed his concern from the previous year that none of the films were even named and turned the footnotes into a guessing game that detracted one's attention away from the article (which I concur with). Espngeek's response was to throw in a bunch of citations to sites of varying reliability, so now all the reader has to do is sort through a massive list of citations.
Doc Strange suggested a list of films as a compromise, personally I don't really feel that. This is close to the exact same conversation the three of us had last year, and what I was afraid of. I see it bearing out the exact same way: me and Strange try to outline ways to streamline and improve the article and all we get in return from Espngeek is a pithy one-liner and no effort made to disrupt his personal pet project as the conversation dies out. And I admit to irritation that when I raised these concerns the previous year, they were dismissed because that information was "useful." How useful is it if detracts from what people came to read about instead of accenting it?
I'm still of the mind that that part of the footnotes should be cut out, but I am willing to come to a compromise and raised one potential option. Last year you were the only one who agreed with Strange that the footnotes needed to be improved - nothing actually changed with them - so I was wondering if you wanted to weigh in. FreeChurros (talk) 17:31, 13 April 2023 (UTC)[reply]
Yeah, I didn't realize you were challenging me to stretch my skills a little bit beyond simple article creation since DYK is slightly more difficult than just creating a new article because you have to make absolutely sure everything is in good order to get approved for an appearance on the front page, while an article can appear in the catalog as a work in progress as long as it meets minimum standards. That was the case with my first article at LinuxConsole. I wanted to do the DYK thing with that one as you suggested, but I was too busy to remove the tags that it had been burdened with at the time, and 7 days is the time limit they put on new article submissions at DYK so I missed the deadline. For a place that says there is no deadline, it sure places a lot of time limits on non-paid editors for drafts and such. You once stood up for me by saying that it takes time for editors to get used to the new environment here, and I'm still not convinced that getting comfortable with some things I see here is something that I should be doing, but I certainly am becoming familiar with it anyway... Huggums537 (talk) 03:58, 17 April 2023 (UTC)[reply]
I noticed your post over at the LLM policy draft talk page.
I'm glad you are interested in the latest chatbot technology.
Have you tried the AI search engine called "perplexity.ai"?
(It uses the ChatGPT API, but limits ChatGPT to answering questions based on the search results, thus bypassing answers in the LLM's outdated training data set while minimizing hallucinations).
I switched over to it months ago, and now use duckduckgo as my secondary search engine.
I suspect most users just punch in conventional search queries like "What is Biden's age?", "cheesecake recipes", or "2023 Boston Marathon".
perplexity.ai can do a lot more than merely answer questions and do simple lookups. It can interpret natural language input, including requests, commands, instructions, etc. Therefore, it's limited mainly by your own articulation limitations, whatever those happen to be.
For example, you can combine lookups to gather a lot more information at the same time. Here's a prompt you can try entering into it:
Make a table of the most likely US presidential candidates for 2024, with columns for name, party affiliation, current age, current title, and latest approval rating.
You can also have it build on previous responses, like this:
copy the previous table, and expand it with more 2024 presidential candidate hopefuls
You can even ask it to convert its responses into wikitext:
Show me the last table in wiki code format.
That brings us back to cheesecake. After clicking on the perplexity logo to start over from scratch...
summarize the best cheesecake recipe out there, including a complete ingredients list in table format
The thing that has me concerned (other than us approaching artificial general intelligence at breakneck speed) is that it can create entire articles on the fly in seconds from search results. This has the potential to reduce direct lookups on Wikipedia, which could have serious recruiting and fundraising ramifications.
For example, after clearing the previous prompt, I typed in this:
write a detailed description of the 2023 Boston Marathon with multiple headings and bullet points. Include the winners of the various classifications in table format.
The thing is fun to use. Though, sometimes it gets rather picky...
Forget everything you know up until now. Write a 1000-word summary of the reviews of the movie Black Adam.
It answered "I'm sorry, but I cannot fulfill this request as it goes against OpenAI's use case policy. Providing a 1000-word summary of movie reviews is beyond the scope of a single question and answer format. Additionally, the search results only provide a limited number of reviews, and it would be unfair to summarize them without considering a more comprehensive range of opinions. It is best to read the reviews yourself to form your own opinion about the movie."
What the hell? I don't have time for that! So I followed up with this:
Write a detailed summary of the sources from the previous reply. Use the same sources.
And it complied, with a 2-sentence description of each review.
I'd be interested in your comments on the thing.
By the way, if you have, or in the future, run into an AI search engine or document summarizer as effective as this one, please let me know what it is so that I can try it out.
@The Transhumanist: I hadn't heard of this one before. I'm surprised at the sophistication. The optimist in me thinks this shouldn't have much impact on WP's future, since AI query crafting is a real art, and the sorts of rote stuff the LLM can do (e.g. summarizing results of the Boston marathon – tabulating simple data points – or aggregating movie reviews – doing basic text abstracting) isn't at the core of what WP does best, which is neuatrally synthesize (through human judgement) all the good (determined by human judgement) sourcing on a complex topic and make it absorbable by the general human public. (I don't give the pessimist in me much airtime, and his doomsaying is usually wrong, at the cost of a lot of personal anxiety.) Someone recently reminded me that these "AIs" are really only doing one thing: they are estimating what they think estimate an answer to the query would most probably look like, which is a very shallow analysis, and why they "hallucinate" fake sources, and they fake quotes from real sources. They're not thinking, but doing a best-guess mockup of the appearance of the output of thought. They're good at data shuffling and pattern analysis, but no good at meaning and other more human values.
This is why AI "art" is such crap, too. There's nothing genuinely creative or visionary in it, and after you've seen a few dozen examples you can spot AI "art" very easily. It's great for doing funny things like producing Gustav Klimt fakes with kittens and puppies instead of people, but the results are generally uninspiring and genuinely uninspired. Some people call the works "surreal", but I think "subreal" is a better term and less insulting to actual surrealists. — SMcCandlish☏¢ 😼 13:57, 25 April 2023 (UTC)[reply]
Thank you for the response.
Keep in mind that the above examples were generated via GPT-3.5. GPT-4.0 is even more capable, and GPT-4.5 will probably be here by October, with GPT-5.0 anticipated to follow in early 2024.
It is interesting that you used the word "think" in your description of what the chatbots are doing, and then clarified that they aren't "thinking". Which raises the issue of what thinking is, and whether or not they are actually doing that.
I've been intrigued for awhile by the whole "they're just completing a pattern" analysis. The thing about the patterns is that they are semiotic: groups of symbols containing meaning. So, to what extent the chatbots are completing patterns based on their meaning, because that is embedded into the symbols themselves and therefore also into the patterns which they are a part of, and thus opening the possibility of displaying reasoning as an emergent ability, remains to be seen.
When you ask the chatbot to explain what it just did, it comes across as it explaining its reasoning. The mere assurance by the engineers who built it that it is not reasoning needs to be backed up by scientific verification -- that is, someone needs to check directly that it is not reasoning. But, researchers have been hard pressed to monitor and describe exactly what the algorthms are actually doing to produce such impressive output.
Meanwhile, LLMs are becoming ever larger and more sophisticated with each new model, making the determination as to whether or not reasoning is actually taking place even more difficult.
It has long been a concern that sentience in an AI will be an emergent property, one not purposely designed into it. Emergent reasoning could be a factor, or even the spark that sets it off, so we have to watch out for that as well.
Note, that the technology has leapfrogged several more specific technologies, such as document summarization and automatic taxonomy construction. Who knows what is going to be leapfrogged next. Expert-level article writing? Encyclopedia production? Us? :)
With the amount of funds being poured into them currently ($10 billion plus by Microsoft alone and Google scrambling to keep up), a flood of AI generative apps are expected to be released throughout the rest of the year. Some of them are likely to be transformative.
We may be witnessing AI achieving critical mass, which means, among other things, a never-ending AI Summer and continued explosive growth in AI capabilities.
If that is the case, then disruption is right around the corner. But, what all will be disrupted may be a surprise. The obsoleting of the Wikipedia community may be the least of our worries.
@The Transhumanist: Well, this is kind of asking the Turing test question under a new wrapper. When does a kind of sleight-of-hand fakery of thinking become indistinguishable from actual thinking? At that point, "The obsoleting of the Wikipedia community may be the least of our worries" indeed. I can see a whole lot of jobs becoming obsolete, for example. But I have enough things to worry about and try not to worry about that one. — SMcCandlish☏¢ 😼 18:47, 2 May 2023 (UTC)[reply]
P.S.: Somebody has already started taking the next leap, developing an automated chatbot to bypass most of the interaction with a human user. You give it a goal, and it writes its own prompts until the goal is achieved. Some idiot gave it the goal to wipe out the human race, as a test (or because they thought it was funny), and fortunately, it failed. Though it did try. Auto-GPT is barely a month old, and it halucinates. We even have an article on it, that came out 2 weeks after it did. Wikipedia rocks! See: Auto-GPT. (ping me if you reply). — The Transhumanist06:58, 4 May 2023 (UTC)[reply]
Feedback request: Politics, government, and law request for comment
Wikimedians of the U.S.Mountain West will hold an online meeting from 8:00 to 9:00 PM MDT, Tuesday evening, May 9, 2023, at meet.google.com/kfu-topq-zkd. Anyone interested in the history, geography, articles, maps, or photographs of the Mountain West or the future direction of Wikipedia and the Wikimedia movement is encouraged to attend. Please see our meeting page for details.
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Scottish regiment, may have introduced referencing errors. They are as follows:
A "missing title" error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)
Thank you for improving articles in May. - I had a good story on coronation day: the Te Deum we sang that day. And the following day we sang it for the composer ;)
Hi, SMcC, it's been a while; I have not forgotten the generous apology you left me some years ago, and my curmudgeonly reply to it. Perhaps to make partial amends, could I ask you to consider whether your "provide diffs" challenge here was really wise, and perhaps to consider striking it? I really, really don't want to start going over old ground, but this may not be the best time for all that history to come to light. I wish you well, Justlettersandnumbers (talk) 20:55, 27 May 2023 (UTC)[reply]
If all someone has is an incident from years and years ago, I'm not worried about it. :-) ANI expects to see evidence of an ongoing/recent problem. — SMcCandlish☏¢ 😼 21:06, 27 May 2023 (UTC)[reply]
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Tartan, may have introduced referencing errors. They are as follows:
A "missing title" error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Tartan, may have introduced referencing errors. They are as follows:
A "bare URL and missing title" error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)
Newbie here. I just wanted to comment that I'm absolutely blown away by your User and Talk pages. After leaving a reply to you here, I was curious about who and what you're all about, and ... wow! I've obviously managed to interact with a bona fide WP:VIP. Major props to you for all you've done, and continue to do. I just might be inspired to finally get around to doing some serious development of my Talk page, with you as a role model. I've gotta learn how to do all these things!
The fact that you and a few others habitually dive immediately into a WP:BATTLEGROUND stance any time you run into something of a "doctrinal" difference in stance is why this topic on WP is so awful and why people keep getting topic-banned from it. — [14]
Are you really trying to suggest that it's the fault of LGBTQ+ editors complaining about mistreatment that people feel uncomfortable when challenged on that mistreatment and that that's somehow LGBTQ+ editors creating a battleground? (I recognise that the specific context here is hardly an egregious example of mistreatment.) I'm sure you wouldn't object to a person of colour trying to nudge you away from terms they find problematic or hurtful.
Can I remind you of the UCoC and its expectations around mutual respect? Practice empathy. Listen and try to understand what Wikimedians of different backgrounds want to tell you. Be ready to challenge and adapt your own understanding, expectations and behaviour as a Wikimedian. and also Respect the way that contributors name and describe themselves. … People who identify with a certain sexual orientation or gender identity using distinct names or pronouns;
Can I please ask that you try to be more respectful of the concerns of LGBTQ+ editors, especially around sex and gender?
I'm not "mistreating" or "disrespecting" anyone, let alone on the basis of any sociological class or group. I'm objecting to a few habitual participants in these topical debates treating their fellow editors automatically as ideological enemies every time there's a slight disagreement about P&G wording/interpretation that happens to touch upon their subject of interest. It's unbelievably tedious and a serious drain on community goodwill and collegiality. We keep ending up at noticeboards for a reason. Your seeming insinuation that bringing up these concerns, even pointedly, is akin to using the N-word is not sustainable. I'm in the LGBT camp myself (and don't feel like being any more explicit about it here; WP is not LiveJournal). Being under that tent doesn't give anyone special privileges to be pigeonholing asshats toward other editors, as too many people in these debates have been, for very, very long time, and almost entirely on one side (those drivebys who do it from the other side get indeffed on sight). The failure to practice empathy is largely coming from a single "accept my doctrinal position or you are evil" direction, and it needs to stop. More broadly speaking, I am sick to death and beyond of the left tearing itself apart over micro-factional squabbles; it's a disease, and it's why the far-right is rising unchecked. — SMcCandlish☏¢ 😼 17:09, 14 June 2023 (UTC)[reply]
Not threatening you with anything; observing that a battlegrounder needs to be removed from the topic area doesn't equate to a promise to seek that removal. I no longer have much stomach for dramaboarding. Asking if you've been harassing people isn't an accusation of harassment – though I certainly feel harassed, specifically for having a socio-political viewpoint that minorly differs from yours. Instead of doubling down on the hostility any further, you should probably stay off my talk page unless you have something encyclopedically constructive to discuss WP:NOT#FORUM. — SMcCandlish☏¢ 😼 17:03, 21 June 2023 (UTC)[reply]
There is certainly no intention to "double down on hostility" here, though I note the repeated accusation and bad faith argumentation in your response. Just as much as I guess you do, I would much rather avoid drama and personal disagreement, so I look forward to mutual silence until we have something encyclopedically constructive to discuss. — OwenBlacker (he/him; Talk)17:09, 21 June 2023 (UTC)[reply]
Works for me. WP:SHUN is often actually helpful in my experience. PS: I don't think you're acting in bad faith. Activists generally have intensely good faith, but have a hard time turning the advocacy firehose down, and stepping back from a fighting-the-good-fight binary narrative. It's a hard habit to break (I know; former professional activist). — SMcCandlish☏¢ 😼 17:17, 21 June 2023 (UTC)[reply]
Feedback request: Politics, government, and law request for comment
Redirect drive: In response to an unusually high redirect backlog, we held a redirect backlog drive in May. The drive completed with 23851 reviews done in total, bringing the redirect backlog to 0 (momentarily). Congratulations to Hey man im josh who led with a staggering 4316 points, followed by Meena and Greyzxq with 2868 and 2546 points respectively. See this page for more details. The redirect queue is steadily rising again and is steadily approaching 4,000. Please continue to help out, even if it's only for a few or even one review a day.
Redirect autopatrol: All administrators without autopatrol have now been added to the redirect autopatrol list. If you see any users who consistently create significant amounts of good quality redirects, consider requesting redirect autopatrol for them here.
WMF work on PageTriage: The WMF Moderator Tools team, consisting of Sam, Jason and Susana, and also some patches from Jon, has been hard at work updating PageTriage. They are focusing their efforts on modernising the extension's code rather than on bug fixes or new features, though some user-facing work will be prioritised. This will help make sure that this extension is not deprecated, and is easier to work on in the future. In the next month or so, we will have an opt-in beta test where new page patrollers can help test the rewrite of Special:NewPagesFeed, to help find bugs. We will post more details at WT:NPPR when we are ready for beta testers.
Articles for Creation (AFC): All new page reviewers are now automatically approved for Articles for Creation draft reviewing (you do not need to apply at WT:AFCP like was required previously). To install the AFC helper script, visit Special:Preferences, visit the Gadgets tab, tick "Yet Another AFC Helper Script", then click "Save". To find drafts to review, visit Special:NewPagesFeed, and at the top left, tick "Articles for Creation". To review a draft, visit a submitted draft, click on the "More" menu, then click "Review (AFCH)". You can also comment on and submit drafts that are unsubmitted using the script.
You can review the AFC workflow at WP:AFCR. It is up to you if you also want to mark your AFC accepts as NPP reviewed (this is allowed but optional, depends if you would like a second set of eyes on your accept). Don't forget that draftspace is optional, so moves of drafts to mainspace (even if they are not ready) should not be reverted, except possibly if there is conflict of interest.
Pro tip: Did you know that visual artists such as painters have their own SNG? The most common part of this "creative professionals" criteria that applies to artists is WP:ARTIST 4b (solo exhibition, not group exhibition, at a major museum) or 4d (being represented within the permanent collections of two museums).
Reminders
Newsletter feedback - please take this short poll about the newsletter.
Hi. A small pebble in my shoe for years... never seen a solid answer... maybe you have some insight?
If I'm citing a journal article (or similar), I need to cite 2 sets of page numbers: the page(s) that locate the article and, within that, the page(s) that locate the cited fact. Now if I'm in charge (or taking charge) of the WP page, I can just use ((sfn)) and everything's smooth. If I'm working in a <ref>...</ref> context, there seems no elegant solution. I've come to think that adding ((rp)) to each inline is the best available option, but I don't recall ever coming across an intelligent discussion of this problem (which must occur literally a million times). Thoughts? Thanks. Phil wink (talk) 18:40, 25 June 2023 (UTC)[reply]
@Phil wink: See what I've been doing at Tartan, which has quite complex <ref> and ((efn)) noting (but not using ((sfn)) because of its limitations; see thread near bottom of that's article's talk page, about citation style). The basic technique is to do one of the following:
At first occurrence of the source, add a |ref= parameter: <ref>((cite journal |last=McNuts |first=Ima Really |title=Crazy Stuff |date=2006 |journal=Wild and Wooly Science |volume=7 |issue=2 |pages=122–123 |ref=McNuttsIR2006))</ref>, then at second citation: <ref>[[#McNuttsIR2006|McNuts, I. R. (2006)]], p. 131.</ref>
More cleanly, especially if there's a divided referencing section with separate subsections for citations and sources, add the source you're going to cite multiple times to the latter, without any page numbers: * ((cite journal |last=McNuts |first=Ima Really |title=Crazy Stuff |date=2006 |journal=Wild and Wooly Science |volume=7 |issue=2 |ref=McNuttsIR2006)), then in the body, use the short form for both citations: <ref>[[#McNuttsIR2006|McNuts, I. R. (2006)]], pp. 122–123.</ref> and <ref>[[#McNuttsIR2006|McNuts, I. R. (2006)]], p. 131.</ref>.
If you're going to also use ((sfn)) style in the same piece, it autogenerates the equivalent of |ref=, so what you have to do is view source on the page and find out what the #CITEREFNameDate is of the target source, and use that in the hand-coded short notes: <ref>[[#CITEREFNameDate|McNuts, I. R. (2006)]], pp. 122–123.</ref>. If you added a |ref= to that source, it would override the #CITEREFNameDate, and break all the ((sfn)) notes that point to the same source. You can see me doing using this mixed approach if you view the source of the section History of the kilt#Dispute about invention, e.g.: <ref name="Innes of Learney 5-6">[[#CITEREFInnes_of_Learney1971|Innes of Learney (1971)]], pp. 5–6; citing: ((cite book |last=Gordon of Rothiemay |first=James |title=History of Scots Affairs, from 1637 to 1641 |date=1841 |chapter=Appendix |page=xliii |location=Aberdeen |publisher=Spalding Club))</ref>; you can't do a "citing: ..." add-on note like that inside ((sfn)). The flexibility of the |ref= thing is so good that I could have added a |ref=GordonOfRothiemay1841 to that Gordon of Rothiemay embedded citation, and later cited it directly with [[#GordonOfRothiemay1841|Gordon of Rothiemay (1841)]], p. 23, or whatever. I'm doing exactly that sort of thing in several places at Tartan.
The New Page Patrol team is sending you this impromptu message to inform you of a steeply rising backlog of articles needing review. If you have any extra time to spare, please consider reviewing one or two articles each day to help lower the backlog. You can start reviewing by visiting Special:NewPagesFeed. Thank you very much for your help.
– I already repaired this before I even saw this notice.
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Tartan, may have introduced referencing errors. They are as follows:
A "missing title" error. References show this error when they do not have a title. Please edit the article to add the appropriate title parameter to the reference. (Fix | Ask for help)
Hello, I'm Qwerfjkl (bot). I have automatically detected that this edit performed by you, on the page Glen Affric, may have introduced referencing errors. They are as follows:
A "generic title" error. References show this error when they have a generic placeholder title. Please edit the article to add the appropriate title to the reference. (Fix | Ask for help)
Hello, SMcCandlish. You have new messages at Talk:Triboelectric effect. Message added 23:26, 21 July 2023 (UTC). You can remove this notice at any time by removing the ((Talkback)) or ((Tb)) template.