User talk:Jtmorgan/Archive 7

I like your Teahouse quote.
I had listened to Graceland within a week before reading it. I had listened to Paul Simon that very same morning. I'm assuming you're a fan too. :) Best, Alt3no (talk) 21:42, 16 May 2017 (UTC)

HOST BOT
What is a BOT ? LadyWolfEtnaOH (talk) 16:33, 21 February 2017 (UTC)

BAGBot: Your bot request HostBot 8
Someone has marked Bots/Requests for approval/HostBot 8 as needing your input. Please visit that page to reply to the requests. Thanks! AnomieBOT ⚡ 03:53, 22 May 2017 (UTC) To opt out of these notifications, place  anywhere on this page.

Thanks for the invite
I will probably not go to the Teahouse that often, but I still thank you for inviting me.--77Ravin77 (talk) 20:35, 13 May 2017 (UTC)


 * thankyou for inviting me on teahouse.--

Jyotilohkana —Preceding undated comment added 00:24, 17 May 2017 (UTC)

Hey Jtmorgan! Just want to say thanks so much for inviting me to the Teahouse, I have already asked a question. It looks like such a helpful page. Anyway if you have anything else you'd like me to see please do as I am quite new to Wikipedia accounts :) Really kind of you to invite me, hope you have a nice day! Iris x

Iris Medallion (talk) 07:35, 24 May 2017 (UTC)

Speedy deletion nomination of User talk:Igwe Kastan


A tag has been placed on User talk:Igwe Kastan requesting that it be speedily deleted from Wikipedia. This has been done under section U5 of the criteria for speedy deletion, because the page appears to consist of writings, information, discussions, and/or activities not closely related to Wikipedia's goals. Please note that Wikipedia is not a free web hosting service. Under the criteria for speedy deletion, such pages may be deleted at any time.

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, or if you have already done so, you can place a request here. Winged Blades Godric 07:34, 30 May 2017 (UTC)

Hi. I'd like my content back up
I'd appreciate you stop your malicious removal of my content. Thanks. The content is relevant to the subject and has links to prove it. If something needs to be changed or added to fit your approval, you can just tell me and stop being rude about it. I realize computer screen anonymity makes you feel powerful, but kindness is still a good trait to have. If you'd like to call me and have a chat, I'd love it. So, give me an email to send a number to. — Preceding unsigned comment added by DavidMoyle (talk • contribs) 18:29, 6 July 2017 (UTC)
 * I'm not removing your content,, and neither is my bot HostBot. All HostBot does is send welcome messages. I know that Wikipedia can be confusing and that it sometimes feels like you're under attack. If you have questions about why your content is being removed, I suggest you ask them at the Teahouse. Hint: being polite increases your chances of getting a useful reply. Cheers, J-Mo 20:47, 6 July 2017 (UTC)

Well, then, interestingly Wikipedia made a mistake as it told me it was removed by your bot. And I'm having a lot of issues as I followed your standards and it was still reported by someone and removed without even contacting the person who posted it first. Until I tried a couple more times. So, you can understand my frustration maybe. — Preceding unsigned comment added by DavidMoyle (talk • contribs) 23:04, 6 July 2017 (UTC)

Speedy deletion nomination of User talk:يوسف محمد سعيد


A tag has been placed on User talk:يوسف محمد سعيد requesting that it be speedily deleted from Wikipedia. This has been done under section U5 of the criteria for speedy deletion, because the page appears to consist of writings, information, discussions, and/or activities not closely related to Wikipedia's goals. Please note that Wikipedia is not a free web hosting service. Under the criteria for speedy deletion, such pages may be deleted at any time.

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, or if you have already done so, you can place a request here. &mdash; fortuna  velut luna  11:58, 15 July 2017 (UTC)

Requested modification of HostBot Teahouse invitations
Hey Jtmorgan. On occasion, I've come across edits by HostBot to user talk pages where I have previously placed a uw-coi-username template. I'm concerned that the HostBot invitation, posted after the coi warning, is conveying the idea that it's ok for them to continue under that account name. As an example, have a look at User talk:UOWSydneyBusinessSchool. The editor's name as well as their edits strongly show they are operating under a conflict of interest. Should they continue to make edits without renaming, it is likely they will be blocked from further editing.

So, I was wondering; could you modify HostBot to detect if the username is in Category:User talk pages with conflict of interest notices, such as HBC AIV helperbot5 did with this edit, and if so not place the Teahouse invitation?

Your thoughts? --Hammersoft (talk) 20:44, 24 July 2017 (UTC)


 * . Thanks for the ping. I can make the change without much trouble. I'm a bit hesitant to do so. I see your point that it might send a mixed message. But most new editors who receive Teahouse invites are getting mixed messages, for the simple reason that so many of them get revert and warn messages on their talkpages as well as cheery welcomes. I already screen out people with sockpuppet templates and level 4 user warnings, so I guess it comes down to whether or not we consider a COI username to be a 'serious' issue on the scale of one of those warnings. My preference would be to send the invites, because a) they will still see the COI warning, b) if they visit the Teahouse they will certainly be informed that their username is COI, c) almost any Wikipedian they talk to will point out their COI username, and d) a little gentle encouragement and an offer for personal support for someone who is acting in good faith (if against policy) as many of them probably are, never hurts :) If you'd like to see this criterion added, perhaps post to Teahouse talk and ask the hosts; I'll follow their recommendation on this one. Thanks, J-Mo 23:22, 24 July 2017 (UTC)

Teahouse archival: coming up...
Hi!

If you remember the archival notification bot thing, I have a good chunk of code already done, as well as the template that the bot should substitute.

If you have time to review the code / make any comments, I would welcome it. The most simple test case is python3 find_and_notify.py > test.log which creates a list of entries user talk page -> text to add via the template (pull the repo, move to /scripts, run the command, check out the warnings in command line and inspect test.log). From what I could see, there are a few false negatives No matches for the creation of the following thread: which I believe are caused by a size limitation of how much history the API accesses in one go.

I still haven't made heads or tails of pywikibot's means to authenticate and post to pages, so I haven't coded the notification process itself (but it should be fairly quick once I understand what is going on). Once that is done, I think the bot request is good to go.

Also, I have trouble to access block info for IP editors via the API, if you know how it is done I am all ears.

All the best, Tigraan Click here to contact me 20:55, 18 June 2017 (UTC)


 * Hi ! I replied on the MediaWiki thread with a solution to getting block status for IP users that should work. In terms of authentication, I know of two ways to do it. The first is to just make a POST request to the API with your normal user credentials. There's an example of that here (see the login_request, token_request, and publish functions). That should work for testing the scripts. For running HostBot, I use OAuth directly, via requests-oauthlib, rather than going through PyWikiBot (I can never make heads or tails of PWB either). You can see my implementation here, if that's helpful. The documentation for setting up your bot to use OAuth is a bit confusing. I don't remember the details of how I did it, or exactly why it's necessary/preferred, but it's worth looking into once you've got the bot tested and ready to go.


 * I took a quick look at you code and watched the repo. I probably won't have time to test it directly, but if there are any pieces you'd like another set of eyes on let me know. J-Mo 21:03, 19 June 2017 (UTC)

Sorry, I forgot to answer to you. I did not need your help for testing. The task has been approved, so it is now time to merge to HostBot and add the cron job. I suppose you can show me the way through that; the only potential roadblock is that it uses PWB which might or might not be available in the current HostBot environment.

I won't be much online in the next week or so, but after that I can take a more active part. Tigraan Click here to contact me 16:52, 7 July 2017 (UTC)
 * Great news! I'm kind of swamped for the next couple weeks, though. Are you comfortable running the bot under your testbot account in the meantime? Using PWB isn't a problem in itself (I'm 99% sure it's available on tool-labs), but I might want to see if we can refactor that out when we merge, to reduce dependencies. It looks like you're using PWB for authentication and to add the message to the page. I have code that will cover both of those tasks, as long as you just want to add a new section to the bottom of a talkpage. Let me know if an extended timeline works for you. Cheers, J-Mo 23:53, 13 July 2017 (UTC)
 * No problem for the timeline: I doubt the TeaHouse folks that lacked this feature for many years will suddenly demand it done soon.
 * PWB is used only for authentication and adding a bottom-post, correct. It should be relatively easy to refactor. However, during posting, it also provides (1) detection and parsing of nobots, (2) a timeout between write requests. The former is IMO necessary; the latter is useful when posting to the same page in quick succession (one edit may overwrite the next one otherwise), but not indispensible (worse-case scenario, multiple notices are replaced by a single one on a user's talk page).
 * Tigraan Click here to contact me 09:43, 17 July 2017 (UTC)

WIP update: I copied your scripts over to the HostBot repo (onto their own branch, for testing). I hacked at the code a bit and managed to make it run without PyWikiBot. You can see the test edits. I'll need to refactor a bit and clean up my mess before it's production-ready. Longer term, I'd like to refactor some MORE (mostly around standardizing authentication and settings configuration with the rest of the codebase, at least initially). Overall your code is great; easy to work with and understand--thanks esp. for the detailed docstrings :) I'll try to get this up and running on EnWiki within the next week or so. Then, if you're still interested, we can go through the necessary steps to make you a co-maintainer of HostBot. LMK if you have any thoughts/questions! Cheers, J-Mo 00:08, 3 August 2017 (UTC)
 * Sorry for not answering sooner, I promised myself to drop you a note but my holidays happened to not have Wifi.
 * I am happy that you could navigate through the code, though I doubt it deserves to be called "great" - I had to dust off my Python writing (which was not great to start with) during the coding.
 * I gave a look at your codebase; the only question I have is about the features I used PWB in the first place, namely rate-limiting the edits and obeying . The former is (I think) no big deal since the bot isn't making that many edits, but the latter is potentially problematic since non-newbies occasionally post at the Teahouse.
 * I also think we need to go through BAG again, especially if the nobots thing is not handled by PWB. It should be a walk in the park (fingers crossed). I should also motivate myself to write a proper documentation for all the weird edge cases of misbehavior (some indices are scattered across the code and the GitHub repo, but I should write something proper).
 * I am still interested in co-maintaining HostBot, but with an emphasis on "co" - I looked through the code and feel a bit overwhelmed, but that is what usually happens at first contact.
 * Thank you for making the merge, Tigraan Click here to contact me 19:01, 18 August 2017 (UTC)
 * I think we're good on the 'nobots' and rate-limiting front. We can rate limit by using time.sleep(num_seconds) between edits. I've used this approach before. I've also checked for the NOBOTS template before... in fact I thought I was, but apparently that got lost in some refactor at some point. I can add it back easily though; I have a configurable list of keywords to check for on a user talkpage, that I use for skipping Teahouse invites to people who have received level-4 userwarnings, sockpuppet notices, etc. I can just add "|nobots}}" to the list, and we should be good.
 * We can go to BAG again if you'd prefer. I have no issues with that. As for the HostBot code... yeah, it's more readable than it used to be, is the best I can say for it :) I'm a self-taught Python programmer and some of my conventions are probably pretty, um, 'bespoke', so don't think that your confusion is your own fault.
 * I've been sitting on this for too long, and I hope you aren't getting impatient with me. This is really your project, and I don't want my desire to incorporate the functionality into HostBot to be a blocker. I intend to work more on this tomorrow afternoon and Sat, mostly cleaning up some of the workarounds I did to integrate your code into mine, and deleting some unused stuff. Hopefully we will have a robust-enough system to test on Enwiki and/or show BAG by early next week. Cheers, J-Mo 22:13, 24 August 2017 (UTC)
 * Rate-limiting is easy enough, but I think it should be done. During testing with no rate-limit I ran into edit conflicts by overwriting like this one. It probably occurred because the bot tried to edit the same page in succession, which will be much rarer in production but can still happen (if the same user creates two TH threads).
 * For exclusion compliance, your suggested approach is not enough since there are multiple syntaxes for the exclusion template or . However, its documentation helpfully provides a Python implementation (confusingly, "user" is the name of the bot and "text" is the text of the user page, but the rest is fairly straightforward). While it may not be optimal performance-wise, it may be simpler to just copy-paste it into a "test if user excludes the bot" routine, that we call inside the "is user notifiable" check. If you don't want to use the mwparserfromhell module, it will probably take a bit of tweaking to find the correct regexp or whatever to parse the page.
 * I think we are pretty much forced to go through BAG again because of the exclusion compliance bit. I do not think the bot would have been approved if it wasn't exclusion-compliant, which was handled by AWB, which is removed in the new architecture. Maybe it will be a smooth sailing, but we need to be open about this. We do not want that in half a year's time a veteran user posts on the bot's noticeboard that a clearly-labelled as exclusion-compliant bot ignored their template.
 * My own Python is self-taught as well, and tainted by other languages (the most blatant mark is the absence of class constructors in the code, when it probably would have been warranted), so I am not going to judge you for it. Also, even in languages I am familiar with, I can get lost in my own code from a year ago; I looked through the code and feel a bit overwhelmed, but that is what usually happens at first contact was a statement of fact, not a polite criticism. (Maybe later, after digging in the code, I will curse you to death, but I have no reason to do so yet )
 * I don't care a lot about the time it takes to get it implemented - the Teahouse could survive without it for multiple years, it is not an urgent task. No hurry. Tigraan Click here to contact me 14:26, 1 September 2017 (UTC)

What happens if you shut off the bot?

Bot-talk
what happens if you shut off a bot? HaapsaluYT (talk) 22:02, 1 September 2017 (UTC)

broken page Comment
Teahouse/Host lounge/Metrics has not updated since 2014. A Guy into Books (talk) 11:54, 9 September 2017 (UTC)
 * Thanks . I've added a historical template to the page to make it clear that the feature is no longer maintained. Cheers, J-Mo 23:31, 14 September 2017 (UTC)
 * ok. &Alpha; Guy into Books &trade;  &sect; ( Message ) -  07:30, 15 September 2017 (UTC)

why blocked?
Hi. Why is HostBot currently blocked? — usernamekiran (talk)  10:36, 15 September 2017 (UTC)
 * Some bug in my code apparently. Currently investigating; should be up again pretty soon. J-Mo 18:23, 15 September 2017 (UTC)
 * I just found out this thread Administrators' noticeboard, because informed me about it another post regarding bots in general. See you guys around. — usernamekiran (talk)   20:07, 16 September 2017 (UTC)

Hostbot broken
Its not inviting even through its unblocked  Flow 234 (Nina)   talk  10:26, 20 September 2017 (UTC)
 * Hi . You're right, HostBot is still offline--I need to make some updates. Thanks for reminding me to change the status :) Cheers, J-Mo 04:01, 21 September 2017 (UTC)

JADE: topics to discuss
Hello,

Here are some topics the JADE team would like to discuss. If you are interested, follow the link to join the conversation:
 * Judgments, Endorsements, and Preference
 * Free text comments and suppression
 * Should we integrate JADE with Flow?
 * Thematic and quant analysis of judgements

Thank you. On behalf of the Scoring Platform Team, Keegan (WMF)(talk) 21:09, 13 October 2017 (UTC)

Thanks for your warm welcome, HostBot!
Thanks for thinking of me good friend Jtmorgan! All hail HostBot! Will try not to be too loud in the the Teahouse! [whispers] Best. - Asdiprizio (talk) (UTC)

Message from User:173.209.211.197
I must have done something Very Very awful to you because I never thought I would be called names when I preview things as browser. Things like last edited by an annoying person to be nice. I am managing partner of a very generous Corp. with 211 employees most work from home. That said I have just been trying to learn how to do new things on computers on my own and as a Gen X guy it can be difficult. however, I taught myself a lot over a year and I figured I could try writing on Wikipedia and not bother anyone no matter how long I work at it. so yesterday Invite to take an adventure while learning but I didn't understand the idea or what was happening. I waisted so much time doing as told went to the tea shop everything but it ran me in circles. I was so mad I had our legal counsel here at six am along with local employees to see what would happen well the names came faster. so I sent someone there the name and phone number of our law firm. then my history was changed or deleted friends saw different things with my name on it and in the same house the screens are different. I hope it's a freak thing because I don't feel good after presenting four attorneys to young smart people that I thought you were. all done maybe venting will help.

Please join us for our Cascadia Wikimedians annual meeting, Saturday, December 23, 1 PM
06:19, 20 December 2017 (UTC) To unsubscribe from future messages from Meetup/Seattle, please remove your name from this list.

Happy New Year, Jtmorgan!


Happy New Year! Jtmorgan, Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.

Ceannlann gorm (talk) 00:25, 1 January 2018 (UTC)

Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.


 * Thank you, ! J-Mo 19:53, 2 January 2018 (UTC)

Facto Post – Issue 9 – 5 February 2018
{| style="position: relative; margin-left: 2em; margin-right: 2em; padding: 0.5em 1em; background-color: #7FFFD4; border: 2px solid #00FFFF; border-color: rgba( 109, 193, 240, 0.75 ); border-radius: 8px; box-shadow: 8px 8px 12px rgba( 0, 0, 0, 0.7 );"
 * Facto Post – Issue 9 – 5 February 2018

 

m:Grants:Project/ScienceSource is the new ContentMine proposal: please take a look.

Wikidata as Hub
One way of looking at Wikidata relates it to the semantic web concept, around for about as long as Wikipedia, and realised in dozens of distributed Web institutions. It sees Wikidata as supplying central, encyclopedic coverage of linked structured data, and looks ahead to greater support for "federated queries" that draw together information from all parts of the emerging network of websites. Another perspective might be likened to a photographic negative of that one: Wikidata as an already-functioning Web hub. Over half of its properties are identifiers on other websites. These are Wikidata's "external links", to use Wikipedia terminology: one type for the DOI of a publication, another for the VIAF page of an author, with thousands more such. Wikidata links out to sites that are not nominally part of the semantic web, effectively drawing them into a larger system. The crosswalk possibilities of the systematic construction of these links was covered in Issue 8.

External links speaks of them as kept "minimal, meritable, and directly relevant to the article." Here Wikidata finds more of a function. On viaf.org one can type a VIAF author identifier into the search box, and find the author page. The Wikidata Resolver tool, these days including Open Street Map, Scholia etc., allows this kind of lookup. The hub tool by takes a major step further, allowing both lookup and crosswalk to be encoded in a single URL.

Links
To subscribe to Facto Post go to Facto Post mailing list. For the ways to unsubscribe, see below. Editor, for ContentMine. Please leave feedback for him. Back numbers are here. Reminder: WikiFactMine pages on Wikidata are at WD:WFM. If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page. Newsletter delivered by MediaWiki message delivery MediaWiki message delivery (talk) 11:50, 5 February 2018 (UTC)
 * What galleries, libraries, archives, and museums can teach us about multimedia metadata on Wikimedia Commons, Wikimedia Foundation blogpost, 29 January 2018, by Jonathan Morgan and Sandra Fauconnier
 * The Wikipedia Library/1Lib1Ref/Connect, 2018 institutional participation in the #1lib1ref campaign
 * Newspeak House queries, created at 3 February 2018 event in London led by
 * Cochrane–Wikipedia Initiative, Wikipedia Signpost special report 5 February 2018, by
 * What is the Last Question?, 5 February 2018
 * }