Jump to content
Wikimedia Meta-Wiki

User talk:Donald Trung/Archive 1

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 6 years ago by MediaWiki message delivery in topic Learning Quarterly: November 2018

Template:Aan

Wikidata weekly summary #292

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Due to the Christmas and New Year's Eve holidays, no deployment will happen before January 3rd.
    • Monolingual language codes for Old French (fro) and Middle French (frm) added (phabricator:T181823)
    • Finishing touches on storing statements on Forms
    • No longer checking constraints on the property example statements (phabricator:T183267)
    • More work on caching constraint check results so we can roll out constraint checking for all logged in users

Wikidata weekly summary #293

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your first Wikidata Weekly Summary of the year 2018 (Calendar: Gregorian)!
  • Development
    • Fixed a problem with references in history of items (phab:T182767) Thanks to Matěj Suchánek who helped providing a workaround
    • Make statements on forms persistent for lexicographical data (phab:T163724)
    • Fix a bug that removed the collapse button (phab:T175492)
    • Remove cache constraint check results on purge (phab:T182107)
    • Add sitelinks to hif.wiktionary (phab:T180785)
    • Read constraint check results from cache and check freshness (phab:T182106)
    • Re-label the "Save" links to "Publish" (phab:T161367)

You can see all open tickets related to Wikidata here.


This Month in Education: December 2017

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
This Month in Education

Volume 6 | Issue 11 | December 2017

This monthly newsletter showcases the Wikipedia Education Program. It focuses on sharing: your ideas, stories, success and challenges. You can see past editions here. You can also volunteer to help publish the newsletter. Join the team! Finally, don't forget to subscribe!

In This Issue


Wikidata weekly summary #294

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development

This Month in GLAM: December 2017

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Headlines

To assist with preparing the newsletter, please visit the newsroom. Past editions may be viewed here.

If users want to start a nee topic here they should use "Add topic"

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Since a month has passed I'll start removing these off-topic links on sight. Honestly I'm also not comfortable with an user non probation welcoming newcomers. --Vituzzu (talk) 11:57, 14 January 2018 (UTC) Reply

Wikidata weekly summary #295

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Mahir256
    • Closed request for adminship: Jarekt (as successful)

The Signpost: 16 January 2018

[edit ]

Wikidata weekly summary #296

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: Mahir256 (as successful)

Wikidata weekly summary #297

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Constraint violations can now be checked on qualifiers and references (phab:T168532)
    • Implemented usage tracking deduplication to reduce database load (phab:T178079). This should not have any effect on what users see on recent changes and watchlists.
    • Redirects on client wikis that are connected to a Wikidata item can have a tracking category, if set up (phab:T185743). Thanks, Matěj!
    • Improved documentation of the pageterms query module (gerrit:406240). Thanks, Niedzielski!
    • Improved empty "content was:" in deletion logs for entities (phab:T184025)
    • Fixed links to external user pages in recent changes (phab:T183019)
    • Fixed user names beginning with a star sometimes being rendered as a list (phab:T182800)
    • Fixed constraint check results possibly showing up in the wrong language (phab:T185688)
    • Fixed ArticlePlaceholders possibly not showing up in search results (gerrit:406168)
    • Some of the developers attended to the Wikimedia Developer Summit 2018. You can find some notes on the Phabricator board

You can see all open tickets related to Wikidata here.


Learning Quarterly: January 2018

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

This Month in Education: January 2018

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Wikipedia Education globe
Wikipedia Education globe
This Month in Education

Volume 7 | Issue 1 | January 2018

This monthly newsletter showcases the Wikipedia Education Program. It focuses on sharing: your ideas, stories, success and challenges. You can see past editions here. You can also volunteer to help publish the newsletter. Join the team! Finally, don't forget to subscribe!

(追記) (追記ここまで)

In This Issue


The Signpost: 5 February 2018

[edit ]
News, reports and features from the English Wikipedia's weekly journal about Wikipedia and Wikimedia

Nieuwsbrief 68 Wikimedia Nederland

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

Wikidata weekly summary #298

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • We are saddened to report that Polish Wikimedian Krzysztof Machocki (who was also active on Wikidata) died on 31 January 2018, aged 36, after a couple of weeks of illness. Our condolences to his family and friends.
    • Notes of the IRC office hour of January 30th
    • The call for submissions for Wikimania (Cape Town, July 2018) is now open. Deadline is March 18th. Ideas of submissions related to Wikidata can be discussed here
    • Based on community discussions, the ArticlePlaceholder will soon be deployed on Urdu and Estonian Wikipedias.
    • Statistics
      • January 2018 brought us 9,770,248 edits, 445,027 new items were created.
      • The number of users that edited Wikidata per day grew in 2017 from 2439 to 2672 users, 9,6% more compared to 2016. The number of edits by them grew with 18% to 190k edits per day. We also get edited by 542 IP adresses per day, 50% more than in 2016.
      • In 2017, Wikidata got edited by 46 various bots per day, executing 334k edits per day (63% more than in 2016). The most active bot in 2017 was Emijrpbot, who added 18 million edits to Wikidata.
      • 284 million statements now contain references, compared to 67 million at the start of 2017. The average number of statements per item grew from 5 to almost 9. 73 million qualifiers are now used to provide more details for statements, 13 million in early 2017.
    • New tool based on Wikidata: Random TV episodes
  • Development
    • Diffs now show the entity ID in the page title (phab:T181077)
    • Improved handling of translations in the Query Service UI (gerrit:406301, gerrit:406996), thanks to Li Song
    • Continued working on diffs for forms on Lexemes (eg. phab:T186317)
    • Added summaries for edits on representations or grammatical features of a form (phab:T184702)
    • Worked on showing links to Lexemes and statements (phab:T185332)
    • Rolling out fine grain usage tracking on more wikis, so only relevant changes are shown in the watchlist and recent changes (phab:T185032)
    • Improved scalability of fine grain usage tracking (phab:T185693)

You can see all open tickets related to Wikidata here.


Wikidata weekly summary #299

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.

You can see all open tickets related to Wikidata here.

Wikidata weekly summary #300

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Welcome to the 300th Weekly Summary!

The weekly newsletter was started by Lydia at the very beginning of the Wikidata project, even before the first deployment, to keep the community informed about the developments, the new projects and tools. More than five years later, the newsletter is still there, its content powered by the community, and sent every week all along the years. I wanted to say a warm "thank you!" to each person who helped filling the Weekly Summary <3

Over the past years, as you know, Wikidata has grown a lot. More data, more tools, more editors and reusers, more exciting projects led by the community. The Weekly Summary has evolved with us, and the 300th edition seems a good moment to ask you all your suggestions about the newsletter, how it could continue evolving, and how you would like to improve it.

On that purpose, you can find a feedback page to express all your ideas about the Weekly Summary. We're very interested to know more about your reading habits, the parts you're more or less interested in, the new topics you would like to share with the community. Thanks in advance for filling it.

I stay available anytime to discuss with you, feel free to contact me if you have any question or concern! Cheers, Léa

  • A selection of cool tools on Wikidata

Here are a few tools that are recommended by some Wikidata community members. External websites, gadgets or scripts, they are very useful for Wikidata editors or users!

    • The Wikidata Query Service is an infinite source of amazing data and one of the best ways to explore and use Wikidata. (TweetsFactsAndQueries)
    • QuickStatements is a powerful tool that can edit or add Wikidata item en masse, via a text editor or importing a spreadsheet. (Éder Porto via Facebook)
    • Mix'n'match (manual), which helps us to interlink Wikidata with the rest of the web and the world :-) (Spinster, Siobhan via Twitter)
    • WikiShootMe! allows you to see Wikidata items plotted out on a map and shows you whether they have images or not. (Ham II)
    • Yair Rand's WikidataInfo script adds the QID of the equivalent Wikidata item to the page being viewed (on sister projects), along with its Wikidata label and description. (Andy Mabbett)
    • Recoin measures the degree of completeness of relevant properties of a Wikidata item and suggests any relevant statements that can be added to the item. (Rachmat04)
    • Template:Wikidata list ("Listeria") Self-updating lists on wiki pages, to drive projects and show results. Over 14,000 now live. (Jheald)
    • DuplicateReferences gadget adds a link to copy references and add them to other statements on the same item. (PKM)
    • checkConstraints gadget adds notifications on the interface to easily notice the violation of constraints and help people fixing them (Léa)
    • Resolve authors lists scientific articles with the property author name string (P2093) and groups them on the basis of co-authors and topic, which helps to distinguish people referred to by identical name strings. (Daniel Mietchen)
    • The Wiki Loves Monuments map is powered by Wikidata. You can look for a city and find the monuments around. (Stefano Sabatini via Facebook)
  • Development
    • Fixed incomplete "Label:", "Description:" and "Statement:" entity usage messages in various places (phab:T178090). Thanks, Matěj!
    • Improved violation messages for ranges involving the current date (e. g. "should not be in the future").
    • Continued work on caching constraint check results.
    • Enabled Lua fine-grained usage tracking for better performance on several more wikis: hywiki, frwiki, svwiki, itwiki, zhwiki, bewiki, nlwiki, glwiki, and Wikimedia Commons (phab:T187265 phab:T186714)
    • Representation and grammatical features of the form can be changed using the UI (WikibaseLexeme) (phab:T173743, phab:T160525)

You can see all open tickets related to Wikidata here.


The Signpost: 20 February 2018

[edit ]

Archive

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

Hi Donald, Do you wish for me to Archive your talk page here? --Artix Kreiger (Message Wall) 19:42, 20 February 2018 (UTC) Reply

Wikidata weekly summary #301

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Make it possible to link to Lexemes and Statements (phab:T1854997)
    • Disabling senses for the first release of Lexemes (phab:T186995)
    • Caching for constraints check

You can see all open tickets related to Wikidata here.


Nieuwsbrief 69 Wikimedia Nederland

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

Wikidata weekly summary #304

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
  • Development
    • Looking into current Lua usage to see where we can improve the Lua functions we provide (phab:T189506)
    • When there is a constraint violation in a reference, the reference is now automatically expanded to make it more visible (phab:T177970)
    • Looked into issues around notifying the Wikipedias about changes happening on Wikidata (sometimes delayed due to too quick bot editing) (phab:T189772)
    • Fixed some translation issues in the embeded part of the Query Service (phab:T188990)
    • Fixed an issue with usernames being broken for Wikidata changes in watchlist and RC on Wikipedia (phab:T189320)
    • Optimizing a heavily used database table (wb_terms) (phab:T188279)
    • Polishing a lot of things for lexicographical data first deployment
    • Make it possible to remove a Form (phab:T173332)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Template Wizard script available for testing

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

Hello. I'm contacting you because you voted for the Infobox Wizard in the 2017 Community Wishlist Survey.

The Infobox Wizard has gotten an upgrade - it's now a Template Wizard which works for infoboxes and all other templates. The feature is being developed as an extension (which will allow for localization) but there is a prototype user script which works well.

The Wishlist Team would love it if you could take a few minutes to try the Template Wizard prototype script out and give us feedback on whether it lives up to your expectations. This feedback will help build the script into an extension. To get started, add the following to your Special:MyPage/common.js -

mw.loader.load( 'https://en.wikipedia.org/w/index.php?title=User:Samwilson/TemplateWizard.js&action=raw&ctype=text/javascript' );

The Template Wizard will show up as a puzzle-piece icon in the 2010 WikiEditor. You can click on the icon to insert a template. Your thoughts are needed on whether it makes sense for the wizard to be available for all users by default or if there should be a preference for it. If it's a preference, what should the default be? Please leave your feedback here. Thank you! -- Keegan (WMF) (talk) 22:41, 28 March 2018 (UTC) Reply

Learning Quarterly: June 2018

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

L&E Newsletter / Volume 5 / Issue 16 / June 2018
Learning Quarterly

Stay tuned
blogs, events
& more!

Unblock

[edit ]
Latest comment: 7 years ago 1 comment1 person in discussion

@MarcoAurelio: I will leave Meta alone for a week, if you think that there are reasonable conditions for an unblock I will return after that week and request an unblock then, feel free to list those conditions below, because I don't want ro lose the ability to gain any user rights on other wiki's because of an indefinite block on Meta, and I have no intent on arguing about steward policy and global locks, if you think that a shorter block (a month or two) can also be used to sufficiently warn me against ever repeating that behaviour too then I will not comment on my talk page for the entire duration of a finite block.--Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 22:08, 10 February 2018 (UTC) Reply

Block

[edit ]
Latest comment: 7 years ago 9 comments4 people in discussion

@MarcoAurelio: What was wrong with symbolic voting? I just shared criticism of the way I was treated. I was "trolling" at all. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 19:54, 10 February 2018 (UTC) Reply

Also can you not blank my user page? as I don't want to make one for every small wiki I am active at.


(Edit conflict.)

This user is indefinitely blocked from editing Meta-Wiki. Do not unblock this user without first gaining consensus to do so. If you believe the block was placed in error, you may place an {{unblock}} request on your talk page. Please note that abuse of the privilege of editing your talk page will result in it being removed immediately. Thanks.

Unblock tools: block loggblock logblockliststalktoygucunblockgunblock • contribs: +/-


Your recent contributions after your global lock was lifted cannot be considered positive in any way, not even assuming the highest quotas of good faith in the wiki world. Feel free to request an unblock should you feel this block is innapropriate. —MarcoAurelio (talk) 19:57, 10 February 2018 (UTC) Reply

Only on Meta or in general? --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:01, 10 February 2018 (UTC) Reply
If my comments about stewards and admins are the issue I can stop as I wasn't planning on even bringing up stewards after this election, but I am not sure how criticism of a lack of communication can be seen as either "bad faith? Ot "trolling". --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:01, 10 February 2018 (UTC) Reply
So you think opposing all the running steward candidates to prove a point isn't disruptive? 212.117.188.19 20:04, 10 February 2018 (UTC) Reply
I just don't agree with the current culture, and how did I oppose -revi? --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:09, 10 February 2018 (UTC) Reply
Also if I had just voted "no" with no reason given )as some users fo) it would seem personal while I made it very clear that it wasn't. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:11, 10 February 2018 (UTC) Reply
Also if that comment is in general then I could say that I am one of the most active members on Wikimedia Commons which not exactly being "unproductive". --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:13, 10 February 2018 (UTC) Reply
what a charming confirmation of what you were complaining about. yet another drive by infinite - dissent = "'ad nauseam' trolling". i.e. "i don't want to hear it." the blocks will continue until the attitude improves. and threats of block for talking about mass deletions.
but no, they will not reform from within, (they will censor dissenting voices) it will require some imposition of a standard of practice from without. don't get mad, organize. Slowking4 (talk) 13:55, 14 February 2018 (UTC) Reply

email

[edit ]
Latest comment: 7 years ago 2 comments2 people in discussion

Just curious but why block my ability to e-mail if I don't even have an e-mail account linked to my Wikimedia account? Just ask at enwiki since my unlock I haven't e-mailed a single user.--Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:02, 10 February 2018 (UTC) Reply

Email can be blocked for a number of reasons. If you have the potential to send spam emails after attaching an email account, then your email may be blocked. Some admins always block email when blocking editors. Just understand that they are just doing everything they can to stop disruption. Ups and Downs () 20:02, 15 February 2018 (UTC) Reply

Votes

[edit ]
Latest comment: 7 years ago 7 comments4 people in discussion

Just a note that I have started a conversation at Talk:Stewards/Elections 2018 about whether the votes that led to the blocks should be struck. TonyBallioni (talk) 23:10, 10 February 2018 (UTC) Reply

@TonyBallioni: I endorse the struck. SA 13 Bro (talk) 23:23, 10 February 2018 (UTC) Reply
SA 13 Bro, I think the best place to have this discussion would be on the talk page I mentioned above. I notified Donald in case he wanted to make a response here for others to see. TonyBallioni (talk) 23:25, 10 February 2018 (UTC) Reply
@TonyBallioni:, I would understand for the copy-paste votes that were not directed at the individual, but it would give an odd impression to retroactively remove votes as other editors have voted "no" on multiple candidates without justification and f my votes were simply "no" with no other text accompanying them then this probably wouldn't have lead to a block in the first place as user Hindustanilanguage also massively voted against certain people in a previous election. I honestly have no intent in reading a conversation I am not allowed to participate in so I will not comment on the content of the conversation --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 06:19, 11 February 2018 (UTC) Reply
@Donald Trung: Sure other editors voted "no", but they did not mass vote candidates no like you did. Ups and Downs () 03:32, 16 February 2018 (UTC) Reply
I know that those votes lead to my block and if unblocked (based on that the block is no longer necessary because you understand what you are blocked for, you will not do it again, and you will make productive contributions) I could manually change my own vote based on studying each candidate, and make arguments as to why I would or wouldn't trust them, I can't recall anyone ever being banned for "voting wrong" before but I can see how a blanket vote can be seen as disruptive. I had just hoped that by seeing those comments someone would be inspired to bring the current policies up for discussion, but starting an RFC would probably be a better idea. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 10:47, 11 February 2018 (UTC) Reply
Or a full topic ban on anything related to stewards as I haven't been disruptive in other areas, I will fully respect the topic ban if that were to be deemed acceptable, a topic ban and a reduction of my block to a finite period (3 months or whatever is deemed necessary), as there are other areas of Meta where I would like to continue editing and I will not mention anything related to stewards or global locks on Meta ever again. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 12:48, 11 February 2018 (UTC) Reply

Conditions

[edit ]
Latest comment: 7 years ago 19 comments8 people in discussion

@MarcoAurelio: I will accept any reasonable conditions for an unblock, if y'all don't want me to comment about stewards as a group anymore then I won't, if I am not allowed to mention my global lock on Meta anymore I won't, but if I'm blocked here I probably won't be able to request user rights on Commons so I will understand a "last chance" for editing here and won't break it. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:06, 10 February 2018 (UTC) Reply

You've already had your last chance when your lock was lifted. – Ajraddatz (talk) 20:13, 10 February 2018 (UTC) Reply
I still have a language version to propose and request for comments here affect all other projects, is my account now getting globally locked again because of this block? Also I didn't herass anyone or "trolled" anyone.--Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:15, 10 February 2018 (UTC) Reply
No, your account won't be locked. – Ajraddatz (talk) 20:17, 10 February 2018 (UTC) Reply
And if the issue is regarding my comments about stewards why not just let me edit other parts of Meta such as proposed wiki's? Or RFCs? --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:22, 10 February 2018 (UTC) Reply

Would it be reasonable to ask if this block could expire in November or something so I can participate in the next Community Wishlist survey? --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:18, 10 February 2018 (UTC) Reply

No. You are playing the system and creating disruption again and again after warnings and (not only one) final chance. If you continue misusing the talkpage access to continue with drama then we have to revoke the access as well. --Steinsplitter (talk) 20:28, 10 February 2018 (UTC) Reply
I am not trying to deliberately stir up drama against anyone, the previous warnings were against my signature and I changed it, if there is something wrong with how I am currently using my talk page then I will stop doing that. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:31, 10 February 2018 (UTC) Reply
If you seriously believe you need to be told every little thing you're doing wrong is wrong, then I will have to point you to a good old enwiki policy. Your votes had nothing to do with the candidates' qualifications to becoming a steward. I'm not expecting mine to pass at this point so your vote doesn't really matter on mine, but fowling up other candidate's with a blanket principle oppose is nothing but disruptive. If you wanted to voice your concerns, the neutral vote would have been best, or the talk page of the elections page.—CYBERPOWER (Chat) 20:37, 10 February 2018 (UTC) Reply
That sounds reasonable, or I could've opened an RFC, and for the entire duration of 2017 post my unlock other than the comments made about my signature my editing on Meta wasn't seen as disruptive, this is mostly about the Steward elections and my previous warnings were about the global ban policy vs. Global locks which was explained to me and I didn't comment on that in general, and I've changed my signature. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 20:42, 10 February 2018 (UTC) Reply
But an indefinite block is excessive, in case I would get unblocked I wouldn't repeat any of the mistakes that lead to it, and I haven't kept my old signature when consensus was against it and have tried to follow policy as closely as possible, just look at my conduct on other wiki's, I've had no issues on Wikimedia Commons or after my unblock om the English Wikipedia other. If the issue is with my comments regarding stewards then I won't comment about stewards. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 21:01, 10 February 2018 (UTC) Reply
Did you know my very first block ever was an indefinite block? And it wasn't just an indefinite block, I had to go through ArbCom to get myself unblocked. I promised to them that I learned my lesson and wouldn't do what I did again, and they gave me another chance. I was unblocked 4 days later, and now I am an administrator there. If I can get myself blocked like that and get out of it, and stay out of it, that means so can others, and if you can't, then it would suggest that you haven't yet learned your lesson. The point is your behavior is disruptive in general. I think I've only ever seen you make disruptive edits here. Another good example is the question you asked all of us. How would you figure any steward candidate would possibly have any insight on that user that led to their lock, if they weren't there. They would have to research a lot of backstory, some or most of which aren't even visible to them. Thus the question does not allow any of the candidates to demonstrate their qualifications to be a steward. That's why every answer you got, including me, said a lock and a ban are not the same thing, without any comment on the specifics for that user. You got to think, "Will my actions be seen positive or at least neutrally by the general community?", and "Does this help the project overall?" If you can answer yes to both, it's likely okay. I'm no sysop here, but honestly you have dug a hole for yourself. You've been blocked for sockpuppetry there and disruption here, and have even been locked. If I have to be blunt about it, your word at the moment isn't carrying much weight, sorry.—CYBERPOWER (Chat) 23:02, 10 February 2018 (UTC) Reply
I also felt pretty bad about that question. I envied the other candidates that were not involved in the user you mentioned. I was involved in that case, so yes my answer was different. I had to be very cautious with my answer, that is I said very little really, that was not public knowledge, knowing full well the whole backstory of that very loaded question. However it was mostly under privacy rules. Hypothetical situation are fair enough, and I am not saying I did well in one of those. But at least it was hypothetical. Your bringing up of a very specific case that had a lot of ramifications was very unpleasant for me, as the one candidate I am guessing who had been involved in the case you mentioned. Cheers Scott Thomson (Faendalimas) talk 23:10, 10 February 2018 (UTC) Reply
People like cyberpower678 can change by learned their lesson on the mistake issue, and even be a good admin on English Wikipedia. If you can't, then very sorry for you. SA 13 Bro (talk) 23:23, 10 February 2018 (UTC) Reply
I was later informed of the circumstances that lead to the lock I had made a question about here by a steward but I did not know how to retract the question, also I had participated in the community wishlust survey without much complaints (well, other than adding too much suggestions but I had later retracted the ones I saw as less pressing), I see that my comments on the stewards are the reason why I'm banned and don't have much intent on commenting about stewards beyond this election as I had simply wanted to bring to light the issues I see with the current culture where there is very little communication by the stewards, and aren't there any clear rules on when global locks should be used or not. I am happy that there is no Global ArbCom, but there should br a global UTRS or ban appeals committee as most successful unlock requests are filed by other users, not the locked ones. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 06:26, 11 February 2018 (UTC) Reply
Maybe a condition where I would be allowed to open 1 RFC regarding the issues I see with stewards and then simply respect the outcome by the community and never mention it again, and never comment on stewards on Meta after the RFC closes. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 06:28, 11 February 2018 (UTC) Reply
I personally see no reason to unblock you or to continue the perpetual exercise of dealing with the disruption you have caused ever since your rather generous unlock. I think we should just revoke your talk page access and simply move on. Nihlus 11:08, 11 February 2018 (UTC) Reply
But I have no intent in bringing up the subjects that lead to my block again, and I will accept an indefinite block with no TPA if I were to break it, but I have adapted to every warning given, I changed my signature. If I were to only restrict myself to proposed projects, languages, and RFCs? Meta is more than only stewards and I will avoid any subject related to stewards including elections. --Donald Trung (Talk 🤳🏻) (Articles 📚) (WikiProject Numismatics 💴) 11:53, 11 February 2018 (UTC) Reply
Just let it go. If someone has proof of sockpuppetry or other issues and blocks you there's a valid reason. You issued many remove votes against stewards here and here] simply because they would not respond or help you remove your lock. I'm sure many community members would (normally of course there are exceptions) not look favourably upon a user who has been previously locked for cross wiki abuse (sure people change but your past history does raise issues with some). Just let it go and move on since there are other things which might suit you better. Continuing to push your case after it has been closed often doesn't result in favourable outcomes for the pusher (personal experience on phabricator and other places) --Sau226 (talk) 11:00, 27 February 2018 (UTC) Reply

Commond deletion bot requirements

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

I'm contacting you because you supported the Commons Deletion Bot proposal in the 2017 Community Wishlist. The Wishlist team has finalized the draft specifications for how the bot will work, and are seeking review in confirming or discussing the plans for the bot. If you have some time, please take a look and leave a comment. Thanks, happy editing to you. - Keegan (WMF) (talk) 19:06, 12 April 2018 (UTC) Reply

New Wikipedia Library Accounts Available Now (May 2018)

[edit ]


Hello Wikimedians!

The TWL OWL says sign up today!

The Wikipedia Library is announcing signups today for free, full-access, accounts to research and tools as part of our Publisher Donation Program. You can sign up for new accounts and research materials on the Library Card platform:

  • Rock's Backpages – Music articles and interviews from the 1950s onwards - 50 accounts
  • Invaluable – Database of more than 50 million auctions and over 500,000 artists - 15 accounts
  • Termsoup – Translation tool

Expansions

Many other partnerships with accounts available are listed on our partners page, including Baylor University Press, Loeb Classical Library, Cairn, Gale and Bloomsbury.

Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 18:03, 30 May 2018 (UTC)

You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

Commons deletion notification bot

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

Greetings,

You are receiving this message because you supported the Commons deletion notification bot in the 2017 Community Wishlist Survey.

Commons deletion notification bot is ready to be deployed to any Wikimedia wiki that wishes to use it. If your community is interested in the bot, you can leave a request on the project page on meta-wiki. The bot messages are available for translation on translatewiki.net, as part of preparing the bot for release.

Thank you for your participation in the Wishlist. -- Keegan (WMF) (talk) 17:29, 16 August 2018 (UTC) Reply

SVG Translate Community wishlist survey project

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

Hello! Thank you for voting for the SVG Translate project that was proposed in the 2017 Wishlist survey. The Community Tech team in the Wikimedia Foundation is beginning to start their work on the project. We're currently looking for feedback on some open questions which will allow us to come up with preliminary designs for the tool. If you are interested in being involved, you can watch the project page and join in the discussions on the talk page. Looking forward to hearing your thoughts and learning from your experiences. Thank you. -- NKohli (WMF), Product Manager, Community Tech (talk) 21:53, 16 August 2018 (UTC) Reply

Community wishlist survey 2018

[edit ]
Latest comment: 6 years ago 4 comments3 people in discussion

@MarcoAurelio:

×ばつ">×ばつ
Unblock request declined

This blocked user has had their unblock request reviewed by one or more administrators, who has/have reviewed and declined this request.
Other administrators can also review this block, but should not override the decision without good reason.
Do not remove this unblock review while you are blocked.

Request reason: Is there a possibility I could be unblocked to participate in this years community survey? Further I would like to be able to manage my subscriptions to newsletters. I will not edit any steward-related pages nor will I talk about any steward actions and I won't vote in any steward elections and I fully understand that I should not breach any of these conditions if you would accept them. The thing is there there are some improvements to the mediawiki upload wizard that I want to suggest and that's not possible due to the current block. --Donald Trung (talk) 19:03, 3 October 2018 (UTC) Reply

Decline reason: Net negative editor, plus we've 'been here before' - TNT 💖 13:22, 28 October 2018 (UTC) Reply


বাংলা | English | español | français | magyar | italiano | 한국어 | Plattdüütsch | Nederlands | українська | 中文 | edit

@Billinghurst: does the above seem credible or would you advise me to chang it? As I haven't had a response in quite some time. --Donald Trung (talk) 12:58, 16 October 2018 (UTC) Reply

You emailed me from Commons ages ago, and I responded to you at Commons. I have no further comment.  — billinghurst sDrewth 03:29, 17 October 2018 (UTC) Reply

The Community Wishlist Survey

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

Hi,

You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.

You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF) 11:23, 30 October 2018 (UTC) Reply

Learning Quarterly: November 2018

[edit ]
Latest comment: 6 years ago 1 comment1 person in discussion

L&E Newsletter / Volume 5 / Issue 17 / November 2018
Learning Quarterly

Stay tuned
blogs, events
& more!

New Wikipedia Library Accounts Available Now (March 2019)

[edit ]

Hello Wikimedians!

The TWL OWL says sign up today!

The Wikipedia Library is announcing signups today for free, full-access, accounts to published research as part of our Publisher Donation Program. You can sign up for new accounts and research materials on the Library Card platform:

  • Kinige – Primarily Indian-language ebooks - 10 books per month
  • Gale – Times Digital Archive collection added (covering 1785-2013)
  • JSTOR – New applications now being taken again

Many other partnerships with accounts available are listed on our partners page, including Baylor University Press, Taylor & Francis, Cairn, Annual Reviews and Bloomsbury. You can request new partnerships on our Suggestions page.

Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 17:40, 13 March 2019 (UTC)

You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

New Wikipedia Library Collections Now Available (September 2020)

[edit ]


Hello Wikimedians!

The TWL owl says sign up today!

The Wikipedia Library is announcing new free, full-access, accounts to reliable sources as part of our research access program. You can sign up for new accounts and research materials on the Library Card platform:

Many other partnerships are listed on our partners page, including Adam Matthew, EBSCO, Gale and JSTOR.

A significant portion of our collection now no longer requires individual applications to access! Read more in our recent blog post.

Do better research and help expand the use of high quality references across Wikipedia projects!
--The Wikipedia Library Team 09:49, 3 September 2020 (UTC)

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

AltStyle によって変換されたページ (->オリジナル) /