| Revision as of 02:57, 5 December 2023 editIsaacl (talk | contribs)Extended confirmed users23,471 edits →New former editor-in-chief?: my mistake← Previous edit | Latest revision as of 03:57, 27 December 2024 edit undoCarrite (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers98,857 edits →Writer Request: ReplyTag: Reply | ||
| (132 intermediate revisions by 51 users not shown) | |||
| Line 24: | Line 24: | ||
| {{clear}} | {{clear}} | ||
| == |
== Vandalism Removal == | ||
| I've just found out that an IP ] me and another user from the list last month. Could we do something to prevent that? Thanks ] (]) 14:56, 15 November 2024 (UTC) | |||
| I'm sure not many people visit Signpost on mobile, but I've realised that the text wrap around images on Signpost articles isn't working well. I came to ] from a Depths of Wiki tweet, and the leading words of the obituary are unreadable due to being broken into fragments across many lines as it is pushed to the left of the image that already takes up much of the space. It is reproducible with other Signpost articles too. <span class="nowrap">—''']'''</span> <sup class="nowrap">(] • {]•]})</sup> 23:01, 18 August 2023 (UTC) | |||
| :{{Ping|JPxG}} should be easy for an admin to change page privileges?? ☆ <span style="white-space:nowrap;font-family: Papyrus">]</span> (]) 19:15, 18 November 2024 (UTC) | |||
| :Mobile is fucked, desktop is fucked, and I don't think anyone understands how the stylesheets work. The good news is that I might, soon, and then I will do my best to fix it. ''']'''×''']''' 04:25, 24 August 2023 (UTC) | |||
| ::Yeah, this is cooked. I do not see a single IP subscription in this whole list, which suggests there is no reason to not have it semiprotected -- have also taken the liberty of TE-move protecting it because inb4onwheels. <b style="font-family:monospace;color:#E35BD8">]×]]</b> 22:40, 18 November 2024 (UTC) | |||
| :{{ping|CX Zoom}} IDK what browser you're using but, if you increase the size of your ] within ] (by toggling 'Desktop site'‡ button under the hamburger menu) it reflows the page and things usually look fine… even on the dumpster fire mobile web version. Also: within the Misplaced Pages mobile apps, data comes off the Wikimedia API so, formatting is stripped, and images live on separate lines from text. Apps are buggy as all hell in their on right, however (often can't reply on this very page for example)… | |||
| : | |||
| :‡ not to be confused with the 'Desktop'/'Mobile view' button at bottom of Wiki pages. -- ] '''</sup></span>]] 07:23, 25 August 2023 (UTC) | |||
| ::]Thanks for letting me know that Browser's desktop mode fixes it, and I assume that is due to the fact that all elements (texts and images) appear to reduce in size in that mode allowing more space for complete words to appear. However, on the right you can see how a Signpost article with image in portrait mode looks like in mobile generally. Another way to view it would be to view it in landscape mode, but portrait mode should also work fine without needing to change mode or orientation. Thanks! <span class="nowrap">—''']'''</span> <sup class="nowrap">(] • {]•]})</sup> 07:41, 25 August 2023 (UTC) | |||
| :::It's primarily due to ] being shit and full of ]. Files are displayed within tables – rendering engine of the browser tries to wedge those tables into a tiny viewport, instead of doing sensible wordwrapping. The two coupled together = pain and suffering… with WMF web developers doing the flogging… Also doesn't matter if JP makes markup changes on their posts, as the mobile version here overrides competent formatting or markup choices. -- ] '''</sup></span>]] 08:53, 25 August 2023 (UTC) | |||
| ::::MediaWiki doesn't use tables for images. Editors do. —] (] • ]) 11:59, 26 September 2023 (UTC) | |||
| :::::So, is there some solution for this? <span class="nowrap">—''']'''</span> <sup class="nowrap">(] • {]•]})</sup> 16:00, 6 October 2023 (UTC) | |||
| == Writer Request == | |||
| == A few suggestions about the ''Signpost'' website == | |||
| I would like to help write stories for the Signpost as a official writer. Would that be possible. ] (]) 02:44, 28 November 2024 (UTC) | |||
| @] Hello, I just wanted to thank you again for implementing for the ''Signpost'': it definitely has got potential! | |||
| :Write something good and submit it. Then do it again. Then do it again. Then do it again. Then do it again. Then do it again. Voilà! ] (]) 03:57, 27 December 2024 (UTC) | |||
| I don't know if you already saw my comment on ], but I just wanted to point out a few graphical issues I've encountered over there. Firstly, some of the pictures included in the articles look misplaced and tend to "invade" quotes (like on , for example); secondly, I think the bold font used for the articles' headlines and paragraphs is a bit too hard on the eyes, since it appears to be in heavy contrast with everything else... | |||
| == Last (12-12-24) issue was not announced == | |||
| Speaking of high/low contrast, what about including an option to switch from a light background to a dark one, and vice versa? Anyway, keep it up, because you've already done a great job so far! : ) ] (]) 09:13, 16 September 2023 (UTC) | |||
| Or at least, not through MassMessage. Was that intentional? — ] ] 15:07, 15 December 2024 (UTC) | |||
| === Gallery issue at signpost.news === | |||
| :@] it was announced, ]. <span style="white-space:nowrap"><span style="font-family:monospace">'''<nowiki>''']<nowiki>]]'''</nowiki>'''</span> (] • ])</span> 15:33, 15 December 2024 (UTC) | |||
| ::Probably because I ask for it interwiki, at enws. Seems that all users of ] did not get it (). — ] ] 15:44, 15 December 2024 (UTC) | |||
| == Reply button is not working == | |||
| Featured pictures at signpost.news looks pretty bad. Somehow it turned the gallery into a bulleted list of thumbnails (or something). ☆ <span style="white-space:nowrap;font-family: Papyrus">]</span> (]) 18:46, 4 October 2023 (UTC) | |||
| == Watchlist notices == | |||
| While readinga signpost i tried to reply to a comment showing below the page but the button gave me error said | |||
| If I'm reading ] correctly, the Signpost hasn't had a watchlist notice since May. Is this a problem with the Signpost publishing script, or something else? Could it be fixed? This is the main way I was getting reminded to read the Signpost. | |||
| " Could not find the comment you're replying to on the page" | |||
| ] (]) 09:39, 25 December 2024 (UTC) | |||
| Is the Signpost still publishing bi-weekly? Was that a factor in watchlist notices getting declined? Personally I liked it when the Signpost published monthly instead of bi-weekly, so just throwing that out there. –] <small>(])</small> 16:09, 4 October 2023 (UTC) | |||
| :{{ping|R1F4T}} - try it now. If you are on the article page, click on the talk tab and then the "edit" or "+" links on the top line. This should work automatically every time, but I think sometimes for the first comment a bit of code gets accidentally removed in the prepublication process (and then it should be just like creating any other talk page). Maybe if the comment was removed while you were typing, you'd get messed up. Maybe if you are commenting on an old article, something different might be happening. ]<sub>(])</sub> | |||
| :I just put ] on my watchlist. The traffic on this talk page is low enough that nearly every time this page pops up on my watchlist, it's for a new issue. I think you can also get a notice delivered to your talk page. – ] (]) 16:22, 4 October 2023 (UTC) | |||
| ::{{replyto|Jonesey95}} To get a notification *only* about new issues without the talk page traffic, you can watch ]. For anyone who wants them, subscriptions are ]. ] (]) 12:23, 23 October 2023 (UTC) | |||
| :We got pushback from the community on using the watchlist notices when we made publication more frequent than monthly: see ]. I would not say it was consistent or overwhelming, but if somebody wanted to get it started again, it would probably need some kind of approval. The "monthly only" dictum might have spawned from the closure of ]. ☆ <span style="white-space:nowrap;font-family: Papyrus">]</span> (]) 16:33, 4 October 2023 (UTC) | |||
| ::Perhaps the publishing script could be modified to only request a watchlist notice once every other issue. –] <small>(])</small> 16:47, 4 October 2023 (UTC) | |||
| :::For context, {{section link|Misplaced Pages talk:Misplaced Pages Signpost/Newsroom/Archive 35|Watchlist notifications}} is where the last discussion on this can be seen. ] (]) 17:17, 4 October 2023 (UTC) | |||
| :::: I see the delivery notice on the user talk page of several colleagues. That's plenty for me; no need to put it in the watchlist header. ] (]) 11:02, 8 October 2023 (UTC) | |||
| == Ping JPxG == | |||
| @JPxG I emailed you an idea for a submission a few days ago but didn't hear back, even after after following up with {{t|ygm}} on your talk page. Can you confirm that you saw my email and/or I'm following the right process? ] ] 16:08, 3 November 2023 (UTC) | |||
| :{{u|JPxG}} fix ping ] ] 16:26, 3 November 2023 (UTC) | |||
| == New former editor-in-chief? == | |||
| I'm a bit confused by : is there a new former editor-in-chief who doesn't appear in {{section link|Misplaced Pages:Wikipedia_Signpost/About#Editors in chief}}? ] (]) 02:32, 5 December 2023 (UTC) | |||
| :That editor (called EricPupper at the time) declared themselves to be EiC in a moment of turnover at this project. I was already out as part of the team so I can't really speak to which issues EricPupper published. As I was a prior regime guy, I'll say no more. <span class="nowrap" style="font-family:copperplate gothic light;">] (])</span> 02:54, 5 December 2023 (UTC) | |||
| ::My mistake; I forgot (or didn't know about?) the account rename. ] (]) 02:57, 5 December 2023 (UTC) | |||
Latest revision as of 03:57, 27 December 2024
 | Please use this page for general or technical issues, praise, queries, or complaints related to The Signpost as a whole.
|
 | To help centralize discussions and keep related topics together, all talk pages of subpages of Misplaced Pages:Misplaced Pages Signpost except /Newsroom redirect here. |
|
|
|
|
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. | |
 (talk · chat) |
|---|
|
|
|
|
|
|
|
Recent changes: main · talk |
|
|
Vandalism Removal
I've just found out that an IP removed me and another user from the list last month. Could we do something to prevent that? Thanks Nobody (talk) 14:56, 15 November 2024 (UTC)
- @JPxG: should be easy for an admin to change page privileges?? ☆ Bri (talk) 19:15, 18 November 2024 (UTC)
- Yeah, this is cooked. I do not see a single IP subscription in this whole list, which suggests there is no reason to not have it semiprotected -- have also taken the liberty of TE-move protecting it because inb4onwheels. jp×g🗯️ 22:40, 18 November 2024 (UTC)
Writer Request
I would like to help write stories for the Signpost as a official writer. Would that be possible. WikiEditor5678910 (talk) 02:44, 28 November 2024 (UTC)
- Write something good and submit it. Then do it again. Then do it again. Then do it again. Then do it again. Then do it again. Voilà! Carrite (talk) 03:57, 27 December 2024 (UTC)
Last (12-12-24) issue was not announced
Or at least, not through MassMessage. Was that intentional? — Alien 3
3 3 15:07, 15 December 2024 (UTC)
- @Alien333 it was announced, for me at least. ''']''' (talk • contribs) 15:33, 15 December 2024 (UTC)
- Probably because I ask for it interwiki, at enws. Seems that all users of the interwiki list did not get it (random example). — Alien 3
3 3 15:44, 15 December 2024 (UTC)
- Probably because I ask for it interwiki, at enws. Seems that all users of the interwiki list did not get it (random example). — Alien 3
Reply button is not working
While readinga signpost i tried to reply to a comment showing below the page but the button gave me error said " Could not find the comment you're replying to on the page" R1F4T (talk) 09:39, 25 December 2024 (UTC)
- @R1F4T: - try it now. If you are on the article page, click on the talk tab and then the "edit" or "+" links on the top line. This should work automatically every time, but I think sometimes for the first comment a bit of code gets accidentally removed in the prepublication process (and then it should be just like creating any other talk page). Maybe if the comment was removed while you were typing, you'd get messed up. Maybe if you are commenting on an old article, something different might be happening. Smallbones(smalltalk)