Wikinews

Wikinews:Water cooler/proposals/archives/2024/October

< Wikinews:Water cooler | proposals
This is an archive of past discussions from Wikinews:Water cooler/proposals/archives/2024. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current page.


New version of social bookmarks

The current social bookmarks template is outdated, and since it is one of the most widely used templates, I am proposing a new version for social bookmarks. There is currently an editprotected request open for this. Asked42 (talk) 17:39, 28 September 2024 (UTC)[reply]

Thanks I will check it out. Gryllida (talk) 12:07, 4 October 2024 (UTC)[reply]

More OR

To make news writing more fun I am suggesting to try to add OR to every submitted story. (They don't respond every time anyway.) Interview someone or request information from original sources which was not published elsewhere. This could make the Wikinews reports more unique and freshness issues would be less severe. Just a thought. Gryllida (talk) 11:09, 4 October 2024 (UTC)[reply]

Maybe the phrase is "more exclusive" 🙂 Gryllida (talk) 12:07, 4 October 2024 (UTC)[reply]

Communication venues and software

Hi, I am trying to understand how to make newswriting and reviewing easier. I've created a few proposals, which are noted in subsections below (split into separate sections to make it easier to reply individually).

(P.S. Your help with reviewing and editing in Newsroom would be appreciated now.)

Hope to hear what you think. Special ping to @Acagastya, @Heavy Water as we communicated about a part of the above elsewhere recently. However, input is welcome from everyone, of course.

Thanks and regards, Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]

Splitted updates on articles' talk pages

  • About collaboration, it was mostly happening in talk pages, so a busy reviewer cannot get a recap of recent discussions unless he or she checks recent drafts and each of their talk pages. I see it as a bit of a problem as it is time consuming. --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    I think the talk page is a great place for collaboration of a given article to happen. It's centrally located to the article and is "attached" to it making it easy to find for editors, reviewers, and readers of articles who may not be wikimedians. One problem that arises from that is when an article doesn't get published but it has important conversations happening in its talk page, which gets deleted if it isn't published. —Michael.C.Wright (Talk/Published) 12:50, 30 August 2024 (UTC)[reply]
    So we could copy some part of article talk or summarize on the /assistance water cooler at time of deletion if needed, especially if article was a great piece of work and there is an important lesson to be learned? Gryllida (talk) 22:27, 20 October 2024 (UTC)[reply]

IRC

  • IRC live chat could help a lot, Acagastya's bot announces article status changes there. My nick is "gry" and I am in UTC+10. --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    A challenge with IRC is that the conversation isn't kept as a record, where here in non-article talk pages and other pages, it is recorded. We need to ensure that our use of IRC as a communication channel doesn't exacerbate the problem I see in institutional knowledge; where a few people have exclusive knowledge on how the project works. That goes against the spirit of open knowledge and open collaboration.
    One of my previous employers was a large architecture firm. They had an entire department dedicated to Knowledge management. I think an eventual focus for en.WN, once we are able to routinely publish articles again, is to improve our knowledge management. —Michael.C.Wright (Talk/Published) 12:55, 30 August 2024 (UTC)[reply]
    I have privacy concerns with IRC being recorded. Can we probably just use it for now at least among reviewers and aim to summarize what was discussed on wiki - for time being? When news publishing speed goes up a bit we could probably revisie the question of having one irc channel that's publicly logged and another that's not if contributors want to discuss personal matters affecting availability and the like. Gryllida (talk) 22:28, 20 October 2024 (UTC)[reply]

Off-wiki notifications

  • As a rare example, loads of changes happened this year. dropped freshness standard. added pre reviews. requested help from stewards. other points here and there. i missed them all for half a year because my email was misconfigured. despite having a note on my user page that i use irc live chat a lot. I mean it is my fault but I am wondering, for those who do not edit the wiki every day and have too many emails, what is the best way to stay in the loop of what is happening? --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    @Gryllida freshness change wasn't this year. And the help requested was from the global sysops. Me Da Wikipedian (talk) 00:49, 29 August 2024 (UTC)[reply]
    "Last year, even better"? Yes, global sysops, thanks for clarifying it. Gryllida (talk) 01:02, 29 August 2024 (UTC)[reply]
    I personally think the best way to stay informed on the project is to stay engaged, at least at a minimum level. Log in and check wiki messages, watch lists, water cooler pages, etc. Spend a bit of time just reading what's happening or what is not happening that should be. If one can't engage at a minimum level by reading what is going on, they don't have the time to contribute; and that isn't a judgement against people without the time, we are all volunteers. But at a certain point, if one wants to remain informed in en.WN, they need to log in and catch up. —Michael.C.Wright (Talk/Published) 13:02, 30 August 2024 (UTC)[reply]
    Doubt majority of reviewers read all recent changes yet maybe they could be pinged on selected discussions with higher urgency or within their interest scope area? Off wiki notifications could help make them reachable? Gryllida (talk) 22:29, 20 October 2024 (UTC)[reply]

Android notifications

Water cooler for reviewing updates

  • For on-wiki communication might just pick one of the existing water coolers and use it for reviewers collaboration. I dunno which, but I will pick one and maybe if reviewers like then everyone can add it to watchlist to make things easier. It would get spammed with one section for each new draft and reviewers can leave notes like "I am taking this" or "Not me, sorry" and then key issues with the story. This would make stuff more challenging as the reviewers would need to read that place in addition to article talk page. Aftera point this could also get noisy on that page, though probably not for a few months. --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    I don't see how this is better than doing the same on the article's talk page, where it is logically attached to the article. I like the idea of reviewers 'calling the ball' and/or collaborating on a review. But in my time here, I haven't known of a case where we had a problem of too many reviewers or reviewers having a hard time collaborating on a review. I could be missing something due to their use of IRC, wiki messages, outside email, etc, but I haven't seen that to be a problem to solve. —Michael.C.Wright (Talk/Published) 13:07, 30 August 2024 (UTC)[reply]

Draft writing: 'save and keep editing' without waiting

  • For draft writing I find on-wiki editing problematic simply because I have to wait for the editor to load. I created a .html file on my computer which saves my draft in localStorage in browser. Even if I have a .docx file open or a notepad open then I can have editable text in front of me and save after each substantial edit without waiting to go into read only mode and then back again. On wiki I resolved this by having a "save and keep editing" button in the editor but with ui changes it stopped working around 3 years ago. Is this a problem for other contributors writing drafts? Is there a good solution? --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    I will often have a full, first draft created off-wiki and then cut/paste into wiki to complete. I then finish the article using source editor so that there is a bit of editing history of me linking to sister projects, related articles, infoboxes, categories, etc.
    Since I use source editor, I use the preview a lot. I also tend to follow the Wikipedia recommendation of small edits saved over time so they can be easily tracked and easily undone. I think this is especially important for the review process so that authors can better understand what was changed and why during the review. —Michael.C.Wright (Talk/Published) 13:11, 30 August 2024 (UTC)[reply]
    Thanks, I think I would a way to change to another source editor which has this feature. Gryllida (talk) 22:29, 20 October 2024 (UTC)[reply]
    I mean 'found' Gryllida (talk) 22:29, 20 October 2024 (UTC)[reply]

Reviewing by specialisation

  • For reviewing this is just hard. I can only motivate myself by reviewing stories local to my area or within an interesting topic. My user page has a link to WelcomeABit software that can categorize users into their preferred topic areas and deliver notifications to them when a new draft is created within their interest. Would you like to sign up to this? What improvements would you suggest - maybe some other place where to deliver notifications, irc, email, on wiki, where else? --Gryllida (talk) 11:22, 28 August 2024 (UTC)[reply]
    @Gryllida the issue with reviewing by specialisation is that there is 1 semi-active reviewer every few months around here, thats it. Me Da Wikipedian (talk) 12:24, 29 August 2024 (UTC)[reply]
    I know. I am trying to get more than one person involved in being notified, hoping that will eventually improve this situation. Gryllida (talk) 18:45, 29 August 2024 (UTC)[reply]
    In addition to MDW's point above, there are also so few articles being generated right now, that it is easy to stay on top of the review queue. I don't recall ever seeing double-digits in the review queue. So personally, I don't need notified if an article in my favorite category is up for review. I can quickly scan the headlines and know. This might be useful if the project were busy. —Michael.C.Wright (Talk/Published) 13:13, 30 August 2024 (UTC)[reply]
    @Michael.C.Wright there were double digits review queues when Cromium was active reviewing in the beginning of June. This is because (at least for me) I'm more likely to contribute if its more likely my contribution wont be thrown in the trash, so I think the review queue might grow as the number of active reviewers does. Me Da Wikipedian (talk) 15:39, 30 August 2024 (UTC)[reply]
    Hi @Me Da Wikipedian would you like to write something in one of the topic areas listed on my user page and see how well I will review it. I am testing the hypothesis that in my topic area it is easier for me to review. Gryllida (talk) 02:24, 3 September 2024 (UTC)[reply]
    @Gryllida your topics aren't on your user page (at least I didn't see them) but I'm pretty sure you said it was Australia, Science and Technology, right? Me Da Wikipedian (talk) 10:28, 3 September 2024 (UTC)[reply]
    Yup Gryllida (talk) 11:12, 3 September 2024 (UTC)[reply]

Theme

MassMessage

Hi @Acagastya I am proposing that the enwnbot sends messages not only to IRC but also using MassMessage to User:Gryllida/Notifications/New/Develop (new articles added to develop cat) and User:Gryllida/Notifications/New/Review (new articles added to review cat). And same for User:Gryllida/Notifications/New/Publish. Could you possibly code this, please? Gryllida (talk) 08:49, 6 October 2024 (UTC)[reply]

The program needs to check every min for new category members and if found, send a massmessage using mediawiki api. Anyone's help is very welcome. Gryllida (talk) 09:06, 6 October 2024 (UTC)[reply]

Guideline for AI-generated content

I have proposed a guideline for AI-generated content: The use of AI in generating content (WN:AI).

Maybe it should be a policy. Maybe we should forbid it altogether. What are your thoughts? —Michael.C.Wright (Talk/Published) 16:07, 18 October 2024 (UTC)[reply]

For what it's worth, see similar policies from d:Q116214731, b:en:Wikibooks:Artificial Intelligence, w:en:Wikipedia:Using neural network language models on Wikipedia, and m:Using neural network language models. —Justin (koavf)❤T☮C☺M☯ 16:21, 18 October 2024 (UTC)[reply]
Haven't encountered this issue frequently enough and there is no reliable way to check whether AI was used or not. So forbidding would be problematic. I tried using AI once and it got the event date wrong three times, all three times it said three different dates, and one was last year. .... Gryllida (talk) 22:31, 20 October 2024 (UTC)[reply]

Proposal summary 22:20, 20 October 2024 (UTC)

Hi, summary of proposals:

  • Date script by Asked42. One question.
  • To copy part of article talk to this page, if needed, before article deletion. Proposed by Gryllida. One comment. (Michael.C.Wright)
  • IRC live chat usage proposed by Gryllida. One comment from Michael.C.Wright expressing concern that it is not recorded.
  • Off-wiki notifications proposed by Gryllida. One comment from Michael.C.Wright noting it is best to read everything everywhere to catch up.
  • Android notifications proposed by Gryllida. No comments.
  • One page for review updates proposed by Gryllida. One comment from Michael.C.Wright suggesting to use talk pages. Gryllida is concerned reviewers are not in any way notified of new updates on talk pages, and reading all recent changes may be too much effort.
  • 'Save and keep editing' for draft proposed by Gryllida. One comment from Michael.C.Wright saying 'i do not use it, i edit on my pc before posting article on-wiki'.
  • Gryllida proposed reviewing by specialisation, someone wrote too hard when there is only 1.5 reviewers on site.
  • News writing theme proposed by Gryllida. Reviewing theme proposed by Michael.C.Wright. Same issue as in previous point.
  • Site banner/notice proposed to include note of review/drafts status. No comments.
  • New social bookmarks template proposed by Asked42. No comments.
  • More OR proposed by Gryllida. No comments.
  • Coding work needed for draft notifications through massmessage suggested by Gryllida. No response.
  • Guideline for AI generated content proposed by Michael.C.Wright. Koavf linked related pages.
  • Inline citations proposed by Michael.C.Wright. Gryllida noted it may be confusing and this is not Wikipedia.
  • Elsewhere Gryllida proposed mailing lists-like setup to get notifications on-wiki using MassMessage. No response was made.
  • Gryllida created tiny articles last week. They were easier to review, and were successfully published. Thanks to @RockerballAustralia. Gryllida is seeking to continue this effort.
  • Gryllida proposed 'review only date of event, and 5W, and no plagiarism' without verifying full article. If some statement is obviously unsourced it can be removed. This should make publishing process quicker. Link to proposal here.
  • Gryllida is suggesting to undo the status 'global sysops' of this wiki. Discussion is in following section.
  • @George Ho assisted with main page makelead. Thanks.

May I suggest that you all comment on the above, 90% of them are on this page and 10% are on another page linked here. This should be less time consuming than full reviews of anything.

I consider this an important participation as lack of support in coding, writing, reviewing, and feedback on the slightly more challenging situations hinders news writing; whereas participation in the above helps trenemdously, even if it is only a little note here or there.

Thanks. Gryllida (talk) 22:20, 20 October 2024 (UTC)[reply]

Script for quickly creating date categories.

Hello, everyone. There is a script that might help with easily and quickly creating (or updating) date and month category pages. This will let you know which pages are being created before they are created, so you can identify any mistakes. To use the script, add the following code to your common.js page: 

mw.loader.load('//en.wikinews.org/w/index.php?title=User:Asked42/QuickCat.js&action=raw&ctype=text/javascript');

After that, you also need to use the following code somewhere on your subpage to invoke the operation. Or just visit this subpage after installing the script, to access the form. 

<div id="category-create-form"></div>

Thank you! Asked42 (talk) 16:57, 6 June 2024 (UTC)[reply]

It can also be used for wikinews date and month list pages. Asked42 (talk) 18:40, 6 June 2024 (UTC)[reply]
Thanks and when would I need to use this? Gryllida (talk) 22:27, 20 October 2024 (UTC)[reply]
This script is useful when there is a need to create date categories and date list pages on Wikinews, which are usually generated manually, one by one. This task can be time consuming. By using the script, it becomes possible to quickly generate these pages by simply inputting the year, month, and selecting the type of pages to create (e.g. date categories, month categories, etc). Asked42 (talk) 10:17, 21 October 2024 (UTC)[reply]

Page UI for writing a new story

About engagement of readers on-wiki. What if there was a widget, which is full screen width, a textbox with a 'write' -- that'd go to headline, and take the users to new article writing page? Currently writing a story requires at least two clicks and one scrolling down, and knowing where to look.

The timeless skin ( https://en.wikinews.org/w/index.php?title=Main_Page&skin=timeless ) provides full screen width text box for search. A little JS could be written to add a pencil button near search button, which would take the user inputted text as headline, and open the article writing page (https://en.wikinews.org/w/index.php?action=edit&preload=Template%3ANew_page&editintro=Template%3ANew_article_intro&title=hi&create=Create+page).

Hence I propose

Option 1

  • add javascript which adds the pencil icon
  • change skin to timeless for all users who didn't edit their skin preference

Option 2

  • edit sidebar and add a box in it for writing a new article (a text box with a pencil) if software allows, if it does not, then do the same anyway using JavaScript
  • or a wiki extension, which will take weeks to approve but will behave more stable, because JavaScript is annoying

Option 3

  • add the text box and pencil button somewhere else in the page where I didn't think of it before

The target audience is visitors of main page and people who read articles. Gryllida (talk) 00:07, 29 August 2024 (UTC)[reply]

I think we need to hammer the basics first; write an article, review an article, publish an article. Once we are able to have an article a day published, then we can consider other widgets. We don't even have the manpower right now to effectively upgrade our copyright license, a project we have consensus on pursuing. —Michael.C.Wright (Talk/Published) 13:17, 30 August 2024 (UTC)[reply]
Good goal I will work toward it. Can you review 1.5 articles a day, of which 1 is a tiny article on a non-controversial topic? Gryllida (talk) 22:30, 20 October 2024 (UTC)[reply]
This is a volunteer project. I contribute my time when I'm able. In the past 30 days, I've used EasyPeerReview 18 times, nearly twice as much as the next-most-active reviewer. I believe we've had three active reviewers during this period. The second-most-active reviewer used the tool 10 times, and the third used it 7 times. Our review rate as a group is currently fewer than 1.5 articles per day.
To really affect the number of articles getting published, we need more active reviewers and a revised review process. How we achieve that is the million-dollar question. —Michael.C.Wright (Talk/Published) 13:58, 21 October 2024 (UTC)[reply]
Retrieved from "https://en.wikinews.org/w/index.php?title=Wikinews:Water_cooler/proposals/archives/2024/October&oldid=4830864"