User talk:PPelberg (WMF)/Archive 2
Question
[edit]How did you copy links to comments like [1]? I'm guessing you didn't write out the URL fragment by hand? ProcrastinatingReader (talk) 01:33, 8 March 2022 (UTC)
- hi @ProcrastinatingReader – I'm generating links to specific comments using a gadget the Editing Team created. If you'd like to try the gadget out for yourself, you can find instructions for installing it on mediawiki.org here: Topic:Wmredg44lh8v9x9i.
- Note: if you end up trying the feature and comments/questions/ideas emerge while you're using it, we'd value knowing what they are! PPelberg (WMF) (talk) 03:41, 8 March 2022 (UTC)
- Thanks! Will try it out. I suspect an issue might be that these links will stop working after a section is archived. Currently I've been using User:Evad37/TimestampDiffs which turns the timestamp into a diff link (eg [2]) but comes with the downside that you can't view the discussion after the comment without manually finding the section in archives. ProcrastinatingReader (talk) 12:41, 8 March 2022 (UTC)
I suspect an issue might be that these links will stop working after a section is archived.
- Good instinct. What you described above is accurate: the links this gadget produces will break if/when the comment to which they are linking is moved to a different page (e.g. archived, as you mentioned).
- With this said, the Editing Team is actively working on a way to offer genuine permalinks that will continue to function if/when a comment is moved or archived. This work is happening in T296801. PPelberg (WMF) (talk) 23:21, 8 March 2022 (UTC)
- Thanks! Will try it out. I suspect an issue might be that these links will stop working after a section is archived. Currently I've been using User:Evad37/TimestampDiffs which turns the timestamp into a diff link (eg [2]) but comes with the downside that you can't view the discussion after the comment without manually finding the section in archives. ProcrastinatingReader (talk) 12:41, 8 March 2022 (UTC)
The Signpost: 27 March 2022
[edit]- From the Signpost team: How The Signpost is documenting the 2022 Russian invasion of Ukraine
- News and notes: Of safety and anonymity
- Eyewitness Wikimedian, Kharkiv, Ukraine: Countering Russian aggression with a camera
- Eyewitness Wikimedian, Vinnytsia, Ukraine: War diary
- Eyewitness Wikimedian, Western Ukraine: Working with Wikipedia helps
- Disinformation report: The oligarchs' socks
- In the media: Ukraine, Russia, and even some other stuff
- Wikimedian perspective: My heroes from Russia, Ukraine & beyond
- Discussion report: Athletes are less notable now
- Technology report: 2022 Wikimedia Hackathon
- Arbitration report: Skeptics given heavenly judgement, whirlwind of Discord drama begins to spin for tropical cyclone editors
- Traffic report: War, what is it good for?
- Deletion report: Ukraine, werewolves, Ukraine, YouTube pundits, and Ukraine
- From the archives: Burn, baby burn
- Essay: Yes, the sky is blue
- Tips and tricks: Become a keyboard ninja
- On the bright side: The bright side of news
The Signpost: 24 April 2022
[edit]- News and notes: Double trouble
- In the media: The battlegrounds outside and inside Wikipedia
- Special report: Ukrainian Wikimedians during the war
- Eyewitness Wikimedian, Vinnytsia, Ukraine: War diary (Part 2)
- Technology report: 8-year-old attribution issues in Media Viewer
- Featured content: Wikipedia's best content from March
- Interview: On a war and a map
- Serendipity: Wikipedia loves photographs, but hates photographers
- Traffic report: Justice Jackson, the Smiths, and an invasion
- News from the WMF: How Smart is the SMART Copyright Act?
- Humour: Really huge message boxes
- From the archives: Wales resigned WMF board chair in 2006 reorganization
Phabricator tickets
[edit]Hi Peter! Lately I've found myself subscribed to a lot of Phabricator tasks, such as this one you authored. I enjoy being able to follow along with features as they're developed, but it's a little more than I can actively follow. Am I being directly added to tasks like that or is it happening (semi-)automatically because of something I followed elsewhere? {{u|Sdkb}} talk 21:49, 8 May 2022 (UTC)
- Yikes! I'm just now seeing this message, @Sdkb. I think you were getting auto-subscribed to tasks I filed as sub-tasks of tickets you had elected to file. Going forward, I'll be sure to make sure the subscriber lists don't get "copied" over in these cases. Thank you for stopping by to say something ^ _ ^ PPelberg (WMF) (talk) 23:43, 4 August 2022 (UTC)
The Signpost: 29 May 2022
[edit]- From the team: A changing of the guard
- News and notes: 2022 Wikimedia Board elections
- Community view: Have your say in the 2022 Wikimedia Foundation Board elections
- In the media: Putin, Jimbo, Musk and more
- Special report: Three stories of Ukrainian Wikimedians during the war
- Discussion report: Portals, April Fools, admin activity requirements and more
- WikiProject report: WikiProject COVID-19 revisited
- Technology report: A new video player for Wikimedia wikis
- Featured content: Featured content of April
- Interview: Wikipedia's pride
- Serendipity: Those thieving image farms
- Recent research: 35 million Twitter links analysed
- Tips and tricks: The reference desks of Wikipedia
- Traffic report: Strange highs and strange lows
- News from Diff: Winners of the Human rights and Environment special nomination by Wiki Loves Earth announced
- News from the WMF: The EU Digital Services Act: What’s the Deal with the Deal?
- From the archives: The Onion and Wikipedia
- Humour: A new crossword
The Signpost: 26 June 2022
[edit]- News and notes: WMF inks new rules on government-ordered takedowns, blasts Russian feds' censor demands, spends big bucks
- In the media: Editor given three-year sentence, big RfA makes news, Guy Standing takes it sitting down
- Special report: "Wikipedia's independence" or "Wikimedia's pile of dosh"?
- Featured content: Articles on Scots' clash, Yank's tux, Austrian's action flick deemed brilliant prose
- Recent research: Wikipedia versus academia (again), tables' "immortality" probed
- Serendipity: Was she really a Swiss lesbian automobile racer?
- News from the WMF: Wikimedia Enterprise signs first deals
- Gallery: Celebration of summer, winter
The Signpost: 1 August 2022
[edit]- From the editors: Rise of the machines, or something
- News and notes: Information considered harmful
- In the media: Censorship, medieval hoaxes, "pathetic supervillains", FB-WMF AI TL bid, dirty duchess deeds done dirt cheap
- Op-Ed: The "recession" affair
- Eyewitness Wikimedian, Vinnytsia, Ukraine: War diary (part 3)
- Community view: Youth culture and notability
- Opinion: Criminals among us
- Arbitration report: Winds of change blow for cyclone editors, deletion dustup draws toward denouement
- Deletion report: This is Gonzo Country
- Discussion report: Notability for train stations, notices for mobile editors, noticeboards for the rest of us
- Featured content: A little list with surprisingly few lists
- Tips and tricks: Cleaning up awful citations with Citation bot
- On the bright side: Ukrainian Wikimedians during the war — three (more) stories
- Essay: How to research an image
- Recent research: A century of rulemaking on Wikipedia analyzed
- Serendipity: Don't cite Wikipedia
- Gallery: A backstage pass
- From the archives: 2012 Russian Wikipedia shutdown as it happened
Thank you
[edit]Thanks for your mail.
Just to note though, please make sure you won't confuse my admittance of sometimes being difficult to deal with with an admission of wrongdoing. I don't always go easy on others, but I don't expect others to always go easy on me either, especially if I screwed up. Conflict can drive solutions and blowing off steam is generally healthy IMHO. User talk:Alexis Jazz/Bawl/preload starts with "Alexis Jazz, you messed up! (possibly) " for a reason.
Sometimes I can take things slightly too far, but even when that happens the only way to resolve differences is to keep talking. I was thankful when matmarex shared his hack to make windowed popups, but he didn't really respond to the several concerns I voiced about it.
I wonder if either matmarex or Esanders would have reported me to the TechConductCommittee. Being as vague as the committee is and having no return channel to the reporter really fosters speculation/paranoia. I doubt it was you, it might have been Aklapper but I somehow think he would have said something. I had interactions with both matmarex and Esanders in Phabricator tickets that were mostly tangentially related to VE, but I'm not sure I posted in any ticket about VE itself recently. Of course, someone I don't even know could have filed the report.
My current thought is "How hard would it be to implement a decent bugtracker on-wiki?" I think it would take 1-2 weeks to a useful prototype, but I'm not sure if/when I might try that. — Alexis Jazz (talk or ping me) 04:13, 2 August 2022 (UTC)
- hey @Alexis Jazz – I appreciate you following up with me here. I can understand you seeking answers to questions like the ones you've posed above. And while I don't think you were expecting me to be equipped to answer them, I thought it might be worth saying explicitly (so as to avoid any kind of ambiguity): I do not know anything about the message you received from the Code of Conduct/Committee. The above said, I'm motivated to do what we can to get these mobile edit notices out and available to people. I'll have an update about the Editing Team's work on this next week. PPelberg (WMF) (talk) 23:40, 4 August 2022 (UTC)
- I know you likely wouldn't have answers. Maybe if you'd happen to know (from private communication) who filed the report and that person would be okay with you telling me. But if that was the case you'd have told me by now. The only thing you could technically do (but have zero obligation to) is to ask TechConductCommittee to answer me as there is currently no indication they plan on telling me what their message is even about. They probably wouldn't give you personally any information, but if they gave me links I'd share them on-wiki.
There's one reason I can think of for you to consider that: it'll tell you something about how they operate. If they provide a reasonable answer, maybe the committee is slightly less terrible than I currently make them out to be. If they stonewall you, you'll know they are accountable to no one. Which could be handy to know.
Though I respect it's easier to keep your head down. Especially considering who signs your paycheck. If at any point it would come down to a choice between keeping your head down or having to worry about paying rent, I never could or would blame you for taking the paycheck.
As you may have noticed, keeping my head down is not a quality I possess or would like to possess.I'll have an update about the Editing Team's work on this next week.
Where will you post it? I'm guessing T312587? — Alexis Jazz (talk or ping me) 03:36, 5 August 2022 (UTC)Where will you post it? I'm guessing T312587
- @Alexis Jazz: yep, I'll be posting an update on phab:T312587 and Wikipedia_talk:EditNoticesOnMobile before this week is over.
- On the topic of the TechConductCommittee, would it be okay for us to agree to stop talking about this? Please know this question comes from a place of kindness and that I ask it in attempt for us to be on the same page about me not having anything to offer to this particular discussion. Note: I considered not addressing this topic at all in this response. Tho, I assumed you would value me sharing what I'm thinking rather than having to assume on my behalf. PPelberg (WMF) (talk) 01:51, 10 August 2022 (UTC)
- Thanks for being clear. I can only speculate what your motivation is. My request to you was to make a singular request, potentially a single line, to ask the committee to provide some links. I have at least 5 theories as to why you'd decline that request, but the why is irrelevant: you have no obligation to, so it's fine.
Similarly, I have no obligation to help the editing team (or anyone else), so I'll be minimizing my contributions to Phabricator. I've already skipped on reporting several bugs because I just don't care anymore. So unless an issue involves ENOM, don't count on my input.
There's been friction between the WMF and me, but I often understand both the community/user side and the developer side, and I can translate between the two. I thought about the possibility of applying for a paid position/contract/something at some point. Thanks to TechConductCommittee's (largely staffed by people on the WMF's payroll) unwillingness to answer a simple question, nobody has to worry about that anymore. I'm sure that's a relief for many.
I'll check your update once you post it. — Alexis Jazz (talk or ping me) 04:53, 10 August 2022 (UTC)
- Thanks for being clear. I can only speculate what your motivation is. My request to you was to make a singular request, potentially a single line, to ask the committee to provide some links. I have at least 5 theories as to why you'd decline that request, but the why is irrelevant: you have no obligation to, so it's fine.
- I know you likely wouldn't have answers. Maybe if you'd happen to know (from private communication) who filed the report and that person would be okay with you telling me. But if that was the case you'd have told me by now. The only thing you could technically do (but have zero obligation to) is to ask TechConductCommittee to answer me as there is currently no indication they plan on telling me what their message is even about. They probably wouldn't give you personally any information, but if they gave me links I'd share them on-wiki.
The Signpost: 31 August 2022
[edit]- News and notes: Admins wanted on English Wikipedia, IP editors not wanted on Farsi Wiki, donations wanted everywhere
- Special report: Wikimania 2022: no show, no show up?
- In the media: Truth or consequences? A tough month for truth
- Discussion report: Boarding the Trustees
- News from Wiki Education: 18 years a Wikipedian: what it means to me
- In focus: Thinking inside the box
- Tips and tricks: The unexpected rabbit hole of typo fixing in citations...
- Technology report: Vector (2022) deployment discussions happening now
- Serendipity: Two photos of every library on earth
- Featured content: Our man drills are safe for work, but our Labia is Fausta.
- Recent research: The dollar value of "official" external links
- Traffic report: What dreams (and heavily trafficked articles) may come
- Essay: Delete the junk!
- Humour: CommonsComix No. 1
- From the archives: 5, 10, and 15 years ago
The Signpost: 30 September 2022
[edit]- News and notes: Board vote results, bot's big GET, crat chat gives new mop, WMF seeks "sound logo" and "organizer lab"
- In the media: A few complaints and mild disagreements
- Special report: Decentralized Fundraising, Centralized Distribution
- Discussion report: Much ado about Fox News
- Traffic report: Kings and queens and VIPs
- Featured content: Farm-fresh content
- CommonsComix: CommonsComix 2: Paulus Moreelse
- From the archives: 5, 10, and 15 Years ago: September 2022
The Signpost: 31 October 2022
[edit]- From the team: A new goose on the roost
- News from the WMF: Governance updates from, and for, the Wikimedia Endowment
- Disinformation report: From Russia with WikiLove
- Featured content: Topics, lists, submarines and Gurl.com
- Serendipity: We all make mistakes – don’t we?
- Traffic report: Mama, they're in love with a criminal
The Signpost: 28 November 2022
[edit]- News and notes: English Wikipedia editors: "We don't need no stinking banners"
- In the media: "The most beautiful story on the Internet"
- Disinformation report: Missed and Dissed
- Book review: Writing the Revolution
- Technology report: Galactic dreams, encyclopedic reality
- Essay: The Six Million FP Man
- Tips and tricks: (Wiki)break stuff
- Recent research: Study deems COVID-19 editors smart and cool, questions of clarity and utility for WMF's proposed "Knowledge Integrity Risk Observatory"
- Featured content: A great month for featured articles
- Obituary: A tribute to Michael Gäbler
- From the archives: Five, ten, and fifteen years ago
- CommonsComix: Joker's trick
The Signpost: 1 January 2023
[edit]- Interview: ComplexRational's RfA debrief
- Technology report: Wikimedia Foundation's Abstract Wikipedia project "at substantial risk of failure"
- Essay: Mobile editing
- Arbitration report: Arbitration Committee Election 2022
- Recent research: Graham's Hierarchy of Disagreement in talk page disputes
- Featured content: Would you like to swing on a star?
- Traffic report: Football, football, football! Wikipedia Football Club!
- CommonsComix: #4: The Course of WikiEmpire
- From the archives: Five, ten, and fifteen years ago
The Signpost: 16 January 2023
[edit]- Special report: Coverage of 2022 bans reveals editors serving long sentences in Saudi Arabia since 2020
- News and notes: Revised Code of Conduct Enforcement Guidelines up for vote, WMF counsel departs, generative models under discussion
- In the media: Court orders user data in libel case, Saudi Wikipedia in the crosshairs, Larry Sanger at it again
- Technology report: View it! A new tool for image discovery
- In focus: Busting into Grand Central
- Serendipity: How I bought part of Wikipedia – for less than $100
- Featured content: Flip your lid
- Traffic report: The most viewed articles of 2022
- From the archives: Five, ten, and fifteen years ago
Testing phab:T326500
[edit]testing PPelberg (WMF) (talk) 19:53, 17 January 2023 (UTC)
Testing highlight
[edit]testing
PPelberg (WMF) (talk) 19:53, 17 January 2023 (UTC)
Wikimedia Hackathon 2023
[edit]Hello Sir... Hope you are fine?? I just applied for this year's hackathon... I'm hoping to be enlisted... Moreover I need more info on it... Thanks Yaw tuba (talk) 23:08, 24 January 2023 (UTC)
- hi, @Yaw tuba – I think the best place to ask questions about the hackathon is by visiting Wikimedia Hackathon 2023 and if you don't see the answer to the question(s) you have in mind, you might consider asking them on this talk page. I hope this helps! PPelberg (WMF) (talk) 18:13, 27 January 2023 (UTC)
- Oh okay.... Thanks a lot Yaw tuba (talk) 20:15, 27 January 2023 (UTC)