Commons talk:Mobile app/Feedback

Sorry for deletion

see: User talk:Krd#Bitte um Hilfe/Korretur Molgreen (talk) 08:55, 18 June 2023 (UTC)

Hello Krd thank you very much for your quick support. I do not realize how this happened to me and I hope that something like this will not happen to me again. (DE: Hallo Krd herzlichen Dank für Deine schnelle Unterstützung. Mir ist nicht klar, wie mir das passiert ist und ich hoffe, dass mir so etwas auch nicht wieder passiert.) --Molgreen (talk) 17:03, 18 June 2023 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. Molgreen (talk) 17:05, 18 June 2023 (UTC)

Archive resolved sections

In reaction to both a question of Molgreen on my usertalk page and an according ticket on GitHub resource for Android-Commons-app (Archive function for feedback page) let’s discuss it here, by the way also for the talk page itself. Pinging @Molgreen, Syced as former talk participants.

I read only resolved sections should be archived, which seems sensible. For this task we have to use template {{Autoarchive resolved section}}, and SpBot will do the archiving. Molgreen is right that it looks for {{section resolved|1=~~~~}} (important is a valid signature, included with ~~~~).

What I need to know are the wanted parameter settings. There is a sub template {{Autoarchive resolved section/usertalksetup}} which could be added and then fine tuned if the active values do not fit:

• archive parameter: Should there be an archive per year (a longer period is not possible) – done so with the usertalk setup – or is something like /Archive1 and counting preferred? The latter case needs some manual updating in longer terms, if an archive gets too large.
• age: How fast should sections declared as resolved be archived? The usertalk setup sets an age of seven days.
• Should it be hidden? In my opinion not necessary, note also the next item.
• If visible should there be a pointer to the archive or a least the arcive overview? I think this is useful. Also set by the usertalk setup.

@Syced: The template must be on the page itself. It must be somehow secured that it is placed on top of the page. I think it even worked if placed in bottom area, but the displayed parts should be on top of the page.
— Speravir – 22:15, 26 February 2024 (UTC)

I have meanwhile noticed that Kaartic has secretly started with archiving already earlier than I asked, and this in a way that definitively works only manually. For keeping it simple I by now think that annual archiving would be the best, instead. Just for the record: I would have added the mentioned template a while ago if the most recent reactions wouldn’t be on top. Keeping the archiving information on top is the main task I see here. — Speravir – 23:05, 20 March 2024 (UTC)

@Speravir Does this mean that sections could already be archived with {{section resolved|1=~~~~}}? (What do you have to do practically?)

How about implementing a variant that you think should work well. (That wouldn't be "bad" from my point of view. That's exactly why we're discussing it here). Molgreen (talk) 05:05, 21 March 2024 (UTC)

Molgreen, you could add {{section resolved|1=~~~~}} in sections you think they are out of date, but this will not have any effect until {{Autoarchive resolved section}} has been added. I already could have added this template with the parameter hidden show=no at bottom of the feedback page, but this is far from user friendly: You have to know that archiving is done, discover the embedded template, and have to find out yourself the address(es) of the archive(s). This is by the way also the issue I have with the actual archiving done by Kaartic which is even without any hint on the page itself (together with the address scheme which enforces manual archiving and watching the archive size). — Speravir – 01:18, 22 March 2024 (UTC)

I believe Template:Autoarchive resolved section needs to be at the top of the page, not the bottom. Anything at the bottom will be part of the last section, and will be archived with them - at least that's how ArchiverBot works, and I don't think SpBot is any different about that. We might want to change the section order from newest at the top to oldest at the top, to match the normal talk page structure. whym (talk) 11:38, 23 April 2024 (UTC)

Oh my gosh, I think you are absolutely right, Whym. How could I forget about this. So, the only possible clean solution would be what you wrote and was also my first intention, but according to Syced the app adds intentionally new reactions on top (cf. Syced's answer in archived thread on their talk page). Just another idea: We could try to set the template into a section that itself is prevented from archiving, but I do not know whether this works. In German lang Wikipedia there is a note in the template page that it has to be placed quite on top of a page, but this information is missing in Commons (and e.g. in Meta). — Speravir – 23:44, 23 April 2024 (UTC)

Actually, I think what I said was not accurate. ArchiverBot will definitely look for the template in the header - text written on top of the first section. I don't know if SpBot will do the same, or look for the template in the entire page. If the latter, it might work, as long as the template is in a section that's never archived. I think we can just try. whym (talk) 00:07, 25 April 2024 (UTC)