Jump to content

User talk:DatGuy/Archives/2017/June

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


Wish to be adopted

Hello! I'm a new wikipedian and I saw you were adopting users, and I would like to fall under your mentorship :) Looks like we share the same interests with video games and whatnot! — Preceding unsigned comment added by Xetotrius (talk • contribs) 17:32, 27 May 2017 (UTC)

@Xetotrius: Sorry, I'm already mentoring a user :). If you still need a mentor once the other editor doesn't need support anymore, I'll be sure to help you :). Dat GuyTalkContribs 16:32, 2 June 2017 (UTC)

Teletype Model 28 Tape Punch Set

If you were determined to make the Teletype Model 28 Tape Punch Set.jpg unreadable and basically unusable by reducing the picture in size then CONGRATULATIONS, you have succeeded!

And, you saved 150KB too!

20:21, 27 May 2017 (UTC)

:). I've fixed this since the section was made. Dat GuyTalkContribs 16:32, 2 June 2017 (UTC)

ITN recognition for Cheick Tioté

On 5 June 2017, In the news was updated with an item that involved the article Cheick Tioté, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. Ad Orientem (talk) 17:46, 5 June 2017 (UTC)

The future of NPP and AfC/Work group

Hi DatGuy/Archives/2017,

In view of the huge and sudden backlog at Special:NewPagesFeed since mid 2016, the WMF has begun a dialogue in a quest to examine the situation and possible solutions. Please consider commenting there if you have not already done so. It is highly recommended to read it all before it becomes too long to follow. The project is at Wikipedia:New pages patrol/Analysis and proposal, and its talk page.

If you wish to opt-out of future mailings, go here. MediaWiki message delivery (talk) 18:57, 5 June 2017 (UTC)

Tech News: 2017-23

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • You can see new files on Special:NewFiles. You can now pick which dates you want to see files from. [1]
  • When you read Wikipedia on a mobile device the first paragraph now comes before the infobox. [2]
  • You can now remove navigation elements from your results when you search. This could for example be part of an infobox that is only there to help you find the previous or next article. [3]
  • New users on Wikivoyages and Wikipedias (except French, English and German) now get a notification when a page they created is connected to Wikidata. Other wikis will get it 13 June. [4]

Problems

  • The MediaWiki version from two weeks ago was rolled back. It was fixed late last week. Changes that were planned to go out last week did not happen. [5]

Changes this week

  • Wikimedia wikis can show fewer links to articles in other languages. This is to make it easier to find the languages likely to be useful to the reader or editor. Everyone can still click to see the full list. Logged-in users who use the compact language links will see languages they have in their Babel box on their user page in the first, shorter list. You can turn the compact language list off or on in your preferences. [6]
  • You can choose what dates to look at when you look at a user's contributions. [7]
  • When you click on your watchlist in the mobile view you get a list of all pages in the watchlist instead of the latest changes to them. Logged-in users with at least ten edits will now get the latest changes instead. [8]
  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 June. It will be on non-Wikipedia wikis and some Wikipedias from 7 June. It will be on all wikis from 8 June (calendar).
  • String comparisons in Scribunto modules are now always done case-insensitively by byte order. Before they were sometimes in a case-sensitive US-English collation order. This could break some modules. [9]

Meetings

  • You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 June at 19:00 (UTC). See how to join.

Future changes

  • The 2006 wikitext editor will be removed the week of 27 June. This is the old toolbar with small square blue buttons. You can see a picture of it. 0.03% of active Wikimedia editors use this old tool. They will not see a toolbar at all. [10][11]
  • Wikimedia wikis use OCG to create PDFs. The OCG code has a lot of problems and will stop working. It has to be replaced. An alternative is Electron. You can tell the developers what you need the PDF service to be able to do. Electron already works on German Wikipedia. It will be on English Wikipedia later this week so you can test it there too. [12]
  • The Architecture Committee will change and get a new name. You can read and comment on the draft that describes the new committee.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

19:05, 5 June 2017 (UTC)

NonFreeImageResizer

Please let the bot stop reducing images it got reverted on before. Images made from text become unreadable: resolution not applicable. Other images are only fair use when the resolution stays the same. It also ignores the values of low resolution in the Non-free media information and use rationale. Ondertitel (talk) 19:24, 1 June 2017 (UTC)

I'll see if there's a similar complaint but Ronhjones am I wrong saying that the original size of File:AXXo nfo.png was small enough? Dat GuyTalkContribs 16:32, 2 June 2017 (UTC)
@Ondertitel: One man's low res is another man's high res. Also Wikipedia uses a strange defination of file-resolution - it's the square root of the pixel count - try incategory:"All non-free media" fileres:>316 filetype:bitmap in an advanced search for Files - it shows all files greater than a fileres of 316 which is 100,000 pixels as shown in the non-free guideline at WP:Image resolution (yes, there are a lot there - it is going to take us some time to sort out this category). There is no requirement to have the text perfectly in focus, even the reduced image in this case is still readable, so I do not see any reason to have a bigger image. If you insist on a bigger image then we will have to go to WP:FFD and get a consensus. Your image is 287,200 pixels (fileres=536) which is rather well over the guideline. Ronhjones  (Talk) 20:36, 2 June 2017 (UTC)
@Ronhjones: Please take a step back and ask yourself what you're doing. Objectively, you are making Wikipedia worse. I hope you are able to reach this level understanding.
Secondly, you are abusing the WP:MINOR checkbox for the template adding. Where should we get a consensus on that, WP:ANI?
Now, I see you have the understanding/knowledge of the guideline, but you are lacking wisdom. (exactly this is the Achilles' heel of WP, but that's another discussion [13]) A guideline is something that can be deviated from, but in such a way to still walk the line in the larger scheme of things. You'll have to get beyond the binary application of a rule and understand exceptions exist. The images in question are all text-based. The text is converted into an image to force the code page it should be viewed in, having the art displayed as intended. An image facilitates the inclusion on the page. These text files are often part of warez releases or closely related to it. They are intended to be shared, but of course there is no formal license for it. The current "high res" image is already smaller than how it's commonly viewed. I don't call the reduced image readable. It clearly reduces the WP:ACCESSIBILITY for visible users. Added to all that, remember the guidelines are worse than the minimum observed by law. Ondertitel (talk) 09:34, 3 June 2017 (UTC)

Sorry, I misunderstood the situation. Ronhjones is abusing the WP:MINOR checkbox. Your bot reacts correctly. I strongly suggest to ignore templates added as a minor edit. Ondertitel (talk) 07:27, 3 June 2017 (UTC)

@Ronhjones: You shouldn't add non-free reduce with a minor edit; uncheck the minor edit box in AWB for those edits. @Ondertitel: One of the prongs of the test on whether content is eligible for fair use is whether the minimum amount of the work necessary is used, which is why we need an image to be low resolution. Wikipedia is most worse off if the WMF and our contributors, including individuals that re-added copyright violations such as yourself in this case, get sued by copyright holders for adding copyright infringing content. Note that if copyright is registered with the US Copyright Office, copyright holders can sue for statutory damages, meaning they don't even have to prove the violation adversely affected them (just that it could have, to defeat one of the prongs of the fair use test). Statutory damages can run as high as $30,000. Our non-free content criteria are intended to prevent us from being open to liability under current copyright law. Given that it's a policy with legal considerations, there are no exceptions when applying them. In any event, this image doesn't even qualify for non-free use in full, as only the logo is needed for identification purposes. I'll crop it. ~ Rob13Talk 16:08, 3 June 2017 (UTC)
OK, AWB settings changed. I've put s {{non-free no reduce}} on the cropped image, I assume you don't want it reduced further. Ronhjones  (Talk) 21:31, 3 June 2017 (UTC)
@BU Rob13: Again, this is another prime example of what's wrong with Wikipedia culture causing user drop off. Let's take the approach of a proof. What do we have?
  • The policy. The policy is WP:NFCC and repeated on WP:FAIRUSE. Everything applicable to the discussion is this piece:

3. Minimal usage: b. Minimal extent of use. An entire work is not used if a portion will suffice. Low- rather than high-resolution/fidelity/bit rate is used (especially where the original could be used for deliberate copyright infringement). This rule also applies to the copy in the File: namespace.

  • All relevant bits related to the guideline is summarized in this quote:

Image resolution: There is no firm guideline on allowable resolutions for non-free content;

  • An example to discuss is File:AXXo nfo.png
  • Because I sense a lack of understanding, here is a complete example of the text where the image could be sourced from [14]. The image is of the text shown with the cp437 character set.
  • The safe harbor protections for Wikimedia. [15] [16] [17] [18]
What do I want to prove? Very simple, nothing to prove. Facts are in the given. Everything else is interpretation (culture) and/or bias. Only things to indicate: approach, fearmongering or lies.
"eligible for fair use is whether the minimum amount of the work necessary is used, which is why we need an image to be low resolution" The word 'which' indicates an implication, but there isn't. The policy exists of standalone parts: the portion and the fidelity. Each independent of each other. I argue the portion was minimal for its use on the article page: "Visual of a typical .nfo file included in a movie release." and the rationale for the image: "To illustrate a file that validates the authenticity of an aXXo release." You changed the purpose to logo, but he original purpose is to refer to an .nfo file. It's minimal in that it uses the art text header and one part of the body. Refer to the original source where the body is much longer. The body part is cleared of text to make it movie release independent and minimal. The other part is the fidelity. The original is resolution independent. Making it an image reduces the resolution by definition. As explained before, the resolution of the image is made lower than how it's commonly viewed. High: text, standard: image made of average font size, low: small font used for image. Making it even smaller made the text unintelligible for its purpose.
"Wikipedia is most worse off if..." Here starts the fearmongering. As shown above, there never was a copyright violation. The Wikimedia foundation is protected by the safe harbor laws. It's about warez, so no way in hell that something is registered. The original is text. What you write are things to say to make people understand why things happen the way they do, but it cannot be used as argumentation. It is pushing a certain bias. "Given that it's a policy with legal considerations, there are no exceptions when applying them." While this is 100% true, it must not be used it in a way to further guideline compliance. That is the part where there most certainly are exceptions on how to implement the policy in a specific case.
"this image doesn't even qualify for non-free use in full, as only the logo is needed for identification purposes." The purpose was showing an NFO file, not a logo for identification. From the article: "The aXXo postings also carried a .nfo file about the movie". Any visualization of the movie part is no more.
All that being said, I don't oppose the image cutoff. The structure of the NFO file isn't special enough to be mentioned in the article. The empty movie template information isn't referenced in the article and doesn't make the article nicer or better to understand. It's not unique. I think just the logo makes the page look nicer. But this is a choice we make for this specific case. I still oppose the size reduction of images specifically made from text to the point where they become totally useless and the reduction of demoscene images where the intent of its creators is totally ignored. Ondertitel (talk) 10:13, 5 June 2017 (UTC)
Depicting the .nfo file, which has graphics that are undiscussed in the article itself, would fail WP:NFCC#8. Copyright does not need to be registered to be protected; it is automatic in the United States. The rest of the argument boils down to "We can get away with breaking the law, so we should", and that's obviously not (a) good practice, (b) respectful of the rights of copyright holders, or (c) supported by policy. Note that even if the WMF is protected, you are not, and a copyright holder can sue whoever uploaded/restored a copyright violation individually for actual or (if registered) statutory damages. Actual damages can be unlimited, whereas statutory damages are between $750 and $30,000 as determined by a court. That's one of many reasons we don't just knowingly allow people to break copyright law. As for the resolution, the previous resolution was several times larger than it appeared in the article. The bot reduced it roughly to the size it appeared as in the article itself. The only valid instance of fair use is in the article, so we have no need to store the image at a greater size in the file namespace. ~ Rob13Talk 12:44, 5 June 2017 (UTC)
I see that interpretation as too narrow. You still call text graphics. It boils more down to "When we can do it, we should". Avoid copyright paranoia To quote a famous decision in copyright law "the parties are advised to chill." Mattel, Inc. v. MCA Records, Inc., 296 F.3d 894, 908 (9th Cir. 2002). Ondertitel (talk) 19:41, 6 June 2017 (UTC)
If the country of first publication is the United States, then I'd tag the file with {{PD-ineligible}}. If the country of first publication is some other country (or if the country of first publication is unknown), then I'd use {{PD-ineligible-USonly}} to avoid that the file is moved to Commons in case it isn't allowed there. --Stefan2 (talk) 21:55, 3 June 2017 (UTC)
@Stefan2: The threshold of originality is far lower than you're applying it. The logo is not simple geometric shapes. It contains originality in the shape of the shaded area surrounding the text, and so it is copyrightable. Further, text and layout may not be copyrightable, but this is not known for sure, and even if it were, isn't relevant here. The case you cited was a 4–4 split decision that did not set any national precedent. The court has become substantially more expansive in their view of copyright since that case was decided, to the point where I feel reasonably confident that they would say layout of a program is copyrightable if they decided a similar case today. For context, the current court expanded the set of copyrightable items to include the designs of any useful item, provided that design could be depicted outside of the useful item itself (e.g. in a photograph or drawing), which is a rather insane expansion of copyright. That decision was 6-2, so it wasn't even close. See Star Athletica, L. L. C. v. Varsity Brands, Inc.. Further, layout isn't what's likely copyrightable here. It's the framing which is. The fancy header, etc. is original. ~ Rob13Talk 03:02, 4 June 2017 (UTC)

Tech News: 2017-24

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • Some wikis have the larger and brighter OOjs UI edit page buttons. When you write an edit summary there you can now see how many bytes you have left before the summary is too long. [19]
  • When you search on Wikipedia you can now find pages on other Wikimedia projects that could be relevant. You see them next to the search results. [20]

Changes this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 June. It will be on non-Wikipedia wikis and some Wikipedias from 14 June. It will be on all wikis from 15 June (calendar).

Meetings

  • You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 13 June at 19:00 (UTC). See how to join.

Future changes

  • You will soon be able to get a notification when someone tries to log in to your account. You can test this on the test wiki. This will only work if they fail to log in to your account. [21]
  • Wikimedia wikis use OCG to create PDFs. The OCG code has a lot of problems and will stop working. It has to be replaced. An alternative is Electron. You can tell the developers what you need the PDF service to be able to do. Electron now works on all Wikimedia projects. [22]
  • Administrators can soon search for deleted page titles and find results that are similar to what they searched for. Today the search only finds pages that are exactly the same as what you search for. This is to make it easier to find pages when you don't know the exact title. Administrators on Arabic, Catalan, English, Persian, German, Italian, Polish, and Russian Wikipedia and on mediawiki.org can test this by adding &fuzzy=1 to the end of the web address when looking at Special:Undelete. [23][24]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:30, 12 June 2017 (UTC)

RonBot problem

Hi DatGuy,
New trial failed and I aborted fairly early, as soon as I saw an issue. A couple of files were OK (see top 2 on Special:Contributions/RonBot) - both these files had the {{Orphaned non-free revisions|date=02:13, 8 June 2017 (UTC)}} well down the page, after that it started to process files where the template was the top line, and it failed to remove the template - see Special:Log/RonBot. I assume this all down to the edit you did in respoinse to Rob's comment about blank lines. It appears to have stopped it working when the template is at the top. As an aside I fixed all the bad files with User:Legoktm/rescaled.js - that has a RegEx to remove the template which works OK - would that help you with this bot? Ron. Ronhjones  (Talk) 21:04, 15 June 2017 (UTC)

@Ronhjones: Sorry, dumb mistake - Change the line in the code to
pagetext = re.sub(r'(?:\n)?\{\{(?:[Oo]rphaned non-free revisions|[Nn]on-free reduced).*}}', '', pagetext)
Dat GuyTalkContribs 22:11, 15 June 2017 (UTC)
It's good, small trial OK, now on run of 250. Ronhjones  (Talk) 22:51, 15 June 2017 (UTC)
Removes the template fine, but leaves a blank line in it's place, and any blank lines below it. e.g.
{{Orphaned non-free revisions|date=00:12, 8 June 2017 (UTC)}}

== Summary ==
With RonBot we are getting


== Summary ==
With User:Legoktm/rescaled.js I get
== Summary ==
Compare File:Babhdasound.jpg with File:Backtofronttempt.jpg Ronhjones  (Talk) 23:08, 15 June 2017 (UTC)
"Borrowing" the code from the js script - will this work? ---- pagetext = re.sub(r'/\n*\{\{\s?(Non\-free reduced|Orphaned non\-free revisions)\s?\|\s?(?:\d|date)?\=?(\d\d\:\d\d\,\s\d\d?\s.*\s\d\d\d\d(\s\(UTC\))?|.*\d\d?(?:\s[a-z]+)?\s\d\d\d\d)\s?\}\}/ig', '', pagetext) ? Need to wait now, until there are more files available to process. Ronhjones  (Talk) 23:18, 15 June 2017 (UTC)
@Ronhjones: Just replace the (:\n)? with \n*. Dat GuyTalkContribs 08:49, 16 June 2017 (UTC)
?? There is no (:\n)? in the line you posted above - it's (?:\n)? - is that the bit to replace? Ronhjones  (Talk) 19:07, 16 June 2017 (UTC)
Yes, sorry. Dat GuyTalkContribs 19:12, 16 June 2017 (UTC)
Sadly, still blank lines at top - User:RonBot/Source2 is what I just ran - see File:A push and a Shove.jpg Ronhjones  (Talk) 19:51, 16 June 2017 (UTC)

@Ronhjones: No idea, there shouldn't be any different with Lego's code. If you do want to try his, remove the /ig from the end of the regex and put it at the end. End result: pagetext = re.sub(r'/\n*\{\{\s?(Non\-free reduced|Orphaned non\-free revisions)\s?\|\s?(?:\d|date)?\=?(\d\d\:\d\d\,\s\d\d?\s.*\s\d\d\d\d(\s\(UTC\))?|.*\d\d?(?:\s[a-z]+)?\s\d\d\d\d)\s?\}\}', '', pagetext, flags=re.IGNORECASE) Dat GuyTalkContribs 20:44, 16 June 2017 (UTC)

Nothing is simple... Left the template in (File:A Time And A Place.jpg) - had to remove it with Lego's script! Ronhjones  (Talk) 21:03, 16 June 2017 (UTC)
OK. going back to previous code and playing with a non-saving version, and looking at more detailed screen output - If I add pagetext='\n\n\n\n'+pagetext before the "re.sub" line, then that gives me 4 blank lines, then the template, then the blank line that is under it. After the "re.sub" there are two blank lines - that suggests that the 4 extra blank lines went OK, the template line has been replaced with a blank line and the blank line that was there is still there. Hope that makes some sense...? Ronhjones  (Talk) 21:47, 16 June 2017 (UTC)
Maybe a second "re-sub" - removing blank lines when they are at the start of the string? Is that possible? Ronhjones  (Talk) 21:50, 16 June 2017 (UTC)
Found the answer - added pagetext=pagetext.lstrip() after the "re.sub" statement, running a trial now Ronhjones  (Talk) 22:41, 16 June 2017 (UTC)
75 files processed OK - code at User:RonBot/Source2, more tomorrow when more files available. Ronhjones  (Talk) 22:54, 16 June 2017 (UTC)
Running fine, found 3 issues - 2 fixed
  1. If file has been put in "Category:Non-free files with orphaned versions more than 7 days old needing human review", then it's still in "Category:Non-free files with orphaned versions more than 7 days old", so it got processed again and another human=yes added - put the cat in with the list of cats to skip. Works.
  2. File:Áilleacht.jpg failed - too many print statements - some did not like the accent and got "'ascii' codec can't encode character u'\xfa' in position 42: ordinal not in range(128)" - removed print statements. Works.
  3. File:Farz Aur Kanoon.Jpg 4 images in list - call them - current, old1, old2, and old3. old3 deleted ages ago. Bot deleted old1 and left old2. Sadly lost log for that run, so wait for something similar to happen - as a last resort I can unhide old1 and old2 and (temp) delete the edits post DatBot to make it look like it did before the run. Hopefully I will find the error again first.
Ronhjones  (Talk) 00:57, 18 June 2017 (UTC)

RonBot Update

Was working as above, found another file with multiples to do and did only one. The abuse check (which is done for each version) failed on the second pass. So I have modified the code User:RonBot/Source2 to set a variable (firstversion) to yes at the start of a file, and then only do the abuse checks on the first pass. I ran it as shown on the same file File:Amira Nature Foods Logo.png (after deleting the RonBot edits, so it looked OK to the Bot) and it works fine. Since my python is not great - can you have a quick look at my changes and see that it looks OK to continue? Ronhjones  (Talk) 16:41, 18 June 2017 (UTC)

@Ronhjones: You could just move it above the for version in todelete: loop and under the for filep in pages: loop. Dat GuyTalkContribs 20:02, 18 June 2017 (UTC)

Tech News: 2017-25

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

  • ORES had some problems on 13 June between 16:00 and 19:40 UTC. It has now been fixed. [25]

Changes this week

  • irc.wikimedia.org has to be rebooted. This will probably happen on 21 June. It may be postponed. Some tools use this to get the recent changes feed. They will not work when it is down. [26]
  • Special:PageData will be an entry point for machine-readable page data. [27]
  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 20 June. It will be on non-Wikipedia wikis and some Wikipedias from 21 June. It will be on all wikis from 22 June (calendar).

Meetings

  • You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 20 June at 19:00 (UTC). See how to join.

Future changes

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:44, 19 June 2017 (UTC)

DatBot minor change

When reporting IP vandals, can you have it use Template:IPvandal instead of Template:Vandal? —Guanaco 23:03, 21 June 2017 (UTC)

 Done. Dat GuyTalkContribs 10:45, 22 June 2017 (UTC)

Speedy deletion nomination of Draft:Port-au-Prince Soccer Massacre

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

Hello, and welcome to Wikipedia. This is a notice that the page you created, Draft:Port-au-Prince Soccer Massacre, was tagged as a test page under section G2 of the criteria for speedy deletion and has been or soon may be deleted. Please use the sandbox for any other tests you want to do. Take a look at the welcome page if you would like to learn more about contributing to our encyclopedia.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Legacypac (talk) 04:03, 25 June 2017 (UTC)

Tech News: 2017-26

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

  • The <inputbox> has a new searchfilter parameter. You can add values like searchfilter=insource:foo. It will add that to the user's search query. [28]

Changes this week

  • The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 June. It will be on non-Wikipedia wikis and some Wikipedias from 28 June. It will be on all wikis from 29 June (calendar).
  • Users will be able to choose whether they want to see Wikidata changes in enhanced watchlist/recent changes. Previously, this was disabled for everyone. [29]

Meetings

  • You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 27 June at 19:00 (UTC). See how to join.
  • You can join the next WMF Language team office hour, an open session to talk about Wikimedia Language projects. The meeting will be on 27 June at 13:00 UTC. [30]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:38, 26 June 2017 (UTC)

Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:DatGuy/Archives/2017/June&oldid=788980092"