User:Billinghurst in WMF wikis
IRC: sDrewth/sDrewthedoff billinghurst@wikisource/billinghurst
User Details
- User Since
- Oct 6 2014, 10:50 PM (441 w, 6 d)
- Availability
- Available
- IRC Nick
- sDrewth
- LDAP User
- Billinghurst
- MediaWiki User
- Billinghurst [ Global Accounts ]
Sun, Mar 19
Noting that the death of 1855 is obviously wrong when he married and had children after that date. I suspect it is meant to be 1885, to be confirmed at author talk page at enWS
Feb 16 2023
Dec 23 2022
It is primarily Beetstra's project which I support onwiki as a doer, and on the instances as a pair of arms. I don't think that it needs any further approval nor action than Beetstra's.
Oct 29 2022
Oct 9 2022
Sep 24 2022
Jun 23 2022
Mar 10 2022
Mar 6 2022
Feb 2 2022
It would be lovely if all these pages could be migrated to a standard set of (reserved) NS numbers for ProofreadPage and have a redirect from the old to the new so that they old will continue to work while all tools are updated and issues resolved.
could we please rerun the xwiki report to see where we have issues to address? Thanks.
Jan 24 2022
Looks like someone needs to reboot ws-export.wmcloud.org seems to be hung up on something
Dec 23 2021
Not grok'ing this exactly, I will just view it in action. We should write good instructions, with all the appropriate caveats on the mediawiki guidance page. Thanks.
Dec 15 2021
@Aklapper Are we able to find someone to review this? This is a break stopping work that has a solution, and having to get people to do css fixes is less than ideal. Thanks.
Nov 21 2021
As a note, I did go through something like
https://ta.wikinews.org/w/api.php?action=query&meta=allmessages
Nov 18 2021
@MusikAnimal guessing that the code for ProofreadPage, or the hooks for it, should be checked if it is just Page: namespaces
It also overrides my version of the old toolbar that I use (2006 toolbar that is gadgetified). The modern toolbar is highly ineffective for the Wikisource work where I am needing my customisation for quick and effective transcription and formatting work. This change is very impactful on productive work, almost to the point of needing to stop the relieve that aggravation.
Nov 13 2021
Do we need to do anything in the task list for the creation of wiki space for any future Wikisources so that there does not have to be separate new site requests?
Nov 11 2021
Nov 10 2021
Nov 8 2021
Nov 5 2021
Some of these can be managed by metawiki's title blacklist. We already do that for numbers of prominent users, and would do that in this situation where duplicity is being attempted. Happy for a strings of regex to be provided to the talk page to achieve this, also noting that we have the antispoof ability there too.
Nov 3 2021
It would be really nice if this got a bit of love. It is 13 years old, and with so many links being https by default it is becoming a pussy bedsore of a problem
Nov 2 2021
Also noting that I had a similar issue with Pywikibot and its response in fail to login was equally confusing as it was talking about api changes for login with breaking changes. So it lead me off on a bit of a wild goose chase.
Nov 1 2021
Oct 29 2021
Name: Thomas Charles Turberville
Gender: Male
Event Type: Birth
Birth Date: 2 Jun 1825
Birth Place: St Nicholas, Worcester, Worcestershire, England
Denomination: Baptist
Father: Thomas Turberville
Mother: Mary Turberville (formerly Daniell)
South Africa, Cape Province, Civil Deaths, 1895-1972. Salt Lake City, Utah: FamilySearch, 2013.
Name: Frank Selden Turberville
Gender: Male
Age: 79
Death Date: 25 Aug 1941
Death Place: Albany, Cape Province, South Africa
FHL Film Number: 4532652
@Charles_Matthews h
Oct 21 2021
That happens from any filtered abuselog listing
Oct 8 2021
Not certain whether there should be consideration of self-reupload and reupload. For the sake of AbuseFilters, that is not necessary as we can utilise page_first_contributor for those needs.
Oct 5 2021
Oct 3 2021
This one can be wiped from prep and output.
Oct 2 2021
Sep 30 2021
Sep 27 2021
[current firefox browser]
Sep 22 2021
Sep 20 2021
time heals everything? worked a few days later
If it is too hard to do an automated process, then maybe we can have an advanced functionality, Either something were we can exclude a page name, or an intermediary page where we can grab all the pages into a list, and then checkbox them for inclusion, and allow the manual deselection of pages for exclusion. It is problematic at this time that many works are pretty much excluded. I have deleted half a dozen of uploads due to this issue.
Sep 18 2021
Maybe was at the time, though still failing now.
Sep 13 2021
@Omer_abcd this is a reason to also consider whether a filter should be public or private
Sep 12 2021
Sep 10 2021
Sep 6 2021
Sep 4 2021
Sep 3 2021
The Tablet
Brooklyn, New York
19 Jun 1926, Sat • Page 1
The Morning News
Wilmington, Delaware
18 Jul 1893, Tue • Page 2
Aug 30 2021
Aug 28 2021
Aug 26 2021
Aug 17 2021
Aug 16 2021
Aug 14 2021
I am still seeing plentiful spambots in the abuselog. so yes, little to no difference
We are again being hammered by spambots, and they are again clogging up the Abuselog despite them being blacklisted days or weeks ago. Could we please see if there could be implementation of the suggested change. There is nothing more despairing in doing the hard work to get controls in place and having to have abuselogs bombed with the spambots. Thanks.
Aug 13 2021
I still think that it should just be easier to hide a problematic publicly viewable abuse report, that can be by deletion or setting an individual report to non-public. ~~~~
Aug 9 2021
Aug 8 2021
Aug 7 2021
Aug 5 2021
This has broken the Wikisources who were neither notified nor tagged. Bit ugly.
Aug 2 2021
Jul 31 2021
Jul 27 2021
Jul 25 2021
@Ninovolador In cases where there are endnotes in a chapter, I have done it two different ways, neither using "ref follow"
Until someone analyses what is happening in the lint component for what is otherwise non-problematic code elsewhere, then who knows.
Jul 20 2021
I am not certain that this would require a community consensus of Commons. As I remember it, these restrictions have pretty much come from staff over the days. If push comes to shove. let us have the capacity to upload it to English Wikisource and everyone else can go and work out their own requirements, and when they do, then we can migrate it to Commons.
Is there more that needs to be done to get this undertaken? Any questions? Any problems. It seems a fairly simple request, has the consensus of our community as a needed group/role. Thanks.