"Protection restricts the modification of pages to specific groups of users. Pages are protected when there is disruption that cannot be prevented through other means, such as blocks. Wikipedia is built on the principle that anyone can edit, and therefore aims to have as many pages open for public editing as possible so that anyone can add material and correct issues. This policy states in detail the protection types and procedures for page protection and unprotection, and when each protection should and should not be applied."

These mechanisms do include a "Pending changes" mode: https://en.wikipedia.org/wiki/Wikipedia:Pending_changes

* Cite Unseen (https://meta.wikimedia.org/wiki/Cite_Unseen): show icons in an article's References section that indicate what the Wikipedia community knows about that source, such as whether a website is a known unreliable source - such as whether a source is banned on Russian and/or Ukrainian Wikipedia. [https://gitlab.wikimedia.org/kevinpayravi/cite-unseen]

* AI Source Verification (https://en.wikipedia.org/wiki/User:Alaexis/AI_Source_Verific...): use LLMs to help check whether the citations in an article support the claims, providing a summarized report. [https://github.com/alex-o-748/citation-checker-script]

* Suggestion Mode (https://www.mediawiki.org/wiki/VisualEditor/Suggestion_Mode): provide automatic in-line edit suggestions, including using small language models to detect potential tone issues. Demo: https://www.tiktok.com/@wikipedia/video/7634591061553237266?...

* Microtask Generator (https://meta.wikimedia.org/wiki/Research:Micro-task_Generato...): provide a list of prioritized edit suggestions based on the editor's choice of category. [https://gitlab.wikimedia.org/toolforge-repos/microtask-gener...]

* WikiTask Pro (https://nethahussain.github.io/wikitask-pro/ + https://github.com/nethahussain/wikitask-pro) - another approach to integrating signals to recommend potential edits to editors.

There are also interesting conversations happening about developing and maintaining better data about questionable sources - check out this amazing compilation: https://en.wikipedia.org/wiki/User:Kuru/fakesources

Some places to stay in touch with these things if you're interested: https://www.wikicred.org/ + https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AI_Tools (not all of these kinds of tools involve AI, but it's a component of various things people are working on). If you’re in the SF Bay Area, come to our meetups: https://en.wikipedia.org/wiki/Wikipedia:Bay_Area_Wikipedians...

Also, on the report abuse page that I got to from the user profile page, the green submit button is nearly hidden by the grey footer, even when I scroll the page around and complete the captcha.

They do good work, and it’s an important service. I believe it saves a ton of money for the federal government by reducing reinvention of the wheel. As a former federal employee and current federal contractor, it’s been very helpful to be able to use their no-cost-to-customer search services on multiple projects. On my current project we eventually shifted to doing our own search (using Postgres full text search) so we could customize the indexing and ranking, but Search.gov was a useful interim solution.

You can learn more about that project here, including the open source code: https://18f.gsa.gov/what-we-deliver/forest-service/ - and a few blog posts about it: https://18f.gsa.gov/tags/forest-service/

Both that Forest Service project and Federalist run on cloud.gov, which is a Platform as a Service operated by 18F.

(I work for 18F but don't officially represent it here.)

Also the salary cap is $161,900, as shown in this pay grade table for SF: https://www.opm.gov/policy-data-oversight/pay-leave/salaries... Not a top-of-the-line private sector salary, but not some kind of hardship.

Applying to 18F didn't require a drug test for me. The application process asks this question in the background check part (details at "security clearance" at the bottom of https://pages.18f.gov/joining-18f/how-to-apply/ for anyone curious), but answering yes to the "have you ever done federally-illegal drugs" question is not an automatic disqualification. It can be a disqualification depending on the details of the drug use.

We did sell out of tickets; our very graciously donated venue (thanks to Eventbrite) has an attendee limit since it's basically an office rather than a large venue. I hope you all will watch the streams! The talks will also be recorded so you can watch them later.

This is an unusually direct opportunity to share your expertise to help the entire U.S. federal government do a better job of building software.

The idea of the bot is to be mindful of gendered language when talking to your coworkers in your workplace, which is a different and slightly more formal context.

Comments URL: https://news.ycombinator.com/item?id=10241602

Points: 2

# Comments: 0