Knowledge

User talk:Jappalang/Policy and guidelines stuff

Source 📝

82:
of books have also been used to declare some of them as unreliable (evidenced mostly in military and historical subjects). I believe the policies and guidelines are tailored to this method, as it is the most convenient form to get agreement and is the common practice in academics and business. The project passes off the judgment of accuracy to the "bigger party" because getting bogged down in disputes over reliability of so-and-so especially in obscure fields of study would prove to be non-productive. Imagine the edit wars and incivil incidents, especially for pop-culture subjects in this period of "free" publishing over the Internet, if the project has to debate over every source used in an article, or has to simply accept them all. The "filter" of commercially-judged reliability, biased or not, helps to cut down the arguments. It is unfortunate for the personal sites of the dedicated hobbyist, who has taken meticulous measures to ensure accuracy in his or her work but is unrecognized by the "commercial" sources.
65:, to be considered "reliable" a source must have "a reputation for fact-checking and accuracy"; elsewhere you state the same, the source "must show itself to have professional editorial standards and a reputation." But how exactly can this be shown? It seems to me that we rely on certain heuristics: it's declared "reliable" if it's closely associated with a dead tree publication or major media company, if it has been around for a while and makes enough money that people get paychecks as writers and editors, (sometimes) if it's run by someone well-known for writing for dead tree publication or other reliable sites, or (sometimes) if it happens to be credited more than a few times by other "reliable" sources; otherwise, it's declared "unreliable". A source that does have fact checking and accuracy but lacks the big-name endorsement seems to have little hope of surviving once the "wrong" people come around. 31: 134:
instead of the niche crowd. I believe this is happening with greater publications (mostly books), but as with all starting ventures, the effects are slow and require time to change perceptions. We might not see it in effect now, but perhaps 20–30 years later... In the meantime, we could work along Knowledge policies and guidelines, slowly expanding the pool of reliable sources that cannot be casually disputed and increasing the reputation of the project.
112:
can't even use the "expert in the field" clause to get around it, because even if the author knows everything about the topic there is nothing in "the field" to establish experthood. And even if there were a good way to recognize the dedicated hobbyist's experthood (I for one have no ideas there), it would never get consensus past those who would prefer every speck of popular culture be deleted from Knowledge.
160:
Regarding your comments in opposition to date autoformatting, I'd like to point out that one of the core features of any proposed replacement for the current autoformatting was that unregistered ("anon") users see a consistent format within any given article. That feature was actually implemented in
111:
is heavily biased towards academic subjects and mainstream news, as you said. I wish there were some way to keep the standards there while at the same time not eviscerate the non-academic, popular culture articles where peer-reviewed journals don't exist and major media doesn't care. In many cases we
281:
Thanks for continuing to discuss this; I think it's important a consensus is reached about how to use flags within F1 articles. For me, the most important thing is the prose part of the article, so while I can offer my opinion I'm not going to argue passionately as some do. Regardless, thank you for
181:
working, and tested by several users at MOSNUM, before the developer (UC_Bill) threw a fit elsewhere (unrelated to date issues) and quit the project. It was available for download from his site for a while, and somebody may still have a copy.. but in any case, it wasn't that hard to develop, and it
124:
We cannot totally blame the mainstream for this. Part of popular culture thrives on sensationalism, and academics and other "serious" studies frown on statements that try to play on the human emotions (several history books have derided ancient historic records for exaggerating accounts, and tried
81:
I kind of doubt I am one of those people listen to (nor do I have specific expertise in this area) ... Anyway, I do agree with what you say. On this project, reliable tends to mean association with a paper publication or major media company; however, the predisposition of the authors and reviews
176:
I'm sorry if you took offense to my message here. I wasn't trying to change your mind, I was trying to get you to make your reasons for opposition as clear as possible. As originally stated, they simply weren't applicable and left open the possibility of your opposition !vote being discounted as
133:
is not alone in this. A contributing factor to this is the rampant "fanboy-ism" that one faces on casually browsing through the web for anime or video game stuff. One thing the projects can hope is for there to be academic studies that are strictly objective that targets the mainstream audience
398:
Whats going on with this? I've had a look at the discussion on it, but I don't really understand. I'm only really concerned about the changes in relation to the Manchester United F.C. article; my understanding is that some changes have been made to the template, but how do I update these on the
254:
I'm contacting a few people who took an interest in the video games WikiProject guidelines last year, to let them know of a project I'm working on. It's strictly in the interest of collecting information, but I think that information could prove useful for refining our guidelines and policies.
104:
used to contain a short paragraph about what was changed in each remake, which seems to be a question that a lot of people ask in forums elsewhere. But we had to remove just about all of it, because all any "reliable" source mentions is that graphics were changed and a few extras
229:
Indeed. Actually, anons will see, in many cases, different formatting from the privileged few editors who insist on selecting a single month-day or day-month order. I dont' know where User Sapphic got this idea that these patches/article tags will make all uniform for all users.
100:, your opinions seem well-regarded there. It just disappoints me sometimes that there are some popular culture topics we simply cannot write about because the mainstream media doesn't think its worth covering. For example, 153: 161:
several different patches and demo systems that were created over the past few months of discussion, so it's entirely possible to have autoformatting that doesn't result in a mix of formats. --
170: 378:, although there are one or two minor issues. The "Vice Captain" one isn't a problem per-se, but a visual demonstration of the possible knock-on effect of narrowing the player name field. 154: 364: 61:
I've noticed you're one of the people that others listen to when discussion the reliability of online sources, and I'm hoping you can answer a question for me. According to
211: 375: 75: 346: 352: 125:
to downplay the events chronicled in ancient scripts for a more accurate re-telling). There is also the pervasive thought that "games are only for kids". I believe
337: 408: 360: 243: 392: 143: 119: 91: 191: 56: 223: 356: 271: 341: 318: 374:
Hi there. I've done some development based on the changes you wanted to make. A demonstration of all of them at work can be found at
295: 369: 206:
which you might like to add to your userspace to indicate your position. Having one in your userspace could deter unwanted
333: 202:
Hi there, Jappalang. I noticed that like me, you are opposed to any form of dates autoformatting. I have created some
388: 197: 259: 381:
The page above has wikilinks to the sandbox template source codes- feel free to edit any of them. Regards. --
249: 101: 38: 219: 139: 87: 385: 289: 8: 404: 267: 97: 47: 17: 329: 314: 306: 203: 187: 166: 323: 300: 215: 207: 116: 72: 382: 309:
yet? Are you interested? It does make vandalism reversion easier. Let me know.
284: 238: 182:
should be easy to reproduce, if the community decides they want that. Cheers, --
126: 46:
If you wish to start a new discussion or revive an old one, please do so on the
400: 263: 135: 83: 355:. Since you were involved in the old one, I figured I should invite you over. 310: 276: 183: 162: 130: 108: 62: 113: 69: 231: 332:
to see wether we can copy and past text from there into wikipeida.
155:
Knowledge:Date_formatting_and_linking_poll/Autoformatting_responses
177:"confused" about the situation. And a demo system 347:Notability-based restrictions for infobox credits? 129:also suffers from this reliable source issue, so 210:on your talk page. ;-) You will find the boxes 399:article so that it is MOS compliant? Thanks, 351:I've brought up a new discussion about this 305:I was surprised to see that you don't have 262:, if you find a moment. Thanks in advance, 14: 44:Do not edit the contents of this page. 96:I've been watching the discussion at 25: 57:"professional editorial standards"? 23: 24: 420: 29: 370:Template:Football squad player 67:I will watch here for replies. 13: 1: 342:19:04, 25 January 2010 (UTC) 7: 319:02:42, 16 August 2009 (UTC) 144:09:02, 3 January 2009 (UTC) 120:03:11, 3 January 2009 (UTC) 92:01:24, 3 January 2009 (UTC) 76:00:58, 3 January 2009 (UTC) 10: 425: 272:19:17, 29 April 2009 (UTC) 102:Final Fantasy (video game) 409:13:50, 22 July 2010 (UTC) 393:02:48, 21 July 2010 (UTC) 376:User:WFCforLife/Sandbox 4 365:16:17, 20 July 2010 (UTC) 296:05:28, 22 June 2009 (UTC) 244:06:37, 1 April 2009 (UTC) 224:06:35, 1 April 2009 (UTC) 192:01:30, 1 April 2009 (UTC) 171:00:34, 1 April 2009 (UTC) 198:Date autoformatting poll 282:your ongoing support. 328:Could you check this 42:of past discussions. 250:guideline discussion 18:User talk:Jappalang 260:at this discussion 68: 54: 53: 48:current talk page 416: 294: 292: 287: 258:Please check in 241: 236: 66: 33: 32: 26: 424: 423: 419: 418: 417: 415: 414: 413: 372: 349: 326: 303: 290: 285: 283: 279: 252: 239: 232: 200: 158: 59: 30: 22: 21: 20: 12: 11: 5: 422: 412: 411: 371: 368: 348: 345: 325: 322: 302: 299: 278: 275: 251: 248: 247: 246: 199: 196: 195: 194: 157: 152: 151: 150: 149: 148: 147: 146: 106: 58: 55: 52: 51: 34: 15: 9: 6: 4: 3: 2: 421: 410: 406: 402: 397: 396: 395: 394: 390: 387: 384: 379: 377: 367: 366: 362: 358: 354: 344: 343: 339: 335: 334:207.233.70.79 331: 321: 320: 316: 312: 308: 298: 297: 293: 288: 274: 273: 269: 265: 261: 256: 245: 242: 237: 235: 228: 227: 226: 225: 221: 217: 213: 209: 205: 193: 189: 185: 180: 175: 174: 173: 172: 168: 164: 156: 145: 141: 137: 132: 128: 123: 122: 121: 118: 115: 110: 107: 103: 99: 95: 94: 93: 89: 85: 80: 79: 78: 77: 74: 71: 64: 49: 45: 41: 40: 35: 28: 27: 19: 380: 373: 350: 327: 304: 280: 257: 253: 233: 201: 178: 159: 60: 43: 37: 216:Ohconfucius 36:This is an 357:Prime Blue 208:canvassing 264:Randomran 204:userboxes 136:Jappalang 84:Jappalang 324:Free use 311:Karanacs 307:rollback 301:Rollback 127:WP:ANIME 330:website 184:Sapphic 163:Sapphic 98:WT:VG/S 39:archive 286:Aptery 240:(talk) 114:Anomie 105:added. 70:Anomie 277:Flags 131:WP:VG 109:WP:RS 63:WP:RS 16:< 405:talk 361:talk 353:here 338:talk 315:talk 291:gial 268:talk 234:Tony 220:talk 212:here 188:talk 167:talk 140:talk 88:talk 401:Tom 391:-- 179:was 407:) 363:) 340:) 317:) 270:) 222:) 214:. 190:) 169:) 142:) 90:) 403:( 389:C 386:F 383:W 359:( 336:( 313:( 266:( 218:( 186:( 165:( 138:( 117:⚔ 86:( 73:⚔ 50:.

Index

User talk:Jappalang
archive
current talk page
WP:RS
Anomie

00:58, 3 January 2009 (UTC)
Jappalang
talk
01:24, 3 January 2009 (UTC)
WT:VG/S
Final Fantasy (video game)
WP:RS
Anomie

03:11, 3 January 2009 (UTC)
WP:ANIME
WP:VG
Jappalang
talk
09:02, 3 January 2009 (UTC)
Knowledge:Date_formatting_and_linking_poll/Autoformatting_responses
Sapphic
talk
00:34, 1 April 2009 (UTC)
Sapphic
talk
01:30, 1 April 2009 (UTC)
userboxes
canvassing

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.