Title says it all.
Talk:Talk pages project/New topic/Flow
Forgot to tell you, but this is related to the DiscussionTools extension.
In a few rare cases set out by local project rules it might be necessary to not add a signature. How can one turn off the automatic signature?
This post was hidden by Tacsipacsi (history)
You just edit the page like you used to, instead of using DiscussionTools.
No longer, apparently.
Is there any way to disable this feature when I'm viewing an oldlink or diff? There's rarely a good reason to write a comment on an old revision (overwriting the new revisions), and it also scrolls me away from where I want to look most of the time. Theleekycauldron (talk) 16:40, 8 September 2023 (UTC)
There's rarely a good reason to write a comment on an old revision (overwriting the new revisions)
As far as I know, DiscussionTools never overwrites new revisions โ even if you write a comment on an older revision, it tries to insert in the newest revision, and doesnโt let you post the comment if itโs unable to do so (which may happen when replying, but not when creating new topics, as โadd to the bottomโ always works). I donโt say that auto-restore on old revisions is a good thing, but at least it wonโt destroy the page history.
I am often reading long pages in diff mode, and I particularly appreciate being able to post a Reply without having to leave the diff page.
Sure, but recovering unsaved changes for a comment written for a different diff? That just seems like a headache.
When I still have the other comment open in another tab, yes, it's a bit of a hassle. But I'd rather have that hassle (a few times a month, in my case) than to not be able to reply until I reload the whole page (i.e., on the order of 100 times a month).
can we enable replies on diff pages but not recover in-progress ones?
I don't know if it's realistically possible to detect that state. Probably @ESanders (WMF) would have an idea about that.
It might be possible to do this technically, but (1) this seems quite rare and (2) someone will then complain that it didn't recover their message if we change it. And then someone will ask to just make it a user preference...
It happens whenever I'm writing a comment on a page and need to check through that page's history for a diff to bring up. It doesn't seem insubstantial?
@Theleekycauldron, did I ever tell you about Ed's magic script? Look at line 4 in m:User:Whatamidoing (WMF)/global.js. It turns the timestamp for comments into a link. (Right-click to copy the link, so you can paste it into your comment.)
Oh, I've wanted that forever! :D thank you very much
I think it would be better to translate "New Topic Tool" in Japanese as "ๆฐใใ่ฉฑ้กใใผใซ".
Foomin10 ใใใ่ฒด้ใชใๆๆใใใใจใใใใใพใใ
ๆ่ฟใ่ฑ่ชใฎ็จ่ชใฏๆดๆฐใใใฆใใใใฅใผใใใใฏใใซๅคใใใพใใใ
ใใใจใๆ็คบใฎใๆฐใใ่ฉฑ้กใใผใซใใๅฝใฆใฏใใใใใใใใฏใพใๅฅๆกใใๆใกใงใฏใใใพใใใ๏ผ ใใใใใใฐไธ่จใฎ็ทใฎ็ฟป่จณใชใณใฏใ้ใใฆใๆดๆฐใใฆใใ ใใใจๅฉใใใพใใไปๅพใจใใใใใใ้กใใใใใพใใ
Hello, do you mind to check/update translation, please?
It has been updated from New discussions โ New topic.
| New |
New topic |
at: translate page.
This new talk page topic editor no longer has the insert toolbar (with Latin, symbols, Greek, etc.) characters. Please put it back. -- ๆฅๆฌ็ฉฃ Nihonjoe (talk) 19:33, 2 September 2022 (UTC)
hi @Nihonjoe โ are you referring to the special characters toolbar pictured below? If so, then this is functionality we will be introducing soon. If you'd like, you can track our progress by following this Phabricator task: T249072.
Thanks for the information. Okay then, how do I turn off the new editor and use the old one? I use that toolbar multiple times daily, and not having it makes things extremely difficult when I'm working on characters with macrons, umlauts, accents, and so on. -- ๆฅๆฌ็ฉฃ Nihonjoe (talk) 23:03, 2 September 2022 (UTC)
I use that toolbar multiple times daily, and not having it makes things extremely difficult when I'm working on characters with macrons, umlauts, accents, and so on.
Understood!
Okay then, how do I turn off the new editor and use the old one?
- Visit: Special:Preferences#mw-prefsection-editing
- Disable the "Enable quick topic adding" setting
- โ That's it
Thanks! -- ๆฅๆฌ็ฉฃ Nihonjoe (talk) 16:47, 6 September 2022 (UTC)
That ain't no good for anonymous user. And I mostly only need the line-break code, which does not occur by pressing Enter.
The good news is that the special character tool has become available in the reply and new topic tools in the meantime (unless you disable the toolbar, but doing so also requires logging in). Although I donโt know what line-break youโre speaking about, I donโt find a such thing in the special character toolbar of either the new topic tool or the edit toolbar of the legacy full-page editor (WikiEditor). (By the way, pressing Enter once indeed doesnโt create a line break indeed, as it has always been in wiki code. You need to press Enter twice to create a paragraph in unindented mode (new topic tool), one Enter works only in indented mode (reply tool).)
Still not returned, so sad!
What not returned? The special character tool has been available in DiscussionTools since November 2022. Did you actually check the tool before commenting here?
Was soll das? Warum gibt es bei dieser Pseudoverbesserung nicht die sonst รผblichen Helferlein unter dem Editorfenster um z.B. โโ einzufรผgen. Mal wieder eine Verschlimmbesserung
Leider gibt es noch keine Helferlein, aber hoffentlich wird es mรถglichst bald geben (sie werden ober statt unter dem Editorfenster sein, aber daran kann man sich gewรถhnen). Wenn du dich fรผr die Details interessierst, kannst du phab:T249072 folgen. In der Zwischenzeit kannst du anmelden (bzw. einen Benutzerkonto anlegen), damit du diese Funktion in deinen Einstellungen ausschalten kannst oder du kannst eine Browsererweiterung installieren, um den wichtigsten Sonderzeichen zu speichern. (Ich benutze zum Beispiel Clippings, aber es gibt sicher viele andere.)
This post was hidden by Tacsipacsi (history)
(For the benefit of those who read the original message with Google Translate: GT translates Verschlimmbesserung as improvement. It quite isnโt that.)
Man kann auch das ganzseitige Bearbeitungswerkzeug verwenden ("Quelltext bearbeiten" oben auf der Seite).
HI, could we get a preview of the Edit summary too when responding to a topic? Necessary with linking or pinging in the summary. Thanks!
hi @Bertux โ thank you for stopping by to share this feedback. While the Editing Team will not have room in our plans to add the functionality you're describing here, I have added this request to the ticket in Phabricator where we are tracking this idea: T274434.
Vote +1 for a preview feature.
Hi thereย :-)
Basically what the title says. Echo is installed and working for all other pages. Maybe somebody has a clue what the issue might be, maybe something hidden in the configs?
Kind regards
Artem
Before I used to have all functionalities of a Visual Editor when creating or responding to a talk page, more specifically adding urls or referencing Wiki pages; now I have to do it with code editor which is not only slow, but extremely annoying, I'm on my third attempt to write on someone's talk page and already on the brink of not writing at all... Please fix it back!!! ~~~~
Any time I go to RSN it will "helpfully" scroll me all the way down to the bottom -- even if I got there by clicking a section link -- and "helpfully" autofilling a bunch of text from a discussion thread I was going to open several months ago and didn't (because I looked in archives and someone had already brought it up). I tried pressing "cancel". Over and over. I even tried posting it with nonsense and then self-reverting, but that didn't work either, because it still paged me down to the bottom of the page. Does anyone know how to make it stop obsessively doing this? The current state of affairs is unacceptable and it is almost impossible for me to use the noticeboard.
Note that, apart from this, I think it's quite useful and am glad of it, although there is another bizarre bug on Android that I can't seem to fix, which is taht on my phone occasionally it decides that I can't move the cursor at all or select multiple characters or backspace them or anything (it just automatically moves my cursor to the very end of the text no matter what I do).
Can you think of pages where people adding new topics to them are instructed, via Edit notices or otherwise, *NOT* to sign the topics they post?
CONTEXT
We ask the above with the following in mind...
As we are currently thinking about the New Discussion Tool, people who have it enabled will notice that clicking a "New section" / "Add topic" link will lead them to the new tool. This new tool will automatically sign all sections created with it.
Before implementing the above, we would like to know if there are instances where this behavior would be disruptive.
On the English Wikipedia, there are some substituted templates that automatically include the user's signature, and this the user shouldn't include a duplicate signature. en:Template:Please_see is one example.
Yes, at the Teahouse on en-wiki, there was recently implemented a new 'Ask a Question' button which autosigned the first post by that new editor. It was intended to avoid the issue of new editors forgetting to sign, and then making more work for Teahouse hosts if Sinebot didn't autosign the question for them. (I'm not convinced that the extra 'hidden text' that is then visible when editing - especially in mobile view - makes a new editors life any easier, and we sometimes get double signature from those who already instinctively know they need to sign their posts. See a discussion about this and screenshots here. Any help/advice to improve the coding there would probably be appreciated - especially by @Sdkb, who implemented it for us)
...at the Teahouse on en-wiki, there was recently implemented a new 'Ask a Question' button which autosigned the first post by that new editor. It was intended to avoid the issue of new editors forgetting to sign, and then making more work for Teahouse hosts if Sinebot didn't autosign the question for them
@Nick Moyes it's great to see your name again! You sharing the above reminds me of a related question we are seeking an answer to and I think you, and perhaps @Sdkb are well positioned to answer...
Holding the design of the form aside for a second, have y'all observed cases where newcomers use the "New section" link/tab at Wikipedia:Teahouse instead of the "Ask a question" button? If so, what mistakes do you notice them making?
The question above sits within a separate and related investigation we're doing into how the new workflow for starting a new discussion will relate to the existing "New section" affordances. This task has some more context: phab: T263710.
cc @Iamjessklein
I agree with @Sdkb (below) that the Teahouse would happily adopt any method you provided us with of posting which makes that task easier for new editors to ask questions. We don't do things just to be different, but sometimes it is really hard to put oneself in the eyes of a brand new editor - we do try!
I certainly see quite a lot of new Teahouse posts where the poster has simply clicked edit and added a brand new question to the end of a completely unrelated topic. I probably have to deal with that myself maybe twice a week, though its hard to say how many such posts are made in total and handled by other Hosts. I usually deal with that simply by adding in an anodyne header title like" ==Question==" without any berating or advising the questioner as to what they did wrong.
Eek, I'm sorry for the late reply here, @Nick Moyes. A few comments and a question in response to what you shared here, below.
...the Teahouse would happily adopt any method you provided us with of posting which makes that task easier for new editors to ask questions
This is encouraging to hear. We anticipate having an initial design proposal to share this week. Would you be open to reviewing them once we have them posted?
...new Teahouse posts where the poster has simply clicked edit and added a brand new question to the end of a completely unrelated topic.
Interesting. This is leading me to think that in the usability test we have planned, we ought to be explicit about asking newcomers what they understand the "Add topic" and "Edit" tabs to mean.
I've added this to the Phabricator task where this work will be happening: phab:T243249.
@PPelberg (WMF)Yes, I think we'd be delighted to look over anything that might ease user interaction. @Sdkb has a better practical understanding than I do of templates and script operations, but we (or you) can bring anything up for general discussion on the Teahouse Talk page if you want wider input. We've recently had quite an influx there of new 'Teahouse Hosts' who will may probably bring a fresher perspective on engaging with new users than some of the older hands. (I would also note that I was also unaware of Wikipedia:WikiProject Usability which, to their credit, SDKB appears to be singlehandedly lifting from the doldrums. I've now added it to my watchlist.
I think we'd be delighted to look over anything that might ease user interaction...we (or you) can bring anything up for general discussion on the Teahouse Talk page if you want wider input.
Wonderful! Would you be up for posting an invitation for feedback at the Teahouse? I'm thinking it will be helpful for this to come from a familiar "face."
If this sounds good to you, please let me know if there is particular information/language you think would be helpful to have from beyond what we're planning to share (see below).
New Discussion Tool feedback
Below is a list of what we plan to include in the post we make on mw.org inviting people to share feedback about the New Discussion Tool mockups:
- Mockups showing the proposed design
- Mockups showing the current "Add topic" experience/workflow
- The specific feedback questions we are seeking peoples' input on/answers to
- The scope of changes we considered for this round of mockups (e.g. we didn't focus on the initial call to action in this iteration)
They do indeed sometimes use that button, or the general "edit" button, which can cause problems. You might be interested in this discussion.
I'd add the caveat, though (and this is sort of related to my reply to Nick), that the en-WP Teahouse is a very non-standard space. It's non-standard because it tries to use workarounds to address the problems that make the normal way of doing things too unfriendly for beginners, but it would be better if the normal way was beginner-accessible enough that it could just be adopted there (i.e. what you're trying to do). So in most regards it's not the best place to use as precedent for making project-wide decisions.
...en-WP Teahouse is a very non-standard space. It's non-standard because it tries to use workarounds to address the problems that make the normal way of doing things too unfriendly for beginners, but it would be better if the normal way was beginner-accessible enough that it could just be adopted there (i.e. what you're trying to do)
Mmm, this is helpful context, @Sdkb and we agree. We are designing this new workflow/tool to be, as you described, "beginner-accessible."
As I mentioned to Nick above, would you be open to reviewing the design approaches we are considering taking for this new discussion tool once we post them on-wiki this week?
You might be interested in this discussion.
This is great; would it be accurate for me to understand you starting this particular conversation as a response to you observing newcomers face the following challenges?
- Newcomers are not clear which call to action ("Edit," "Add topic" or "Ask a question") they ought to use to ask the question they came to ask.
- It can be difficult for newcomers to post questions that comply with conventions considering 2 out of the 3 potential workflows ("Edit" and "Add topic") do not offer them any kind of guidance.
Yeah, I most likely will; just share it at WikiProject Usability or similar forums.
Awesome and woah, WikiProject_Usability, this is the first I've heard of this project. You sharing the mockups there would be wonderful, thank you! cc @JKlein (WMF).
By the way, I'm not sure if you saw, but I updated the comment above [i] with an additional question for you.
---
I'd say yes, those are both accurate descriptions of problems newcomers face at the Teahouse.
Understood, okay. Thank you for confirming.
Now, in response to the two issues you've highlighted here:
1. Newcomers are not clear which call to action ("Edit," "Add topic" or "Ask a question") they ought to use to ask the question they came to ask.
I've added this issue to the ticket [i] where we are accumulating the challenges people, across experiences level, face with how the actions, activity and content on talk pages are currently presented.
2. It can be difficult for newcomers to post questions that comply with conventions considering 2 out of the 3 potential workflows ("Edit" and "Add topic") do not offer them any kind of guidance.
To address the above, we're currently thinking about doing the following:
For people who have the New Discussion Tool enabled (eventually, we anticipate this tool be enabled for all newcomers by default), clicking on the "Add topic" will initiate the New Discussion Tool which, ideally, will lead people who are new to add new topics in ways that comply with wiki conventions (e.g. topics are signed, topic titles are defined and the entirety of the post is appended to the bottom of the page).
In parallel, we'll see in usability testing [ii] whether people seeking to start new conversation become distracted/confused by the "Edit" call to action. If they do, we're thinking we can explore drawing more attention to the "New topic" (exact copy TBD) affordance as part of the talk page "visual enhancements" work I mentioned above. [i]
If anything above prompts new thoughts or questions, we'll be keen to hear.
---
Thanks for the ping, @Nick Moyes. Templates that autosign are basically just a patchwork fix to the larger problem of discussion pages being too complicated for beginners to easily engage with. The new discussion tool being developed here will hopefully obviate the need for that sort of patchwork fix by addressing the more fundamental issue.
@Nick Moyes, @Pppery: Thanks for these. The tool will prevent duplicate signatures, so these cases should be ok. To clarify, we are looking for workflows where any signature at the end of the comment is undesirable.
Signatures are at least unnecessary on some pages, e.g., w:en:Wikipedia:Arbitration/Requests/Case/Portals/Workshop. I'm not sure anyone would complain if the comments were signed, though.
If you're starting an RFC at enwiki, then you might prefer a signature that includes the date only. A very long time ago, RFCs at the English Wikipedia were supposed to be dated but unsigned. I don't know what other wikis' practices are. @Gnom, is an unsigned discussion ever a good idea at the German-language Wikipedia? @Koavf, can you think of a wiki where editors prefer to have a new ==Section== for discussion started with no signature?
None come to mind.
Hi, I have to say I don't know where that would be the case.
@Pppery, @Nick Moyes, @Sdkb, @Koavf and @Gnom: we appreciate you putting thought to this.
It sounds like as far as everyone here is concerned, we're not currently aware of pages/contexts where it would be disruptive for the new sections posted there to contain their authors' signatures.
I've represented as much in the Phabricator ticket where this ticket grew out from: T262313#6490050.
Note: the above is not meant to suggest our quest for cases is complete!
@PPelberg (WMF)
I see this:
>This initiative sits within the Talk pages project, our teams larger effort to help contributors, across experience levels, communicate more easily on Wikipedia using talk pages. To accomplish this, we are building upon the Talk pages consultation 2019, and existing community conventions, to evolve existing wikitext talk pages.
Going up a level I see:
>It contains information about the goals of this work, the past efforts that have influenced it and why evolving talk pages is a priority right now.
(however the word goal appears only once in the document - in the introduction and nowhere else)
What I do not see is a document explaining the wmfs strategy in regards to improving talkpages: what is the overall purpose of this project, what are the timelines for implementation, which wmf-wikis are affected, etc.
The overall purpose is: to make it easier to participate in discussions.
The timeline is: Finish this year.
The wikis affected are: all of them. Eventually, all WMF wikis and most non-WMF third-party MediaWiki installations will likely want to use this.
User:Whatamidoing (WMF) Someneone enWQ VP was asking about lenghthy unarchived talkpages. Will this project fix that? Thanks in advance, BTW will this project be concluded this year?
Some of the work they did will make it easier to address archiving problems (e.g., broken links) in the future, but they will not address archiving directly.
I believe that they hope the project will conclude in June 2022. Also, it feels like everything has taken approximately twice as long as hoped for. Therefore, there's a chance that things will not be finished in June after all.
A case where adding the signature of an editor is not helpful is when manually archiving something. For example, when I am clerking for ArbCom on enwiki I will use the new section link to create a section which then contains the archived request. This shouldn't have my signature at the end as I'm not making a comment when archiving, but simply copying verbatim to a talk page so that it's archived. Pinging @PPelberg (WMF) as they said they were looking for use cases where signature addition would not be appropriate. This, however, is such a small use case that I think the clerk team could always adapt to just using wikitext editing to create the new section (instead of relying on the new section link).
My thought was that the edit interface could have a tickbox only shown to users who meet a certian condition which allows the removal of the users signature but defaults to adding it. This condition could be having a user right or alternatively having a preference set. This would prevent inexperienced users from accidentally or mistakenly clicking the disable signature option, but would allow users who understand when and when not to sign to not append the signature when manually archiving.
An example of this is w:en:Special:Permalink/1045395589#Clarification request: Antisemitism in Poland (September 2021) where I used the tool to create a section. My signature was added at the end, which I removed in a subsequent edit. Although removing the automatically appended signature does not take much time, it may be missed.
@Matma Rex, if I copy someone else's message to the correct talk page, what happens to the proposed [thank] button? Does it just fail to work, because there's no signature in the comment that aligns with the page history?
I don't know, I think we haven't even gotten to the point where we'd consider this yet. (Did you mean to ask this question in some different topic? I don't understand why it came up here.)
It came up here, because Dreamy Jazz (and all the enwiki ArbCom clerks) spend a lot of time rearranging pages. People frequently post things in the wrong place. If it's just moving the comment to a different place on the same page, I would expect the thank tool to find the original; if you move the comment to a different page, then I would expect it to get confused.
Perhaps it is a use case to remember for that magical future.