This is an old revision of this page, as edited by Lfernando18 (talk | contribs) at 09:13, 8 October 2023 (→javascript: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 09:13, 8 October 2023 by Lfernando18 (talk | contribs) (→javascript: new section)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)The project page associated with this talk page is an official policy on Misplaced Pages. Policies have wide acceptance among editors and are considered a standard for all users to follow. Please review policy editing recommendations before making any substantive change to this page. Always remember to keep cool when editing, and don't panic. | Shortcuts |
Text and/or other creative content from this version of Misplaced Pages:User access levels was copied or moved into Misplaced Pages:CheckUser with this edit on 10 January 2017. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists. |
Archives | |||||||
|
|||||||
This page has archives. Sections older than 180 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present. |
Should administrators be desysopped for undoing a checkuser block?
OP has been blocked. For those looking for the referenced thread, it's Misplaced Pages:Administrators' noticeboard/Archive353#Block of 2600:1017:B400:0:0:0:0:0/40 RoySmith (talk) 16:41, 7 July 2023 (UTC)The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Many years ago, the arbcom reminded users that checkusers have access to hidden information most of us don't. while it's accepted that undoing an arbcom decision lead to desysopping arbcom editors are usually held in an official light given they're nominated by a more rigorous process than the run of the mill RFA where all editor can simply support or oppose the request. That being said I would like to clarify
- are checkusers a subdivision of arbcom?
- given that a checkuser block can be restore like any other edit, would it be more prudent to AGF on the part person who reversed the block and simply restore the block? hundreds of accounts get indeffed and all too often the creator of these accounts end up in a vicious cycle of sock/block they can't escape.
- how exactly would regular admin unblocking a checkuserblock undermine the site's integrity? Shim119 (talk) 13:52, 7 July 2023 (UTC)
- This a crazy RfC. Much of the English is imprecise and borders on incomprehensible. I don't see why we should we be wasting our time on such an ill-considered RfC.--Bbb23 (talk) 14:03, 7 July 2023 (UTC)
- @Bbb23 Seems related to their Admin Review and ANI threads chasing after Daniel Case. I've left a comment at ANI. I'm just going to remove the RFC tag. This isn't even asking for a change to policy, just questioning it. -- ferret (talk) 14:23, 7 July 2023 (UTC)
CheckUser VRT Role Account
Hi,
I’m not sure what would need to happen to set this up — or if it would be technically prohibitive — but I was wondering if it would be possible to set up a CheckUser role account, similar to User:Oversight, for the purpose of sending emails through Misplaced Pages to the CheckUser VRT queue.
My reason for asking this is because the email linked to my WP account is an anonymous one, which I can reply to emails sent to, but can’t initiate emails from that specific address directly (or at least, I don’t think I can). Therefore, if I sent an email from my email client to the CheckUser email address, it wouldn’t be able to be verified to my account; whereas one sent through the Misplaced Pages interface would be.
Best, A smart kitten (talk) 11:52, 1 September 2023 (UTC)
The "contacting a checkuser" section.
Currently, it advises users to look at the "active users" list, which shows which user who happen to have CU bits have done literally anything lately, while Misplaced Pages:Arbitration Committee/Audit/Statistics shows who has been recently active as a CU. Should we replace and/or just add a link to the stats? Thoughts? Beeblebrox (talk) 18:51, 28 September 2023 (UTC)
- That makes sense to me. I'd go with prominently adding the stats, on the basis that more choice of information is good. -- zzuuzz 21:23, 28 September 2023 (UTC)
- I'd say both. Show the stats while letting them see who is currently active. Better to know that someone who has been using it frequently is around right now than know one or the other. TonyBallioni (talk) 01:47, 29 September 2023 (UTC)
javascript
High-level programming language Not to be confused with Java (programming language), Javanese script, or ECMAScript. ".js" redirects here. For the Microsoft dialect used in Internet Explorer, see JScript. For the uses of JavaScript on Misplaced Pages, see Misplaced Pages:WikiProject JavaScript.Screenshot of JavaScript source code | |
Paradigm | Multi-paradigm: event-driven, functional, imperative, procedural, object-oriented programming |
---|---|
Designed by | Brendan Eich of Netscape initially; others have also contributed to the ECMAScript standard |
First appeared | December 4, 1995; 29 years ago (1995-12-04) |
Typing discipline | Dynamic, weak, duck |
Filename extensions |
|
Website | ecma-international |
Major implementations | |
V8, JavaScriptCore, SpiderMonkey, Chakra | |
Influenced by | |
Java, Scheme, Self, AWK, HyperTalk | |
Influenced | |
ActionScript, AssemblyScript, CoffeeScript, Dart, Haxe, JS++, Opa, TypeScript | |
|
JavaScript (/ˈdʒɑːvəskrɪpt/), often abbreviated as JS, is a programming language that is one of the core technologies of the World Wide Web, alongside HTML and CSS. As of 2023, 98.7% of websites use JavaScript on the client side for webpage behavior, often incorporating third-party libraries. All major web browsers have a dedicated JavaScript engine to execute the code on users' devices.
JavaScript is a high-level, often just-in-time compiled language that conforms to the ECMAScript standard. It has dynamic typing, prototype-based object-orientation, and first-class functions. It is multi-paradigm, supporting event-driven, functional, and imperative programming styles. It has application programming interfaces (APIs) for working with text, dates, regular expressions, standard data structures, and the Document Object Model (DOM).
The ECMAScript standard does not include any input/output (I/O), such as networking, storage, or graphics facilities. In practice, the web browser or other runtime system provides JavaScript APIs for I/O.
JavaScript engines were originally used only in web browsers, but are now core components of some servers and a variety of applications. The most popular runtime system for this usage is Node.js.
Although Java and JavaScript are similar in name, syntax, and respective standard libraries, the two languages are distinct and differ greatly in design.
Return to JavaScript.
Misplaced Pages
Privacy policy Terms of UseDesktop
- "Netscape and Sun announce JavaScript, the Open, Cross-platform Object Scripting Language for Enterprise Networks and the Internet" (Press release). December 4, 1995. Archived from the original on 2007-09-16.
- "nodejs/node-eps". GitHub. Archived from the original on 2020-08-29. Retrieved 2018-07-05.
- Seibel, Peter (September 16, 2009). Coders at Work: Reflections on the Craft of Programming. ISBN 9781430219484. Archived from the original on December 24, 2020. Retrieved December 25, 2018.
Eich: The immediate concern at Netscape was it must look like Java.
- ^ Cite error: The named reference
origin
was invoked but never defined (see the help page). - "Popularity – Brendan Eich".
- "Brendan Eich: An Introduction to JavaScript, JSConf 2010". YouTube. p. 22m. Archived from the original on August 29, 2020. Retrieved November 25, 2019.
Eich: "function", eight letters, I was influenced by AWK.
- Eich, Brendan (1998). "Foreword". In Goodman, Danny (ed.). JavaScript Bible (3rd ed.). John Wiley & Sons. ISBN 0-7645-3188-3. LCCN 97078208. OCLC 38888873. OL 712205M.
- "Usage Statistics of JavaScript as Client-side Programming Language on Websites, July 2023". w3techs.com. Retrieved 2023-07-02.
- "ECMAScript® 2020 Language Specification". Archived from the original on 2020-05-08. Retrieved 2020-05-08.