Document
stringlengths 87
1.67M
| Source
stringclasses 5
values |
|---|---|
The Market's Disregard for Alphabet Should Make Investors Smile
Thecurrent stock marketis in no mood to tolerate any earnings misses, whether from a young upstart or a trillion-dollar company. Alphabet (NASDAQ: GOOGL), the parent of Google, found that out the hard way. It missed on analysts' top- and bottom-line estimates, and was punished with a more than 9% drop in its shares the next day.
Sure, Alphabet's earnings were lukewarm. But the market's sell-off of its shares, largely based on one quarter's performance and on top of the pullback over the past year, seems like an overreaction. Placing Alphabet's results in the context of the current economic environment, and looking at its future prospects, actually suggest that now may be an enticing time for long-term investors to add Alphabet shares.
Earnings were mixed, but not nearly as bad
Alphabet's overall revenue for the third quarter (ended Sept. 30) was up by only 6%, reaching $69.1 billion. Google services -- its largest segment at 88% of total revenue and consisting mostly of the ad business -- grew by just 2.5% to $61.4 billion. Both numbers were quite uninspiring. There wasn't much good news on the profitability front, either. The operating margin fell to 24.8% from 32.3%, and the net income margin contracted to 20.1% from 29% a year ago.
While the reported quarter's numbers don't look great, they also don't tell the full story when seen in isolation. Businesses are lowering their ad budgets with growing uncertainty around the economy as inflation stays high and interest rates continue climbing. Alphabet saw pullbacks in ad spending in Q3 from several sectors, including mortgage, lending, insurance, and crypto.
The strong U.S. dollar further dampened the company's numbers. Foreign exchange headwinds lowered year-over-year revenue growth by a notable 5%.
Finally, Alphabet was overcoming a really tough year-over-year comparison as sales had surged by a whopping 41% in Q3 2021. Considering all those factors, the company's modest growth is not a big surprise.
Image source: Getty Images.
CEO Sundar Pichai expects Alphabet to sharpen its focus on managing expenses with slower hiring in the coming quarters. That should help improve its margins in a tepid growth environment.
Even the big trillion-dollar stalwarts like Alphabet -- whose Google Search, YouTube, Maps, and Android products are so central to daily life -- aren't entirely immune to economic cycles. Looking at the big picture rather than placing too much emphasis on a few quarters can better validate the investing thesis.
The long-term story looks intact
The good news is that the current economic downturn isn't Alphabet's first rodeo. It successfully navigated major economic headwinds, including the 2001 dot-com crash and the 2008 global financial crisis. In many ways, Alphabet is in a dramatically better position to not only weather the ongoing macroeconomic storm but get even stronger.
Consider that the company's various products have over one billion users. Google Search, the engine that fuels Alphabet's growing product ecosystem and the ad revenue, has a 91% of the market share. Android, the mobile operating system, has a 71% market share.
Viewers across the globe watch over 700 million hours of YouTube content daily, and YouTube Shorts -- the company's TikTok competitor -- now has over 1.5 billion monthly users. And Alphabet hasn't even begun to monetize that service.
The essential nature of Alphabet's services in today's life makes it a top destination for advertisers, and that seems unlikely to change anytime soon. Alphabet has efficiently translated its product-driven moat into financial success with smart leadership and execution.
METRICS 2017 2018 2019 2020 2021 CAGR
Revenue ($billion) 111 137 162 183 258 23.5%
Free cash flow ($billion) 24 23 31 43 67 29.4%
Data source: Company earnings releases. CAGR = compound annual growth rate.
Alphabet's balance sheet is also plenty sound with over $116 billion in cash and equivalents on its balance sheet, and a nominal $15 billion in long-term debt. With that kine of liquidity, Alphabet has been able to invest over $123 billion in research and development and $108 billion in capital expenditures from 2017 through 2021 -- extending its lead in existing products and inventing new products.
Savvy investors realize that the sheer scale of its business, stickiness of its products, future potential ahead of it, and financial resilience make Alphabet one of the most attractive businesses. It's simply too hard for rivals to compete with Alphabet.
The valuation makes the decision even easier
Despite Alphabet's strengths, the current economic environment, the market's obsession over short-term results, and overall pessimism about tech stocks are driving a sell-off in Alphabet's shares.
But that sell-off means an opportunity for those willing to hold shares for the long term. On both a price-to-earnings and price-to-free cash flow basis, shares of Alphabet are trading toward the lower end of their 10-year values.
GOOGL PE Ratio data by YCharts
Near-term economic turbulence may cause Alphabet's shares to be volatile, but investing in this high-quality business at today's discounted price can produce exceptional returns in the long run.
10 stocks we like better than Alphabet (A shares)
When our award-winning analyst team has a stock tip, it can pay to listen. After all, the newsletter they have run for over a decade, Motley Fool Stock Advisor, has tripled the market.*
They just revealed what they believe are the ten best stocks for investors to buy right now... and Alphabet (A shares) wasn't one of them! That's right -- they think these 10 stocks are even better buys.
See the 10 stocks
*Stock Advisor returns as of September 30, 2022
Suzanne Frey, an executive at Alphabet, is a member of The Motley Fool's board of directors. Kaustubh Deshmukh (KD) has positions in Alphabet (A shares) and Alphabet (C shares). The Motley Fool has positions in and recommends Alphabet (A shares) and Alphabet (C shares). The Motley Fool has a disclosure policy.
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.
|
NEWS-MULTISOURCE
|
CVS difference for ais/ai-00169.txt
Differences between 1.12 and version 1.13
Log of other versions for file ais/ai-00169.txt
--- ais/ai-00169.txt 2001/03/22 22:24:53 1.12
+++ ais/ai-00169.txt 2001/12/06 01:22:01 1.13
@@ -156,18 +156,16 @@
!ACATS test
-Create a C-Test to check an anonymous object is finalized if a transfer of
+Test C761012 checks that an anonymous object is finalized if a transfer of
control or exception causes its innermost enclosing master to be left.
-(Test, 7-1-0, ARG Letter Ballot, February 2001). The test would be similar
-to C760008.
+(Test, 7-1-0, ARG Letter Ballot, February 2001).
-Create a C-Test to check that it is not a bounded error for an explicit call
+Test C760010 checks that it is not a bounded error for an explicit call
to Adjust or Finalize to propagate an exception.
-The test would insure that Program_Error is not propagated by such a call.
(No Test, 3-3-2 (2/3rd majority required, but not achieved), ARG Letter Ballot,
February 2001). This seems unlikely to be wrong in a compiler, and not very
-common in any case. (Editor's note: After the vote, it was discovered that
-existing ACATS test C760010 already checks this.)
+common in any case. (Editor's note: After the vote, the existing test was
+discovered.)
Test C761011 checks that if a finalize invoked due to finalization of
an anonymous object propagates an exception, other finalizes due to be
Questions? Ask the ACAA Technical Agent
|
ESSENTIALAI-STEM
|
Wikipedia:Sockpuppet investigations/OvskMendov1/Archive
Suspected sockpuppets
The account is already blocked by User:Johnuniq for email spam, but has since confessed to being a sock of this globally-banned user and claimed to have a sockfarm. Let's find out whether that's the case with CU (i.e. sleeper check). Jasper Deng (talk) 08:54, 7 January 2024 (UTC)
* Two more accounts added based on this comment by implicating them in the same spam.--Jasper Deng (talk) 09:08, 7 January 2024 (UTC)
Comments by other users
See Administrators' noticeboard/Incidents for a report of similar activity by and. Johnuniq (talk) 09:11, 7 January 2024 (UTC)
Clerk, CheckUser, and/or patrolling admin comments
* Summary: Three accounts already blocked, appear to be part of the same email spam farm. Fourth account consistent with the others, but technical data doesn't permit a more specific finding.
* Detailed findings: Proxy use makes it impossible to find certain answers here. A good reminder that p2p proxies should indeed be blocked. So, the CU data is consistent with these accounts all being controlled by the same person, but it is not possible to confirm this. Please note that I'm being very specific. The data is "consistent with", but that's all. I can say and and do indeed appear to be part of the Wikipedia Sucks email spam based on technical data, as noted by the above linked comment from El C, here. So, WP:SOCK or WP:MEAT. The technical data on Ovsk does not support that conclusion but does not refute it. The technical data is consistent with that account being controlled by the same person as the others, but simply used for commenting on admin noticeboard threads rather than email spam, but this is not the only possible explanation. I have no access to information about the claimed sockmaster, OvskMendov1, as that account does not exist on en.wiki. All of the accounts apart from Ovsk are already blocked. Due to the extensive use of proxies, I found no sleeper accounts. Ovsk should be evaluated based on behaviour and username rather than technical data. To the extent I'm permitted, I'm happy to clarify my findings. --Yamla (talk) 15:22, 8 January 2024 (UTC)
* CU-blocked Ovsk for trying to gain access to other people's accounts, and per Open proxies. --Blablubbs (talk) 15:38, 8 January 2024 (UTC)
* Four accounts are already blocked. The fourth one (master) does not exist on English Wikipedia. Closing. Vanjagenije (talk) 18:06, 9 January 2024 (UTC)
Suspected sockpuppets
* ( originally filed under this user)
I am being harassed by the named editor and their socks. They make no edits but each has sent me this email: "Hi,
I see that you have recently been blocked from Wikipedia.
I run a forum called Wikipedia Sucks! at the website https://wikipediasucks.co, which is free to join, and you can share your experiences as to why you were blocked, if you think it was unfair.
We know from experience that the vast majority of people who were blocked from Wikipedia were blocked for being critics of the way that Wikipedia works, as they hate criticism.
We would appreciate you sharing your story so that the world can know how bad Wikipedia really is.
Thank you, and we look forward to hearing from you on Wikipedia Sucks!"
I have replied to each one on their talk page and explained that I have not been blocked recently and am not interested in helping them. I do not have a vendetta against Wikipedia or any editor, although an admin here is harassing me off-wiki for the legitimate activity of using my user space as a draft space for article creation. That is clearly allowed, but they don't like the topic so are harassing and stalking me. (They do this at a different wiki-hate site, Wikipediocracy, where I am not registered or participate, but I can see their nasty comments and accusations about me there. A kind soul here alerted me to their activities there. Other admins have encouraged me to take this to ArbCom, but I don't trust that process. I need other help that is not open to the public or the nasty admin. Private suggestions, by email, would be welcomed.)
I want these emails to stop. Some type of IP range block may be necessary. Is there a way to block new editors who are not yet autoconfirmed from misusing email? -- Valjean (talk) ( PING me ) 16:35, 11 January 2024 (UTC) Valjean (talk) ( PING me ) 16:35, 11 January 2024 (UTC)
* Jo-Jo Eumerus, I would normally never include the email, but this is the only evidence I have, and it does not out or dox anyone. Feel free to abbreviate that mention. I would appreciate any help you can provide. Thanks. -- Valjean (talk) ( PING me ) 17:40, 11 January 2024 (UTC)
* BTW, I am likely not the only one receiving these emails. -- Valjean (talk) ( PING me ) 17:42, 11 January 2024 (UTC)
Comments by other users
Clerk, CheckUser, and/or patrolling admin comments
I am not sure that posting the email in public is OK per WP:EMAILABUSE I see that all these accounts have been globally locked by stewards and the Wikimedia Foundation, but apparently aren't linked to any known master/WMF-banned user. As for your question, I believe we can block individual accounts from sending email, but not non-autoconfirmed users in general. What could be done is to run a checkuser on the underlying accounts and see if they are on common range(s) with no legitimate user creation that we can block account creation from. So long way short, this seems like a reasonable case for CU. Jo-Jo Eumerus (talk) 17:16, 11 January 2024 (UTC)
* This is the Wikipedia Sucks email spammer, who we're currently calling OvskMendov1, so I'll merge this case there. CUs and others are very much aware of this, and are working on it, and that's about all I can say. Unfortunately a rangeblock isn't going to be possible here. P.S. I don't think posting the email is a privacy issue, since it's just spam (I double-checked with an OSer who agreed with me). Thanks, Spicy (talk) 19:44, 11 January 2024 (UTC)
|
WIKI
|
Adoptable Cookbooks List
Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks
Supermarket Belongs to the Community
Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.
Select Badges
Select Supported Platforms
RSS
minitest-handler (30) Versions 0.0.7
Installs and configures minitest-chef-handler
Berkshelf
Policyfile
Knife
cookbook 'minitest-handler', '= 0.0.7'
cookbook 'minitest-handler', '= 0.0.7', :supermarket
knife supermarket install minitest-handler
knife supermarket download minitest-handler
README
Dependencies
Quality -%
Cookbook: minitest-handler
Author: Bryan McLellan btm@loftninjas.org
Author: Bryan W. Berry bryan.berry@gmail.com Copyright: 2012 Opscode, Inc.
License: Apache 2.0
Description
This cookbook utilizes the minitest-chef-handler project to facilitate cookbook testing.
minitest-chef-handler project: https://github.com/calavera/minitest-chef-handler
stable minitest-handler cookbook: http://community.opscode.com/cookbooks/minitest-handler
minitest-handler cookbook development: https://github.com/btm/minitest-handler-cookbook
Attributes
node[:minitest][:path] - Location to store and find tests, defaults to /var/chef/minitest
Usage
• The node run list should begin with 'recipe[chef_handler]', 'recipe[minitest-handler]'
• Each cookbook should contain tests in the 'files/default/tests/minitest' directory with a file suffix of '_test.rb'
Minitest: https://github.com/seattlerb/minitest
Examples
Tradition minitest
class TestApache2 < MiniTest::Chef::TestCase
def test_that_the_package_installed
case node[:platform]
when "ubuntu","debian"
assert system('apt-cache policy apache2 | grep Installed | grep -v none')
end
end
def test_that_the_service_is_running
assert system('/etc/init.d/apache2 status')
end
def test_that_the_service_is_enabled
assert File.exists?(Dir.glob("/etc/rc5.d/S*apache2").first)
end
end
Using minitest/spec
require 'minitest/spec'
describe_recipe 'ark::test' do
# It's often convenient to load these includes in a separate
# helper along with
# your own helper methods, but here we just include them directly:
include MiniTest::Chef::Assertions
include MiniTest::Chef::Context
include MiniTest::Chef::Resources
it "installed the unzip package" do
package("unzip").must_be_installed
end
it "dumps the correct files into place with correct owner and group" do
file("/usr/local/foo_dump/foo1.txt").must_have(:owner, "foobarbaz").and(:group, "foobarbaz")
end
end
For more detailed examples, see here
No quality metric results found
|
ESSENTIALAI-STEM
|
Blake Continues His Turnaround by Defeating No. 2 Nadal
It was a performance that not only a mother could love: full of huge, bold forehands and deep first volleys, of astonishing defense and sportsmanlike behavior. But after James Blake put the finishing but hardly delicate touches on one of the most remarkable upsets of the tennis season, it was not the shot-making and court coverage that made the deepest impression on his mother as she watched from the stands on this crystalline late-summer Saturday at the United States Open. ''You don't know how I feel when I see him smiling like that,'' Betty Blake said as she watched her son celebrating with the crowd and his rowdy cheering section after his 6-4, 4-6, 6-3, 6-1 victory over second-seeded Rafael Nadal in the third round. ''To see him smiling again without it being crooked. He would smile and only half of it would work, and you knew he wasn't really smiling because he was still wondering whether he'd ever play again.''
|
NEWS-MULTISOURCE
|
User:TedderBot/NewPageSearch/Canadianmusic/archive
archived entries
* by started at 23:12, 16 May 2011, score: 99
* by started at 09:19, 18 May 2011, score: 109
* by started at 09:24, 18 May 2011, score: 119
* by started at 09:29, 18 May 2011, score: 109
* by started at 09:35, 18 May 2011, score: 109
* by started at 17:57, 15 May 2011, score: 218
archived entries
* by started at 13:03, 27 May 2011, score: 99
archived entries
* by started at 11:12, 24 May 2011, score: 119
archived entries
* by started at 14:19, 26 May 2011, score: 99
archived entries
* by started at 11:51, 31 May 2011, score: 238
archived entries
* by started at 17:52, 03 June 2011, score: 10
* by started at 11:06, 04 June 2011, score: 10
archived entries
* by started at 23:51, 08 June 2011, score: 99
archived entries
* by started at 13:55, 11 June 2011, score: 10
archived entries
* by started at 23:59, 11 June 2011, score: 99
* by started at 12:09, 13 June 2011, score: 436
* by started at 02:53, 12 June 2011, score: 218
* by started at 13:06, 13 June 2011, score: 99
archived entries
* by started at 20:33, 14 June 2011, score: 426
* by started at 18:22, 14 June 2011, score: 10
archived entries
* by started at 10:58, 16 June 2011, score: 218
* by started at 12:03, 16 June 2011, score: 99
* by started at 19:36, 15 June 2011, score: 208
archived entries
* by started at 13:42, 19 June 2011, score: 208
archived entries
* by started at 23:02, 24 June 2011, score: 99
* by started at 11:04, 24 June 2011, score: 99
* by started at 01:52, 25 June 2011, score: 99
* by started at 18:24, 22 June 2011, score: 99
* by started at 19:23, 04 July 2011, score: 218
archived entries
* by started at 11:24, 29 June 2011, score: 99
* by started at 19:09, 28 June 2011, score: 20
* by started at 15:23, 28 June 2011, score: 198
* by started at 16:12, 28 June 2011, score: 208
archived entries
* by started at 07:31, 30 June 2011, score: 10
* by started at 11:02, 30 June 2011, score: 10
archived entries
* by started at 17:40, 06 July 2011, score: 99
archived entries
* by started at 09:28, 05 July 2011, score: 99
archived entries
* by started at 12:59, 06 July 2011, score: 10
* by started at 13:37, 06 July 2011, score: 10
archived entries
* by started at 03:23, 08 July 2011, score: 20
* by started at 17:04, 09 July 2011, score: 208
* by started at 13:55, 08 July 2011, score: 208
* by started at 11:30, 09 July 2011, score: 208
* by started at 09:58, 08 July 2011, score: 99
archived entries
* by started at 15:32, 05 November 2012, score: 426
* by started at 15:05, 12 November 2012, score: 436
* by started at 12:48, 11 November 2012, score: 20
* by started at 11:29, 13 November 2012, score: 20
* by started at 10:40, 13 November 2012, score: 20
* by started at 00:05, 10 November 2012, score: 317
archived entries
* by started at 17:16, 17 November 2012, score: 99
archived entries
* by started at 21:50, 18 November 2012, score: 198
archived entries
* by started at 11:50, 21 November 2012, score: 20
archived entries
* by started at 17:02, 22 November 2012, score: 99
archived entries
* by started at 19:55, 23 November 2012, score: 20
archived entries
* by started at 11:14, 24 November 2012, score: 218
archived entries
* by started at 14:02, 25 November 2012, score: 218
archived entries
* by started at 11:06, 26 November 2012, score: 10
archived entries
* by started at 17:18, 27 November 2012, score: 10
* by started at 21:35, 26 November 2012, score: 228
* by started at 21:10, 26 November 2012, score: 228
* by started at 22:44, 26 November 2012, score: 426
* by started at 23:19, 26 November 2012, score: 228
* by started at 17:36, 27 November 2012, score: 446
archived entries
* by started at 06:57, 28 November 2012, score: 317
archived entries
* by started at 11:21, 01 December 2012, score: 99
* by started at 21:30, 28 November 2012, score: 10
* by started at 16:38, 29 November 2012, score: 10
* by started at 16:25, 29 November 2012, score: 10
archived entries
* by started at 15:37, 30 November 2012, score: 297
* by started at 17:55, 30 November 2012, score: 198
archived entries
* by started at 06:05, 02 December 2012, score: 208
* by started at 10:27, 02 December 2012, score: 10
archived entries
* by started at 10:44, 04 December 2012, score: 10
* by started at 20:30, 03 December 2012, score: 218
* by started at 23:27, 03 December 2012, score: 208
archived entries
* by started at 12:30, 06 December 2012, score: 208
archived entries
* by started at 13:10, 08 December 2012, score: 396
* by started at 09:10, 08 December 2012, score: 317
archived entries
* by started at 22:04, 08 December 2012, score: 10
archived entries
* by started at 02:58, 10 December 2012, score: 426
* by started at 17:26, 10 December 2012, score: 852
archived entries
* by started at 17:47, 12 December 2012, score: 99
archived entries
* by started at 11:34, 13 December 2012, score: 436
archived entries
* by started at 13:48, 21 December 2012, score: 99
* by started at 17:55, 21 December 2012, score: 20
* by started at 11:55, 21 December 2012, score: 99
* by started at 05:14, 18 December 2012, score: 208
* by started at 14:12, 21 December 2012, score: 208
* by started at 14:02, 22 December 2012, score: 317
|
WIKI
|
France to convene Middle East peace conference on Jan. 15
PARIS (Reuters) - France will convene some 70 countries on Jan. 15 for a Middle East peace conference in Paris, its foreign minister said on Thursday, and will invite the Israeli and Palestinian leaders to meet separately at its conclusion. France has repeatedly tried to breathe new life into the peace process this year, holding a preliminary conference in June where the United Nations, European Union, United States and major Arab countries gathered to discuss proposals without the Israelis or Palestinians present. The plan was to hold a follow-up conference before the end of the year with Israeli Prime Minister Benjamin Netanyahu and Palestinian President Mahmoud Abbas involved to see whether the two sides could be brought back to negotiations and revive moribund peace talks. Netanyahu had repeatedly rejected the conference proposal. “France is still determined to hold a conference in Paris to reaffirm the necessity of a two-state solution,” Jean-Marc Ayrault told journalists. “January 15 is the date that has been fixed and 70 countries are invited. We are not going to give up now.” A French diplomatic source said invitations would also be sent to Netanyahu and Abbas to meet French president Francois Hollande to outline the results of the conference. The source said that with uncertainty surrounding how the next US administration would handle the issue it was more important than ever to deal with the issue. “You can see that it’s even more justified in this context,” the source said. Ahead of a UN Security Council vote at the UN later on Israeli settlements, Ayrault declined to say how Paris would vote, but repeated that settlements were illegal. “We will look at this text carefully. The ongoing settlements completely weaken the situation and create tensions and move Us away from a two-state solution”. Reporting by John Irish; Editing by Maya Nikolaeva and Richard Balmforth
|
NEWS-MULTISOURCE
|
I Crossed the Streams, Ray
March 3, 2011 — Posted by Scott Bain
I like tools. I'm old enough to remember what it was like to develop software with a simple text editor (VI, anyone? Emacs? How about See? I'll bet nobody remembers See.exe…) Then you'd compile it at the command line, manually run the linker, etc… and I appreciate how much our tools have improved over time. I love intellisense, source trees, version control, context highlighting, the wonderful way resharper allows you to fix problems en-situ, and all that.
But I also know that the more powerful your tools are, the more you can become dependent on them and, worse, the easier it is to misuse them.
A good example of this is the use of automatic mocking tools like NMock, Easymock, Rhinomocks, and the like. I'm not focusing here on a specific tool or approach, but these are frameworks which are capable of generating your mock objects for you. The dynamic tools (my preference) can actually do this at runtime, while a given test is running, requiring no additional source code in your project. Nice.
They also make it easy to create a mock that is both conditionable and inspectable. A conditionable mock is one that the test can "program" to return different values. An inspectable mock is one that will "remember" what happens to it during the test so that the test can verify that it was the right stuff. If you are unfamiliar with mocking, you can visit the mock object page at our pattern repository for more details and examples.
But… just because you can do something does not mean you should.
Let's say object O, if operating properly, should produce value V when given parameter P. A typical unit test would create an instance of O, pass it P and assert that V was returned. Now let's further stipulate that object O, in order to fulfill this requirement, interacts with another object, which we will call S (for service). Using a dynamic mocking tool we could, if we like, mock out S and have the mock record the interaction between O and S, then the test could inspect the mock afterward to ensure that the interaction was what the test expects.
You can do this with hand-crafted mocks, but the tools make it so easy to do. Usually this is just a single method call on the mock's control… something like: control.verify();
Sometimes the interaction between objects and systems ("workflow") is specified by requirements, and as such you'd expect a test to verify it. But very often a given workflow is simply the implementation the developer has chosen, and might be refactored at some point into a better or more advantageous implementation. When we refactor, we are not changing behavior, and we expect our tests to continue to pass as a guarantee that we're doing what we expect; refactoring and not enhancing, changing, or decaying the behavior of the system.
In other words, perhaps the test above should simply verify that O, given P, returns V, and not how it manages to accomplish this. Perhaps we should be free to change how it does so without causing the test to fail. If the test verifies that O interacts with S in a specified way, we would not be free to change this in refactoring.
I'm not saying either thing is right in all cases, I am saying that the tool makes it easy to ignore the question, and to verify many workflows that should not be part of testing. This tightly couples tests to implementation and makes refactoring very difficult.
I'm not picking on mocking tools here, this is just an example. Tools that speed up reflection (and thus make it easy to break encapsulation on types), clever techniques for testing private methods on classes, etc… these all add power but potentially cause us to avoid thinking things through.
When I started woodworking, I decided not to buy a table saw. I cut wood using a Japanese woodworker's draw-saw. It takes longer (much longer), but in order for me to harm myself with my draw-saw it would literally take the kind of effort the guy in "127 Hours" put into removing his arm. With a table saw I could dismember myself effortlessly in seconds.
Being a good developer is about your brain, not your tools. I'm not saying you should avoid powerful tools (though I still don't own a table saw), but that you should not allow the power they give you to cause you to stop thinking.
As usual, I encourage any comments or thoughts at our Lean Programming Group yahoo forum.
-Scott-
---------------------------------------------------------------------------------------------------------
Subscribe to our blog Net Objectives Thoughts Blog
Share this:
About the author | Scott Bain
Scott Bain is an consultant, trainer, and author who specializes in Test-Driven Development, Design Patterns, and Emergent Design.
Blog Authors
Al Shalloway
Business, Operations, Process, Sales, Agile Design and Patterns, Personal Development, Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Cory Foy
Change Management, Innovation Games, Team Agility, Transitioning to Agile
Guy Beaver
Business and Strategy Development, Executive Management, Change Management, Lean Implementation, Transitioning to Agile, Lean-Agile, SAFe
Israel Gat
Business and Strategy Development, DevOps, Lean Implementation, Agile, Lean, Kanban, Scrum
Jim Trott
Business and Strategy Development, Analysis and Design Methods, Change Management, Knowledge Management, Lean Implementation, Team Agility, Transitioning to Agile, Workflow, Technical Writing, Certifications, Coaching, Mentoring, Online Training, Professional Development, Agile, Lean-Agile, SAFe, Kanban
Ken Pugh
Software Design, Design Patterns, Technical Writing, TDD, ATDD, Coaching, Mentoring, Professional Development, Agile, Lean-Agile, Lean, SAFe, Kanban, Kanban Method, Scrum, Scrumban, XP
Marc Danziger
Business and Strategy Development, Change Management, Team Agility, Online Communities, Promotional Initiatives, Sales and Marketing Collateral
Scott Bain
Analysis and Design Methods, Agile Design and Patterns, Software Design, Design Patterns, Technical Writing, TDD, Coaching, Mentoring, Online Training, Professional Development, Agile
Tom Grant
DevOps, Analyst, Analysis and Design Methods, Innovation Games, Lean Implementation, Lean-Agile
|
ESSENTIALAI-STEM
|
Macarena (disambiguation)
"Macarena" is a 1993 song by Los del Río most well known for its 1995 remix, as well as the name of its accompanying dance.
Macarena may also refer to:
* Macarena (name), Spanish given name
* Virgin of Hope of Macarena, Catholic Virgin from Seville, Spain
* "Macarena", a song by Damso
* "Macarena", a song by Pietro Lombardi
* The Macarena (drag queen), Spanish drag queen
Places
* Macarena, Seville, a neighborhood in Seville, Spain
* Puerta de la Macarena (Seville), a wall gate in Seville
* La Macarena, Meta, a village in Meta Department, Colombia
* Serranía de la Macarena, a mountain range in Colombia
|
WIKI
|
Talk:North Carroll High School
North Carroll High was proposed for deletion. This page is an archive of the discussion about the proposed deletion. This page is no longer live. Further comments should be made on the article's talk page rather than here so that this page is preserved as an historic record. The result of the debate was CONSENSUS NOT REACHED though since the article was improved all votes were to keep.
Untitled
Non-notable high school. --LeeHunter 17:26, 27 Oct 2004 (UTC)
* Delete: The author isn't even sure where it is and has trouble writing in standard English. No sign is provided in the article that the school is remarkable in any way. Geogre 17:57, 27 Oct 2004 (UTC)
* Allow me to point out that this article qualifies as a speedy delete for being a substub from which nothing could grow (inasmuch as the author didn't know where the school was) and for being nonsense (incomprehensible sentence sthat showedn o effort at al by the author). However, some people are hyperventilating over schools. No argument on why schools are inherently needed, just "Well, the whole system won't crash if they're there." I've done a fair bit of historical research. When the archeologists of the present appear in 50 years, they will not go to an encyclopedia to find out about routine high schools: they'll go to reliable, informative sources like local county records. If they want to know what one child thought about it, they'll go to whatever Internet archive exists and look at the school's own website. They won't come here. We can't do the job, don't need to do the job, and shouldn't be doing the job of cataloging routine schools without discussion. Geogre 20:14, 27 Oct 2004 (UTC)
* I disagree that this is a substub "from which nothing could grow." Clearly there is a lot of factual information about this school that could be added. Also, we are not solely working towards being a record of information that archeologists would look to us for in fifty years time. Surely this would not be where they would go to find information on most historical notable persons, because there are other sources of information on those people; but we still have articles on important historical personages. Posiduck 00:31, 28 Oct 2004 (UTC)
* I was only talking about the "useful" argument for school inclusion. To me, it seems like the argument for universal school inclusion is only that we provide a service to information or to browsers. I think we do not, on the former. To the latter, I think that way lies Everything2.com. The reason that we have historically notable people is that it is at least the hypothesis of Wikipedia that we might achieve as good or better with our open model as others have with peer reviewed proprietary services. I think the farther back in history a thing is, the better we can do, because we can have multiple researchers culling from stores of information. When things get right up to the second, again we do better, because we don't have a production lag. Where we do worst is in stuff like schools, armies, national economies, and other things that change quickly and where massive information is required and where the information is not easy to get. Otherwise, I think my "doughnut shop" analogy is in play. I think we should have notable schools. I just ask that a school be notable (and therefore something that can be discussed rather than just entered into a list). As it turns out, this article is by a vandal. Also, it was a substub to which nothing could be added on its face because it did not give editors an idea of where to go. That we are clever enough to figure it out anyway is just a bonus. Geogre 03:49, 28 Oct 2004 (UTC)
* Geogre; While I can respect our difference of opinion on the issue of school notability, I would ask that you don't leap to the conclusion that the contributor was a vandal. Careless and green, perhaps, but making a test page and a short stub on his own high school does not make him de facto a vandal. Besides, I think we'd both agree that regardless of whether or not he was trying to vandalize the wikipedia, if the stub he created was about a notable topic, and not false or nonsense, we should keep the article and expand it (though keep an eye on him if he is indeed vandalizing). Does that make sense? Posiduck 04:33, 28 Oct 2004 (UTC)
* I based that charge on the contribution of Harry Anuszewski by the same person. That article is a crude schoolroom pun. The contributor had only that and this. I think in this case the contributor didn't make a useful stub. I think that was our doing. The contributor was, I think, vandalizing and getting jollies, but he gave a valid name of a school and a state, and we did all the rest. It's only pertinent in that I fear that school articles, when they get to VfD, are getting radically different appraisals by virtue of being schools. They're being instantly built up, where an article on the daughter of a Congressman wouldn't. (I regard a congressional daughter as equally inherently notable.) Geogre 13:21, 28 Oct 2004 (UTC)
* Delete, no claim or evidence of notability. Sietse 18:01, 27 Oct 2004 (UTC)
* No vote. Withdrawing vote to delete. Not voting to keep. Because of Mark Richards' expansion, it is now a real article about a non-notable school. [[User:Dpbsmith|Dpbsmith (talk)]] 20:20, 28 Oct 2004 (UTC) Delete. Wikipedia is not greatschools.net. Or publicschoolreview.com. Which seem to me to be doing a fine job. The website cited, NorthCarrollHigh.com, does not appear to exist, by the way, which seems odd. The town of Hampstead, Maryland does exist and is in fact located in Carroll County. [[User:Dpbsmith|Dpbsmith (talk)]] 18:24, 27 Oct 2004 (UTC)
* keep, school articles are easily verifiable, and in my opinion, schools (like towns) are inherently notable. Posiduck 18:28, 27 Oct 2004 (UTC)
* Does anybody actually verify them? [[User:Dpbsmith|Dpbsmith (talk)]] 18:39, 27 Oct 2004 (UTC)
* Well that's an entirely separate question, perhaps there should be a wikiproject specifically for fact-checking school information. At any rate, I think its a separate issue from whether or not this article ought to be deleted. I cleaned up the article somewhat, and added a stub notice. Posiduck 18:52, 27 Oct 2004 (UTC)
* Well, it's not an entirely separate question, since if there isn't a wikiproject in place it isn't as "easily verifiable". -- WOT 23:03, 27 Oct 2004 (UTC)
* I often do verify them. anthony 警告 04:23, 28 Oct 2004 (UTC)
* Keep I am becoming somewhat disturbed at the level of deletionism occuring for seemingly worthy articles. There little, if any, harm in keeping interesting and esoteric material. If someone does not want to know about this topic then they will not be subjected to it, yet it will be here for people who do want to know about it.--ShaunMacPherson 18:30, 27 Oct 2004 (UTC)
* And if we delete it, it will be here, listing at GreatSchools, for people who want to know about it. And here, Public School Review listing, for people who want to know about it. And, of course, here McFly listing, for people who want to know about it. So, what's the problem? [[User:Dpbsmith|Dpbsmith (talk)]] 18:55, 27 Oct 2004 (UTC)
* Well, the existence of that information in other places doesn't seem to be a good reason not to also have it here. Posiduck 19:23, 27 Oct 2004 (UTC)
* Why not have it here as well, As well Jimbo Wales said the goal of Wikipedia is to have the sum of all human knowledge, and that sum of knowledge includes important institutions like schools. --ShaunMacPherson 21:04, 27 Oct 2004 (UTC)
* Schools are not important in and of themselves. Chris 02:54, 28 Oct 2004 (UTC)
* publicschoolreview.com and greatschools.net aren't free. mcfly.org is, but it's not editable (yet, anyway). anthony 警告 04:32, 28 Oct 2004 (UTC)
* Delete, I'm disturbed at the level of inclusionism for seemingly unworthy articles. Shaun, How the !@#$ is this article worthy? "X high school is a high school in Y state. It is located near P city in Q county. It has been recently renovated." Substitute appropriate values for any school and it'll be true. Generic articles with no notable content are not encyclopedic. -Vina 19:30, 27 Oct 2004 (UTC)
* Look at this, and tell me you don't think just about any school could be expanded in a similar way. Posiduck 20:25, 27 Oct 2004 (UTC)
* No, it couldn't be, because there isn't a large pool of contributors like User:Gerald Farinas. Look at the edit history of Moanalua_High_School. Articles do not grow by themselves,...
* Couldn't be, or won't be? There is a difference. One is about whether or not the article has the capacity to be expaned, the other is your prediction about the interest level of contributors. Posiduck 00:31, 28 Oct 2004 (UTC)
* No they do not, however you are not even giving them a chance to grow.--ShaunMacPherson 21:17, 27 Oct 2004 (UTC)
* ...there need to be people to do the work of writing them, people that care about the subject matter. I can see that there are several people dedicated to voting "keep" on school articles, but I don't yet see a lot of activity in the way of expanding them.
* The last 4 hours of my time has been spent in here voting. If you want articles to be expanded upon then I suggest you get busy writing them and not in here causing others to divert their time in making the articles that you want 'activity' in.--ShaunMacPherson 21:17, 27 Oct 2004 (UTC)
* The point was that if you're so keen to have one-line articles kept, go expand them into something useful. VfD is usually judged on a case-by-case basis. This vote is not about whether all schools should be kept, it's about why this school should be kept. Eton College is in, but that doesn't mean this should. Eton is a notable public school, this school is unremarkable. In the same way that Albert Einstein is in here, but I am not. Einstein is one of the most important (if not the most important) physicists ever. I am a lowly student. Chris 02:54, 28 Oct 2004 (UTC)
* ShaunMacPherson, spend your time as you like. Relax and stop trying to control something that's not very controllable. Accept the fact that some schools are going to be deleted and some are going to be kept. There's no consensus, no likelinood of achieving one, so schools will be debated case by case and the decisions aren't going to be exquisitely consistent. The range of opinion clearly includes people that believe that all school articles, no matter how short, badly written, incomplete, inaccurate, and non-notable the school should be kept, even if it's an elementary school. It also includes people that believe that superb articles about non-notable high schools should be deleted. In actual fact, many articles about schools do get deleted so there's no point in asserting as SimonP has that "these articles get kept anyway." And many get kept. So there's no point in arguing against their being listed here, since the outcome is variable. Trying to control the process by investing personal energy is not a recipe for happiness. When the deletionists are asleep, out of town, or working on articles more school articles will be kept, and vice versa. Hop into VfD when you feel like it, vote as you wish, spend your time as you please, and don't pretend that you're saving the world. We're not talking about human embryos, we're talking about very poor, very short, articles about non-notable schools, typically by anons. Think in specifics, not abstractions. If some dedicated person contributes half-a-dozen superb articles about borderline-notable schools and they get deleted in some parliamentary maneuver by deletionists and the contributor leaves Wikipedia in a huff, then we can talk about it. [[User:Dpbsmith|Dpbsmith (talk)]] 09:42, 28 Oct 2004 (UTC)
* There's no point in an article like this one. <IP_ADDRESS> isn't Gerald Farinas and isn't coming back to expand the article. And as for Posiduck, he has not only not expanded the article, he has removed material from it. By and large people are not that interested in working on school articles about schools they have no personal connection with, and most school articles stand or fall on the energy and writing ability of single contributors [[User:Dpbsmith|Dpbsmith (talk)]] 21:09, 27 Oct 2004 (UTC)
* Look at it this way; lets say there was some Gerald Farinas for this particular high school. And they turned it into an amazing page. Would you vote to delete it then? Based on the reasoning you are giving here, I think not. At least, I haven't seen the Hawaiian school I linked to on the deletion block. So, the subject matter isn't the problem. Now, is "currently a stub" a good reason to delete? No. "Not expandable" would be, but clearly, it is expandable. Perhaps if high schools weren't voted to be deleted so often, people who care about those high schools might realize what they could do here, and we'd have more Gerald Farinas. Posiduck 00:31, 28 Oct 2004 (UTC)
* Keep. Agree with Posiduck and ShaunMacPherson. -- Radman1 20:16, 27 Oct 2004 (UTC)
* Delete. Indrian 21:52, Oct 27, 2004 (UTC)
* Delete - Geogre pretty much stated how I feel. Ian Pugh 22:17, 27 Oct 2004 (UTC)
* Delete. No realistic potential to become encyclopaedic. -- WOT 23:03, 27 Oct 2004 (UTC)
* Delete. — Bill 23:07, 27 Oct 2004 (UTC)
* Delete. I agree with Vina. NeoJustin 23:28 Oct 27, 2004 (UTC)
* Delete if fewer than 370 students attend this school, keep otherwise. I don't really mind either way, but a 370 person town was unanimously voted for keeping a few days ago, so I feel we should be consistent. Shane King 23:32, Oct 27, 2004 (UTC)
* Schools are not towns. Schools are not important in and of themselves. New schools go up every day. New towns do not. Chris 02:54, 28 Oct 2004 (UTC)
* Delete. Non-notable, as are most of these school articles, but that doesn't bother those who would prefer to attack the motives of those of us who believe in making a real, valid encyclopedia instead of a Garbageopedia. Why don't you all work on McFly, which will accept anything? RickK 23:39, Oct 27, 2004 (UTC)
* Why don't the people who think we shouldn't include all of the Factual NPOV information we can go start some slimwiki project which contains only that information a traditional encyclopedia would? It seems unfair for you to say that because I disagree with you about whether or not schools are notable, I should go work on another project. Posiduck 00:31, 28 Oct 2004 (UTC)
* McFly doesn't accept direct contributions anyway. anthony 警告 12:16, 1 Nov 2004 (UTC)
* Keep. Mark Richards 00:49, 28 Oct 2004 (UTC)
* Delete. Joke or test, could have been a speedy. Andrewa 01:05, 28 Oct 2004 (UTC)
* On what grounds would this be a speedy? Posiduck 02:14, 28 Oct 2004 (UTC)
* On the grounds of being a joke/test page. Chris 02:55, 28 Oct 2004 (UTC)
* Right, except, let's say that we didn't have a page on Louis the Fifteenth, and someone created it as a joke/test (not containing false information, but instead containing very small amounts of correct information). Surely we should amend that article rather than deleting it. It seems as though it should only count as a joke or test page if the content is false or the content clearly indicates that it is a test page. Posiduck 04:05, 28 Oct 2004 (UTC)
* Keep. School. anthony 警告 01:21, 28 Oct 2004 (UTC)
* D One line, no evidence of notability, Google seems to agree. The Keep voters are not providing valid reasons for their votes other than "why not just keep it?" - a point which has been validly answered several times. Chris 02:54, 28 Oct 2004 (UTC)
* I urge you to reconsider your position. Here is reasoning in support of keeping articles about schools.
* Articles about schools would contain factual verifiable NPOV content.
* There is evidence of how robust an article about a "non-notable" school can become: Moanalua_High_School
* Many, many newcomers seem to create articles about schools. I.E. many future wikipedians could begin by creating a school article and then, as a result become more active members.
* A fully robust article on any given high school is unlikely to emerge in one or two short edits, but given practically any stub, someone can add a little bit to it at a time; (the general idea of the wiki process).
* A growing number of wikipedians consider schools to be, on the whole, notable merely in virtue of being schools.
* And, finally, in light of those considerations, and because we ought to catalogue as much verifiable, NPOV knowledge as possible, unless there are very good reasons to eliminate an article on a school, it should be kept. And I, for one, don't consider "not notable" to be a good objection, and I think the objection "unlikely to blossom into an article" is overly pessimistic.
* Posiduck 03:25, 28 Oct 2004 (UTC)
* Verifiable and NPOV is not enough to make something worth having. What would you think if I literally went and created an article on, say, my pet Iguana, my neighbor's birds, the sidewalks of my neighborhood, the sidewalks of somebody else's neighborhood, a random bus stop in Cleveland, some graffiti I saw in a bathroom stall, the menus at local food stands, some kid I met, or similar things. Would you actually vote to keep such stuff? --Improv 19:43, 28 Oct 2004 (UTC)
* I'd be surprised if you can write a verifiable, factualarticle on some graffiti you saw in a bathroom stall, and to be honest, it looks like a straw-man argument. But if you think you can, go ahead, and we can vote on it. Mark Richards 23:37, 28 Oct 2004 (UTC)
Kill it or I'm going to have to create an article on Saratoga High School, which Steven Spielberg thought was the worst experience of his life. Obviously we need an article on Eton, just as obviously we don't need one on every high school in the world. Gene Ward Smith 03:55, 28 Oct 2004 (UTC)
* Delete. . Surprised? :) --Improv 04:24, 28 Oct 2004 (UTC)
* From the OED: encyclopedic: "that aims at embracing all branches of learning; universal in knowledge, very full of information, comprehensive." In exactly what way do schools fail this criteria? Posiduck 05:07, 28 Oct 2004 (UTC)
* I'm especially impressed as how you've managed to beg the question twice in one sentence. anthony 警告 13:31, 28 Oct 2004 (UTC)
* Delete. Fuzheado | Talk 04:46, 28 Oct 2004 (UTC)
* Comment: My claim above that this is a joke or test and a possible speedy was based on the link that I supplied, showing that the user's only contributions were this and a related joke or test page also listed for deletion. You might like to read the original text they contributed. Despite a lot of comment and work since, as I write this the only material yet added to the article is a latitude and longitude, so the only claim to notability remains The school has recently been renovated, now spelled correctly. If we keep that, we will be a laughingstock. This goes a bit deeper than being a test case for high schools. No useful content, no change of vote. Andrewa 19:08, 28 Oct 2004 (UTC)
* I made some changes. Mark Richards 19:25, 28 Oct 2004 (UTC)
* What we now have is an actual article, about a non-notable school. I'm not going to vote to keep, but I'm simply going to withdraw my delete vote, as I do not care whether this article is kept or deleted. [[User:Dpbsmith|Dpbsmith (talk)]] 20:20, 28 Oct 2004 (UTC)
* Merge and redirect to a Schools section of Hampstead, Maryland. The Steve 19:45, Oct 28, 2004 (UTC)
* Keep (change of vote). Now a reasonable article. Too much content to merge. Andrewa 21:22, 28 Oct 2004 (UTC)
* Keep. Trollminator 00:07, 29 Oct 2004 (UTC)
* Comment. I am glad someone actually took some time to attempt improving one of these articles rather than just complaining. I still do not think it is notable enough, but this is certainly a step in the right direction. Indrian 01:58, Oct 29, 2004 (UTC)
* Keep. older ≠ wiser 16:55, Oct 30, 2004 (UTC)
* Keep - David Gerard 12:51, 31 Oct 2004 (UTC)
* Keep — siro χ o 10:28, Nov 1, 2004 (UTC)
This page is now preserved as an archive of the debate and, like other '/delete' pages is no longer 'live'. Subsequent comments on the issue, the deletion or on the decision-making process should be placed on the relevant 'live' pages. Please do not edit this page.
|
WIKI
|
Wikipedia:Articles for deletion/Rocabu
The result of the debate was delete. -- ( drini's page ☎ ) 01:07, 17 January 2006 (UTC)
Rocabu
Non-notable "religion" some guy made up. 109 google hits, mostly his own forums posts. Delete.-Halidecyphon 00:07, 12 January 2006 (UTC) Don't delete this article. I personally have been to the Temple of Sugarloaf Drive and I must say he's for real and so is this group. Just because you all aren't open to new things doesn't mean they aren't valid. -- Unsigned comment by User:<IP_ADDRESS>
* Delete. And many of the 103 (YMMV) hits don't seem to have anything to do with him. Schutz 00:43, 12 January 2006 (UTC)
* Delete as per nom. Lukas 11:42, 12 January 2006 (UTC)
* Delete as utterly non-notable, and unverifiable to boot. Stifle 09:05, 13 January 2006 (UTC)
* No, but it means they're not encyclopedic. Have a look at WP:NOT if you like. And please sign your comments, it's only polite. -Halidecyphon 21:34, 13 January 2006 (UTC)
Rocabu is a vibrant religion who's numbers are growing every day. —Preceding unsigned comment added by <IP_ADDRESS> (talk) 02:33, 21 April 2009 (UTC)
|
WIKI
|
I believe that, in Ruby 1.8, Continuation.call raises
RuntimeError.new "continuation called across trap"
in situations that should be allowed.
The error occurs when the current cont_protect context is different from
the one that was stored in the continuation object when it was created
(with callcc).
cont_protect is assigned a new unique value whenever a trap is executed.
The original intent seems to have been to ensure that a continuation
created in one trap context (or in the main context) did not get called
on
another. This certainly makes sense, as I could see where Unix signal
handling would be corrupted if the stack were replaced while processing
a different trap.
However...
cont_protect is also assigned a new unique value whenever as string is
evaluated. It is also assigned by rb_protect(), which is exported from
eval.c and used by extensions to handle exceptions raised by ruby code.
As a consequence, for instance, one cannot call an continuation created
(with callcc) while evaluating a string in any other eval string.
The error message in these cases is incorrect, for the problem has
nothing to do with traps of any kind.
Further, I cannot see why an exception is raised at all.
As an experiment, I modified rb_protect() as follows:
VALUE
rb_protect(proc, data, state)
VALUE (*proc) _((VALUE));
VALUE data;
int * volatile state;
{
VALUE result = Qnil;
int status;
PUSH_TAG(PROT_NONE);
if ((status = EXEC_TAG()) == 0) {
result = (*proc)(data);
}
POP_TAG();
if (state) {
*state = status;
}
return result;
}
And I renamed the original rb_protect() to rb_trap_protect() and
gave it "static" linkage. I then modified rb_trap_eval to call
rb_trap_protect() instead of rb_protect().
With this change cont_protect is *only* modified when a trap is
evaluated.
This suppressed the bogus exceptions that had been raised by
Continuation#call and "fixes" my application.
Note, that I'm not the first person to complain about this.
See:
http://www.ruby-forum.com/topic/82927
The self contained test case presented in topic 82927 deals with
continuations across forks, but the issue is related and both are
corrected by the change I proposed above.
Is there really some reason that Continuation.call should be this
restrictive?
If we agree there is none, would you like me to submit this as a
(trivial) patch? It clearly makes the common case of rb_protect()
faster and leaves the eval_trap case unchanged.
- brent
--
Posted via http://www.ruby-forum.com/.
|
ESSENTIALAI-STEM
|
Allergy Basics
Allergic Asthma
Asthma is a respiratory disease that affects the lungs and is intricately linked with allergies. A tendency towards asthma often is inherited. Although we know a lot about asthma and more than 20 million Americans have this disease, we do not know what causes it. This section will explore what we know about allergic asthma.
What Exacerbates Allergic Asthma?
Triggers of allergic asthma include allergens such as mold, pollen, dust-mite and cockroach leavings, and animal dander. Other triggers include an assortment of irritants such as cigarette smoke and stimuli such as cold weather, infections, and exercise.
Being a worrywart or the fearful type may also trigger asthma attacks or make an attack more severe. Emotional stress and bodily reactions are tied together in a bond that is, fortunately, breakable through such means as relaxation and exercise, stress management, and proper nutrition. Other asthma triggers capable of causing (or worsening) asthma symptoms include viral infections, drug allergies, and even positive emotions, such as excitement and laughter.
When asthmatics encounter a trigger, their airways become inflamed and swollen and increase the production of mucus, all of which reduce the supply of air. Wheezing, that whistling sound from the chest that can be heard on exhalation, is the most recognizable asthma symptom, a result of a constricted airway. However, some asthmatics never wheeze. Other symptoms may include coughing, shortness of breath, tightening of the chest, and difficulty breathing.
|
ESSENTIALAI-STEM
|
THE_BLOG
Too Scared to Sleep? What Can You Do?
Being scared or fearful activates our primitive fear response, increasing adrenaline levels and keeping us on high alert. For some it can cause trouble getting to sleep, whereas for others it can result in waking at night or sleep not being restorative.
This post was published on the now-closed HuffPost Contributor platform. Contributors control their own work and posted freely to our site. If you need to flag this entry as abusive, send us an email.
No title
No title
We all have lots of fears. Fears for our health, family and for some personal safety.
Our news headlines are full of things to be frightened of. Advertisers play on our fears to sell us products to protect us or our family. In this setting, we can perceive that there are threats around every corner. It's not surprising that for some, these fears can interfere with sleep. Being scared or fearful activates our primitive fear response, increasing adrenaline levels and keeping us on high alert. For some it can cause trouble getting to sleep, whereas for others it can result in waking at night or sleep not being restorative.
How does fear cause sleep disturbance?
Anytime we are fearful of things or scared, the natural human response is to activate the fight-and-flight response system. This is called the sympathetic nervous system and increases chemicals such as adrenaline, noradrenaline, dopamine, serotonin and histamine. These are the common neurotransmitters involved in maintaining alertness. So when levels of these neurotransmitters are higher it is much harder to switch off and go to sleep. Some people are still able to get to sleep, but find themselves waking at night and unable to get back to sleep.
When we are scared of something, the brain tries to maintain a degree of awareness or alertness whilst the body maintains muscle tone and energy levels. If we do need to escape quickly from a threat, these changes ensure we have both the muscle strength and energy to do so as well as being alert enough to do detect the threat quickly. These are all things that are not part of normal sleep. Good sleep is usually characterised by unawareness, muscle relaxation and low circulating energy levels.
When the sympathetic nervous system is highly active during sleep, a condition sometimes called hyperarousal, the brain monitors the environment more carefully. This can result in people sensing that sleep is lighter with a greater awareness of things going on around them and they are more easily awoken from sleep. Some people can also experience nightmares and acting out behaviours during sleep (parasomnias) as a consequence of muscles being more active.
This type of hyperarousal does not settle quickly. Even once the source of fear is removed the brain and body can remain in a hyperaroused state over weeks and even months. Commonly in my practice I see people who have begun sleeping poorly in the setting of fear. They've addressed their fears or that set of circumstances have passed, but they're still having ongoing difficulties with sleep and a sense of increased agitation and restlessness.
Fear can also make sleep less refreshing
When people sleep in a hyperaroused state as well as sleep feeling light and readily disturbed it is not as refreshing as it would be otherwise. It seems that the heightened state of activation reduces the brain's ability to clear away waste products accumulated throughout the day, part of the restorative nature of sleep.
There is also interesting research showing that turning off the sympathetic nervous system, particularly during REM sleep, is important for reducing the fear component of our experiences. As such, if people have heightened sympathetic nervous system activity after an exposure to fear it can increase the likelihood of getting ongoing nightmares or other disorders such as post-traumatic stress disorder.
This means it is important to recognise people who have been exposed to a fearful stimulus early and intervene so that they are less likely to develop hyperarousal and post-traumatic stress disorder in the future.
What be done to reduce the impact of fear on sleep?
• Many of our fears are perceived rather than real threats - One of the most important strategies is to recognise our fears for what they are. In modern society we are generally very safe and many of our fears are perceived rather than real threats. It can sometimes be hard to step back from our situation to get this wider perspective but attempting to do so is usually helpful. This is particularly so for our children who often do not have a broader context in which to place their fears and can become overly concerned about things they see on television or in the news which can make threats seem more likely than they are in real life.
• Distraction techniques - If we are awake at night and unable to break the cycle of fear or feeling scared, then using relaxation strategies to distract ourselves from those thoughts can be helpful. Focussing on muscle relaxation or visual imagery can change focus from fearful thoughts to concentrating on muscles or visual images and allow sleep to return. Some audio files with good examples of muscle relaxation of visual imagery exercises are available from the University of Western Sydney and Dartmouth.
• Mindfulness - One of the ways of getting a broader perspective on fear as well as being less focussed on fearful thoughts is mindfulness. The practise of mindfulness is training ourselves in present focussed observation and disconnecting from the judgement and emotion involved in our experiences. This can help us to see fears for what they really are and give insights into whether we should in fact be fearful or whether our fears are not justified or over exaggerated. Mindfulness also has a role in reducing symptoms of disturbed sleep and hyperarousal. Examples of guided mindfulness meditations can be found at A Mindful Way and UCLA's Mindfulness Awareness Research Center.
If you are having trouble with sleep despite the above measures, talk to your health professional about it. They may refer you to a psychologist or a sleep physician if they feel that further investigation or treatment is needed. Some of the treatments health professionals may use are:
• Cognitive behavioural therapy (CBT-I) - I'll often use CBT-I to help with disturbed sleep in the setting of fear. Often, even though sleep problems start in the setting of fear, once the fear has passed, sleep problems continue because of changed thinking and behaviour around sleep. These can be addressed using CBT-I in the same way as this technique is used to treat insomnia.
• Medications - can be used to reduce the sympathetic nervous system response. For example, alpha-blockers or beta-blockers can be effective at reducing nightmares and disturbed sleep that are part of post-traumatic stress disorder.
So, if fear is impacting on your sleep, there are things that you can do and it's also worth talking to your health professional to help get your sleep back on track.
Does fear impact on your sleep? What have you tried to help?
This post originally appeared in a modified form in the online sleep resource, SleepHub. You can follow David Cunnington on Facebook and Twitter.
|
ESSENTIALAI-STEM
|
Talk:El Chapo (TV series)
Add cast
Add the cast please. Also, please add information about when is it going to be released on Netflix. — Preceding unsigned comment added by <IP_ADDRESS> (talk) 17:15, 10 April 2017 (UTC)
Number of Episodes Season 1
Can anyone explain the number of episodes in season 1 to me? The table lists 7 and according to the introduction, Nexflix published 9 episodes (which also is the info I get elsewhere). Are episodes 8 and 9 just missing from the table (if so, why?) or is there a different reason for that? Krevitos (talk) 17:31, 16 October 2017 (UTC)
* Because in the table of episodes we are guiding is by its broadcast in Univision, and according to this only 7 episodes were released for television, while on Netflix were released 9 episodes.-- Philip J Fry : Talk 22:42, 16 October 2017 (UTC)
* Shall we put a hidden message in the article for editors who may be thinking of "fixing" the episode count? MX ( ✉ • ✎ ) 22:50, 16 October 2017 (UTC)
Juan Carlos Oliva(s)?
Article at Juan Carlos Olivas is unsourced except for imdb but this has the final "s". Cast list in this article omits that "s". Which is correct? Pam D 08:18, 6 November 2017 (UTC)
Fourth season
Will there be a fourth season or not? — Preceding unsigned comment added by <IP_ADDRESS> (talk) 22:11, 25 August 2018 (UTC)
|
WIKI
|
User:GregoryAmico
The Reb Meeker Movie is a 2020 american online YouTube film starring Reb Meeker from the movie Cars 3. The film was originally gonna be uploaded on November 22nd, but it was soon uploaded on November 19th, 2020.
|
WIKI
|
Dan Callaghan
Unhelpful errors in CherryPy with _cpmodpy
Recently I found myself stumped by a very unhelpful error message, while trying to mount a CherryPy app behind Apache using the built-in adapter for mod_python, _cpmodpy. I was seeing a text/plain 500 response containing only:
Unrecoverable error in the server.
This message comes from cherrypy._cperror.bare_error, which is called by _cpmodpy if an exception is raised outside of the ordinary CherryPy request handling code. In my case, some erroneous initialisation code was raising an exception when the CherryPy tree was being set up, causing the handler to drop out to the bare_error call.
Unfortunately a traceback isn't included in the error message, even if request.show_tracebacks is True, since the CherryPy Request object is not in scope (and may never have existed) at that point; I guess in this case the best thing to do is be conservative and not show the traceback. A traceback is apparently logged to somewhere though — but (maybe due to a misconfiguration?) it wasn't showing up in my Apache logs.
In the end I hacked _cpmodpy.py to show me a traceback, revealing the error in my initialisation code. Here is the trivial patch:
--- _cpmodpy.py
+++ _cpmodpy.py
@@ -202,7 +202,7 @@
except:
tb = format_exc()
cherrypy.log(tb)
- s, h, b = bare_error()
+ s, h, b = bare_error(tb)
send_response(req, s, h, b)
return apache.OK
Originally published . Tagged: , , , .
|
ESSENTIALAI-STEM
|
# KUTTL Test Harness
KUTTL is a declarative integration testing harness for testing operators, KUDO, Helm charts, and any other Kubernetes applications or controllers. Test cases are written as plain Kubernetes resources and can be run against a mocked control plane, locally in kind, or any other Kubernetes cluster.
Whether you are developing an application, controller, operator, or deploying Kubernetes clusters the KUTTL test harness helps you easily write portable end-to-end, integration, and conformance tests for Kubernetes without needing to write any code.
Table of Contents
# Installation
The test harness CLI is included in the KUTTL CLI, to install we can install the CLI using krew (opens new window):
krew install kuttl
You can now invoke the KUDO test CLI:
kubectl kuttl test --help
See the KUTTL installation guide for alternative installation methods.
# Writing Your First Test
Now that the KUTTL CLI is installed, we can write a test. The KUTTL test CLI organizes tests into suites:
• A "test step" defines a set of Kubernetes manifests to apply and a state to assert on (wait for or expect).
• A "test case" is a collection of test steps that are run serially - if any test step fails then the entire test case is considered failed.
• A "test suite" is comprised of many test cases that are run in parallel.
• The "test harness" is the tool that runs test suites (the KUTTL CLI).
Be aware that KUTTL CLI expects a kuttl-test.yaml needs to be available, see setup the kuttl kubectl plugin if you didn't do so yet.
# Create a Test Case
First, let's create a directory for our test suite, let's call it tests/e2e:
mkdir -p tests/e2e
Next, we'll create a directory for our test case, the test case will be called example-test:
mkdir tests/e2e/example-test
Inside of tests/e2e/example-test/ create our first test step, 00-install.yaml, which will create a deployment called example-deployment:
apiVersion: apps/v1
kind: Deployment
metadata:
name: example-deployment
labels:
app: nginx
spec:
replicas: 3
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx:latest
ports:
- containerPort: 80
Note that in this example, the deployment does not have a namespace set. The test harness will create a namespace for each test case and run all of the test steps inside of it. However, if a resource already has a namespace set (or is not a namespaced resource), then the harness will respect the namespace that is set.
Each filename in the test case directory should start with an index (in this example 00) that indicates which test step the file is a part of. Files that do not start with a step index are ignored and can be used for documentation or other test data. Test steps are run in order and each must be successful for the test case to be considered successful.
Now that we have a test step, we need to create a test assert. The assert's filename should be the test step index followed by -assert.yaml. Create tests/e2e/example-test/00-assert.yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
name: example-deployment
status:
readyReplicas: 3
This test step will be considered completed once the pod matches the state that we have defined. If the state is not reached by the time the assert's timeout has expired (30 seconds, by default), then the test step and case will be considered failed.
# Run the Tests
Let's run this test suite:
kubectl kuttl test --start-kind=true ./tests/e2e/
Running this command will:
• Start a kind (Kubernetes-in-Docker) cluster (opens new window), if there is not already one running.
• Create a new namespace for the test case.
• Create the resources defined in tests/e2e/example-test/00-install.yaml.
• Wait for the state defined in tests/e2e/example-test/00-assert.yaml to be reached.
• Collect the kind cluster's logs.
• Tear down the kind cluster (or you can run kubectl kuttl test with --skip-cluster-delete to keep the cluster around after the tests run).
# Write a Second Test Step
Now that we have successfully written a test case, let's add another step to it. In this step, let's increase the number of replicas on the deployment we created in the first step from 3 to 4.
Create tests/e2e/example-test/01-scale.yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
name: example-deployment
spec:
replicas: 4
Now create an assert for it in tests/e2e/example-test/01-assert.yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
name: example-deployment
status:
readyReplicas: 4
Run the test suite again and the test will pass:
kubectl kuttl test --start-kind=true ./tests/e2e/
# Test Suite Configuration
To add this test suite to your project, create a kuttl-test.yaml file:
apiVersion: kuttl.dev/v1beta1
kind: TestSuite
testDirs:
- ./tests/e2e/
startKIND: true
Now we can run the tests just by running kubectl kuttl test with no arguments.
Any arguments provided on the command line will override the settings in the kuttl-test.yaml file, e.g. to skip using kind and run the tests against a live Kubernetes cluster, run:
kubectl kuttl test --start-kind=false
Now that your first test suite is configured, see test environments for documentation on customizing your test environment or the test step documentation to write more advanced tests.
|
ESSENTIALAI-STEM
|
User:Habst/Collins Kipruto
Collins Kipruto (born 12 April 1994) is a Kenyan middle-distance runner specializing in the 800 metres. He was the overall winner of the 2020 World Athletics Indoor Tour in the 800 m.
Biography
Collins is from Nyahururu, Kenya where he is a Kenya Wildlife Service officer in addition to his athletics career.
At the 2019 Penn Relays, Kipruto anchored the winning Kenyan sprint medley relay team with a 1:47.16 split. This performance led to him qualifying for the 2019 IAAF World Relays, where he competed in the new mixed 2 × 2 × 400 m relay with women's teammate Eglay Nafuna Nalyanya. The team finished 4th across the line, but was later disqualified due to Nalyanya accidentally stepping inside the track.
Kipruto was a regular on the 2020 World Athletics Indoor Tour series, which concluded in February 2020. By virtue of winning the 800 m at the Copernicus Cup, Meeting Hauts-de-France Pas-de-Calais, and the Villa de Madrid Indoor Meeting, Kipruto was the overall Tour winner in the 800 m category.
In March 2021, Kipruto criticised Kenyan president Uhuru Kenyatta's COVID-19 policies requiring athletes to train alone, saying that they would negatively affect his preparations for international competitions.
At the February 2022 Meeting de l’Eure, Kipruto held off Noah Kibet to win the 800 m in a meeting record of 1:47.05. With the 2022 World Athletics Indoor Championships qualifying standard achieved, Kipruto was targeting a podium finish, stating that he knew a win would not be easy considering the competition such as American athlete Craig Engels. At the World Indoor Championships, Kipruto finished fourth in his heat and did not qualify for the finals.
|
WIKI
|
Equifax, Western Union, Priceline settle with New York attorney general over insecure mobile apps – TechCrunch
New York’s attorney general has settled with five tech and financial giants, requiring each company to implement basic security on their mobile apps. The settlements force Credit Sesame, Equifax (yes, that Equifax), Priceline, Spark Networks and Western Union to ensure data sent between the app and their servers are encrypted. Specifically, the attorney general said their apps “could have allowed sensitive information entered by users — such as passwords, social security numbers, credit card numbers, and bank account numbers — to be intercepted by eavesdroppers employing simple and well-publicized techniques.” In other words, their mobile apps “all failed” to properly roll out and implement HTTPS, one of the barest minimum security measures in any modern app’s security. HTTPS certificates (also known as SSL/TLS certificates) encrypt data between a device, like your phone or computer, and a website or app server, ensuring any sensitive data, like credit card numbers or passwords, can’t be intercepted as it travels over the internet — whether that’s someone on the same coffee shop Wi-Fi network or your nearest federal intelligence agency. These certificates are more common than ever, not least because when they’re not incredibly cheap, they’re completely free — and most modern browsers these days will bluntly tell you when a website is “not secure.” Apps are no different, but without a green padlock in your browser window, there’s often very little to know for sure on the face of it that your data is traversing the internet securely. At least, with financial, banking and dating apps — you’d just assume, right? Bzzt, wrong. “Although each company represented to users that it used reasonable security measures to protect their information, the companies failed to sufficiently test whether their mobile apps had this vulnerability,” the office of attorney general Barbara Underwood said in a statement. “Today’s settlements require each company to implement comprehensive security programs to protect user information.” The apps were picked out after an extensive batch of app testing in an effort to find security issues before incidents happen. Underwood’s office follows in the footsteps of federal enforcement in recent years by the Federal Trade Commission, which brought action against several app makers — including Credit Karma and Fandango — for failing to properly implement HTTPS certificates. In taking action, the attorney general gets to keep closer tabs on the companies going forward to make sure they’re not flouting their data security responsibilities. Equifax breach was ‘entirely preventable’ had it used basic security measures, says House report
|
NEWS-MULTISOURCE
|
Herbalzym
Natural treatment for HPV infections (genital warts) and cervical dysplasia, Part 2
October 17, 2010, Featured in Cancer and Natural Medicines, 0 Comments
Viruses are found wherever there is life and have probably existed since living cells first evolved. Most virus infections eventually result in the death of the host cell. Viral infections provoke an immune response that usually eliminates the infecting virus. However, some viruses including those causing AIDS, viral hepatitis, genital warts and cervical cancer evade these immune responses and result in chronic infections. Antibiotics have no effect on viruses. Viral populations do not grow through cell division, because they are acellular. Instead, they use the machinery and metabolism of a host cell to produce multiple copies of themselves, and they assemble in the cell.
Some viruses cause no apparent changes to the infected cell. Cells in which the virus is latent and inactive show few signs of infection and often function normally. This causes persistent infections and the virus is often dormant for many months or years. This is often the case with herpes viruses. Some viruses, such as Epstein-Barr virus, can cause cells to proliferate without causing malignancy, while others, such as papillomaviruses (HPVs), hepatitis B and C viruses are established causes of cancer.
1. hepatitis B virus (HBV): hepatocellular carcinoma (a type of liver cancer)
2. hepatitis C virus (HCV): hepatocellular carcinoma (a type of liver cancer)
3. human papillomavirus (HPV) types 16 and 18, as well as other HPV types: cervical cancer, vaginal cancer, vulvar cancer, oropharyngeal cancer (cancers of the base of the tongue, tonsils, or upper throat), anal cancer, penile cancer
4. Epstein-Barr virus: Burkitt lymphoma; non-Hodgkin lymphoma; Hodgkin lymphoma; nasopharyngeal carcinoma (cancer of the upper part of the throat behind the nose)
5. human T-cell lymphotropic virus 1 (HTLV1): acute T-cell leukemia
Unlike most bacteria, which can be recognized by their distinctly foreign features, a virus becomes invisible as it hides and multiplies inside the infected cells of the host. To enable the immune system to detect viruses, the host cells have evolved an elaborate mechanism called the “antigen presentation pathway. This pathway scrutinizes virtually all actively synthesized proteins in the cell. A few snippets or peptides are produced from the proteins and are ferried to the cell surface by the major histocompatibility complex (MHC) class I molecules. The circulating T cells of the immune system probe the peptide–MHC complexes (pMHCs) on the cell surface to identify and eliminate infected cells. Viruses have evolved various strategies to prevent peptide display by MHC molecules. If any of the key steps in the antigen presentation pathway is blocked, MHC molecules fail to present appropriate peptides.
The intracellular antigen transport machinery TAP in adaptive immunity and virus escape mechanisms.
Immune surveillance obstructed by viral mRNA.
Regulation of protein translation through mRNA structure influences MHC class I loading and T cell recognition.
The MHC class I antigen presentation pathway: strategies for viral immune evasion.
MHC class I antigen presentation: learning from viral evasion strategies.
HPV infections are exclusively intra-epithelial and, theoretically, HPV attack should be detected. Regression of HPV infections is accompanied histologically by a CD4+ T cell dominated Th1 response. However, HPV avoids host defences. How HPV infection remains undetected by the immune system for so long? In this location there is only a limited expression of viral proteins. Other factors contributing to the low level of host immunity are that HPV infection is non-lytic (does not cause death of the infected cell); that a functionally active immune response is generated only at later stages of HPV infection, in post-mitotic suprabasal keratinocytes where all viral genes are expressed; and that only in suprabasal keratinocytes has the HPV DNA been sufficiently amplified to be detected by the host immune-surveillance cells.
The prolonged duration of HPV infections is associated with effective evasion of innate immunity as reflected in the absence of inflammation during virus replication, assembly and release and down regulation of interferon secretion and response thus delaying the activation of adaptive immunity. Thus,for most of the duration of the HPV infectious cycle there is little or no release into the local milieu of proinflammatory cytokines important for DC (dendritic cells) activation and migration and the central signals to kick start the immune response in squamous epithelia are absent.
In addition to the natural low-level immune responses towards HPV, HPV also employs several mechanisms to down-regulate innate and cell-mediated immunity, thus facilitating host immune evasion and persistent infection. Tregs (regulatory T cells: known as suppressor T cells) are a specialized subpopulation of T cells that act to suppress activation of the immune system and thereby maintain immune system homeostasis and tolerance to self-antigens. It is believed that Tregs suppress the immune control of cervical neoplasia and furthermore that suppression of immunity by Tregs will be another hurdle to overcome in therapeutic immunization strategies against cervical neoplasia. The environment, lifestyle, the genetic make-up of the host, and the viral genomic characteristics can also influence the persistence of HPV infection, and consequential diseases.
Immune responses to human papilloma viruses.
High-risk human papillomavirus E7 expression reduces cell-surface MHC class I molecules and increases susceptibility to natural killer cells.
Papillomavirus capsid mutation to escape dendritic cell-dependent innate immunity in cervical cancer.
Frequencies and role of regulatory T cells in patients with (pre)malignant cervical neoplasia.
High-resolution analysis of genomic alterations and human papillomavirus integration in anal intraepithelial neoplasia.
HPV infections disrupt cytokine expression and signalling with the E6 and E7 oncoproteins particularly targeting the type I interferon (IFN) pathway. High doses of IFN can overcome the HPV-mediated abrogation of signalling, and this may be the basis for the therapeutic effects on HPV infections of immune-response modulators. Stimulation of TLRs (Toll-like receptors) results in the activation of innate immune cells such as macrophages and dendritic cells, leading to the production of proinflammatory cytokines and up-regulation of costimulatory molecules. Thus, TLRs provide the “danger signals” required for clearance of infection by innate immune cells and also for the initiation of adaptive immune responses. Activation of TLR7 induces high levels of type I IFNs.
Roles of toll-like receptors in natural interferon-producing cells as sensors in immune surveillance.
Molecular basis for the immunostimulatory activity of guanine nucleoside analogs: activation of Toll-like receptor 7.
HPV: from infection to cancer.
Reversal of human papillomavirus-specific T cell immune suppression through TLR agonist treatment of Langerhans cells exposed to human papillomavirus type 16.
Particle size and activation threshold: a new dimension of danger signaling.
Imiquimod (Aldara) is commonly used topically to treat warts on the skin of the genital and anal areas. However, Imiquimod does not cure warts, and new warts may appear during treatment. Imiquimod does not fight the viruses that cause warts directly, however, it does help to relieve and control wart production. Imiquimod is a topical immune response modifier that acts as a TLR7 agonist. Study shows that combination of locally delivered imiquimod with systemic anti-CD40 immunotherapy drive systemic antitumor immune responses.
The antiviral activity of Toll-like receptor 7 and 7/8 agonists.
Mechanism of action and other potential roles of an immune response modifier.
Reversal of human papillomavirus-specific T cell immune suppression through TLR agonist treatment of Langerhans cells exposed to human papillomavirus type 16.
Detection of human papillomavirus (HPV) 16-specific CD4+ T-cell immunity in patients with persistent HPV16-induced vulvar intraepithelial neoplasia in relation to clinical impact of imiquimod treatment.
Locally administered TLR7 agonists drive systemic antitumor immune responses that are enhanced by anti-CD40 immunotherapy.
The immune system counters with too little of a Th1 response, the virus remains concealed and the infection becomes active or chronic. It is well established that immune functioning decreases as we age. During aging, a Th2 dominant immune response becomes established. A Th1 immune response dominates at an earlier age. A Th2 dominant immune response cannot protect us from most infections and cancer.
Dendritic cells (DCs) are potent antigen presenting cells (APCs) that possess the ability to stimulate naive T cells. They comprise a system of leukocytes widely distributed in all tissues, especially in those that provide an environmental interface. DCs are derived from bone marrow progenitors and circulate in the blood as immature precursors prior to migration into peripheral tissues. Within different tissues, DCs differentiate and become active in the taking up and processing of antigens (and their subsequent presentation on the cell surface linked to major histocompatibility (MHC) molecules. Upon appropriate stimulation, DCs undergo further maturation and migrate to secondary lymphoid tissues where they present antigen to T cells and induce an immune response. When naive CD4 T cells encounter dendritic cells, they can develop into the following:
1. Th1 cells which promote cell mediated immunity (cellular immunity).
2. Th2 cells which promote antibody formation (humoral immunity).
3. Th3 cells which promote tolerance (immune tolerance).
In order to stimulate the production of CD4 T cells that promote cell mediated immunity, dendritic cells must secrete IL-12. If they secrete IL-4, IL-5 and IL-13 instead, the CD4 T cells will promote the secretion of antibody. On the other hand, if the dendritic cells secrete IL-10, tolerance or immune non-responsiveness will occur.
The good news 90% of people with a balanced immune system will clear the virus, without medical treatment, within two years of becoming infected. Smokers or those with suppressed immune systems may need to wait longer. There are many natural agents available to help restore balance in an underactive Th1 immune response. These include:
Omega-3 fatty acids, monounsaturated fats found in olive and hazelnut oils, vitamin A cod liver oil, L-Glutamine, Inosine, Silica, digestive enzymes, friendly intestinal flora or soil based organisms (SBOs), ginseng (Red Korean or concentrated Siberian Ginseng extract), chlorella (spirulina and some other sea vegetables may have similar benefits), thyroid hormones, garlic (raw or aged extract), L-Glutathione (or products that raise levels), DHEA or AED (androstendiol), UV-A light, vitamin E, transfer factor (antigen specific) – protein immunomodulators extracted from colostrum, colostrum, low dose naltrexone, IP6, lentinian and certain other mushrooms, Thymus extracts, licorice root, dong quai, beta 1,3-glucan, noni, neem, gingko biloba, exercise, water (to aid detoxification), a positive attitude and prayer, the ability to forgive and be compassionate, and having long-term goals.
Factors that induce Th2 and suppress Th1 immune reaponse: Processed, heated vegetable oils high in trans-fatty acids and linoleic acid (safflower, soy, canola, corn and sunflower), glucose (white sugar), asbestos, lead, mercury and other heavy metals, pesticides, air and water pollutants, progesterone, prednisone, morphine, tobacco, cortisol (in high doses), HIV, candida albicans, HCV, E coli and many other pathogens, continuous stress, thalidomide, UV-B light, pregnancy, melatonin (conflicting research suggests that high levels induce Th2 while very small amounts induce Th1), alcohol (animals studies show that ethanol definitely suppresses Th1 and induces Th2; beer was not tested and there are some indications it may help), streptococcus thermophilis (sometimes found in yoghurt), candidiasis, circulating immune complexes (CICs – caused by a combination of leaky gut syndrome and poor digestion of proteins due to a lack or HCl and digestive enzymes), sedentary lifestyle, negative attitudes, low body temperature, acid saliva pH, chronic insomnia, inability to dream, weight lifting, and steroids (for muscle gain).
Finally, the great news is that it’s quite possible to solve all these problems and cure your chronic HPV infections, genital warts and cervical dysplasia naturally. We have developed a natural Th1 immune modulator/enhancer “Hepazym™”, and succeeded in clinical treatment of primary HPV-16 and HPV-18 infection of the cervix in women. Don’t be depressed by chronic HPV infections. It can be cured. Hepazym™ has demonstrated how new natural treatment way and approaches make it possible to not only cure, but also to prevent HPV infections.
Comments are closed.
|
ESSENTIALAI-STEM
|
Article
From:
To:
Dann Croghan
Subject:
Re: WSDL - Cannot Unwrap issues [Edit]
Newsgroup:
embarcadero.public.delphi.webservices
Re: WSDL - Cannot Unwrap issues [Edit]
Hello,
I just spent a few minutes on this and, yes, if I'm reading this WSDL correctly, indeed the Service requires WS-Addressing. The top level WSDLs contains not Policy elements but if you look at the other WSDL, https://tapstaging.tax.utah.gov/efile/MFET/WSDL/?wsdl=wsdl0, imported from the top-level one you'll see the following:
{code} <wsp:Policy wsu:Id="WSHttpBinding_MFET_policy"> <wsp:ExactlyOne> <wsp:All> <wsaw:UsingAddressing /> </wsp:All> </wsp:ExactlyOne> </wsp:Policy> {code}
I'll come back to WS-Addressing later. Each operation exposed by the Service also expects a MFETHeader. Here's how you set this header:
{code} procedure TForm16.Button1Click(Sender: TObject); var AMFETHeader: MFETHeader; AService: MFET; ASubmissionList: SubmissionList; I: Integer; begin AMFETHeader := MFETHeader.Create; try AMFETHeader.User := 'user'; AMFETHeader.Password := 'password'; AMFETHeader.Environment := EnvironmentType.P;
AService := GetMFET(False, '', HTTPRIO1); (AService as ISOAPHeaders).Send(AMFETHeader);
ASubmissionList := AService.SubmissionListBySubmissionId('100'); try // Here process response finally for I := 0 to Length(ASubmissionList)-1 do ASubmissionList[I].Free; end; finally AMFETHeader.Free; end; end; {code}
If you hook the OnBeforeExecute event on the RIO you'll see that the above calls generates the following request:
{code} <?xml version="1.0"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Header> <NS1:MFETHeader xmlns:NS1="http://www.fastenterprises.com"> <NS1:User>user</NS1:User> <NS1:Password>password</NS1:Password> <NS1:Environment>P</NS1:Environment> </NS1:MFETHeader> </SOAP-ENV:Header> <SOAP-ENV:Body> <SubmissionId xmlns="http://www.fastenterprises.com">100</SubmissionId> </SOAP-ENV:Body> </SOAP-ENV:Envelope> {code}
Adjust the user/password and Environment appropriately.
But the above will still generate the error you received because that error, as I suspected, is not about a missing MFEFHeader but rather that the Service requires WS-Addressing. I suspect that the service probably wants the minimal WS-Addressing header: with 'To', 'Action', 'MessageID' and (maybe) 'ReplyTo'. Automatic handling of WS-Addressing is something we plan to add to Delphi SOAP. For now, when required, it has to be handled manually.
I tried to add a manual WS-Addressing header. First I added the 'Action' - which is what the service complained about. Once that was done, it complained about the 'To' item. I added that one, and a MessageID. At that point the Service simply returns 400 (Bad Request). So it seems that I'm getting through the WS-Addressing issues. I'm hoping that '400' is the way the Service says "You don't have a valid user/password or submissionId for me to process"... although I can't really confirm this. Here's the request I sent:
{code} <?xml version="1.0"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Header xmlns:wsa='http://www.w3.org/2005/08/addressing'>
<wsa:Action>http://www.fastenterprises.com/MFET/SubmissionListBySubmissionId</wsa:Action>
<wsa:To>
<wsa:Address>https://tapstaging.tax.utah.gov/efile/MFET</wsa:Address>
</wsa:To>
<wsa:MessageID>13F6D3EE-B4C1-4CD8-A16B-BC1852C31D7D</wsa:MessageID>
<NS1:MFETHeader xmlns:NS1="http://www.fastenterprises.com">
<NS1:User>user</NS1:User>
<NS1:Password>password</NS1:Password>
<NS1:Environment>P</NS1:Environment>
</NS1:MFETHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SubmissionId xmlns="http://www.fastenterprises.com">100</SubmissionId>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
{code}
The 'Action' has to match the SOAPAction of the method you're invoking. In the case of this Service, you'll see that the importer generated the following line:
{code} InvRegistry.RegisterDefaultSOAPAction(TypeInfo(MFET), 'http://www.fastenterprises.com/MFET/%operationName%'); {code}
So you just have to substitute %operationName% for whatever operation/method you are invoking.
The 'To' must be the URL to which we're sending requests. You can find that value again in the code generated by the importer:
{code} function GetMFET(UseWSDL: Boolean; Addr: string; HTTPRIO: THTTPRIO): MFET; const defWSDL = 'https://tapstaging.tax.utah.gov/efile/MFET/WSDL/?wsdl'; defURL = 'https://tapstaging.tax.utah.gov/efile/MFET'; defSvc = 'MFET'; defPrt = 'WSHttpBinding_MFET'; {code}
It's the 'defURL' constant that's needed.
The MessageID must be a unique identifier - so I just create a GUID.
If you have a valid user/password/submissionId and can try the above, please let me know if that worked for you.
Cheers,
Bruneau
FYI: Phrase searches are enclosed in either single or double quotes
Originally created by
Tamarack
Sun, 25 Oct 2020 08:42:20 UTC
Copyright © 2009-2020
HREF Tools Corp.
|
ESSENTIALAI-STEM
|
p450 - publications
Predict more p450 - ligand interactions now!
Generation and Characterization of Novel Cytochrome P450 Cyp2c Gene Cluster Knockout and CYP2C9 Humanized Mouse Lines.
Mol Pharmacol. 2012 Aug 23;
Authors: Scheer N, Kapelyukh Y, Chatham L, Rode A, Buechel S, Wolf CR
Abstract
Compared to rodents and many other animal species the human cytochrome P450 Cyp2c gene cluster varies significantly in the multiplicity of functional genes and in the substrate specificity of its enzymes. As a consequence, the use of wild type animal models to predict the role of human CYP2C enzymes to drug metabolism and drug-drug interactions is limited. Within the human CYP2C cluster CYP2C9 is of particular importance, because it is one of the most abundant P450 enzymes in human liver and it is involved in the metabolism of a wide variety of important drugs and environmental chemicals. In order to investigate the in vivo functions of cytochrome P450 Cyp2c genes and to establish a model for studying the functions of CYP2C9 in vivo, we have generated a mouse model with a deletion of the murine Cyp2c gene cluster and a corresponding humanized model expressing CYP2C9 specifically in the liver. Despite the high number of functional genes in the mouse Cyp2c cluster and the reported roles of some of these proteins in different biological processes, mice deleted for Cyp2c genes were viable and fertile but showed certain phenotypic alterations in the liver. The expression of CYP2C9 in the liver also resulted in viable animals active in the metabolism and disposition of a number of CYP2C9 substrates. These mouse lines provide a powerful tool for studying the role of Cyp2c genes, and of CYP2C9 in particular, in drug disposition and as a factor in drug-drug interaction.
PMID: 22918969 [PubMed - as supplied by publisher]
|
ESSENTIALAI-STEM
|
Henricus Marinus Neeb
Henricus Marinus Neeb, often recorded as H.M. Neeb, (22 November 1870 in Muntok, Bangka Island, Sumatra - 15 September 1933 in Bandung, Indonesia) was a Dutch military doctor during the later stages of the long lasting Aceh War. He photographed sights in the area beginning in 1904 including architecture, indigenous peoples, colonial buildings such rail infrastructure and buildings, topography, scenes of Dutch soldiers, and Acehnese killed in the conflict.
Neeb was born in Muntok on Bangka Island on the coast of eastern Sumatra. His father, P. G. Neeb, was also a military doctor.
Neeb studied medicine in Leiden, Netherlands and joined the Royal Netherlands East Indies Army (KNIL) in 1892. He was stationed at the military hospital of Surabaya and other stations before being dispatched to Kotaraja in June 1903. He served under Gotfried Coenraad Ernst van Daalen's command in the regions of Gayo, Alas and Batak, and remained in Aceh until at least 24 November 1907, when he photographed scenes in Sidikalang.
Photographs from a medical congress in Manila to study American hospitals there in 1910 are the only known photographs taken later in his career. He died on 15 September 1933 and is buried in Bandung.
J.C.J. Kempees, Van Daalen's aide-de-camp, published some of his photos in his 1905 book and notes that Neeb utilized a portable dark room. Neeb included detailed captions on his prints.
|
WIKI
|
Wikipedia:Articles for deletion/Bharatiya Jain Sanghatana
The result was soft delete. Based on minimal participation, this uncontroversial nomination is treated as an expired PROD (a.k.a. "soft deletion"). Editors can request the article's undeletion. Daniel (talk) 09:31, 4 September 2021 (UTC)
Bharatiya Jain Sanghatana
* – ( View AfD View log )
Thee seem to be insufficient substantial 3rd party reliable published sources, not press releases or blogs or postings or mere notices See also Draft:Shantilal Muttha and Draft:Shantilal Muttha Foundation, which seem part of the same PR campaign. DGG ( talk ) 05:57, 13 August 2021 (UTC)
* Note: This discussion has been included in the list of India-related deletion discussions. Eastmain (talk • contribs) 08:38, 13 August 2021 (UTC)
* Note: This discussion has been included in the list of Organizations-related deletion discussions. Eastmain (talk • contribs) 08:39, 13 August 2021 (UTC)
Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, ✗ plicit 09:03, 20 August 2021 (UTC) Relisted to generate a more thorough discussion and clearer consensus.
Please add new comments below this notice. Thanks, Less Unless (talk) 09:02, 28 August 2021 (UTC)
* Weak Delete While the current sourcing is insufficient to establish notability per WP:NORG, there could be non-English or offline sources. I'd be happy to change my vote if other sources are presented. -- Ab207 (talk) 15:24, 3 September 2021 (UTC)
|
WIKI
|
Computer Programmer MCQs Quiz Online Tests pdf Download
Practice computer programmer MCQs, computer MCQ for online test prep. Jobs in computing quiz has multiple choice questions (MCQ), computer programmer quiz questions and answers as programmer who writes system software is called, answer key with choices as system programmer, analysis programmer, train programmer and design programmer for competitive exam prep. Free study guide is to learn computer programmer quiz online with MCQs to practice test questions with answers.
MCQs on Computer Programmer Quiz pdf Download
MCQ. Programmer who writes system software is called
1. system programmer
2. analysis programmer
3. train programmer
4. design programmer
A
MCQ. Programmer who works with high level languages and have better understanding with applications are considered as
1. design programmer
2. application programmer
3. analysis programmer
4. train programmer
B
MCQ. People who accept tasks from computer users, processes it and then return user there complete tasks are considered as
1. terminal control staff
2. data control staff
3. peripheral control staff
4. librarian control staff
B
MCQ. Person who keeps disc and tape files up to date for computer installation is called
1. file librarian
2. punch librarian
3. peripheral librarian
4. terminal librarian
A
MCQ. Type of programmer who write programs for a specific user to carry out special instructions is classified as
1. applications programmer
2. analysis programmer
3. train programmers
4. design programmers
A
|
ESSENTIALAI-STEM
|
Trump aide Boris Epshteyn leaving White House, officials say
(CNN)Boris Epshteyn, a special assistant to President Donald Trump who leads the White House's television surrogate operations, is expected to leave the White House, potentially for a position outside the West Wing, two senior administration officials have told CNN. A senior administration official confirmed Epshteyn's expected departure, saying, "We are exploring opportunities within the administration." Epshteyn, who was a campaign surrogate himself, declined to comment when contacted by phone. Epshteyn was also director of communications for Trump's Presidential Inaugural Committee. He gained a reputation in recent months for his testy demeanor and gruff personality in his dealings with national TV news networks.
|
NEWS-MULTISOURCE
|
Achim Gercke
Achim Gercke (3 August 1902 – 27 October 1997) was a German politician.
Born in Greifswald, Gercke became a department head of the NSDAP in Munich on 1 January 1932. In April 1933 he was appointed to the Ministry of the Interior, where he served as an expert on racial matters.
Gercke devised the system of "racial prophylaxis", forbidding the intermarriage between Jews and Aryans. As a student, he had attempted to develop a card index listing all Jews in Germany. His articles outlined Nazi policy on what to do to the Jews during the early phase of the Third Reich, which included expulsion from Germany. He described the just-enacted Nuremberg Laws restricting Jews as provisional measures, which indicated the direction future measures would take. Gercke argued for defining "Jew" as including any person with one-sixteenth Jewish blood. Later in 1942, the Wannsee Conference ultimately defined "Jew" quite differently: Persons having one Jewish grandparent were mostly excluded and even certain persons with two Jewish grandparents might be excluded, if they followed the Christian faith.
In 1932, Nazi Gauleiter Rudolf Jordan claimed that SS Security Chief Reinhard Heydrich was not a pure "Aryan". Within the Nazi organisation such innuendo could be damning, even for the head of the Reich's counterintelligence service. Gregor Strasser passed the allegations on to Achim Gercke who investigated Heydrich's genealogy. Gercke reported that Heydrich was "... of German origin and free from any coloured and Jewish blood". He insisted that the rumours were baseless. Even with this report, Heydrich privately engaged SD member Ernst Hoffman to further investigate and deny the rumours.
In 1935, Gercke was dismissed following allegations of homosexuality. After the war, he worked as an archivist and town clerk.
|
WIKI
|
Oncologist-approved cancer information from the American Society of Clinical Oncology
Printer Friendly
Download PDF
Siblings and Cancer
This section has been reviewed and approved by the Cancer.Net Editorial Board, 7/2012
Key Messages:
• When one child has cancer, it can be challenging for parents to focus on the needs and concerns of the other siblings.
• It’s common for the brothers and sisters of a child with cancer to experience conflicting emotions. They may express these emotions through their behavior.
• Parents can help by keeping the normal routines as much as possible, spending time with the other siblings, talking with each child about their feelings, and letting the children know they are loved.
A child with cancer changes the family dynamics, and these changes are often especially difficult for the healthy siblings. Some parents find that they don't have much energy left to spend with their other children after looking after a sick child. Many parents find it difficult to think about the experience from the viewpoint of the healthy siblings. With a little effort, though, parents can help maintain a family life that feels more normal and takes into account everybody’s needs.
Common emotions experienced by siblings
Brothers and sisters of a child with cancer experience a variety of emotions—many similar to those experienced by parents and other adults. Your child’s age, maturity, and personality all affect their reactions and may include these common and normal emotional responses.
Fear and anxiety. Younger children may fear they caused the cancer or that they might catch it, like the flu. Others may worry about what will happen to the family because of the illness or that their sick brother or sister may die. It is important to allow children to express their fears and to make it safe for them to do so.
Anger. Sometimes a brother or sister is angry with their parents or with the sibling with cancer for not having time for them anymore. Parents can help by allowing the sibling to express this anger in a safe way (see below for suggestions).
Jealousy and resentment. Along with anger, a sibling may be jealous of the attention focused on the child with cancer or resent the fact that the sibling with cancer doesn't have to do chores or go to school.
Loneliness. A brother or sister may feel left out of the family activities, especially if they are centered around hospital stays and doctors visits. Or, they may feel that they have just lost the support and friendship once provided by the child with cancer. A sibling may also miss time with friends when their parents can't take them to after-school activities or to a friend's house to play.
Guilt. Often, the healthy sibling experiences guilt for not being the sick child. In addition, a brother or sister may feel guilty for saying mean things to the sibling with cancer, having bad thoughts about their ill sibling, or for having emotions such as anger and jealousy.
Sadness and grief. Siblings may feel sad for their ill brother or sister and for their parents. They may feel sad that everything seems to have changed. Also, they may grieve the loss of normal family life and a carefree childhood.
Common behaviors observed in siblings
Children often lack the emotional maturity and experience to understand their emotions and may not have words to describe how they feel. Because children often don't talk about how they are feeling, they frequently express their feelings and needs through behavior. The following behaviors are common and normal among siblings of children with cancer:
• Misbehaving or acting out in negative, attention-seeking ways at home or school
• Increased separation anxiety, such as acting "clingy," not wanting to leave mom or dad, or not wanting to go to school
• Withdrawing from the family or wanting to be alone
• Regressing or acting younger, such as a preschooler wanting to go back to diapers or an older child using baby language or sucking his or her thumb
• Demanding or entitled behaviors, such as wanting new toys during every trip to the store or demanding special foods
• Increased physical symptoms, such as headaches, stomachaches, or bedwetting
• Having trouble sleeping and/or nightmares
• Being moody and irritable, including temper tantrums, fighting with parents or siblings, or crying a lot
• Performing worse academically or having difficulty concentrating
• Demonstrating "extra good" behavior; some children try to take care of the rest of the family by being behaving well and suppressing their own feelings
Helping siblings cope
It is impossible for parents to remove all the emotions and fears experienced by siblings; however, parents can help meet the needs of healthy siblings and help them cope with the sibling's cancer.
Get help. Coping with cancer as a family is difficult so don’t feel like you have to do it alone. Neighbors, friends, and family members often want to help but aren’t sure what to do. Give them specific tasks, such as taking siblings to sports practice, or asking someone to help you with grocery shopping to give you time to take the other children out for ice cream. Coordinate these tasks among family and friends by using the tools offered by online communities.
Talk with your other children about cancer. Give them age-appropriate, accurate, and honest information without being overly frightening. Provide frequent updates and encourage them to ask questions. You can say that cancer is a serious illness and that the doctors are doing everything possible to help your brother or sister get better. Appropriate information helps children feel less anxious and prepares them to answer questions from teachers and friends. Read more about talking with your child and talking with your teen about cancer.
Reassure your children. Children need to know that they did not cause the cancer, that it is not contagious, and that you still love them.
Talk with your children about their feelings and worries. Encourage your children to share their feelings with you and reassure them that these feelings are normal and okay. Do not scold the siblings for having negative feelings. Acknowledge that the child with cancer is "lucky" to get special attention and desirable gifts, but "unlucky" to need medical interventions and to feel ill. Let them know they can talk to you at any time and that you will love them no matter what they tell you. Help them find other ways to express themselves, such as writing in a journal, doing art, or playing.
Share your own feelings and fears. Tell the siblings that sometimes you feel sad, scared, and even angry, and what you do to help yourself cope with those difficult feelings.
Spend time with the healthy siblings. If possible, at least one parent should spend time with the other children every day. If you can't be there physically, talk with them on the phone or make a video call. Ask them about their day and tell them how much you miss them when you can't be there.
Involve the siblings with making decisions. When possible, let your other children make choices about things that affect them, such as which friend’s house they would like to go to after school or which parent should come to their concert or sporting event.
Let your other children help. This helps them feel more involved and less isolated. Let the siblings choose toys to take to the hospital, or allow them to read a book or play cards with their sick brother or sister. Although it is okay to ask siblings to help, don't overburden them with extra chores, and let them know how much you appreciate their assistance.
Help your children keep in touch. If the child with cancer must spend time in the hospital, encourage the siblings to keep in touch with cards, letters, and text messages or e-mail, if available. If possible, have the healthy siblings visit the hospital frequently, which can help ease anxiety about what goes on at the hospital.
Encourage the siblings to do things they enjoy. This includes continuing after-school activities and spending time with friends. Let them know that it’s okay for them to want to have fun and to enjoy time away from the worries of home.
Keep things consistent. Try to keep consistent schedules so your children know who will pick them up from school or where they will be eating dinner each night. As much as possible, keep discipline fair and consistent at home. This helps both healthy siblings and the sibling with cancer.
Seek professional help. If your children seem to be struggling despite your efforts, you might consider seeking help from a mental health professional, such as a social worker or child psychologist. Many hospitals have sibling support groups or can recommend counseling for siblings and families of children with cancer.
Take care of yourself. Make sure that you are taking care of your own physical and emotional needs so you can best help all your children.
Upsides for siblings
Many children respond to a sibling with cancer with enormous love, care, and support. Parents often observe positive changes in siblings of children with cancer, such as increased capacity for empathy and compassion, better coping skills, enhanced self-esteem, confidence in responding to adversity, closer relationships with siblings and parents, and greater insight into the things that really matter. When the entire family comes together during a crisis, it provides everyone with a renewed sense of commitment to each other.
More Information
How a Child Understands Cancer
Family Life
Camps and Retreats for Families and Children Touched by Cancer
Additional resources for parents
CancerCare: Helping Children When a Family Member Has Cancer
Additional resources for siblings
CancerCare: CancerCare for Kids
© 2005-2012 American Society of Clinical Oncology (ASCO). All rights reserved worldwide.
|
ESSENTIALAI-STEM
|
Syrian rebels say U.S. won't intervene in south Syria
AMMAN (Reuters) - The United States has told Syrian rebel factions they should not expect military support to help resist a Russian-backed government offensive to regain opposition-held parts of Syria bordering Jordan and the Israeli-occupied Golan Heights. A copy of a message sent by Washington to heads of Free Syrian Army (FSA) groups, which was seen by Reuters, said the U.S. government wanted to make clear that “you should not base your decisions on the assumption or expectation of a military intervention by us”. The United States had earlier warned Syrian President Bashar al-Assad and his Russian allies that violations of a “de-escalation” zone agreed by the United States and Russia last year would have “serious repercussions” and pledged “firm and appropriate measures.” The toughly worded statements had raised the hopes of the Western-backed opposition of a possible American military intervention in the event that the Syrian army’s bombing campaign broadens to an all-out offensive across the southwest. The U.S. message also told the rebels it was left to them alone to decide how to face the Syrian army’s military campaign based on what they saw was best for themselves and their people. “We in the United States government understand the difficult conditions you are facing and still advise the Russians and the Syrian regime not to undertake a military measure that violates the zone,” the message also said. The United States has supported the moderate mainstream FSA faction with millions of dollars worth of arms and paid monthly salaries to thousands of rebels in the course of the seven-year war under a military aid program run by the Central Intelligence Agency. But analysts believe the aid has dropped after U.S. President Donald Trump decided last year to shut down the program. Late on Saturday, Russian jets struck an opposition held town in southwest Syria, opposition sources said, in the first air cover provided by Moscow to an expanding Syrian army offensive. At least 20 raids struck Busra al Harir, a town east of Deraa city that were followed by other strikes on a string of other rebel-held areas at dawn, residents and rebels said. “We don’t care if its Russian air cover or not. We are on the ground and steadfast,” said Abu Ayham, a field commander with Ahrar al Ashaer rebel group. Residents also cited intense air reconnaissance by jets believed to be Russian flying at high altitudes over Deraa city, where rebels control a portion of the provincial capital along the Jordanian border. Syrian state media said rebels had fired indiscriminately on residential areas of the city causing several casualties, adding that the army had hit what it called “terrorist” hideouts. Since the start of the offensive last week, the Syrian government had mostly deployed artillery and rockets. Russian warplanes that were critical to the recapture of other rebel-held areas were conspicuously absent. Throwing in Russia’s full military weight in the campaign to regain southern Syria will weaken the ability of mainstream rebel groups to hold their ground. The southwest is of strategic concern to U.S.-allied Israel, which has this year stepped up attacks on Iran-backed militia allied to Assad. U.S ally Jordan, which has been worried by the escalation, said it was engaged in intensive diplomacy with Washington and Moscow to preserve the zone and prevent a wider confrontation. The loss of opposition-held southern Syria would deal a major blow to the rebel cause. It could secure the reopening of a major international border crossing with Jordan. The southwestern city of Deraa is seen by the opposition as the cradle of the 2011 uprising that began as a peaceful protest movement against Assad’s authoritarian rule but has spread across the country and degenerated into civil war. Reporting by Suleiman Al-Khalidi; Editing by Robert Birsel and Keith Weir
|
NEWS-MULTISOURCE
|
Wikipedia:Village pump (proposals)/Archive 141
Guild or WikiProject of paid editors
* (also posted at Jimbo's talk page and at WT:COI)
I want to ask - at a high and initial level, does anybody here oppose the formation of something like a "guild or WikiProject of paid editors", by paid editors? I have proposed this initially in three places, but I want to also float this balloon here, and if it doesn't get terminally shot down here, I want to go to work doing what I can to help them plan and form it, and then at some point bringing it to a community-wide forum to get validation before it would actually launch.
The notion here is to formalize and build on what is already going at Statement on Wikipedia from participating communications firms, and there is some support among two of the key signatories there, to do this.
If you read self regulation you will see that many industries have a level of self-regulation. The American Bar Association is cited in that article; the ABA operates within the bounds of the law of course, but it has additional rules and ethics, and if you break them, the ABA will throw you out and you can't practice law. Same deal with practicing medicine - you have to be certified by various boards, that are run by the medical profession itself.
If we had something like a guild of paid editors here (again, formalizing what it is going with the Statement), people who are part of it would pledge to follow PAID (disclose, not edit directly, and follow the other policies and guidelines) and the members of the guild would a) watch each other, and b) watch non-members, and c) train new members. They would throw out people who violated PAID or who socked, etc. They would also never: refuse entry to someone who said they would follow the "rules"; never lobby for changes in policies or guidelines; never implement each other's edits; never advertise their services in WP or chase people here.
Outside of that they would be like other editors, and the guild would give them no special privileges.
The community and WMF could say to the public, "There are paid editors who violate WP's rules and are not members of the WP community, and many of them have been banned and have to lie just to write in Wikipedia - they should be avoided. There are paid editors who are members of the community in good standing; people in the Guild of Paid Editors are examples of that, as far as we know."
There are lots of ways this could go wrong if it is set up wrong (there always are) and of course in its execution, but there are many potential benefits.
The thing I am most interested in, is starting to influence the market for paid editing. The public has no idea that there are "white hat" paid editors who are different from "black hat" paid editors, and pretty much the only message that WMF and the editing community put out there, is "paid editing is bad." This leaves the market wide open, and it is kind of like Prohibition in the United States where the gangsters are flourishing. Which is kind of foolish. I am not saying that anybody should endorse paid editing but we should make it clear there are "good guys" and "bad guys".
We could point to the "Statement" now, but that is kind of loose not formal, and if the paid editors themselves form the Guild/WikiProject and invest in it working, paid editors in it will have more of a stake in keeping it clean. And we would all have something more substantial to point to as examples than "signatories of the statement" which is kind of flimsy, and I don't know how rigorous the signatories are in throwing people out who violate their pledges.
If this is effective, it will decrease the amount of undisclosed paid editing that happens from the demand side - from people making better choices if they choose to use a paid editor.
Again, just looking for initial buy-in or "blockers" (to use the WMF dev term) at this very initial stage of thinking. Jytdog (talk) 00:43, 15 July 2017 (UTC)
* I think the idea is worth looking into. • • • Peter (Southwood) (talk): 05:13, 15 July 2017 (UTC)
* One thing to consider is whether members of such a guild should be required to disclose their real identities: a) to the guild, and b) on Wikipedia. • • • Peter (Southwood) (talk): 05:19, 15 July 2017 (UTC)
* Anything that encourages compliance with the COI guideline, utilizing carrots as well as sticks, is constructive. Figureofnine (talk • contribs) 12:10, 15 July 2017 (UTC)
* And now the proposal is dead. The requirement is disclosure, not self doxxing. When you make the rules harder for being honest, you encourage dishonesty. --v/r - TP 14:46, 15 July 2017 (UTC)
* , I miss your point. Could you clarify? • • • Peter (Southwood) (talk): 15:12, 15 July 2017 (UTC)
* User:Pbsouthwood Tparis is kind of emotional about these things and tends to over-react. I think his concern is that we make this onerous paid editors will not use it. In my view the main thing is that paid editors use a stable WP identity and don't sock. Because paid editors who follow PAID need to disclose their employer, many of them do disclose their RW identity in WP. (see signatories to the Statement, linked in the OP) but I don't see a need to place an extra burden on paid editors outside of what is already required in PAID. Jytdog (talk) 19:56, 15 July 2017 (UTC)
* Strong oppose ....in no way should the Wikipedia Community look like it's endorsing paid edited by hosting a special place for these people. We should form a Wiki project that searches out these people and looks over their work.--Moxy (talk) 17:18, 15 July 2017 (UTC)
* WP:WikiProject Integrity was set up years ago to examine the work of paid editors. isaacl (talk) 17:36, 15 July 2017 (UTC)
* User:Moxy, this is not about endorsing, really. I understand that there is a risk that people will take it that way, but it is not that. The points here briefly are:
* 1) paid editing is never going away
* 2) There actually are "white hat" paid editors and "black hat" paid editors, but the public doesn't know this.
* 3) If we were to educate the public, this would do a lot to dry up the market for black hat paid editors
* 4) As part of that, we need something to point to, as "white hat" -- the "guild" would be people who say they follow PAID and the other guidelines and have not been indeffed. In other words as far as we know (always, "as far as we know"), the members are paid editors in good standing. This is essential for communicating to the public
* 5) there would be a bunch of other benefits to the self-regulation and having a centralized location for dealing with certain aspects of paid editing (e.g maybe listing all articles worked on by legit paid editors in one place). There are lots of things we could do with it if it were up and running.
* I hope that all makes sense. But this is very much about dealing with the reality that paid editing is never going away, and thinking about strategies to manage the market for it. Jytdog (talk) 19:51, 15 July 2017 (UTC)
* Just wondering, Jytdog. If the Guild won't work at Wikipedia, why not at Meta-wiki instead? They might form a User Group, seen at meta:Category:Wikimedia User Groups. --George Ho (talk) 18:48, 15 July 2017 (UTC)
* I am not convinced that it won't work in WP. There will be turbulence getting there, but that is not unexpected. But meta could be an option, sure. Jytdog (talk) 19:51, 15 July 2017 (UTC)
* I don't see why such a thing could not be done off-wiki, with a Facebook group or the like. I don't think such a thing belongs on the project. bd2412 T 22:42, 15 July 2017 (UTC)
* Strong oppose - Sorry, Jytdog, but the fact that "paid editing is not going away" is not a reason to give it the imprimatur of our approval, any more than the fact that socking isn't going away is any reason to stop blocking socks and their masters. Beyond My Ken (talk) 20:34, 15 July 2017 (UTC)
* User:Beyond My Ken This is not giving it "approval" and it is disappointing to hear this framed that way. Paid editors who follow PAID (and the other PaG of course) are members of the community in good standing. There is no argument against that, that you or anyone else can make. Let me come at this from a different direction -- you didn't !vote at the MfD on the Statement. How would you have !voted, if you had, why? Jytdog (talk) 21:08, 15 July 2017 (UTC)
* I disagree, allowing such a guild to be formed would indeed give tacit approval to their efforts.Personally, I am opposed to paid editing in any way, shape, or form. The WMF's most recent pronunciation on it tip-toed right up to the line of banning it altogether, and I have no idea why they didn't bite the bullet and do the deed. In any case, paid editing, whether they adhere to WP:PAID or not, is detrimental to our project, as we don't really have the resources to police their efforts properly -- hell, we can barely keep up with outright vandalism, and sock puppets will remain uncontrollable as long as en.wiki (not the WMF, since other language wikis have more stringent rules) continues to stick its head in the sand and disallow "fishing expeditions" when experienced editors smell something rotten and report it, only to be told that an overriding concern for privacy (ha!) is more important. Well, that's bullshit, and so is this. Yes, I want paid editors to be pariahs, and I will oppose anything which will tend to integrate them into the community, whether they follow WP:PAID or not. If that's harsh, well, tough, they shouldn't be attempting to sully the integrity of our project with their PR. Beyond My Ken (talk) 21:26, 15 July 2017 (UTC)
* User:Beyond My Ken taking a moral stance "against paid editing" is like taking a moral stance against drinking alcohol. People feel how they feel about it, but we as a society came to realize people are going to drink, and trying to stop it is pointless. So we regulate it. Likewise, we put PAID in place, but given the nature of this place it is easy for bad faith people to just ignore it. But there are people who follow PAID and we are shooting ourselves in the foot by not acknowledging that. We need to let the public know that good faith PAID editors exist, and we can dry up the market for bad faith paid editors by establishing something more solid for good faith PAID editors to inhabit and maintain - this guild or WikiProject. The moral absolutism is not helpful. We need to move past that by now. This is a strategy to influence the market that works on a bigger scale than the whack-a-mole of catching individuals. (I still do a lot of that work; it needs to keep going, of course). But please do hear me - I am not offering this lightly, and it comes with a lot of thought. So please, put away the emotion. Please. Jytdog (talk) 22:19, 15 July 2017 (UTC)
* Your comparison to Prohibition is silly, frankly, as what paid editors are doing is a job, and their employment is damaging the encyclopedia I've spent a lot of time and effort on improving, and don't wish to see harmed. I fully understand that you have put a lot of thought into this, and I accept that you offer it in total good faith -- I would expect nothing less from an editor such as yourself -- but that doesn't make it any better of an idea. You say that it will "sway the market", and I say that it will throw the doors of the market wide open and make paid editing even less subject to control than it is now, as more and more people realize that they can get away with pure promotionalism and swamp our already meager ability to police it. I ask you to believe that this is a fully rational, well thought out stance which has little, if anything to do with "emotionalism". You asked for opinions on your idea, and this is my opinion: it is a bad idea. Beyond My Ken (talk) 22:33, 15 July 2017 (UTC)
* The point of the Prohibition metaphor, is that doing what we have been doing - namely saying with straight backs and all moral fiber in place, "Paid editing is bad!"..... does absolutely nothing to affect whether people buy the service and what is worse, leaves those purchasers mostly at the mercy of the "gangsters" (the people who sold alcohol lucratively during prohibition)
* tThis reported article in the Entrepreneur (and I mean "reported" - the author went out and talked to people including the WMF) gives no inkling that there are paid editors who are "white hats" and follow policy and there are "black hats". That really, really bothered me. The reporter tried to find out the score and walked away clueless. And communicated that to her audience, which is probably one of our biggest sources of shitty paid articles (startups, business people looking for exposure). I want the public to know there are legitimate people offering paid editing services, who follow policy and that there is a "black market". And just like buying anything on the black market, you do so with risks that you don't take with legit enterprises.... and that using this black market is actually kind of filthy, and actually harms the public good that is WP. The harm comes from undisclosed paid editors who sock and lie and directly dump garbage in WP. It doesn't come from the legit paid editors. Jytdog (talk) 02:54, 18 July 2017 (UTC)
* Oppose. I disagree about the "good" vs. "bad guys" dualism mentioned in the proposal. There are many shades of paid editing, and the best ones still contribute to a systemic bias in favor of recent products and companies, which would usually have gotten fairly decent coverage anyway -- at best we're talking about a "bad guys" vs. "more-or-less neutral guys". There is nothing Wikipedia would gain from letting them organise into an interest group and (attempt to) gain public validation with this. Daß   Wölf 21:38, 15 July 2017 (UTC)
* Strong Oppose per BMK. I'd also disagree with Jytdog's statement that declaring your paid status makes you a community member in good standing. Following the TOU does not necessarily mean that. It means that you are not excluded from using the website by the legal owner of the servers. Spamming is still against community policy even if the paid editor has declared their affiliation, and there are paid users who spam even when this is declared and think that somehow their following the terms of use makes this okay. I fear if this proposal was adapted it would further the misconception that paid editors who declare and create otherwise unacceptable articles should be allowed to do so (even though I know that was the intent of the proposal). TonyBallioni (talk) 21:43, 15 July 2017 (UTC)
* You are killing me and worse you are not responding to what I have actually written here. When I say "following PAID" - what that means (if you actually read PAID) is, that they don't edit directly, they don't hammer people at talk pages, etc. Paid editing is not banned (and is impossible to ban given how WP is structured); we need to take that seriously. We don't love paid editors, but you cannot say that they are not members of the community when they are following what PAID actually says. Please go slower in responding to this. Leaving the market as it is, means just more of the same. This is a strategy to influence the market and having something substantial like what is being proprosed will help better regulate paid editing internally and will give us something to point the public to. I arrived at this proposal after a lot of thought. Jytdog (talk) 22:08, 15 July 2017 (UTC)
* It references the COI guideline and NOTSPAM as well, but the core of it is the terms of use, which is what is normally meant when people say following PAID. I have read the page, and while your interpretation of it is the one that is most in line with our other community policies beyond TOU, PAID itself does not go into that much detail. I stand by my comments above: making it so that there is a semi-official grouping within Wikipedia lends legitimacy to the idea that paid editors complying with the terms of use allows them to violate other community policies on promotion. I am not actually anti-paid editor as a whole, there are some good ones (people who get grants to do this is just one example). The majority, however, are going to be spammers, and that is easier to deal with when there isn't an organized group sanctioning it. TonyBallioni (talk) 22:33, 15 July 2017 (UTC)
* I would say that people who get grants to edit Wikipedia might be a form of paid editing I could accept, if their grant is on the order of "to improve Wikipedia's coverage of X subject" and not in the form of "reverse the bias in Wikipedia regarding X subject", since people who edit with the intent of undoing a bias generally end up editing with the entirely opposite bias, instead of endeavoring to edit neutrally. We had the recent example of the teacher who assigned their students the task of showing how Trump's policies were going to damage the environment. I believe the teacher ended up being indef blocked after an extremely long community discussion that went across numerous venues. That wasn't a grant situation, but it could certainly be one, depending on who is giving out the grants and what their purpose is. Non-profits aren't required to be neutral, nor are academics, but we are -- and PR people are never neutral concerning the subjects they're paid to promote. I see no reason whatsoever to open our arms to them, welcome them to Wikipedia, and give them their own clubhouse. Beyond My Ken (talk) 23:20, 15 July 2017 (UTC)
* Leaning oppose but could be persuaded. Jytdog, I think I agree most with the opinion expressed by Daß Wölf here but leaning towards BMK. I have to ask, what do we hope to have happen if such a guild existed? How would it improve the current situation? I think the argument for self-regulation is not persuading me because the undeclared paid's already exist so far outside the bounds of what is considered acceptable (even legally per ToS and US commercial laws vis-a-vis FTC disclosures for advertising). ☆ Bri (talk) 02:49, 16 July 2017 (UTC)
A few comments based on what has been said above: As I mentioned elsewhere, I am not optimistic that there will be any self-policing of membership in a support group run by paid editors, so I personally don't see this as making much difference in helping identify paid editors who follow the rules versus those who don't (I know others do; let's agree to disagree). (Editors interested in sorting this out are welcome to help keep WikiProject Integrity/Editor Registry up to date.) In the collaborative spirit of a wiki, though, I think it is desirable for editors to support each other in following policies and guidelines, and I can't see any grounds to prevent non-banned editors from doing so. isaacl (talk) 03:44, 16 July 2017 (UTC)
* It's unclear to me that the signatories to the statement from the communications firms in question are truly interested in proceeding with forming a support group of sorts, given that they haven't in the past three years since the statement was released. But if they do proceed, I'd as soon it have some presence within Wikipedia to make it easier to monitor (and apply sanctions against, if necessary).
* Wikipedia editors and readers are sufficiently savvy to understand that the views given in any number of essays in Wikipedia space are not tacitly approved by the community. I trust they will understand this regarding any project pages used by a paid editor support group.
* Paid editors who wish to ignore Wikipedia policies and guidelines will do so anyway, no matter what pages exist in Wikipedia. A support group page or the absence of one won't influence them.
* It all comes down to what the community wants. If they don't want such a guild to exist, and an RfC shows that, then the guild will not exist. There doesn't have to be a specific policy giving the community the authority to stop it from forming or shut it down if it already has. We make policy, policy doesn't make us. Beyond My Ken (talk) 05:31, 16 July 2017 (UTC)
* Sure, any group can be prevented from forming on-wiki (can't stop a group from forming off-wiki, as I mentioned). As much as possible, though, I'd prefer to base opposition on general principles, rather than on personal preferences, or else every conversation will just be an "I like it" discussion. isaacl (talk) 13:15, 16 July 2017 (UTC)
* Oppose. I've been scanning over this discussion of dealing with paid editing for the past few days. This...is an interesting way to deal with it. Very interesting. A lateral way to deal with such situation. But no. The key priority is keeping transparency with paid editing, and enforcing transparency with paid editing. This path...seems lucrative, but any fear, uncertainty and doubt is very justifiable, if this system operated. That's not saying that I would not trust the editors, but we have seen that past (and current) works of black-hat editing have used very sophisticated means to hide their editing. This...is another thing to care about. And it could all go very wrong if it isn't cared for properly. I support 's idea on Wales' talk page. My name is not dave (talk/contribs) 12:57, 16 July 2017 (UTC)
* With apologies, nothing you wrote makes sense. This doesn't make anything less visible and there is no new "system". I don't know what you are reacting to, but it is not this proposal. Count Ibis's idea on Jimbo's talk page means committing fraud, as I wrote there, and neither the WMF nor the community will engage in illegal behavior. If you want to go commit crimes, that is your deal, of course. Jytdog (talk) 21:45, 16 July 2017 (UTC)
* I've put this on Template:Centralized discussion. . My name is not dave (talk/contribs) 13:10, 16 July 2017 (UTC)
* I oppose paid editors, period. Wikipedia should be neutral, and paid editors aren't . --NaBUru38 (talk) 15:11, 16 July 2017 (UTC)
* Jytdog, maybe you can give this one or a few more days. So far, I see unanimous/huge opposition toward the proposal. I'll let you decide when you can withdraw this proposal. Okay? --George Ho (talk) 21:30, 16 July 2017 (UTC); Never mind; after seeing a few "support" votes below, I'll give it some appropriate time. --George Ho (talk) 03:46, 17 July 2017 (UTC)
* The conversation at Jimbo's talk page is going quite differently, and likewise the one at WT:COI - both places where people have been considering and discussing these issues for a long time. This thread has a very weird jag of emotional, kneejerk reactions that I was somewhat worried about when I posted this. But it doesn't matter that people don't "like" paid editing or that they imagine that this would change in any way the underlying policy basis under which paid editing should happen. And almost no one who has opposed seems to be aware of the activities around the Statement on Wikipedia from participating communications firms that this would merely formalize. This isn't facebook and we don't decide things on "like"s or people shooting from the hip. Please don't close this prematurely. Jytdog (talk) 21:45, 16 July 2017 (UTC)
* It seems to me that we should oppose undisclosed paid editing with a vengeance. But paid editors who are conscientious about following WP:PAID can make useful contributions, albeit only on a short leash. We must never give the appearance of giving approval to spammers. But if some good-faith editors are willing to voluntarily, and perhaps unofficially, patrol for violations and give advice about best practices, that could be a good thing. Maybe we just don't need to put an official name on it. --Tryptofish (talk) 22:34, 16 July 2017 (UTC)
* Possible support While I oppose all paid editing, to the extent that I would long ago have actually proposed a ban if there were a feasible way to accomplish this, there is no fair method of detection--all that a ban would do is drive all paid editing underground. Given that it exists, we need to provide incentives for paid editors to declare themselves. This project could assist this, by providing clear standards to those in the trade in their own language, and enable us to keep a better watch on the declared paid editors to ensure that they were actually following the rules. It would assist the critical effort that ought to be made by the foundation to make it unambiguously clear by its own PR efforts that all advertisements of paid editors that do not specifically say they will guarantee the terms of use are opposed to our terms of use, and in many cases pure scams--and to clarify that there is a legitimate alternative. I'm aware that the declared paid editors have a commercial interest in discouraging the undeclared, but it coincides with our own priorities.
* But this has to be named and run like any other wikiproject, with open membership and general participation. No wikiproject is "official". I've joined a few wikiprojects whose work I do not necessarily approve of, to keep tabs on what they are doing; many others do likewise. DGG ( talk )
* Oppose. This would encourage EVEN MORE unconstructive paid editing. KMF (talk) 00:31, 17 July 2017 (UTC)
* Comment. The following is something I suggested years ago, so I offer it here again. I would like to see an organization that acts as a neutral go-between, so that Wikipedians can be paid for their work, but not directly by article subjects or their agents.Ideally, the Wikimedia Foundation would set up a team with an email address and website, or OTRS-type multiuser system, to which people wanting to pay for articles could apply, and to which all approved paid editors would have access. The Foundation's team would set the fees; choose the editors from a list of Wikipedians who sign up for the scheme (who must have a minimum number of years spent only as volunteers, and a minimum number of edits); pay those editors as independent contractors; and take a percentage of the fee for having organized the transaction. The Foundation's brief to the paid editors would be to write a neutral, policy-compliant article. The payers would have no say over which editor was given the job. Editors producing non-compliant articles would have their paid privileges removed. This system would remove or at least reduce the COI; would give people requesting articles somewhere to go; and would provide fees for editors who understand the policies and have the project's interests at heart. It would be win-win. The Foundation is unlikely to do this, but I wonder whether it could be persuaded to help set it up and maintain s close tie with it. and would be ideally placed to lead it. SarahSV (talk) 01:17, 17 July 2017 (UTC)
* This is something I definitely would not support, and I think is a direct contradiction to our basic principles. It essentially amounts to turning us officially into a partially paid encyclopedia. I consider it similar to book review journals which review some books for free, but will also renew anythign else if you pay for it--the most prominent example I know of this is now no longer accepted as a source for WP. It would give the WMF every incentive to maximize the proportion of paid articles, if they received part of the fee. Even volunteer editors often have a great attachment to the articles they work on, and OWNership is an ever-present if subliminal temptation--if the same people did it for money it would be much intensified. It would also put the WMF in the position of "approving" editors, which essentially means interfering with our content, and that would destroy the site entirely. Not only should the WMF not do it, but it should never let itself be connected to any entity doing it. It might even affect our safe-harbor status in terms of copyright and libel. There have been sometimes problems with organizations giving the foundation grants to support Editors in Residence, and Editor in Residence sometimes getting too much involved with articles closely connected with the organization that pays them, but these are at least supposed to be highly reputable non-profits. Having current legitimate paid editors organize it would be the worst way of all--they would essentially be establishing a monopoly. DGG ( talk ) 02:54, 17 July 2017 (UTC)
* Support per . I've worked pretty deeply on the problem for years, with hundreds of blocks at SPI, hundreds of AFDs and if I've learned anything, it is that it is impossible to prove paid editing most of the time, so managing the problem is better than trying to pretend we could really "outlaw" it. Better to have a system of self-policing with input from the entire community, to have self-declaring, some ethical standards, and then perhaps they would be helpful in getting rid of the bad players, because they have a stake in keeping in the community's good graces as well. It would be the lesser of two evils, which is still the better choice. Dennis Brown - 2¢ 02:26, 17 July 2017 (UTC)
* Support. Paid editing is here to stay, so it's overall beneficial for Wikipedia to turn some of these edits to be useful. Paid editors who want their work to survive would benefit from this project, while those who refuse to abide by Wikipedia policies will continue to ignore this project. f e minist 16:48, 17 July 2017 (UTC)
* Comment I'd like to push back agains the idea that it is better to have this out in the open with an endorsed organization rather than shunned and underground simply because we aren't able to stop it that has brought up. I disagree completely. As it stands, we are actually pretty good about picking out the clear spam and getting rid of it through one of the deletion processes. People hide the fact of their employment status and then when it is put up for deletion and they gang up, it is very easy to spot and we deal with it quite well when the editors are undeclared. We can't prove the paid editing, but we can get rid of the non-notable spam articles.Working with new pages, I've been on the end of several declared paid editing AfDs where the declared paid status of the editor is used as a way to lend legitimacy to the article outside of policy concerns about notability and promotionalism. The editor is free to game the process circulating press release stories and sometimes canvassing sympathetic !votes to the process. This is without a guild of paid editors, but based solely on the idea that compliance with the TOU is enough if someone is paid. A guild would make this mentality worse and I think would be a step towards the effective end of AfD as a useful process for dealing with articles created by paid accounts on the merits. I respect the work of quite a lot and know that they have put a lot of thought into the process, but this is not a kneejerk reaction: before articles get to COIN, they pass through NPP. I really believe this would make the already tough task of dealing with paid editors who will pester you about why their non-notable article should be kept even worse and make our task there much more difficult. As I mentioned above, I am not against all paid editing, but I don't see how this would do anything other than make Wikipedia's processes easier to game. TonyBallioni (talk) 17:03, 17 July 2017 (UTC)
* User:TonyBallioni - Thanks for your kind words. The goal here is to promote best practices for paid editors - disclosing and proposing, and not being a jerk and being pushy. There are paid editors who behave this way, and one of the key goals of having a WikiProject of paid editors would be to promote and propagate these best practices. Besides the goal of having something to point the public to (so they have somewhere to go, to choose a "white hat" editor instead of a "black hat"), there benefits internal to WP. Like that propagation of best best practices. Another thing I would want to do is have a page within the project where all articles where paid editors are working, are listed. Another benefit would be, that the kind of pushy paid editors you raise, could go there and ask for advice, and the more experienced ones would tell them that they are barking up the wrong tree. This would all happen out in the open, and self-interest among white hats would drive propagation of best practices. This would be so valuable. Jytdog (talk) 17:17, 17 July 2017 (UTC)
* I certainly get the concept in theory. I just don't think it will work in implementation. The paid editor has both ethical and practical obligations to their client: ethical in that they're being paid to promote the clients interests on Wikipedia, so the client should always come first, practical in that they are getting paid for a task and even if you come up with some sort of code of professional standards that includes things such as being paid per hour and not based on articles being kept, it is still going to be bad for business to have articles deleted. Both of these motivations are very compelling motivators to find ways to game the system with the TOU. The really good PR people will find ways to game the system whether they are "white hat" or "black hat", and as DGG has pointed out in the past, in exceptionally rare circumstances they actually help us by producing a good and neutral article about a notable client. My fear is that this will help mediocre and bad PR professionals game Wikipedia more easily. TonyBallioni (talk) 17:42, 17 July 2017 (UTC)
* Virtually all editors at Wikipedia have no idea how flooded we are with paid accounts. A few years ago, I estimated it was many thousands of accounts, many per person. Again, I worked here as admin on this problem at SPI and elsewhere. Paid editors games the system in part because it is easier to avoid the rules than follow them here. And there are so few admin compared to paid editors, it is laughable to think we can keep up. Putting some sunshine on paid editing, setting standards, allow them to use one account instead of having to sock (our TOU is problematic as well, but that is another story), and generally allowing them to do so in the open under the same rules that everyone follows, meaning the ones that edit ethically and follow WP:RS, WP:V and WP:N are more likely to be successful here and with their clients. The ones that don't won't be. It reminds me of the illegal nature of cannabis in the US. Everyone practically laughs about it, enforcement can't keep up, the real damage is less than the damage of over-policing it. Paid editing is a problem, but I would rather manage it than be foolish enough to think that we can "stop" it. We can't. I tried, really hard, I failed, it can't be stopped. It can be managed better. Not all paid editors are evil, but we need a system to manage and allow them to self-manage and point out the problem editors, as they will want to protect their own self interest by doing it right. Or we can continue the way we are, and for every sock we block, two more pop up. Dennis Brown - 2¢ 19:15, 17 July 2017 (UTC)
* Strong oppose (ec) Tomy Ballioni above raises excellent points. Paid editing is a problem that consumes vast amounts of volunteer time and resources, taking away from more worthwhile pursuits. Why? Because there is demand from people and companies for articles that they can utilize in their marketing. The fact that it "is going to happen anyway" is no reason to create a Wikiproject about it, co-equal with Wikiproject Biographies and dozens of other legitimate subjects, giving it an implicit blessing by the project. And no, the fact that there are "white hat" paid editors is no reason to uncork the champagne. There are advantages of abiding by the rules (Tony Ballioni raised a couple above that I hadn't thought of), and one can accomplish most paid editing objectives by doing so. There is no reason to feel such gratitude for compliant paid editors, whose activities require constant policing by other editors,, to give them their own project as a kind of reward and acknowledgement of their service to the project. Lastly, a Wikiproject Paid Editors would be a significant public relations gaffe, albeit one that doesn't dismay me as the WMF deserves a p.r. thrashing for its ambivalent attitude toward this problem. Coretheapple (talk) 17:08, 17 July 2017 (UTC)
* the purpose of the project ought to be to keep watch over it. It would be a good place to monitor if they kept their promises, or were just making pious gestures of good will. Companies put considerable effort into accurate disclosure forms. Unlike the government, we cannot penalize them civillly or criminally if they aren't correct, but we can certainly expose them to public embarrassment. DGG ( talk ) 20:06, 17 July 2017 (UTC)
* Then perhaps there should be a paid editors registry, so organized and named that it would provide no marketing advantage to paid editors. "Guild" or "Project" implies Wikipedia approval, and gives paid editors something real nice to put in their advertising. Wikipedia should not be helping paid editors, even so called "white hat" ones, get business. Coretheapple (talk) 21:02, 17 July 2017 (UTC)
* I think that registry is one of the purposes of the proposal. I do not particularly want to help whiteh at paid editors, but if the only way we can get rid of the black hats is to extend some coperation to them under our own terms, it's a good bargain. I would even say a necessary bargain. DGG ( talk ) 05:37, 18 July 2017 (UTC)`
* I'd suggest there's an underlying fallacy, which is that we can get rid of, or substantially reduce, the so-called "black hats" without taking a variety of steps not acceptable to WMF or the community. However, I think that they can be discouraged - while still retaining Wikipedia's integrity and brand identity - by creating a "consumers guide" for subjects of articles, a variation on ideas that TParis and Smallbones have made. Essentially, potential subjects of articles should get a scary portrait of what happens and how it can and often is a net negative to hire someone to put an article on Wikipedia. If they do so, they should look for various stringent and rarely-met characteristics. Or perhaps better use can be made of article requests. There are a whole bunch of things like that that can be done to attack the problem from the consumer end. For instance, WMF, instead of just responding to requests for comment from journalists, can be more proactive in waging p.r. wars against paid editing. Creating a "white hat project" undermines the rationale behind such an effort, which is that Wikipedia is a volunteer project and that commercial exploitation is contrary to that and undermines public trust in the project. Coretheapple (talk) 13:20, 18 July 2017 (UTC)
* Conflict of interest is everywhere in the world. What undermines public trust is unmanaged conflict of interest. This is a tool to help better manage the specific form of COI that is paid editing. Jytdog (talk) 15:05, 18 July 2017 (UTC)
* No, what undermines public trust is conflict of interest. Period. What undermines puiblic trust even more is condoned COI. Coretheapple (talk) 17:10, 18 July 2017 (UTC)
* Coretheapple, potential COI is everywhere, and every responsible organization has ways to manage it. Pretending it can be eliminated (especially here) is not the real world. You are invalidating your stance here by writing this kind of nonsense, and I will not be responding to you further. Jytdog (talk) 17:23, 18 July 2017 (UTC)
* Good. You haven't or won't grasp my point, your WP:BLUDGEONing of the discussion is getting tiresome, and your inflammatory edit summaries gild the lily. Coretheapple (talk) 17:44, 18 July 2017 (UTC)
* There is a paid editor registry: WikiProject Integrity/Editor Registry. It can use updating; everyone is welcome to pitch in! isaacl (talk) 00:51, 19 July 2017 (UTC)
* Strong oppose-All paid editing is, by its very nature, biased. And, as Coretheapple said, this would also put Wikipedia in the position of being seen (rightly or wrongly) as supporting those companies that pay these editors. --Khajidha (talk) 12:38, 18 July 2017 (UTC)
* Comment I want to make a note here that even if everyone opposed the idea, someone could start the project, which could only be removed for cause, not just because we don't like it. As far as I know, Projects are not vetted beyond having a scope that is within the limits of the greater project, and this clearly is. When it gets started (and it could be a month, a year, a decade, but not "if"), it would best be started by someone that isn't a paid editor but is willing to provide some guidance and written material to keep paid editors out of trouble. In the end, that should be our goal: help any editor follow policy, generate worthwhile content, and avoid sanctions. That which isn't worthwhile, we have AFD for, no different than today. Dennis Brown - 2¢ 13:27, 18 July 2017 (UTC)
* Dennis, thanks for your note. My goal in posting here was to make sure that the community was aware of this from the beginning. I am aware that people have strong feelings about paid editing so wanted to communicate clearly and broadly, at an early stage, and get useful feedback so that as this move forward (if it does...) that could be built in. My plan has been to do further planning and then present again, with detail, before launching it. Jytdog (talk) 15:02, 18 July 2017 (UTC)
* Comment We already have WikiProject Cooperation. How is this proposal different? Doc James (talk · contribs · email) 13:54, 18 July 2017 (UTC)
* That WikiProject is not really driven by paid editors. With the lack of that sense of "ownership" in the positive sense, comes neglect. Part of the design of this WikiProject is that paid editors will "invest" in its authentic success in the community - that it would propagate best practices and help us identify paid editors who aren't following PAID much less best practices. Jytdog (talk) 15:02, 18 July 2017 (UTC)
* I saw that yesterday and just didn't say anything yet. That WikiProject isn't driven by anything, it is basically a ghost town. Re-purposing defunct projects is allowed. Dennis Brown - 2¢ 15:12, 18 July 2017 (UTC)
* i allso wanted to say that this would be "organic" - the next step in the evolution of rhe Statement. Jytdog (talk) 15:16, 18 July 2017 (UTC)
* IMO before we will get those involved with paid editing interested in doing it above board, we need to be much more vigorous in policing those involved with undisclosed paid editing. As lots of the articles made by throw away socks of undisclosed paid editors are kept they have no incentive to change. Doc James (talk · contribs · email) 15:21, 18 July 2017 (UTC)
* User:Doc James, of course we need to keep working on that. But part of the design of this is to dry up the market for unpaid editing by making a place for "white hat" paid editors to be, and communicating to the public that there is a difference. A big goal here is to influence the marketplace and drive business away from the socking, undisclosed paid editors. If this works (and I don't know that it will) there would be fewer people choosing to buy paid editing services on the black market. But right now the marketplace is undifferentiated and that is really our fault, as we have done nothing to define it for people. Nobody else is going to do that, right? We need to do it. And to do that, we need something that defines the legit (as far as we know) service providers. We don't need to endorse or recommend them (indeed we shouldn't) but we need to have a place to point people to. You can think of this like needle-exchange services in Vancouver or the like, and all the issues around that. Jytdog (talk) 15:37, 18 July 2017 (UTC)
* I have seen a handful of disclosed paid editors who consistently use the AfC process. There is nothing stopping us form listing them in a central location right now. Doc James (talk · contribs · email) 16:02, 18 July 2017 (UTC)
* In a way, a project would have us picking the winners and losers. Paid editors that followed the rules wouldn't have any problems, so they would be more efficient (from their perspective). Paid editors that didn't, who still socked, who lied about their status, would be subject to having all their work deleted, wasting their time. This creates a financial incentive to play by the rules, and rewards those that do by letting them spend more time writing passable articles and getting new clients, and less time dodging AFD and Checkusers. This may sound simplistic, but people always act in their own self-interest. We just need to provide a better alternative to socking, one where we can easily monitor everything. Dennis Brown - 2¢ 16:41, 18 July 2017 (UTC)
* A "project" or a "guild" won't do anything to deal with the cause of so-called black-hat paid editing, which is the demand for articles about non-notable subjects. They'll continue to take money from people who want articles written about them, they'll create their throwaway socks for that purpose. If they don't slip by under the radar they will be blocked. So what? They don't care. They'll create other socks, using VPNs etc. Coretheapple (talk) 17:08, 18 July 2017 (UTC)
* I have over 1500 SPI blocks, including a record setting 300 in a single paid editing case. VPNs aren't that hard to catch and rangeblock, and pushing as many as you can into the "good" side means fewer to deal with at SPI. Its a bit more complicated than you are making it out to be. I've had more than a few extended conversations with paid editors offwiki, I know the system quite well. Many would rather do so in a legit fashion but the current rules make it hard. Dennis Brown - 2¢ 01:27, 19 July 2017 (UTC)
* This would be a lot more organic if it had happened three years ago, and if there were more involvement from any of the signatories. Right now there are just a couple of statements on the statement's talk page, with only vague details on what kind of work and outreach the parties in question would do. Absent their participation in these discussions, it's hard to tell if they're interested in this initiative or in engaging the non-paid editor community in general. isaacl (talk) 05:55, 19 July 2017 (UTC)
* That's true. There is not a single paid editor involved in this discussion one way or the other. They can come here and argue how such a project or guild would benefit them, and complain directly about how supposedly difficult it is to comply with the very few rules regulating paid editing (per Dennis's comment above). I've never heard such complaints, and I've never seen them in public, probably because they would be greeted with ridicule. Coretheapple (talk) 12:59, 19 July 2017 (UTC)
* I see WikiProject Cooperation and in particular WikiProject Cooperation/Paid editor help (the paid editor noticeboard) as a way for the non-paid editor community to provide support to paid editors. For any paid editor support group to be successful, I feel the community needs to reinvigorate a group of non-paid editors to provide assistance, whether it is at the current paid editor noticeboard or somewhere else. isaacl (talk) 00:59, 19 July 2017 (UTC)
* Oppose: We don't want all paid editors to create an project, otherwise it can cause problems. KGirlTrucker81 huh? what I've been doing 19:17, 18 July 2017 (UTC)
* Oppose As stated above, allowing for the formation of a WikiProject/Guild/What have you essentially grants tacit approval. We should be here for the benefit of the project, and not to try to turn a buck or push an agenda. caknuck ° needs to be running more often 20:44, 18 July 2017 (UTC)
* Oppose this would further legitimise some paid editing, the more we de-legitimise it the more the paid editors have to hide by writing neutrally and including neutral sources. I doubt we can get to the stage where paid editors are telling their clients that they had to mention the scandal but they did keep it out of the lede, but that is the direction I'd prefer us to aim for. Ϣere Spiel Chequers 14:17, 19 July 2017 (UTC)
* User:WereSpielChequers the notion of "deligitimizing" is what we have always done, and there is no evidence that the problem of undisclosed paid editing is going away or that the public even understands what that means. The goal here again is to a) influence the market for it (which has grown up despite the message that "paid editing is bad"), which we have never tried to do before, and b) be provide a more well-defined space where paid editors can learn best practices (the real ones, not the worst ones). Jytdog (talk) 00:15, 20 July 2017 (UTC)
* That the problem is pretty bad right now doesn't mean it won't get far worse if we stop managing it. I've seen a few nice people who backed out quietly when I pointed out that what they were doing was in conflict with our goals, but the egregious examples of gaming the system and trying to covertly promote their stuff more than make up for that, and if we give the latter a soapbox to stand on, we'll have an even harder time ridding the project of spam. Daß   Wölf 00:38, 20 July 2017 (UTC)
* Well said Wolf. I'd add that we don't want paid editors learning from each other, we want paid editors learning from editors who write neutrally, use reliable sources and who avoid areas where they have a conflict of interest. Ϣere Spiel Chequers 07:07, 20 July 2017 (UTC)
* Just fyi, have been thinking about this further, and it might make sense to move that activities around the "Statement" that are already happening, to the WP:WikiProject Cooperation. Might be an easier way to go to accomplish the same thing. Jytdog (talk) 00:00, 20 July 2017 (UTC)
* Support - A step in the right direction. There is a difference between white hat and black hat paid editors. Sorting the sheep from the goats is what it's all about... Carrite (talk) 04:29, 20 July 2017 (UTC)
* Support, after thinking about it for a while. We're never going to stop paid editing altogether, so having some paid editors who are members of the community in good standing is an absolutely solid idea. Enterprisey (talk!) 06:43, 20 July 2017 (UTC)
* Oppose - these guilds generally refer to self-regulatory bodies for desired groups; paid editors are, by our standard, an undesired group. עוד מישהו Od Mishehu 07:58, 20 July 2017 (UTC)
* Support I'm opposed to paid editing, but I don't see the harm. Perhaps it's a dog whistle I'm not hearing. As pointed out above, anyone can create a Wikiproject. So what are we arguing about? Whatever happens here it will be done, or not, depending upon whatever the whims of individual Wikipedians. Figureofnine (talk • contribs) 00:15, 21 July 2017 (UTC)
* Oppose, mostly per Coretheapple. Double sharp (talk) 08:40, 21 July 2017 (UTC)
* Suggestion. Is there milage in encouraging corporate user pages? Let us say that Bodgeit & Scarper want to inform the world that they are "the largest (2017 sales: 35 million) and best manufacturers of spring loaded rodent elimination devices". They, or their agent, can put this on a user:Bodgeit_&_Scarper. An editor can then edit mouse trap to add the information that "In 2017 Bodgeit & Scarper claimed to be the largest manufacturer with 35 million sold. ". Paid editing of the main encyclopedia can then be banned but "white hats" are able to input traceable information whilst eliminating POV. Just a half-formed thought! Martin of Sheffield (talk) 09:56, 21 July 2017 (UTC)
* Oppose I appreciate Jytdog and others here commenting to advance the conversation. If Wikipedia were to develop infrastructure for supporting paid editors, then I think the start should be for paid editors who are not editing Wikipedia articles on people or organizations. Right now "paid editing" is almost synonymous with "editing for a brand or promotion". Because of that heated discussion, we do not create pathways for benevolent paid editing about general reference topics which do not benefit promotional interests. We have a highly committed model for expert paid editing in Wikipedians in Residence. We do not have a light payment model, like for example, an organization which wants to be less committed in funding a scholar to edit Wikipedia articles in a general field like "sanitation" or "public parks" without promoting a brand. For political debates there are some organizations which would fund neutral discourse and presenting all sides of issues, like for example, listing all major points of view in a discussion on any major policy issue. There are lots of organizations which invest large sums of money in sharing ideas in Facebook and Twitter, when actually, what they would really like is to have neutral information in Wikipedia. If there were a club for "no branding, no promotion paid editors" then I think that could be a workable, positive space for some editors. Once we established a clear path for paid editors who have nothing to do with branding, then perhaps we could address the more controversial talk about branding. So far as I know, 100% of paid editors doing editing for brands have caused problems and made volunteers upset. I see no reason to chase a path with a 15 year, 750,000+ attempt, 100% failure rate. Blue Rasberry (talk) 16:35, 21 July 2017 (UTC)
* Limited support Some editors perform absolutely herculean tasks on WP, and it is a travesty that none of them should ever receive any recognition for their labors and the selfless giving of their time and expertise beyond just a few barnstars. This should certainly change, even if it is only a small stipend as a token of appreciation for their prolific efforts. Whether it be done through crowdfunding or some Wiki endowment, I do not know. And no doubt not all editors would even wish to be paid for their work, but those who do should have a means of submitting their editing history for review. A committee of admins could then analyze the value of their contribs and decide what, if any, compensation would be appropriate. Another option might be a PayPal link placed on certain user pages to recognize some of the top contributors, allowing others who wish to subsidize and encourage their efforts to do so. Incentivization of excellent work is certainly in the interest of this site. - JGabbard (talk) 17:37, 21 July 2017 (UTC)
* Support with Guild member fees in Bronze, Silver and Gold accounts. Membership cards include exclusive benefits, such as immunity from 3RR and get out of AfD for free (see fine print for disclaimers and limitations). Members earn double and triple points for gratis edits made in a non-paid capacity. Other benefits include free Wikimania scholarships, the private email address of the WMF president and a Wikipedia tote. -- Green C 18:52, 21 July 2017 (UTC)
* Very strong Oppose. Every single paid edit whether it is written neutrally or not, is an attempt to promote a company, a product, a person, or a non-profit. That is not what Wikipedia is for, and it's not what thousands of maintenance workers and bona fide content creators offer their unpaid free time for. The slightest relaxation in our view on paid editing, especially the creation of help/support areas for paid editors will be taken by them as a legitimisation of their activity. We already have plenty who think that by putting a paid editing declaration on their user page means we condone paid editing and give them carte blanche to go ahead and write what is basically blatant spam.
* Give these spammers the slightest crack in the plaster and they will soon be chipping away at our rules and guidelines until they've knocked the whole wall down. In collaboration of the community and the WMF a short trial of some new measures is soon going to take place and its analysis will show what kind of effect, if any, it has had on spam (as well as other unwanted content). That, together with the non-indexing of new articles, should go a long way towards negating the SEO advantages for the 'Get me a page on Wikipedia' customers, and reduce the incentive for the 'We'll get you a page on Wikipedia' merchants.
* Paid editing is not particularly difficult to detect by experienced New Page Reviewers, and spam links slipped into articles should be recognised by recent changes patrollers and Pending Changes Reviewers, and a few software enhancement we are asking for (eg. ORES, and better automatic duplication detection) should do the rest. What is increasing now however, is the number of direct offers of money for work being sent by email to admins from professional rings of socks (so it's already going partly underground). We can only rely on the sysops' integrity to refuse. I understand that measures to combat paid editing will drive it underground, but I think we need to stick to our principles and if we don't yet have such strong principles, it's time we did. Kudpung กุดผึ้ง (talk) 21:42, 21 July 2017 (UTC)
* Very strong Oppose. Kudpung has said it all above and I concur.Charles (talk) 21:53, 21 July 2017 (UTC)
NFCC #8 and Discographies
Hello, I apologize if this is the incorrect place, or if this has already been discussed ad nauseum. It appears it has been discussed before, but not at the village pump, and afaik, not recently.
But: I recently added album covers to the Bob Dylan discography, and these additions were reverted. [note: at the time I wasn't aware of the policy, btw] This appears to be the general practice on WP, and I certainly don't blame anyone for following general practice. BUT if you look closer at the reasoning behind it, it doesn't make much sense to me.
NFCC #8: ''Contextual significance. Non-free content is used only if its presence would significantly increase readers' understanding of the article topic, and its omission would be detrimental to that understanding.''
The reason I added the pictures is not because I love Bob Dylan and want his cover art everywhere (though that's not totally untrue). It's because I was on the discography page and it really did not help me. It's a bunch of names, a bunch of numbers. Without pictures, Dylan's 38 albums all run together. It's just a wall of text, separate by a table, but still not helpful. The cover art provides context, it DOES significantly aid in understanding of the article. Maybe it doesn't assist when an artist has 4 albums. But for artists like Dylan, or say Paul Simon (he came to mind), or anyone with a large amount of work, I think having pictures DOES help. The pictures help to identify the content. Without it, Blood and the Tracks and Street-Legal might as well be the same album.
I would further like to point out the wording of the WP policy: The use of non-free media (whether images, audio or video clips) in galleries, discographies, and navigational and user-interface elements generally fails the test for significance (criterion #8).
There it is, GENERALLY FAILS. That is to say, there ARE exceptions.
So again, I bring it to you - should there be leniency on no album art in discographies where the artist has over a certain number of albums? I certainly think it makes sense, and personally it WOULD significantly increase my understanding of discographies. It appears to fall within fair use - and the image size used could be even smaller than the 300px used on the album pages. I don't see how this would go awry with fair use any more than using it in the album page. ‡ Єl Cid, Єl Caɱ̩peador ᐐT₳LKᐬ 13:30, 31 July 2017 (UTC)
* What significance is putting album covers in a list helping? I know that for music fans it will rapidly help them find an album (they're likely to remember imagery over names), but we're writing for the general reader that may never have seen these. And just adding the image to the list just to help break up the space visually is absolultely not acceptable. You can use free imagery of Dylan in concert or other aspects to help visually assist the list, for example, but there's no logic to considering an NFCC exception for long discographies. --M ASEM (t) 13:34, 31 July 2017 (UTC)
* What do you mean? Fair use is not connected to whether the user is a music fan or not. I didn't say the purpose was the break up space - all I meant was that having pictures to go with the extensive text would HELP the understanding. Seeing the name of an album vs seeing the name and a picture of the album would certainly appear to provide more context and help in the understanding. And by your logic, what help is there in having the album art on the album's article? The same argument applies in both places. ‡ Єl Cid, Єl Caɱ̩peador ᐐT₳LKᐬ 13:38, 31 July 2017 (UTC)
* Except on a discography, you are not going into any details of the album, just basic facts. Note that we generally do allow cover art on standalone articles about published works even if the cover art is not discussed because we recognize that there is implicit marketing and promotion that comes from the selection of art, but this atop a lot of coverage of the work itself, so it clearly is a reasonable allowance. You don't have the same in the table of albums, and as we are trying to minimize the amount of non-free images used and how many times they are used, we do not allow those in discography tables because these do not go into any significant details about the works. --M ASEM (t) 13:43, 31 July 2017 (UTC)
* I think the discussions listed in WP:NFC are relevant here. I agree with Masem in that such usage just to break up lines of text tends to be decorative and should not be allowed per WP:NFLISTS and WP:NFTABLES; moreover, if the albums are Wikipedia notable in their own right, there is likely to be a link to a stand-alone article where the cover art is being used as the primary means of identification and can be seen per item 6 of WP:NFC. A single mention by name in a list of albums does not (in my opinion) provide the context required by WP:NFCC. As for being fair use, I think you should take a look at WP:ITSFAIRUSE. There are lots of fair use images which could be used on Wikipedia in a variety of ways, but "Wikipedia fair use" and "US copyright law fair use" mean slightly different things. Wikipedia's non-free content use policy is puposely more restrcitive than fair use and asks us to try an minimize our use of non-free content as much as possible. This does not mean that a non-free file can only be used once, but it does mean that we should try and use alternatives to non-free content whenever possible. -- Marchjuly (talk) 13:55, 31 July 2017 (UTC)
* Masem, why do we include photos of people in Featured Lists such as List of Nobel laureates affiliated with the University of Pennsylvania? Surely it's not because we think that our readers are fans of them, or will have any idea what most of them look like. But we still think that including those images is useful and appropriate. I believe that readers learn something from photos – perhaps not much from a whatever photos of mostly old white men we could find, at least from seeing how a musical group's album artwork has changed (or not) over time. For some (perhaps a minority of) discographies, I think it would be perfectly reasonable to show most or all of the artwork along with a written, sourced analysis of the artwork.
* I think it is very plausible to claim that someone who is not a fan might scroll through The Beatles discography in search of "The White Album" (a navigational use), and be discouraged to discover that you can't just look for white-colored album art. The educated fan already knows that "The White Album" has a different name. The general reader doesn't. WhatamIdoing (talk) 22:13, 2 August 2017 (UTC)
* Wikipedia's non-free content use policy does not allow non-free images to be used in articles such as List of Nobel laureates affiliated with the University of Pennsylvania per WP:NFLISTS. All of the files being used in that article are freely licensed or in the public domain, so this is why comparisons of this kind are not often very helpful per WP:OTHERIMAGE. The same goes for File:TheBeatles68LP.jpg; it is not licensed as non-free content which means its use is not subject to Wikipedia's non-free content use policy. If the cover art for The Beatles (album) is not being used in The Beatles discography, then it was probably done for editorial reasons and not non-free content reasons. -- Marchjuly (talk) 22:24, 2 August 2017 (UTC)
* If the person does not known the album but by name and is scanning a discography list here, the album art won't help them. An avid fan might be aided by the art, but is also going to know the name. We consider in-table album art on discographies to be pretty much decorative - it would be nice to have but it is far from essential, and thus fails NFCC#8 and thus why it fails NFLISTS. If the art can be free, then great, we can include it if desired, but it is still serving the same purpose, being decorative. --M ASEM (t) 22:45, 2 August 2017 (UTC)
* I think you're assuming that the reader has started at Wikipedia, and not started at a web search engine, which will have displayed some images. I believe that recent research shows that assumption would be wrong about 90% of the time. WhatamIdoing (talk) 02:16, 3 August 2017 (UTC)
* You're describing a situation regarding ease of navigability for readers already familiar with the album art in question, whereas the policy is concerned with readers' understanding of the topic as written. In your specific example (Bob Dylan discography, I take it), I don't see any text in the article whose conveyed meaning would be facilitated by accompanying copyrighted album art, nor is any of the text's meaning currently lost on me due to lacking the album art. Readers who are already familiar with the broad strokes of Mr. Dylan's album art might find the information for which they're looking faster than by reading the table of contents, yes. However, consensus says that's not a significant enough reason to use copyrighted material in contravention of WP:5P3. — fourthords | =Λ= | 15:51, 31 July 2017 (UTC)
* But such text could be added (and sourced). The idea that Bob Dylan's album art reveals something about the music is not original to Wikipeida. Does your objection end if analysis of the artwork is added to that page? WhatamIdoing (talk) 22:13, 2 August 2017 (UTC)
* Discussing the album art on the page about the album makes sense and in fact should be included to strengthen the reason to show the cover art, but it doesn't make sense to cover it on the discography page at all, since there's nothing that connects the art to the overall discographies. --M ASEM (t) 22:45, 2 August 2017 (UTC)
* I've seen sources that connect the art to the overall discography. "See how all of the albums by Favorite Band have a similar ____ in the artwork" is not an unusual subject for a magazine article (e.g., or ). When the source is talking about all of the albums, and comparing and contrasting the artwork on album #1 with album #2, it doesn't make sense to discuss the analysis in an article that's just about a single album. WhatamIdoing (talk) 02:16, 3 August 2017 (UTC)
* Then perhaps an article discussing the artwork of a set of albums might be appropriate if sufficient reliable sources can be found to support it. That wouldn't validate inclusion in a discography. --Hammersoft (talk) 13:39, 3 August 2017 (UTC)
* Or here's where an imageframe or a small montage image in the lede or outside the tables would be appropriate to discuss the album art sequence. But it would not be required to show every cover, just a few examples to demonstrate the perceived connectivity of the album coverage; since our goal is to summarize and not be exhaustive, we can use the references provided to give the reader a site to learn more from. But that type of source would not be allowed to justify the inclusion of all album covered in the discography table itself. --M ASEM (t) 14:17, 3 August 2017 (UTC)
* IFF it's not a user generated montage, and IFF the specific album covers are discussed in the context of reliable source citations. --Hammersoft (talk) 15:37, 3 August 2017 (UTC)
* Yes, actually - strike the montage. If we assume we have the individual album art available, then its better to reuse these images (with additional rationales) stuffed into an imageframe than make a new non-free montage of the two images. The former is minimizing non-free use. --M ASEM (t) 15:43, 3 August 2017 (UTC)
ANI reform RfC
Hello. You are invited to comment on this ANI reform RfC. Please do not comment in this thread; post all comments on the RfC pages. Thanks, Biblio (talk) 19:29, 5 August 2017 (UTC)
WikiProject Hasbro
I think there should be a WikiProject that oversees the Wikipedia articles about Hasbro's toy, games and multimedia businesses, named WikiProject Hasbro (just like WikiProject Lego). A child project of WikiProject Toys, it would have two WikiProjects - Transformers and G. I. Joe (the latter is believed to be semi-active) - as child projects, and absorb Wikiproject My Little Pony (which is believed to be inactive). It should also oversee other subjects (like Mr. Potato Head, Nerf, Jem, Moon Dreamers, Glo Friends, Hanazuki, FurReal Friends, etc.) previously not overseen by the three individual projects. I'm not sure if I could intensively participate in that project for the long time, but I feel there's a need. JSH-alive/talk/cont/mail 15:31, 6 August 2017 (UTC)
* You can read WP:PRJCRE and then start it yourself. Ruslik_ Zero 20:16, 6 August 2017 (UTC)
* JSH-alive, a WP:WikiProject is a group of people. If you don't have a group of people that want to work together, then there is no point in creating yet another set of inactive pages for a WikiProject that doesn't really exist. In general, niche areas without a serious (think "Star Wars"-level) fan base are doomed to failure. People who are interested in Hasbro toys should start off by trying to WP:REVIVE WikiProject Toys, and only split into a narrower group if it gets too busy (which, in my not-inconsiderable experience, requires more than one hundred participants). WhatamIdoing (talk) 17:59, 7 August 2017 (UTC)
Television channels
I thought there should be new rules regarding articles about television (and, to some extent, radio) channels. JSH-alive/talk/cont/mail 15:29, 6 August 2017 (UTC)
* 1) If a regional version of a multinational TV channel business has a fully independent schedule, an article about that particular version can be created, regardless of where the channel is actually transmitted from. (Thus, for example, the articles like Cartoon Network (Brazil) and Discovery Kids (Brazil) can be created apart from Cartoon Network (Latin America) and Discovery Kids (Latin America), respectively.)
* 2) * Of course, channels with simple regional advertisement opt-out or minor variation(s) in schedule (like UK's Sky Sports channels in the Republic of Ireland) should not be counted as such.
* If, for example, 'Channel H' is simply a rebrand of 'Channel Q', and thus making the former a continuation of the latter, the two should be regarded as a same channel, even if the channel was also reformatted in the process (for example, a documentary channel turned into a sports channel).
* 1) * In that sense, Discovery Kids USA-The Hub-Hub Network-Discovery Family should be treated as same channel rebranded over the years, and so does Locomotion (TV channel)-Animax (Latin America)-Sony Spin-Lifetime (Latin American TV channel).
* 2) * (Edited. JSH-alive/talk/cont/mail 15:35, 7 August 2017 (UTC)) Some exception(s) can be made if the two channels should be considered as different channels for legal or technical reason: for example, Discovery Kids (Canada) was replaced on most Canadian TV providers by Nickelodeon (Canada) with a separate CRTC licence. Thus, DK Canada and Nick Canada can be regarded as two separate channels.
* 3) And finally, article's title (with parenthesis) for disambiguation...
* 4) * If a channel's name has any word that indicates a broadcast channel (like 'channel', 'television', 'TV', 'network', etc.), a word that strongly implies a media brand, or a name of broadcaster, article's title can simply have a name of country or region in parenthesis.
* 5) ** Cartoon Network (Latin America), TVN (South Korea), Disney Channel (Southeast Asia), Channel 5 (United Kingdom), etc.
* 6) ** Discovery Turbo (UK & Ireland), Cartoonito (Italy), Disney XD (Netherlands), etc.
* 7) ** BBC Entertainment (Southeast Asia), CBS Reality (UK & Ireland), CBC TV (Barbados), etc.
* 8) * If a channel's name consists of normal word(s), there should be 'TV channel' in parenthesis as well.
* 9) ** Fox (Finnish TV channel), Boing (Spanish TV channel), Pop (Italian TV channel), Boomerang (Latin American TV channel), etc.
* This sounds like something to discuss at WikiProject Television. Praemonitus (talk) 19:47, 9 August 2017 (UTC)
Request for Importers access
Hello all, I have created a discussion to request importer access. Your input at Wikipedia talk:Requests for page importation is welcome. Thank you for your consideration, — xaosflux Talk 14:42, 11 August 2017 (UTC)
CWW - What's the point?
I intended to clean up an article marked {Copypaste} from 2016. It was fresh in Oct 2016, a complete article, but with tags that indicated they had been retrieved several years before. It was a mashup of other articles from WP or mirrors.
WP:CWW says a new article like this one needs to have attribution unless WP:NOATT applies or WP:PATT is satisfied. I got into a discussion with another editor who deleted a speedy-delete tag and said the process was fine.
The logical result, over time, is that we end up with a multiplicity of articles describing the same content in different mixtures. There is no harm in that, but if an error is injected into one copy, it can be copied from parent to child indefinitely. Because these pages all come with references, they look legit. Only a review of every line and reference would fix each one. Fixing one leaves the others broken.
WP editors, according to their own desires like to format, correct grammar mistakes, discover new facts and cite them, rearrange old unwieldy articles, or create new ones. That is satisfying work. You can see your results. Asking someone to verify every reference in an article is not very popular, as you can tell from the backlogs. There a million articles (yes 1,000,000) with bad references. Every time one of those articles is copied, the number ratchets up.
In the database world, there is a concept called normality. One such standard is third form normal. In it a fact (datum) occurs only once. It is either correct or false. Fix it once and it is fixed everywhere. We allow wikilinks to whole articles. Why not have another form of wikilink that allows one to build an article from portions of other articles? Instead of copying a paragraph, leaving two separate paragraphs that have to be maintained, there is only one underlying paragraph that is correct in both articles? It would solve so many problems where we now use {main}. The subsidiary article explodes and gets out of sync with the main article.
It's a big step, but it would solve many problems. I posted at the Teahouse, but was recommended here. Rhadow (talk) 13:01, 11 August 2017 (UTC)
* I'll start with where I do agree with you. Normalisation is a great goal for basic data. We all should be using it to simplify references and citations. AS an example I have just been looking at one page where one book has its bibliographical information and wikilinks repeated 13 times, a full reference for each change of page number! My task this evening will be to change it to a sfn system so that there is one bibliography and a series of simple references with the page numbers.
* Where I disagree however is when we have "a multiplicity of articles describing the same content in different mixtures" and you say "There is no harm in that". Intelligent use of WP:MERGE and hat notes should seriously reduce duplication. This is the 21st century and we do have hypertext! It is reasonable to précis the page "History of XYZ" into a one or two paragraph summary in a section called history within the "XYZ" article. A hat note will lead the reader to the fuller form. What is a waste of time is to copy word for word (and reference for reference) paragraph after paragraph from one page to another. Speaking personally I would not expect a summary to have detailed referencing if there is a full form elsewhere, so the issue of propagating bad references also goes away.
* In summary; lets keep normalisation for data and sort out duplication using the existing structures of Wiki. I'm sure there are boundary cases but to create a structure to solve a problem that shouldn't be there in the first place is, IMHO, a waste of time. Regards, Martin of Sheffield (talk) 13:24, 11 August 2017 (UTC)
* It'd be difficult to maintain. For example, when preparing Papal conclave, May 1605 for GA review I copied content into the background from Papal conclave, March 1605, since that was the background and it had just made it through a GAR, so I knew the content was of GA quality. I made some tweaks to it if I recall in terms of tense, etc. Having the content for these articles be in one normalized source paragraph makes little sense because they took place in (barely) different moments in time. While one is the background for the other, having them be from the same source (let's assume it is a page with the paragraph that could be transcluded), would not be helpful but copying existing content in a new page and then tweaking it was. Similar issues took place with Foreign policy of the Donald Trump administration, which we split and trimmed from Foreign policy of Donald Trump and Economic policy of Donald Trump. Copying the content was useful, but keeping them separate was as well. TonyBallioni (talk) 13:36, 11 August 2017 (UTC)
* Hello Martin of Sheffield -- "[T]o create a structure to solve a problem that shouldn't be there in the first place is, IMHO, a waste of time." It seems we are in violent agreement. On the point of copying paragraphs and references we agree completely. One should be able to capture a lede in its entirety and in fixed, verified form, and insert it elsewhere, not as a hyperlink, but as readable text, no references needed (because they have already been captured). Having two articles that include common elements, but from a different viewpoint, is a matter for discussion. I say "no harm in that." You see it as unnecessary duplication we can eliminate by WP:MERGE. In the example I described, the editor defended the article to the extent that he or she reverted the Delete tag. Losing the history of the text and its references didn't matter to the editor in the slightest. I pointed out the danger in that, and I think you agree. TonyBallioni gives support for copying and pasting in a specific instance, to disaggregate articles as was done with Trump. What is the solution? Rhadow (talk) 14:23, 11 August 2017 (UTC)
* I do like being in "violent agreement", it's much better than the other! :-) I suspect that the instance you are talking about comes under the "boundary cases" heading. Yes they occur, but are rare and can be dealt with in an ad hoc manner. I just don't see the need for establishing the superstructure of a paragraph database. I may have a poke around and take a look this evening. Martin of Sheffield (talk) 15:03, 11 August 2017 (UTC)
* Hello Martin of Sheffield -- Think of the problem another way: Most all of the satisfaction WP gives editors comes from fixing, adding to, or creating content. How about some kind of recognition for merging content, making WP more compact without losing any knowledge? Rhadow (talk) 15:10, 11 August 2017 (UTC)
* The issue here is that you are basically talking about a paragraph database. Anyone who is not a data scientest has worked with databases will tell you how difficult they are to maintain: doing it for something as complex as paragraphs within the English Wikipedia (which is already poorly maintained on many of our older articles) would be much more difficult than just doing it on an article-by-article basis. Wikidata exists and tracks some data between the English Wikipedia and her sister projects. It might be something that you might be interested in if you didn't already know about it. TonyBallioni (talk) 15:39, 11 August 2017 (UTC)
Proposal to change the existing displayed title "Ching Hai" to "Supreme Master Ching Hai"
As said in the subject, I suggest the title of the article "Ching Hai" should be changed to "Supreme Master Ching Hai" due the following reasons: According to the Wikipedia policy for article titles, 1. When the subject of an article is referred to mainly by a single common name, as evidenced through usage in a significant majority of English-language reliable sources, Wikipedia generally follows the sources and uses that name as its article title (subject to the other naming criteria). And "Supreme Master Ching Hai is the name of the subject that is most frequently used to refer to the subject in English-language reliable sources. 2. Ching Hai can be meant to be anyone's name, a name of a place, a name of a thing, and even a phrase of certain meaning in Chinese Language. You will find all different kinds of information related to these two words "Ching Hai" not related to the subject depicted in this article while searching on the internet. And therefore, due to ambiguity in the name "Ching Hai", I suggest "Supreme Master Ching Hai" is the most adequate title name for the article. -- Orwuck (talk) 06:12, 15 August 2017 (UTC)
* That is not the purpose of this page. See Requested moves for information about how to propose a move (title change) of an article. ― Mandruss ☎ 06:54, 15 August 2017 (UTC)
* Also, that would not be a correct move. We don't even have the page name Emperor Akihito for Akihito. We don't call the queen of the U.K. "Queen" in the title of the article either. RileyBugz 会話 <sub style="color:#D7000B;">投稿記録 10:55, 15 August 2017 (UTC)
RfC notice: Remove "adult" as a descriptor from the opening sentence of Family Guy
I've made a proposal to have "adult" removed from the opening sentence of Family Guy at Talk:Family Guy. Curly "JFC" Turkey 🍁 ¡gobble! 13:15, 15 August 2017 (UTC)
Bot to add Template:High-use and Template:High-risk to templates that need them
Template:High-use and Template:High-risk are templates which are meant to be added to the documentation pages of templates which are transcluded on more than 2,500 (Template:High-use) or more than 100,000 (Template:High-risk) pages. They notify people viewing these templates that changes to them are risky since they are transcluded on so many pages. But, many templates that need the high-use or high-risk templates still don't have them. For example, many of the templates in the lower ranks of the top 3000 most transcluded templates don't have the high-use template, even though most of them are transcluded on 5,000-6,000 pages. To solve this problem, I propose a bot that would look through the templates in Category:Wikipedia templates and see how many transclusions they have. If one had more than 2,500 and less than 100,000 transclusions, the high-use template would be added to its documentation page. However, if it had more than 100,000 transclusions, the high-risk template would be added to its documentation page. Phil roc My contribs 15:42, 15 August 2017 (UTC)
Allow users in the Account Creator user group to add users to the Confirmed user group
Some time in the next month or so, the Wikimedia Foundation will be implementing WP:ACTRIAL at the request of the English Wikipedia community. (See the RfC.) During this trial, new (non-autoconfirmed) users will not be able to create new pages in the main (article) namespace. There is concern this could interfere with legitimate new article creation during edit-a-thons and similar events. In order to address this issue, I would like to propose that we modify the Account Creator user group (which is commonly assigned temporarily to people running edit-a-thons) so that users in this group can add other users to the Confirmed user group, thereby allowing vetted users to create new articles at these events. (Note that these articles will still be added to the reviewing queue at Special:NewPagesFeed.) The purpose of this change is basically to provide a work-around during ACTRIAL, so that disruption to these events can be minimized during the trial. As such, it can either be a temporary or permanent change, depending on what the community prefers. Kaldari (talk) 21:23, 4 August 2017 (UTC)
* Support as a temporary change during WP:ACTRIAL. Most users who are added to the Account Creator user group are experienced event coordinators who are at least providing some basic guidance on how to create proper articles. Although I'm sure there will still be a fair percentage of low quality new articles from edit-a-thons, this will hopefully keep us from throwing the baby out with the bathwater. We should remember that ACTRIAL is about reducing the volume of spam and COI articles, not 100% eliminating all bad new articles. Overall, I think the contributions from edit-a-thons are a net positive for Wikipedia and we shouldn't cut those contributions off. Kaldari (talk) 21:23, 4 August 2017 (UTC)
* One of the major objectives of ACTRIAL is to reduce the workload for reviewers and other maintenance workers. Last week an editathon in South Africa organised by the SA chapter and the Swedish embassy was publicised during a TV interview and received a high participation. Unfortunately, the facilitator was ill prepared for the unexpected high participation and a number of articles were produced in good faith but were totally unsuitable for an encyclopedia. It's a shame to have to delete these otherwise good faith efforts. Rather than making any changes to the User Group permissions, perhaps it would be more appropriate for editathon facilitators to teach their students how to edit by getting them to create their articles in their sandbox or or in the Draft namespace instead. Facilitators could them move suitable articles to mainspace for them. Kudpung กุดผึ้ง (talk) 00:20, 5 August 2017 (UTC)
* See the TV article on SABCnews. Kudpung กุดผึ้ง (talk) 03:05, 5 August 2017 (UTC)
* Ha! Kaldari, you should know by now that "experienced" has a multitude of meanings. You are aware of the issues relating to the recent Dalit campaign, which involved edit-a-thons and was a disaster. This summary only brushes the surface and is replete with poor decision-making from admins and past/present WMF staff. I can assure you that I am not alone in my estimation that it was a complete mess. I wouldn't trust people like that to make exceptions to whatever the standard operating procedure/policy/guidelines might be. There is no deadline for creating articles but we have a limited number of regulars who actually know what they're talking about, and they're stretched as it is. - Sitush (talk) 00:37, 5 August 2017 (UTC)
* Oppose/Needs improvement first as-is, way too many people are getting added to account-creator already that aren't even confirmed themselves! (See this list). I would normally support this, but not unless we put some actual requirements on being an account creator first. — xaosflux Talk 01:04, 5 August 2017 (UTC)
* There are 338 names on that list, probably a lot more than are needed, a very large number of which whose edit count is only double figures. Recently buttons were added to the User Rights Manager to be able to accord rights for a limited period after which they would expire. This was particularly useful for Account Creator. However this feature seems to come and go for various user groups and is again not available for Account Creator. Curiouser and curiouser. Kudpung กุดผึ้ง (talk) 03:37, 5 August 2017 (UTC)
* the expiration should be always available to assign, if you see a case where it's not I'd be happy to check and get a bug open if it is not. Many, many of these were added for "events" and a specific administrator did the majority - I'm following up with them. — xaosflux Talk 12:34, 5 August 2017 (UTC)
* It's a browser problem, . The buttons are not rendering in Firefox on Mac. Kudpung กุดผึ้ง (talk) 16:37, 6 August 2017 (UTC)
* Re: needs improvement: To be clear, what I think needs fixing first is qualifications/expiration needs for the account creators themselves. — xaosflux Talk 20:04, 7 August 2017 (UTC)
* Support as useful: as a Lead Trainer for WMUK, I've been running editathons and other training events for the last five or six years and have trained hundreds, perhaps thousands of new editors. As I stated at Wikipedia talk:Autoconfirmed article creation trial, it would be helpful – but by not means essential – to be able to grant autoconfirmed status to event participants on occasion. Most participants work in their sandboxes, and it is not so often that they want to create a new article, so ACTRIAL won't impact much on most of them. In those cases where an non-autoconfirmed editor has the ability to create a new article on the day, there are work-arounds available. Nevertheless granting autoconfirmed status to someone who is clearly capable of producing a new article that early in their editing career doesn't seem like much of a risk, so I can't see any problem with account-creators being able to do that. Either you trust account-creators to do these sorts of jobs, or you don't; if you don't, then I can understand you opposing the proposal here. --RexxS (talk) 12:12, 5 August 2017 (UTC)
* I don't - but I think I could - if we vetted the account creators more (e.g. they had to be extended confirmed to use this). Guidance would be to add confirmed with say a short expiration date, if the people are editing they will end up getting autoconfirmed in a few days anyway. — xaosflux Talk 12:34, 5 August 2017 (UTC)
* So the instructions at the editathon might be: "You've made 10 edits, so now all you have to do is sit around here for a few days and you'll able to move your new article into mainspace." It kinda misses the immediacy I usually hope for. :D --RexxS (talk) 15:10, 5 August 2017 (UTC)
* No, assuming this gets supports, I'm saying that attendees would get +confirmed for say a month - if they never come back it just expires, else by the time it expires they would already be autoconfirmed. — xaosflux Talk 16:15, 5 August 2017 (UTC)
* That sounds very reasonable. In practical terms then, what would be the difference between having the right expire after a month and not having the right expire after a month (assuming all participants at an editathon/training event will make at least 10 edits on the day)? --RexxS (talk) 16:24, 5 August 2017 (UTC)
* Support per RexxS; and speaking as an equally-active trainer. Andy Mabbett ( Pigsonthewing ); Talk to Andy; Andy's edits 16:46, 5 August 2017 (UTC)
* Support as a temporary change during ACTRIAL: Some newbies go through the ACC process, but during edit-a-thons etc; will be a major disruption to events. KGirl (Wanna chat?) 18:49, 5 August 2017 (UTC)
* Support per RexxS, but with the understanding that there will be clear guidelines for granting that would include among other things time limited granting, both of the confirmed status and of account creator status. Note, I don't think ACTRIAL will be a major disruption for editathons per feedback we've received at those discussions. This is, however, a nice plus to make it easier. TonyBallioni (talk) 18:55, 5 August 2017 (UTC)
* Support on a temp basis Maybe we can see how this works in the future as well. <sup style="color:#093">My name is <small style="color:#4000FF">not <sup style="color:#093">dave (talk/contribs) 08:19, 6 August 2017 (UTC)
* Support on a temp basis during the trial, for in person event coordinator use only, due to the time and logistical limitations of such events. Any other use of the ability (in the ACC process, etc) should be treated as misuse and grounds for removal of the bit. – Train2104 (t • c) 12:27, 6 August 2017 (UTC)
* Oppose Per the comments below and some review of the list of users with this flag, I have some serious concerns about a relatively large number of users with little to no experience/knowledge of WP policies having this ability. If/when the eligibility requirements for accountcreator are stricter, we can revisit this. See also this apparent free-for all request page. – Train2104 (t • c) 16:48, 8 August 2017 (UTC)
* Support during ACTRIAL per above for now. There is no need for having this on a permanent basis. I don't think it should be limited to event coordinators though. Regards So Why 16:44, 6 August 2017 (UTC)
* Support - both as a temporary change during ACTRIAL and as a permanent change. It would be good to have this on a permanent basis because of the fact that it would help those at Edit-a-thons upload images for the articles they are creating. RileyBugz <sup style="color:#D7000B;">会話 <sub style="color:#D7000B;">投稿記録 16:52, 6 August 2017 (UTC)
* Support during ACTRIAL. Edit-a-thons often involve creating articles. — MRD 2014 Talk • Edits 00:25, 7 August 2017 (UTC)
* Support at least for now until we work out something better. This won't deal with all difficulties in training, but it will help. About 9/10 of the trainees usually do not come back after a month, so there ought to be some expiration date, or they might come back years later and still have the confirmed right (unless this proves to be too difficult to program, it which case we just think of it as a minor problem. However, it is essential that for relatively inexperienced group leaders granted account creator for a particular editahon, that both account creator and this userright expire . DGG ( talk ) 05:26, 7 August 2017 (UTC)
* Support for the duration of ACTRIAL, and or if that experiment becomes permanent. Sadads (talk) 17:57, 7 August 2017 (UTC)
* Support on an ongoing basis. Enabling edit-a-thons and other events with training and editing on the same way is good for the encyclopedia.--Carwil (talk) 20:34, 7 August 2017 (UTC)
* Support Give the userright and let participants make wiki articles. I sympathize with Xaosflux's reasons for opposing but the reality is that at the current pace of conversation, the account creator userright will not be developed sufficiently within the next 3 years. Despite the potential for abuse, there is no public history of problems documented with this userright or with in-person Wikipedia editing events. I do not think that this userright is the origin of the tension, but rather, the tension is between the WMF and Wikimedia communities who are organizing large numbers of in-person wiki events while some of the Wikipedia community are unwilling and uninterested to acknowledge the existence of the events. If the events will happen, then the user right should be granted. If anyone opposes the events, then please take the argument to the WMF which sponsors them and has capacity to host discussions on how they should be managed. Blocking events with private discussions with the lower level, more vulnerable, and well meaning volunteer organizers who do not want to be swept into wiki politics is not the way to develop the Wikimedia community's event policy. Blue Rasberry (talk) 21:15, 7 August 2017 (UTC)
* Support confirmed is not a very dangerous user right to have and the threshold for getting it normally is very low. I would support making this permanent. Hut 8.5 21:20, 7 August 2017 (UTC)
* Support I think account creators are trustworthy enough to know who should and shouldn't be able to create pages during ACTRIAL, and this seems to be beneficial for letting them create pages without making a given # of minimum edits. Everymorning (talk) 22:12, 7 August 2017 (UTC)
* Support This seems like an eminently reasonable proposal, and in cases of abuse it seems easy enough to reverse. Ancient Studies major (talk) 22:40, 7 August 2017 (UTC)
* Oppose Let these new editors write drafts. I've been to a fair number of edit-a-thons and I don't think most account creators are doing enough to control what the attendees write. Show me that account creators are always being held responsible before I place any trust in their discretion. Chris Troutman ( talk ) 22:45, 7 August 2017 (UTC)
* Support - Sure. Account creators are trusted individuals, and this addition makes sense for their work. -- Ajraddatz (talk) 23:07, 7 August 2017 (UTC)
* Support per RexxS. Thanks. Mike Peel (talk) 23:20, 7 August 2017 (UTC)
* Oppose until we prune the list of account creators. As of now, I count some 320 account creators, 221 of which have made fewer than 1000 edits (including 50 that have made <10 edits, and another 96 that have between 10 and 99 edits). T. Canens (talk) 23:30, 7 August 2017 (UTC)
* Oppose per T. Canens. There are very few editors I'd trust with this tool. Callmemirela 🍁 talk 23:55, 7 August 2017 (UTC)
* Support per Blue Rasberry. Double sharp (talk) 23:59, 7 August 2017 (UTC)
* Oppose first per Chris Troutman (I wish all editathon organizers were RexxS but that is not what the incoming pages stream suggests) and then additionally for sake of ACTRIAL's data. I'd rather see what ACTRIAL does when "fully" implemented rather than muddy the data by allowing account creators with potentially widely varying standards to override the limit on new users sending pages straight to mainspace. Innisfree987 (talk) 00:30, 8 August 2017 (UTC)
* Oppose. Let's be clear on a few things. There is nothing bad about editors creating drafts as part of edit-a-thons and submitting those drafts through AfC. In fact, that's the whole point of ACTRIAL; new editors submitting to AfC instead of mainspace. Second, keep in mind this opens the door of removals of account creator for cause. If this passes and I see an account creator grant the right to an editor who goes on to create inappropriate articles, that account creator will lose their user right. That's going to affect edit-a-thons more severely than submitting drafts to AfC. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 01:12, 8 August 2017 (UTC)
* , from some of the comments here re: account creators, creating clear guidelines for revoking the tool seems like a positive to me, not a reason to oppose. Re: ACTRIAL, we received some pretty vocal feedback from users who cared about editathons and similar programs. We do have some very bad editathon creations, but we also have some very good ones that I think are probably a large part of the 20% of articles by non-AC users that don't get deleted. Your comment did remind me though that I think that if this is implemented, there should be an explicit guideline preventing its use as a part of the education program/WikiEd/school courses: those are the organized events that in my opinion have the most inappropriate creations directly in article space. TonyBallioni (talk) 03:04, 8 August 2017 (UTC)
* Here's the scenario I'm worrying about. Account creator grants the confirmed flag during an editathon, and the editor they grant it to creates an article that is immediately speedy deleted as a copyright violation. At this point, the account creator has bypassed ACTRIAL for an editor who doesn't know what they're doing, and the only recourse to prevent this from recurring is to yank the account creator right. Now the account creator is 30 minutes into their edit-a-thon without the ability to help editors create accounts and everyone's worse off. That's surely a concern. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 12:30, 8 August 2017 (UTC)
* , thanks for the response. I still see having a fleshed out policy as to when to remove the account creator bit is needed, and think that this conversation has shown that. Your example is a good one, but by giving people clear guidelines, I think it would be rare. As an aside that is probably better for one of our talk pages, the issue of copyvios in new content is really something that we need to work on educating people at NPP/AfC about. So much gets through that isn't caught by EranBot. TonyBallioni (talk) 15:07, 8 August 2017 (UTC)
* Oppose mainly for the reasons highlighted in my initial comment above, which Chris Troutman reflects in a more succinct manner.; also per BU Rob13 and Innisfree987. I think T.Canens; figures may be slightly skewed because there are some obvious low-count entries in the results list where it would seem experienced contributors have created "roaming"/"public place" accounts for use at edit-a-thons. Nonetheless, there are enough scary examples in there to make me wonder who has been granting these user rights. - Sitush (talk) 02:57, 8 August 2017 (UTC)
* support seems like a good idea. this way, during editathons and such, they can edit semi-protected articles, and create new pages during the ACTRIAL. really, confirmed is not that much of an additional privilege. if there are problems, it can always be rescinded. -- Aunva6talk - contribs 03:22, 8 August 2017 (UTC)
* Oppose This sounds like a horrible idea in my opinion. Whispe ring 03:31, 8 August 2017 (UTC)
* Oppose As a recent participant in a Wikipedia Meetup, almost all users were creating articles as drafts or in the sandbox anyway. There is no reason why edit-a-thon contributors cant just submit their drafts for review to AfC as intended, and no reason why these drafts cannot simply be added to a list and edit-a-thon helpers (like myself) can't review their AfC creations themselves, or else move the drafts to mainspace for them (after reviewing them). In the worst case, a draft has to go through a bit of a wait at AfC... what is the problem here? This is the whole point of ACTRIAL, and shouldn't be sidestepped during edit-a-thons or meetups. — InsertCleverPhraseHere 04:05, 8 August 2017 (UTC)
* Oppose per Keira 1996 04:10, 8 August 2017 (UTC)
* Oppose per Xaosflux, Kudpung, and Sitush. Vanamonde (talk) 04:40, 8 August 2017 (UTC)
* Oppose: I fundamentally oppose to all measures increasing any rights of those organizing mass events. This is just WM-agenda, increasing their maneuverable volume, but decreasing WP-quality by under cover agenda pushing. See all further arguments above. Purgy (talk) 06:32, 8 August 2017 (UTC)
* Oppose I see no real reason why new editors should be given the ability to easily make pages, they should go through the proper autoconfirm process. or they should create an account before the event like a sensible person would, to learn about Wikipedia, rather than jumping into the deep end of Wikipedia's most difficult task. making bulk new pages does not really help Wikipedia much anymore, since it just 'bungs up' the new page patrol system. A Guy into Books (talk) 07:23, 8 August 2017 (UTC)
* Oppose. The most appropriate, manageable, and helpful route to creating new articles during an edit-a-thon is via the draft process. The participants are then being taught the method which they will need to know when the edit-a-thon is over, and there is an encouragement and incentive for participants to get the article right in order for it to go live. It also encourages the attitude that while anyone can edit Wikipedia, what we're after these days is quality contributions. I would rather an edit-a-thon resulted in just one good quality contributor remaining active than have 100 well meaning but less than competent contributors remaining active adding inappropriate unsourced material which then has to be dealt with. SilkTork <sup style="color:#347C2C;">✔Tea time 08:03, 8 August 2017 (UTC)
* Support This should be granted on a long-term basis as it's a hassle if this keeps lapsing. For example, I currently have the account creator right. On Aug 17, I'll be attending an event at the Royal Society of Chemistry. So far as I know, the main organisers are not admins and neither am I. Because it will be on a weekday, participation by volunteers may be limited and so this seems a good example of an event that might be disrupted by over-zealous throttles on account and article creation. The institution and organisers are of impeccable quality and so it's us that will look bad if we can't handle the smooth onboarding of novices at such an event. As another example, I was recently discussing setting up an event at the Wiener Library. At the last event there, the main organiser was actually blocked by an admin, which caused considerable bad feeling. Such hostility is contrary to policy and is foolish. I was myself checking out Everipedia this morning. I don't know much about it yet but get the impression that it has some momentum because it is more open and welcoming. Wikipedia is not the only game in town. As a further example, I just got an edit conflict posting this. This place really tries one's patience... Andrew D. (talk) 08:06, 8 August 2017 (UTC)
* "Impeccable quality" as scientists, sure. But in terms of Wikipedia knowledge? - Sitush (talk) 08:17, 8 August 2017 (UTC)
* The main organisers I'm thinking of are Dr Jess Wade and Dr Alice White. They are bright, energetic and personable. And they are fun to work with – that's why I'm going to take a day's leave to support this event. They exemplify "good faith" and so we should strive to facilitate their work rather than putting obstacles in their way. Andrew D. (talk) 09:44, 8 August 2017 (UTC)
* Encouraging users to use the appropriate process should not be viewed as an obstacle. No one here is suggesting putting obstacles in anyone's way; rather, that the due process we have been developing to protect Wikipedia and to enable and encourage positive participation should not be specially put aside. All new articles are over-viewed by the community, be they articles created in someone's home, place of work, university library or an edit-a-thon. The users at the edit-a-thon are no different to any other user - their work will be seen by our new page patrollers and dealt with. If inappropriate articles are rejected by the patrollers this will have a dispiriting effect on the edit-a-thon editors. I'd rather they were shown the right way of editing Wikipedia, so they don't have the experience of their work being speedy deleted, but have it go through AFC where if it gets rejected reasons are given, and the work is still available for the user to work on. Not an obstacle, but an assistance. SilkTork <sup style="color:#347C2C;">✔Tea time 11:43, 8 August 2017 (UTC)
* That sounds like you are suggesting that some people are more equal than others, more deserving of special treatment that is not available to other new contributors. As I said way, way above, it is evident that course organisers etc cannot or do not always vet what goes on and so such special treatment both undermines the trial and doesn't fix the longer-term problem. I realise different edit-a-thons attract different people but the ones I've come across have had pretty universally poor outcomes that have entailed a massive amount of clean up for BLP violations, copyright issues, sourcing and, well, pretty much everything. Being keen is good; being au fait with how Wikipedia works takes time. Edit-a-thons tend to rush through a lot in a short span. Tbh, I'd be quite happy if they didn't exist. - Sitush (talk) 12:03, 8 August 2017 (UTC)
* All users are not equal – that's the point of this discussion as we're talking about permissions and privileges. Confirmed status seems designed mainly as a pure obstacle. The main issue is the four-day wait and that has no functional purpose as nothing much happens during that time; it's just a cooling-off period to discourage people. One consequence of not having confirmed status is that you have to supply CAPTCHAs when adding references. Adding citations is painfully difficult for experienced users; that's why so little of it gets done. When you have to do CAPTCHAs too then it becomes really annoying because they are not easy; I have trouble with them myself. Again, this is another obstacle especially designed to make it difficult for new users rather than encouraging them. Experienced users and admins tend not to appreciate how obnoxious Wikipedia is for a new user because, thanks to their privileged status, they don't have to deal with these obstacles. But all our current experienced users will not exist in due course because we don't live forever. Who will edit Wikipedia in the future if we make it increasingly difficult to get in? Andrew D. (talk) 17:50, 8 August 2017 (UTC)
* All new user are equal. They have no privileged rights unless someone grants them. I don't trust the edit-a-thon environment (plenty of empirical evidence) nor, indeed, quite a few of the account creators to grant rights appropriately and I don't see why a new user should so arbitrarily be able to leapfrog a system that by far the majority of new users have to go through. I'm well aware of the issues of not being autoconfirmed because I've edited occasionally when logged out (one or two edits, in subject areas I never visited before or since). Not having the arbitrary account creatoin process does not make it more difficult to "get in" than it already is. - Sitush (talk) 18:49, 8 August 2017 (UTC)
* Empirical evidence? I have attended over 10 events so far this year. They were all of high quality and were typically in partnership with world-class academic and GLAM institutions. They were typically focussed on a new event or on filling in red links, such as missing women. Article creation is a fundamental aspect of such events and it's something that our partners like and can get funding for, because it's productive – an outcome that they can measure and boast about. If you invite people to a one-day event with such a focus it is then ridiculous to tell them that they have to wait four days. That's what ACTRIAL would mean; it would make us look like jobsworths rather than the encyclopedia that anyone can edit. Andrew D. (talk) 06:48, 10 August 2017 (UTC)
* I've given you some empirical evidence, Andrew and I've already explained that being an expert in an academic field has no bearing on abilities as a newcomer to Wikipedia. This isn't really about biting the edit-a-thon newcomers, who would be treated just like any other newcomer, but rather the people who grant the rights. Too many, including admins and WMF staffers, demonstrated cluelessness in this area and are so set on their pet "social justice" projects, grant income etc that they can't see the wood for the trees. Sue Gardner's much maligned Indian Education Program was another example. That said, even a select group of newcomers - whom you for some reason think automatically know what they're doing here - would be less likely to be bitten if they went through the usual processes of AfC etc. - Sitush (talk) 07:20, 10 August 2017 (UTC) (Sorry, my "biting" bit makes little sense because you edited your comment while I was writing mine. - Sitush (talk) 08:18, 10 August 2017 (UTC))
* Oppose As per, while we want to encourage the view that anyone can edit Wikipedia, we also want to encourage the view that creating quality material requires learning about policies and processes, particularly the need for reliable sourcing. Peter coxhead (talk) 08:47, 8 August 2017 (UTC)
* Oppose, per Xasoflux. Joefromrandb (talk) 08:51, 8 August 2017 (UTC)
* Support while I haven't been involved in many editathons since I left WMUK, I have been involved in quite a few in the past. This userright would be useful in running such events, and it is a reasonable mitigation of ACTRIAL. I have seen attendees at such events not get the importance of having some reliable sources before they hit save, but most attendees create articles that meet our notability threshold, and I've never encountered a commercial spammer or a vandal at an editathon. More to the point, such articles created at editathons are almost always more encyclopaedic than the aspiring not yet professional model, musician or sportsperson who NPP is deluged with. Ϣere Spiel Chequers 10:01, 8 August 2017 (UTC)
* Oppose, I agree with Xasoflux and Kudpung, and, this imho is where draft process is for. ron az <sup style="color:purple;">Talk! 10:18, 8 August 2017 (UTC)
* Oppose Until there some kind of vetting policy for Account Creator, I can't see giving that user group that kind of power. Sario528 (talk) 11:59, 8 August 2017 (UTC)
* Oppose Edit-a-thons & other wiki-events will be far more productive if they aim to develop new wikipedians who understand why wikipedia is the way it is and happen to have a specialist knowledge rather than incubating COI editors who will abandon the wiki as soon as the event is over and they encounter the real requirements of the wiki. The problem as outlined is more about how the event is conducted rather than about how ACTRIAL and Wikipedia operate.
* Encouraging new editors by promoting their articles from userspace/draft rather than setting them up for a bruising review experience the next day will be more likely to encourage them to stay - and that is the purpose of these events, isn't it?
* The objectives of the proposal would be better met by:
* A template on the draft/article stating that it was produced as part of event, identifying the event's coordinator, categorising the article/draft into a maintenance category for the event, and requesting that during the event (start date & time, end date & time) it would be appreciated if all review action were focussed on helping the author grow as a wikipedian rather than cleanup.
* An editnotice onthe draft/article to the same effect, with an expiry set for the event's end.
* Getting Twinkle & Huggle to observe the event's template & refuse to add deletion tags during the event. Cabayi (talk) 11:57, 8 August 2017 (UTC)
* Oppose - for the reasons stated by Chris Troutman, and BU Rob13. The draft process has a greater control aspect as to the quality of the work proposed. Kierzek (talk) 13:34, 8 August 2017 (UTC)
* Oppose, users participating in edit-a-thons should experience the same Wikipedia processes as everyone else. (If my brother goes to an edit-a-thon and then tells me how he created an article, and I then I make an account but can't create an article, I will give up on Wikipedia right away). Also, edit-a-thons and other newbie-sirected activities should probably try to focus on editing existing articles. —Kusma (t·c) 13:38, 8 August 2017 (UTC)
* Oppose per those in favor of using the draft space. Bending the rules for new users may have the opposite effect of what the edit-a-thons are trying to accomplish. May as well use the processes your typical new user has to use and adequately prepare them for what Wikipedia is really like. ZettaComposer (talk) 14:05, 8 August 2017 (UTC)
* Oppose Primarily the reason being not all account creators are properly vetted. I do not feel autoconfirmed is a high bar and recommend reaching this bar stay in situ. While necessarily removing a hindrance, this also can be wrongfully abused, accidentally or not. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 ) 15:24, 8 August 2017 (UTC)
* Support as temporary change during WP:ACTRIAL. Unless a large portion of the members of the account creator group suddenly decides to join the dark side en masse, I can't see how this can blow up in any meaningful way during a short trial period. I would however suggest combining this with somewhat greater circumspection in handing out the right (500/30 seems like a reasonable bar). -- Elmidae (talk · contribs) 15:32, 8 August 2017 (UTC)
* That isn't possible, because we have people who aren't familiar with Wikipedia running edit-a-thons from an administrative perspective all the time. Do we bar such edit-a-thons from occurring? Moreover, the concern isn't "those evil account creators". I don't doubt our account creators act in good-faith. The concern is that they hand out the "confirmed" right to everyone participating in the edit-a-thon, and the edit-a-thon participants create articles not suited for mainspace. That happens all the time in connection with edit-a-thons. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 15:54, 8 August 2017 (UTC)
* My thinking is that any edit-a-thon participants of events held during the envisioned ACTRIAL period are unlikely to make much of a blip on the radar, compared to the usual flood of unsuitable creations. a) There wouldn't be all that many of them (don't have any stats - a couple of thousand people? I may be way off); b) as someone noted above, they are well-intentioned and at least somewhat supervised. So, I doubt much potential damage in total, compared to business as usual. Thus an evaluation of the effectiveness of ACTRIAL should still be very possible - and isn't that the main goal?
* Regarding experience thresholds of edit-a-thon organizers - I was under the impression these would be somewhat seasoned users. If that's not generally the case, a high threshold for account creation rights wouldn't be sensible, of course. -- Elmidae (talk · contribs) 19:04, 8 August 2017 (UTC)
* The granting guidelines for ACC seem to be rather permissive at present, perhaps better to instruct coordinators on the process to request confirmed and try to have an administrator or two to keep an eye on the permission page during the event if the participants are expected to require 'confirmed'. –<b style="font-family:verdana;color:#000">xeno</b><sup style="color:#000">talk 17:12, 8 August 2017 (UTC)
* Oppose- it is what, four days and 10 edits? If someone is going to come onto WP, I think 4 days is a logical minimum to understand the ropes of article quality. Further, the 10 edits shouldn't even be an issue, as if the user is creating the article in the sandbox or similar space, they should make at least 10 edits in creating the article there. I don't think edit a thons deserve special treatment (though I'm not wholly familiar with what they are). And being a part of an edit a thon doesn't make someone more trustworthy. Summary - 4 days and 10 edits do not create undue hardship for anyone, and giving power to lift it arbitrarily because someone is part of some organization does not seem rational. Even if we trust the admin more than anything, how can they have any idea if the individual is trustworthy? Leave it be ‡ Єl Cid, Єl Caɱ̩peador ᐐT₳LKᐬ 19:23, 8 August 2017 (UTC)
* Support as a temporary change per those above. JTP (talk • contribs) 21:16, 8 August 2017 (UTC)
* Support If one of the goals of editathons is to bring in new editors and get them to write articles, making them potentially wait weeks to get their articles reviewed (and possibly shot down by a reviewer with really high standards anyway) is going to be really unsatisfying. The discussions on ACTRIAL happened before article-creation editathons were as frequent as they are now (in particular, WikiProject Women in Red didn't exist back then), and we need a measure like this to account for that change. TheCatalyst31 Reaction•Creation 23:50, 8 August 2017 (UTC)
* I literally just participated in a women in red editathon meetup and I have to say that there is no need for this. Everyone was working in the draft space anyway, it it was much better to review the articles myself before submitting them to namespace than to let the new users do it themselves (a result of some users working in the mainspace resulted in some articles getting prodded, and another article getting onto mainspace with copyright violations. These problems would have been avoided if these users needed help promoting their articles as the issues would have been flagged when doing so. — InsertCleverPhraseHere 00:02, 9 August 2017 (UTC)
* Support during ACTRIAL. --joe deckertalk 01:29, 9 August 2017 (UTC)
* Comment I'd be far, far, more amenable to arguments that "let 'em use drafts" if we had a Draft review process that wasn't badly backlogged. --joe deckertalk 03:35, 11 August 2017 (UTC)
* Neutral. Assigning any user right should be left in the hands of administrators. But, then again, aren't account creators supposed to have their identities confirmed by the foundation? With that being said, I'm torn on where I stand, given that the requirement to have account creators' identities confirmed by the foundation adds accountability. Steel1943 (talk) —Preceding undated comment added 01:40, 9 August 2017 (UTC)
* Account creators who work in the request an account process are identified, but the user right is more commonly handed out to event organizers, who need not be identified. Many of these organizers are new users who have not even reached extendedconfirmed yet. – Train2104 (t • c) 03:51, 9 August 2017 (UTC)
* I now oppose this proposal now that I know there is a group besides Administrators that can have the account creation permission other than Account Creators. Steel1943 (talk) 18:49, 9 August 2017 (UTC)
* Question - Would implementing this proposal allow account creators to add existing accounts to the confirmed user group, or only allow for assigning this right during the creation of an account? I am inclined to support the latter but quite reserved on the former. Thank you.--John Cline (talk) 02:25, 9 August 2017 (UTC)
* As far as I can tell, it would be the former, just like an admin can assign permissions to any user. – Train2104 (t • c) 03:58, 9 August 2017 (UTC)
* Comment - It seems to me that supporting this as a temporary measure to mitigate the effects of ACTRIAL is tantamount with supporting a measure to reduce the value of the statistical data being assessed, and the trail itself. Am I wrong?--John Cline (talk) 05:48, 9 August 2017 (UTC)
* Comment I've been assuming that that the effects of this on the trial results would be insignificant, that new articles from these events do not make up anything like a signficant fraction of incoming articles from new editors. Am I mistaken? --joe deckertalk 15:00, 9 August 2017 (UTC)
* Same here. Any numbers available on that? -- Elmidae (talk · contribs) 16:54, 9 August 2017 (UTC)
* Oppose. With Wikipedia's increasing maturity, the bar for article creation needs to be higher to maintain quality. Editathons seem too often to be a source of low quality article by newbies whose convenors are unwilling to criticize. Xxanthippe (talk) 06:06, 9 August 2017 (UTC).
* Oppose Creating them in Draft adds extra work at the beginning for experienced users to review them but I feel that it will also allow to better guide new users and improve the quality of articles in main space. --Crystallizedcarbon (talk) 15:37, 9 August 2017 (UTC)
* Oppose per Kudpung, xaosflux, Sitush, and many others above who have observed quite serious problems with the provision of the account creator userright and suitability for mainspace of articles created at these events. Draft space is the way to go for these events. Ivanvector (Talk/Edits) 16:45, 9 August 2017 (UTC)
* Oppose. New editors should be encouraged to create drafts, and that's what editing event organizers should have them do anyway. I had people do that at an editing event I worked on and there were no issues with it at all, and a much reduced risk of having to field the question "Why does someone say my article should be deleted?". (Never happened.) Creating an article that's immediately mainspace ready is not something we should encourage new users to try, it's just likely to cause frustration on all sides. Seraphimblade Talk to me 17:10, 9 August 2017 (UTC)
* Oppose Per . This just doesn't make sense. Let me get this straight, the community decided to increase the prerequisite for article creation from "nothing" to "4 days and 10 edits" (addendum, per : for a trial run). But the WMF blocked this, and more than 6 years later they're just getting around to testing it? But they want to add the caveat where Account Creators, of all people, can exempt anyone as they see fit? What's even the point then, honestly? It seems like WMF is just trying to add a major loophole to something that they apparently disagree with enough to block a community decision for 6 years. As one of the admins involved at Requests for Permissions, I'll share something that not everyone may realize: Account Creator has fairly high requirements usually, including identification to the foundation, but it's also granted to basically anyone who says they need it for an event. These users may well just barely be autoconfirmed themselves. They're not some well-vetted, highly trusted class. They're literally random people, many of them inexperienced, who claimed they were running an event, and were permanently granted this flag (the ability to grant it temporarily finally exists, but it was only recently implemented). The task of revoking the flag from these users was reinforced by a community consensus, but it has yet be undertaken by admins, due it being a large, tedious and relatively unimportant task in an area where not many admins are involved. Anyway, if you're going to give Account Creators the ability to confirm accounts, you may as well give it to everyone. I just can't see the logic of delegating an administrative responsibility to a ragtag group of users who were rubber stamped. S warm ♠ 18:09, 9 August 2017 (UTC)
* I don't think the WMF is seeking this change; it's community members who for some reason think edit-a-thon participants going through AfC would be harmful (how? no clue). The WMF, if anything, would likely oppose this change because it would pollute the statistical results of the trial. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 18:17, 9 August 2017 (UTC)
* , my impression is that the WMF has as one of its goals increasing new editors. I don't think and the Community Tech team have strong opinions either way on this. I believe who works in another WMF department was one of the first to bring this up as an issue. also probably has thoughts on this as his team more directly deals with editor retention, but I don't know what his thoughts are on it in terms of affecting the trial. The short: my impression is that different parts of the WMF are viewing ACTRIAL in different ways. There is definitely some support for something like this there, but there are likely others who oppose it for the reasons you pointed out. TonyBallioni (talk) 18:24, 9 August 2017 (UTC)
* I see what you're saying about WMF not wanting to dilute the data, and that's certainly what you would think they would want. However, after the six-year delay in implementing this, a WMF employee's request for a major exemption for all outreach initiatives certainly does not give the appearance that they are actually supportive of this idea. I'm not saying Kaldari is disingenuously pursuing some sort of hidden agenda, and I think Tony's comment makes sense. I'm just pointing out that the ACTRIAL is such a modest change, and combined with the ridiculousness of this proposal (see my comments on ACCers above), which would gut it, the whole thing seems disingenuous. S warm ♠ 18:57, 9 August 2017 (UTC)
* With all due respect, much of what you said above is wrong. First, the community didn't decide to increase the prerequisite for article creation, they decided to request a trial of such a limitation. The WMF is now running that trial. The WMF doesn't want to add a caveat; the community expressed support for a very similar idea at Wikipedia talk:Autoconfirmed article creation trial. No one at the WMF has any strong opinions on this proposal (that I know of). If you don't want to AGF, that's fine, but I promise there's no conspiracy here. Kaldari (talk) 19:15, 9 August 2017 (UTC)
* Again, I was not assuming bad faith, nor alleging some sort of conspiracy, and I expressly clarified that in my previous comment. Thank you, but I don't actually need assurances from WMF staff that there are no nefarious motives at play. I'm sure we can both agree that such a notion is a bit ridiculous. And I'll point out that that aspect of my comment was not even my reason for objecting. It was just an observation on how ridiculous this proposal looks, in the context of my perspective on Account Creators and my perceived significant ramifications for the ACTRIAL. S warm ♠ 20:03, 9 August 2017 (UTC)
* The Community Tech team is helping to support ACTRIAL as a research experiment, because it'll give us better information about how all these processes work. It's possible that restricting page creation to autoconfirmed users will drive new people away to an unacceptable extent, and we'll lose good editors and good content. But creating a new page and having it deleted within a couple hours is a terrible experience for new users, so it's possible that if we redirect them to the Article Wizard and Drafts, then they'll be more likely to stick around and learn how to edit. Opinions on both sides are pretty entrenched, and running this trial will help us all have informed discussions about it. So that's why Community Tech is working on this -- you can see the hypotheses and measures that we're working on at Research:ACTRIAL on Meta.
* Running this trial has an impact on other people's work, so we want to minimize that if we can. People at the WMF who work with program leaders, like, want to make sure that people can run events successfully during the trial. We haven't actually looked at the experiment-pollution angle; we should see if we could get an estimate of the number of main namespace articles created in editathons, to see if it would make a difference to the statistical significance.
* But this is a community decision; that's why proposed this here. Running ACTRIAL isn't dependent on this decision; we've committed to running the experiment. -- DannyH (WMF) (talk) 19:18, 9 August 2017 (UTC)
* Those are the events that bring in a bunch of (often conflicted) new contributors who are enabled by people who often don't have much experience themselves (honourable exceptions) or who share similar conflicts and want to steamroller over policy etc in order to get their way (per the link to my talk page right near the top). "More editors" seems to be the overarching mantra and it should not be. - Sitush (talk) 19:29, 9 August 2017 (UTC)
* , how much research has been done into what type of editing productive long term users do when they first become active on Wikipedia, compared with the type of editing done by short term or single purpose editors whose work is largely unhelpful? Anecdotally, my impression is that the sort of editors on this page commentating on this (representative of the productive heart and core of Wikipedia), would not have started on Wikipedia by attempting to create a new article. While those editors who have started off by creating a new article, have tended to be those who have a vested interest in the subject they are introducing onto Wikipedia (and no real interest in editing on any other subject), and either disappear soon after they have created the article, or simply hang around to feed that article and none other. My anecdotal experience might well be shared by others on this page. We have spent a disproportionate amount of our time over the years, attempting to clean up messes created by users who are not interested in Wikipedia itself, but only in their particular subject appearing on Wikipedia. If WMF wishes to encourage new users, perhaps conduct research into what attracts productive users compared to what attracts disruptive or unhelpful users, and then work on attracting productive users while discouraging unproductive users. It seems to me, again purely anecdotally, that directing new users to go through an approved article creation procedure is likely to attract, develop and retain the sort of editor we want, while discouraging the sort of editor we don't want. SilkTork <sup style="color:#347C2C;">✔Tea time 08:53, 11 August 2017 (UTC)
* I'm not sure that I can agree with the implicit idea that only long-term users are desirable. However, you may be interested in a quick check that I did: The first (undeleted) edit for three of the current 22 bureaucrats was creating an article in the mainspace. Adding internal or external links (including adding a line to WP:Build the web to the linked article) was the most common first edit, and a couple fixed typos or similar small errors. Only two made major changes to an article. Two created their user pages, one moved a page (back then, you didn't have to be autoconfirmed to do that), one warned a spammer, one voted in a discussion, one expressed an opinion about a merge proposal on a talk page, and the other inserted an image to an article. So if you assume that bureaucrats are "productive, long-term users", then the answer seems to be: they did almost everything for their first edit.
* There has been some research into the effect of sandboxes and draft space. Someone involved in that project will have more information, but the TLDR seems to be "Draftspace is where articles (and their creators) go do die". WhatamIdoing (talk) 22:11, 11 August 2017 (UTC)
* Oppose, Whether via Edit-a-thons or not, articles created by non-autoconfirmed editors should go through AfC, or draft-to-AfC. Softlavender (talk) 22:29, 9 August 2017 (UTC)
* Support Trim the list by all means, but this will help the trial not be skewed.L3X1 (distænt write) )evidence( 22:58, 9 August 2017 (UTC)
* Oppose - in my opinion, Edit-a-thons ought to focus on editing instead of article creation, especially if the editors are so inexperienced that they are not even autoconfirmed. And I think the ability to add a user right necessitates the ability to remove that user right, which this proposal does not address.--John Cline (talk) 23:40, 9 August 2017 (UTC)
* Support for a number of reasons - if the purpose of opposing is to force new people into AFC/Draft process thats is nothing but a power trip to many of the reviewers with expectations of content being GA/FP ready. I always encourage new editors to ignore that process, just we did when we started editing its a learning curve becuase its almost certain negative experience. The big issues at editathons isnt so much the creation of new articles but rather that every edit the user gets a captcha thats really unproductive especially as new editors in a workshop are being supervised anyway. There is already a limit on the number of accounts an IP can create so generally need an account creator or an admin, having run workshops for most of the last 10 years as an admin I actually prefer to edit user rights as auto confirmed so that I can capture the new editors usernames and monitor post event whether they return, what issues they run into, review their edits, and generally keep in contact. Gnangarra 00:24, 10 August 2017 (UTC)
* The captcha argument is the most convincing argument I've seen here (as it really is very disruptive to new users at meetups). AfC also does sometimes require far too much of new articles. However, the arguments that this change would undermine ACTRIAL, as well as the fact that there are so many users that currently have account creator rights that clearly shouldn't have the ability to do what is proposed here are stopping me from changing my !vote. — InsertCleverPhraseHere (or here) 18:40, 10 August 2017 (UTC)
* Oppose On the theory that the current system works reasonably well. If an editor feels that the confirmed right is needed, it can be requested through an admin at WP:PERM. Dolotta (talk) 00:33, 10 August 2017 (UTC)
* Oppose during ACTRIAL, Support a trial run afterwards if we decide to go forward with ACTRIAL changes. One experiment at a time, please. <b style="color:#da0000;">Daß</b>   <b style="color:#0044c3;">Wölf</b> 01:29, 10 August 2017 (UTC)
* Oppose as proposed. has presented a number of reasons. In brief, too much chance of trouble that will be hard and/or long to undo. Let them create in draftspace. — No stance on experimenting in a more controlled and limited way. --Thnidu (talk) 04:56, 10 August 2017 (UTC)
* Oppose Per . Way too many users with the ACC flag, in my opinion, that list needs to be pruned by about 300 users and a vetting process for the flag needs to be hammered out. - FlightTime ( open channel ) 07:10, 10 August 2017 (UTC)
* Oppose I'm generally uncomfortable with tool unbundling, but this is just a bad idea. As many people above me have stated, giving relatively new editors (and yes, we do hand out Account Creator to almost new accounts who are perhaps running an editathon) the ability to not only bypass ACTRIAL themselves, but to allow the rest of their group to do it too. I also fail to see how articles created at these events are automatically legitimate new article[s] - does being at an editathon just magically make you an experienced editor? There's the implied understanding that perhaps these participants have been given training, but that's entirely down to the organisers. -- There'sNoTime (to explain) 07:35, 10 August 2017 (UTC)
* Oppose per Xaosflux, Kudpung, Sitush, SilkTork and others. Callanecc (talk • contribs • logs) 08:46, 10 August 2017 (UTC)
* Oppose per Swarm and several others. I can add that I took a quick look at the 50 or so first names on the list of users with the "account creator" right, and found a whole bunch of users who aren't even autoconfirmed themselves (several of them have only two or three edits of their own...), but would still be given the right to autoconfirm other users if this proposal passes... - Tom | Thomas.W talk 17:22, 10 August 2017 (UTC)
* Worth mentioning that they could autoconfirm themselves and any socks they wanted to create (should they not actually be running an editathon shock horror ) -- There'sNoTime (to explain) 17:37, 10 August 2017 (UTC)
* Oppose As per and many others. We must continue to encourage the fact that anyone can edit Wikipedia, but we must be cognizant that not everyone can simply jump in without learning policies and processes. High quality standards have taken years of collaborative effort to create and changing this will undermine a lot of that effort. Spacini (talk) 18:13, 10 August 2017 (UTC)
* Oppose per Kudpung amongst others. (((The Quixotic Potato))) (talk) 19:29, 10 August 2017 (UTC)
* Oppose I'm not so enthusiastic about the qualities of newly created articles by non-confirmed users. — JudeccaXIII (talk) 19:50, 10 August 2017 (UTC)
* Oppose per way up above. If anything, this flag needs to be tightened, not loosened in any way. GenQuest "Talk to Me" 21:41, 10 August 2017 (UTC)
* Oppose - My reasoning is the same as many of the other editors on this page. All Wikipedians should go through the same processes when joining the website, regardless of the circumstance. The drafting process, in addition to vetting some of the more incomprehensible work that's produced, can serve as an important teaching moment for newer users. Those who are committed to collaborating on Wikipedia will hopefully have the patience to learn from that experience. The only real problem I see here is that new editors unable to directly publish their work might feel discouraged (like they aren't truly editing the encyclopedia "anyone can edit") from the onset and never bother sticking around. But if an editor is committed and goes through with the processes they will almost certainly come out of it more competent than their peers. So I say its worth it if we break a few eggs if that keeps the one-time contributors with their "drive-by" articles under proper supervision. Lastly, I think that this proposal would undermine ACTRIAL and its effects, which would by extension undermine the research that's to be conducted. -Indy beetle (talk) 06:54, 11 August 2017 (UTC)
* Oppose. My early thought on this were to support, but I declined to comment for a few days until some of the arguments for and against had been brought up. Now that I read them I'm swayed the other way. Optimist on the run (talk) 09:54, 11 August 2017 (UTC)
* Oppose - As per Swarm, I do not think it is a good idea. Adityavagarwal (talk) 12:52, 11 August 2017 (UTC)
* Oppose - As per SilkTork, in addition I feel that this proposal would undermine the research that is being conducted with regards to ACTRIAL -- Imminent 77 (talk) 13:45, 11 August 2017 (UTC)
* Oppose - Per many others, allowing many new editors to obtain confirmed status is a dangerous prospect. Edithons are a good thing, but they also overload editors like myself that cruise the new page feed. Diverting traffic through our existing system of drafts is the best way to do things. SamHolt6 (talk) 16:54, 11 August 2017 (UTC)
* Oppose - encouraging new editors to jump into creation causes more problems than it solves. I am a case in point. Let them cut their teeth on the million plus articles that have problems, so they don't create more. Rhadow (talk) 19:44, 11 August 2017 (UTC)
* Oppose per many editors here (too many to name) - If newbies want to create articles we have drafts which is more than sufficient - I see no valid reason as to why we should allow account creators to go on a mass-adding spree especially when most (judging by the link by Xaosflux) shouldn't even be account creators anyway!. – Davey 2010 Talk 21:43, 11 August 2017 (UTC)
* Oppose: it would be a big security risk, especially as many of the account creators are inactive. Esquivalience (talk) 22:34, 12 August 2017 (UTC)
* Support as a temporary change during ACTRIAL: This will be a major help during edit-a-thons, which are already guided environments. Sayan rc (talk) 13:57, 13 August 2017 (UTC)
* The right to auto-confirm other users, and even themselves and whatever socks they might create, isn't a temporary right connected to a certain event, so it wouldn't be limited to just whatever edit-a-thon they were to take part in but would be a "full-time" right that they can use as they want, whenever they want to, and would also be given to several hundred existing user accounts that haven't been screened at all... - Tom | Thomas.W talk 14:16, 13 August 2017 (UTC)
* oppose new editors should put articles through AfC - there is no shame in that, and there appears to be an underlying assumption that there is. Doing that does not harm editathons in any way, and actually helps teach new users to respect that they are new and learning and that it takes time to understand the policies and guidelines that allow WP articles to realize the mission of providing high quality articles summarizing accepted knowledge to the public. There is a learning curve. Not impossible to travel up, but there.
* On a further note, once permissions are given it is often very hard to take them back, and i do not think it is wise to add this particular permission to this particular class of users.
* A better way to manage the trial, if an editathon organizer really wants to give participants the immediate gratification of seeing their work published, would be to recruit independent article reviewers to participate in real time, which also would be helpful in teaching new users how to interact with independent community members. Jytdog (talk) 18:54, 13 August 2017 (UTC)
* Oppose: It doesn't help as it can be workaround. I think we can work out a better measure to support edits. Also could be harmful for less developed Wikipedias in other languages take this action. MaoGo (talk) 16:06, 14 August 2017 (UTC)
* Comment Support: Does this proposal affect the 500/30 rule? If so, I'm against it because it is not fair to allow some but not all people to circumvent that process. Otherwise, I'm in favor. ImTheIP (talk) 18:14, 14 August 2017 (UTC)
* no, this would not allow adding "extended confirmed". It would allow bypassing the "10/4" autoconfirmed period only. — xaosflux Talk 02:23, 15 August 2017 (UTC)
* Comment I think all of the opposed (and my currently ambivalent self) would feel better if this "trial period" (as others have suggested) is transparent to confirmed users without account creation rights. Apologies for my prepossession if it already is. :/--<small style="font: 13px Courier New">Monochrome _ <small style="font: 13px Courier New">Monitor 19:59, 14 August 2017 (UTC)
* For reference, here's a histogram of account creators by age and edit count. As stated above, I can't support this right when this chart looks like this. en.wp account creator stats August 2017.png – Train2104 (t • c) 23:40, 14 August 2017 (UTC)
* How do people with less than 100 edits get creation rights? That histogram is very concerning. It's quite the opposite of a normal distribution.--<small style="font: 13px Courier New">Monochrome _ <small style="font: 13px Courier New">Monitor 01:36, 15 August 2017 (UTC)
* in short: this permission is given out a few basic ways: (a) For editors actively working in the WP:ACC program, (b) For editors doing work in the Education program, (c) By request (typically short term for specific events) at WP:PERM, and (d) Ad-hoc by any admin, presumably in support of general community standards. If the standards need better definition or a change, a discussion for what works best may be needed. — xaosflux Talk 10:59, 15 August 2017 (UTC)
* Support. This is more than about the drafts process. The purpose of autoconfirmed is to filter out potential abuse from newly registered accounts, mainly socking. Confirmed / autoconfirmed merely means "based on personal acquaintance or track record, we trust that this account is operated by a well-meaning human being". As an admin who regularly grants confirmed status at editathons so new editors can move pages and edit semi-protected pages, I am persuaded that if a user is trusted enough to be given accountcreator rights, they should be trusted enough to give new users confirmed rights. If this opens up the possibility of demoting accountcreators, well, that means the system worked. Deryck C. 11:06, 15 August 2017 (UTC)
* Comment The ability to grant confirmed status to a new user during edit-a-thons and similar events could be helpful, if in the right hands. I have been watching this for a while, and Deryck finally convinced me that it could work. My previous main concern was the potential abuse of this privilege by inexperienced users (such as myself) that happen to have been granted this option. The user group in question, that of account creators, is a fairly small one. Yet its impact is quite large, and apparently a large portion of current account creators may not be trustworthy with this proposed ability. I apologise beforehand if the following question has been brought up and turned down before, but why not create a new user group: "account confirmers", with stricter criteria for acceptance? Inatan (talk) 17:51, 15 August 2017 (UTC)
* Oppose: Creators of new articles should be experienced Wikipedians. I am suspicious about edithons anyway. Zezen (talk) 22:33, 15 August 2017 (UTC)
Implement Highlight, Underline, Note, and "share notes" features into Wikipedia.
Implement a highlighting, underlining, and notes feature into Wikipedia.
All changes and uses of these features will be completely unique to every account unless a "share notes" button was added.
Imagine the possibilities of adding these features. Usage of Wikipedia will go up Time management will go up Literacy will go up Efficiency will go up The Learning Curve will dwindle
These 3 features and the "share notes" feature will be great tools for college students and professors, and essentially everyone because it will make learning that much quicker
My general proposal of this will be the follow; Add a Highlighting feature Add a Underlining feature Add a note/comment feature Add a "share notes (highlights, underlines, notes)" feature to other users
And if a page gets updated or a pice of information is removed on a page and you highlighted that part, it will give you a prompt saying "This edit has been changed. Will you like you review it?", something of this nature.
I do a ton of reading on Wikipedia and enjoy learning, and this is certainly a feature that is missing in my life and certainly millions of other users as well. — Preceding unsigned comment added by Aviartm (talk • contribs) 15:47, 11 August 2017 (UTC)
* The ability to highlight text Template:Highlight already exists but I don't recall it being used often.--<IP_ADDRESS> (talk) 23:07, 13 August 2017 (UTC)
* This seems to be more about implementing notetaking features into Wikipedia, rather than strictly text formatting options. I weak support it due to these being cool features that can be potentially helpful in some situations, but I wonder about the overall usefulness of such added features, and how they would even be implemented. I think some more thought needs to be given into how how these features will be implemented, and into the actual, concrete problems and situations this will be useful in. The original proposal seems to be trying to advertise these features, rather than simply proposing them. JaykeBird (talk) 06:57, 14 August 2017 (UTC)
* I'd oppose increasing "private storage" areas - how and by who would they be policed? — xaosflux Talk 02:24, 15 August 2017 (UTC)
* Oppose - I see little value in this use of developer's time and system storage space for all the notes that no one will ever read. Beyond My Ken (talk) 01:52, 16 August 2017 (UTC)
Reviving WP:WikiProject Neutrality
I've been looking at the Articles with a promotional tone category, and it worries me that it keeps rising in article count month after month. While the Neutral point of view Noticeboard is useful for situations where neutrality is unclear or debated, in many situations it is obvious that an article is promotional, with some articles remaining promotional for over 9 years. I believe that promotional articles are one of the worst problems on Wikipedia, as companies or individuals take advantage of the influence of Wikipedia to promote themselves. I believe that if promotional articles had a similar WikiProject to the Guild of Copy Editors, the number of promotional articles would begin to go down. WikiProject Neutrality could be revived and altered to help solve the problem of promotional articles. Thoughts? CoolieCoolster (talk) 13:09, 20 August 2017 (UTC)
* I'm not sure if it's possible to muster enough manpower to deal with the increasing influx of the marketing material, let alone meaningfully reduce the backlog. I fear that the project may be fighting the windmills in absence of editing restrictions for new accounts or raised notability standards or better policing. But let's assume that it's possible. It was estimated that 30% to 40% of all new business articles were paid for. The fraction is surely higher for business articles included in CAT:PROMO, which together with borderline notable BLPs seem to dominate the category. Which raises the following questions:
* Is it ethical to ask volunteers to work on articles created by paid editors instead of articles about more notable subjects, thus letting the market dictate what they work on? Why should they work for free instead of becoming paid editors themselves?
* I was recently approached by a person who wanted to pay me for making their article neutral so as to allow the COI tag to be removed. This is exactly what the proposed WikiProject would be doing for free.
* What message does doing their work for free send to paid editors, their clients and their potential clients?
* One undisclosed paid editing company used to advertise: Our Wikipedia veterans create or correct it in a way that [...] sticks on the wiki, even gets updated for free by the Wikipedia volunteers later on.
* That said, doing something is better than doing nothing. I would be interested in getting involved in such project with two caveats:
* It should prioritise the truly notable subjects (as opposed to articles that haven't been deleted only because some editors think that Forbes content farm and the like are reliable sources).
* It should focus on removing the promotional content rather than trying to polish the turds that most of these articles are. Many long articles will be stubified. Realistically, that's the only way to make a dent in the backlog.
* Rentier (talk) 23:19, 20 August 2017 (UTC)
* Just as there are people who enjoy fixing typos, copyediting, or stopping vandalism, I believe there must be editors out there who would be interested in helping to remove all of these promotional articles on Wikipedia. The article creation companies may say it is "free editing", but it would be "free editing" just as editors do for any other article. If a company creates an article that is not notable, then it will be taken down. If they create a promotional article, it will be made neutral. Any "free editing" would just be to update notable topics with unbiased information, just so that anyone reading those articles has up to date, neutral information on notable topics. Just like the Guild of Copy Editors has, a WikiProject like this could have events that reward editors with barnstars for significantly reducing the backlog. If we show the writers of these promotional articles and their clients that we are going to start fixing them at an even faster rate, then the clients would see that they are just wasting their money trying to have a company write an advertisement on Wikipedia for them, and some of these editing companies would go out of business. And while it may be more important to focus editing time on articles that are viewed more often and are more important, it is also important to make Wikipedia an even more reliable source by removing biased information and articles that don't belong on Wikipedia. Accepting money for making articles neutral would break the fundamental rules of editing on Wikipedia, so I think if we can come up with other ways of rewarding volunteers for their time spent improving Wikipedia and removing biased information, Wikipedia as an encyclopedia would be greatly improved. Such a project would not be keeping articles on Wikipedia that do not belong on Wikipedia, it would simply delete insufficiently notable promotional articles, and de-advertise articles that are sufficiently notable to be on Wikipedia. These editing companies tell companies that they can write positive articles about them that won't be taken down or edited, so if we can show them that that is not the case, I think it would be a major step in solving paid editing. CoolieCoolster (talk) 00:16, 21 August 2017 (UTC)
* Right now you have four main areas that are dealing with these issues: WP:COIN, WP:NPOVN, WP:NPP, and WP:SPI. Many people such as Rentier and myself are involved in several of these. There very much is an effort going on in en.Wiki to deal with advertising and spam. I agree that we need a more comprehensive look at this, but for now I think the best way forward is to work towards achievable outcomes step by step that will build a framework for a neutral and trustworthy encyclopedia. WP:ACTRIAL will hopefully be a step in that direction that will also provide us with data on other changes that we can make involving new content, much of which is not neutral. TonyBallioni (talk) 01:04, 21 August 2017 (UTC)
* I just think it would be easier for people to coordinate and discuss issues on a WikiProject instead of a noticeboard. There is currently no WikiProject dedicated to removing the backlog of promotional articles. CoolieCoolster (talk) 01:26, 21 August 2017 (UTC)
* If you want to create a disincentive for clients to pay someone to create an article for them, then I don't think fixing their articles will help. Reviving WikiProject Requested articles and making the article request process more responsive would provide an incentive to use this process instead. isaacl (talk) 02:06, 21 August 2017 (UTC)
* The kinds of companies that hire editors to make them articles don't want actual Wikipedians to be making articles for them, as no regular editor would make an article promotional enough to meet the demands of the company. The companies don't care about improving Wikipedia, they just want a permanent advertisement. And even if some companies would use the Requested Articles WikiProject, I imagine many companies would rather hire editors who professionally make corporate articles than to get one of their employees to have a long discussion with editors that will not approve of everything the company wants. CoolieCoolster (talk) 02:15, 21 August 2017 (UTC)
* Sure, but fixing their articles won't discourage them from using paid editors either, because they still get an article, jumping the queue over companies playing by the rules by submitting requests. If you really want to discourage them from hiring editors, then they can't receive an advantage from hiring someone. isaacl (talk) 02:23, 21 August 2017 (UTC)
* They will always have the advantage of having the content they want in their article when they hire editors. Fixing more of those articles won't incentivize more companies to do it, as it will simply mean that they will have a promotional article for less time than before. The kinds of companies who hire editors are different from the kinds of companies that follow the rules of Wikipedia. The ones that hire editors have no respect for the rules of Wikipedia and simply want an advertisement, while those who follow the all of the rules, for the most part, simply want their company, if it is notable enough, to be included on Wikipedia. CoolieCoolster (talk) 02:38, 21 August 2017 (UTC)
For an essay on that topic, see Buy one, get one free. It explains the concept in a fair amount of detail and I think raises a lot of good points. TonyBallioni (talk) 02:33, 21 August 2017 (UTC)
If the article is deleted instead of fixed, the promotional words will be around for even less time and a disincentive for hiring an editor will be given. Why should priority be given to those who engage in a discouraged practice over those who do not? isaacl (talk) 03:23, 21 August 2017 (UTC)
* Because sometimes articles created that way are too notable to be deleted. Although for a lot of those articles they end up just becoming stubs anyways, so for most of them it would probably just be better to delete them than fix them, which would leave them as stubs. CoolieCoolster (talk) 12:44, 21 August 2017 (UTC)
* Requested articles can be notable too; if the intent is to discourage paid editing, it would be reasonable to give them priority over preserving articles created by paid editors. That being said, I recognize there isn't a perfect answer; if editors are interested enough in fleshing out an article on a notable topic, they should be able to do so, even if the article was started by a paid editor. But if there's nothing to save from the paid editor, the article may as well be deleted and placed on the requested article queue to be dealt with in good time. isaacl (talk) 02:25, 22 August 2017 (UTC)
Lists to include number of pages
For certain lists, e.g. people born in a certain month and year, one can repeatedly click on "Next page" to find a specific entry. Would it be possible to have the page number and a little note about how many pages such lists go across, as this may make it easier to find entries?Vorbee (talk) 10:57, 21 August 2017 (UTC)
* Could you give a specific example of a page that has this situation? Depending what namespace and how it's formatted, the solution might already be doable vs substantially difficult in different ways. DMacks (talk) 16:31, 21 August 2017 (UTC)
Sorry - my mistake, I think it has already been done. I just went to the category called "1989 births" and I see it does say at the top "The following 200 pages are in this category". Vorbee (talk) 10:10, 22 August 2017 (UTC)
* Glad you are able to do what you want. "On Category:... pages" was the key detail I didn't recognize from your original question. DMacks (talk) 13:37, 22 August 2017 (UTC)
Add an option with "Show pages starting with this text" on logs
Hi. I wanted to suggest an option that has "Show pages starting with this text" in the logs because I thought that would be a useful addition. For example, you put "2017" and have that option checked. The log displays every page, deleted or not, that begins with "2017". I would find it difficult to find some log actions without this option, as you have to type in the exact page name, so that's why I'm requesting this feature. Or even better, either that or add the option of "show titles containing this text", so any article with "2017" in its name is listed. I would find this convenient. Rain drops, drop top (talk) 01:37, 21 August 2017 (UTC)
* I like this idea; it would also be helpful in finding log entries by namespace (other than mainspace). עוד מישהו Od Mishehu 10:47, 21 August 2017 (UTC)
Would this include categories?Vorbee (talk) 10:52, 21 August 2017 (UTC)
* If we can search for anything starting with the text "Category:", then we would get the categories. עוד מישהו Od Mishehu 10:53, 21 August 2017 (UTC)
Fun fact: That already exists in mediawiki, see http://social-tools.wmflabs.org/wiki/Special:Log (though it may stop working at some point). Bad news: It cannot run on Wikimedia wikis because it is inefficient see (https://phabricator.wikimedia.org/T29020). Good news: Filtering log entries by namespace is already possible, it can be done using a userscript or the api, e.g. https://en.wikipedia.org/w/api.php?action=query&format=xml&list=logevents&letype=move&lenamespace=2&lelimit=3. 21:42, 22 August 2017 (UTC)
Delay visibility of recent IP edits
Petty impulse vandalism of articles is a common pastime among certain IP visitors, such as bored schoolkids. If IP edits were not visible for the first few minutes, it would discourage a lot of this noise. Pending changes achieves something vaguely similar but carries a page-specific admin overhead and has no timeout. I therefore propose that, when an IP user edits an article:
* 1) The IP edit will not be updated in the article served to IP visitors until one of:
* 2) *A fixed time period, say ten minutes, has elapsed, or
* 3) *A logged-in editor (preferably not all bots though) subsequently updates the article.
* 4) The IP edit will continue, as now, to be immediately visible to logged-in editors.
* 5) Anybody who edits the article, even an IP editor, will see the IP altered version while editing and not necessarily the displayed version.
The second condition assumes that the logged-in editor has vetted the IP edit, and also allows their user account edit to appear immediately. Most bots cannot vet and their edits do not require visual feedback, so they are best treated the same as IP editors. However a few bots do specifically revert vandalism, so they should be treated the same as logged-in users.
The overall idea is to reduce petty vandalism while affecting genuine editing as little as possible. It will be invisible to logged-in editors. Good faith IP editors would be mildly inconvenienced by not seeing their edits immediately, but not unduly so as they will see the edited version in the page preview and can still make further improvements while waiting.
The use case really only makes much difference in main article space, but there would be little harm in implementing it on all pages, if that were easier and carried a lower processing overhead.
— Cheers, Steelpillow (Talk) 09:56, 21 August 2017 (UTC)
* One significant probelm: A good-faith anonymous user who doesn't understand that they sould use the "Preview" button, or doesn't bother to do so, will count on after-the-fact proofreading of the sentence immediately after saving; denying them this right (which you propose to do) will probably increase the amount of mistakes which persist on Wikipedia, as well as some other user, genuinely not understanding the edit, reverting it as vandalism. עוד מישהו Od Mishehu 10:46, 21 August 2017 (UTC)
* I am not sure that the immediacy of feedback to the untutored editor is a "right", that is strong language to use. I propose only that it is briefly delayed, not removed. The impact of ignorance could be lessened by adding an info banner explaining that the edit will be displayed shortly. This kind of approach is common on many commentary sites (blogs, etc) elsewhere, sometimes even with logged-in users, so it should not confuse the online citizen unduly. For example I find no problem with it on The Register forums. — Cheers, Steelpillow (Talk) 11:54, 21 August 2017 (UTC)
* Oppose vehemently Hells no. Users who have not registered accounts are not to be treated as lesser humans ever. We do not require the creation of an account for normal editing, and should never do so. We already put too many restrictions that require a registered account, and the barrier for entry to Wikipedia gets higher and higher each year, decimating our editor base. The last thing we need is another hoop for new editors to jump through. Let the IP editors fix spelling mistakes, and stop pre-judging them to be vandals, which they by-and-large are not. -- Jayron <b style="color:#090">32</b> 14:30, 21 August 2017 (UTC)
* Oppose - Wikipedia already doesn't have enough editors to fix all of its problems. We should not make it even more difficult for new people to edit Wikipedia. CoolieCoolster (talk) 14:37, 21 August 2017 (UTC)
* Strong oppose-A thousand times no! Amidst all the fanfare with vandal-edits by IPs, we miss their good and sometimes brilliant contributions.The collateral damage exceeds the benefit of such a policy by miles. Winged Blades of Godric On leave 15:44, 21 August 2017 (UTC)
* Suggest snow close. - FlightTime ( open channel ) 16:23, 21 August 2017 (UTC)
* OK, I get the "death by a thousand cuts" argument. Probably best if it is closed, then. — Cheers, Steelpillow (Talk) 18:14, 21 August 2017 (UTC)
Guideline status of WP:Recent years
Please see: Wikipedia talk:Recent years.
In a nutshell, supporters of guideline status state that consensus was already achieved at WP:VPPOL to elevate that wikiproject advice page from WP:Essay to WP:Guideline, earlier this year. Opponents observe that the proposal was not made at WP:VPPRO, and was buried at the end of a multi-part RfC about "Recent years" trivia of various sorts, where it received very little comment. That RfC was closed by one of its own !voters.
Both viewpoints (and some neutral/other ones) also, of course, have substantive reasons pro and con the page being a formal guideline. I'm "advertising" the discussion here because it's the primary venue for elevation/demotion discussions, and was left out of the original loop. The ongoing discussion is also listed in WP:CENT, so its location on the project's own talk page (a non-neutral venue, but one with a small number of regulars) is probably not much of an issue in this case. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 23:01, 23 August 2017 (UTC)
Proposal to have the Programs and Events Dashboard have an English Wikipedia interface
Hi, following consultation with course leaders at the University of Edinburgh, we are looking to see if the Programs and Events Dashboard can be brought up to the same level functionality as the Wiki Edu Dashboard. Currently the Wiki Edu Dashboard has the facility where a Course Extension-esque Wikipedia page can be automatically created at the same time as course is created on the Wiki Edu Dashboard. The Programs and Events Dashboard does not offer this and course details are kept firmly within the Programs and Events Dashboard with no in-Wikipedia interface provided. The proposal is for the Programs and Events Dashboard to be able to create a Project Page / Course Extension-like page on English Wikipedia so that any course programme would have this as standard. In short:I'm proposing to enable edits via Programs & Events Dashboard on this wiki. Once enabled, related activity for courses and other events on Programs & Events Dashboard would be reflected with wiki edits, as currently done on English Wikipedia with the Wiki Ed Dashboard. Here are the types of edits it can potentially make:
— Preceding unsigned comment added by Stinglehammer (talk • contribs) 18:13, 21 August 2017 (UTC)
* Updates to a course page, showing the list of editors and the articles they work on:
* Adding templates to user pages when the user joins a course:
* Adding templates to article talk pages to show who is working the article:
* Strong support – As one of those University of Edinburgh course managers, I would wholeheartedly love to have this facility. It is something that currently exists for educational institutions – but only if in the via the US-institution-only Wiki Edu. It is hard to encourage academic colleagues in the UK to get on board with using Wikipedia in the classroom without the flexibility of such tools to make that happen. Thanks! —Caorongjin (talk) 08:53, 22 August 2017 (UTC)
* Support I am a big supporter of the Dashboard. It is an essential tool for any Wikipedian to partner with any external expert organization, such as in a Wikimedian in Residence program. It also is essential for any Wikimedia or chapter group to fulfill its obligation to the Wikimedia Foundation when receiving any grant funding, as anyone getting funded through meta:grants:start has to make a report through meta:Learning and Evaluation/Global metrics and the dashboard is the only way to do this in 5 minutes versus 5+ hours for typical new users in typical programs. As you say, the dashboard is actually designed for schools and does this very well.
* I regret to say that the politics around developing the dashboard is tangled. I do see a path forward, and I could use your assistance. Here is my proposal for next steps -
* both of you are in the UK, and I expect that both of you have communication with Wikimedia UK. I request that you both contact that organization and see if you can negotiate organizational support for what you are proposing. Ask Wikimedia UK if it as an organization would be willing to routinely use and recommend the dashboard for all UK school outreach and perhaps all public editing events whatsoever. Please determine how much event coordinators with that group are willing to support what you are proposing.
* as a step two, please have someone at Wiki UK contact me as a member of Wiki NYC. Both NYC and the UK speak English, we share a Wikipedia, and we ought to collaborate. NYC already uses the dashboard for everything.
* The Wikimedia Foundation currently has no plans to encourage the use of the dashboard. So far as I understand, the WMF's position is that Wikimetrics is their preferred alternative tool, but I find this advice to be misguided because obviously Wikimetrics is inaccessible and obviously the Dashboard provides the same information except for a non-technical user base. The WMF moves slowly until and unless an organized group of people make a clear demand. I feel that if we could demonstrate a user base, such as commitments from two chapters, then we would be better positioned to make requests which affect the community. Personally I recommend the Dashboard for all languages, for all Wikimedia projects, and to all wiki event organizers.
* FYI - the dashboard is going to need funding for development, and probably that money should to to Wiki Education Foundation because they produced the tool. The dashboard works, but there are some situations where the math is inaccurate and especially for university and professional use, I do not want anyone putting research or their reputations on the line over software that gives data which is correct in 90% of cases but is incorrect in some common use cases. The dashboard looks great and provides data which makes people excited but it would cost less to just fix some problems than it would to document and train against its peculiar shortcomings. Perhaps funding could come directly from the WMF, perhaps it could come indirectly from the WMF but through Wiki UK and Wiki NYC, or perhaps it could come from other sources. Either money or a committed developer is required if large group of people make long term plans around this tool. Somehow, users of the tool are going to need to assign a value to the outcomes of the tool to establish a case to request development funding. $100,000 would be good for a year, $25,000 would go a long way and provide some stability and continuity to the tool's development. In my view, thousands of people discuss the data from this tool and I get really anxious about my reputation and Wikipedia's reputation when I know that people expect web applications to only work perfectly, especially in data science.
* Thanks for making the proposal. Blue Rasberry (talk) 19:10, 22 August 2017 (UTC)
* Critical suggestion: The Wiki Edu Dashboard looks prettier, but appears to provide less utility (or much of it is buried). The Programs & Events Dashboard appears to provide more functionality or at least more immediate access to the features. I would suggest a merger of the approaches, not a binary choice between them. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 16:56, 24 August 2017 (UTC)
RfC of interest
There's an RfC at WT:NOT that would change that policy, and would have wide implications for all articles relating to recent events. See https://en.wikipedia.org/wiki/Wikipedia_talk:What_Wikipedia_is_not#RFC:_New_subsection_under_.22Not_a_Newspaper.22_about_commentary Coretheapple (talk) 14:51, 25 August 2017 (UTC)
Re-ordering 'Interaction' box menu on left-hand side
Background: Noticed over the years that some new editors that hurting to create an article about the company they own or the company they work for or a band that the have just formed or their sister that has just had her first poem published.... have a desire to have the article about 'that' -to appear only. Many (most) show no willingness at all, to read though Your first article but instead go straight to a help-desk. After much guidance and a editors setting them up with a draft space etc, they still came back and say “HELP my submission is about to be deleted!!!” simply because they obviously haven't felt it necessary to read and digest the advice nor follow it – and why should they? When all they have to do is comeback to help-desk every-time when things don't go their way. Thus, requiring more editors to spend more time holding their limp hands. Result is: I don't think any of these proto-articles (of this nature) ever get into main-space due to lack of notability etc., but they absorb at lot of our time and it is a waist of time, when we could be spending it on new 'editors' that may stay if we give them some early help on the specific problems they are still having after reading and digestion WP's written and comprehensive guidance. Proposal: Suggest we move 'Help' down to the bottom of the menu and replace it with 'Howto create an article' at the top. This can be a link to Your first article. Not only will it send single purpose accounts there first but if they turn up on 'Help' later, having a problem, of not so much comprehension but having obviously not having bothered to really read it, we can simply refer them back to Howto create an article. It is pretty easy to distinguish newbies who have come here to contribute from those that are just here to promote. So, don't see a deep policy objection here, rather more of a streamlining. HelpDesk is a help-desk not a kindergarten for single purpose accounts who are here to-day and will be gone tomorrow. Aspro (talk) 17:50, 22 August 2017 (UTC)
* Half-support: We should add something like "How to create an article", but this does not require moving or removing the "Help" link. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 23:04, 23 August 2017 (UTC)
The OP just explained why WP:ACTRIAL is so useful Legacypac (talk) 00:36, 27 August 2017 (UTC)
Bot to move superscript/subscript pages to their correct location
Unicode superscripts and subscripts cause several accessibility and display issues.
This is a proposal to For a practical examples of where this is done, see Vitamin B6, Golem100, 12e Régiment blindé du Canada, Aice5, or Tommy heavenly6 discography.
* mass-move pages with unicode super/subscript in their titles to their non-unicode version (e.g. move Foo²bar to Foo2bar)
* add the appropriate displaytitle key to the new page (e.g. ) so "Foo²bar" is displayed as "Foo2bar"
* update the main text (e.g. change to in the article)
This has several advantages
* Accessibility issues: Most screen readers will not be able to handle titles such as Gen¹³ (normally pronounced 'Gen thirteen'), pronouncing either 'Gen-supercript one-superscript three' or 'Gen-superscript one-cubed'. Modern screen readers would handle Gen13 as 'Gen-superscript 13'.
* Several characters lack corresponding unicode superscript/subscripts.
* Consistency in how we present our articles. Over 2000 pages correctly display the superscripts/subscripts. About 120 don't.
* MOS compliance. See Manual of Style/Superscripts and subscripts (which failed because the information was elsewhere / didn't need its own page, not because the information was disputed) Manual_of_Style/Mathematics and also. There is also MOS:UNITSYMBOLS.
* Easier to find/search engine friendly. Someone looking for INXS²: The Remixes will type INXS2: The Remixes.
* Non-unicode superscripts/subscripts read way better and have wider font support
The list of affected pages would be
Articles
* (ISC)²
* 101²
* ABCD² score
* AM²
* America³
* America³ (1992 yacht)
* Atm⁵
* A² Records
* A¹ homotopy theory
* Book:E=MC² (Mariah Carey album)
* Carl²
* Chhut-thâu-thiⁿ
* Counterfeit²
* DNA²
* Don Omar Presents MTO²: New Generation
* E=MC² (Giorgio Moroder album)
* E=MC² (Mariah Carey album)
* E²
* E² (album)
* GA²LEN
* Gen¹³
* Gen¹³ (film)
* Gen¹³/Monkeyman and O'Brien
* Heavy Metal: F.A.K.K.²
* Hi-Teknology²: The Chip
* INXS²: The Remixes
* I²C
* I²S
* J²
* K² (band)
* Live at the O² Arena
* L²
* L² cohomology
* MAC³PARK Stadion
* MD² International
* Magnavox Odyssey²
* Mercedes-Benz G500 4×4²
* Me²
* M²
* M² (album)
* PC²
* Rite²
* SGI Indigo² and Challenge M
* SR² Motorsports
* Sailing at the 1920 Summer Olympics – 30m² Skerry cruiser
* Sailing at the 1920 Summer Olympics – 40m² Skerry cruiser
* Sailing at the 1956 Summer Olympics – 12m² Sharpie
* Secretory Pathway Ca²⁺ ATPase
* Stella Women’s Academy, High School Division Class C³
* V-Partei³
* Why Does E=mc²?
* Zeit²
* Z² (album)
(I'd exclude Chhut-thâu-thiⁿ from the bot however, since this might be a grammar specific thing. Likewise for and 101², which would clash with 1012. I'd make a formal WP:RM for either of those.)
Categories
* Category:(ISC)²
* Category:12m² Sharpie
* Category:12m² Sharpie class Olympic sailors
* Category:12m² Sharpie class sailors
* Category:30m² Skerry cruiser class Olympic sailors
* Category:30m² Skerry cruiser class sailors
* Category:40m² Skerry cruiser class Olympic sailors
* Category:40m² Skerry cruiser class sailors
* Category:40m² Skerry cruisers
* Category:Gen¹³ and DV8 characters
* Category:Suspected Wikipedia sockpuppets of Eep²
(I'd exclude Category:Suspected Wikipedia sockpuppets of Eep² from the bot however, since the user was User:Eep² and no readers would come across it anyway.)
* I would just delete that ten-year-old sockpuppet category. It serves no real purpose now. bd2412 T 15:05, 25 August 2017 (UTC)
Files
* File:Carl².png
* File:Counterfeit².jpg
* File:E=MC² 1.png
* File:E=MC² cover.jpeg
* File:Gen¹³ FilmPoster.jpeg
* File:Gen¹³ vol. 2 6 Coverart.jpg
* File:I²C bus logo.svg
* File:Me² (Red Dwarf).jpg
* File:SABIN【420 stoⁿer】.jpeg
* File:Sini Sabotage - 22 m².jpg
* File:Why Does Emc².jpg
Templates
* Template:Footer Olympic Champions 30m² Skerry cruiser
* Template:Footer Olympic Champions 40m² Skerry cruiser
* Template:S³ University Alliance
* Template:The EMC² Barnstar
Discussion
Personally, I'd support moving everything, but files and templates don't really need to be. Starting the discussion to see what the support is for this. Headbomb {t · c · p · b} 11:57, 16 August 2017 (UTC)
* I have made previous comments at Bot requests. --Izno (talk) 12:32, 16 August 2017 (UTC)
* I'd support this in full: screen readers have very variable unicode support, and having something closer to plain text would be almost always an improvement in the experience of readers using assistive technology. I've taken the liberty of changing the pseudo-headings above to real headings in the interest of accessibility. --RexxS (talk) 20:48, 16 August 2017 (UTC)
* Oppose mass bot moves. Only 101 titles are listed above. They can be evaluated manually, and some should have navbox updates if they are moved (to make the bold selflink feature work). DISPLAYTITLE only works on the page itself, not in categories, search results and so on. The mentioned guidelines are about article content and don't consider this limitation in page names. If a sub/superscript is usually ignored in pronunciation then dropping it is usually acceptable, but if a superscript means a power like a square then it's pronounced differently and looks confusing without it. We should consider the common plain text notation "^2", like moving 12m² Sharpie to 12m^2 Sharpie or 12 m^2 Sharpie instead of the cryptic 12m2 Sharpie. The "^" character can be hidden by DISPLAYTITLE with positioning like Kalai's 3^d conjecture at Template:DISPLAYTITLE. I don't know how screen readers pronounce "^" but I guess their users are used to it meaning a power. There are other special cases like 101² which might be moved to 101 Vol. 2 like some sources call it. 1012 would be strange (and is taken by the year). PrimeHunter (talk) 22:59, 16 August 2017 (UTC)
* Here is where we ought to evaluate them. 12m2 Sharpie is not 'cryptic', because that's not how people would see it. They would see it as 12m2 Sharpie. The only place you would see 12m2 Sharpie is in the edit window, and is no more unclear than seeing '5-HT2C receptor' in the edit window, rather than '5-HT2C receptor' (which cannot be rendered with unicode subscripts). 101² may required some additional thought however, but moving to Highway 101, Vol. 2 or similar would likely be the correct solution to that one. Headbomb {t · c · p · b} 13:44, 17 August 2017 (UTC)
* I've gone and done the move to 12 m2 Sharpie, so you can see the difference it makes in practice. Headbomb {t · c · p · b} 22:51, 20 August 2017 (UTC)
* I've gone and done the move to 12 m2 Sharpie, so you can see the difference it makes in practice. Headbomb {t · c · p · b} 22:51, 20 August 2017 (UTC)
* Oppose moves by a bot, the number of items involved is quite small per PrimeHunter, and each article/category requires individual review. Templates and files, whose names aren't exactly reader-facing, should definitely not have these characters in them (they have to be typed by editors). FYI, I've sent one of the files to FFD. – Train2104 (t • c) 23:55, 16 August 2017 (UTC)
* Why oppose those moves by a bot? Are there any listed above that should not be moved, beyond the few I've already mentionned? If so, we can just exclude those, and let the bot perform these rather tedious things for us. Headbomb {t · c · p · b} 02:44, 17 August 2017 (UTC)
* Do not use a bot, and do not rename files or templates for this reason. Files or template names will not be read by screen readers. And why can't screen readers be updated to include more unicode characters like this? Superscripts have been there for a long time now. Anyway there may be reasons to rename apart from this. Windows 10 Narrator reads these correctly as "superscript 2" or even "square meters". Windows 10 narrator does not handle the ^2 as well as ² so please don't change this to ^2. So screen readers are not a good reason the alter these. Graeme Bartlett (talk) 00:36, 17 August 2017 (UTC)
* The reason mostly is because unicode superscripts/subscripts are pretty much deprecated everywhere, and are an incomplete set. undefined and undefined tags support all characters, so that's what people use. There's no effort to improve unicode subscript support, because it's an incomplete character set, and the effort required to improve it would duplicate the existing solution by doubling the unicode character sets, and then somehow develop an alrorithm that could parse ₕₑₗₗₒ as 'subscript hello'. And update thousands of fonts to line up and kern subscripts/superscript characters. Headbomb {t · c · p · b} 14:06, 17 August 2017 (UTC)
* I support this in principle, as a relatively minor and handy improvement. However, I'm really not in a position to look into this in great detail ... except to reply to the points by Graeme Bartlett that Windows Narrator is not widely used as a screen reader by blind people, screen reader makers have enough trouble updating their products to work with new software versions rather than thinking about Unicode characters, and file names can sometimes be read by screen readers because of the way Wikipedia's image syntax works (as most images are linked and have no alt text). Graham 87 02:38, 17 August 2017 (UTC)
* Support I don't care what tools you use (bot or manual), end result is what matters. Not sure what the issues are with template and files, but I would support the Articles anyway if had to narrow the choice. -- Green C 03:11, 17 August 2017 (UTC)
* Support, after giving users a reasonable amount of time to review trhese lists and request individual exclusions. עוד מישהו Od Mishehu 19:44, 17 August 2017 (UTC)
* Oppose. Use redirects instead. KMF (talk) 22:42, 20 August 2017 (UTC)
* I'm not sure you understand what is being proposed here. Moving the pages will create redirects automatically. Headbomb {t · c · p · b} 22:48, 20 August 2017 (UTC)
* Support getting it done. Neutral leaning oppose on bot method; I tend to trust the objections of the bot-experienced when they say the number of affected articles is too small, and the amount of manual review needed too high, for that method to be practical. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 23:13, 23 August 2017 (UTC)
* I am bot-experienced, and the amount of manual review for this is pretty small, and would mostly amount to deciding 'should this page be moved' or not. This would require a series of ~300 edits [150 moves, with 150 follow up maintext updates, with corresponding edit summaries for each]. This cannot easily be easily performed automatically/semi-automatically. If it's worth anything to you, I plan on personally reviewed each of the bot's edit after the fact [probably would take 10 minutes to review it all]. This likely would save me over 4 hours of work. Headbomb {t · c · p · b} 03:06, 24 August 2017 (UTC)
* I've done AWB runs over more pages than that, in less time than we've been discussing this. :-) — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 03:08, 25 August 2017 (UTC)
* Yes, but you can't move pages with AWB. Headbomb {t · c · p · b} 14:19, 25 August 2017 (UTC)
* Actually, yes you can. There's a working "Move" button on the "Start" screen, right next to the "Watch" button. bd2412 T 14:27, 25 August 2017 (UTC)
* A button which is disabled and can't be used. Headbomb {t · c · p · b} 14:35, 25 August 2017 (UTC)
* It may be disabled based on the permission level of the user. I just used it to move all 21 of the lists of political and geographic subdivisions from titles ending in "km²" to titles ending in "square kilometers". bd2412 T 14:39, 25 August 2017 (UTC)
* Well, if someone's willing to do the work manually, certainly I'm not going to object to it. Headbomb {t · c · p · b} 14:52, 25 August 2017 (UTC)
* However, you did seem to have forgotten to move the talk pages. Headbomb {t · c · p · b} 14:54, 25 August 2017 (UTC)
* If you look at my edit history, you will see that all of the talk pages were moved along with the articles. What is left are talk page redirects. bd2412 T 14:59, 25 August 2017 (UTC)
* I think one was missed. It just so happened to be the one I randomly looked at. Anyway, all fine now. Headbomb {t · c · p · b} 15:08, 25 August 2017 (UTC)
* Yes, I probably missed one. The interface requires clicking an additional field to also move the talk page. I would prefer to have the talk page moved by default. bd2412 T 15:12, 25 August 2017 (UTC)
* There's Javascript for that; I have it in User:SMcCandlish/common.js, second code block. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 21:00, 28 August 2017 (UTC)
WP:INFOCOL
Attempting infobox merger is a tedious and time consuming process. What adds to the difficulties is the strong opposition faced from Wikipedians with absurd reasons. I liked the WP:INFOCOL, but it's a mere essay. Can a guideline or policy be framed regarding infobox consolidation listing conditions qualifying for merger or converting to wrappers? -- Pankaj Jain Capankajsmilyo (talk · contribs · [//tools.wmflabs.org/xtools-ec/?user=Capankajsmilyo&project=en.wikipedia.org count]) 13:44, 28 August 2017 (UTC)
* This has already been brought up at Village pump (policy). – Uanfala 22:06, 28 August 2017 (UTC)
Add the Logged in Protection level
Create Logged-in Protection level, which only allows any registered user to edit. Newly-registered users will be able to edit pages with this level. If there is high vandalism from IPs, use logged-in protection. If there is severe vandalism from IPs or any high vandalism from new users, use semi-protection. However, users can request it if the vandalism came from IPs. Please do it. It will use the "Permission=Require registered editor access" text when a page is protected with this level.. For example: "Protected "Page" Persistent vandalism [Edit=Require registered editor access] (indefinite) [Move=Require registered editor access] (indefinite)". 2600:387:9:3:0:0:0:C5 (talk) 10:47, 28 August 2017 (UTC)
* Why do you believe semi-protection is insufficient for this case? --Izno (talk) 13:12, 28 August 2017 (UTC)
* Oppose. This is the whole point of semi. (As a side note, I vaguely recall a sockpuppetry case where an editor continuously recommended new protection levels, including inserting new padlock color symbols in their proposals. Does anyone else recall that and remember the name?) ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 15:23, 28 August 2017 (UTC)
* The creator of this thread is a sock of User:Maleidys Perez, using an IP on this formerly blocked range. -- Ajraddatz (talk) 17:44, 28 August 2017 (UTC)
* Support. So after creating an account, I won't have to wait until autoconfirmation. Please do not deny. Approve. 2600:387:9:3:0:0:0:B4 (talk) 20:42, 28 August 2017 (UTC)
* I can't wait to see what happens after this level is added. But HOW can someone edit the protection interface? 2600:387:9:3:0:0:0:B4 (talk) 20:44, 28 August 2017 (UTC)
Sorry Button
I say we need a sorry button like the thank button but if you make a mistake you can apologize!
* Please read WP:Bug reports and feature requests. עוד מישהו Od Mishehu 03:33, 3 September 2017 (UTC)
* A user talk page post is much more meaningful and more apt to be taken as sincere. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 08:59, 5 September 2017 (UTC)
Automatic R2
I propose that R from move, which is automatically added to all moves, be modified to transclude db-r2 when located in mainspace and the target is located outside the Main/Template/Category/WP/Portal spaces. We already allow page movers to suppress redirects when making these moves (WP:PM/C). I don't see the benefit of having others' moves leave redirects that then have to be cleaned up, and as far as I can tell, there are no valid reasons for keeping such redirects. See R from move/sandbox for a draft implementation. – Train2104 (t • c) 21:26, 26 August 2017 (UTC)
* The template R from move would need to know where a page redirects. If it is placed above the #redirect call, that is not possible. If it is placed below, it might be possible in Lua (but not in Template script), but I'm not sure the MediaWiki API knows where a page redirects on the redirect page. --Izno (talk) 21:30, 26 August 2017 (UTC)
* It's placed beneath the redirect by MediaWiki:Move-redirect-text, and Module:Redirect provides the functionality. For testing purposes I changed the conditional to check for userspace and used db-g7 instead of db-r2, since the latter does not display outside mainspace. Test It works, except that speedy template looks really strange. – Train2104 (t • c) 21:48, 26 August 2017 (UTC)
* Can someone familiar with the R-tag templates tell me why the CSD tag looks so strange in there? perhaps? – Train2104 (t • c) 23:40, 26 August 2017 (UTC)
* Thank you very much for the ping, Train2104! I think the reason some of the text is outside and above the main display has something to do with the fact that the outside text is generated by the meta template used by db-g7. That template, db-meta, uses the Mbox template, which can be interfered with by HTML Tidy when not correctly positioned on a page. In this case, the G7 template should go at the TOP, the very top of a page. Place it anywhere else on a page, as the R from move/sandbox does, and HTML Tidy may cause the template to appear in an abnormal and unexpected manner when saved.
* We should also note that page movers are given the suppress-redirect tool specifically to perform round-robin page swaps. The redirect is suppressed only to make way to move another page into that title. Page movers are warned that to suppress a redirect under any other circumstances should be done only very carefully and selectively to prevent breaking links both on and off Wikipedia. Paine Ellsworth put'r there 00:48, 27 August 2017 (UTC)
* Fixed it by putting it on top of the message. I've seen many cases of CSD buried under redirect and they looked fine, unfortunately we can't automatically place it on top of the page (unless a bot is involved). Thanks for the hint to look into positioning! – Train2104 (t • c) 01:43, 27 August 2017 (UTC)
* Yes, I thought about that possibility several hours after I posted the above. The important thing with the Mbox and HTML Tidy is that the template should be at the start of its own line (not necessarily at the TOP of the page). I'm glad you tried that and that it worked. Yet I'm still a bit concerned over the "automatic" addition of any Db template. Seems to me it could quickly grow to be a migraine for admins. Paine Ellsworth put'r there 06:17, 28 August 2017 (UTC)
* Support if possible. If it is easy to implement this with existing tools, I don't see how this would not be an improvement. Even in cases where you mean to redirect the page to something else in mainspace afterwards, blanking the R2CSD when doing so is easy enough and doesn't add an extra step. — InsertCleverPhraseHere (or here) 23:09, 26 August 2017 (UTC)
* Oppose WP:RDRAFT says this should not be done and provides a justification. Thincat (talk) 13:49, 1 September 2017 (UTC)
* RDRAFT is about pages that were moved from the Draft: namespace to the main namespace. This proposal is about the reverse. —Cryptic 16:42, 1 September 2017 (UTC)
* My oppose struck, thank you. Thincat (talk) 16:47, 1 September 2017 (UTC)
* Comment WP:R2 says "If the redirect was the result of a page move, consider waiting a day or two before deleting the redirect." so this places the onus for the delay on the admin, not the tagger. Perhaps that is what is meant anyway. Can a warning to the admin be placed in some way? Thincat (talk) 16:56, 1 September 2017 (UTC)
* My comment struck because db-r2 already provides a warning. Thincat (talk) 17:02, 1 September 2017 (UTC)
* Oppose. I've decided to oppose this suggestion. This proposal seems unnecessary since admins and page movers are supposed to suppress mainspace redirects to other namespaces. Paine Ellsworth put'r there 09:47, 3 September 2017 (UTC)
* Um... I'm pretty sure that this proposal meant to apply specifically to moves made by non page movers and admins (which together make up a very small fraction of total editors). I thought it was implied that moves made by page movers and admins would be suppressed (if checked) and moves made without suppression (i.e. by others) would be tagged for R2 if directed to draft space. Presumably that would also tag redirects created by page movers or admins that forgot to suppress, but that is still better than leaving these cross namespace redirects in place. — InsertCleverPhraseHere (or here) 11:11, 3 September 2017 (UTC)
* As you noted, there are a very small number of editors to whom this might apply. And WP:R2 covers the deletion of redirects from page moves that are not needed. It also states: "If the redirect was the result of a page move, consider waiting a day or two before deleting the redirect." To me, this means for non-page movers to refrain from even applying db-r2 for "a day or two", which goes counter to this proposal that would apply the SD template immediately. To address "...that would also tag redirects created by page movers or admins that forgot to suppress..." That is not really a good reason for such changes. IMHO, we should not make sweeping changes just to try to make up for editorial mistakes. A better solution would be to educate editors. We might want to consider an edifying addition to WP:MOVE where needed. Paine Ellsworth put'r there 22:27, 3 September 2017 (UTC)
* I think you misunderstand me. this change would affect and improve the experience of all of the other editors (the large group), not admins or page movers (the small group). For page movers and admins, this change would likely have no effect at all, as those users generally suppress redirects anyway (again unless they forget, in which case this change would be a bonus improvement to them as well). The R2 statement about deleting the redirect is about when to delete the redirect after the redirect has been tagged (i.e. it does not say "consider waiting a day or two before tagging the redirect for deletion." it says "before deleting the redirect") This isn't about making up for editorial mistakes, it is about making the lives of normal editors who do not have redirect suppression privileges easier by autotagging redirects from mainspace to draftspace. dbR2 should always be applied to the redirect in these cases, so there is no reason not to make the process automatic and remove a trivial step (none that I am aware of anyway, feel free to enlighten me). — InsertCleverPhraseHere (or here) 23:07, 3 September 2017 (UTC)
* First enlighten me. You said "this change would affect and improve the experience of all of the other editors (the large group)". So just how large is this "large group" of editors that move unready mainspace pages to draftspace and cannot suppress the redirect themselves and must add the db-r2 template? Is it large enough to warrant this alteration to a template that is presently used on close to a million redirects with the number growing daily by leaps and bounds? I doubt it, so no, IMAO there is no reason that the "large group" of editors can't continue to apply the SD template manually, which really isn't such a chore, you know. Paine Ellsworth put'r there 23:17, 3 September 2017 (UTC)
* PS. I consider your interpretation of the text at db-r2 to prove that it's subject to intepretation. And if we go with your choice, then we just get back to this proposal being a potentially huge migraine for the admins who monitor the db-r2 template application log. PS added by Paine Ellsworth put'r there
* Those are fair arguments. It may be that the number of people performing such moves is small (I'd have have a watch of the R2 CSD category for a while to see), but it could also be that many non-pagemover reviewers simply avoid the hassle of draftification because of the need to manually add tags (probably not that likely but possible). In any case the potential number of people that this would apply to (all editors except the 1000 or so Admins and page movers), is a very large group. Per your second point, I guess the real question is if changing the global template makes any noticeable change to any of the existing non-draft pointing redirects, if not, and visible changes are only applied to redirects pointing at draft space, then I would argue that there are only positive benefits. Would this change immediately apply a CSD tag to all existing (but unidentified) cross namespace redirects (potentially inundating that category with many pages creating a temporary backlog)? Even if that is the case, this would only be temporary, and would be preferable to leaving such redirects in place.
* As it is, I am surprised that we do not have a bot that automatically tags such inappropriate cross namespace redirects. Perhaps this would be an alternative proposal, a bot that tags all such redirects with a new tag 'cross namespace redirect' which would highlight such articles and put them in a new category so that a user (I'll volunteer) can manually rummage through and tag those that are appropriate for db R2. Would you support this as an alternative? — InsertCleverPhraseHere (or here) 00:30, 4 September 2017 (UTC)
* I've done two mass R2 taggings with AWB and a Quarry query. Don't remember how many each were, but someone who can see my deleted contribs could check. – Train2104 (t • c) 13:43, 4 September 2017 (UTC)
* I see nothing wrong with a bot that would tag the redirects with R to draft namespace, which would sort them to . Paine Ellsworth put'r there 01:31, 6 September 2017 (UTC)
Merge discussion: WP:Naming conventions (identity) to WP:Manual of Style
Please see "Wikipedia talk:Manual of Style", a proposal to merge perennial draft material at WP:Naming conventions (identity) to the WP:Manual of Style in one way or another (probably a section at MOS:BIO), since it is a draft style guideline with almost nothing in it that pertains specifically to article titles (i.e., it is not a naming convention).
Cross-listing at VPPRO because parts of the "naming convention" page date as far back as 2005, and it's been tagged with for way too long. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 07:48, 11 September 2017 (UTC)
Enhance Lint pages
Lint Errors could be enhanced with a short description of each type of error. The nine sub-pages could be enhanced with a short description of their respective type of error. For example, Lint errors: Fostered content should define "Fostered content" with a link to a page where the topic is discussed. (I found that page before but I can't find it now.) Paragraph wrapping bug workaround and Tidy whitespace bug are similarly non-obvious even to experienced editors. Also, these pages seem to list approximately, but not exactly, in order of least-recently to most-recently edited. It would be useful to know the exact rule for how the pages are ordered. One reason this would be useful is, after editing a listed article, the editor may wish to revisit the lint error list page to make sure the error is truly gone. But if editing affects the page ordering, then the user needs to know how to find where the page would be listed after editing.
For that matter, it would be useful to know the rule for how search results in general are ordered. —Anomalocaris (talk) 02:36, 1 September 2017 (UTC)
* There is a help page linked in the top right of each error type as well as the general special page. I agree, it is not very discoverable. I have also observed the order as "most-recently edited at the bottom". --Izno (talk) 12:17, 1 September 2017 (UTC)
* Regarding order, it's probably in order of "last parsed", which explains why edited articles are lower (as they automatically cause a new parse if the content has changed). But rendering can occur for many reasons, so that explains why the order is not exactly like that. BTW. these are not search results, they are just a list in our databases. Search results are what is returned by Special:Search (these use a completely different storage system, which is optimized for textual and partial matching). —Th e DJ (talk • contribs) 09:24, 5 September 2017 (UTC)
One can already see all errors in a page without ever going to the special page, e.g. https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)?action=info#Lint_errors. Note that the header only shows up on pages with errors. Userscripts can also show them without reloading the page. 17:58, 2 September 2017 (UTC)
* Thanks for discussing this. I think Subbu may be able to do something about T162895. But I also have a question about what else it is that we could be doing to solicit more involvement here :) I have posted info a number of times (in random order, this obviously doesn't include other venues such as the mailing lists, for example), and we really welcome more ideas about finding other interested people who we could support in fixing pages :) Elitre (WMF) (talk) 16:16, 7 September 2017 (UTC)
* While signatures can contain lint errors, there's little chance in reducing the figures significantly. T140606 would need fixing to help with it. -- WOSlinker (talk) 20:23, 7 September 2017 (UTC)
* I've been focusing on mainspace content and have filed a couple tasks that would help track the mainspace problems. Signatures being broken is not a significant issue IMO. If people use <font ></font> and find that they aren't getting the effect they want, they'll ask for help fixing it, at which point the "lint for signatures" issue mostly becomes moot. --Izno (talk) 22:17, 7 September 2017 (UTC)
* These messages can all be defined locally, for example in MediaWiki:linter-category-fostered-desc - someone just needs to propose the messages. Feel free to leave edit requests on the talk page of the mediawiki: page. — xaosflux Talk 03:24, 8 September 2017 (UTC)
* … but, as always, please don't do local customisations unless there's a serious need for bespoke information, as it means all future updates are lost to the English Wikipedia unless someone notices and manually copies them across. Jdforrester (WMF) (talk) 15:45, 8 September 2017 (UTC)
"But I also have a question about what else it is that we could be doing to solicit more involvement here :)" It is a problem of inefficient tooling. Tasks like this are a) hard to fix b) require an understanding of many technologies (html, css, wikitext, and maybe lua), and then they need to dig and investigate where these errors are coming from. In complicated cases, the lint only gives a hint of where it may come from, this could be a very deeply nested template. Psychology 101, means people only care about things that impact them directly. The pages currently look perfectly fine, and there is seemingly no need to do anything. The situation can be improved by either using the carrot or the stick.
The carrot:
* 1) Show errors in preview (https://phabricator.wikimedia.org/T163072)- This should be triaged and prioritized, and is the carrot because it will help all wikitext editors because editors often introduce such errors unknowningly and then spend minutes searching for the cause.
* 2) Expand highlighted segment and run the linter on it - (https://phabricator.wikimedia.org/T151362), (https://phabricator.wikimedia.org/T152824), or (https://phabricator.wikimedia.org/T163149) . The latter would be the most useful, and can be trivially done using a userscript.
The stick:
* Add an popup whenever people introduce basic errors to pages and try to save (this already happens with the code-editor)
* Forcibly activate the parser-migration extension for everyone or show it whenever there are migration errors in the page.
* Abusefilter - block new edits (e.g. new editors) from adding such simple (e.g. unclosed tags) lint errors to the template or possibly even the article namespace
The point is that the situation will continue as long as the lint error reports are stuffed in some special page somewhere that only few people even know about and fewer even care. The workboard for editors is the editing tool, putting things elsewhere is a great way to tell them not to care about it. Here's a recent example of this problem (https://en.wikipedia.org/w/index.php?title=Template%3AWFTDA_Division_3&type=revision&diff=799743535&oldid=799729962). A user edited 1 page (template) and immediately brought about 100 high priority lint errors, it could easily have been a template used in thousands or millions of pages, and if someone reverts it they'll simply come back.
The current approach is quite simply insane ... 16:18, 9 September 2017 (UTC)
* I don't think that we want to stop new editors from working on templates. Very few of them do, and they're the ones least likely to know how to figure out a problem. IMO it would make more sense to flag this kind of typo to experienced editors. The one responsible for the error you link has more than 10K edits, and even if s/he didn't know how to fix it, the editor would know where to ask for help. Whatamidoing (WMF) (talk) 15:33, 12 September 2017 (UTC)
Meta RfC to try to address one aspect of impersonation
Here Doc James (talk · contribs · email) 15:37, 13 September 2017 (UTC)
Automatic column mode for references element
Recently it became possible for or on every page, but this proposal is unrelated to that. Supporting or opposing this change will not have any effect on or any page that is using that template.
* Given that the Article Wizard puts plain in all articles, and given that plain seems to have been put by bot/AWB into more than a million articles during the last five years, I am not convinced by your assertion that the use of the plain template indicates an intentional use of one column. Perhaps a better measure would be the use of columns in GAs and FAs, since those generally include long lists of references, and are generally written by editors who know how to change the default.
* But even if I were convinced by your argument that not changing the template indicates intentionality, it's pretty much irrelevant, because this change will not have any effect whatsoever on the reflist template, or on any page that is using the reflist template. This change amounts to "When the responsive status is not specified (e.g., when the responsive-status-specifying reflist template is not used), then it should produce two or maybe three columns, on long lists of references, if your screen is wide enough."
* This change will likely affect ≤2% of articles. Whatamidoing (WMF) (talk) 16:36, 18 August 2017 (UTC)
* , your example, Great Officer of State, has quite short references compared to fully expanded references for books, institutional web pages, and journal articles used in many areas of Wikipedia. To have reflist detect such short references and use overly wide columns would completely undo the point of responsive references for much of the English Wikipedia. StarryGrandma (talk) 21:00, 14 August 2017 (UTC)
* That PBS and a few others feel that more disc. is needed, I would like to request the discussants to re-post this thread at Cent and make some fresh advertisements at related notice-boards.Otherwise, from the mini-post-closure discussion that is taking place, I fear, that it may be the same set of faces arguing/discusing broadly on the same set of themes.Esp. in an area where perceptions (rel. to readability et al) matter considerably, new faces would be welcome for sure. Winged Blades Godric 10:02, 14 August 2017 (UTC)
* I reinserted the entry into CENT template, Godric. I also notified others about this discussion. I wasn't sure whether to notify at WT:V or request posting an announcement at MediaWiki talk:Sitenotice, or MediaWiki talk:Watchlist-details, but I should be careful about canvassing before doing any of those options. --George Ho (talk) 10:34, 14 August 2017 (UTC); partially struck, 13:05, 15 August 2017 (UTC)
* thats fine, but I will not spend more time on this than I have. —Th e DJ (talk • contribs) 02:57, 15 August 2017 (UTC)
* PBS, may this discussion be mentioned in MediaWiki:Watchlist-details or MediaWiki:Sitenotice? You said that the discussion needs more input, right? --George Ho (talk) 12:50, 15 August 2017 (UTC)
* , a watchlist or site notice for this would be inappropriate. This a minor formatting change, not a major policy issue. TonyBallioni (talk) 13:03, 15 August 2017 (UTC)
* Rescinded consideration. --George Ho (talk) 13:04, 15 August 2017 (UTC)
* Comment@ StarryGrandma I agree with you, but the problem I have finding a really good example is that most of the pages I edit tend to use short citations and separate references section, and I think that columns are preferable for short citations. I tend to come across articles with 100 of large inline references only when I am running AWB scripts to fix something else, and as this is not an issue that has come up before I have not kept a record of such articles. Perhaps someone else has a few examples which can be used so that others view them and made an informed decision. -- PBS (talk) 09:24, 15 August 2017 (UTC)
* Try Pythagoreanism and Birecik, both of which contain two of the "long" version of the EB1911 template. Now I look at those, with some other long citations, I'm even more against the idea of forcing a width without reference to the line lengths. There are many other pages with multiline references due to book citations etc. But I am sensitive to the problem that choosing a bigger width (42 or 48) would result in just one column anyway, on most displays that aren't fullscreen on a PC. David Brooks (talk) 16:41, 15 August 2017 (UTC)
* Support - Since it's re-opened, I then add my full support. Making adopt to different screen sizes is always a plus to readers, this can be easily overridden with (with this version) or for editors who prefer a single column, the latter can also be added to charinsert gadget for an even easier access. --Lam-ang (talk) 15:15, 16 August 2017 (UTC)
* Support Headbomb {t · c · p · b} 15:53, 16 August 2017 (UTC)
* Support all the supporting arguments above. — Stanning (talk) 17:24, 16 August 2017 (UTC)
* Weak support as the general preference among editors, though I don't prefer the format myself, and I'm skeptical we have any real data on reader preferences. As long as we have a means of overriding it when it's not helpful, which is any time it's done with extensive footnotes rather than just short reference citations. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 23:31, 23 August 2017 (UTC)
Changing the color of DELETION TEMPLATES from from red to light green/light blue
has a page User:Ritchie333/How newbies see templates.
It would reduce WP:BITE, if Prod, csd templates and "notifying page creator templates" don't have red color. Red is warning/danger sign. If these Twinkle "article deletion" messages are light green, it won't scare new editors. -- <b style="color:Red">Marvellous</b> Spider-Man 05:34, 2 September 2017 (UTC)
Humm well it might scare them a little less. I'm ok with a change. Legacypac (talk) 05:53, 2 September 2017 (UTC)
* I admit, green and blue seem a little incongruous on a "ATTENTION THIS PAGE MAY BE DELETED" template. Deletion is deletion, irregardless of whether the template is red, blue or green. Jo-Jo Eumerus (talk, contributions) 08:46, 2 September 2017 (UTC)
* They will know that their article might be deleted. Red is a color of warning, which should be used only to warn vandals, or block templates. Creating article about non-notable actors, musicians, bands, politicians is not vandalism. They should not see red colored template on their article page and talk page. <b style="color:Red">Marvellous</b> Spider-Man 09:10, 2 September 2017 (UTC)
* While I appreciate the intent here, red is the appropriate color for "THIS NEEDS URGENT ATTENTION". Alsee (talk) 17:52, 2 September 2017 (UTC)
* Split the difference and use yellow or orange. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 09:01, 5 September 2017 (UTC)
* Yellow seems right--or orange -- red is overused on WP. Are there any problems about accessibility? DGG ( talk ) 20:27, 6 September 2017 (UTC)
* No more so than Red.
* People with deuteranomaly and protanomaly are collectively known as red-green colour blind and they generally have difficulty distinguishing between reds, greens, browns and oranges. They also commonly confuse different types of blue and purple hues. People with reduced blue sensitivity have difficulty identifying differences between blue and yellow, violet and red and blue and green. To these people the world appears as generally red, pink, black, white, grey and turquoise.
* So to color blind people it will look the same. (probably) Α Guy into Bοοks ™ § ( Message ) - 09:15, 10 September 2017 (UTC)
* Have a look at it yourself with Coblis if you want to check. — InsertCleverPhraseHere (or here) 04:52, 11 September 2017 (UTC)
* Oppose. The Ambox color scheme was decided 10 years ago, and most changes since then have been minor. This is not minor at all. KMF (talk) 16:39, 16 September 2017 (UTC)
* Readers of this proposal may be interested to know that "Change the colour of redlinks" appears on Perennial proposals. Vorbee (talk) 19:52, 16 September 2017 (UTC)
* Oppose. Solution in search of a problem. Kudpung กุดผึ้ง (talk) 21:14, 16 September 2017 (UTC)
|
WIKI
|
User:Mccapra/CSD log
May 2020
* McCordick Glove & Safety: CSD G11 (db-spam); notified 12:51, 4 May 2020 (UTC)
* Ala Hazrat Imam Ahmed Raza Khan: CSD A10 (db-a10); additional information: {A10 article: Ahmed Raza Khan Barelvi}; notified 15:53, 12 May 2020 (UTC)
* Frictionless: CSD A5 (db-transwiki); additional information: {A5 location: https://en.m.wiktionary.org/wiki/frictionless}; notified 20:46, 18 May 2020 (UTC)
* Albemarle High School (North Carolina): CSD A3 (db-nocontent); notified 09:15, 23 May 2020 (UTC)
June 2020
* African American Artists Collective KC: CSD A7 (db-club); notified 20:51, 17 June 2020 (UTC)
* Firstbahn: CSD A7 (db-corp); notified 20:54, 17 June 2020 (UTC)
July 2020
* The Book of Daniel (film): CSD A3 (db-nocontent); notified 04:01, 15 July 2020 (UTC)
* Humphrey seithati: CSD G1 (db-nonsense); notified 20:21, 22 July 2020 (UTC)
* Conquest of Shewa/Temp: CSD G6 (db-g6); additional information: {G6 rationale: Recreation of Conquest of Shewa by author after the main article was blanked over copyright concerns, is resolved } 04:43, 26 July 2020 (UTC)
* Philip I of England: CSD G3 (db-hoax) 12:51, 27 July 2020 (UTC)
* Basim zulfkar: CSD G6 (db-g6); additional information: {G6 rationale: Apparent user page in mainspace } 20:28, 30 July 2020 (UTC)
August 2020
* Լիանա Ալեքսանյան, սոպրանո: CSD A2 (db-foreign); additional information: {A2 source: https://hy.wikipedia.org/wiki/%D4%BC%D5%AB%D5%A1%D5%B6%D5%A1_%D4%B1%D5%AC%D5%A5%D6%84%D5%BD%D5%A1%D5%B6%D5%B5%D5%A1%D5%B6}; notified 15:25, 16 August 2020 (UTC)
* Battle of Aror: CSD G12 (db-copyvio); additional information: {G12 url: http://fazal-pakistan.blogspot.com/2011/11/}; notified 06:10, 26 August 2020 (UTC)
* History of the Aramean people: CSD G12 (db-copyvio); additional information: {G12 url: https://aratta.wordpress.com/2018/05/17/is-there-any-connections-between-armenians-and-arameans/}; notified 19:29, 30 August 2020 (UTC)
September 2020
* Convent of Jesus and Mary, Shimla: CSD G12 (db-copyvio); additional information: {G12 url: http://www.cjmshimla.org/school-history.aspx}; notified 18:54, 4 September 2020 (UTC)
* Stefan Blankertz: db-reason Db-r2 21:27, 29 September 2020 (UTC)
* Jack Hoffenberg: db-reason Db-r2 21:35, 29 September 2020 (UTC)
* Mohammad Al-Hasan Al-Dido: db-reason Db-r2 21:45, 29 September 2020 (UTC)
* Ortha O. Barr Jr.: db-reason Db-r2 04:37, 30 September 2020 (UTC)
* Jean-Paul Skoczylas: db-reason Db-r2 19:44, 30 September 2020 (UTC)
* Most Terrifying Places: db-reasonDb-r2 21:11, 30 September 2020 (UTC)
October 2020
* Salome Gviniashvili: db-reason Db-r2 03:57, 1 October 2020 (UTC)
* Actix: db-reason Db-r2 03:59, 1 October 2020 (UTC)
* Studies in the Upapurāṇas: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles_for_deletion/Studies_in_the_Upapur%C4%81%E1%B9%87as}; notified 07:53, 5 October 2020 (UTC)
* Dato' Sri Dr. Sallehuddin bin Ishak/sandbox: CSD A10 (db-a10); additional information: {A10 article: Dato' Sri Dr. Sallehuddin bin Ishak}; notified 06:57, 12 October 2020 (UTC)
* Dick Wiend: CSD R3 (db-redirtypo) 18:07, 13 October 2020 (UTC)
* Kingdom of Luang Phrabang (1945): CSD A10 (db-a10); additional information: {A10 article: French protectorate of Laos}; notified 05:11, 17 October 2020 (UTC)
* Kylie morgan: CSD G12 (db-copyvio); additional information: {G12 url: http://www.smacksongs.com/kylie-morgan}; notified 20:41, 23 October 2020 (UTC)
November 2020
* Renk: CSD G6 (db-move); additional information: {G6 page: https://en.wikipedia.org/wiki/Draft:Renk} {G6 reason: Article ready to come from draft after addition of sufficient sources } 13:38, 1 November 2020 (UTC)
* Lakhan Pasi: CSD A3 (db-nocontent); notified 06:06, 7 November 2020 (UTC)
* WikiProject ConwayLibrary/Contributors: CSD G6 (db-g6); additional information: {G6 rationale: Accidental creation. Proper page is Wikipedia:WikiProject ConwayLibrary/Contributors} 06:20, 7 November 2020 (UTC)
* Russell Dennis Lewis: CSD G7 (db-author); additional information: {G7 rationale: Author request on page } 06:25, 14 November 2020 (UTC)
* Jody Paulsen: CSD G12 (db-copyvio); additional information: {G12 url: https://smacgallery.com/artist/jp-cv/}; notified 18:48, 23 November 2020 (UTC)
* Tharos Ltd: CSD G11 (db-spam); notified 11:39, 26 November 2020 (UTC)
* Tharos.co.uk: CSD G11 (db-spam); notified 11:39, 26 November 2020 (UTC)
* Tharos (company): CSD G11 (db-spam); notified 11:39, 26 November 2020 (UTC)
* EquiNectar.com: CSD G11 (db-spam); notified 11:40, 26 November 2020 (UTC)
* Equinectar: CSD G11 (db-spam); notified 11:40, 26 November 2020 (UTC)
* Equinectar.com: CSD G11 (db-spam); notified 11:41, 26 November 2020 (UTC)
* EquiNectar: CSD G11 (db-spam); notified 11:41, 26 November 2020 (UTC)
* EquiNectar (product): CSD G11 (db-spam); notified 11:42, 26 November 2020 (UTC)
December 2020
* UserBear6811Wiki: CSD G6 (db-g6); additional information: {G6 rationale: Accidental creation of user page in mainspace } 22:07, 3 December 2020 (UTC)
* Election fraud: CSD G3 (db-vandalism); notified 21:40, 5 December 2020 (UTC)
* Political Thought: CSD G6 (db-g6); additional information: {G6 rationale: New editor created this by mistake, intending to add it as a section to John Dickinson (now done).} 04:26, 6 December 2020 (UTC)
*<PHONE_NUMBER>00002020200001111111: CSD G1 (db-nonsense); notified 05:23, 11 December 2020 (UTC)
* Not Me (TV series): CSD G1 (db-nonsense); notified 18:32, 19 December 2020 (UTC)
* The Morning Crew (radio): CSD A7 (db-corp); notified 06:30, 21 December 2020 (UTC)
* Mary Elizabeth MacCallum Scott: CSD G6 (db-move); additional information: {G6 page: https://en.wikipedia.org/wiki/Dr._Mary_Elizabeth_MacCallum_Scott} {G6 reason: User wanted to move sandbox article to mainspace } 06:01, 22 December 2020 (UTC)
* Leomarve: CSD G2 (db-test); notified 22:01, 24 December 2020 (UTC)
* Modern technology: CSD G2 (db-test); notified 12:02, 26 December 2020 (UTC)
* Calendar (New Style) Act 1750/sandbox: CSD G6 (db-g6); additional information: {G6 rationale: Calendar (New Style) Act 1750 already created by same editor } 00:07, 27 December 2020 (UTC)
* Syed Uzair Ali: CSD A7 (db-person); notified 22:10, 28 December 2020 (UTC)
January 2021
* Nyoni Couture: CSD G11 (db-spam); notified 07:22, 2 January 2021 (UTC)
* O.W. Richards: CSD G1 (db-nonsense); notified 07:24, 2 January 2021 (UTC)
* Being Human (Music Producer): CSD A7 (db-person); notified 16:59, 5 January 2021 (UTC)
* Μέδουσα: CSD G1 (db-nonsense); notified 22:45, 6 January 2021 (UTC)
* Queensland State Soils Collection: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft: Queensland State Soils Collection}; notified 23:03, 6 January 2021 (UTC)
* RNZAF Police: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:RNZAF Police}; notified 23:09, 6 January 2021 (UTC)
* Hugo Berthold von Buttel-Reepen: CSD G1 (db-nonsense); notified 07:58, 11 January 2021 (UTC)
* Secular Democratic Progressive Alliance: CSD A3 (db-nocontent); notified 09:10, 12 January 2021 (UTC)
* Political history of Belarus: CSD G12 (db-copyvio); additional information: {G12 url: https://photius.com/countries/belarus/government/belarus_government_prelude_to_independe~677.html} {G12 url2: http://countrystudies.us/belarus/39.htm} {G12 url3: https://namecensus.com/reference/country_studies/belarus/GOVERNMENT.html}; notified 19:54, 17 January 2021 (UTC)
* French Territory of the Comoros: CSD G12 (db-copyvio); additional information: {G12 url: http://countrystudies.us/comoros/3.htm} {G12 url2: http://www.country-data.com/cgi-bin/query/r-3392.html} {G12 url3: https://namecensus.com/reference/country_studies/comoros/HISTORY.html}; notified 22:43, 20 January 2021 (UTC)
* Wowflute: CSD G11 (db-spam); notified 07:51, 29 January 2021 (UTC)
* Sk. Md. Zakir Hossain: CSD A7 (db-person); notified 09:20, 29 January 2021 (UTC)
* This attack page: CSD G10 (db-attack); notified 18:01, 29 January 2021 (UTC)
February 2021
* Congettura di Takeuti: CSD G7 (db-author); additional information: {G7 rationale: Page blanked by author. Article was in Italian } 07:50, 1 February 2021 (UTC)
* Eli Primmer: CSD G2 (db-test); notified 19:10, 5 February 2021 (UTC)
* Enternalkinghmm: CSD G1 (db-nonsense); notified 06:33, 13 February 2021 (UTC)
* NURUZY: CSD G1 (db-nonsense); notified 06:34, 13 February 2021 (UTC)
* Sahasrad chippa: CSD G1 (db-nonsense); notified 23:53, 14 February 2021 (UTC)
* Kotoe Hatsui: CSD A7 (db-person); notified 23:56, 14 February 2021 (UTC)
* Cletus Verycorrupt: CSD G3 (db-hoax); notified 05:40, 16 February 2021 (UTC)
* شهاب پارنج: CSD A3 (db-nocontent); notified 05:29, 19 February 2021 (UTC)
* Asia highway 121: CSD A3 (db-nocontent); notified 05:51, 27 February 2021 (UTC)
* AMUSIKA: CSD A7 (db-person); notified 05:52, 27 February 2021 (UTC)
* 2LANE: CSD A7 (db-person); notified 05:55, 27 February 2021 (UTC)
March 2021
* Kamal Haasan books recommendation: CSD G11 (db-spam); notified 12:42, 3 March 2021 (UTC)
* Samar Singh Gandhi: CSD A7 (db-person); notified 05:23, 14 March 2021 (UTC)
* Theresemsmith: CSD G1 (db-nonsense); notified 06:31, 15 March 2021 (UTC)
* Pearl C. Hsiung: CSD A7 (db-person); notified 05:33, 17 March 2021 (UTC)
* The Sir World: CSD G1 (db-nonsense); notified 07:33, 21 March 2021 (UTC)
* Clown Core: CSD A7 (db-band); notified 04:35, 25 March 2021 (UTC)
* Keith O'Conner Murphy - singer, songwriter, Rockabilly Hall of Fame, recording artist in USA and UK on Stacy, King, Polydor: CSD A7 (db-person); notified 17:54, 26 March 2021 (UTC)
* Kanshiram Bahujan Samaj Party: CSD A3 (db-nocontent); notified 06:48, 28 March 2021 (UTC)
* Bruno Simon: CSD A7 (db-person); notified 09:12, 29 March 2021 (UTC)
* Cooperative Development Authority: CSD G12 (db-copyvio); additional information: {G12 url: https://cda.gov.ph/about-us/historical-background/}; notified 11:33, 29 March 2021 (UTC)
* M.R. Gandhi: CSD G11 (db-spam); notified 18:02, 29 March 2021 (UTC)
* Gadwall State: CSD G3 (db-hoax); notified 20:42, 29 March 2021 (UTC)
* Gadwallis: CSD G3 (db-hoax); notified 20:43, 29 March 2021 (UTC)
* Sri Gadwall: CSD G3 (db-hoax); notified 20:43, 29 March 2021 (UTC)
* Gadwallis people: CSD G3 (db-hoax); notified 20:45, 29 March 2021 (UTC)
* Draft:Gasya or Gadh-lipi: CSD G3 (db-hoax); notified 21:20, 29 March 2021 (UTC)
* RPSI Controversy's: CSD A10 (db-a10); additional information: {A10 article: Railway Preservation Society of Ireland}; notified 08:27, 30 March 2021 (UTC)
* Zawackimc/Buonconte da Montefeltro: CSD A10 (db-a10); additional information: {A10 article: Buonconte da Montefeltro}; notified 06:57, 31 March 2021 (UTC)
April 2021
* Bella mia fiamma, addio: CSD G12 (db-copyvio); additional information: {G12 url: https://mozartschildren.wordpress.com/2010/11/03/bella-mia-fiamma-addio-3-november-1787/}; notified 12:25, 1 April 2021 (UTC)
* Kagyusasdf: CSD G2 (db-test); notified 15:02, 5 April 2021 (UTC)
* Leegy discography: CSD G1 (db-nonsense); notified 18:00, 5 April 2021 (UTC)
* Second Birth: CSD G7 (db-author) 18:30, 5 April 2021 (UTC)
* Sachin Singh Sisodia: CSD A7 (db-person); notified 21:36, 5 April 2021 (UTC)
* Yesno/sandbox: CSD G2 (db-test); notified 04:25, 13 April 2021 (UTC)
* Sachin Sharma: CSD A7 (db-person); notified 05:41, 16 April 2021 (UTC)
* Soorasamgaram: CSD G1 (db-nonsense); notified 06:41, 17 April 2021 (UTC)
* A1 x J1: CSD A7 (db-band); notified 11:35, 17 April 2021 (UTC)
* David O'Keeffe: CSD A3 (db-nocontent); notified 18:13, 22 April 2021 (UTC)
* Mxolisi Nhleko: CSD A7 (db-person); notified 22:37, 24 April 2021 (UTC)
* Guang Gun: db-reason; additional information: {Custom rationale: Author has created the same page three times today }; notified 12:32, 25 April 2021 (UTC)
* 光棍 (Bare Branches): db-reason; additional information: {Custom rationale: Author has created the same page three times today }; notified 12:33, 25 April 2021 (UTC)
* Island states navy officer ranks: CSD G7 (db-author); additional information: {G7 rationale: Discussion on creator talk page indicates the article was OR } 09:30, 26 April 2021 (UTC)
May 2021
* 2020–21 Chinese Basketball Association: CSD A3 (db-nocontent); notified 17:58, 2 May 2021 (UTC)
* AlZamakhshari: CSD A10 (db-a10); additional information: {A10 article: Al-Zamakhshari}; notified 09:41, 3 May 2021 (UTC)
* Soham Lahiri: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Soham Lahiri}; notified 05:12, 6 May 2021 (UTC)
* Pranabjyoti Das: CSD A7 (db-person); notified 18:11, 8 May 2021 (UTC)
* Md Anan Islam: CSD A7 (db-person); notified 04:44, 12 May 2021 (UTC)
* Alya Mansa: CSD A3 (db-nocontent); notified 07:22, 12 May 2021 (UTC)
* Yo Yo Alok King: CSD A7 (db-person); notified 18:01, 14 May 2021 (UTC)
* Daily Nai Baat: CSD A7 (db-corp); notified 18:01, 14 May 2021 (UTC)
* Rasadul Islam Mozumder Tanzil: CSD A7 (db-person); notified 23:10, 15 May 2021 (UTC)
* Imu Ovaioza Yunusa: CSD A7 (db-person); notified 15:14, 18 May 2021 (UTC)
* Okpanachi Ocholi Yusuf: CSD A7 (db-person); notified 15:15, 18 May 2021 (UTC)
* Joshua King Dada: CSD G11 (db-spam); notified 15:18, 18 May 2021 (UTC)
* Sandeep Kumar Reddy: CSD A7 (db-band); notified 18:49, 22 May 2021 (UTC)
* Willy Bang Kaup: CSD G12 (db-copyvio); additional information: {G12 url: https://www.iranicaonline.org/articles/bang-kaup-johann-wilhelm-max-julius-known-as-willy-german-orientalist-b}; notified 22:21, 22 May 2021 (UTC)
* Polar bears: CSD A1 (db-nocontext); notified 08:43, 24 May 2021 (UTC)
* Marco Goldschwartz: CSD G3 (db-hoax); notified 04:04, 25 May 2021 (UTC)
* GoDa: CSD A7 (db-person); notified 18:25, 26 May 2021 (UTC)
* Rezaul Karim Refath: CSD G11 (db-spam); notified 07:45, 27 May 2021 (UTC)
* Mithlesh Kaushik (Mith): CSD G11 (db-spam); notified 08:04, 27 May 2021 (UTC)
* William Western: CSD A7 (db-person); notified 07:18, 28 May 2021 (UTC)
* Battle of Kangra: CSD G12 (db-copyvio); additional information: {G12 url: https://pparihar.com/2019/08/31/battle-of-kangra-rajput-defeated-tuglaq-truth-retold/}; notified 12:43, 28 May 2021 (UTC)
* Battle of Lier: CSD A3 (db-nocontent); notified 21:47, 28 May 2021 (UTC)
* Kiin Jama: CSD A7 (db-person); notified 09:15, 29 May 2021 (UTC)
* Anonto Hasan Rajan: CSD A7 (db-person); notified 18:52, 29 May 2021 (UTC)
* 2001 Interlagos F3000 Round: CSD G7 (db-author) 19:48, 29 May 2021 (UTC)
* DaQuan Aaron Tyler: CSD A7 (db-person); notified 22:17, 30 May 2021 (UTC)
* Badi Doooor Se Aaye Hai (Franchise): CSD G1 (db-nonsense); notified 13:00, 31 May 2021 (UTC)
June 2021
* Zoie (comedian): CSD G1 (db-nonsense); notified 12:35, 1 June 2021 (UTC)
* Biraj Bhattarai: CSD A7 (db-person); notified 07:01, 3 June 2021 (UTC)
* Olivia Chenery: CSD A7 (db-person); notified 17:53, 3 June 2021 (UTC)
* Online Signatures: CSD G1 (db-nonsense); notified 14:33, 4 June 2021 (UTC)
* Valluri kranthi: CSD A7 (db-person); notified 20:42, 4 June 2021 (UTC)
* Andrei Croitoru: CSD A7 (db-person); notified 20:52, 4 June 2021 (UTC)
* Gerard Hooper: CSD A7 (db-person); notified 21:31, 4 June 2021 (UTC)
* Lil Darkie: CSD A7 (db-person); notified 02:00, 5 June 2021 (UTC)
* Tomb of Ali: CSD G14 (db-disambig); notified 13:49, 5 June 2021 (UTC)
* Kamakkk kunall: CSD A7 (db-person); notified 04:28, 6 June 2021 (UTC)
* K. Kavi Nanthan: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/K. Kavi Nanthan}; notified 04:35, 6 June 2021 (UTC)
* Kosovo at major beauty pageants: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Kosovo at major beauty pageants}; notified 05:00, 6 June 2021 (UTC)
* 2020-21 Aberystwyth Town F.C. season: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/2020–21 Aberystwyth Town F.C. season}; notified 05:07, 6 June 2021 (UTC)
* Stephen Akintayo: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Stephen Akintayo (2nd nomination)}; notified 05:11, 6 June 2021 (UTC)
* Freelancer nasim: CSD G11 (db-spam); notified 22:26, 7 June 2021 (UTC)
* Varun Krishna: CSD A7 (db-person); notified 01:45, 8 June 2021 (UTC)
* Shakti Singh (politician): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Shakti Singh (politician)}; notified 12:06, 9 June 2021 (UTC)
* Hemant Sharma: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Hemant Sharma}; notified 18:59, 9 June 2021 (UTC)
* List of notable football players in Kerala: CSD G12 (db-copyvio); additional information: {G12 url: http://www.owlapps.net/owlapps_apps/articles?id=43229944&lang=en}; notified 19:35, 9 June 2021 (UTC)
* Ximei: CSD G12 (db-copyvio); additional information: {G12 url: https://www.acfilmsinc.com/ximei}; notified 08:23, 11 June 2021 (UTC)
* Andre Mario Smith (Composer): CSD G11 (db-spam); notified 08:24, 11 June 2021 (UTC)
* Andre Mario Smith: CSD G11 (db-spam); notified 08:25, 11 June 2021 (UTC)
* Rovere Stellanera: CSD G3 (db-hoax); notified 11:09, 12 June 2021 (UTC)
* The Great Song to Mani: CSD G12 (db-copyvio); additional information: {G12 url: http://www.manichaean.org/pdf/manichaean-psalms.pdf}; notified 11:57, 12 June 2021 (UTC)
* Qavloical Authority: CSD A11 (db-madeup); notified 21:47, 12 June 2021 (UTC)
* Chase Community Independents Group: CSD A7 (db-corp); notified 07:37, 13 June 2021 (UTC)
* Marshall Lewy: CSD A7 (db-person); notified 19:31, 13 June 2021 (UTC)
* Selfpause: CSD A7 (db-corp); notified 07:45, 14 June 2021 (UTC)
* FaZmash: CSD A7 (db-person); notified 07:46, 14 June 2021 (UTC)
* Miriam Abadi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Miriam Abadi}; notified 11:50, 14 June 2021 (UTC)
* Dr Mohammed Asheel: CSD A7 (db-person); notified 07:40, 15 June 2021 (UTC)
* Sikka (1989 film): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sikka (film)}; notified 21:09, 15 June 2021 (UTC)
* Ljkingcc 1: CSD G1 (db-nonsense); notified 02:38, 16 June 2021 (UTC)
* Parnas Café: CSD A7 (db-corp); notified 20:00, 16 June 2021 (UTC)
* Eghe Nimose: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Eghe Nimose}; notified 20:19, 16 June 2021 (UTC)
* Arvind Arora: CSD G11 (db-spam); notified 12:20, 17 June 2021 (UTC)
* Maximilian Von Rusburg: CSD G3 (db-hoax); notified 09:01, 18 June 2021 (UTC)
* Jilito: CSD G11 (db-spam); notified 18:57, 18 June 2021 (UTC)
* Daniel Camarena: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Daniel Camarena}; notified 21:28, 18 June 2021 (UTC)
* Sac, Sacians: CSD A7 (db-club); notified 09:22, 19 June 2021 (UTC)
* Baabarr Mudacer: CSD A7 (db-person); notified 10:07, 19 June 2021 (UTC)
* The Holiday Crafters: CSD A7 (db-corp); notified 12:54, 19 June 2021 (UTC)
* Ellist: CSD A7 (db-band); notified 08:27, 20 June 2021 (UTC)
* Pratik Solanki: CSD A7 (db-person); notified 08:43, 20 June 2021 (UTC)
* Emmanuel Vasily: CSD G3 (db-hoax); notified 04:03, 22 June 2021 (UTC)
* Haseeb Choudhary: CSD A7 (db-person); notified 07:45, 22 June 2021 (UTC)
* My fanmade templates: CSD G2 (db-test); notified 04:04, 23 June 2021 (UTC)
* Mohammed Ismail Sadiq Monsoor: CSD A7 (db-person); notified 18:01, 25 June 2021 (UTC)
* OniX CyberTronN: CSD A7 (db-person); notified 07:05, 28 June 2021 (UTC)
* Thacholi Othenan (film): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Thacholi Othenan (film)}; notified 07:06, 28 June 2021 (UTC)
* Dean Lee Hansen: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Dean Lee Hansen}; notified 21:14, 28 June 2021 (UTC)
* Raybak Abdesselem: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Raybak Abdesselem}; notified 21:16, 28 June 2021 (UTC)
July 2021
* Sebastian Ousepparampil: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sebastian Ousepparampil}; notified 07:35, 1 July 2021 (UTC)
* R. D. Saini: CSD G11 (db-spam); notified 18:13, 1 July 2021 (UTC)
* Suman Sen: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Suman Sen}; notified 08:53, 3 July 2021 (UTC)
* Bikash Jung Karki: CSD G11 (db-spam); notified 09:43, 3 July 2021 (UTC)
* Theri (2016 Indian film): CSD G7 (db-author); additional information: {G7 rationale: Edit history shows ARD} 09:59, 3 July 2021 (UTC)
* Vijayakumar (Tamil actor): CSD G7 (db-author) 10:19, 3 July 2021 (UTC)
* Millie Tunnel: CSD A3 (db-nocontent); notified 17:13, 3 July 2021 (UTC)
* Nina Aquila: Legal Eagle: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Nina Aquila: Legal Eagle}; notified 17:17, 3 July 2021 (UTC)
* Vilagran & Delavy: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Vilagran & Delavy}; notified 09:33, 4 July 2021 (UTC)
* Jethalal Champaklal Gada: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of Taarak Mehta Ka Ooltah Chashmah characters (2nd nomination)}; notified 13:27, 4 July 2021 (UTC)
* Khan Sir Patna: CSD G11 (db-spam); notified 12:19, 7 July 2021 (UTC)
* Mustafa Kayyali: CSD A7 (db-person); notified 21:59, 7 July 2021 (UTC)
* Miss Wonderland and landscape 2015: CSD G1 (db-nonsense); notified 22:26, 7 July 2021 (UTC)
* Ôlåids: CSD G11 (db-spam); notified 05:01, 8 July 2021 (UTC)
* Avijit Bera: CSD A7 (db-person); notified 06:43, 8 July 2021 (UTC)
* Ôlåids: CSD G11 (db-spam); notified 08:00, 8 July 2021 (UTC)
* Safe Society: CSD G12 (db-copyvio); additional information: {G12 url: https://safesociety.in/gender-equality/}; notified 19:42, 9 July 2021 (UTC)
* Aryan Zodiac: CSD G11 (db-spam); notified 01:43, 10 July 2021 (UTC)
* Aryan zodiac: CSD G7 (db-author) 02:13, 10 July 2021 (UTC)
* Jibran sami khan: CSD A7 (db-person); notified 08:37, 10 July 2021 (UTC)
* Muthuramalinga Sethupathi: CSD G12 (db-copyvio); additional information: {G12 url: https://www.istampgallery.com/muthuramalinga-sethupathy/}; notified 09:24, 10 July 2021 (UTC)
* Physics wallah: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Physics Wallah}; notified 09:01, 11 July 2021 (UTC)
* Miša bitenc hernčič: CSD A7 (db-person); notified 16:44, 11 July 2021 (UTC)
* Ritesh Malik: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ritesh Malik (2nd nomination)}; notified 12:03, 12 July 2021 (UTC)
* All-Europeans Player of the Year: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/All-Europeans Player of the Year}; notified 12:05, 12 July 2021 (UTC)
* Dr.Mahendra singh chouhan: CSD A7 (db-person); notified 13:02, 12 July 2021 (UTC)
* Dr.Mahendra Singh Chouhan: CSD G6 (db-g6); additional information: {G6 rationale: Attempted redirect to article with correct spelling. Other article at SD. } 13:03, 12 July 2021 (UTC)
* Reza Bahram: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Reza Bahram}; notified 15:34, 12 July 2021 (UTC)
* Pur (action): CSD G1 (db-nonsense); notified 18:35, 12 July 2021 (UTC)
* Kakran: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Kakran}; notified 02:44, 14 July 2021 (UTC)
* Uthishta: CSD G11 (db-spam); notified 07:40, 14 July 2021 (UTC)
* Susmoy Debnath: CSD A7 (db-person); notified 17:11, 16 July 2021 (UTC)
* Amir Al-Ammari: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Amir Al-Ammari}; notified 19:04, 16 July 2021 (UTC)
* Brian David Gilbert: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Brian David Gilbert}; notified 19:08, 16 July 2021 (UTC)
* Docto (company): CSD A7 (db-corp); notified 09:01, 17 July 2021 (UTC)
* Annamalai Kuppusamy: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/K. Annamalai (I.P.S)}; notified 12:33, 17 July 2021 (UTC)
* Muhammad Waqas: CSD A7 (db-person); notified 12:35, 17 July 2021 (UTC)
* List of Awards and nomiantions recieved by Aftab Shivdasani: CSD G7 (db-author) 11:18, 18 July 2021 (UTC)
* Digambar Ashram: CSD A7 (db-corp); notified 11:19, 18 July 2021 (UTC)
* Digambar Ashram Asni: CSD A7 (db-corp); notified 12:02, 18 July 2021 (UTC)
* Henry Segerman: CSD A7 (db-person); notified 15:45, 18 July 2021 (UTC)
* Ali Arkady: CSD G12 (db-copyvio); additional information: {G12 url: https://viiphoto.com/profile/ali-arkady/}; notified 20:28, 18 July 2021 (UTC)
* This attack page: CSD G10 (db-attack); notified 10:12, 20 July 2021 (UTC)
* Arnob khan akib: CSD A7 (db-person); notified 21:21, 20 July 2021 (UTC)
* What's Made Milwaukee Famous (Has Made a Winner Out of Me): CSD G7 (db-author) 05:04, 21 July 2021 (UTC)
* Arash Mardani: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Arash Mardani}; notified 11:38, 22 July 2021 (UTC)
* Jai Srinivas: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Jai Srinivas}; notified 19:43, 22 July 2021 (UTC)
* Mohd Bakri Omar: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Mohamed Bakri Omar}; notified 07:01, 23 July 2021 (UTC)
* Wikipedians interested in colored pencil: CSD G1 (db-nonsense); notified 11:51, 24 July 2021 (UTC)
* List of President of India (Micronation): CSD G3 (db-hoax); notified 17:45, 26 July 2021 (UTC)
* Tigray People's Liberation Front, Ethiopia: CSD G1 (db-nonsense); notified 17:53, 26 July 2021 (UTC)
* Leo Heaps: CSD G1 (db-nonsense); notified 07:45, 27 July 2021 (UTC)
* John Donald Cody: CSD G7 (db-author) 17:59, 27 July 2021 (UTC)
* Kurukahveci Mehmet Efendi: CSD G11 (db-spam); notified 01:29, 28 July 2021 (UTC)
* Kallamadi surendra swamy: CSD A7 (db-person); notified 09:56, 28 July 2021 (UTC)
* New Hope Givers Society: CSD A7 (db-corp); notified 14:10, 29 July 2021 (UTC)
* Lucie Kriegsmannová: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Lucie Kriegsmannová}; notified 22:41, 29 July 2021 (UTC)
* Ella & Etta Cesaire: CSD A1 (db-nocontext); notified 10:40, 30 July 2021 (UTC)
* Cycling in Kohima: CSD G11 (db-spam); notified 15:08, 30 July 2021 (UTC)
* Flint McGlaughlin: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Flint McGlaughlin}; notified 21:21, 30 July 2021 (UTC)
* Jalapeños Mexican Restaurant: CSD A7 (db-corp); notified 07:58, 31 July 2021 (UTC)
August 2021
* Aakash Kumar Jha: CSD G11 (db-spam); notified 04:20, 1 August 2021 (UTC)
* Sekolah Jenis Kebangsaan (C) Kuen Cheng (1): CSD A7 (db-corp); notified 09:29, 1 August 2021 (UTC)
* Hermann Guthe (Geograph): CSD A10 (db-a10); additional information: {A10 article: Hermann Guthe (geographer)}; notified 18:04, 1 August 2021 (UTC)
* Energy The Ep: CSD A9 (db-a9); notified 03:17, 2 August 2021 (UTC)
* Susan dolan: CSD A7 (db-person); notified 04:12, 5 August 2021 (UTC)
* M.Muruganandam: CSD A7 (db-person); notified 04:38, 5 August 2021 (UTC)
* Lakshya Dweep Jha: CSD G11 (db-spam); notified 04:51, 5 August 2021 (UTC)
* Róth Rebeka: CSD A7 (db-person); notified 08:12, 7 August 2021 (UTC)
* Albania at major beauty pageants: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Albania at major beauty pageants}; notified 07:15, 8 August 2021 (UTC)
* Chandrashekar NR: CSD A7 (db-person); notified 13:07, 9 August 2021 (UTC)
* Costa Rica at major beauty pageants: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Cayman Islands at major beauty pageants}; notified 03:51, 11 August 2021 (UTC)
* The Obelisk (magazine): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/The Obelisk (magazine)}; notified 06:17, 11 August 2021 (UTC)
* Mohd Saif: CSD A7 (db-person); notified 17:20, 11 August 2021 (UTC)
* Ryan Padula Jayathunga: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Ryan Padula Jayathunga}; notified 17:42, 11 August 2021 (UTC)
* Mohd Saif: CSD A7 (db-person); notified 17:46, 11 August 2021 (UTC)
* REDROSE RECORDS: CSD G11 (db-spam); notified 04:41, 12 August 2021 (UTC)
* Agni Sūktam: CSD G12 (db-copyvio); additional information: {G12 url: https://www.shastras.com/vedic-hymns/agni-suktam/}; notified 16:53, 12 August 2021 (UTC)
* Main road 106 (Hungary): CSD G7 (db-author) 19:58, 12 August 2021 (UTC)
* Elvis Obinna Nwankwo: CSD A7 (db-person); notified 01:24, 13 August 2021 (UTC)
* List of Deputy Chairman of the Maharashtra Legislative Council: CSD G6 (db-copypaste); additional information: {G6 sourcepage: https://en.wikipedia.org/wiki/Draft:List_of_Deputy_Chairman_of_the_Maharashtra_Legislative_Council}; notified 13:20, 14 August 2021 (UTC)
* Sayyid Raphael Dakik: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sayyid Raphael Dakik}; notified 21:15, 14 August 2021 (UTC)
* Isaac Saul: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Isaac Saul}; notified 22:22, 14 August 2021 (UTC)
* Hina Altaf: CSD G7 (db-author) 22:31, 14 August 2021 (UTC)
* Pak Sindhiana Island: CSD A1 (db-nocontext); notified 22:32, 14 August 2021 (UTC)
* Minerals in Pakistan: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Minerals in Pakistan}; notified 23:18, 14 August 2021 (UTC)
* Masroor Sheidaei: CSD A7 (db-person); notified 06:16, 15 August 2021 (UTC)
* Nimesh gurung: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Nimesh Gurung}; notified 06:36, 15 August 2021 (UTC)
* Hafiz Ahmad Amin: CSD A7 (db-band); notified 06:46, 15 August 2021 (UTC)
* Nandu (Hindi actor): CSD G2 (db-test); notified 07:56, 15 August 2021 (UTC)
* Huddo May: CSD A7 (db-band); notified 07:58, 15 August 2021 (UTC)
* Yungeen Ace: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Yungeen Ace}; notified 13:11, 15 August 2021 (UTC)
* A C Kadloor: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/A C Kadloor}; notified 21:07, 15 August 2021 (UTC)
* Wattdj: CSD A1 (db-nocontext); notified 12:38, 17 August 2021 (UTC)
* Meghranjani Medhi: CSD A7 (db-person); notified 18:45, 17 August 2021 (UTC)
* Dixon waz: CSD A7 (db-person); notified 20:32, 17 August 2021 (UTC)
* Dixson Waz: CSD A7 (db-band); notified 20:33, 17 August 2021 (UTC)
* Takae Itō: CSD G6 (db-g6); additional information: {G6 rationale: Unnecessary disambig page } 01:30, 18 August 2021 (UTC)
* Dennis Cartier: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Dennis Cartier}; notified 22:22, 18 August 2021 (UTC)
* MoneyBroz Records: CSD A7 (db-corp); notified 23:25, 18 August 2021 (UTC)
* Md Asiful Islam (Scientist): CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Md Asiful Islam}; notified 06:30, 19 August 2021 (UTC)
* Bikram Malati Show: CSD A7 (db-web); notified 10:07, 19 August 2021 (UTC)
* Embassy of Germany, Paris: CSD A7 (db-corp); notified 19:13, 19 August 2021 (UTC)
* Uday Ali Pabrai: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Uday Ali Pabrai}; notified 04:19, 20 August 2021 (UTC)
* Talia Mar: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Talia Mar}; notified 04:22, 20 August 2021 (UTC)
* Adewumi Idowu Paul: CSD A7 (db-person); notified 04:55, 20 August 2021 (UTC)
* Craig Davidson (rugby union): CSD G7 (db-author) 20:54, 21 August 2021 (UTC)
* Naval Infantry Armed Services: CSD G6 (db-g6); additional information: {G6 rationale: Need to free up title for page move ref talk page of Naval Infantry Arms} 05:57, 22 August 2021 (UTC)
* "Draft:"Alessandro Serpieri: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft: Alessandro Serpieri}; notified 13:07, 22 August 2021 (UTC)
* Rachna Chhachhi: CSD G11 (db-spam); notified 07:05, 23 August 2021 (UTC)
* Church of Sant'Anselmo on the Aventine: CSD A10 (db-a10); additional information: {A10 article: Sant'Anselmo all'Aventino}; notified 09:05, 23 August 2021 (UTC)
* DJ FR OFFICIAL: CSD A7 (db-person); notified 21:23, 23 August 2021 (UTC)
* Gia Jichonaia: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Gia Jichonaia}; notified 21:44, 23 August 2021 (UTC)
* Anu K Aniyan: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Anu K Aniyan}; notified 04:54, 24 August 2021 (UTC)
* Deputy Station Master: CSD A7 (db-club); notified 04:59, 24 August 2021 (UTC)
* Yo Yo Alok King: CSD A7 (db-band); notified 04:18, 25 August 2021 (UTC)
* KARMA: CSD A7 (db-person); notified 04:19, 25 August 2021 (UTC)
* Insta X: CSD A7 (db-band); notified 04:20, 25 August 2021 (UTC)
* Rachna Chhachhi: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Rachna Chhachhi}; notified 07:04, 25 August 2021 (UTC)
* Aileen Regio: CSD A7 (db-person); notified 11:26, 26 August 2021 (UTC)
* Mugen Rao: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Mugen Rao}; notified 11:32, 28 August 2021 (UTC)
* Jafiey: CSD G11 (db-spam); notified 18:05, 28 August 2021 (UTC)
* Maha wajahat: CSD A7 (db-person); notified 18:08, 28 August 2021 (UTC)
* Joel P. West: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Joel P. West}; notified 20:41, 28 August 2021 (UTC)
* Sayyed Mohammad Ahmad: CSD A7 (db-person); notified 05:15, 29 August 2021 (UTC)
* Dabang delhi: CSD A1 (db-nocontext); notified 05:16, 29 August 2021 (UTC)
* DWCS-FM: CSD G6 (db-copypaste); additional information: {G6 sourcepage: draft:DWCS-FM}; notified 11:48, 29 August 2021 (UTC)
September 2021
* "Wayne Adrian Davis": CSD G7 (db-author) 07:16, 2 September 2021 (UTC)
* Emilie Asselin: CSD G7 (db-author) 07:51, 2 September 2021 (UTC)
* 2MIA FM 95.1: CSD A7 (db-corp); notified 12:43, 2 September 2021 (UTC)
* Daymak: CSD A7 (db-corp); notified 18:35, 3 September 2021 (UTC)
* Tv gospel hour: CSD G7 (db-author) 14:48, 4 September 2021 (UTC)
* Jawaharlal Nehru University alumni: CSD A10 (db-a10); additional information: {A10 article: List of Jawaharlal Nehru University people}; notified 05:30, 5 September 2021 (UTC)
* Shahzad Dana: CSD G11 (db-spam); notified 05:52, 6 September 2021 (UTC)
* Shivam Bangwal: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Shivam Bangwal}; notified 06:34, 10 September 2021 (UTC)
* Kota Venkatachalam: CSD G12 (db-copyvio); additional information: {G12 url: https://www.shikshabhartinetwork.com/dayinhistory.php?eventId=3166}; notified 06:37, 10 September 2021 (UTC)
* Artto: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Artto}; notified 07:59, 11 September 2021 (UTC)
* Sepehr Sepi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sepehr Sepi}; notified 22:14, 12 September 2021 (UTC)
* Falling Into Your Smile: CSD G12 (db-copyvio); additional information: {G12 url: https://www.viki.com/tv/37358c-falling-into-your-smile}; notified 19:38, 14 September 2021 (UTC)
* List of motte-and-bailey castles in Belgium: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:List of motte-and-bailey castles in Belgium}; notified 20:43, 14 September 2021 (UTC)
* Adegoke Olubummo: CSD G12 (db-copyvio); additional information: {G12 url: http://www.math.buffalo.edu/mad/PEEPS/olubummo_adegoke.html}; notified 12:10, 15 September 2021 (UTC)
* Kai Phyo Aung: CSD A7 (db-band); notified 06:35, 16 September 2021 (UTC)
* Moulavi Vakkom Khader: CSD G12 (db-copyvio); additional information: {G12 url: http://indianmuslimlegends.blogspot.com/2011/02/vakkom-moulavi.html}; notified 06:15, 19 September 2021 (UTC)
* Moulavi Vakkom Khader: CSD A10 (db-a10); additional information: {A10 article: Vakkom Moulavi}; notified 06:49, 19 September 2021 (UTC)
* Skydive Space Center: CSD G11 (db-spam); notified 21:47, 19 September 2021 (UTC)
* Sharma boy discography: CSD A7 (db-band); notified 06:08, 22 September 2021 (UTC)
* Sharma boy: CSD A7 (db-band); notified 06:10, 22 September 2021 (UTC)
* QOUTE Freaks: CSD A3 (db-nocontent); notified 20:45, 23 September 2021 (UTC)
* Yousfia Islamic English Medium School Dangiwacha: CSD A7 (db-corp); notified 21:26, 23 September 2021 (UTC)
* Ben Britton (actor and teacher): CSD A7 (db-person); notified 03:30, 24 September 2021 (UTC)
* Kuwait Society in Scotland: CSD A7 (db-corp); notified 12:35, 24 September 2021 (UTC)
* Aryan Kumar Singh: CSD A7 (db-person); notified 16:19, 24 September 2021 (UTC)
* Studio Pango: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Studio Pango}; notified 16:21, 24 September 2021 (UTC)
* Chon Shiryu: CSD G7 (db-author) 02:32, 25 September 2021 (UTC)
* Md Ilias Ali (Politician): CSD G7 (db-author) 08:08, 25 September 2021 (UTC)
* Armando Ferreira Alvares: CSD A7 (db-person); notified 01:41, 26 September 2021 (UTC)
* HeyAlihaider: CSD A7 (db-band); notified 12:30, 27 September 2021 (UTC)
* Eduardo Behrentz: CSD G7 (db-author) 19:19, 27 September 2021 (UTC)
* Hitesh C. Soni: CSD G11 (db-spam); notified 22:59, 28 September 2021 (UTC)
* Md Mehedi Hasan: CSD A7 (db-person); notified 06:14, 29 September 2021 (UTC)
* Rithu Akarsha: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Rithu Akarsha}; notified 06:29, 29 September 2021 (UTC)
* J. Sai Deepak: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/J. Sai Deepak}; notified 05:56, 30 September 2021 (UTC)
* Satheeshan Rathnayaka: CSD A7 (db-band); notified 19:49, 30 September 2021 (UTC)
* Kush Maini: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Kush Maini}; notified 21:02, 30 September 2021 (UTC)
October 2021
* Fraz Wahlah: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Fraz Wahlah}; notified 03:24, 1 October 2021 (UTC)
* Artin vosoughi: CSD G7 (db-author) 11:04, 1 October 2021 (UTC)
* ESanjeevani OPD: CSD G12 (db-copyvio); additional information: {G12 url: https://dialcare.in/online-doctor-consultation-free-in-india/}; notified 09:10, 3 October 2021 (UTC)
* Ayoub El Maroufi: CSD A7 (db-band); notified 11:58, 4 October 2021 (UTC)
* Elijah Yates: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Elijah Yates}; notified 23:22, 5 October 2021 (UTC)
* Meri Doli Mere Angana: CSD G1 (db-nonsense); notified 05:56, 6 October 2021 (UTC)
* Www.giantscauseway.tours: CSD G11 (db-spam); notified 11:40, 6 October 2021 (UTC)
* Brendon Ellis: CSD A7 (db-person); notified 21:11, 6 October 2021 (UTC)
* Dreaming records: CSD G11 (db-spam); notified 06:56, 7 October 2021 (UTC)
* List of international goals scored by Islam Slimani: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of international goals scored by Islam Slimani}; notified 20:37, 9 October 2021 (UTC)
* Arofaus/kii: CSD G7 (db-author) 20:08, 11 October 2021 (UTC)
* Beach hazards statement: CSD G12 (db-copyvio); additional information: {G12 url: https://forecast.weather.gov/wwamap/wwatxtget.php?cwa=akq&wwa=beach%20hazards%20statement}; notified 20:13, 11 October 2021 (UTC)
* High surf advisory: CSD G12 (db-copyvio); additional information: {G12 url: https://forecast.weather.gov/wwamap/wwatxtget.php?cwa=usa&wwa=high%20surf%20advisory}; notified 20:17, 11 October 2021 (UTC)
* Ivan Serebrennikov: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Ivan Serebrennikov}; notified 20:20, 11 October 2021 (UTC)
* Tonny Oryem: CSD A7 (db-person); notified 21:14, 13 October 2021 (UTC)
* User:Mccapra/Arias: CSD G8 (db-g8); additional information: {G8 rationale: Was going to translate from es.wiki but can’t find any sources } 19:50, 18 October 2021 (UTC)
* User:Mccapra/Arias: CSD G7 (db-author); additional information: {G7 rationale: Was going to translate from es.wiki but can’t find any sources.} 19:51, 18 October 2021 (UTC)
* Jim Field illustrator: CSD A7 (db-person); notified 20:32, 20 October 2021 (UTC)
* McDollars: CSD A7 (db-person); notified 09:01, 23 October 2021 (UTC)
* Republic of King Mosha Campus: CSD A7 (db-person); notified 10:51, 23 October 2021 (UTC)
* Chandra Mohan Jayaramaiah (C M): CSD A7 (db-person); notified 10:53, 23 October 2021 (UTC)
* Manoj Dey: CSD A7 (db-person); notified 08:27, 24 October 2021 (UTC)
* Hathaway Shepherd: CSD A7 (db-person); notified 22:21, 24 October 2021 (UTC)
* Reza Tajbakhsh: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Reza Tajbakhsh}; notified 11:36, 25 October 2021 (UTC)
* Shirdale: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Shirdale}; notified 21:57, 26 October 2021 (UTC)
* Henry Oaminal Sr.: CSD G7 (db-author) 09:06, 27 October 2021 (UTC)
* Randy Kristoforus Senduk: CSD A7 (db-person); notified 12:52, 27 October 2021 (UTC)
* Tongbram Robindro Singh: CSD A7 (db-person); notified 12:52, 27 October 2021 (UTC)
* Nishant Sharma: CSD A7 (db-person); notified 08:10, 28 October 2021 (UTC)
* S-Nashiik: CSD A7 (db-corp); notified 11:52, 28 October 2021 (UTC)
* Adnan Faiz: CSD A7 (db-person); notified 20:03, 28 October 2021 (UTC)
* List of historical monuments in Qatar: CSD G12 (db-copyvio); additional information: {G12 url: https://qatarmuseumsstorageprd.blob.core.windows.net/media/documents/QM_heritage_sites_English.pdf}; notified 06:58, 29 October 2021 (UTC)
* Koona Sree Sai Sandeep: CSD A7 (db-person); notified 10:02, 31 October 2021 (UTC)
November 2021
* Beanstain angel: CSD A11 (db-madeup); notified 12:56, 1 November 2021 (UTC)
* Eghosa Anglican Grammar School: CSD G12 (db-copyvio); additional information: {G12 url: https://eghosaoldboyshouston.org/our-history/}; notified 22:11, 1 November 2021 (UTC)
* Julia Johnstone (Julia Storer): CSD G6 (db-copypaste); additional information: {G6 sourcepage: https://en.wikipedia.org/wiki/Josiah_Cottin}; notified 07:09, 2 November 2021 (UTC)
* Julia Johnstone (Julia Storer): CSD A10 (db-a10); additional information: {A10 article: Josiah Cottin }; notified 07:11, 2 November 2021 (UTC)
* Kuruluş: Osman (season 3): CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Kuruluş: Osman (season 3)}; notified 06:42, 3 November 2021 (UTC)
* EM10000 2: CSD G7 (db-author) 23:44, 4 November 2021 (UTC)
* Barbi Afrika: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Barbi Afrika}; notified 23:34, 5 November 2021 (UTC)
* London Business E-School: CSD G11 (db-spam); notified 22:05, 6 November 2021 (UTC)
* Rayan Baghdadi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Rayan Baghdadi}; notified 08:41, 7 November 2021 (UTC)
* Morattu single of TamilNadu: CSD G1 (db-nonsense); notified 09:17, 7 November 2021 (UTC)
* Philip Robert Anstruther: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Philip Robert Anstruther}; notified 07:42, 8 November 2021 (UTC)
* Dhananjay Das Kathiababa: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:Dhananjay Das Kathiababa}; notified 22:22, 8 November 2021 (UTC)
* Fenix outdoors: CSD A7 (db-corp); notified 22:33, 8 November 2021 (UTC)
* Bikash Basnet: CSD A7 (db-person); notified 14:31, 9 November 2021 (UTC)
* Dr. Mrinmoy Debnath: CSD G1 (db-nonsense); notified 14:50, 10 November 2021 (UTC)
* Antonio Maceo monument, Havana: CSD G12 (db-copyvio); additional information: {G12 url: https://equestrianstatue.org/maceo-antonio/}; notified 14:59, 10 November 2021 (UTC)
* Jyothish p jayakumar: CSD A7 (db-person); notified 17:26, 10 November 2021 (UTC)
* Abhishek Yadav (IPS): CSD A7 (db-person); notified 06:33, 11 November 2021 (UTC)
* Edlose Diaz: CSD G7 (db-author) 16:29, 11 November 2021 (UTC)
* List of earlier known date deaths: CSD A11 (db-madeup); notified 20:14, 11 November 2021 (UTC)
* Pepperoni road: CSD G1 (db-nonsense); notified 20:44, 11 November 2021 (UTC)
* Emillos pizza town: CSD G1 (db-nonsense); notified 20:45, 11 November 2021 (UTC)
* Soldaty: CSD A3 (db-nocontent); notified 04:24, 12 November 2021 (UTC)
* List of earlier known date deaths: CSD A11 (db-madeup); notified 11:39, 12 November 2021 (UTC)
* OBN Horn of Africa: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft:OBN Horn of Africa}; notified 20:01, 12 November 2021 (UTC)
* Miss Teen Supranational: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Miss Teen Supranational}; notified 09:44, 13 November 2021 (UTC)
* Shahid Shafi: CSD A7 (db-person); notified 08:41, 14 November 2021 (UTC)
* Draff:John Herbert Roper: CSD G7 (db-author) 14:40, 15 November 2021 (UTC)
* OSAM (Belarus): CSD G7 (db-author) 18:28, 15 November 2021 (UTC)
* Raphael Dakik: CSD G11 (db-spam); notified 12:24, 16 November 2021 (UTC)
* Tommy Jonathan Sinaga: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Tommy Jonathan Sinaga}; notified 13:12, 18 November 2021 (UTC)
* Hafiz Hamidun: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Hafiz Hamidun}; notified 08:04, 19 November 2021 (UTC)
* Shivani Rajasekhar: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Shivani Rajasekhar}; notified 07:20, 20 November 2021 (UTC)
* Jefferson Lobo: CSD A7 (db-band); notified 10:44, 20 November 2021 (UTC)
* SfNllnVEhZ0: CSD G11 (db-spam); notified 21:25, 20 November 2021 (UTC)
* Mars Government: CSD A11 (db-madeup); notified 11:55, 21 November 2021 (UTC)
* Hardik Akbari: CSD G11 (db-spam); notified 19:25, 21 November 2021 (UTC)
* A Certain Energy (Musician): CSD A7 (db-band); notified 19:35, 21 November 2021 (UTC)
* Thar Process: CSD G11 (db-spam); notified 00:01, 23 November 2021 (UTC)
* Bahrain Ministry of Interior Tennis Challenger: CSD A7 (db-event); notified 00:04, 23 November 2021 (UTC)
* SudheerAttavar: CSD G6 (db-copypaste); additional information: {G6 sourcepage: draft:SudheerAttavar}; notified 05:41, 23 November 2021 (UTC)
* Mamta Panwar: CSD A7 (db-band); notified 07:28, 24 November 2021 (UTC)
* Somya Daundkar: CSD A7 (db-band); notified 07:30, 24 November 2021 (UTC)
* Somya Daundkar: CSD A7 (db-person); notified 11:29, 24 November 2021 (UTC)
* Paul Enenche: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Paul Enenche}; notified 22:22, 25 November 2021 (UTC)
* Dambady: CSD A3 (db-nocontent); notified 07:01, 26 November 2021 (UTC)
* YNW Sakchaser: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/YNW Sakchaser}; notified 07:59, 26 November 2021 (UTC)
* Sardar Fateh Muhammad Khan Karelvi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Fateh Muhammad Khan Karelvi}; notified 22:27, 26 November 2021 (UTC)
* Santadas Kathiababa: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Dhananjay Das Kathiababa}; notified 17:24, 27 November 2021 (UTC)
* Nicaragua at major beauty pageants: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/France at major beauty pageants}; notified 04:13, 28 November 2021 (UTC)
* Walter Nandalike: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Walter Nandalike}; notified 10:32, 29 November 2021 (UTC)
December 2021
* Tayyab Mahmood Sheikh: CSD A7 (db-person); notified 12:15, 4 December 2021 (UTC)
* Mominul Haq: CSD A7 (db-band); notified 14:14, 5 December 2021 (UTC)
* Tayyab Mahmood Sheikh: CSD A7 (db-person); notified 10:01, 6 December 2021 (UTC)
* Professional gemstone testing laboratory: CSD A7 (db-corp); notified 20:42, 6 December 2021 (UTC)
* Wahaj Ahmed: CSD A7 (db-person); notified 11:55, 7 December 2021 (UTC)
* Mohamad ghorbani ghomshi: CSD A7 (db-person); notified 11:29, 10 December 2021 (UTC)
* Dusty Locane: CSD A7 (db-band); notified 21:16, 10 December 2021 (UTC)
* List of living former United States senators: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of living former United States senators}; notified 17:43, 12 December 2021 (UTC)
* List of living former members of the United States House of Representatives: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of living former United States senators}; notified 17:47, 12 December 2021 (UTC)
* List of living former United States Governors: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of living former United States governors}; notified 18:26, 12 December 2021 (UTC)
* Illusion Museum Erbil: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Illusion Museum Erbil}; notified 18:35, 12 December 2021 (UTC)
* List of longest-living United States senators: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of longest-living United States senators}; notified 18:37, 12 December 2021 (UTC)
* Habibani: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Habibani}; notified 07:39, 13 December 2021 (UTC)
* Drasar Monumental: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Drasar Monumental}; notified 07:42, 13 December 2021 (UTC)
* Gui Poh Choon: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Gui Poh Choon}; notified 07:47, 13 December 2021 (UTC)
* Dr. Azhar Qayyum: CSD A7 (db-person); notified 07:48, 13 December 2021 (UTC)
* Category;Cambodian people of Indonesian descent: CSD G6 (db-g6); additional information: {G6 rationale: Not a category } 13:19, 13 December 2021 (UTC)
* Dipak Majumdar: CSD A7 (db-person); notified 13:29, 13 December 2021 (UTC)
* Ramana Sayahi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ramana Sayahi}; notified 21:37, 13 December 2021 (UTC)
* Dr Bhartendra Arun: CSD G7 (db-author); additional information: {G7 rationale: Mistaken creation } 18:31, 14 December 2021 (UTC)
* Malvika Raaj: CSD A3 (db-nocontent); notified 08:40, 15 December 2021 (UTC)
* Rinzing Denzongpa: CSD A3 (db-nocontent); notified 08:40, 15 December 2021 (UTC)
* Bashir Haj Ali: CSD G6 (db-copypaste); additional information: {G6 sourcepage: https://en.wikipedia.org/wiki/Draft:Bashir_Haj_Ali}; notified 10:51, 15 December 2021 (UTC)
* Pictionstar: CSD A7 (db-corp); notified 11:56, 17 December 2021 (UTC)
* Syed Ahmed Shah: CSD A7 (db-person); notified 22:14, 17 December 2021 (UTC)
* Shanu Kumar: CSD A7 (db-person); notified 06:01, 18 December 2021 (UTC)
* Samira Khan Mahi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Samira Khan Mahi}; notified 06:44, 19 December 2021 (UTC)
* Aaron Forwell: CSD A7 (db-band); notified 14:11, 19 December 2021 (UTC)
* Kazamjikh: CSD A11 (db-madeup); notified 23:37, 19 December 2021 (UTC)
* Catergory:National Historic Sites in Tanga Region: CSD A3 (db-nocontent); notified 08:49, 20 December 2021 (UTC)
* Wode Maya: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Wode Maya}; notified 23:42, 20 December 2021 (UTC)
* SAMBA FC CHATHAMANGALAM: CSD A7 (db-club); notified 08:39, 22 December 2021 (UTC)
* CITY TIGERS FC CHATHAMANGALAM: CSD A7 (db-club); notified 08:40, 22 December 2021 (UTC)
* ZIDAN FC CHATHAMANGALAM: CSD A7 (db-club); notified 08:40, 22 December 2021 (UTC)
* NFC CHATHAMANGALAM: CSD A7 (db-club); notified 08:41, 22 December 2021 (UTC)
* Kiron Shikder: CSD A7 (db-person); notified 08:46, 23 December 2021 (UTC)
* Vaishanar Chatterjee: CSD A7 (db-person); notified 13:52, 23 December 2021 (UTC)
* Mass Resistence conservative group: CSD A10 (db-a10); additional information: {A10 article: MassResistance}; notified 13:54, 23 December 2021 (UTC)
* Ethnic African Americans: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/African Americans (ethnicity)}; notified 02:41, 26 December 2021 (UTC)
* Luke Miani: CSD A7 (db-person); notified 20:51, 27 December 2021 (UTC)
* Sth Nahiyan: CSD A7 (db-band); notified 20:02, 29 December 2021 (UTC)
* About example users: CSD A1 (db-nocontext); notified 21:46, 30 December 2021 (UTC)
* Sandeep Nailwal: CSD A7 (db-person); notified 22:24, 30 December 2021 (UTC)
* P. K. Firos: CSD A7 (db-person); notified 22:26, 30 December 2021 (UTC)
* Feroz Award for Best Main Actor in a Film: CSD A10 (db-a10); additional information: {A10 article: Feroz Awards}; notified 23:19, 30 December 2021 (UTC)
* Thabang JR Mofokeng: CSD A7 (db-person); notified 08:32, 31 December 2021 (UTC)
* Idi Barde Gubana: CSD G6 (db-copypaste); additional information: {G6 sourcepage: Draft: Idi Barde Gubana}; notified 13:28, 31 December 2021 (UTC)
* Vladimir D. Bulaong: CSD A7 (db-person); notified 13:29, 31 December 2021 (UTC)
January 2022
* Mohd Kaifi Warsi: CSD A7 (db-person); notified 10:19, 2 January 2022 (UTC)
* Fayzo Pro: CSD A7 (db-person); notified 09:46, 3 January 2022 (UTC)
* Rik tinory: CSD A11 (db-madeup); notified 22:23, 3 January 2022 (UTC)
* Jeet trivedi: CSD A7 (db-person); notified 12:56, 5 January 2022 (UTC)
* Baconville: CSD G1 (db-nonsense); notified 14:20, 5 January 2022 (UTC)
* Ross Otterman: CSD A7 (db-person); notified 20:46, 5 January 2022 (UTC)
* List of ecoregions in São Tomé and Príncipe: CSD A10 (db-a10); additional information: {A10 article: São Tomé, Príncipe, and Annobón forests}; notified 22:08, 6 January 2022 (UTC)
* Pcx1 present - Prabuddha Dissanayake - pcx1network owner and founder: CSD A7 (db-person); notified 16:45, 7 January 2022 (UTC)
* Kasur District Chess Association: CSD A7 (db-club); notified 22:29, 7 January 2022 (UTC)
* Nadeem khan: CSD G7 (db-author) 14:25, 8 January 2022 (UTC)
* List of obscure historical nations: CSD A7 (db-person); notified 22:37, 9 January 2022 (UTC)
* American descendants of slavery (ethnicity): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/African Americans (ethnicity)}; notified 19:52, 10 January 2022 (UTC)
* Saint-Simon, Bas-Saint-Laurent, Quebec: CSD G7 (db-author) 00:28, 11 January 2022 (UTC)
* Sanjaysinh Sukhdevsinh Gohil: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sanjaysinh Sukhdevsinh Gohil}; notified 09:17, 11 January 2022 (UTC)
* Aryan Verma: CSD A7 (db-person); notified 08:00, 18 January 2022 (UTC)
February 2022
* Junagadh and Manavadar: CSD A10 (db-a10); additional information: {A10 article: Junagadh State, Bantva Manavadar}; notified 04:47, 10 February 2022 (UTC)
* Rohit joshua.k: CSD A7 (db-person); notified 04:49, 10 February 2022 (UTC)
* The Spanish Habsburgs monarchs during Spanish Empire: CSD A10 (db-a10); additional information: {A10 article: Habsburg Spain}; notified 08:12, 10 February 2022 (UTC)
* Armed Forces Senior High Technical School: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ghana Armed Forces Senior High School}; notified 03:45, 12 February 2022 (UTC)
* Daniel Larze: CSD G7 (db-author) 04:58, 17 February 2022 (UTC)
* Daniel Larze: CSD A7 (db-person); notified 07:03, 17 February 2022 (UTC)
* D00nik: CSD A7 (db-person); notified 07:59, 18 February 2022 (UTC)
* Rob kirkland: CSD A10 (db-a10); additional information: {A10 article: Rob Kirkland}; notified 08:01, 18 February 2022 (UTC)
* 1st Lt Robert L. Hite: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Robert L. Hite}; notified 20:50, 22 February 2022 (UTC)
* Lillian Priest (public servant): CSD A7 (db-person); notified 20:51, 22 February 2022 (UTC)
* Manzoor Bhat: CSD A7 (db-person); notified 21:06, 22 February 2022 (UTC)
March 2022
* Hurricane Henry (2021): CSD G7 (db-author) 23:44, 4 March 2022 (UTC)
* Paw Oo Longyi: CSD A7 (db-corp); notified 08:25, 8 March 2022 (UTC)
* CRITICS & METHODES: CSD G1 (db-nonsense); notified 22:03, 8 March 2022 (UTC)
* Audire Sound: CSD G7 (db-author) 22:04, 8 March 2022 (UTC)
* Paw Oo Longyi: CSD A7 (db-corp); notified 03:10, 9 March 2022 (UTC)
* HMS Fame (1666): CSD G7 (db-author) 03:12, 9 March 2022 (UTC)
* Ethelie Evelyn: CSD G7 (db-author) 22:14, 10 March 2022 (UTC)
* Alyssa Gadson: CSD A7 (db-person); notified 12:53, 11 March 2022 (UTC)
* Vibhu Varshney: CSD A7 (db-person); notified 14:17, 11 March 2022 (UTC)
* Ifedayo Durosinmi-Etti: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ifedayo Durosinmi-Etti}; notified 12:47, 12 March 2022 (UTC)
* This is a new page: CSD G1 (db-nonsense); notified 19:51, 13 March 2022 (UTC)
* Rudolfo Fernandes (politician): CSD G7 (db-author) 19:56, 13 March 2022 (UTC)
* Habib Sabagh Rahme: CSD A7 (db-person); notified 13:09, 17 March 2022 (UTC)
* Nathan Urban: CSD A7 (db-person); notified 21:58, 17 March 2022 (UTC)
* Shailesh Singh Shailu: CSD A7 (db-person); notified 22:04, 17 March 2022 (UTC)
* Global Networks & Reliable Solutions: CSD G3 (db-hoax); notified 14:39, 20 March 2022 (UTC)
* Bis TV: CSD A3 (db-nocontent); notified 14:40, 20 March 2022 (UTC)
* Pudukottai Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://tnhighways.tn.gov.in/en/odr-pudukkottai-candm}; notified 11:31, 27 March 2022 (UTC)
* Trichy Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://tnhighways.tn.gov.in/en/odr-trichy-candm}; notified 11:33, 27 March 2022 (UTC)
* Ariyalur Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://tnhighways.tn.gov.in/en/odr-ariyalur-candm}; notified 11:35, 27 March 2022 (UTC)
* Cuddalore Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://tnhighways.tn.gov.in/en/odr-cuddalore-candm}; notified 11:36, 27 March 2022 (UTC)
* Kallakurichi Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://tnhighways.tn.gov.in/en/odr-kallakurichi-candm}; notified 11:37, 27 March 2022 (UTC)
* Villupuram Division (Highways): CSD G12 (db-copyvio); additional information: {G12 url: https://www.tnhighways.tn.gov.in/index.php/en/odr-villupuram-candm}; notified 11:39, 27 March 2022 (UTC)
* Dhiren Bhagat: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Dhiren Bhagat}; notified 21:10, 30 March 2022 (UTC)
* Feyzullah Aktürk: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Feyzullah Aktürk}; notified 21:17, 30 March 2022 (UTC)
April 2022
* Fabrizio Campelli: CSD A7 (db-person); notified 02:57, 4 April 2022 (UTC)
* TST Satanism (disambiguation): CSD G7 (db-author) 22:54, 12 April 2022 (UTC)
* Jahanzaib Hussain: CSD G12 (db-copyvio); additional information: {G12 url: https://www.hmagpak.com/23-Jun-2020/in-conversation-with-rising-filmmaker-jahanzaib-hussain}; notified 05:03, 13 April 2022 (UTC)
* Sabizabulin: CSD A3 (db-nocontent); notified 21:01, 17 April 2022 (UTC)
* Piperitsa, Messenia: CSD A2 (db-foreign); additional information: {A2 source: https://el.wikipedia.org/wiki/%CE%A0%CE%B9%CF%80%CE%B5%CF%81%CE%AF%CF%84%CF%83%CE%B1_%CE%9C%CE%B5%CF%83%CF%83%CE%B7%CE%BD%CE%AF%CE%B1%CF%82}; notified 10:51, 18 April 2022 (UTC)
May 2022
* Eritrean Giro d'Italia stage winners: CSD G7 (db-author) 20:40, 23 May 2022 (UTC)
June 2022
* Dr. Pradeepa Sudhakar: CSD A7 (db-person); notified 10:16, 3 June 2022 (UTC)
* Parlin Gressitt: CSD A7 (db-person); notified 12:34, 4 June 2022 (UTC)
* Kiirya Beats: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Kiirya Beats}; notified 04:10, 5 June 2022 (UTC)
* Tibeauthetraveler: CSD A7 (db-band); notified 07:46, 8 June 2022 (UTC)
* Mehdi Monir: CSD A7 (db-band); notified 21:24, 10 June 2022 (UTC)
* The features of Shia' jurisprudence: CSD A10 (db-a10); additional information: {A10 article: Jaʽfari jurisprudence}; notified 21:52, 10 June 2022 (UTC)
* Shammi Jalandhari: CSD A7 (db-person); notified 04:54, 11 June 2022 (UTC)
* Ajoy Hijam: CSD A7 (db-person); notified 22:51, 11 June 2022 (UTC)
* Sematary: CSD A7 (db-band); notified 08:48, 12 June 2022 (UTC)
* Colors Odia: CSD A3 (db-nocontent); notified 08:49, 12 June 2022 (UTC)
* MD Abdus Sattar: CSD A7 (db-person); notified 13:11, 13 June 2022 (UTC)
* Ravi Mehrotra: CSD A7 (db-person); notified 07:49, 14 June 2022 (UTC)
* Shooting at the 2024 Summer Olympics: CSD G7 (db-author) 08:00, 14 June 2022 (UTC)
* Shattered Island (Skylanders): CSD G7 (db-author) 03:14, 15 June 2022 (UTC)
* Lyndon Barbers: CSD A7 (db-person); notified 12:45, 25 June 2022 (UTC)
* Dikko Umaru Radda: CSD G12 (db-copyvio); additional information: {G12 url: https://smedan.gov.ng/dgs-office/}; notified 19:45, 25 June 2022 (UTC)
* Polarity therapy: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Polarity therapy}; notified 20:26, 25 June 2022 (UTC)
* Jayniac Jr.: CSD A7 (db-band); notified 12:01, 26 June 2022 (UTC)
* Lagging (TV series): CSD A3 (db-nocontent); notified 12:04, 26 June 2022 (UTC)
* Kipton Cariaga: CSD A7 (db-person); notified 22:28, 27 June 2022 (UTC)
* E.R.K Group of Institutions: CSD A7 (db-corp); notified 12:40, 28 June 2022 (UTC)
* Jojo Soria de Veyra: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Vicente-Ignacio Soria de Veyra}; notified 05:46, 29 June 2022 (UTC)
July 2022
* Charles Wells Russell Jr.: CSD G7 (db-author) 20:17, 1 July 2022 (UTC)
* Tunisia women's national under-18 3x3 team: CSD A7 (db-club); notified 19:19, 4 July 2022 (UTC)
* Tunisia men's national under-18 3x3 team: CSD A7 (db-club); notified 19:19, 4 July 2022 (UTC)
* Tunisia women's national under-23 3x3 team: CSD A7 (db-club); notified 19:21, 4 July 2022 (UTC)
* Tunisia men's national under-23 3x3 team: CSD A7 (db-club); notified 19:21, 4 July 2022 (UTC)
* Haim Cohen: CSD A7 (db-person); notified 19:27, 4 July 2022 (UTC)
* Zacharia Matur Makuer: CSD G7 (db-author) 12:00, 6 July 2022 (UTC)
* Y Glaslanciau: CSD A7 (db-band); notified 22:02, 6 July 2022 (UTC)
* Umid Zokirov: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Umid Zokirov}; notified 11:52, 10 July 2022 (UTC)
* Who is xiao ling: CSD G1 (db-nonsense); notified 14:53, 11 July 2022 (UTC)
* Abudu Postoffice, Aibiokunla: CSD A7 (db-corp); notified 12:28, 13 July 2022 (UTC)
* Bwari Postoffice, Abuja: CSD A7 (db-corp); notified 12:31, 13 July 2022 (UTC)
* Marina Postoffice, Lagos: CSD A7 (db-corp); notified 12:32, 13 July 2022 (UTC)
* Prabhjeet singh: CSD A7 (db-person); notified 04:26, 15 July 2022 (UTC)
* New Zealand biblical scholars: CSD G6 (db-g6); additional information: {G6 rationale: Intended to be a category not an article } 08:01, 15 July 2022 (UTC)
* David Koffi: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/David Koffi}; notified 17:48, 16 July 2022 (UTC)
* Abdellatif Aboukoura: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Abdellatif Aboukoura}; notified 17:52, 16 July 2022 (UTC)
* Chief Dakota Burgess: CSD A7 (db-person); notified 22:41, 17 July 2022 (UTC)
* Manjari TV: CSD G7 (db-author) 16:07, 19 July 2022 (UTC)
* Ollywood TV: CSD G7 (db-author) 16:08, 19 July 2022 (UTC)
* Odisha Plus: CSD G7 (db-author) 16:08, 19 July 2022 (UTC)
* Odisha Television Ltd: CSD G7 (db-author) 16:09, 19 July 2022 (UTC)
* Dhanraj Acharya: CSD G12 (db-copyvio); additional information: {G12 url: https://english.onlinekhabar.com/dhana-raj-acharya-pokhara-mayor.html}; notified 07:53, 23 July 2022 (UTC)
* Abdul Bashir - (AB): CSD A7 (db-person); notified 20:06, 23 July 2022 (UTC)
* Sean Elo-Rivera: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sean Elo-Rivera}; notified 20:08, 23 July 2022 (UTC)
* Sphinx album: CSD G7 (db-author) 03:43, 25 July 2022 (UTC)
* Simon B. Harry: CSD G12 (db-copyvio); additional information: {G12 url: https://businessday.ng/news/article/what-you-need-to-know-about-the-late-simon-harry/}; notified 21:05, 25 July 2022 (UTC)
* উইকিপিডিয়া: শর্টকাট: CSD A2 (db-foreign); additional information: {A2 source: https://bn.wikipedia.org/wiki/%E0%A6%89%E0%A6%87%E0%A6%95%E0%A6%BF%E0%A6%AA%E0%A6%BF%E0%A6%A1%E0%A6%BF%E0%A6%AF%E0%A6%BC%E0%A6%BE:%E0%A6%95%E0%A7%80%E0%A6%AC%E0%A7%8B%E0%A6%B0%E0%A7%8D%E0%A6%A1_%E0%A6%B6%E0%A6%B0%E0%A7%8D%E0%A6%9F%E0%A6%95%E0%A6%BE%E0%A6%9F}; notified 11:09, 27 July 2022 (UTC)
* Furia (esports): CSD G7 (db-author) 20:37, 27 July 2022 (UTC)
* Abdullah AL Mamun: CSD A7 (db-person); notified 22:29, 28 July 2022 (UTC)
* David Ghassabi: CSD A7 (db-person); notified 20:56, 29 July 2022 (UTC)
* Advocate Harjinder Singh Dhami: CSD A7 (db-person); notified 05:58, 30 July 2022 (UTC)
August 2022
* Nithra Apps India Private Limited: CSD A7 (db-corp); notified 07:00, 1 August 2022 (UTC)
* Ndayizeye Emmanuel: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ndayizeye Emmanuel}; notified 08:10, 5 August 2022 (UTC)
* Lorelle George: CSD A7 (db-person); notified 08:11, 5 August 2022 (UTC)
* Statues in Motion: CSD A7 (db-band); notified 09:12, 5 August 2022 (UTC)
* Lucas Paulista: CSD A7 (db-person); notified 09:31, 6 August 2022 (UTC)
* Biswarup Biswas: CSD A7 (db-person); notified 18:09, 8 August 2022 (UTC)
* Pradeep sethi: CSD A7 (db-person); notified 18:50, 9 August 2022 (UTC)
* Arfaz Iqbal: CSD A7 (db-person); notified 06:05, 10 August 2022 (UTC)
* Xpargee: CSD A7 (db-band); notified 23:01, 10 August 2022 (UTC)
* Ishtiyaq Rashid: CSD A7 (db-person); notified 04:20, 12 August 2022 (UTC)
* Thomas Gipson (Actor): CSD A7 (db-person); notified 04:36, 12 August 2022 (UTC)
* Valentin Spătaru: CSD A7 (db-person); notified 21:23, 13 August 2022 (UTC)
* Governemnt of Gujarat: CSD G6 (db-g6); additional information: {G6 rationale: Misspelled attempt at Government of Gujarat} 15:47, 14 August 2022 (UTC)
* Monther Al Kabbani: CSD A10 (db-a10); additional information: {A10 article: Mundhir Qabbānī}; notified 21:18, 14 August 2022 (UTC)
* Peter Atsu Ahianyo: CSD A7 (db-person); notified 19:48, 15 August 2022 (UTC)
* V. P. Jaya Pradeep: CSD A7 (db-person); notified 18:57, 19 August 2022 (UTC)
* Mohammad inam: CSD A7 (db-person); notified 10:20, 20 August 2022 (UTC)
September 2022
* Malik Ado-Ibrahim: CSD A7 (db-person); notified 23:28, 1 September 2022 (UTC)
* Miachel Austin Wardlow: CSD G7 (db-author) 14:11, 2 September 2022 (UTC)
* UZM: CSD G7 (db-author) 20:43, 2 September 2022 (UTC)
* 2009 Portland nightclub shooting: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/2009 Portland nightclub shooting}; notified 20:46, 2 September 2022 (UTC)
* MC STAN: CSD A7 (db-band); notified 07:10, 3 September 2022 (UTC)
* Bharat Jodo Yatra: CSD G11 (db-spam); notified 07:21, 5 September 2022 (UTC)
* Shayan bahrainy: CSD A7 (db-person); notified 21:27, 7 September 2022 (UTC)
* Giottiline Ginko: CSD G7 (db-author) 05:01, 9 September 2022 (UTC)
* Jonathan Browne (racing driver): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Jonathan Browne (racing driver)}; notified 21:47, 9 September 2022 (UTC)
* Simon Shina Oluwafemi: CSD A7 (db-person); notified 06:03, 10 September 2022 (UTC)
* Arun Adsad: CSD A7 (db-person); notified 07:18, 10 September 2022 (UTC)
* 2022 Quezon City fire: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/2022 Quezon City fire}; notified 05:46, 11 September 2022 (UTC)
* Yohanna Izam: CSD A7 (db-person); notified 12:10, 15 September 2022 (UTC)
* Dennis Shen: CSD A7 (db-person); notified 21:37, 15 September 2022 (UTC)
* Draft:Abu Aleeha: CSD G12 (db-copyvio); additional information: {G12 url: https://www.imdb.com/name/nm10689162/bio?ref_=nm_ov_bio_sm}; notified 22:27, 16 September 2022 (UTC)
* Nithra Apps: CSD G6 (db-g6); additional information: {G6 rationale: Disambig page with no articles to disambig } 09:41, 22 September 2022 (UTC)
October 2022
* 2022 Liga 3 West Sumatra: CSD G7 (db-author) 10:27, 3 October 2022 (UTC)
* Satheesh MS artiest.jpg: CSD A1 (db-nocontext); notified 03:43, 4 October 2022 (UTC)
* Rashmi Teltumde: CSD G12 (db-copyvio); additional information: {G12 url: https://texastech.com/sports/womens-tennis/roster/rashmi-teltumbde/1842}; notified 21:28, 4 October 2022 (UTC)
* Dignan: CSD G1 (db-nonsense); notified 21:44, 6 October 2022 (UTC)
* Shubham Das: CSD A7 (db-person); notified 22:16, 6 October 2022 (UTC)
* Thanh Le: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Thanh Le}; notified 16:59, 7 October 2022 (UTC)
* Irene Flaugher: CSD A7 (db-person); notified 02:42, 8 October 2022 (UTC)
* Kuloshvili Giorgi: CSD A7 (db-person); notified 20:46, 9 October 2022 (UTC)
* Charlie The Dog: CSD A7 (db-animal); notified 20:47, 9 October 2022 (UTC)
* Paran Murmu: CSD G11 (db-spam); notified 07:17, 11 October 2022 (UTC)
* Anthony Pangilinan: CSD G11 (db-spam); notified 07:30, 11 October 2022 (UTC)
* Hôtel de la Ma rine, Nantes: CSD G7 (db-author) 09:44, 11 October 2022 (UTC)
* This attack page: CSD G10 (db-attack); notified 00:41, 13 October 2022 (UTC)
* Mirzaganj Thana: CSD A7 (db-corp); notified 16:00, 18 October 2022 (UTC)
* Lewis Elsdon, 1st Duke of Muggleswick: CSD A11 (db-madeup); notified 21:15, 18 October 2022 (UTC)
* Charter 91: CSD G12 (db-copyvio); additional information: {G12 url: https://www.rferl.org/a/rights-charter-attempts-to-unify-iranians/24704125.html?fbclid=IwAR2Ekxx9I9J3V2mb7__jDAXcoFMRzoUBYVDXTTCrrpPapNsCSd1FKhHGW8M}; notified 14:25, 19 October 2022 (UTC)
* Raphael Hazrat Ishaan: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Sayyid Raphael Dakik}; notified 18:10, 22 October 2022 (UTC)
* Hegedusj/Propaganda: CSD A10 (db-a10); additional information: {A10 article: Propaganda}; notified 21:43, 25 October 2022 (UTC)
* Daniel Michelson: CSD G12 (db-copyvio); additional information: {G12 url: http://www.realbiblecodes.com/people/michelson.php}; notified 05:54, 26 October 2022 (UTC)
* Climatic info: CSD G6 (db-g6); additional information: {G6 rationale: User talk page moved to mainspace. Unable to undo. } 21:16, 26 October 2022 (UTC)
* Andrew Berglund: CSD A7 (db-person); notified 22:32, 26 October 2022 (UTC)
* Nik Omar Nik Abdul Aziz: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Nik Omar Nik Abdul Aziz}; notified 05:13, 27 October 2022 (UTC)
* Be glorious, our city!: CSD G7 (db-author) 20:24, 27 October 2022 (UTC)
* Množična tragedija na festivalu v Seulu: CSD G7 (db-author) 08:57, 31 October 2022 (UTC)
November 2022
* Mbuni FC Arusha: CSD A3 (db-nocontent); notified 21:31, 3 November 2022 (UTC)
* This attack page: CSD G10 (db-attack); notified 03:59, 4 November 2022 (UTC)
* Adam Faria: CSD A7 (db-person); notified 21:06, 4 November 2022 (UTC)
* Jam2022/sandbox: CSD G6 (db-g6); additional information: {G6 rationale: Redundant - Full draft already exists in user space } 21:16, 7 November 2022 (UTC)
* Maddala Krishna Murthy: CSD A7 (db-person); notified 07:15, 11 November 2022 (UTC)
* Deepak Kumar (cricketer): CSD A7 (db-person); notified 07:15, 11 November 2022 (UTC)
* Goddala Elaizar: CSD A7 (db-person); notified 07:17, 11 November 2022 (UTC)
* Arjun Kumar (cricketer): CSD A7 (db-person); notified 07:17, 11 November 2022 (UTC)
* Kumarswamy: CSD A7 (db-person); notified 07:18, 11 November 2022 (UTC)
* Chidambareswara Rao: CSD A7 (db-person); notified 07:18, 11 November 2022 (UTC)
* Noor Khan (cricketer): CSD A7 (db-person); notified 07:19, 11 November 2022 (UTC)
* Venkata Appa Rao: CSD A7 (db-person); notified 07:20, 11 November 2022 (UTC)
* Bharat Reddy (cricketer): CSD A7 (db-person); notified 07:28, 11 November 2022 (UTC)
* Shankara Rao: CSD A7 (db-person); notified 07:28, 11 November 2022 (UTC)
* Satyakumar Verma: CSD A7 (db-person); notified 07:29, 11 November 2022 (UTC)
* Loud prayer: CSD A1 (db-nocontext); notified 11:59, 11 November 2022 (UTC)
* Hunter Ifland: CSD A7 (db-person); notified 19:18, 11 November 2022 (UTC)
* Jessica Markowitz: CSD A7 (db-person); notified 08:29, 15 November 2022 (UTC)
* Hellogghu: CSD G2 (db-test); notified 01:01, 19 November 2022 (UTC)
* Kentos Music Band: CSD A7 (db-band); notified 10:56, 19 November 2022 (UTC)
* Cadet College Ormara: CSD G11 (db-spam); notified 11:05, 19 November 2022 (UTC)
* Canoe2: CSD A7 (db-corp); notified 19:47, 20 November 2022 (UTC)
* Wouter Corduwener: CSD A7 (db-person); notified 02:35, 24 November 2022 (UTC)
December 2022
* Liquorose: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Liquorose}; notified 13:05, 9 December 2022 (UTC)
* Miss Grand Albania: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Miss Grand Albania}; notified 16:48, 10 December 2022 (UTC)
* Daniel R. Treccia: CSD A7 (db-person); notified 09:31, 11 December 2022 (UTC)
* Chris A Official: CSD A7 (db-band); notified 19:41, 14 December 2022 (UTC)
* Passing Through: Woni Spotts, The First Black Woman to Travel to Every Country and Continent: CSD G7 (db-author) 03:18, 15 December 2022 (UTC)
* Tolga Akcay (Author): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Tolga Akcay}; notified 08:52, 20 December 2022 (UTC)
* Cornelis van Rooyen: CSD G7 (db-author) 08:30, 22 December 2022 (UTC)
* North Sudan: CSD G1 (db-nonsense); notified 19:07, 25 December 2022 (UTC)
* Thumb, Mr. Rungsun Klinkaeo., February 20, 2019.jpg: CSD A1 (db-nocontext); notified 08:44, 26 December 2022 (UTC)
* World 271 Countries., Mr. Rungsun Klinkaeo., February 20, 2019.jpg: CSD A1 (db-nocontext); notified 08:45, 26 December 2022 (UTC)
* Birendra Kishore Roaza: CSD G12 (db-copyvio); additional information: {G12 url: https://www.elengcha.com/2022/12/birendra-kishore-roaza.html?m=1}; notified 08:16, 27 December 2022 (UTC)
* People's Republic of Manchuria: CSD A10 (db-a10); additional information: {A10 article: Taiwan}; notified 19:02, 27 December 2022 (UTC)
January 2023
* The Dacca Bank: CSD G7 (db-author) 00:07, 4 January 2023 (UTC)
* Kingdom of Algiers: CSD A10 (db-a10); additional information: {A10 article: Ottoman Algeria}; notified 22:50, 7 January 2023 (UTC)
* Teplate:User Sagittarius A*: CSD G7 (db-author) 08:20, 10 January 2023 (UTC)
* Mufassil Islam: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Mufassil Islam}; notified 22:52, 10 January 2023 (UTC)
* Rana Intezar: CSD A7 (db-person); notified 23:56, 16 January 2023 (UTC)
* Third Reich NSDAP cabinet 1925: CSD G3 (db-hoax); notified 17:57, 18 January 2023 (UTC)
* Suite über 6 Schweizerische Volkslieder: CSD G7 (db-author) 19:49, 22 January 2023 (UTC)
* Danny Barbarigos: CSD A7 (db-person); notified 20:58, 25 January 2023 (UTC)
* Walter Bradick: CSD A7 (db-person); notified 21:00, 25 January 2023 (UTC)
* Brahmrishi Bawra Shanti Vidya Peeth, Udhampur: CSD A7 (db-corp); notified 21:01, 25 January 2023 (UTC)
* Video game designer: CSD G1 (db-nonsense); notified 08:08, 26 January 2023 (UTC)
* Citation templates now better at flagging free access content: CSD G1 (db-nonsense); notified 09:25, 28 January 2023 (UTC)
* DYK, or proudly displaying incorrect information on the Main Page with alarming regularity: CSD G1 (db-nonsense); notified 09:26, 28 January 2023 (UTC)
* Ira-wellies: CSD G1 (db-nonsense); notified 05:57, 30 January 2023 (UTC)
February 2023
* Port Phillip Backwater: CSD G1 (db-nonsense); notified 00:38, 2 February 2023 (UTC)
* Noahkrijtat: CSD G7 (db-author) 23:25, 2 February 2023 (UTC)
* AmbaSat: CSD G7 (db-author) 18:21, 3 February 2023 (UTC)
* Aryan Actor: CSD G1 (db-nonsense); notified 09:13, 11 February 2023 (UTC)
* Time To Realize (song): CSD A9 (db-a9); notified 13:37, 11 February 2023 (UTC)
* Zarathustra in Manichaeism: CSD G12 (db-copyvio); additional information: {G12 url: https://sciencetheory.net/manicheism/}; notified 09:13, 12 February 2023 (UTC)
* Greg Rutkowski: CSD A7 (db-person); notified 07:10, 14 February 2023 (UTC)
* Aminhossein Rad: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Aminhossein Rad}; notified 07:11, 18 February 2023 (UTC)
* Syed Muhammad Ahmad Shah: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Gesudaraz I}; notified 07:26, 18 February 2023 (UTC)
* Sir gxrg: CSD A3 (db-nocontent); notified 13:50, 23 February 2023 (UTC)
* Sir-gxrg: CSD A7 (db-person); notified 13:51, 23 February 2023 (UTC)
* Amin Rad: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Aminhossein Rad}; notified 11:17, 24 February 2023 (UTC)
* Shoaib Ahmad Malik: CSD A7 (db-person); notified 10:17, 25 February 2023 (UTC)
* Jalen Jahn: CSD G11 (db-spam); notified 18:13, 26 February 2023 (UTC)
March 2023
* WWE Raw (season 1): CSD G7 (db-author) 22:38, 1 March 2023 (UTC)
* 20th Century Fox World (South Korea): CSD A3 (db-nocontent); notified 20:42, 4 March 2023 (UTC)
* Alien: Descent: CSD A3 (db-nocontent); notified 20:43, 4 March 2023 (UTC)
* Nimrod Nkosi: CSD A7 (db-person); notified 23:10, 6 March 2023 (UTC)
* Koudeiland Islands: CSD G3 (db-hoax); notified 22:51, 7 March 2023 (UTC)
* Level 245: CSD G1 (db-nonsense); notified 22:17, 9 March 2023 (UTC)
* List of chairpersons of the Union of Bumibaru Socialist Republics (Fiction): CSD G1 (db-nonsense); notified 22:28, 12 March 2023 (UTC)
* Lordboy Cmt: CSD A7 (db-band); notified 23:02, 12 March 2023 (UTC)
* List of Mister Tourism Venezuela titleholders: CSD G7 (db-author) 17:37, 18 March 2023 (UTC)
* Golden Larnax: CSD G12 (db-copyvio); additional information: {G12 url: https://m.marefa.org/%D8%B4%D9%85%D8%B3_%DA%A4%D8%B1%D8%AC%D9%8A%D9%86%D8%A7}; notified 07:27, 29 March 2023 (UTC)
* DAWS TEAM: CSD A7 (db-club); notified 06:21, 30 March 2023 (UTC)
* California's travel ban: CSD G7 (db-author) 19:39, 30 March 2023 (UTC)
April 2023
* Carl Ciantar: CSD G7 (db-author) 20:24, 3 April 2023 (UTC)
* Princess Towers: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Princess Towers}; notified 06:18, 4 April 2023 (UTC)
* Sundaram Multi Pap Limited: CSD G11 (db-spam); notified 06:46, 4 April 2023 (UTC)
* SN 2014c: CSD G7 (db-author) 20:00, 4 April 2023 (UTC)
* Revia: CSD G7 (db-author) 18:40, 8 April 2023 (UTC)
* Free Officers Movement (Libya): CSD G12 (db-copyvio); additional information: {G12 url: https://countrystudies.us/libya/28.htm}; notified 22:08, 8 April 2023 (UTC)
* Shantha mohan: CSD G7 (db-author) 22:12, 8 April 2023 (UTC)
* Orkhan Mammadov: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Orkhan Mammadov}; notified 08:31, 10 April 2023 (UTC)
* SSSniperwolf: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/SSSniperwolf}; notified 09:02, 10 April 2023 (UTC)
* Hassan Bawab: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Hassan Bawab}; notified 22:34, 10 April 2023 (UTC)
* Ben Kissel: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Ben Kissel}; notified 21:27, 11 April 2023 (UTC)
* Light Scattering Spectroscopy: CSD G12 (db-copyvio); additional information: {G12 url: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6594557/}; notified 04:23, 14 April 2023 (UTC)
* Vinny Troia: CSD G12 (db-copyvio); additional information: {G12 url: Wikipedia:Articles for deletion/Vinny Troia (2nd nomination)}; notified 18:45, 14 April 2023 (UTC)
* Carolyn Leach: CSD A7 (db-person); notified 05:17, 16 April 2023 (UTC)
* Joel M. Albrizio: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Joel M. Albrizio}; notified 20:13, 17 April 2023 (UTC)
* Vincent James (streamer): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Vincent James (Streamer)}; notified 04:53, 18 April 2023 (UTC)
* Claire Guillard: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Claire Guillard}; notified 04:58, 18 April 2023 (UTC)
* Vindia national cricket team: CSD G3 (db-hoax); notified 06:41, 18 April 2023 (UTC)
* Sattaru Vishwa Raj: CSD G3 (db-hoax); notified 06:42, 18 April 2023 (UTC)
* Sattaru Samanyu: CSD G3 (db-hoax); notified 06:43, 18 April 2023 (UTC)
* Sattaru Vishnu Raj: CSD G3 (db-hoax); notified 06:44, 18 April 2023 (UTC)
* Sattaru Ranesh: CSD G3 (db-hoax); notified 06:44, 18 April 2023 (UTC)
* Sattaru Vardhan: CSD G3 (db-hoax); notified 06:44, 18 April 2023 (UTC)
* Peter Pan's Neverland Nightmare: CSD G7 (db-author) 01:59, 22 April 2023 (UTC)
* YourPritam: CSD A7 (db-person); notified 04:39, 23 April 2023 (UTC)
* P C Dhiman: CSD A7 (db-person); notified 21:26, 24 April 2023 (UTC)
* List of Bangladeshi actors: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/List of Bangladeshi actors}; notified 07:09, 25 April 2023 (UTC)
* Laura Ledesma: CSD G5 (db-banned); additional information: {G5 user: User:Mongies} 05:45, 26 April 2023 (UTC)
May 2023
* Brett Mosser: CSD A7 (db-person); notified 04:52, 3 May 2023 (UTC)
* Fathullah =Rahmat: CSD G6 (db-g6); additional information: {G6 rationale: Typo} 04:03, 5 May 2023 (UTC)
* Jeff Nace: CSD A7 (db-person); notified 04:05, 5 May 2023 (UTC)
* Sebastian Gorin: CSD G7 (db-author) 20:16, 5 May 2023 (UTC)
* BristolWorld: CSD G7 (db-author) 17:08, 6 May 2023 (UTC)
* Vincent La: CSD G1 (db-nonsense); notified 23:40, 6 May 2023 (UTC)
* AZ's Blue Politico: CSD G1 (db-nonsense); notified 23:41, 6 May 2023 (UTC)
* The Bear Pundit: CSD G1 (db-nonsense); notified 23:41, 6 May 2023 (UTC)
* Amrita Jash: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Amrita Jash (2nd nomination)}; notified 20:53, 10 May 2023 (UTC)
* Miss Grand United States 2023: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Miss Grand United States 2023}; notified 09:59, 11 May 2023 (UTC)
* Jimmy Chau: CSD G7 (db-author) 13:17, 13 May 2023 (UTC)
* Troodontidae indet: CSD G7 (db-author) 13:29, 13 May 2023 (UTC)
* Katzun: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Katzun}; notified 20:56, 13 May 2023 (UTC)
* 2023–24 WE League season: CSD G7 (db-author) 08:34, 21 May 2023 (UTC)
* The reconstruction of the Berlin Palace: CSD A10 (db-a10); additional information: {A10 article: Berlin Palace}; notified 09:26, 23 May 2023 (UTC)
* Aryan Rathore: CSD A7 (db-person); notified 09:50, 23 May 2023 (UTC)
June 2023
* Strauss II cabinet: CSD G6 (db-g6); additional information: {G6 rationale: To make way for article move } 21:27, 13 June 2023 (UTC)
* Strauss II cabinet: CSD G6 (db-move); additional information: {G6 page: Cabinet Strauss II} {G6 reason: Standard English word order} 05:16, 14 June 2023 (UTC)
* Jack345110/twinkleoptions.js: CSD G6 (db-error) 12:59, 17 June 2023 (UTC)
* Austrian Football League Players: CSD G6 (db-error) 07:12, 20 June 2023 (UTC)
* Plantilla:Línea de tiempo DragonFly BSD: CSD G6 (db-error) 02:23, 23 June 2023 (UTC)
August 2023
* Manisha Rani: CSD G11 (db-spam); notified 09:14, 5 August 2023 (UTC)
* Manik Marria: CSD G11 (db-spam); notified 09:15, 5 August 2023 (UTC)
* Consulate General of The People's Republic of Bangladesh, Milan: CSD A7 (db-corp); notified 05:52, 13 August 2023 (UTC)
* Huw Thomas (correspondent): CSD A7 (db-person); notified 13:31, 13 August 2023 (UTC)
* Household Of Maliks: CSD G12 (db-copyvio); additional information: {G12 url: https://medium.com/@footcardage/entrepreneurial-ventures-of-the-malik-dynasty-7bf727d8d2e8}; notified 07:31, 17 August 2023 (UTC)
* Dotup Technology Consulting: CSD A7 (db-corp); notified 07:36, 17 August 2023 (UTC)
* ROYAL MEDIA SERVICES: CSD A7 (db-corp); notified 12:34, 17 August 2023 (UTC)
* Omkar Prasad Baidya: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Omkar Prasad Baidya}; notified 04:03, 19 August 2023 (UTC)
* Rahul Saini: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Rahul Saini}; notified 05:18, 19 August 2023 (UTC)
* Swaroop Puranik: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Swaroop Puranik}; notified 05:26, 19 August 2023 (UTC)
* Mill Creek Entertainment: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Mill Creek Entertainment}; notified 05:28, 19 August 2023 (UTC)
* Powdair: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Powdair (2nd nomination)}; notified 10:53, 19 August 2023 (UTC)
* Abhishek Shukla: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Abhishek Shukla VK}; notified 12:23, 19 August 2023 (UTC)
* NCircle Entertainment: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/NCircle Entertainment}; notified 13:11, 19 August 2023 (UTC)
* Swathi jagdish: CSD A7 (db-person); notified 17:25, 20 August 2023 (UTC)
* H. J. Kennedy: CSD A7 (db-person); notified 18:26, 20 August 2023 (UTC)
* Fort Jennifer Kennedy: CSD A3 (db-nocontent); notified 18:27, 20 August 2023 (UTC)
* Great-Great-Grandpa Kennedy: CSD A7 (db-person); notified 18:28, 20 August 2023 (UTC)
* Raktabeej: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Raktabeej}; notified 01:41, 23 August 2023 (UTC)
* Olu Akanmu: CSD G11 (db-spam); notified 07:59, 23 August 2023 (UTC)
* Matthew Géczy: CSD A7 (db-person); notified 10:35, 23 August 2023 (UTC)
* Malek Mehri: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Malek Mehri}; notified 21:46, 26 August 2023 (UTC)
September 2023
* Baban Paul: CSD A7 (db-person); notified 08:44, 17 September 2023 (UTC)
* Philippine Association of Colleges and Universities Commission on Accreditation: CSD G12 (db-copyvio); additional information: {G12 url: https://sites.google.com/ceu.edu.ph/pacucoa/about}; notified 19:18, 17 September 2023 (UTC)
* Sabina Kodra: CSD A7 (db-person); notified 20:42, 17 September 2023 (UTC)
* Robert Budina: CSD A7 (db-person); notified 20:43, 17 September 2023 (UTC)
October 2023
* Mccapra/sandbox: CSD R3 (db-redirtypo) 06:54, 8 October 2023 (UTC)
* Vincenzo Calenda,Tavani: CSD G6 (db-g6); additional information: {G6 rationale: Typo when creating new article } 18:50, 19 October 2023 (UTC)
* Appu (1990 film): CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Appu (1990 film)}; notified 20:33, 29 October 2023 (UTC)
* Kristina Marinova: CSD G11 (db-spam); notified 21:40, 29 October 2023 (UTC)
December 2023
* Kingdom of Pakistan: CSD A11 (db-madeup); notified 01:19, 18 December 2023 (UTC)
January 2024
* Malek Mehri: CSD G4 (db-repost); additional information: {G4 xfd: wikipedia:Articles%20for%20deletion/Malek%20Mehri}; notified 22:21, 2 January 2024 (UTC)
* Jai Gautam: CSD G11 (db-spam); notified 15:39, 6 January 2024 (UTC)
* H:PH: db-reason; additional information: {Custom rationale: Random weird thingy that has been knocking about since 2016 but doesn't belong in en.wiki. It’s a genealogical list of sayid Ghazanfer Shah, whoever that is. }; notified 21:02, 9 January 2024 (UTC)
* History of the America's Cup: CSD G12 (db-copyvio); additional information: {G12 url: https://www.pittwateronlinenews.com/RPAYC-Commodore-America-Cup-Challenger-1908-1914.php}; notified 22:54, 22 January 2024 (UTC)
February 2024
* Bernard Whiteside: CSD G4 (db-repost); additional information: {G4 xfd: Wikipedia:Articles for deletion/Bernard Whiteside}; notified 21:08, 1 February 2024 (UTC)
* Armistice of Villafranca: CSD G6 (db-move); additional information: {G6 page: Villafranca Armistice} {G6 reason: Common English rendering of name } 06:13, 8 February 2024 (UTC)
* Manzur Shafi Chowdhury: CSD A7 (db-person); notified 22:35, 10 February 2024 (UTC)
March 2024
* Monzur Qadir Shafi: CSD A7 (db-person); notified 06:39, 19 March 2024 (UTC)
* Manzur Qadir Shafi: CSD A7 (db-person); notified 17:58, 19 March 2024 (UTC)
April 2024
* Ashtami (TV series): CSD G7 (db-author) 13:51, 28 April 2024 (UTC)
May 2024
* Raphael kid (Nigerian singer and songwriter): CSD G5 (db-banned) 08:17, 6 May 2024 (UTC)
* New haven philatelic soceity: CSD G6 (db-error) 14:37, 11 May 2024 (UTC)
* This attack page: CSD G10 (db-attack); notified 07:11, 14 May 2024 (UTC)
* Lalla Sitt al-Mulk: CSD A7 (db-person); notified 22:22, 24 May 2024 (UTC)
* This attack page: CSD G10 (db-attack); notified 07:19, 30 May 2024 (UTC)
June 2024
* 1891 Census of Scotland: CSD G7 (db-author); additional information: {G7 rationale: Accidentally copied to mainspace from user:TriosLosDios/sandbox} 18:48, 5 June 2024 (UTC)
July 2024
* Lee Da-hye (cheerleader): CSD G11 (db-spam); notified 23:34, 4 July 2024 (UTC)
* Battle of Gogetti: CSD G12 (db-copyvio); additional information: {G12 url: https://profilpelajar.com/article//Battle_of_Gogetti}; notified 00:50, 11 July 2024 (UTC)
|
WIKI
|
Natural magic
Natural magic in the context of Renaissance magic is that part of the occult which deals with natural forces directly, as opposed to ceremonial magic which deals with the summoning of spirits. Natural magic sometimes makes use of physical substances from the natural world such as stones or herbs.
Natural magic so defined includes astrology, alchemy, and disciplines that we would today consider fields of natural science, such as astronomy and chemistry (which developed and diverged from astrology and alchemy, respectively, into the modern sciences they are today) or botany (from herbology). The Jesuit scholar Athanasius Kircher wrote that "there are as many types of natural magic as there are subjects of applied sciences".
Heinrich Cornelius Agrippa discusses natural magic in his Three Books of Occult Philosophy (1533), where he calls it "nothing else but the highest power of natural sciences". The Italian Renaissance philosopher Giovanni Pico della Mirandola, who founded the tradition of Christian Kabbalah, argued that natural magic was "the practical part of natural science" and was lawful rather than heretical.
|
WIKI
|
Adoptable Cookbooks List
Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks
Supermarket Belongs to the Community
Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.
Select Badges
Select Supported Platforms
RSS
deploy_key (9) Versions 0.0.1
Manage deploy keys on Github and Bitbucket
Berkshelf/Librarian
Policyfile
Knife
cookbook 'deploy_key', '= 0.0.1'
cookbook 'deploy_key', '= 0.0.1', :supermarket
knife cookbook site install deploy_key
knife cookbook site download deploy_key
README
Dependencies
Quality
deploy_key cookbook
This is a Chef cookbook to manage deploy_keys on SaaS VCSs. Currently, it supports Bitbucket and Github.
This work is heavily based on the ideas and code of ZippyKid's github-deploy-key cookbook.
Usage
Use this cookbook as a dependency of whatever cookbook will manage your deploy keys.
Declare a deploy_key resource and configure the provider:
deploy_key "app_deploy_key" do
provider Chef::Provider::DeployKeyGithub
...
end
Supported providers:
• Chef::Provider::DeployKeyGithub
• Chef::Provider::DeployKeyBitbucket
Attributes
<table> <tbody> <tr> <th>Attribute</th> <th>Type</th> <th>Description</th> </tr> <tr> <td><code>label</code></td> <td>String</td> <td>This will be used as both the name of the key pair files and the key label on the provider. Defaults to the <code>name</code> attribute</td> </tr> <tr> <td><code>path</code></td> <td>String</td> <td>The directory where the private and public keys are stored</td> </tr> <tr> <td><code>credentials</code></td> <td>Hash</td> <td>The credentials used to authenticate on the API - see <a href="#authentication">below</a></td> </tr> <tr> <td><code>repo</code></td> <td>String</td> <td>The repository where the deploy key will be installed. Has to be in the format <code>username/repo_slug</code> (e.g.: <code>cassianoleal/cookbook-deploy_key</code>)</td> </tr> <tr> <td><code>owner</code></td> <td>String</td> <td>The owner of the key files on disk</td> </tr> <tr> <td><code>group</code></td> <td>String</td> <td>The group of the key files on disk</td> </tr> </tbody> </table>
Actions
• :create - Runs ssh-keygen to create a key pair on the designed path;
• :delete - Deletes the key pair from the disk;
• :add - Adds the public key as a deploy key for the repository;
• :remove - Removes the key from the list of deploy keys on the repository
<a id="authentication"></a>Authentication
Authentication can be done either via username/password:
deploy_key "app_deploy_key" do
provider Chef::Provider::DeployKeyGithub
credentials({
:user => 'username@org.com',
:password => 'very_secure_password'
})
...
end
or OAuth token ( Github | Bitbucket ):
deploy_key "app_deploy_key" do
provider Chef::Provider::DeployKeyGithub
credentials({
:token => 'awesome_and_much_more_secure_token'
})
...
end
A full example
deploy_key "bitbucket_key" do
provider Chef::Provider::DeployKeyBitbucket
path '/home/app_user/.ssh'
credentials({
:token => 'my_bitbucket_oauth_token'
})
repo 'organization/million_dollar_app'
owner 'deploy'
group 'deploy'
action :nothing
end
Author
Cassiano Leal (cassianoleal@gmail.com | twitter | github)
Dependent cookbooks
This cookbook has no specified dependencies.
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
No quality metric results found
|
ESSENTIALAI-STEM
|
Talk:Viktor Bout
Merchant of Death book as source
From hearing interviews with the authors of the book, I am skeptical as to the quality of their information. They seem to pass anecdotes as official info. I think it would be better to cite more solid sources than the book.
I think it is important to have super-solid sources for this article, otherwise it may quickly degenerate into a pile of sensationalist rumors. vlado4 (talk)
wife
"married to Alla Vladimirovna Bout [....] was the owner of clothing stores in the UAE, Germany, South Africa and Russia." - Name of her store(s) in Germany ? When (till when) was it ?
brother
"Elder brother and former partner Sergey Anatolyevich Bout continues to conduct an aviation business in United Arab Emirates (Sharjah) and Bulgaria." - Name of his air-line(s) ? (I wonder especially about Bulgaria = EU country !)
|
WIKI
|
[Japanese businessman] Omori and his 500 fellow prisoners reached India, after a ten-day voyage. They berthed at Calcutta, and stayed there for three days. At Changi Prison [in Singapore] they had been divided into two batches, and half of the original group from Port Swettenham had not appeared. Nor had they seen their wives and daughters.
After a 70-hour ride, they were unloaded in the middle of nowhere and marched two hours with their bags to the bulwark of an old fort. They filed through a huge entrance on which was written “Pranakila”. Inside, in a large patch of lawn, tents were lined up in rows to which they were assigned, six persons to one tent. One week later their missing families arrived, around 500 women and children, whom British authorities had held in separate camps on Blakang Mati (now renamed Sentosa) and other islands off Singapore.
Life at Pranakila camp near New Delhi, on an Indian diet of curries, lots of beans and gallons of tea, was not uncomfortable. The women had their own quarters with partitions in between and their beds were lined up under the thick stone ramp which acted as insulation against heat and coldness. The men were treated according to the standards of Indian soldiers; they slept in hammocks, and when it got cold they were given hay in addition to a blanket. Slowly their numbers grew to around 3,000 as they awaited the day when they would return home.
|
FINEWEB-EDU
|
Page:Notes and Queries - Series 12 - Volume 7.djvu/326
266
NOTES AND QUERIES. [12 s. vn. OCT. 2, 1920.
retention of the ship during the winter and of her dispatch homewards in 1621, never once chances to mention her name nor that of the Speedwell. They are to him'always the "larger " and the "lesser " ship. Nor in a letter of which he quotes part, in which the Agent Weston reports the return of the vessel, and alludes with dis- . appointment to her having no cargo, does the name appear. And this is the more remarkable as Bradford does mention by name the ship, the * Fortune, ' which came rom England in 1621, and in the rest of his history we find that nearly every other ship mentioned is named either by himself or Bothers in course of correspondence. Bradford moreover, tells us that some of the second party from Leyden came out in 1630 in the Mayflower. But he utters not a word of recognition of an old friend, if it Tvas the same ship, or of the coincidence of names if it was not.
The same is the case with the other passenger in the Mayflower, Governor E. Winslow, who has left a record. His narrative New Plimouth,' (published by George Mourt) makes no mention of the ship's name. Nor do we find it in his ' Good News from New England," 1624.
* ' A Relation or Journall of the beginning of
Captain John Smith more than once men- tions the voyage and seems familiar with the details, but gives no name.
It is not till we come to Nathaniel Morton's 1669 that we find the names we are seeking. He transcribes almost verbatim Bradford's words and inserts, after the first mention of the two ships, "called ^the Mayflower," fi called the Speedwell " respectively. After that the poor Mayflower comes to her own.
* New England's Memorial ' published in
There is, however, just one really con- temporary witness to show that the May- flower is not legendary. There is a MS. volume entitled 'Plimouth's Great Book of Deeds of Lands enrolled from Ano. 1627 to Ano. 1651.' It contains records of allot- ments, and at the head of one of the lists, written apparently in Bradford's own hand occur the words "The Falles of their ground which came first over in the May Floure, according as their lots were cast, 1623."
This record has reference to a very in- teresting and important crisis in the history of the Plymouth Colony. It marks the point when the Colonists abandoned the system of Communism which they had adopted and maintained since they left England. The system had broken down and Bradford
records its abandonment with words of shrewd and emphatic criticism well worthy of note at the present time.
The Pilgrim Fathers had no idea of achieving fame for themselves or for their vessel. They knew not *how precious every detail of information would become. We should not have wondered if, in the course of their records, they had refrained from parading the name or bringing it into pro- minence. But that for 50 years it should have occurred to nobody to make mention of the name, and that neither by chance observation, nor by incidental allusion the secret should have come out, seems indeed a remarkable fact. It affords a wholesome warning against the argument from silence. G. CCJTHBERT BLAXLAND.
Ringshall Rectory, Stowmarket.
PAST AND PROSPECTIVE. The voice of the influential press has brought public enthu- siasm, and a vast subscription to the desired repair of some parts of the abbey that had decayed to the point of threatening disaster. We may anticipate that the result will be commendable, and no redundant restora- tions or "carrying out of intended comple- tions " will be suffered in spite of the tempta- tion of adequate funds. Unfortunately previous restorations have not been happy, and for at least a century any interference with the fabric has been the subject of protest usually unavailing. We need hardly refer to the changes made at the instigation of Beans Horsley, Vincent and Ireland. Thereafter the published protests assume sufficient importance to be the subject of the following bibliographical note.j
* , 4 WESTMINSTER ABBEY, RESTORATIONS
M'A Letter to the Dean and Chapter of West- minster on the Intended Alterations in the Interior of Westminster Abbey by a Clergyman of the Church of England.' 1844. This was proceeded by letters contributed to the Builder (June 24 and Oct. 25, 1843) dealing with Daan Tarton's re-arrangement of the choir screen, &c.
2. A 4to Circular, 4 pp. only. ' App3ndix to the Memorial concerning Westminster Abbey,
_circa 1870.^^ss^> .:<
3. Protests published in The Athenceum, Aug. 17, 1878, and The Builder, Sept. 7, 1878, reprinted in slip form for general distribution.
4. 'Concarning Westminster Abbey,' a pamphlet (14 pp., 8vo), issued by the Society for the Protection of Ancient Buildings, circa 1893.
5."? Architecture ,?and History of ^Westminster Abbey,' a paper read before the Society for Protection of Ancient Buildings, by William Morris, July 1, 1884. This was reprinted with
|
WIKI
|
Russia's Lavrov says difficult to solve peace treaty issue with Japan
Russian Foreign Minister Sergei Lavrov said on Saturday it would be difficult to close the gap in positions over a peace treaty and territorial dispute with Japan, two weeks before President Vladimir Putin visits. A territorial dispute between Tokyo and Moscow over a chain of western Pacific islands, seized by Soviet troops at the end of World War Two, has upset diplomatic relations ever since, precluding a formal peace treaty between the two countries. "It's not easy to bridge the gap in the principal positions of both sides, the problem is difficult," said Lavrov at a joint briefing with Japan's Foreign Minister Fumio Kishida in Moscow. "But despite all these difficulties, we expressed mutual readiness to attempt moves in solving the practical issues, so that would help the development of cooperation between the neighboring regions of the two countries," Lavrov said. In September, Putin met Japanese Prime Minister Shinzo Abe in Russia's eastern port city of Vladivostok where both agreed to deepen economic ties and work to make headway on negotiations for the conclusion of a peace treaty ahead of his Japan visit in December. Concessions over the islands would carry risks for Putin but could boost Japanese investment in Russia at a time when Moscow, battered by low global oil prices and Western sanctions, badly needs an injection of cash. Kishida said on Saturday the territorial dispute should be solved on a mutually agreeable basis. Follow CNBC International on and Facebook.
|
NEWS-MULTISOURCE
|
Delaware North
Delaware North is an American multinational food service and hospitality company headquartered in Buffalo, New York. The company also operates in the lodging, sporting, airport, gambling, and entertainment industries. The company employs over 55,000 people worldwide and has over $3.2 billion in annual revenues.
History
Delaware North began as Jacobs Brothers, founded in Buffalo, New York, in 1915 by brothers Marvin, Charles and Louis Jacobs. Its name was changed first to Emprise Corp. and then to Sportsystems Inc. before adopting its current name in 1980. The company remains family-owned and operated by Jeremy Jacobs, who also owns the Boston Bruins. The arena in which the Bruins play, the TD Garden, is owned by Delaware North. Jacobs is also a member of the U.S. Department of Commerce Travel and Tourism Board.
Jacobs Brothers initially operated theater concessions. When the establishments closed down in the hot summer months, the three men turned their attention to ballparks, the first being Offermann Stadium, and the creation of the sports concession industry. Sportservice was created in 1926 following contracts with minor-league ballparks in Buffalo and Syracuse, New York. Sportservice is Delaware North's largest operating company. In 1930, the company entered into its first major-league deal by signing an agreement with the Detroit Tigers to handle food service at Navin Field. The Jacobs brothers expanded their business in 1939 by acquiring a racetrack, marking the beginning of Delaware North Companies Gaming & Entertainment. In 1941, the company entered the airport arena with a contract to provide food service in Washington National Airport. Delaware North Companies Travel Hospitality Services operates in more than 30 major airports worldwide.
Upon the death of his father, founder Louis M. Jacobs in 1968, Jeremy M. Jacobs began leading the company, then called Emprise, at the age of 28. The years that followed were characterized by unprecedented growth and diversification. In 1972, after negative press over alleged connections to organized crime in Sports Illustrated and the Arizona Republic, the Emprise company was convicted of federal racketeering charges over the purchase of the Frontier Hotel in Las Vegas with members of the Mob. Jeremy dissolved Emprise and reorganized his family's holdings under a new company, Delaware North (named after the intersection of Delaware Avenue and North Street in Buffalo where the company was headquartered at the time), with a public emphasis on operating a clean, separate organization with no connection to Emprise. Delaware North acquired the Boston Garden in 1975 while Jeremy Jacobs purchased the Boston Bruins, one of the original six franchises of the National Hockey League. In 1987, the company acquired Sky Chefs, (now LSG Sky Chefs) a move that bolstered its airport business. The company obtained the contract to provide visitor services in Yosemite National Park in 1993. under the terms of the largest concessions contract in the U.S. National Park Service. The award sowed the seeds of a new line of business: Delaware North Companies Parks & Resorts.
In 1995, Delaware North won the contract to run the Kennedy Space Center Visitor Complex. In the late 1990s, the company worked toward becoming the largest racino operator in North America by adding gambling to some of its racetrack properties. The company moved its World Headquarters from the Main Court Building to 40 Fountain Plaza in 1999.
The company became the first U.S. hospitality company in the world to have its GreenPath environmental management system registered to the guidelines put forth by the International Organization for Standardization (ISO 14001) in 1991. In the early 2000s, the company became a hotel owner by purchasing Tenaya Lodge at the entrance to Yosemite and Harrison Hot Springs Resort & Spa in British Columbia, and by building a hotel at its gambling and racing destination resort in Wheeling, West Virginia. 2004 saw the company beginning GuestPath, its companywide continuous improvement process. The company entered the European market with a contract at Wembley Stadium, followed by one at Emirates Stadium in 2006 and 2007. In 2008, the company signed a 10-year contract at Pride Park Stadium, Derby.
In 2008/2009, Delaware North got a contract to operate a 4,500 slot machine racino at Aqueduct Racetrack in Queens, New York. It lost the contract in 2009 when it could not make a $370 million upfront payment to the state of New York. The company was hired by Garrison Investments in 2009 to operate the RMS Queen Mary in Long Beach, California. This partnership ended in April 2011. In 2010, the company acquired Jumer's Casino & Hotel located in Rock Island, Illinois. Thereafter, the company entered the European travel hospitality market opening outlets at Gatwick, Heathrow, and Edinburgh Airports, and the Euston Railway Station. It also acquired the Australian Resorts at Lizard Island, Heron Island, and Wilson Island on the Great Barrier Reef and King's Canyon in the Red Centre of Australia.
In 2014, Delaware North launched a new global brand identity as the company prepared to celebrate its 100th anniversary in 2015. The company is now known just as "Delaware North" – no longer as "Delaware North Companies" – and ended the use of the abbreviation "DNC" in its logo.
The majority of its operating companies, which previously had been identified as "Delaware North Companies Parks & Resorts," for example, are now called "Delaware North." The only exceptions are Delaware North Sportservice – given its historical importance as the company's original operating company and brand recognition in the sports industry – and Delaware North's most recent acquisition, Patina Restaurant Group.
In 2014, Delaware North issued a letter to the U.S. National Park Service, asserting various intellectual property rights, including such names as Ahwahnee, Curry Village, Wawona and other historic names it acquired when it purchased the Yosemite Park & Curry Company in 1993 with NPS approval. The letter estimated the value of those names at $51 million, while NPS estimated it at $3.5 million. A breach of contract lawsuit to determine their value was resolved in July 2019 with Delaware North receiving a $12 million settlement, the majority of which was paid by new Yosemite concessionaire Aramark, and the original place names being restored by NPS and Aramark.
On January 6, 2015, Delaware North Chairman Jeremy Jacobs relinquished the title of CEO and named Jerry Jacobs Jr. and Louis Jacobs Co-CEO's. He also named Charlie Jacobs CEO of Delaware North's Boston Holdings.
In 2015, Delaware North moved its corporate offices to the Delaware North Building in Buffalo, returning the company's headquarters to the namesake avenue after nearly 25 years.
In November 2018, Delaware North announced it was purchasing the SkyCity Darwin casino in Australia from the SkyCity Entertainment Group for A$188 million. The casino was renamed the Mindil Beach Casino & Resort in April 2019.
Sportservice
Delaware North Companies Sportservice provides concessions, premium dining, catering and retail services to sporting and entertainment venues in the United States and Canada. The company operates at over 50 venues including the homes of such franchises as the San Diego Padres, Baltimore Orioles, Green Bay Packers, Milwaukee Brewers, St. Louis Cardinals, Cleveland Guardians, Cincinnati Reds, Detroit Tigers, Minnesota Twins, Buffalo Bills, Chicago White Sox, Columbus Blue Jackets, and Chicago Bears. Sportservice has been recognized for its culinary advances and PETA approved menus. Sportservice is the company responsible for the creation of Secret Stadium Sauce, a popular condiment mostly associated with Milwaukee.
Gambling and entertainment
Delaware North Companies Gaming & Entertainment is a gambling and racing operations company that focuses on racing venues that offer video gambling machines, poker rooms, table games, restaurants, retail shops and hotels. The company operates more than 10,000 video gambling machines in such places as New York, Arizona, Florida, New Hampshire, Illinois and West Virginia. Venues include:
* Arizona Greyhound Racing
* Daytona Beach Kennel Club & Poker Room
* Finger Lakes Gaming and Race Track
* Gate City Casino
* Hamburg Gaming
* Jake's 58 Casino Hotel
* Mardi Gras Casino and Resort
* Miami Valley Gaming (50%)
* Mindil Beach Casino & Resort in Darwin, Northern Territory, Australia
* Southland Greyhound Park
* Wheeling Island Hotel-Casino-Racetrack
DNC International
Delaware North Companies International provides food service and hospitality to international sporting and entertainment venues including Wembley Stadium, Emirates Stadium, Ricoh Arena, Pride Park Stadium and the Australian Open tennis tournament.
Parks and resorts
Delaware North Companies Parks & Resorts was founded in 1992 following the company's winning bid for primary concessions at Yosemite National Park. The company now operates at other venues including Grand Canyon (one of two concessionaires ), Niagara Falls State Park, Kennedy Space Center Visitor Complex, Shenandoah National Park, and Gideon Putnam Resort (among others).
Patina Restaurant Group
In February 2014, Delaware North announced it would acquire a majority stake in Patina Restaurant Group (PRG), one of the nation's leading multi-concept operator in the premium segments of the restaurant and catering industry. PRG has operations at landmark locations in high-profile cultural and entertainment venues in New York City, California, and Orlando, Fla. Among them are: Rockefeller Center, Lincoln Center, Walt Disney World, Disneyland, Walt Disney Concert Hall, the Empire State Building, Grand Central Terminal/MetLife Building and Madison Square Garden. Patina is also the official caterer for the Creative Arts Ball and the Emmy Awards Governors Ball.
Travel hospitality services
Delaware North Companies Travel Hospitality Services operates food, beverage and retail at airports and toll plazas throughout the United States. The company operates at venues such as Los Angeles International Airport, Minneapolis-St Paul International Airport, Nashville International Airport, Buffalo Niagara International Airport, and the Detroit Metro Airport. The company recently opened the first-ever Sports Illustrated retail store at Detroit Metro Airport's new North Terminal. In September 2008, Delaware North also recently unveiled uWink technology which helps make it easier for international travelers at Ft. Lauderdale Airport.
TD Garden
Delaware North Companies Boston owns TD Garden, the home arena for the Boston Bruins hockey team and Boston Celtics basketball team. Jeremy Jacobs, Chairman of Delaware North, also owns the Bruins. TD Garden is the site of the annual Beanpot college hockey tournament, and hosts the annual Hockey East Championships. The arena has also hosted many major national sporting events including the 1999 and 2003 NCAA Division I Men's Basketball regional first and second rounds, the 2009 and 2012 Sweet Sixteen and Elite Eight, the 1998 Frozen Four, the 2004 Frozen Four, the 2014 United States Figure Skating Championships, the 2006 women's Final Four, and the 2015 Frozen Four. It hosted games 3, 4, and 6 of the 2011 Stanley Cup Finals, also games 3, 4, and 6 of the 2013 Stanley Cup Finals and games 1, 2, 5, and 7 of the 2019 Stanley Cup Finals for the Bruins, and games 1, 2, and 6 of the 2008 NBA Finals, games 3, 4, and 5 of the 2010 NBA Finals, and games 3, 4, and 6 of the 2022 NBA Finals for the Celtics.
Yosemite National Park
Delaware North Companies, having lost the contract to run the concessions at Yosemite to Aramark in 2015, claimed that the names of many historic sites within Yosemite actually belong to them, and not to the United States Government. The site names include Curry Village, Ahwahnee Lodge, Wawona Hotel, Half Dome, and the name of the park itself, Yosemite National Park. The result has been a public relations nightmare for DNC, including calls for boycott of its concessions at other sites.
Delaware North sued the National Park Service in the United States Court of Claims for breach of contract. The lawsuit was settled in July 2019, with Aramark and the Park Service paying Delaware North a total of $12 million in exchange for the trademarks and tangible assets.
In 2017, Delaware North was mentioned as the defendant in Kerr vs. Delaware North Companies, Inc. et al. Kerr alleges sexual misconduct while employed by Delaware North in Yosemite National Park. Among remarks in the legal document, the culture alluded that: "DNC employees working at the remote Tuolumne Meadows Lodge . . . live and work in an atypical environment. Employees are isolated in a small, isolated area surrounded by Yosemite wilderness.” Doc. 1-1 at ¶ 17.Plaintiff's allegations of specific conduct included descriptions of DNC employees making “inappropriate statements to Plaintiff at work,” leaving “sex toys and sexual images in public and private areas of the Tuolumne Meadows Lodge and the common areas of DNC employee housing” and “threats of physical violence against Plaintiff” which motivated Plaintiff to contact security who “spent several days in the DNC employee housing area.” Doc. 1-1 at ¶ 18.The harassment alleged by Plaintiff culminated in an incident at “a work party on DNC property hosted by DNC” where Plaintiff was “physically attacked,” and drugged by DNC employees. Doc. 1-1 at ¶ 21. Plaintiff was then allegedly taken by DNC employees “to one of their DNC employee housing rooms” where Plaintiff was further assaulted." Delaware North sought for dismissal, but the case was remanded to the Superior Court on grounds that the alleged incident occurred on federal land and Delaware North's argument for dismissal "missed the mark".
Yellowstone National Park Visitor Access
From 2009-2019, Delaware North acquired The Holiday Inn, Buffalo Bus Tours, Branch Saloon, Yellowstone Vacation Tours, Grey Wolf Inn, Yellowstone Park Hotel, Best Western Gardiner, Explorer Cabins, Two Top Snowmobiles, The 23-cabin Jim Bridger Motor Court, The Yellowstone Mine restaurant and the Rusty Rail Lounge & Casino, The Branch Saloon and Restaurant, Rendezvous Snowmobile Rentals, and Big Sky Car Rentals. Buffalo Bus, Big Sky Car Rental, and Rendezvous Snowmobile were re-branded as Yellowstone Vacation Tours. Two Top, Buffalo Bus, Rendezvous, The Best Western, and the original Holiday Inn were family run businesses with winter access contracts to operate in Yellowstone National Park prior to their acquisition. With these acquisitions, most of which occurred after DNC's contract loss in Yosemite in 2015, Delaware North owns the majority of all winter access into Yellowstone—without contractual revision by the National Park Service.
Political
In 2020, Delaware North placed Vice President of Development Nate McMurray on unpaid leave without explanation. McMurray was running for Congress against Chris Jacobs, a member of the family that owns the company. McMurray viewed the move as retaliation for running against Jacobs.
Yellowstone National Park Labor Violations
On February 14, 2020, four Yellowstone Vacation Tours Employees, including two summer Yellowstone NPS rangers, were fired after a document leaked to management proposing terms of unification—terms including a living wage, healthcare, sick pay, and conversations over why Yellowstone Vacation Tours was taking in a number of guests with high risk for CoVid-19. A fifth employee was fired three days later, less than an hour after participating in a peaceful protest. Two more employees were later constructively discharged in the following weeks. In March 2020, Delaware North, DBA Yellowstone Vacation Tours and Two Top Snowmobiles, was served with 11 federal labor charges. Charges were built on evidence that the managers in West Yellowstone: "interrogated its employees about their sentiments regarding unions"; "surveilled the protected concerted activities of employees engaged in a picket"; "terminated and effectively terminated the employment of its employees for engaging in federally protected union activity"; "engaged in the conduct (...) because the employees (...) engaged in union and/or protected concerted activities, and to discourage employees from engaging in these or other union and/or protected, concerted activities"; "interfering with, restraining, and coercing employees in the exercise of the rights guaranteed in § 7 of the National Labor Relations Act of 1935 in violation of § 8(a)(1) of the Act", "discriminating in regard to the hire or tenure or terms or conditions of employment of its employees, thereby discouraging membership in a labor organization in violation of §§ 8(a)(1) and (3) of the National Labor Relations Act of 1935".
TD Garden
In March 2020 Delaware North owner Jeremy Jacobs responded to the pandemic by laying off tens of thousands of workers while other NHL and NBA owners pledged to compensate their employees for lost time due to cancelled games caused by the COVID-19 pandemic. Eventually the Bruins were the only team whose owners did not pay their employees for time off while Boston players like Brad Marchand and Charlie Coyle paid out of their own salary to pay the employees.
Awards and recognition
Five Delaware North chefs competed in the 2008 Culinary Olympics in Erfurt, Germany. Delaware North's corporate chef and chief culinary ambassador Roland Henin coached the group. Each chef earned an award for their efforts. Executive sous chef Ambarish Lulay and executive chef Scott Green earned silver medals.
Delaware North Companies Parks & Resorts won the Space Foundation's Douglas S. Morrow Public Outreach Award in 2008.
|
WIKI
|
Quintom scenario
The Quintom scenario (derived from the words quintessence and phantom, as in phantom energy) is a hypothetical model of dark energy.
Equation of State
In this scenario, the equation of state $$p = w\rho$$ of the dark energy, relating its pressure and energy density, can cross the boundary $$w = -1$$ associated with the cosmological constant. The boundary separates the phantom-energy-like behavior with $$w < -1$$ from the quintessence-like behavior with $$w > -1$$. A no-go theorem shows that this behavior requires at least two degrees of freedom for dark energy models involving ideal gases or scalar fields.
The Quintom scenario was applied in 2008 to produce a model of inflationary cosmology with a Big Bounce instead of a Big Bang singularity.
|
WIKI
|
Giuseppe Vacca
Giuseppe Vacca (Naples, 6 July 1810 – Naples, 6 August 1876) was an Italian jurist, magistrate and politician.
Career in the Kingdom of the Two Sicilies
After graduating in law, in 1848 Giuseppe Vacca became a magistrate and attorney general of the Grand Criminal Court of Naples; he was then appointed Undersecretary of the Interior and subsequently of Justice in the Troya government. He drafted the government's protest note addressed to King Ferdinand II on the parlous conditions of the kingdom. After the fall of the liberal ministry and the king’s abrogation of the Constitution, Vacca was first arrested and then, in 1850, condemned to exile. In 1859 King Francis II pardoned him and invited him to serve as Minister of Justice, but he refused. In 1860 he was general secretary of the southern action committee which advocated Garibaldi's entry into Naples.
Career in the Kingdom of Italy
After the unification of Italy, Vacca was attorney general of the Court of Cassation of Naples, and in 1861 he was appointed senator by Victor Emmanuel II. He also served as Minister of Justice in the second La Marmora government, from 28 September 1864 to 10 August 1865.
His role in the government in 1864 was important, as he presented a bill to Parliament for legislative unification, asking Parliament to delegate its right to discuss the draft civil code directly to the government. A commission was therefore created, chaired by him, which drew up a new civil code and another of civil procedure, both of which came into force on 1 January 1866. The situation was different with the Penal Code, which was developed from the Savoy Penal Code and extended to all of Italy, except Tuscany (due to Tuscan rejection of the death penalty); only in 1889 did Keeper of the Seals Giuseppe Zanardelli succeed in extending a new penal code to the entire kingdom.
|
WIKI
|
A Family Travel Playbook: Make Plans, Prepare to Let Them Go
Personal Journeys Clearly, the GPS had gone haywire. We were sitting in our rental car in Belgium, in search of Bruges. After directing me down a series of increasingly narrower country roads, it now wanted me to head into the driveway of a modest suburban house. The children in the backseat were laughing; my wife, to my right, was not. “It’s getting dark. What are we going to do?” It was April 2015 — it is always April when we take these trips — and the sky had turned a striking orange behind the just-budding branches of the trees and the occasional windmill that glided by the windows of our rental car. My wife, Helene, poked with increasing aggravation at the malfunctioning device on the dashboard. “Mommy — what’s going to happen? Belgian bandits?” This was my son, Dean, who sat behind me. “This is fun.” We hadn’t seen a soul for at least a half-hour. And the engine shut off every time I stopped. So at the moment: complete Belgian silence. “O.K. — I’d dead-reckon,” I said. “Let’s go into the driveway!” said my daughter, Paulina. “No!” my wife said. Dead-reckon I did. Bruges is near the coast, right, and the water had to be to the west, right? I backtracked to the last major road and kept the waning sun in front of us. And then 30 minutes later, emerging in the distance in jagged blue-gray shapes — and unmistakable — were the sharp spires of the medieval city, piercing that orange and announcing that we’d arrived, modern devices be damned. *** The episode has become legendary in my little family, one of those moments from our travels that we all recall in short hand — “The crazy Belgian GPS!” — and probably always will. There are quite a few others. Like the English couple running a bed and breakfast in Normandy who kept their place shiveringly cold; did not speak French; had never been to Paris; and went on and on, unbidden, about how much they disliked the French. Or the time, in Shirakawa, Japan, when I asked the man who owned the thatched-roof farmhouse where we’d spent the night if he could provide a discount coupon for the local onsen (hot springs resort). He didn’t understand me, so he called up a translation app on his iPhone. I spoke into it and technology failed us again. Instead of requesting an “onsen discount,” the app told him I wanted “unscented pork.” We could hear him laughing as we headed down the hill. For the remainder of our time in Japan, whenever we sat down to a meal, “Unscented Pork!” was a family rallying cry. I’m writing this now because that trip to Japan, in April of this year, was something of a final chapter for Helene, Dean and Paulina and myself. Dean is 17 and off to college. For seven years, we have taken an ambitious trip during spring break. Everyone has had a vote in our destination — Europe four times, Hawaii, the West Coast (spiritually a different country than Brooklyn, where we live, right?) and Japan. Their public school vacations always lined up, making planning a snap. But that won’t happen anymore with Dean in college. Also, we’ll be broke. Helene and I went all in on these trips — dipping into the home equity account some years, and letting my American Express travel account grow alarmingly — because we saw a brief window when Dean and Paulina, who just turned 14, would be old enough to get a lot out of these journeys, and be fully mobile, yet young enough that they enjoyed spending time with us. These windows snap close fast. We developed a model, and certain patterns emerged. We’ve mixed food and history with views and long walks and mastered transit systems. We plan but not too much. We try to fly nonstop, and accept that at some point someone will get sick. We don’t worry about the weather. (April is unpredictable and it’s always April.) And we’ve accepted that togetherness is great, but so is breaking down into smaller units, even units of one. It seems a shame not to be able to put this knowledge to use; so maybe I can pass it on to other parents whose sons and daughters are nearing the late single digits, and who want to get back out there and see the world, along with the fresh eyes of children. It can be done. Debt or not – these trips were worth every penny. *** First, the destination. Serendipity, individual interests and price always play roles. The first trip was to Ireland for the simple reason that we saw an ad for $400 round-trip flights on Aer Lingus. Scotland came next because Helene’s niece was in school in Glasgow, but also because the flight was $1,000 per person, and flights to Paris – Dean’s top choice – were $1,400. Also, I’d learned in Ireland that I’m pretty good at driving on the wrong side of the road, and I wanted to have another go. A year later, Paris was $1,000 a person, so off we went. Paulina’s dream was Hawaii, so that came next; at $750 a person on Hawaiian Airlines, it felt like a bargain. Japan is my thing, so we’d decided that it would be the grand finale. I booked the roughly $1,000 fare on Japan Airlines nine months in advance on Expedia. The basic model was to stay in one place and take trips: Paris for 10 days, with a night in Normandy; Amsterdam for five days, Bruges for two. We saw much of Ireland from our bed-and-breakfastbase in Oughterard. But some trips involved more running around: driving a circle route around Scotland and the nonstop, even frenzied train journey around Japan, rail passes in hand. Sometimes Helene took the lead in researching and booking hotels, sometimes I did. She did better. We’d poll friends and family, search the Travel section and put the internet to use. We bunked together at the Falls of Dochart Inn in Killin on our first night in Scotland, the falls themselves just audible through the windows; stretched out in a suite at the Sir Francis Drake Hotel in San Francisco (a splurge), the trolley cars clanging on Powell Street; and slept deeply in that Japanese farmhouse (stone cold silence). The former sugar plantation workers’ cottage in Kauai (my find) was cheap at roughly $250 a night, and truly memorable — red sunsets behind palm trees lining the black-sand beach; Paulina in the pool for hours. Not quite so successful was the apartment I rented through a friend near the Luxembourg Gardens in Paris, where the heat was out for three days and where I broke the washing machine. *** The flights and hotels booked, the preparation phase began. The DVD player went into overdrive. Before Ireland, we watched John Ford’s “The Quiet Man,” with John Wayne — the stone bridge glimpsed near the opening is outside Oughterard — and David Lean’s epic, “Ryan’s Daughter,” with Robert Mitchum. Paris was previewed in Truffaut’s “The 400 Blows”; Hawaii with Alexander Payne’s “The Descendants.” In the weeks before Amsterdam and Bruges we watched “The Fault in Our Stars” and — bad parenting alert! — “In Bruges,” Martin McDonagh’s R-rated, blood-soaked hitman comedy. And we read. Paulina tore through “The Fault in Our Stars” before Amsterdam, and Helene read us the opening pages of Ernest Hemingway’s “A Movable Feast” before Paris. Dean finished “Giving Up the Gun” — a slim but fascinating volume on how the samurais reverted to the sword in the 1600s — just before we took off for Japan. I’m not sure if these little culture dives enhanced Dean and Paulina’s experience, but I’m pretty sure they gave some depth to the vistas they saw — a three-dimensional understanding that these were not just places to view and photograph, but to experience as others had before. *** There is no way to sugarcoat it — the first flight is always a misery. Coach seats are plenty big for children, and the entertainment options keep them busy for a while, but Dean and Paulina slept fitfully if at all on our trans-Atlantic flights and were weary by the time we landed. My wheels-on-the-ground exclamations to cheer them up — “We’re in Amsterdam, start of our Grand Tour of the Low Countries!” — drew only sleepy eye-rolls. Dean was looking pretty green as we headed down the aisle to get off the double-decker Air France A380 Airbus that had delivered us to Charles de Gaulle airport. It was while we passed through first class that he threw up. To this day I’m thankful for the flight attendant’s nonchalant charm and grace in the face of Dean’s and my mutual mortification; she was either the kindest person who’d ever lived, or an actress on par with Catherine Deneuve, to whom she bore a not slight resemblance. Now, for all parents — hear what I say: if at all possible, book a hotel room for the night before you arrive so you can go right in and take a three-hour nap. Otherwise, you might find yourself waiting with two exhausted children for several hours for your room to be available, as we did in Scotland. Because when that nap is over, the fun truly begins. To see Paulina’s eyes widen as we stepped out of our hotel into Shinjuku, in Tokyo, with its rushing crowds, flashing neon and bird-tweets emitting from the walk signs was to see a child’s world expand exponentially. “Oh my god this is like another planet.” Same with Dean as we first walked across the Pont des Arts over the Seine in Paris and his brown eyes took in the Pont Neuf, the Ile de la Cite, the towers of Notre Dame and all the rainy-gray and muted brown stone buildings arrayed before us. *** The key to making plans is not making too many. Too little structure and we’d end up wandering the same neighborhoods; too much and the trip becomes a forced march. We always book a few restaurants and, in more recent years, as the crowds have increased, a museum or two. But that’s all. We reserved a specific time at the Rijksmuseum our first day in Amsterdam, and it was a great morning. Enthused, we decided to try for two museums in a row but balked when we saw the long lines at the nearby Van Gogh Museum. So we had a rijsttafel lunch at an Indonesian restaurant we stumbled across. Then we spent some time in a Tesla showroom, for no particular reason. We don’t have to be together, all of us, every minute. Dean started taking long walks by himself in Japan, especially along the river in the mountain city of Takayama, and Helene and I sneaked out to a jazz bar in Kyoto one evening while the two of them luxuriated in their yukata robes back at our ryokan (Japanese hotel). In Paris, after the unfortunate first-class throw-up episode, Dean was laid low for a day, so Paulina and I went up to Montmartre to take in the views and have lunch at a cafe on the Place des Abbesses. Two days later, Dean and Paulina went off on their own with a friend of Dean’s from school. We met them for dessert at Berthillon, the famous ice cream parlor on the Ile St. Louis. That night I decided to go have a drink at Le Select, my favorite of the grand cafes. I invited Dean, and the two of us spent the next 45 minutes negotiating the quiet streets of the Left Bank before emerging into the bright lights of the Boulevard du Montparnasse. We sat at a small table inside. (It was an especially chilly April.) I had a Calvados, and he had an elaborate virgin cocktail. He asked about my drink and I let him dip his pinkie in and try it. He winced. “Do you drink that because you like it, or because you want to be a cool guy?” Good question. “Hmmm. I guess a little of each.” The next night I went back myself — he was exhausted — and I sat at the bar, the waiter with a rag over his shoulder telling his colleague as he cleaned a glass, “Il etait ici hier soir avec son fils.” (“He was here last night with his son.”) *** But even if you only make a few plans, there comes a moment to let them go. The pattern is familiar. At some point, Helene starts to wind down. I have come to strangely enjoy watching her vacation energy arc switch from Let’s-get-going exuberance to exhaustion. On our second to last night in Ireland, we took the kids to a pub to hear music. I detected at least one other pub goer, perhaps a grandmother herself, looking askance at us. Did she mutter under her breath to her companion, Shouldn’t those wee ones be home in bed? The next day, our last, Helene had planned a boat trip to Inishmore, one of the Aran Islands off the coast. She had seemed really excited about it. But I’d begun to see familiar signs: the blank expression, the decreasing eye contact, the inability to engage in a coherent conversation. I suggested that we instead return to Aughnanure Castle, which was nearby and had been a hit with the kids on our first day. She agreed, and we sat beside a glass-clear stream on the castle grounds as Dean and Paulina played with the resident Shorthaired Pointer. Helene fell asleep on the grass -– the start of an epic nap that, after a brief interruption, was continued back at our bed and breakfast. I went in to check on her several times to make sure she was alive. Then I took the kids back down to the pub. Various members of the family can also stage mini revolutions. In Kyoto, looking for a restaurant for our penultimate dinner, we walked past an Italian cafe and everyone’s eyes lit up. Pizza! I objected forcefully – We were in Japan! When would we all be in Japan together again? We have to have Japanese food. How about okonomiyaki? Or ramen? Or yakitori? I got three dirty looks and we were soon taking our seats, English menus in hand. Paulina said what was on everyone’s mind. “Do they have unscented pork?” *** And so, despite all the great food, and the spectacular views, and the visits to pubs and grand cafes, and the museums, the most rewarding parts of these trips have been the explorations of my own family. As they’ve gotten older, acquiring friends and devices, Dean and Paulina have become less the little team they used to be. Their main interaction when we are all together in our house seems to be about who stole the other’s headphones, or keys, or MetroCard. “I hate you!” she’ll tell him with steely eyed rage at the dinner table over this or that imagined slight. “Hey!” I’ll jump in. “I don’t want to hear that word. Don’t say ‘hate.’ Just say, ‘I really, really, really, really don’t like you.’” “Ok – I really, really, really, really don’t like you.” “That’s better.” But not on our trips. They revert to the wee ones who played with that Shorthaired Pointer on the castle grounds. What sounded like an argument in the backseat as we drove up the Pacific Coast Highway — Our Grand California Road Trip — was actually some game they’d invented. I forget if they were trying to touch the other’s arm, or grab something the other had, or win a thumb war — it didn’t matter. Given time, children fill it. But they are old enough, too, to enjoy the fine meal we had in candlelight the night before at Deetjen’s Big Sur Inn, or the ricotta-stuffed roast chicken we had the next night at Tosca Cafe in North Beach. Opinions, insights and observations fly around the dinner table. We’d talk about past trips each of us remembering details that the others had forgotten. Those trips were a time of perfect balance. And I got to check off some important boxes for myself, too. I’d first seen Deetjen’s as I drove along the coast with friends the year after college, in 1988, and swore I’d go back one day. I’d read about the Waimea Plantation Cottages on Kauai in a travel magazine in the early 1990s. It took 22 years to get there. I’d never imagined then being able to share them with my family, or even of having a family. It’s a shame these trips have to end, that spring breaks will cease to line up, that life is so expensive, or that we never made it to several places we’d all wanted to go — Kenya, Germany or Istanbul or Cairo. Although, then again … We’ll all still be free around Christmastime, right? And isn’t that the off-season in places? Hmmm. Excuse me a minute while I check prices on Expedia. Where’s my credit card?
|
NEWS-MULTISOURCE
|
Table 3.
Comparison of overall test performance among those with both CRP and ESR performed simultaneously, N = 43 820a
Disease outcomebnCRP AUCc (95% CI)ESR AUC (95% CI)P-value for CRP versus ESRCRP and ESR AUC (95% CI)P-value for combined versus better single test
Any relevant disease39770.682 (0.672 to 0.690)0.665 (0.656 to 0.674)<0.0010.688 (0.678 to 0.697)<0.001
Infections15650.617 (0.601 to 0.632)0.589 (0.574 to 0.603)<0.0010.619 (0.604 to 0.634)0.018
Autoimmune conditions16630.710 (0.697 to 0.724)0.708 (0.695 to 0.721)0.6800.724 (0.710 to 0.737)<0.001
Cancer8820.774 (0.759 to 0.788)0.766 (0.752 to 0.781)0.0170.777 (0.763 to 0.791)0.006
Polymyalgia rheumatica/giant cell arteritis4760.882 (0.880 to 0.900)0.872 (0.860 to 0.890)0.0990.887 (0.874 to 0.900)0.110
Rheumatoid arthritis5570.691 (0.670 to 0.712)0.690 (0.669 to 0.711)0.8900.700 (0.679 to 0.721)0.007
Seronegative arthritis1510.700 (0.653 to 0.746)0.686 (0.638 to 0.734)0.5100.706 (0.659 to 0.753)0.540
Inflammatory bowel disease2230.698 (0.660 to 0.737)0.691 (0.653 to 0.730)0.4500.701 (0.662 to 0.740)0.510
• a Only 9494 (total amount in 1st column) out of the total 43 820 had a relevant disease outcome. The analysis of test performance uses those with and without relevant disease hence the total n = 43 820 is correct here.
• b Where disease subtypes were examined, diseases other than the specified condition reported were classified as non-diseased.
• c AUC = area under the receiver operator curve, where AUC = 0.5 is equivalent to no diagnostic utility and AUC = 1 is perfect diagnostic accuracy. AUC was calculated using logistic regression modelling with test result(s) on a log scale and age and sex as additional explanatory variables. CRP = C-reactive protein. ESR = erythrocyte sedimentation rate.
|
ESSENTIALAI-STEM
|
Catholic Encyclopedia (1913)/Antoine-Laurent Lavoisier
Lavoisier,, chemist, philosopher, economist; born in Paris, 26 August, 1743; guillotined 8 May, 1794. He was the son of Jean-Antoine Lavoisier, a lawyer of distinction, and Emilie Punctis, who belonged to a rich and influential family, and who died when Antoine-Laurent was five years old. His early years were most carefully guarded by his aunt, Mlle Constance Punctis, to whom he was devotedly attached; and through her assistance he was secured the advantage of a good education. He attended the College Mazarin, which was noted for its faculty of science, and here he studied mathematics and astronomy under Abbé de la Caille, who had built an observatory at the college after having won renown by measuring an arc of the meridian at the Cape of Good Hope, by determining the length of the second's pendulum, and by his catalogue of the stars. Young Lavoisier also received instruction from Bernard de Jussieu in botany, from Guettard in geology and mineralogy, and from Rouelle in chemistry. In logic he was influenced by the writings of Abbé de Condillac, as he frequently acknowledges in his "Traité Elementaire de Chimi." He began his career by entering the profession of the law, but soon abandoned this to return to his favourite studies of chemistry and mineralogy. His first scientific communication to the Academy was upon the composition and properties of gypsum and plaster of Paris, and this is to-day a classic and a valuable contribution to our knowledge of crystallizing cements. He early learned to look to the balance for help in the definition of facts, and found its great value particularly when he began to study the phenomena we now know under the terms combustion or oxidation, and reduction or deoxidation.
The most advanced chemical philosophers of his day taught that there was something in every combustible substance which was driven out by the burning, that the reduction of an oxide of a metal to the metallic state meant the absorption of this substance or principle, which Stahl had called phlogiston. Lavoisier studied the teaching of the phlogistonists, but having also a mastery of physics and of pneumatic experimentation he became dissatisfied with their theory. He seized upon two important discoveries, that of oxygen by Priestley (1774), and that of the compound nature of water by Cavendish (1781) and by a masterly stroke of genius reconciled discordant appearances and threw the light of day upon every phase of the world's reacting elements. His theory, for a long time thereafter known as the antiphlogists' theory, was really the reverse of that of the phlogistonists, and was simply that something ponderable was absorbed when combustion took place; that it was obtained from the surrounding air; that the increase in the weight of a metallic substance when burned was equal to the decrease in the weight of the air used; that most substances thus burning were converted into acids, or metals into metallic oxides. Priestly had called this absorbed substance or gas dephlogisticated air; Scheele called it empyreal air; Lavoisier "air strictly pure" or "very respirable air" as distinct from the other and non-respirable constituent of the atmosphere. Later, he called it oxygen because it was acid-making (oxys, and geinomai).
So great a change ensued in experimental chemistry, and in theory and nomenclature, and such a mass of facts was co-ordinated and explained by Lavoisier that he has been justly called "the father of modern chemistry." He was the first to explain definitely, the formation of acids and salts, to enunciate the principle of conservation as set forth by chemical equations, to develop quantitative analysis, gas analysis, and calorimetry, and to create a consistent system of chemical nomenclature. He made deep researches in organic chemistry, and studied the metabolism of organic compounds. His memoirs and contributions to the Academiy were of extraordinary number and variety. His life in other fields was romantic, full of interest and a social triumph, but sadly destined to end in tragedy. Happily married, and having the aid of his wife even to the extent of employing her in the prosecution and recording of his experiments, he drew around his fireside and to his library at the State Gunpowder Works a circle of brilliant French savants and distinguished travellers from other lands. Early in his career he felt the need of increasing his resources to meet the necessities caused by his scientific experiments. With this in view he became a deputy fermier-général, whereby his income was much increased. But joining this association of State-protected tax-collectors only prepared the way for many years of bitter attack and a share of the public odium attaching to their privilege. He headed many public commissions requiring scientific investigation, he aimed at bringing France to such a state of agricultural and industrial expansion that the peasant and the working-man would have profitable employment and the small landed proprietor relief from the burdensome taxes hitherto purposely increased to make grants to corrupt favourites of the Court. Having incurred the hatred of Marat he found himself, together with his fellow fermiers-général, growing more and more unpopular during the terrible days of the Revolution. Finally in 1794 he was imprisoned with twenty-seven others. A farcical trial speedily followed, in which he was charged with "incivism" in that he had damaged public health by adding water to tobacco. He and his companions, amongst them Jacques Alexis Paulze, his father-in-law, were condemned to death. Lavoisier, who was devotedly attached to him, was obliged to stand and see M. Paulze's head fall under the guillotine, 8 May, 1794. Lavoisier was then 51 years old. His biographers say little as to his last hours. Grimaux relates that all the condemned men were silent and carried themselves with dignity and courage in the face of death. What Lavoisier's sentiments were can be assumed from a passage in Grimaux (p. 53) who had been the first biographer to obtain access to Lavoiosier's papers.
Raised in a pious family which had given many priests to the Church, he had held to his beliefs. To Edward King, an English author who had sent him a controversial work, he wrote, 'You have done a noble thing in upholding revelation and the authenticity of the Holy Scriptures, and it is remarkable that you are using for the defence precisely the same weapons which were once used for the attack.' His goods and chattels and all his scientific instruments were listed and appropriated on the day following his execution, though Mme Lavoisier succeeded in having some restored to her. She was childless and long survived him.
.
|
WIKI
|
* Proportionate sampling without replacement. *actually sampling is done with replacement but a block is retained only the first time it is selected. *City blocks have different populations. The objective is to select a random number of blocks where the probability of selecting a given block is proportional to its population. *The 3 files draw file1.sav draw file2.sav draw file3.sav contain intermediary results. The sole purpose of these files is to help understand and verify what the syntax is doing. * Raynald Levesque raynald@spsstools.net . *************************************************************. *Generate a file of 1000 cases for illustration purposes. *************************************************************. NEW file. input program. loop block=1 to 1000. leave block. compute pop=RND(uniform(10000)). FORMATS block pop (F8.0). end case. end loop. end file. end input program. execute. SET MPRINT=ON. */////////////////////////// BEG OF MACRO//////////////////////////////. DEFINE !SAMPLE (draw=!TOKENS(1) /keep=!TOKENS(1)) COMPUTE case# =$casenum. CREATE t_weight=CSUM(pop). SORT CASES BY case#(D). CREATE c_weight= CSUM(pop). SORT CASES BY case#. IF $casenum=1 #tot_pop=c_weight. VECTOR rva rvb (!draw F8.0). !DO !cnt = 1 !TO !draw DO IF $casenum=1. COMPUTE !CONCAT(rva,!cnt)=UNIFORM(#tot_pop). LEAVE !CONCAT(rva,!cnt). COMPUTE !CONCAT(rvb,!cnt)=!CONCAT(rva,!cnt)lag(t_weight)). END IF. !DOEND COMPUTE flag=MAX(rvb1 TO !CONCAT('rvb',!draw)). SAVE OUTFILE='draw file1.sav' /COMPRESSED. SELECT IF (flag=1). EXECUTE. SAVE OUTFILE='draw file2.sav' /COMPRESSED. VECTOR rvb=rvb1 TO !CONCAT(rvb,!draw). * the same block may have been selected more than once but only the first occurence is kept. COMPUTE done=0. LOOP cnt=1 TO !draw. DO IF rvb(cnt)=1 AND done=0. XSAVE OUTFILE='draw file3.sav' /KEEP block cnt. COMPUTE done=1. END IF. END LOOP. EXECUTE. GET FILE='draw file3.sav'. SORT CASES BY cnt. SELECT IF ($casenum<=!keep). EXECUTE. !ENDDEFINE. */////////////////////////// END OF MACRO//////////////////////////////. * In this example, we want 120 blocks, we select 150 (with replacement) we delete blocks which were selected more than once we keep the first 120 remaining blocks. !SAMPLE draw=150 keep=120.
|
ESSENTIALAI-STEM
|
User:Team KiWi
Team KiWi is a group of 4 Youtubers who started posting gaming videos in october 2018.
|
WIKI
|
Page:The Black Moth.pdf/129
that afternoon Carstares left Thurze House on one of his friend’s horses. He waved a very regretful farewell to O’Hara and his lady, promising to let them know his whereabouts and to visit them again soon. O’Hara had extracted a solemn promise that if ever he got into difficulties he would let him know:
“For I’m not letting ye drift gaily out of me life again, and that’s flat.”
Jack had assented gladly enough—to have a friend once more was such bliss—and had given Miles the name of the inn and the village where he would find him, for O’Hara had insisted on bringing the mare over himself. So Carstares rode off to Trencham and to Jim, with the memory of a very hearty handshake in his mind. He smiled a little as he thought of his friend’s words when he had shown himself reluctant to give the required promise:
“Ye obstinate young devil, ye’ll do as I say, and no nonsense, or ye don’t leave this house!”
For six years no one had ordered him to obey; it had been he who had done all the ordering. Somehow it was very pleasant to be told what to do, especially by Miles.
He turned down a lane and wondered what Jim was thinking. That he was waiting at the Green Man, he was certain, for those had been his orders. He was annoyed with the man over the incident of the pistols, for he had inspected them and discovered that they were indeed unloaded. Had his captor been other
|
WIKI
|
'Rebel' Prince Charles could put monarchy at risk, author says
LONDON (Reuters) - Prince Charles, the “rebel” heir to the British throne, will face a battle to win over Britons and could even put the monarchy at risk if he does not temper his strong views when he eventually becomes king, a royal biographer says. Charles, who turns 70 next week, will be the oldest monarch to be crowned when he finally succeeds his 92-year-old mother Queen Elizabeth. Tom Bower, whose unauthorized “Rebel Prince” biography of Charles was published earlier this year, said the prince was intelligent, kind and sensitive but also selfish, ungrateful, and a lover of luxury whose stubborn streak could risk the institution itself. “I think Charles will try his hardest to be a good king,” Bower, who describes himself as a committed monarchist, told Reuters. “The question will be how he behaves, whether he abandons a lot of the qualities that were shown in the preceding 20, 30 years. “I do believe the queen and (her husband) Prince Philip have been thankful to live so long to prevent their son being the monarch because he would have jeopardized it.” Such critical portraits of the prince are not new. Since the public breakdown of his marriage to Princess Diana in the 1990s, his lifestyle and views on issues such as climate change, religion, alternative medicine and architecture have often had unfavorable treatment. “As a teenager, I remember feeling deeply about this appallingly excessive demolition job being done on every aspect of life,” Charles said in a written response to Vanity Fair magazine for an interview published this month. “In putting my head above the parapet on all these issues, and trying to remind people of their long-term, timeless relevance to our human experience - never mind trying to do something about them - I found myself in conflict with the conventional outlook which, as I discovered, is not exactly the most pleasant situation to find yourself.” Bower, whose biography was based on interviews with 120 people including some who worked closely for the royals, said the prince was committed to issues like the environment but was someone unable to take criticism. “He’s very keen to criticize others but cannot tolerate those who challenge him,” Bower said. “He’s a person who is driven, who undoubtedly wants to do good but doesn’t understand that the consequences of a lot of his actions cause a lot of trouble and he doesn’t like to be told that he might be doing something wrong.” Former aides who have worked closely with Charles say many of the stories in Bower’s book are simply not true. The prince himself has dismissed a story that he travels with his own toilet seat. “I can understand why critics will write ... negatively, but all they’re doing is taking a facet of him and making it the most negative possible,” one former close aide of many years, who described himself as a big fan of Charles, told Reuters. “It’s not such a contradiction that people have these polar views of him because somewhere in the middle is the real man.” Supporters of the prince say his detractors are often those with axes to grind airing exaggerated grievances. “That reflects on Charles for causing those people to have a grievance,” Bower said. “You don’t find people speaking with grievances against the queen.” While the queen was a unifier, he said: “Charles does the opposite. He divides the nation between those who like him and dislike him, he divides his own court, he creates hostility when he be creating harmony and that’s his trait.” Bower said Charles had rebelled against his parents, saying the demise of his relationship with Diana and the romance with his second wife Camilla was part of that rebellion. “He has a view of the world and he wants to impose his view of that world, so in every way he doesn’t want to conform to expectations, so that makes him a rebel,” he said. “I think that if he’s a rebel king, the monarchy will be in danger and I think that is the great problem we face.” Editing by Guy Faulconbridge and Giles Elgood
|
NEWS-MULTISOURCE
|
Sample Code
This page lists sample code for a few common use cases. While samples are provided in Python language, functionality can be ported in any language.
Creating Lightning ADC Cluster
Lightning ADC cluster may be of type Auto or Manual. The code here demonstrates how to create a cluster of type Manual. The cluster ID returned at the end of script is the unique ID of the cluster. This is to be supplied to the Lightning ADC instance. When Lightning ADC connects to the Harmony Controller, it identifies the cluster which the instance belongs to, and places accordingly.
Creating an Application
For creating an application configuration, the entire object hierarchy needs to be created. Calling POST APIs of the objects in the sequence does the job. By default, all the values are taken as default. Only required items are name of the application and first domain for which the application is being created. However, for application to work properly and handle traffic, a few more things like Server IP addresses and Lightning ADC Cluster is also required.
The code example here assumes that required data is available in a JSON file (app_params.json) and makes following calls in sequence:
1. Create Session
2. Create Application
3. Create Domain EndPoint
4. Create Service EndPoint
5. Create Smart Flow
6. Create Smart Flow Policies
7. Associate Application to a Lightning ADC Cluster
Tear Down
Tear down here refers to deleting application and Lightning ADC cluster. Before a cluster can be deleted, it should be removed from all applications. Also all the ADC instances should be removed from the cluster. So the steps for tear down are as following:
1. Delete application
2. Read all ADC instances in the cluster and delete them - the instances should be shut down manually before performing this
3. Delete Cluster
|
ESSENTIALAI-STEM
|
The American Revolution was caused by the colonists disagreeing with the British. The things that the british and colonists disagreed on were the Proclamation of 1763. One of the many things that the colonists thought needs changed is how the colonies approach war, which is why the political cartoon of a snake was made. The stamp act taxed most goods in the colonies. The Quartering Act angered colonists, and strengthened distrust between the colonists and the british soldiers. John Dickinson’s letters gave courage to the colonists to protest. The Boston Massacre, as Paul Revere painted it, was one of the most influential paintings to rebel against the british. These are just some of why the colonists rebelled and protested against Great Britain.
In the middle of the French and Indian war, 1754 to be exact, Benjamin Franklin introduced one of the first, or the first, ever political cartoons in the new world. The political cartoon was of a snake severed into thirteen parts. Each part of the …show more content…
to pay off their debt, they taxed many of the goods being shipped to the new world. This action was called “The Stamp Act” and was put into effect in the colonies in 1765. Taxes were very easily to collect because colonists could not spread out across the Appalachian mountains. The stamp act angered colonists because why would the british parliament be able to tax the colonies without anyone to argue the law. Many colonists took up to saying, “No taxation without representation”. In the same year as the stamp act, Great Britain sent
40,000 british soldiers over to the colonies to help collect taxes. Colonists were forced to house british soldiers, and give them food and supplies for however long they would stay in their house, or even just pass by, which was called “The Quartering Act”. The quartering act only strengthened distrust between colonists and british
|
FINEWEB-EDU
|
Stacks if cubed sugar against a red backdrop
Education
Insulin and Insulin Resistance
0 comments
We talk a lot about insulin and insulin resistance on the blog. It is one of these words that a lot of people throw around but I sometimes wonder whether people actually know what it means exactly. And so this week, we will dive into the basics around what is insulin and insulin resistance.
A gloved hand holding a needle with liquid inside
Dima Solomin auf Unsplash
What is Insulin?
Insulin is a hormone, which is produced in your pancreas. It is essential for our bodies. On a very basic level, it turns eaten food into energy within our cells. It also regulates our blood sugar levels. How does it do that? By messaging cells to absorb glucose (our primary energy source) from our blood stream – either into your muscles, fat, or liver. Your pancreas decides how much of the hormone needs to be produced and “send out” into the bloodstream. This is based on the levels of blood glucose in your body. When stored in the liver, your body can also access this glucose again in times of fasting.
You can see how insulin is super important for our bodies. You can also see how insulin is essential in order to ensure that our blood sugar levels are neither too low or too high at any given time. If one or the other continue over time, they may lead to serious health consequences.
A rollercoaster going down with people in it
Jonny Gios auf Unsplash
Problems with Insulin
There are several things that can cause issues with insulin and, consequentially, our blood glucose levels.
Type 1 Diabetes
In some people, our immune system attacks the part of the pancreas that produces the insulin leading to either too little or no insulin production whatsoever. This is called Type 1 Diabetes. People who are Type 1 diabetic need to inject regular shots of insulin in order to survive
Insulin Resistance
Insulin resistance means that your fat, liver, and muscles do not respond well to soaking up glucose from the insulin produced. Think of a key that kind of sits in a bit of a tricky lock and does not easily turn any longer. As a result of this, your pancreas needs to produce more insulin in order to help support this slightly tricky, not-so-great-working system.
Prediabetes
Prediabetes means that your body has a consistently higher blood glucose levels than what is considered a normal range. However, you are not in a Type 2 Diabetes scenario yet. It usually occurs in people who are already somewhat insulin resistance. Without enough insulin your blood glucose continues to stay elevated in your bloodstream.
Type 2 Diabetes
Type 2 Diabetes is a combination of your pancreas not being able to produce enough insulin in order to regulate your blood sugar levels. At the same time, your cells are not responding to the absorption process. Type 2 Diabetes can mean a slower process that accumulates over time. In many cases moving through first insulin resistance and prediabetes first.
A rollercoaster going high up in the air and coming down
Skyler Gerald auf Unsplash
What Happens If We Have Constantly Elevated Blood Sugar Levels?
Too much blood sugar in your bloodstream will, unfortunately, trigger at the same time an increased inflammatory response. I am conscious that I say this a lot (because it is true!!) but inflammation is one of the key drivers of Western diseases. That means constantly elevated levels of blood sugar also mean higher risks of obesity, heart disease, stroke, and Alzheimer’s disease (which is, as we now know, an inflammation of the brain). There is also more and more research linking inflammation to our mental health – think anxiety and depression.
Just to add a cherry on top of this conversation (I know, I know), it also means that we are speeding up our aging process. You have to think about our body like a toaster. Every time we raise our blood sugar levels massively, we basically brown that toast. The more and quicker we brown the toast, the more we age in a shorter amount of time. So, in summary, elevated blood glucose levels and a constant stream of insulin are not so great for our bodies.
I want to point out that science now knows that more than 90% of people without diabetes experience blood sugar spikes. A blood sugar spike is usually defined as more than 30mg/dL after eating (1.7 mmol/L). For a very long time, it was assumed that only people with diabetes will experience such strong spikes. The idea is to keep the curve as flat as possible. P.S.: I will not go into too much details re. those numbers. I strongly encourage you to speak to your healthcare professional in order to figure these numbers out.
A room with colorful windows and the word "tired" spelled out
howling red auf Unsplash
How Do I Know If I Have Problems With Insulin?
The easiest and quickest way to determine blood sugar levels in your body is through blood testing at a doctor’s office. Doctors most often use a test called fasting plasma glucose (FPG) or an A1C test to diagnose prediabetes. FPG shows your blood glucose levels at the time of the test. A1C measures your levels over a 3 month period of time. There is also an oral glucose tolerance test (OGTT), which means that subjects drink a sugar concoction and get their blood sugar levels measured before drinking, an hour after drinking, and two hours after drinking.
Fasting blood sugar levels should be at least 100 mg/dL (5.5 mmol/L). Optimal levels are below 85 mg/dL (4.7mmol/L). Fasting insulin levels (a great indicator at predicting glucose challenges early on) should ideally be below 6. Insulin resistance can also be measured through something called the “Homa-Index”. Again, this is a determined through a blood draw. Below 2 means there is little likelihood of insulin resistance, between 2 – 2.5 there is a likelihood, and between 2.5 and 5 there is a strong likelihood. Above 5 usually indicates that people already experience Type 2 Diabetes.
Granules of sugar photographed up close
John Cutting auf Unsplash
The Takeaway From This Post
Insulin and insulin resistance are topics that will likely receive even more attention in science and research in the coming years because they are on the of the key contributors to our longevity and overall health. If you want to know how to jump off this rollercoaster of blood sugar be sure to check out the following posts:
I hope this post helped! Let me know your thoughts in the comments below. Beautiful cover photo from Mae Mu auf Unsplash.
Leave a Comment
Your email address will not be published. Required fields are marked *
*
This site uses Akismet to reduce spam. Learn how your comment data is processed.
|
ESSENTIALAI-STEM
|
Wikipedia:Reference desk/Archives/Miscellaneous/2016 November 16
= November 16 =
Why are mathmatical equations displayed so small?
Why are mathmatical equations displayed so small in all science technology engineering and mathmatics? <IP_ADDRESS> (talk) 22:01, 16 November 2016 (UTC)
* Are you asking about how equations are displayed in Wikipedia articles, or in general? -- ToE 22:43, 16 November 2016 (UTC)
* Can you point us to any examples? ←Baseball Bugs What's up, Doc? carrots→ 23:22, 16 November 2016 (UTC)
As an example see Wikipedia Einstein Field Equations > mathmatical form.
Why are mathmatical equations displayed so small?
Why are mathmatical equations displayed so small in all science technology engineering and mathmatics? As a single example please see Wikipedia, Einstein Field Equations, mathmatical form.
To be be more consices and clear. Can Wikipedia do anything to enlarge the display of mathmatical formulas in general. I'm not asking how the program works that creates the display. I'm asking can the mathmatical equations be made large enough without manipulating anything in a Wikipedia article such that a person with poor vision could read the formulas. In general across all Wikipedia articles with mathematical equations. <IP_ADDRESS> (talk) 16:53, 17 November 2016 (UTC)
* The easiest way to make the equations larger is to use the zoom function of your web browser. Usually this is activated by holding down the Control/Command key and tapping the plus sign on the keyboard. Further instructions: Internet Explorer, Google Chrome, Mozilla Firefox. clpo13(talk) 17:02, 17 November 2016 (UTC)
Matt Lauer, Hillary Clinton, Donald Trump interviews
What has Lauer said in responwse to criticisms of his interview with Clinton and Trump?<IP_ADDRESS> (talk) 23:40, 16 November 2016 (UTC)
* I wish I could point you to any public statements by Lauer responding to his critics, but I have spent a good five minutes mining Google with various search attempts, and can't find any. Perhaps he hasn't has any response. I can't, unfortunately, provide a source that says "he said nothing", but I can say I can't find any source at all. -- Jayron 32 03:06, 17 November 2016 (UTC)
|
WIKI
|
Page:Karl Kautsky - Georgia - tr. Henry James Stenning (1921).pdf/67
of mere power, and thinking that its possession alone is sufficient to ensure the fulfilment of the desires and the satisfaction of the wants of the proletariat, at one stroke.
A Socialist Government must always keep steadily in mind that its activities are restricted by the economic necessities, and possibilities, and it may not overstep these limitations without jeopardising society and the progress of the workers to, better conditions of living. With every measure of socialisation, it must verify exactly the condition of the branch of industry, and the capabilities and resources which are at its disposal. With every limitation which it sets upon the will of the employer, it must consider whether the productivity of labour will not thereby be lessened. It must ceaselessly strive to develop the productive forces of the country, and, in so far as this is not yet possible by socialist means and methods, capitalist measures to further this object must be permitted, and under circumstances even encouraged.
The Social-Democratic Government of Georgia has been guided by these principles, and in this have shown themselves to be intelligent pupils of our great masters, Marx and Engels. Whenever a Social-Democratic Government may come into power, it will be obliged to act on the same principles, and the benefit of the Georgian experience will be at its disposal.
The idea that the only task of a Socialist Government is to put Socialism into practice is not a Marxist one, but pre-Marxist and utopian. It conceives of Socialism! as an ideal picture of a complete society. Like ideal conceptions generally, its nature! is very simple. Once it has been thought out, only the necessary power is required to realise this ideal everywhere and under all circumstances. When this result does not immediately follow on the possession of power, it is due either to treachery or to cowardice. A Socialist Government has no other task than the putting into practice of the ideal Socialist State. The
|
WIKI
|
User:Marissabasi/Choose an Article
Article Selection
Please list articles that you're considering for your Wikipedia assignment below. Begin to critique these articles and find relevant sources.
Option 1
* Vaquita
* Article Evaluation
* This is a good topic that has many sources in the online library database at USF. There are gaps in content that I could fill and explore more in depth. The diet section of this article is particularly small and would be a great place for me to fill with more information.
* Sources
* Sources
* Sources
Option 2
* Giant Panda
* Article Evaluation
* This article already has so much information, I feel like the only way I could edit would be to help sum everything up. I do not think this article needs any more information. It is currently up to date and very lengthy.
* Sources
* Sources
* Sources
Option 3
* Red Panda
* Article Evaluation
* This is a fairly good article giving an overall description of the red panda. However, the conservation section of this article is very small. It does not go into depth about specific conservation actions being taken to protect the red panda.
* Sources
* Sources
* Sources
Option 4
* Black rhinoceros
* Article Evaluation
* This is a great article. I was really interested in doing the Black rhinoceros but it seems that this article has everything I would want to include. I would probably add some extra information in the description section for it.
* Sources
* Sources
* Sources
Option 5
* Bornean orangutan
* Article Evaluation
* This is a good article, but I was intrigued by the "see also" section listed at the bottom of the page. It mention human actions and the impact of palm oil along with deforestation. I would like to include a new section for the human impacts that are cause the Bornean orangutan to become endangered.
* Sources
* Sources
* Sources
|
WIKI
|
Rachel York
Rachel York (born August 7, 1971) is an American actress and singer. She is known for stage roles, including award winning performances in Camelot, Hello, Dolly!, Into the Woods, and Anything Goes. She also has performed in film and on television, including her portrayal of Lucille Ball in the 2003 television film Lucy.
Career
At age 19, York approached talent agent Bill Timms. She performed monologues from Nuts and Sophie's Choice and gave him a demo tape with songs from Evita. Timms signed her immediately and described her as being able to "... do anything."
Theatre
York made her Broadway debut as Mallory in the musical City of Angels, and her performance won critical acclaim. Other stage credits include: Fantine in Les Misérables; The Younger Woman in Stephen Sondheim's Putting It Together, which earned her a Drama Desk Award nomination; Norma Cassidy in Victor/Victoria, for which she won a Drama Desk Award; Marguerite in The Scarlet Pimpernel; Lili Vanessi/Katharine in Kiss Me, Kate; Reno Sweeney in Anything Goes; Ruth Sutton in Dessa Rose, earning another nomination for a Drama Desk Award; and Christine Colgate in Dirty Rotten Scoundrels.
York appeared as Guenevere in the National Tour of Camelot in the 2006–2007 season, for which she earned the Golden Icon Award from Travolta Family Entertainment for Best Actress in a Touring Production as well as the Carbonell Award. In 2008, she played Dixie Wilson in Turn of the Century at the Goodman Theater in Chicago. In 2009, she played Dolly Levi in the Reagle Music Theatre production of Hello, Dolly! in Waltham, Massachusetts and won an IRNE Award for her performance.
In 2010, York returned to the Reagle Music Theatre in its production of Into the Woods, where her performance as the Witch earned her another IRNE Award. That same year she played the Lady of the Lake in the Ogunquit Playhouse production of Spamalot.
In 2011, she starred as Billie Burke in the musical Ghostlight Off-Broadway at the Signature Theatre. She then played Anna in the 2011 Walnut Street Theatre production of The King and I.
She starred in the Encores! concert series production of Gentlemen Prefer Blondes as Dorothy Shaw, which earned her and the production rave reviews. The live concert lasted May 9–13, 2012 and was a New York Times Critic's Pick.
York played the role of Reno Sweeney in the national tour of the 2011 Roundabout Theatre Broadway revival of Anything Goes, which began October 2, 2012. For this role, she won the Helen Hayes Award for Outstanding Lead Actress in a Visiting Production. In February 2014, she played Young Belle in the Encores! concert of Little Me.
In May 2015, it was announced that York would appear in the musical Grey Gardens taking the role of Little Edie Bouvier Beale at Bay Street Theater in Sag Harbor, NY. She played the role of Morticia Addams in The Addams Family with 3D Theatricals later that year in Los Angeles.
She returned to Broadway in the musical Disaster!, which played from February to May 2016 at the Nederlander Theatre. In July 2016, York and her Bay Street Theater co-lead, Betty Buckley, reprised their Grey Gardens performance in a limited run at the Ahmanson Theater in Los Angeles.
York originated the role of Gynecia in the Broadway musical, Head Over Heels in 2018. She next appeared as Baroness Rodmilla de Ghent in Ever After The Musical. In October 2021, York once again played Reno Sweeney, this time in the London revival of Anything Goes at the Barbican Theatre.
Film
Her film credits include One Fine Day, Billy Bathgate, Dead Center, Second Honeymoon, Terror Tract, Au Pair II, and the television film Lucy in which she played Lucille Ball. Her performance in the London production of Kiss Me, Kate is available on DVD/video. She also played Lori, The Mystery Woman in Sasha Gordon's highly praised film It Had To Be You.
Television
She also has many credits in television, including appearances on Reba, Frasier, Arli$, Spin City, The Naked Truth, Diagnosis: Murder, and also provides the voices of Bitty on Higglytown Heroes and Circe on Justice League Unlimited. In 2008, she also guest starred on an episode of Hannah Montana, playing Isis on the episode Yet Another Side of Me. York filmed for the TV series Power in 2015 and is featured in Episode 7 "You're Not the Man" as Tina Schulman. She was also guest starred in Frasier as Dinah or "Officer Nasty" in the episode "To Thine Old Self Be True" (Season 7, Episode 20). In 2017, she starred in The Mick, The Implant episode as Dr. Goodby.
Singing
York released her debut album Let's Fall in Love in early 2005, produced by Tor Hyams under the HyLo Entertainment label and was exclusively distributed by Barnes and Noble. She can also be heard on the Cast recordings of City of Angels, Victor/Victoria, The Scarlet Pimpernel: Encore!, Dessa Rose, Putting It Together, Summer of '42, the soundtrack of Billy Bathgate, and recordings of Opal and Celebration of Life.
Personal life
She married actor Ayal Miodovnik on July 20, 2010; the couple met while acting together in a stage production in 2003. They have a daughter, Olivia (born 2011).
Theater
* Broadway
* City of Angels (1989) – Mallory Kingsley
* Les Misérables – Fantine
* Victor/Victoria (1995) – Norma Cassidy
* The Scarlet Pimpernel (1998) – Marguerite
* Sly Fox (2004) – Miss Fancy
* Dirty Rotten Scoundrels (2006) – Christine
* Disaster! (2016) – Jackie
* Head Over Heels (2018) – Gynecia
* Off-Broadway
* Dessa Rose (2005) – Ruth
* Ghostlight (2011) – Billie Burke
* West End/London
* Kiss Me, Kate (2002) – Lilli Vanessi/Kate
* Anything Goes (2021) - Reno Sweeney
* National tours
* Kiss Me, Kate (2001) – Lilli Vanessi/Kate
* Camelot (2007) – Guenevere
* 101 Dalmatians Musical (2009) – Cruella de Vil
* Anything Goes (2012) – Reno Sweeney
* Regional Theater Credits
* The Crucifer of Blood – Irene St. Claire
* Putting It Together – The Younger Woman
* Ragtime – Mother
* Hello Dolly! – Mrs. Dolly Gallagher Levi
* Into the Woods – The Witch
* Spamalot – The Lady of the Lake
* The King and I – Anna Leonowens
* The Addams Family – Morticia Addams
* Grey Gardens – Little Edie Bouvier Beale & Edith Bouvier Beale
* Ever After The Musical – Baroness Rodmilla de Ghent
* Concerts
* The Sound of Music – Elsa Schraeder
* Gentlemen Prefer Blondes – Dorothy Shaw
* Little Me – Young Belle
Video games
* Neverwinter Nights 2 – Shandra Jerro
Recordings
* City of Angels – 1990 Original Broadway Cast Recording
* Putting It Together – 1993 Original Off-Broadway Cast Recording
* Victor/Victoria – 1995 Original Broadway Cast Recording
* The Scarlet Pimpernel – 1998 Broadway Revival Cast Recording by Encore!
* Dessa Rose – 2005 Original Lincoln Center Cast Recording
* Summer of '42 – 2006 Cast Recording
* Disaster! – 2016 Original Broadway Cast Recording
* Opal, Honky Tonk Highway and Other Theatre Songs by Robert Nassif Lindsey
* Let's Fall in Love – Solo album released under HyLo Entertainment and produced by Tor Hyams
* Head over Heels - 2018 Original Broadway Cast Recording
|
WIKI
|
--- search: exclude: true --- # Configuration Files and Recipes SuperGradients supports [YAML](https://en.wikipedia.org/wiki/YAML) formatted configuration files. These files can contain training hyper-parameters, architecture parameters, datasets parameters and any other parameters required by the training process. These parameters will be consumed as dictionaries or as function arguments by different parts of SuperGradients. >You can use SuperGradients without using any configuration files, look into the examples directory to see how. SuperGradients was designed to expose as many parameters as possible to allow outside configuration without writing a single line of code. You can control the learning-rate, the weight-decay or even the loss function and metric used in the training, but moreover, you can even control which block-type or activation function to use in your model. You can learn about and define all of these parameters from the configuration files. Here is an example YAML file (training hyper-parameters in this case): ```yaml defaults: - default_train_params max_epochs: 250 lr_updates: _target_: numpy.arange start: 100 stop: 250 step: 50 lr_decay_factor: 0.1 lr_mode: step lr_warmup_epochs: 0 initial_lr: 0.1 loss: cross_entropy optimizer: SGD criterion_params: {} optimizer_params: weight_decay: 1e-4 momentum: 0.9 ``` ## Why using configuration files Using configuration file might seem too complicated or redundant at first. But, after a short training, you will find it extremely convenient and useful. Configuration file can help you manage your assets, such as datasets, models and training recipes. Keeping your code files as clean of parameters as possible, allows you to have all of your configuration in one place and reuse the same code to define different objects. In the following example, we define a training set and a validation set of Imagenet. both use the same piece of code with different configurations: ```yaml train_dataset_params: root: /data/Imagenet/train transforms: - RandomResizedCropAndInterpolation: size: 224 interpolation: default - RandomHorizontalFlip - ToTensor - Normalize: mean: ${dataset_params.img_mean} std: ${dataset_params.img_std} val_dataset_params: root: /data/Imagenet/val transforms: - Resize: size: 256 - CenterCrop: size: 224 - ToTensor - Normalize: mean: ${dataset_params.img_mean} std: ${dataset_params.img_std} ``` Configuration file can also help you track the exact settings used for each one of your experiments, tweak and tune these settings, and share them with others. Concentrating all of these configuration parameters in one place, gives you great visibility and control of your experiments. ## How to use configuration files So, if you got so far, we have probably manged to convince you that configuration files are awsome and powerful tools - welcome aboard! YAML is a human-readable data-serialization language. It is commonly used for configuration files and in applications where data is being stored or transmitted ([Wikipedia](https://en.wikipedia.org/wiki/YAML)). We parse each file into dictionaries, lists, and objects, and pass them to the code either as a recursive dictionary or as function arguments. Let's try running a training session from a configuration file. ```shell python -m super_gradients.train_from_recipe --config-name=cifar10_resnet ``` You can stop the training after a few cycles. The recipe you have just used is a configuration file containing everything SG needs to know in order to train Resnet18 on Cifar10. The actual YAML file is located in `src/super_gradients/recipes/cifar10_resnet.yaml`. In the same `recipes` library you can find many more configuration files defining different models, datasets, and training hyper-parameters. Try changing the `initial_lr` parameter in the file `src/super_gradients/recipes/training_hyperparams/cifar10_resnet_train_params.yaml` and launch this scrip again. You will see a different result now. This is because the parameters from `cifar10_resnet_train_params.yaml` are used in `cifar10_resnet.yaml` (we will discuss thin in the next section). Two more useful functionalities are ```commandline python -m super_gradients.resume_experiment --experiment_name=cifar10_resnet ``` that will resume the experiment from the last checkpoint, and ```commandline python -m super_gradients.evaluate_from_recipe --config-name=cifar10_resnet ``` that will run only the evaluation part of the recipe (without any training iterations) ## Hydra Hydra is an open-source Python framework that provides us with many useful functionalities for YAML management. You can learn about Hydra [here](https://hydra.cc/docs/intro). We use Hydra to load YAML files and convert them into dictionaries, while instantiating the objects referenced in the YAML. You can see this in the code: ```python @hydra.main(config_path=pkg_resources.resource_filename("super_gradients.recipes", ""), version_base="1.2") def main(cfg: DictConfig) -> None: Trainer.train_from_config(cfg) def run(): init_trainer() main() if __name__ == "__main__": run() ``` The `@hydra.main` decorator is looking for YAML files in the `super_gradients.recipes` according to the name of the configuration file provided in the first arg of the command line. In the experiment directory a `.hydra` subdirectory will be created. The configuration files related to this run will be saved by hydra to that subdirectory. -------- Two Hydra features worth mentioning are _YAML Composition_ and _Command-Line Overrides_. #### YAML Composition If you brows the YAML files in the `recipes` directory you will see some file containing the saved-key `defaults:` at the beginning of the file. ```yaml defaults: - training_hyperparams: cifar10_resnet_train_params - dataset_params: cifar10_dataset_params - arch_params: resnet18_cifar_arch_params - checkpoint_params: default_checkpoint_params - _self_ ``` The YAML file containing this header will inherit the configuration of the above files. So when building a training recipe, one can structure the configurations into a few files (for training hyper-params, dataset params, architecture params ect.) and Hydra will conveniently aggregate them all into a single dictionary. The parameters will be referenced inside the YAML according to their origin. i.e. in the example above we can reference `training_hyperparams.initial_lr` (initial_lr parameter from the cifar10_resnet_train_params.yaml file) The aggregated configuration file will be saved in the `.hydra` subdirectory. #### Command-Line Overrides When running with Hydra, you can override or even add configuration from the command line. These override will apply to the specific run only. ```shell python -m super_gradients.train_from_recipe --config-name=cifar10_resnet training_hyperparams.initial_lr=0.02 experiment_name=test_lr_002 ``` In the example above, the same script we launched earlier is used, but this time it will run with a different experiment name and a different initial learning-rate. This feature is extremely usefully when experimenting with different hyper-parameters. Note that the arguments are referenced without the `--` prefix and that each parameter is referenced with its full path in the configuration tree, concatenated with a `.`. ## Resolvers Resolvers are converting the strings from the YAML file into Python objects or values. The most basic resolvers are the Hydra native resolvers. Here are a few simple examples: ```yaml a: 1 b: 2 c: 3 a_plus_b: "${add: ${a},${b}}" a_plus_b_plus_c: "${add: ${a}, ${b}, ${c}}" my_list: [10, 20, 30, 40, 50] third_of_list: "${getitem: ${my_list}, 2}" first_of_list: "${first: ${my_list}}" last_of_list: "${last: ${my_list}}" ``` The more advanced resolvers will instantiate objects. In the following example we define a few transforms that will be used to augment a dataset. ```yaml train_dataset_params: transforms: # for more options see common.factories.transforms_factory.py - SegColorJitter: brightness: 0.1 contrast: 0.1 saturation: 0.1 - SegRandomFlip: prob: 0.5 - SegRandomRescale: scales: [ 0.4, 1.6 ] ``` Each one of the keys (`SegColorJitter`, `SegRandomFlip`, `SegRandomRescale`) is mapped to a type, and the configuration parameters under that key will be passed to the type constructor by name (as key word arguments). If you want to see where this magic is happening, you can look for the `@resolve_param` decorator in the code ```python class ImageNetDataset(torch_datasets.ImageFolder): @resolve_param("transforms", factory=TransformsFactory()) def __init__(self, root: str, transforms: Union[list, dict] = [], *args, **kwargs): ... ... ``` The `@resolve_param` wraps functions and resolves a string or a dictionary argument (in the example above "transforms") to an object. To do so, it uses a factory object that maps a string or a dictionary to a type. when `__init__(..)` will be called, the function will receive an object, and not a dictionary. The parameters under "transforms" in the YAML will be passed as arguments for instantiation the objects. We will learn how to add a new type of object into these mappings in the next sections. ## Registering a new object To use a new object from your configuration file, you need to define the mapping of the string to a type. This is done using one of the many registration function supported by SG. ```python register_model register_detection_module register_metric register_loss register_dataloader register_callback register_transform register_dataset ``` These decorator functions can be imported and used as follows: ```python from super_gradients.common.registry import register_model @register_model(name="MyNet") class MyExampleNet(nn.Module): def __init__(self, num_classes: int): .... ``` This simple decorator, maps the name "MyNet" to the type `MyExampleNet`. Note that if your constructor include required arguments, you will be expected to provide them when using this string ```yaml ... architecture: MyNet: num_classes: 8 ... ``` ## Required Hyper-Parameters Most parameters can be defined by default when including `default_train_params` in you `defaults`. However, the following hyper-parameters are required to launch a training run: ```yaml train_dataloader: val_dataloader: architecture: training_hyperparams: initial_lr: loss: experiment_name: multi_gpu: # When training with multi GPU num_gpus: # When training with multi GPU # THE FOLLOWING PARAMS ARE DIRECTLY USED BY HYDRA hydra: run: # Set the output directory (i.e. where .hydra folder that logs all the input params will be generated) dir: ${hydra_output_dir:${ckpt_root_dir}, ${experiment_name}} ``` > Other parameters may also be required, depending on the specific model, dataset, loss function ect. > Follow the error message in case you experiment did not launce properly. ## Recipes library structure The `super_gradients/recipes` include the following subdirectories: > - arch_params - containing configuration files for instantiating different models > - checkpoint_params - containing configuration files that define the loaded and saved checkpoints parameters for the training > - conversion_params - containing configuration files for the model conversion scripts (for deployment) > - dataset_params - containing configuration files for instantiating different datasets and dataloaders > - training_hyperparams - containing configuration files holding hyper-parameters for specific recipes These configuration files will be available for use both in the installed version and in the development version of SG.
|
ESSENTIALAI-STEM
|
2019 Bonnaroo Music Festival
The 2019 Bonnaroo Music Festival, the eighteenth consecutive edition of the festival, was held June 13 to 16, 2019, at the Great Stage Park Manchester, Tennessee. The tickets were sold out and it was projected that 80,000 people attended the festival across the weekend. The festival was headlined by two sets by Phish, Childish Gambino, Post Malone, Odesza, and The Lumineers.
Set lists
Here are the lists of songs performed at the 2019 Bonnaroo by the headliners:
Line-ups
The line-up for the 2019 festival was announced five months prior, on January 8, 2019. Esquire called the line-up "the weirdest one in years", criticized Post Malone and two Phish's headlining spots.
The information was obtained from BrooklynVegan website. Artists listed from earliest to latest set times.
Thursday, June 13
* This Tent: Donna Missal, Jack Harlow, All Them Witches, Rolling Blackouts Coastal Fever, The Comet Is Coming, SunSquabi
* That Tent: Peach Pit, Caroline Rose, Grand Ole Opry, The Nude Party, Magic City Hippies, Saba
* The Other: Dorfex Bos, Hekler, Eprom, 12th Planet, Space Jesus B2B Eprom B2B Shlump
* Who Stage: Kalu & the Electric Joint, Drax Project, Mk.gee, Bülow, Friday Pilots Club, Evan Giia
* Silent Disco: Case Bloom, Shlump, DJ Mel
Friday, June 14
* What Stage: Rival Sons, Catfish and the Bottlemen, The Avett Brothers, Childish Gambino, Phish
* Which Stage: The Teskey Brothers, Nahko and Medicine for the People, AJR, GRiZ, Solange, Brockhampton
* This Tent: Tyla Yaweh, Cherry Glazerr, Parquet Courts, K.Flay, Gojira, Beach House, GRiZ Super Jam
* That Tent: Monsieur Periné, Las Cafeteras, Ibeyi, Anoushka Shankar, Courtney Barnett, Deafheaven, Girl Talk
* The Other: Crooked Colours, Mersiv, Ducky, Medasin, Jade Cicada, Liquid Stranger, Nghtmre, RL Grime
* Who Stage: Ida Mae, Lola Kirke, Pinky Pinky, Los Colognes, SOAK, Illiterate Light, King Nun
Saturday, June 15
* What Stage: The Record Company, Maren Morris, Hozier, Odesza, Post Malone
* Which Stage: Rubblebucket, Hippo Campus, Juice Wrld, Kacey Musgraves, The National, The Lonely Island
* This Tent: Little Simz, Chelsea Cutler, Bishop Briggs, Quinn XCII, Jim James, Clairo, Gucci Mane
* That Tent: Deva Mahal, Ruston Kelly, Unknown Mortal Orchestra, Shovels & Rope, John Prine, Joe Russo's Almost Dead
* The Other: DJ Mel, Memba, Whipped Cream, SNBRN, TOKiMONSTA, Space Jesus, Gramatik, Zhu
* Who Stage: Honey Harper, Sego, Delacey, The New Respects, Ximena Sariñana, Liily, Republican Hair
Sunday, June 16
* What Stage: Trampled by Turtles, Brandi Carlile, The Lumineers, Phish (two sets)
* Which Stage: Ripe, The Soul Rebels, Hobo Johnson and the Lovemakers, Walk the Moon, Cardi B
* This Tent: Faye Webster, Two Feet, The Lemon Twigs, Lil Dicky, King Princess
* That Tent: Kikagaku Moyo, Bombino, Princess, The Wood Brothers, Mac DeMarco
* The Other: Iglooghost, Cid, Dombresky, AC Slater, G Jones, Illenium
* Who Stage: Sun Seeker, Jared & The Mill, Patrick Droney, I Dont Know How But They Found Me, Super Doppler, Golden West
|
WIKI
|
Smart home cameras market to grow at a CAGR of 14.78% from 2021 to 2026, Distribution channel expansion strategy to be a key trend - Technavio
The global smart home cameras market size is estimated to grow by USD 4.98 billion from 2021 to 2026, according to Technavio. The market is estimated to grow at a CAGR of 14.78% during the forecast period. Moreover, the growth momentum will accelerate. The distribution channel expansion strategy of vendors is a key trend in the market. Home security product manufacturers are adopting an omnichannel strategy. Moreover, vendors are focusing on distributing smart home cameras through physical retai
|
NEWS-MULTISOURCE
|
1911 Encyclopædia Britannica/Sequin
SEQUIN (the French form of Ital. zecchino, zecchino d'oro), the name of a Venetian gold coin, first minted about 1280, and in use until the fall of the Venetian Republic. It was worth about nine shillings. It bore on the obverse a figure of St Mark blessing the banner of the republic, held by a kneeling doge, and on the reverse a figure of Christ. Milan and Genoa also issued gold sequins. The word in Italian was formed from zecca, Span. zeca, a mint, an adaptation of Arabic sikka, a die for coins. In the sense of “newly-coined,” the Hindi or Persian sikka, anglicised sicca, was specifically used of a rupee, containing more silver than the East India Company's rupee, coined in 1793 by the Bengal government. The “sicca-rupee” ceased to be circulated after 1836. The term “sequin” is now used for small discs made of thin pieces of metal, tinfoil, celluloid or other composite material, highly glazed and brightly coloured, and applied as trimming for ladies' dresses.
|
WIKI
|
C# Recompute specific component
Hi
How can I recompute specific component when I push the button in C# ?
Best,
Shimpei
Try this:
// Rolf
Hi RIL,
Thank you for the reply.
I already tried your method.
However, my component has problem with something that it will calculate only when recomputed(F5).
Re-computing a component once with a button input is tricky. A component will re-compute when the input changes. When pressing and depressing a button this will happen twice.
Rather than using an input, you could just use the “Enable” button on the right click or middle mouse click menus.
You can also add a keyboard shortcut for this under Settings > Interface > Shortcuts > Enable selected.
If you don’t need to solve it all in the same component, Metahopper can assist here, with the “Expire Object” component.
1 Like
Here you have a C# version of what makes Metahopper but selecting the component by its nickname.
Recompute component.gh (5.4 KB)
2 Likes
|
ESSENTIALAI-STEM
|
Talk:Haplogroup L (mtDNA)
Merger proposal
I think that the history of their editing shows that all the present L clade articles are pretty much stubs, and are not likely to change soon. Of course they might one day be subject to a burst of energetic editing, but for the time being it appears one article would be much more appropriate? See Haplogroup L1 (mtDNA),Haplogroup L2 (mtDNA),Haplogroup L3 (mtDNA),Haplogroup L4 (mtDNA),Haplogroup L4a (mtDNA),Haplogroup L5 (mtDNA),Haplogroup L6 (mtDNA)--Andrew Lancaster (talk) 13:12, 1 December 2009 (UTC)
* No merging:
* The African genetic history is the most ancient, diversified and complex. Meanwhile human mitochondrial history is 200,000 years old, the conquest of Europe is only 40,000. However the European population has been given 11 letters in an arbitrary way to define their main haplogroups. East Asia has 8, Australia 3 and Subsaharian Africa only one: “L”. But Europe shows great homogeneous in mitochondrial genetic.
* That means that this system is Eurocentrist (or Occidentalcentrist). The African haplogroups are less advanced because we are not interested enough; but that does not mean they are not important. Making only one article for all of African haplogroups, would be the worst form of Eurocentrism. --Maulucioni (talk) 21:39, 1 December 2009 (UTC)
* This is a similar position to the response of Wapondaponda on WP:HGH but it seems to be based on the idea that articles should be split/merged based on their age, rather than how much there is to say about them?I do not think that merger/split decisions have anything to do with Eurocentrism or with any possible solutions to bias. Even if we should be thinking about bias, do you think it is good for the L articles to all be stubs? Will this lead people to understand their great age and importance?
* Of course, if someone has time to develop them all into articles that would be even better?--Andrew Lancaster (talk) 10:40, 2 December 2009 (UTC)
* I think that what should be done is to develop this article: HG L (mtDNA) in order to lead people to understand its great age, diversification, spreading and importance. I'm willing to do so. If we delete the L articles, then we should also delete articles such as CZ, C, Z, E, G, F, S, R0, JT, and many others that are even shorter than articles like L0, L3 or L1. Every important article starts by being small; don't discriminate against what you call stubs.
* By the way, all these articles are not stubs. Reading Stub: “A stub is an article containing only a few sentences of text which is too short to provide encyclopedic coverage of a subject, but not so short as to provide no useful information, and it should be capable of expansion.” --Maulucioni (talk) 19:53, 2 December 2009 (UTC)
* I think yes, developing these articles would definitely be better, but otherwise, stub or not they would still be more informative to readers, and better even for contributors, if merged in their current form? I think that yes, the same logic could apply to many of the haplogroup articles which seem to have been developed almost blindly over the last year or so. There is no point having an article for every node in a phylogenetic tree. A phylogenetic tree is not an oppressed entity, it is just an effect of someone finding a mutation. To treat subjects fairly, it can not be best to divide them into dozens of little articles no one will ever read.--Andrew Lancaster (talk) 21:31, 2 December 2009 (UTC)
* I am glad that Maulucioni and I have independently come to the same conclusion. There has been indeed some centrism in the scientific community and wikipedia as well regarding mtDNA haplogroups. According to the 2008 publication "Updated Comprehensive Phylogenetic Tree of Global Human Mitochondrial DNA Variation", all the mtDNA haplogroups were named in the order they were discovered, and there was no particular attention paid to phylogenetic relationships. Naturally much of the research was initially in Europe, so Europe picked up the most letters of the alphabet.
* An excerpt states:
* In short the current nomenclature system for mtDNA is not systematic. The YCC did a better job of standardizing Y-chromosome nomenclature. It is possible that the same may be done for mtDNA in the future. Wapondaponda (talk) 10:28, 3 December 2009 (UTC)
* In short the current nomenclature system for mtDNA is not systematic. The YCC did a better job of standardizing Y-chromosome nomenclature. It is possible that the same may be done for mtDNA in the future. Wapondaponda (talk) 10:28, 3 December 2009 (UTC)
* That's because Y DNA haplogroups came a decade after mtDNA's, hind-sight is 20-20. Merging these haplogroups together is an altogether bad idea. Simply because African studies have not caught up with Eurasian levels of typing given the African diversity is no reason to merge. If you really wanna see some sucky nomenclature try HLA-A and B, where they could not distinguish the two loci for the first 10 years and serially named serotypes at for 2 loci treated as one. Andrew, don't you have a few Y-DNA articles that need to be fixed, try R1b1, which you started to work on and quickly petered out, do I need to come over an hold your hand on that one also?PB666 yap 04:44, 15 December 2009 (UTC)
merging
Given this haplogroup's importance, I think that the most accurate name to call this article is Macro-haplogroup L (mtDNA). --Maulucioni (talk) 23:03, 8 December 2009 (UTC)
* In the sense that Haplogroup L is universal, I agree that it is somewhat different. However, the problem is convention and consistency. Other lineages such as haplogroup L1, L2, M, N and R are also sometimes referred to as macrohaplogroups, but we have maintained the "haplogroup" naming system. Wapondaponda (talk) 04:15, 9 December 2009 (UTC)
* Merge done. Histmerge left. --Maulucioni (talk) 14:51, 10 December 2009 (UTC)
Still trying to avoid stubs
I can see that L has been moved to an article with a new name. But there are still too many stubs in this phylogeny which either need to be written up or (for now) merged. I can see L0 now has a decent enough existence, but should all the others perhaps be merged into an article perhaps called Macro-haplogroup 1-6 (mtDNA)?--Andrew Lancaster (talk) 08:56, 5 February 2010 (UTC)
|
WIKI
|
User:CodePanda/sandbox
Bunder is a locality in Mangalore known for being the place where Mangalore Old port is present. Bunder is just 2 km away from heart of the city. Earlier this port was used to ferry goods and passengers to Lakshadweep island and Middle East countries. Now fishing has become main activity of this harbour.
= Team Mangalore = Team Mangalore is a group of kite enthusiasts from the Indian city of Mangalore. The team is known for making kites of unique designs, which depict the folklore and rich culture of India has been our main objective.
Team Mangalore is weelknown for the kites with the themes of Indian mythology, legends and ethnic designs, including Yakshagana, Gajaraj (visage of Ganapathy), Garuda, Pushpaka Vimana and others. Team Mangalore is behind many innovative kite designs out of which Kathakali, Flying Lizard, Yakshagana are the famous creations which are treat to eyes. They have participated in various international kite festivals in countries like Hong Kong, Italy, Korea, France, Thailand, United Kingdom etc.
Mangalore International Kite festival
Team Mangalore often hosts International Kite Festivals in Panambur beach with the support of industrial giants such as ONGC, MRPL etc.
* Kite festival 2003
* Kite festival 2004
* ONGC International kite festival - 2005
* International Kite festival - 2012
* ONGC MRPL International kite festival - 2010
Achievements
Team Mangalore Wins the 'Best International Kite' Award in the International Kite Festival held in Cleethorpes UK during June 2007.
|
WIKI
|
Wikipedia:Edit filter noticeboard/Archive 3
RFC - creation of the edit filter helper user right
In the section above there is local support for creating a new user right called that will allow read only access to private edit filters. That section is also where all the discussion leading up to this RfC took place. The details of the specific rights included, and the associated processes, are at the new information page Edit filter helper (WP:EFH). While this RfC is in progress, please do not make significant changes to that page.
If this RfC is successful, a request will be made at Phabricator for the right to be created (an RfC or similar display of community support is a prerequiste for this), and once created Edit filter helper will be changed from a proposal to an information and process page and updated appropriately. Thryduulf (talk) 14:23, 14 August 2017 (UTC)
Question: Should the user right detailed at Edit filter helper be created, and the associated processes adopted?
Survey regarding edit filter helper
* Support as initiator. Thryduulf (talk) 14:23, 14 August 2017 (UTC)
* Support. I recognise a small previous discussion on this, but I would prefer the application is extended from 3 days to 4 days, as three days is only a weekend. I also think the recommendation to contact an administrator privately upon removal is a bit awkward, but that's not any real reason not to support. -- zzuuzz (talk) 17:15, 14 August 2017 (UTC)
* Support. I have the editor right, but I only need it (and occasionally at that) to view things. I want to be able to view filters without being able to make accidental edits. Nyttend (talk) 19:09, 14 August 2017 (UTC)
* As an admin you should already have access to these rights without needing to grant yourself the EFM flag. – Train2104 (t • c) 23:02, 14 August 2017 (UTC)
* Correct; abusefilter-view-private is included in the sysop group. Nyttend, you also removed your EFM rights in June ;-) -- Ajraddatz (talk) 23:03, 14 August 2017 (UTC)
* Oops, I forgot :-) All the more reason to have such a user group — it proves that the system can work with a user-rights package that includes view but doesn't include edit, so creating this kind of user rights package shouldn't break anything. Nyttend (talk) 04:52, 15 August 2017 (UTC)
* Support - per my comments in the previous discussions. -- Ajraddatz (talk) 23:01, 14 August 2017 (UTC)
* Support per my comments in the workshop. — xaosflux Talk 01:39, 15 August 2017 (UTC)
* Oppose, as the criteria are not well defined. Provision #3 is "At least basic understanding of account security[note 1]" and Provision #4 is "At least basic understanding of regular expressions if the intent is to assist with authoring filters". These aren't defined in the policy page, and is explicitly defined as " There is no formal definition of what constitutes a "basic understanding", but by requesting this right you are asserting that you meet these criteria. ". Until this can be codified, I am opposed to this policy. Nakon 05:00, 15 August 2017 (UTC)
* Support Much needed for SPI clerks, LTA trackers, and sysops from other wikis who want to piggyback off of our filters. I do agree with though – I argue those two clauses should be removed entirely. They are immeasurable (highly doubt we'll be doing quizzes), and again I feel if they are competent at regex (demonstrated by working at WP:EF/R or mailing list, as explained at WP:EFM), and can be trusted with private logs, they probably can attain full-on edit filter management rights. The primary use case here I think is not for those who want to help with filter details (at least such that it'd require any regex competency), but I understand it could be seen as a stepping stone for those who do. Finally, again, this right as proposed isn't super sensitive, requiring 2FA or anything. I would expect stronger account security for a right that can actually allow you to cause damage. We could bikeshed all day about the requirements for granting, but even as proposed, admins should be able to deduce if a candidate can be trusted, which is all that matters — MusikAnimal talk 16:23, 16 August 2017 (UTC)
* Support and I think the 2 provisions in question should more be admin guidelines for granting rather than requirements, being difficult to codify/quantify otherwise. c.f Rollback expects the user to have a basic understanding of vandalism, which is always left to the judgement of the reviewing admin. Crow Caw 16:52, 16 August 2017 (UTC)
* Support -- There'sNoTime (to explain) 17:04, 17 August 2017 (UTC)
* Support as an active LTA tracker but not admin. ☆ Bri (talk) 17:51, 17 August 2017 (UTC)
* Support as a tool that will help long time vandal fighters identify trends and per prior discussions. -- Dane talk 23:13, 17 August 2017 (UTC)
* Support per above. Clearly beneficial to editors focusing on LTA and SPI. - F ASTILY 23:27, 17 August 2017 (UTC)
* Support: I've dealt with many socks and LTAs and this would be beneficial to those who specialize in these areas. — MRD 2014 Talk • Edits • Help! 00:19, 18 August 2017 (UTC)
* Support: Useful for LTA and long-term vandal fighters. KGirl (Wanna chat?) 00:43, 18 August 2017 (UTC)
* Support Anything to help the users who are constantly fighting the losing battle against vandalism on en.wikipedia. Sparkling Pessimist Scream at me! 02:13, 18 August 2017 (UTC)
* Support could be useful. No reason not to have it so long as there is vetting. TonyBallioni (talk) 02:57, 18 August 2017 (UTC)
* Support I'm starting to get a little leery of there being too many user groups, but as per my comments in the workshop this is useful, especially given the danger involved with write access. – Train2104 (t • c) 03:02, 18 August 2017 (UTC)
* Support per SparklingPessimist. Double sharp (talk) 03:08, 18 August 2017 (UTC)
* Support. Will help those who work in these areas but don't qualify for the edit filter manager right. Anarchyte (work | talk ) 03:42, 18 August 2017 (UTC)
* Support - will greatly help hopeful users that have been noticing relevant disruption associated with even private filters, i.e. filter 860. A certain EFM knows why I'm referencing that filter. jd22292 (Jalen D. Folf) (talk) 05:24, 18 August 2017 (UTC)
* Support - (first time voting on policy RfC) Taking the time to digest what this would entail but from what I've gathered so far it would help combat vandalism and what are so often described as good-faith edits. Edaham (talk) 07:25, 18 August 2017 (UTC)
* Support. Granting certain editors the ability to view but not edit hidden abuse filters will increase the number of editors available for relevant tasks by making the privilege easier to receive, since it is not as easy to abuse as the full set of rights. Inatan (talk) 10:38, 18 August 2017 (UTC)
* Support. Sure, why not. Edit filters are specialist tools so it doesn't hurt to have its own user-right hierarchy. The proposal has demonstrated the need for such a right, especially regarding admins and edit filter managers from other WMF wikis who want to learn from or contribute to enwiki. Deryck C. 10:42, 18 August 2017 (UTC)
* Support. Per WP:EFH. --Wario-Man (talk) 10:45, 18 August 2017 (UTC)
* Support Would be a great help for vandal fighters. RickinBaltimore (talk) 13:10, 18 August 2017 (UTC)
* Support: As a user involved in using edit filters to combat harassment, this would be useful to me. Funcrunch (talk) 13:54, 18 August 2017 (UTC)
* Strong support: Would really help defeat sockpuppetry and long-term abuse. Luis150902 (talk | contribs) 14:53, 18 August 2017 (UTC)
* Support: A useful improvement to help non-admins assisting with such long-time problems. The read-only limitation should prevent any unintentional damage to the filters' functionality. Note that I am probably a bit biased, as I would request such a user-right for spam-related research (several relevant filters about common spamming patterns are currently private). GermanJoe (talk) 15:36, 18 August 2017 (UTC)
* Support per so many above. This would be very useful for helping to protect the project. — Jeff G. ツ 15:44, 18 August 2017 (UTC)
* Support, I see no harm in this and a lot of potential benefits. Seraphimblade Talk to me 16:08, 18 August 2017 (UTC)
* Support Take me as biased, I'm a non-admin working at SPI. -- QEDK ( 愛 • 海 ) 17:58, 18 August 2017 (UTC)
* Oppose as the minimum requirements are fixed too low. Private edit filters are a very vulnerable system. If a malicious user wanted access to edit filters, they could just play good vandal fighter or SPI pseudo-clerk for a while and gain access to every edit filter, breaching the secrecy of the whole system. Private edit filters should be on a need-to-know basis for those who wouldn't be trusted with regular edit filter manager or adminship. Esquivalience (talk) 18:10, 18 August 2017 (UTC)
* This is a right that will given on a strictly need-to-use basis. SPI clerks undergo significant vetting (not being modest, I know) and good vandal fighter is not at all enough for EPH. EPHs will not have any write access, which leads me to ask why you'd think there would be serious misuse. -- QEDK ( 愛 • 海 ) 18:48, 18 August 2017 (UTC)
* Private edit filters generally target specific patterns, and can usually be easily circumvented if the pattern is known to the vandal. A malicious user would not need write access to sabotage them. T. Canens (talk) 03:07, 19 August 2017 (UTC)
* I doubt anyone would find it feasible enough to go through strict vetting, display a demonstrated need for access, just to gain access to regex patterns. The only possibility of abuse here is if people go rogue, and that's plausible everywhere. -- QEDK ( 愛 • 海 ) 09:53, 20 August 2017 (UTC)
* Requests for adminship/Pastor Theo - anything is possible, and it looks like with the declining standards it may happen again. Esquivalience (talk) 20:44, 20 August 2017 (UTC)
* Support: Would be useful in the fight against vandalism. FITINDIA 18:36, 18 August 2017 (UTC)
* Question Regarding point 1 Demonstrated need for access (e.g. SPI clerk, involvement with edit filters) What exactly does this mean? Does it mean that being a vandal fighter, who has knowledge of SAF, has used/patrols SAF to catch vandals and report them, counts as "demonstrated need for access"? L3X1 (distænt write) )evidence( 18:43, 18 August 2017 (UTC)
* There is no list of what does or does not count as a demonstrated need, that's up to the people commenting on the application, but if you can't explain why you need to see the details of private edit filters (and most people don't) then you won't be granted the right. Thryduulf (talk) 21:43, 18 August 2017 (UTC)
* Comment - is this just an admission that it's too hard to promote people to sysop these days? Sorry, but I have this concern that we're going to reach the point where nobody without the most spotless record can get through an RfA and so there are thirty different permissions replacing adminship for which people apply individually and the result is less transparency. Blythwood (talk) 19:31, 18 August 2017 (UTC)
* While I understand those concerns, and share them to some degree, the lack of new sysops is not relevant to the need for this right. Edit filters are a very specialised area (most admins don't even know they have edit filter manager rights, and the separate right for that has existed for years) and not everyone working with them wants or needs the other admin tools. This right will also be useful for users who are not active on en.wp but who are working with edit filters on another project (ru wiktionary as a random example) and are here to borrow our knowledge and expertise. Thryduulf (talk) 21:43, 18 August 2017 (UTC)
* Question - In creating this new user group, bearing in mind that it has some degree of the similarities of administration in it, albeit you're not an admin, would users be required to apply for it in a similar way to an RFA? What would be the process for acceptance into the user group / granting of the right? Dane | Geld 00:17, 19 August 2017 (UTC)
* The process for application is detailed at Edit filter helper. It's nothing as big as an RFA because this is very specialised tool that requires a demonstrated need for access and technical competence to gain, so there really aren't that many similarities to admins. Thryduulf (talk) 07:45, 19 August 2017 (UTC)
* Oppose for now due to the low criteria for granting. Extended confirmed? Way, way too low of a bar. Why don't we just invite the sockmasters in to see the filters aimed to block them? If the criteria for granting (and revoking) is raised, I could support this. But it needs to be much harder for socks to game their way to this right and then go on a vandalism spree. ~ Rob 13 Talk 03:35, 19 August 2017 (UTC)
* Only extended confirmed users with no recent sanctions and a demonstrated need for access will get this right, and even then it's only read only so they can't change anything. It would actually be very difficult for a sockmaster to game their way to this right (requiring likely several months minimum of productive working with edit filters or managing to become an SPI clerk (not easy). Thryduulf (talk) 07:45, 19 August 2017 (UTC)
* Very, very false. I regularly see sockmasters working their way toward extended confirmed. They do it already to attempt to get past ECP protection. It requires only 500 edits to become extended confirmed, which can be achieved in a couple days of counter-vandalism. Further, you haven't defined demonstrated need rigorously enough. I would assume that counter-vandalism activities related to sockpuppetry would be demonstrated need. The reality is that no-one except those who edit edit filters (or perhaps those who do so on other wikis) really need to see them. Why does an SPI clerk need to see a filter rather than grab an edit filter manager and ask them to take a look? They'd need an edit filter manager anyway if they needed to make any changes. I'm very sympathetic to a use case of allowing edit filter managers from other wikis to view our filters, but I'm seriously worried about how easily this will be granted. Keep in mind that effective standards for user rights at PERM tend to be very low. Often, I see admins grant rights to editors who have no business having them, because they handle rights they do not know much about (see, for instance, the AWB PERM page). I'm very worried about what this vague and relatively low criteria will result in. A sockmaster viewing the filter intended to block their actions can get around it very easily. ~ Rob 13 Talk 16:02, 19 August 2017 (UTC)
* Just doing counter-vandalism work would not be a demonstrated need for access as you don't need to be able to see the filters to do that, and a new user requesting this right would raise red flags even if it were sufficient - the standard is "demonstrated need" not "it would be helpful" or "I would like". I agree re WP:PERM which is why requests for this very specialised right will be handled on this page (edit filter noticeboard). SPI clerks, AIUI, mainly need access to see the edit filter logs (a right that the software does not separate from viewing the filters themselves) and the spam blacklist logs but MusikAnimal knows more about that aspect than I do. Thryduulf (talk) 16:31, 19 August 2017 (UTC)
* Why don't we just give edit filter manager to the SPI clerks? I'm fine with that. As for non-SPI clerks, I'll keep the conversation in the subsection below. ~ Rob 13 Talk 18:13, 19 August 2017 (UTC)
* "Why don't we just give edit filter manager to the SPI clerks?" because they don't need, or in at least some cases, want write access. Viewing the details of filters and logs, and seeing why a filter was triggered is not the same as writing or modifying a filter. Thryduulf (talk) 18:28, 19 August 2017 (UTC)
* After further consideration, neutral. What I'd really want to see happen is a decoupling of "view filters" from "view filter logs" and the establishment of an "SPI clerk" user right which allows viewing filter logs (and blocking temporarily for a period not to exceed 72 hours? is that possible with the new temporary blocks?). I'm not convinced by the "I don't want write access". The trust required for write and the trust required for read is the same, so long as we think the applicant is competent to not use the write access if we tell them not to without consulting an experienced filter manager (note that most admins have theoretic access to edit filters but would break the site if they tried using that access...). Still, my concerns are largely addressed by the fact that this won't happen at PERM and will only happen after consensus in a discussion. I anticipate the criteria as written will be raised above "extended confirmed" before this goes live. ~ Rob 13 Talk 03:27, 20 August 2017 (UTC)
* I don't know the answer to your question about temporary blocks. Decoupling view filters from view filter logs will require a patch to MediaWiki, which is beyond the scope of this discussion and will need to be requested at Phabricator - I have no idea how likely it is to be actioned. Thryduulf (talk) 09:56, 20 August 2017 (UTC)
* While the idea is novel, yes, but community consensus would surely be against such an userright. Personally, I would never get across adminship/something similar to gain blocking (temporary or not) rights. Also, since non-admin SPI clerks are a handful in number, I do not think people would find it feasible to implement. IMO, giving write-access to EFH wouldn't be a major problem, since the level of trust, as you said, is similar; the only thing holding them back would probably be competency at regex (I myself am very much a rookie at it). -- QEDK ( 愛 • 海 ) 09:59, 20 August 2017 (UTC)
* Well, competency at regex isn't a problem. All you need to not fuck up with write access is competency to know not to touch the shiny buttons when you don't know what you're doing. We trust hundreds of completely non-technical admins with the ability to grant themselves write access and then use it because we trust they'll know not to. Note that write access is needed to write comments on the filters, which it sounds like this group should probably be able to do. ~ Rob 13 Talk 20:51, 20 August 2017 (UTC)
* The comments on the filters are for attribution of and explanations regarding changes to the filters or changes to the status of them (e.g. setting/unsetting the filter to disallow matching edits). Edit filter helps will not be making changes to the filters so they will have no need to write filter comments on them. They can of course discuss filters on this page/on the mailing list as appropriate. Thryduulf (talk) 00:38, 21 August 2017 (UTC)
* Oppose. The level of trust required for this should at least be at the same level of admin, so I don't see the point. If you need this, you might as well stand for admin. -- Tavix ( talk ) 04:29, 19 August 2017 (UTC)
* Why? It's not like any extended confirmed user will get this - they have to demonstrate a need for it and have no recent relevant blocks or sanctions - and remember that the edit filter manager right (which also gives write access, unlike this will) is also available to non-admins and has been for years without any problems that I'm aware of - indeed the only editor who has abused edit filters in recent years was an administrator (Kww). Thryduulf (talk) 07:45, 19 August 2017 (UTC)
* Oppose Great! The community has decided to cherry pick the admin tools. I don't care for the requirements because I'm definitely not putting my trust in non-admins. — JudeccaXIII (talk) 05:18, 19 August 2017 (UTC) (Move to "Support") — JudeccaXIII (talk) 19:44, 22 August 2017 (UTC)
* This has nothing to do with cherry picking the admin tools - firstly admins have write access to the edit filters, this will only grant read access. Secondly almost no admins actually do any work with edit filters (~15 of ). Thirdly, the edit filter manager right (which gives write access) has existed independently of the admin toolkit for years - this is just a subset of that. Thryduulf (talk) 07:45, 19 August 2017 (UTC)
* Thryduulf Question Once an editor is granted this right, I assume (s)he will be able to view the following information: Documentation#Variables. If so, will our actually names associated with our accounts be viewable along with our IPs from all devices we use? — JudeccaXIII (talk) 02:27, 21 August 2017 (UTC)
* The additional rights do not grant access to additional variables, it simply allows access to view filter configuration that is not hidden, and the logs associated with those filters, and to view the contents of the spamblacklist log. As far as the filters go, it is the same variables that are already used (example logs). — xaosflux Talk 03:44, 21 August 2017 (UTC)
* I don't fully understand your question, but the only people who can see the IP addresses used by logged-in users are checkusers and developers. The logs for hidden filters are identical in structure and information presented to the logs for public filters. Any filter may be set or unset as private at any time, and changing that status does not alter the content of the log at all. Thryduulf (talk) 09:30, 21 August 2017 (UTC)
* Support Callanecc (talk • contribs • logs) 11:08, 19 August 2017 (UTC)
* Support. I usually support any process that spread the rights amongst different classes of users, i consider the overall scenario more balanced in this case. And it allows a little bit of cursus honorum too. So, even if there will be some rearrangement in the future of flag architectures, it is good that this functions is not given only to sysops like other ones. In big and variegated community like enwiki it is possible to do it, there should be enough candidate to justify its creation. Maybe we can insert this request for flag in the same watchlists of the procedures of sysops if this gesture reassure or persuade some of the opponents. We could also restrict the flag to only specific classes of users (global patroller, sysops and patrollers on sister platforms, long term autopatrolled users...) for the same reason. In any case, IMHO the core idea is a good one.--Alexmar983 (talk) 12:51, 19 August 2017 (UTC)
* Support, since it looks like a great idea. Enterprisey (talk!) 14:13, 19 August 2017 (UTC)
* Support WP:PERM could be used, and bump up the requirement to 5K edits and 1 year. Not many LTAs get that far. L3X1 (distænt write) )evidence( 15:26, 19 August 2017 (UTC)
* Using WP:PERM was considered and rejected as this is a very specialised right that needs evaluation by people who are actively involved with edit filters, so the requests for the right come here. We want to make as difficult for hat collectors to get as we can, and not having it there will also make it lower profile which is a good thing. Thryduulf (talk) 16:42, 19 August 2017 (UTC)
* Support; and I may be interested in gaining these permissions. groig (talk) 23:05, 19 August 2017 (UTC)
* Support. It makes sense to me that there are users who would make good use of this tool. And I like the idea of granting selected admin-like permissions to non-admins (unbundling!). I've thought about the issue of the wrong users slipping through, and I'm a little bit reassured by the processes for removal of the right. Beyond that, I think it comes down to: don't be foolish about granting the right, and take the granting process seriously. --Tryptofish (talk) 00:14, 20 August 2017 (UTC)
* Oppose: I fail to see the necessity of this proposed user group. Javert2113 (talk) 04:10, 20 August 2017 (UTC)
* Support Creating more specific user rights is a good way of allowing work to be done by people who might not have the overall experience needed to use all admin tools. For example an admin will need to have engaged in Afd, making articles, anti-vandalism, mediation, helping newcomers etc. all while keeping a conflict free record. Whereas this user right could be given to someone who has a track record of dealing with evil minions/vandals/sockpuppets, but may never have engaged in Afd discussions or made many articles. A Guy into Books (talk) 08:49, 20 August 2017 (UTC)
* Oppose Simply not needed in my opinion.--Jasper Deng (talk) 22:24, 20 August 2017 (UTC)
* Why do you think it is not needed? There are quite a few usecases presented in this discussion and in the discussion that occurred prior to the RfC. Thryduulf (talk) 00:38, 21 August 2017 (UTC)
* The use cases can be all accomplished by assignment of the existing EFM right. If they can't be trusted to not abuse that right by modifying filters they aren't knowledgeable about, then they can't be trusted with the right in the first place.--Jasper Deng (talk) 01:12, 21 August 2017 (UTC)
* Oppose. If the user is trusted and experienced enough, give them admin rights. They still don't have to use all the admin rights if they don't want to. No need for a separate permission, anyway. Gestumblindi (talk) 11:06, 21 August 2017 (UTC)
* "Give them admin rights" is easier said than done. Only two people a month (on average) go through RfA. This proposal recognizes that fact and is a lightweight way to have some users, vetted and reviewed, granted the rights without the full RfA process. The proposal is also recognizing that for various reasons, we have more people willing to do some of the work currently restricted to admins, than are willing to go through RfA. ☆ Bri (talk) 18:17, 21 August 2017 (UTC)
PAGE''' ]]) 16:10, 29 August 2017 (UTC)
* Support - Smokin' 🐻 14:37, 21 August 2017 (UTC)
* Support. Will come in handy for SPI clerks and a lot of vandal fighters. R adi X ∞ 18:23, 21 August 2017 (UTC)
* To be abundantly clear, "a lot of vandal fighters" will not be getting access to this. That's actually the major reason I initially opposed. This isn't neo-rollback. It's a highly specialized user right that probably would be given to no more than 20 editors total, if even that. ~ Rob 13 Talk 16:03, 22 August 2017 (UTC)
* Support – I find it very useful to distinguish read access from write access: needs for each, and prerequisite skills are markedly different. — JFG talk 11:51, 22 August 2017 (UTC)
* Support - anything that helps make administrator status less of a big deal is always a good thing in my book. Twitbookspacetube 11:51, 22 August 2017 (UTC)
* Comment moved from the "Discussion" section by Thryduulf (talk) 12:00, 22 August 2017 (UTC)
* Support My main concern was privacy, but my question was answered. Though I still think there are enough user rights already, but if it helps, sure. — JudeccaXIII (talk) 19:44, 22 August 2017 (UTC)
* Reluctant Support. I see this very much as a way of granting a right while avoiding the RfA process, which is simultaneously good and bad. Obviously, RfA has a very high passing bar, and is almost impossible to pass for anyone without a stellar track record, 40 years of experience on WP, and 6 million page creations. The addition of this right to users that have not gone through the RfA process is a good thing, because it avoids that process, but creation of these usergroups for things that have traditionally been admin rights makes adminship even more of a big deal -- it is not. However, with the current state of RfA, I believe that we need to begin exploring alternate avenues to begin granting these rights... Because RfA doesn't look like it's going to change. Keira 1996 01:11, 23 August 2017 (UTC)
* Support but careful vetting would be required. jcc (tea and biscuits) 16:12, 23 August 2017 (UTC)
* Oppose, anyone who needs that right should be made an admin. —Kusma (t·c) 09:20, 25 August 2017 (UTC)
* Even people who have not contributed to a single discussion on en.wp but need this to assist with edit filters on another project? What about those people who are doing SPI work and have no interest or experience in closing XfDs or assessing consensus of discussions (required to stand a chance of passing RFA). It's also worth noting that the edit filter manager right, which is much more powerful than this one, has been available to non-admins for years without a problem. Thryduulf (talk) 11:24, 25 August 2017 (UTC)
* All of those people should be admins. It is sad that the sets of skills required to be an admin is so different from that currently optimal to pass RfA, but creating new user rights is the wrong direction in my (probably minority) opinion. —Kusma (t·c) 11:40, 25 August 2017 (UTC)
* I don't think I'm understanding you. Are you saying that people with zero edits on enwiki who do not know our policies but need to view our filters to be able to implement filters on sister projects should be made enwiki admins? This is a common thing that ends with existing edit filter managers emailing with those folks. It would be easier for them to view filters directly. That's the issue. ~ Rob 13 Talk 00:08, 26 August 2017 (UTC)
* I don't have a problem with zero-edit admins. Compare Requests for adminship/Lustiger seth. —Kusma (t·c) 20:48, 27 August 2017 (UTC)
* Support I came here from phab, after realizing that I needed the view-rights for suggesting changes to a private filter that's malfunctioning. Such a view-only option would be helpful. Lourdes 12:43, 25 August 2017 (UTC)
* Support - I haven't used edit filters much in SPI work but I certainly see how it's a valuable tool for certain long-term cases. I don't see any risk of damage from allowing more users access to this information. Ivanvector (Talk/Edits) 16:27, 25 August 2017 (UTC)
* Oppose The existence of this right will only invite EFMs to keep private filters that should be made public. Furrykiller (talk) 21:51, 28 August 2017 (UTC)
* --That's a pretty bad reason to oppose.Making certain edit-filters visible to everybody is practically impossible since it will, at large defeat their purpose(s).See WP:BEANS.Regards:) Winged Blades of Godric On leave 11:43, 29 August 2017 (UTC)
* Perhaps I was unclear. Filters that are narrowly targeted at LTA cases are and must remain private if they are to be any use at all. My comment was directed at a few low-risk, easily probed private filters that probably produce a lot of false positives (eg #34). This proposal is obviously going to pass, and I hope that when it does, the EFMs don't use it as an excuse to mark filters as private without a good reason. Furrykiller (talk) 12:10, 29 August 2017 (UTC)
* I don't think this is at all likely - after all they would have been doing it for years now if they were going to. Thryduulf (talk) 20:50, 30 August 2017 (UTC)
* Support - There is nothing wrong with giving certain editors this newer right to only view private, hidden edits, especially if editors meet the proposed (or amended) criteria and are trusted to acquire this right. Otherwise, an editor would not deserve this right. Simple as that... I hope. The opponents are opposing this proposal for various reasons neither sufficient nor convincing enough to change my mind about this proposal. BTW, I think publicizing filtered edits would bring more harm than good. --George Ho (talk) 23:11, 28 August 2017 (UTC)
* Comment: Tally so far is 48 support, 8 oppose ☆ Bri (talk) 04:40, 29 August 2017 (UTC)
* Support - Would come in handy for vandal fighters.SshibumXZ (talk) 10:46, 29 August 2017 (UTC)
* Oppose "Demonstrated need" is too vague and subject to creep. Change criteria 1 to "1. Currently-active highly-trusted user that would otherwise qualify for the EFM userright on the English Wikipedia", and, since this is aimed at SPI clerks, add criterion 5: "5. Currently-active SPI clerk or trainee clerk on the English Wikipedia". Then this proposal would have my full support. --Ahecht ([[User_talk:Ahecht|<span style="color:#FFF;background:#00f;display:inline-block;padding:1px 1px 0;vertical-align:-0.3em;line-height:1;font-size:50%;text-align:center;">'''TALK
* I lean slightly toward opposing since it looks like an unnecessary complication, but I do not fully understand it so I have no strong opinion. However, I do have questions.
* I've been an admin on Wikitravel & then Wikivoyage for about a decade & am an experienced abuse fighter back to the 1990s Usenet spam wars. On WP, though, I'm only an occasional contributor. Would I be eligible for this? If so, what use would it be to me?
* Is it possible this should be done on a cross-wiki basis rather than just WP? Pashley (talk) 20:41, 29 August 2017 (UTC)
* If you have no need for it, and don't see the use for it, then I would say that there's no reason for you to have the permissions. We do have editors who absolutely understand how viewing private filters and logs could help them in our anti-abuse efforts. There is a global group: Abuse filter helpers - obviously it's better to restrict things locally when there isn't a global need. -- zzuuzz (talk) 21:12, 29 August 2017 (UTC)
* Strong oppose Pointless. Without the ability to edit anything, this whole thing is useless. Also, I don't see a need. — Mr. Guye (talk) (contribs)  03:48, 30 August 2017 (UTC)
* Support - the ability to grant it should be restricted to Admins who are also EFMs. Cabayi (talk) 07:20, 30 August 2017 (UTC)
* Slightly pointless as any administrator is able to make themselves and edit filter manager at any time. If you mean that only those administrators who work with edit filters should grant it, then there is no technical method available to enforce that but that is one reason why the requests are to be handled on this page rather than WP:PERM. Thryduulf (talk) 20:50, 30 August 2017 (UTC)
* Strong oppose - If you want to be an edit filter helper than be an admin simple as that. – Davey 2010 Talk 20:37, 30 August 2017 (UTC)
* So do you believe that we should remove the edit filter manager right then, given that it is more powerful and available to non-administrators? Thryduulf (talk) 20:50, 30 August 2017 (UTC)
* Absolutely but that's just my personal opinion just the above is my personal opinion .... You can reply and essentially disagree with it but it wont change my mind. – Davey 2010 Talk 21:06, 30 August 2017 (UTC)
* Oppose unless very selective — On the upside, it would demonstrably be useful for the requests that have come, in the past, from other wikis wanting to copy filters, where someone's an admin "there" and by-federation likely trustworthy enough here to be temporarily granted EFM with the agreement it's read-only. Same goes for those who only requested EFM for read-only yet still demonstrated relative trust here. However, if this is put in action, it should be relatively-guarded rather than hat-collectible (e.g., there should be a good reason: demonstrated prior assistance with crafting/debugging public edit filters, being an SPI clerk, being an admin on another wiki, running an approved bot or bot approved for a trial, etc...). A few reasons for my caution: 1.) Edit filters have been extremely useful/game-changing when it comes to fighting both sockpuppetry and vandalism, in part because it's open-source to the trusted but closed-source to the stupid and idiotic (i.e., people who think disrupting a non-profit and wasting volunteer time is somehow good for anyone / socks). 2.) The vast majority of vandalism fighters don't actually need to see explicitly-private edit filters, lack the requisite technical knowledge to modify or contribute to them, and therefore don't clearly demonstrate a need for the extra tool, which isn't even an actionable extra tool otherwise. 3.) Private edit filters tend to be those that are most useful for monitoring severe, long-term sockpuppetry, particularly from the most dedicated sockpuppeteers—possibly even those who can appear to be vandal fighters just by huggling for a few weeks just to find out how they can evade. Forcing substantial, non-trivial contributions to the community seems a good-enough barrier, however; something that's done with EFMs. 4.) We already have a relatively open-door policy of "if you want details on the private filter, ask." 5.) People who actually do have the technical knowledge and/or one or all of the example prerequisites I mentioned can already get EFM. See the various requests over the years. It's not that difficult for someone to get EFM so long as they demonstrate a moderate level of trust and technical capability, which would logically be required for this right to be enabling for a would-be helper in the first place. -- slakr \ talk / 03:04, 1 September 2017 (UTC)
* Pretty much every one of your reasons for caution have been designed into the process - particularly making it difficult for hat collectors, and yes it will be very selective - you only get it if you have a demonstrated need to have it (rather than only refusing if there is a reason to refuse, as some other rights). The reason this is required as well as EFM is that several people who have been given EFM didn't need/want full write access and others who were given EFM when they wouldn't have been if this right were available. Anyone can ask for details of a private filter, but that does not mean the details are given out in public or even given at all in many cases. Thryduulf (talk) 08:39, 1 September 2017 (UTC)
Discussion regarding edit filter helper
* The following people commented in the discussion leading to this RfC: . Thryduulf (talk) 14:24, 14 August 2017 (UTC)
Contrast to the admin right
Edit filter helpers would need to be highly trusted. You need to be highly trusted to be an admin. Admins can see the private edit filter.
What is the need to create this separate right? Is the theory that RfA is too onerous? Do we see there being many people who would get the edit filter helper right who would not make it through a request for adminship?
Yaris678 (talk) 16:58, 18 August 2017 (UTC)
* , while it's true that only 15 of the |167 EFMs are not admins, I would argue that their contributions are just as valuable as those of the admins. Some people simply don't want to be admins, and it's not for us to judge whether they should be forced to go into administration simply to get EFM. Plus, I'll note that only 150 admins actually use EFM, demonstrating that even with the bit there aren't that many who have an interest. Why look a gift horse in the mouth? If someone wants to help out, let them. Primefac (talk) 17:23, 18 August 2017 (UTC)
* Actually, it is for us to "judge whether they should be forced to go into administration simply to get EFM." That's what this RfC is about. The community sets policy and access rights, so it really is for us to judge. ··· 日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan ! 17:39, 18 August 2017 (UTC)
* , you make a very good point. I meant more in an "as of this point in time" metric, though given the nearly unanimous support for the above proposal, it looks like it would go that way in the future as well. I meant more in the fact that we should not make EFM only accessible to admins because that would be like shooting ourselves in the foot.
* The EFH right was proposed based on a case a few months ago where I requested the right for a user because she was demonstrating a definite need to view the edit filters, but was not comfortable with actually editing them. Her gaining the right came with an "unofficial tban" towards actually editing the filters, which made a few of us realize that trusted users could/should still be able to view them if necessary. Primefac (talk) 17:47, 18 August 2017 (UTC)
Concerns about ease of access to the right
and others concerned about it being easy for sockmasters or vandals to get access, it's probably worth noting that the biggest hurdle for getting access to this is the "demonstrated need for access" criterion. The significant majority of people who will benefit from this right will be non-admin SPI clerks, which is a position that requires significant effort to get, it would surprise me if there were more than 2-3 other editors a year who meet the criteria, and some of them will get it by virtue of being an admin on another project - something a sockmaster or vandal is extremely unlikely to be. See Edit filter noticeboard/Archive 2 for where a sockmaster (I love bridges) attempted to get access to private filters but failed. New users requesting this rather specialised and almost certainly quite obscure right will be quite a big flag that there might be something to investigate. Thryduulf (talk) 07:59, 19 August 2017 (UTC) PAGE''' ]]) 17:36, 29 August 2017 (UTC)
* let's try spelling your names correctly this time. Thryduulf (talk) 08:00, 19 August 2017 (UTC)
* What is "demonstrated need"? Is doing counter-vandalism related to sockpuppetry "demonstrated need"? I would assume yes, or I would at least assume other admins would say yes at PERM on occasion. As for your assertion that sockpuppets don't get the bit on other wikis, that is ill-timed, since this literally happened last week. See, who got sysop on Commons with a sock and then went on a spree of vandalism. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 16:05, 19 August 2017 (UTC)
* Concerns about abuse of the right and infiltration of privileged toolsets are completely legitimate. (I have also seen evidence that bad actors have tried to infiltrate OTRS.) However it seems a bit circular to say we only trust admins with the tools, but simultaneously say we don't think they are able to determine who is trustworthy enough to receive permissions to use the tools. At some point don't we have to take action with expansion of access, or else remain paralyzed by fear of abuse? ☆ Bri (talk) 16:24, 19 August 2017 (UTC)
* See also my reply above, but WP:PERM is irrelevant as the right is requested and granted here not there, and it can only be granted when there is consensus to do so. Simply doing counter vandalism work is not a demonstrated need as very few people doing counter vandalism work actually do need to have any involvements with the details of the private filters. Even syspos on other wikis still need to have a demonstrated need for access here and any blocks or sanctions on another wiki will be looked at. Thryduulf (talk) 16:37, 19 August 2017 (UTC)
* I agree the requirement of extended confirmed is a bit low. I can think of a handful of users who I would grant this to right now, and they all have tens of thousands of edits and have been around for quite some time. Indeed the position of being an SPI clerk is not easy to attain, and the only other relevant position (aside from non-enwiki admins) is someone who has long been working toward tracking LTAs, like . Another thing to consider is trusted users who regularly request new filters and amendments at WP:EF/R, targeted towards specific socks. Some of these people I communicate via email since they can't see the logs, so obviously a read-only right would help them. It's all on a case by case basis, and the people here who work on edit filters I think can be trusted to make the right call. Each and every request for this right involves a discussion, after all, not the judgement of a single admin as is the case at WP:PERM. That being said it wouldn't hurt to be more explicit in the granting guideline and raise the bar a bit — MusikAnimal talk 17:17, 19 August 2017 (UTC)
* I'm all for just granting edit filter manager to the non-admins who are regularly requesting new filters/amendments at WP:EF/R and have passed a high threshold of trust. Read-only doesn't help them as much as learning how to actually change filters. If I trust them to read a filter, I trust them to write one. I'm very worried that we're setting a hard threshold too low and this will lead to "well, it's just read access" arguments when a good-faith user seems to vaguely need the right (but not urgently). ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 18:12, 19 August 2017 (UTC)
* Not everybody needs or wants write access - not everybody is comfortable with making the changes (especially as even a minor typo can have very significant consequences), and not everybody has the technical skills required to adjust filters but does understand enough to review logs, and get the gist of the regex (for example, me). It's also a good learning tool and a way for people who want edit filter manager to demonstrate competence before being granted write access. Thryduulf (talk) 18:34, 19 August 2017 (UTC)
* Good points. The bar for write permissions however is super high, much higher than what I would expect for read-only, as it should be. If I see a regular at WP:EF/R is competent at regex and is trusted, I would recommend them ask for write access. This is exactly what happened with, who didn't even want write-access but I sort of pushed them into it as I saw they were perfectly capable :) Meanwhile, others at EF/R are more saying the "sock is now doing this so the filter should do this" in plain English, and may have no conception of technical details. These are the people who would benefit from the logs, because currently all they can tell me is "this edit got through", and have no idea if the sock is active, likewise for SPI clerks and LTA trackers who don't work at EF/R. As the filter author, I monitor to make sure there are no obvious false positives, but sometimes I have to defer to the requester via email. These use cases admittedly don't happen often, but if I know I trust someone, and I know they have no desire to edit filters, why not? Obtaining write access for them wouldn't be easy. Read-only I don't think is near admin-level at all. Admins can cause significant damage, this read-only right by itself can cause zero. It's for trusted users who would clearly benefit from it, that simple. I think we have an excellent edit filter management team, and no one is going to hand out the read-only right without sufficient scrutiny — MusikAnimal talk 22:24, 19 August 2017 (UTC)
* Random thoughts on the above: As with any permission, there's never a requirement to grant it, so a new, suspicious, out of nowhere helper suddenly appearing and requesting doesn't bind anyone's hands. I personally might be a bit more judicious with granting to someone who doesn't know regex but knows what they want the filter to do... the logs will tell you if a filter was hit, but they won't tell you why it *wasn't* hit, so you need to be able to sort through the code to make useful suggested corrections. (There's still a few non-hits that I can't figure out why they didn't trip). I agree with {u|BU Rob13}} that we mustn't set the bar too low, and I think that's where the judgement for "demonstrated need" is crucial. Editorial or technical curiosity (even in good faith), or requests focused around one sock or disruption to one article, should not be considered meeting that need, as the requests page is quite viable for that. I suspect that it will become one of those scenarios where you "just know" if a requester is right or wrong for the permission. Crow Caw 17:03, 22 August 2017 (UTC)
* Yes, and there is a fairly large set of long-term, trustworthy editors who don't want to be admins as I've alluded to above. Some of them have even been collated and vetted as part of an organized admin recruiting effort. ☆ Bri (talk) 17:56, 22 August 2017 (UTC)
* If the intent is to have this permission for admins/filter managers on other wikis, SPI clerks and trainee clerks, and people who would qualify for EFM but don't want the ability to edit, why not just limit it to those groups instead of using the vague "demonstrated need"? --Ahecht ([[User_talk:Ahecht|<span style="color:#FFF;background:#00f;display:inline-block;padding:1px 1px 0;vertical-align:-0.3em;line-height:1;font-size:50%;text-align:center;">'''TALK
* because that is not the intent. The intent is to restrict it to those who have a need, which includes some (but not all) SPI clerks and admins/edit filter managers on other wikis, but is not limited to them - for example Lourdes would benefit from this right to assist with identifying and debugging a (probably MediaWiki) problem that is affecting at leas one filter (see ). In other words not all SPI clerks etc have a need and not everyone with a need is an SPI clerk/admin on another wiki, etc. Thryduulf (talk) 20:58, 30 August 2017 (UTC)
* Vandals and sockmasters can get around filters through trial and error, which would be much easier to do than making an account, becoming an established editor, becoming active in some area of the project that requires filter viewing, and then requesting this permission. I can understand opposing this because we already have a user group - edit filter managers - that can give people view access, with years of it not being abused to work with. But opposing the new group because a troll could use it to view private filters and save themselves a couple minutes figuring out how to bypass the filter manually, after spending months trying to collect the various prerequisites? Truly ridiculous. -- Ajraddatz (talk) 19:15, 22 August 2017 (UTC)
* I'll also add that the sysop unbundling comments don't make sense here either. If anything, complain about EFM unbundling, and tell any candidates to request the full editing rights instead. -- Ajraddatz (talk) 23:57, 25 August 2017 (UTC)
Concern about "at least a basic understanding" of account security
This needs to be more than just a single sentence. There is a reason why WP:PAGEMOVER, WP:TPE and WP:EF are sections instead of semtences. Anybody with this edit helper privilege should also fully understand and follow personal security practices, have a strong password, and everything else listed on WP:SECURITY. It has been mentioned in the concerns about ease of access discussion, but I'll basically repeat it: a vandal or sockpuppet with this would be able to view the private edit filters designed to combat vandalism. Therefore, a compromised account would also have to be blocked and its privileges removed on grounds of site security. Zzyzx11 (talk) 02:04, 25 August 2017 (UTC)
* I feel this is fully answered elsewhere, but if there is any concern that someone's account security practices are too weak then they wont get the right. This was also brought up in the discussion which came before this RfC, which I encourage you to read. There are far easier, and thus far more likely, ways for a vandal to bypass filters. Thryduulf (talk) 11:31, 25 August 2017 (UTC)
* perhaps 2FA should be extended to include this new group? Cabayi (talk) 11:36, 25 August 2017 (UTC)
* This was discussed at . Given the conclusion there that this is not a necessity and the number of people who have already commented in this RfC it will probably better to propose the extension of it to this group separately after the right is created (assuming the RFC is closed as supporting the proposal). I don't know where the best place to make such a proposal would be though. Thryduulf (talk) 11:48, 25 August 2017 (UTC)
* You can turn on 2FA now, without being an admin, by asking on meta. I know because I did it this week. ☆ Bri (talk) 03:16, 26 August 2017 (UTC)
Name
"Edit filter helper" isn't really accurate or descriptive. These people aren't really helping the edit filter managers create filters; if they were, we'd just give them edit filter manager. Can we call this "edit filter viewer" instead? this is far more descriptive and clearly accurate. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 04:15, 5 September 2017 (UTC)
* The name is a bit of a historical oddity. The global group was originally created specifically so people could help design filters globally, while being granted only view access so they had to work with the local admins and abusefilter managers. I have no objection to the local group being called viewers instead, and the global group should probably be changed at some point given its expanded scope now. -- Ajraddatz (talk) 05:20, 5 September 2017 (UTC)
* And note, the proposed local, just like the global, includes spamblacklist viewing as well - I suppose that is still a form of a "filter" but its not from the abusefilter system. Let's make sure to not get hung up on this, we can always localize the name. — xaosflux Talk 12:00, 5 September 2017 (UTC)
* I'm not bothered about the name - I came to this after someone else had originally proposed it and just ran with what they were calling it. If we can change the name locally after the right is created (I don't know) then that's probably the simplest way to go about it, but using the same name as the global group seems like it has less potential to cause confusion when the request is made to the devs on phabricator. Thryduulf (talk) 23:18, 8 September 2017 (UTC)
Publicity of filter 879, filter also affecting accounts
Two things I want to say about this filter:
* 1) Should this filter be private? It seems like it's targeting possible broken proxies, and the "Possible open proxy" filter (464) is private.
* 2) I feel like this filter, since it's titled "Possible broken proxy", shouldn't be affecting accounts. Should it be limited to just IPs (replacing with )?
— MRD 2014 Talk • Edits • Help! 23:40, 12 September 2017 (UTC)
* I think there's no reason for 879 to be private. Malforming edits with a broken proxy is fairly unavoidable - you are either using an IP which breaks articles, or one which doesn't. As far as I can tell there's no one deliberately making these edits, and if someone was trying to avoid the filter that would actually be a good thing. I've been thinking about 464, and am leaning towards thinking it should be also public for the same reasons, but I will add that it is slightly different in that it is more likely to be triggered by some long term abuse cases. My preferred option is to eventually merge the filters and use a custom warning for both. As for edits made by accounts, they are affected exactly the same as the IP addresses they are using, but there is some allowance made for the fact that established users are less likely to make these edits. -- zzuuzz (talk) 04:47, 13 September 2017 (UTC)
* I see. The word "proxy" in the description confused me. — MRD 2014 Talk • Edits • Help! 12:54, 13 September 2017 (UTC)
Move Special:AbuseFilter/879 to disallow, or tag?
I don't actually understand why this is happening, but it looks like none are good edits. — MusikAnimal talk 17:34, 14 September 2017 (UTC)
* Just now noticing your comment above. What confuses me is the tripped edits don't seem to make any change beyond HTML-encoding those characters, and they're always from the mobile interface. I'll admit I am also confused as to what "proxy" means in this case. Also, I lied, there is a false positive here :( We might could use rcount to make sure the before/after are the same — MusikAnimal talk 18:01, 14 September 2017 (UTC)
* I'll be honest I don't know exactly what's happening, but I do know we needed to be at least logging it. It did occur to me that it might be a Wikipedia bug, and nearly got around to asking you if CU could help fill in some of the details with the user agent. This doesn't look like deliberate changes - it could be that other changes are being discarded, but here's two interesting edits (possible vandalism or possible browser bug?). There are two distinct mobile networks which repeatedly appear and I don't think that is a coincidence: roughly 197.156/15 and 42.110/15 and I'm sure I've also seen non-mobile interface edits, but that one's probably still on a mobile, per whois. Mobile networks are far more likely to be doing caching or something, but it could be being broken even before that. It's the type of behaviour I expect from a bad PHP proxy. I'm not sure where to head next with the filter - it still looks a bit to liable for me, and I think we'll need in particular to figure out encoding in URLs. Maybe a warning? -- zzuuzz (talk) 18:47, 14 September 2017 (UTC)
* There is a consistency with the UA come to find out... A browser bug sounds more likely, from what I can tell — MusikAnimal talk 19:44, 14 September 2017 (UTC)
* Thanks, that sounds about right. Perhaps I should rename the filter. So I think tagging would be pointless, and disallowing would be a bit harsh at this stage, but that warning should be able to filter out any accidental edits and we'll see what happens? -- zzuuzz (talk) 20:11, 14 September 2017 (UTC)
* I've renamed the filter and set it to warn for the time being, and we'll see what happens eh. -- zzuuzz (talk) 06:30, 16 September 2017 (UTC)
We built some graphs to monitor Edit filter performance
Hello everyone! As part of our research into improving Edit filter the WMF's Anti-Harassment Tools team has implemented performance tracking to monitor how fast (or slow) the feature is operating. The graphs can be found at https://grafana.wikimedia.org/dashboard/db/mediawiki-abusefilter-profiling. The graph on the left shows the 75th and 99th percentile of runtime, and the other shows the total filters and total conditions run.
Over the next week we'll be adding in some additional reporting for sub-optimal filters. This work can be tracked on Phabricator at T174205.
We're hoping to use this new measuring to make some decisions on how we can make AbuseFilter more performant or if we can raise the condition limit. — Trevor Bolliger, WMF Product Manager 🗨 23:46, 14 September 2017 (UTC)
* Looks good, especially the conditions/limits one! — xaosflux Talk 12:03, 16 September 2017 (UTC)
Edit filter helper - implementation
Following the closure of the RfC above with consensus in favour of creating the right, I have: Things that should be considered while we are waiting: If anyone has strong feelings about either of these (I don't) then I don't see a reason not to be bold. Thryduulf (talk) 13:19, 12 September 2017 (UTC)
* Updated the header of WP:EFH from "proposed" to "pending" and added the tag
* Ideally it should have an "information page" tag at the top and "procedural policy" tag in the relevant section, but the information page tags explicitly say they are not policies or guidelines. If anyone knows how to represent this better, please change it.
* Created a request on Phabricator for the group conferring the rights to be created - see T175684.
* Should Wikipedia talk:Edit filter helper be it's own page or redirect to this noticeboard or redirect to Wikipedia talk:Edit filter (like this noticeboard's talk page does)?
* Should Edit filter helper be included on any navigation templates and/or have any navigation templates transcluded on it?
* I think the talk page should be directed to WT:EF. Instead of being a standalone page, the content could be added under the edit filter managers section of WP:EF. -- Ajraddatz (talk) 17:11, 12 September 2017 (UTC)
* This has gone live, has been tested and is working, including the new non-admin SBL viewing. Localized labels / page directs can be updated as needed. — xaosflux Talk 21:53, 18 September 2017 (UTC)
Filter 98 and ACTRIAL
The autoconfirmed article creation trial has begun. Filter 98 (Creating very short new article) only triggers when a non-autoconfirmed user creates an article less than 150 bytes in size. Now that ACTRIAL has begun, all articles will be created by autoconfirmed users and this filter will not trigger for the duration of the trial (trial ends March 2018). — MRD 2014 Talk • Edits • Help! 01:34, 15 September 2017 (UTC)
* There are a bunch of similar filters. Should we just disable them all, or maybe change them to target non-extended confirmed users? Or users with less than say, 50 edits? — MusikAnimal talk 04:03, 15 September 2017 (UTC)
* See for a phabricator task about a related issue with the page curation filters. We're keeping the old AC filter for now and simply adding the "learner" filter additionally there. I think in this case it would make sense to simply up the definition of new user to be non-extended confirmed. TonyBallioni (talk) 05:52, 15 September 2017 (UTC)
* I've updated 98 to target extended confirmed. The only other filter I could find directly affected by ACTRIAL was Page creation throttle for new users. This one actually disallows if they attempt to create more than 2 pages in a 90-second period. My guess is we don't want this for non-extended confirmed users, as there would seemingly be some legitimate use cases? Maybe target users with less than say, 20 edits? — MusikAnimal talk 03:35, 19 September 2017 (UTC)
Edit filter helper for DatBot
* Ends at: 14:25, 21 September 2017 (UTC)
* Ends at: 14:25, 21 September 2017 (UTC)
* Ends at: 14:25, 21 September 2017 (UTC)
(I believe this is how a request was meant to be. PS to do the 'ends at' thing use +7 days
I'd like to get this flag for my bot so it could use the API to report users. Currently, the bot has to use the database, which frequently lags, thus producing stale reports.
* — Preceding unsigned comment added by DatGuy (talk • contribs)
* This access group doesn't give any access to "report users" - do you mean to "report on" users? Can you provide a link to your existing BRFA? — xaosflux Talk 21:55, 18 September 2017 (UTC)
* Sure, here it is. This is the part of the code that isn't very effective: "SELECT SQL_NO_CACHE afl_id, afl_action, afl_namespace, afl_title, afl_user_text, afl_timestamp, afl_filter FROM abuse_filter_log". It basically tries to get into about the attempted edit. If the bot had access to the API, I wouldn't have to force it to use the SQL database, which has replication lag. Dat GuyTalkContribs 22:00, 18 September 2017 (UTC)
* I'm fine with the bot access from a technical level. — xaosflux Talk 22:08, 18 September 2017 (UTC)
* Note from a practical level, does not have this access today so this request should focus on if he qualifies himself. — xaosflux Talk 22:08, 18 September 2017 (UTC)
* I have zero problem with both DatGuy and DatBot getting EFH. Would actually help some aspects of the bot's performance significantly. Ks0stm (T•C•G•E) 22:11, 18 September 2017 (UTC)
* Gets my support, as essential to get over this rather problematic technical limitation. No issues with DatGuy either. -- zzuuzz (talk) 05:21, 19 September 2017 (UTC)
* Do you want the flag for yourself as well (e.g. would that help with debugging?) or just for your bot? I have no issue with either but it's best to be clear. Thryduulf (talk) 09:26, 19 September 2017 (UTC)
* I originally wanted only my bot to have it, but I believe is saying that I should be an EFH for my bot to be one? Unless I misinterpreted it. Dat GuyTalkContribs 09:41, 19 September 2017 (UTC)
* That is completely up to you, my point is that as you have control of the bot credential you will effectively have the access anyway and as bots are extensions of their operators the general review of meeting criteria should be of the operator (for operators that don't already have access). — xaosflux Talk 11:28, 19 September 2017 (UTC)
* Support both EFH for and as I believe bot operators of EFH-bots should themselves have the flag, if only to demonstrate trustworthiness of the operator, as opposed to the implied trustworthiness of the bot -- There'sNoTime (to explain) 11:16, 19 September 2017 (UTC)
Filter 869 - "Users adding tabloid journalism to BLPs" - move from "log" to "disallow"
This filter traps web citations to The Sun, the Daily Mail and the Daily Star on any BLPs. It's been logging for the past couple of weeks, and I think it's time we turned it on to "disallow". There are a couple of diffs I want to query - for example, this diff by which is actually talking about the Daily Mail might be argued as a false positive, though I would say per WP:BLPSOURCES that if the information is that noteworthy, the broadsheets would have picked it up. (eg: See Enemies of the People which is entirely about a Daily Mail headline without containing a single source to it). As an alternative, we could set it to disallow on just the Sun and the Daily Star, which seem to be far less contentious than the Mail, which seems to trip up the lion's share of the filter logs. Your thoughts, please. <b style="color:#7F007F">Ritchie333</b> <sup style="color:#7F007F">(talk) <sup style="color:#7F007F">(cont) 15:55, 21 September 2017 (UTC)
* I'd say disallow is far more problematic than warning, and it doesn't get my support. Plus, the RfC was very narrow and doesn't support a total ban on the other tabloids. -- zzuuzz (talk) 17:10, 21 September 2017 (UTC)
* The RFC also noted that there were situations where the Mail could be cited (e.g. in articles where it is the subject, and in older stories from before it went downhill quality wise). I don't support disallow. Thryduulf (talk) 00:39, 22 September 2017 (UTC)
* I think changing it to warn might be a better option than to disallow. — MRD 2014 Talk • Edits • Help! 12:19, 22 September 2017 (UTC)
* I'd prefer disallow, but I'd go with warn as well. At least any editor adding the material cannot then complain when it is reverted, as they've already been warned not to add it. Black Kite (talk) 12:31, 22 September 2017 (UTC)
* Such links shouldn't be added in most circumstances, but there are exceptions so if it does go to warn (which I'm happy with) the wording should reflect that. Thryduulf (talk) 23:48, 22 September 2017 (UTC)
As Ritchie mentions, I added a citation from the Daily Mail in this instance as part of a sentence openly discussing that very Daily Mail article itself (which is discussed by other Reliable Sources). I'll bow to whatever the general consensus is on this one, but I personally don't think that there are any problems in having the citation in this particular instance. Midnightblueowl (talk) 19:27, 22 September 2017 (UTC)
* A potential issue with any disallow on such things is a WP:ABOUTSELF and WP:PRIMARY conflict, especially when the site is a news source (even if a low-quality one). They remain legit sources for direct quotations, even if they're worthless as secondary sources for WP:AEIS material. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 17:57, 23 September 2017 (UTC)
Special:AbuseFilter/261 and WP:ACTRIAL
I asked about this above and got no reply. Since this filter currently doesn't do anything, I've disabled it. I think it might be useful to have it check for an edit count less than say, 50, but I'm not sure about the disallow action — MusikAnimal talk 20:03, 27 September 2017 (UTC)
an invitation to Edit filter managers
Hi,
This is an invitation to Edit filter managers and patrollers who refer to edit filters from your wiki project to share and know about effective public filters from various wikimedia wiki projects.
It is almost eight years since March 2009, that Edit filters are in use on various Wikimedia wiki projects. At meta we have started a platform page m:Edit filters benefiting to various local Wikiprojects to know good and effective (public) edit filters by sharing of relevant information with rest of wikimedia community. This will help editfilter managers, and there by concerned projects, to benefit from maximising potential of best possible (public) edit filters.
We are keen to have your participation in this collaborative and constructive endeavour and the discussions.
Mahitgar (talk) 11:09, 30 September 2017 (UTC)
EFH bit request
Requesting EFH bit to view hidden logs. I do a lot of work at COIN leading discussions about conflicts of interest. I expect this right would help me discover relevant COI/UPE cases as well as general vandalism etc. I understand the BEANS need for discretion. If it matters I have academic training in regexp and have demonstrated their use here. ☆ Bri (talk) 16:03, 27 September 2017 (UTC)
* Support have discussed sensitive information with Bri before; they're trustworthy, a long-term contributor, competent and show a need for the right -- There'sNoTime (to explain) 17:00, 27 September 2017 (UTC)
* ✅ — xaosflux Talk 01:51, 1 October 2017 (UTC)
EFH bit request for Mahitgar
Requesting EFH bit to view hidden logs. My interest is more of academic nature to study and help improve m:Edit filters benefiting to various local Wikiprojects this meta page started by me. It will also help in giving references to my bugs filed at phab.
I am not technical expert on regex but have learned, compared and implemented techniques from en:wp and other lang wps past four-five years public filters here. While I have tried inter acting on en wp ef forums, frankly many times may be due to lack of man power, its slow in responding. Over the years I have been supporting mainly help pages on my local lang wiki. I suppose my participation may help, help pages and and once in a while in en wp ef related support/ help activities.
Whatever you decide but please keep supporting. m:Edit filters benefiting to various local Wikiprojects
Thanks and regards
Mahitgar (talk) 08:19, 1 October 2017 (UTC)
* Oppose I'm not sure how viewing the hidden logs will help with the page you've set up. Almost all private filters pertain to specific vandals here on English Wikipedia. They likely will not be of as much use elsewhere, and moreover they should not be published on any public page like the one you speak of.I would also recommend renaming your page to something like "Edit filters of cross-wiki interest". The term "Wikiproject" can be confused with WikiProject, which is different than a project like enwiki, frwiki, etc., also known simply as a wiki. Other wikis also use the term "WikiProject" to refer to their own internal, specialized collaboration groups. — MusikAnimal talk 14:32, 2 October 2017 (UTC)
* Oppose per MA. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 15:23, 2 October 2017 (UTC)
* Oppose per above concerns. I'd like to see a bit more local activity before this was handed out, as was decided in the perm's RfC -- There'sNoTime (to explain) 15:37, 2 October 2017 (UTC)
* Strong Oppose--I want to see much more local activities related to specific usage of EFs before granting the right. Winged Blades of Godric On leave 16:18, 2 October 2017 (UTC)
* Comment: Thanks, As per MA's good suggession I will go for change of page name. In most cases specific words which want to get filtered are confidential and not all technical configurations. If not all atleast few stable configurations are shared (sans confidential part/wors) on common meta page all wikis will benefit from experience and help improve efficiancy to all of us.
* As I said my interest in EFH bit is limited only and not granting as of now is not an issue to me. Just I wanted to bring a common page into focus, and that has been achieved by this discussion. Thanks for considerations. It is ok to close the discussion as EFH bit not accepted.
* Mahitgar (talk) 05:00, 3 October 2017 (UTC)
Request for edit filter manager bit
Ends at: 17:41, 30 September 2017 (UTC)
Professional coder and sysadmin, been here 10 years, 100K+ edits. TemplateEditor (I'm one of the more active non-admins who answers requests, and often go out of my way to implement and sandbox what's requested if the requester doesn't have the skills to do the testing personally). I do not presently run any bots.
Would like to create some informational/tracking edit filters (frequently misused templates, Web sources that are questionably reliable, and a few other cases), for editors to use as cleanup/verification tools. I have no interest in making filters that trigger actions like preventing the edit or delivering a warning (that seems more like an admin-level role to me). — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 17:22, 23 September 2017 (UTC) I was avoiding on purpose, because the docs say regexes are expensive for edit filters; the implication appeared to be that will match literal strings not regexes. That keyword is essentially undocumented, but the says it works with strings. I noted that filter 126 didn't escape the in youtube.com. It wasn't clear that the pipe wouldn't work without or. The pipe is used as an OR more generally in the syntax in other ways, so it didn't seem confined to regex parsing. I had my doubts about, and suspected might be required. Anyway, I'm not sure if it's better to just use, or try to catch case variations another way. That's a "what we've learned about filter efficiency" question for you all. :-) On parens, yes, the intent was (Namespace == 0 AND (link1 OR link2)); methinks this is the fix. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 21:18, 29 September 2017 (UTC)
* Just a comment, EFH cannot create filters, only view the logs of hidden ones. Crow Caw 17:33, 23 September 2017 (UTC)
* It sounds like you'll want to be asking for the edit filter manager bit instead. If that's the case could you first of all mention any experience with edit filters and perhaps regex. I've got to also say one thing we're constantly battling against is an explosion in the number of filters and associated runtime, so an application expressing an interest in creating lots of tracking filters, which in my experience not many people consistently look at, may not seem an obvious way to go. But could you give an example of such a filter, including perhaps its expression? -- zzuuzz (talk) 17:35, 23 September 2017 (UTC)
* Ah, I see, yes I mean the bit for editing them, then (I don't actually care about hidden ones. :-). Changed the heading. Don't want to create lots, and I'd be perfectly happy adding to some rather than adding new ones. As a sysadmin, I work with regex in multiple flavors all the time. Am versed in sandboxing, and of course read WP:Edit filter and its material on not implementing a filter that actually does anything without first observing that it triggers exactly as expected. I've not directly worked on the edit filters here, lacking the bit to do so. Just think I can be of use; I'm one of the more tech-oriented sorts who's active most of the time. PS: I have a long reputation as an outright nay-sayer when it comes to poorly-thought-out changes to important templates, WP:P&G material, interface pages, processes, and other things that could have wide-ranging side effects; I think that's a plus in this context. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 17:41, 23 September 2017 (UTC)
* Thank you for answering most of the question. You know people here can be quite fussy so I'm just trying to elicit the relevant things. We can't expect anyone to know everything, but I'm sensing an element of unfamiliarity with the topic. You're welcome to persuade me otherwise. Personally I don't particularly doubt your technical abilities - what you consider a plus I consider a lack of negatives - but what I'd really like to hear about is what you intend to do. Have you considered having a go at WP:EFR or EFFP? -- zzuuzz (talk) 18:05, 23 September 2017 (UTC)
* I had not looked into EFR or EFFP; can do so. I'm more volunteering to assist than coming in with an agenda. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 12:45, 24 September 2017 (UTC)
* What I intend to do is draft and test some low-key edit filters mostly related to questionable sourcing, and to help fulfill requests for new EFs that are requested and not rejected (i.e. perform TemplateEditor-like work, just also with regard to EFs). — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 14:30, 24 September 2017 (UTC)
* Q: Can you give an example of a filter you might create and how you would code it? Crow Caw 18:03, 23 September 2017 (UTC)
* Two examples that come to mind are citations to QuickAndDirtyTips.com/grammar-girl and MessyBeast.com. Both of these are personal blogs by people with some credentials in a tangentially related field, but not expertise in the one central to what they're writing about (the author of the "Grammar Girl" material at the first is not a linguist but a journalism professor (i.e., steeped in one very particular form of writing, which has numerous norms that conflict sharply with other writing styles and registers of English), and the author of the latter is not a zoologist (or veterinarian, ethologist, etc., much less a felinologist). The sites have huge followings, and are frequently cited on the web as "authorities", but do not make their own sourcing clear, and are mostly advice columns (primary source material) and collections of factoids from other places (tertiary material). They can be legitimately cited here as primary sources for certain things when this is done properly, but more often people try to cite them as secondary. We have very few watchers on the sorts of pages where citations to these websites are most likely to appear. Haven't had coffee yet (it's 5:40-something a.m. where I am), but I can produce a sample filter later. I'll look first into the EFR and EFFP recommendation above. I'm not here to collect some headwear but to be of use. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 12:45, 24 September 2017 (UTC) PS: Looking at the QuickAndDirtyTips.com site again for the first time in ages, I note that it's ballooned to way more than the Grammar Girl material and how has multiple columnists writing on fitness, business, psychology, etc., making it more likely to be used as an probably-bad source on more pages, like the old About.com. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 14:30, 24 September 2017 (UTC)
* Sample filter at User:SMcCandlish/Editfilters. Demo of a potential filter for various questionable but not sites, and some notes on possible efficiency improvements I can't really test directly. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 14:30, 24 September 2017 (UTC)
* Looks good for a tag-only, though as you implied there's some tuning to streamline it (such as one keyword that will catch all case variations). You may want to read, there's some serious power in this tool. :-) Crow Caw 17:12, 24 September 2017 (UTC)
* Just on the technicalities of the filter - and I won't particularly hold this against SMcCandlish as he doesn't have proper access to the filter testing tools - it seems to be confusing plain text searches (<tt>contains</tt> | <tt>contains_any</tt>), with regex (which uses the pipe (|) character). Compare the use of <tt>irlike</tt> in 657 which is referenced with perhaps 31. It also seems to be lacking enough parentheses, and is testing for (Namespace == 0 AND link1 OR link2). Compare 869 and see the archive. -- zzuuzz (talk) 18:35, 24 September 2017 (UTC)
* Additionally you didn't escape the . in the URL, which is needed since it is a valid regex character. I'll note this involves an understanding of regex in general, not a familiarity of the extension, though you might have discovered your mistake using the debugging tools — MusikAnimal talk 14:50, 27 September 2017 (UTC)
* Lack of testing tools (and more detailed documentation – though I'll go check out that mediawiki.org page) is a bit of a hamper. Deets:
* Q: I know it's been a while (7 years), but your last RfA had a lot of opposition. Do you think you have overcome the issues that led to that opposition, if so how? — xaosflux Talk 23:12, 23 September 2017 (UTC)
* Oh, geeze that's from an embarrassing time. At my first RFA I was an enthusiastic noob, and at the second I'd been taking excessively bureaucratic and argumentative stances that were more about trying to make WP operate the way I thought it should rather than vice versa. I've done a 180 on that stuff. These days I'm a huge fan of the WP:POLICY / WP:LAWYER principle that WP's rules and processes are to be interpreted in the spirit in which they're intended not their exact letter, and that they're here to serve our needs and to codify our best practices, not change them. At any rate, I have no interest in an RfA no. 3; the "enforcement" aspects of adminship are of zero interest to me; instead, I've been highly supportive of tech-work unbundlings like template editor and page mover (and would have commented favorably in the unbundling RfC atop this page if I'd not been busy off-site at the time). Happy to address any more specific concerns, but this may all be moot if I need to be shunted into EFR and EFFP for a long while before being considered for EFM. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 12:45, 24 September 2017 (UTC)
* Thank you for the reply, like I led with it has been a long time. I don't know about "a long while" but I would like to see activity at EFR/EFFP for this access. Creating any deny filter is in effect "enforcement" of something as well. — xaosflux Talk 17:23, 24 September 2017 (UTC)
* Sure. I didn't have any interest in deny filters, just logging ones. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 21:18, 29 September 2017 (UTC)
Endorsements / Comments
* Oppose at this time, however I encourage EFR/EFFP engagement as a way to enter this arena. — xaosflux Talk 15:38, 27 September 2017 (UTC)
* Oppose also at this time. I'd like to see more familiarity with the edit filter before granting the bit. I'd encourage more reading of the existing filters, the documentation, and have some input to practise (and demonstrate) putting it all together. -- zzuuzz (talk) 18:21, 27 September 2017 (UTC)
* Request change: EFH rather than EFM might be helpful; it provides a lot more access to pre-existing filter code, which honestly seems like better documentation. :-) A large number of the filters I attempted to examine were not available to me. E.g., I can't look at 31, which zzuuzz suggested looking at. — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼ 21:18, 29 September 2017 (UTC)
Suggested filter
Just a heads up, but I sent an email to the editfilter list email with a suggestion to expand the filters to stop a recent type of spam. I emailed it in order to not give any ideas to possible vandals. Thank you. <b style="padding:2px 4px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 01:52, 3 October 2017 (UTC)
* Responded to by MA -- There'sNoTime (to explain) 20:52, 4 October 2017 (UTC)
Filter 148
Is filter 148 functioning correctly? Activity on it has diminished drastically since mid-September. --Drm310 🍁 (talk) 16:38, 6 October 2017 (UTC)
* This is most likely because of WP:ACTRIAL — MusikAnimal talk 17:25, 6 October 2017 (UTC)
* Ah, OK. That makes sense. That's actually very positive outcome, IMHO. --Drm310 🍁 (talk) 17:52, 6 October 2017 (UTC)
Request for EFH bit for QEDK
Hello, I'm QEDK, a non-admin trainee clerk at WP:SPI. I think EFH might help me with certain cases where I can view the private logs (just citing the Europefan one for now, and more, probably). I hope this right will help in discovering prolific socks which trip private filters, some of which land up at SPI. I understand that this is a need-only basis right and the BEANS requirement for granting this right. With thanks. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 18:54, 5 October 2017 (UTC)
* Support at least once you're out of training. In my opinion EFH makes sense for any SPI clerk — MusikAnimal talk 01:24, 6 October 2017 (UTC)
* In interest of full disclosure, I was in the December 2015 batch which started off but ended before the training was deemed complete. Either way, in the May period next year, which is when the promotion to full clerk was considered, I was inactive then and did not get promoted to full clerk on that basis. I have been working actively as a trainee since but not asked about the promotion to full clerk, just a wandering soul until some CU decides. :) --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 04:17, 6 October 2017 (UTC)
* Support - sure. Trusted user with some use for the bit. -- Ajraddatz (talk) 02:00, 6 October 2017 (UTC)
* Oppose until out of training. As soon as you're out of training, support. I note that you've been in training since December 2015, and if I recall correctly, you weren't promoted initially due to inactivity (correct me if I'm wrong). Either way, I'd want to see you in the role indefinitely before granting this right. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 10:31, 6 October 2017 (UTC)
* QEDK has been working entirely independently at SPI as a clerk for a while. Could you start a formal discussion to promote them to a full clerk if you find their work satisfactory? Any CU can do so. I'd recommend placing this on hold until such a discussion concludes. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 01:32, 7 October 2017 (UTC)
* Stupid typo - see above. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 01:33, 7 October 2017 (UTC)
* Yeah, you are certainly correct but there was no formal training thereafter and since the trainee clerk status wasn't exactly an impediment to any SPI work, I didn't ask for a promotion, but thanks for taking it up with Katie, Rob, I've been promoted to full clerk now. While the requirements do say that trainee clerks can be granted the right too, I'm guessing you have your own thoughts on this, which is absolutely fine. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 17:41, 8 October 2017 (UTC)
* Support I don't see the harm in viewing hidden filters. The user has enough experience at SPI to be trusted, and if this helps at SPI, even better. As a trainee, QEDK can still acquire EFH permission per Edit_filter_helper. — JudeccaXIII (talk) 20:42, 6 October 2017 (UTC)
Request for EFH bit for GermanJoe
Hello, I am a Wikipedian since 2010 and often involved in handling spam and other forms of promotional editing (link cleanup, blacklist reporting, COI-related content cleanup). Access to some spam- and promotion-related logs (for example filter 711 for dead links) would be useful to look for possible spam domains and patterns. As a software project manager I am not a professional full-time developer, but have basic knowledge in regex (and a few structured languages). I also have a strong password as required and know how to handle non-public information. GermanJoe (talk) 23:06, 5 October 2017 (UTC)
* Support - trusted user with a use for the bit. It seems to me that someone involved in COI-related cleanup would benefit from seeing if an account had triggered the SBL or certain private filters. -- Ajraddatz (talk) 02:06, 6 October 2017 (UTC)
* Could you explain your use case more? I'm not particularly convinced by the filter 711 reference. I need to see something that puts your "need" above that of a typical vandal fighter. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 10:37, 6 October 2017 (UTC)
* - initially the filter was public, so I'll try to offer a few more details from the past usage. I (and a few other non-admin regulars) could find new dead link spammmers quite easily while looking through these logs. I know, I have cleaned up atleast 5-6 new cases that way. Granted, such cases would have been found out eventually with regular editing, but sometimes such spamming goes undetected for years - especially in low-traffic articles. Access to the SBL would be another obvious benefit to keep an eye on additional spamming attempts. I am not sure, how you define "need" in that context, but the availability of such data can help to detect problems in this area a lot easier and more efficient (compared to a luck-based random approach). Several other spam-related filters (i.e. 752, 762, 793 etc.) would possibly also contain useful data in occasional related situations, although with hidden filters it's hard to tell for me of course. GermanJoe (talk) 12:35, 6 October 2017 (UTC)
* Could you explain this "dead link spam" issue? Perhaps I'm just not understanding. Are you saying there are editors spamming already dead links onto pages? How is that a problem? ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 12:37, 6 October 2017 (UTC)
* Oops, I am sorry for the misunderstanding. I wasn't aware this jargon-y term was unclear. "Dead link spamming" (professional spammers probably have a more technical term) searches for dead external links, that are usually tagged with Wikipedia's "dead link" maintenance tag. Such tagged links are then systematically replaced with spam links (usually for products or other commercial sites). This type of spam is one of the more "popular" tactics, and also a good example for how logs and semi-automated measures can help to limit such problems. GermanJoe (talk) 12:52, 6 October 2017 (UTC)
* Alright. I think in this case, I oppose granting the right but support making that filter public. I don't think the need here rises to the level it should for edit filter helper, which is really not intended for log patrolling/counter-vandalism. This is a point I was assured on by many people championing the proposal when I had reservations. On the other hand, looking at this filter, there's really no way to get around it, so I don't see an issue in making it public. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 13:17, 6 October 2017 (UTC)
* Oppose I tend to agree with BU Rob13, and I was already thinking that filter 711 should be public and possibly even tag. any opinion on that?762 tags as "possible link spam", so you already can track those hits. Meanwhile 793 disallows. 752 should probably be public too, and seems to be very much prone to false positives, so frankly I question its usefulness to begin with. Overall I think EFH is chiefly about tracking sockpuppetry and long-term abuse, not spam detection and counter-vandalism. In most cases any filter that isn't targeted at specific user(s) should be public, and you should feel free to question the visibility of any filter you think might qualify as general-use — MusikAnimal talk 15:47, 6 October 2017 (UTC)
* Straying a bit off-topic and probably better discussed in a separate thread: if WP:EH ("There are three groups of editors for whom this is is useful:") is meant to exclusively limit this access to the listed three use cases (and not as an incomplete list of common examples), the phrasing should be clarified. However, the RfC closure to establish EFH doesn't mention such a strict limitation. Atleast for me it wasn't clear that these changes aren't meant to help anti-spam contributors or other editors with potentially beneficial but unlisted usages. Regarding public 711 filter: the filter is mostly targetted against repeated and/or organized spammers. Some of these spammers may have the motivation to research the filter to improve their methods. Admittedly a very small risk, but a risk nonetheless. GermanJoe (talk) 21:03, 6 October 2017 (UTC)
* re: 711, I think I made it private because it seemed like some users had figured out how to avoid the filter, but I forget the details, so it can probably go public. Sam Walton (talk) 10:51, 7 October 2017 (UTC)
Filter 881
I tried making an edit filter – would someone like to sanity check Special:AbuseFilter/881? It should perhaps be set to deny, if there's no risk of collateral. Κσυπ Cyp 14:13, 8 October 2017 (UTC)
* I've trimmed it down to be a little less complicated. That IP range has a lot of good edits but is not super busy. I suspect false positives will be slim to none. I'll monitor and if all goes well we'll put it in disallow — MusikAnimal talk 01:22, 9 October 2017 (UTC)
* Thanks – I tweaked it a bit more, and removed rmwhitespace, since it doesn't seem to be compatible with \s and \b. Κσυπ Cyp 12:48, 9 October 2017 (UTC)
* Looks good, I think we're ok to disallow — MusikAnimal talk 15:10, 9 October 2017 (UTC)
Filter 384
Possibly make the regex for "fag" less inclusive to prevent these kind of false positives. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 17:44, 8 October 2017 (UTC)
* Should be fixed! — MusikAnimal talk 00:33, 9 October 2017 (UTC)
* Change to to prevent faggit from not tripping the filter? --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 08:30, 9 October 2017 (UTC)
* Sure — MusikAnimal talk 15:12, 9 October 2017 (UTC)
Filter 680
A false positive came through on 680 when someone was trying to add ♩ to Romanian Folk Dances. I believe the may be a tad strict since the musical notes (♩♪♫♬) do have some encyclopedic value like the pitch symbols ♭♮♯ (U+266D/E/F) that were removed recently. Can we change the range ♃-♬ (U+2643-U+266C) to ♃-♨ (U+2643-U+2668)? Thanks. (I also looked through the last couple hundred of hits and found nothing nefarious with these symbols.) <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 14:09, 6 October 2017 (UTC)
* Can we also take out ☉ (U+2609), as it is now used in the name of an instrument on the Parker Solar Probe. See this false positive. Thanks. <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 19:09, 9 October 2017 (UTC)
* Not sure if this is such an edge case it can be left, but I did add the content to the page. — xaosflux Talk 19:40, 9 October 2017 (UTC)
Request for Edit Filter Helper - Dane
Hello,
I am requesting the Edit Filter Helper right so I can view hidden logs. I am a Tool Administrator at the ACC tool and run across tripped filters occasionally that I am unable to view/evaluate in the course of my work there currently and this would help me in processing those requests. Thank you! -- Dane <font color="#00AC1D">talk 03:50, 4 October 2017 (UTC)
* Q: Can you give a specific (even hypothetical) scenario where seeing the logs would be useful? Crow Caw 15:01, 4 October 2017 (UTC)
* A: Yesterday, I worked a request for example that showed an Edit Filter was tripped but only had a number specified. When we defer requests for CheckUser, we've been asked by CU to supply as much information as possible to assist in their processing of the requests. Because I did not have that information available I wasn't able to properly defer even as a tool administrator and I had to find an on-wiki administrator to research the specific request and write up the summary for CU which can add a delay in processing. In some cases, having the EFH right may even allow a bypass for CU if it's clear that it's the target for a filter created for specific LTAs. -- Dane <font color="#00AC1D">talk 19:43, 4 October 2017 (UTC)
* Expanding on the above, I don't believe being an ACC tool administrator is a sufficient reason to grant, and given the fact you were able to find an administrator to assist there's no real issue.. However, do you posses sufficient understanding of regex/AbuseFilter syntax to be able to reliably make the call on if a specific LTA filter was indeed targetting the request IP you're looking at? -- There'sNoTime (to explain) 19:47, 4 October 2017 (UTC)
* It is true that I was in one instance able to find an administrator who holds sysop on en-wiki as well to evaluate it, however there have been times where there is a delay in that. In asking for the right i'm looking to be able to avoid this delay to resolve the issue myself. I do have a basic understanding of regex and I would defer any case that was in question or unclear to me per the existing operating guidelines. I do not have intent on authoring any filters now or in the future. -- Dane <font color="#00AC1D">talk 20:20, 4 October 2017 (UTC)
* Oppose No real on-wiki need for the tool if other, more trusted editors are easily available . There's a reason we have private filters and granting access solely for off-wiki tools is not a good precedent to set, given there is a real risk of sharing details of private filters with unauthorised parties on mailing lists we would not have access to. EFH was not created for this purpose -- There'sNoTime (to explain) 20:59, 4 October 2017 (UTC)
* Commenting in my capacity as one of the ACC project leads, this seems like an odd objection to make against a group of users who are specifically vetted for their ability to comply with privacy restrictions and are indeed required to sign the Access to nonpublic information policy. -- FastLizard4 (talk•contribs) 22:08, 4 October 2017 (UTC)
* The signing of that document doesn't come into it - I've signed multiple NDAs for WMF, but they don't make me more or less suitable for access. The reason for my objection is as I detailed above - there's no need for this right to be granted -- There'sNoTime (to explain) 07:05, 5 October 2017 (UTC)
* Your own argument is "No real on-wiki need if other, more trusted editors are easily available". With all due respect, if your argument for suitability for access doesn't involve user trust, then why did you literally put those words in your argument? -- FastLizard4 (talk•contribs) 07:33, 5 October 2017 (UTC)
* ...Expanding on my above comment,, your argument can be easily rephrased from "No real on-wiki need for the tool if other, more trusted editors are easily available" to "No real on-wiki need for the tool since Dane is not as trusted as other editors." I believe that it is fair to ask you to expand on the reasons for this distrust in response to my original comment that it seems odd to object on a trust basis to one of the more vetted and trusted groups on Wikipedia, or that you use another basis for your argument that there is no demonstrated need here. -- FastLizard4 (talk•contribs) 07:43, 5 October 2017 (UTC)
* Rephrased perhaps, but that was not the intended meaning - it's clear Dane is a trusted individual as he's been accepted to the lofty position of a tool administrator, but he's not a "trusted editor" in way of advanced permission. I use the phrase "trusted editors are easily available" to refer to the enwp admins who are active at ACC (not counting the many many active admins on IRC). As Crow rightly points out below it seems like an email with the regex would cover 99% of the issues and I'll add a in would solve the rest. You explain below you have an outsider perspective with respect to edit filters, so perhaps you're not familiar with the days people have sunk into creating and maintaining our LTA filters? -- There'sNoTime (to explain) 08:06, 5 October 2017 (UTC)
* Rephrased the above for clarity, additions in green -- There'sNoTime (to explain) 08:19, 5 October 2017 (UTC)
* Again though, I don't feel like you're addressing my argument - my argument is that you have no reason to consider Dane untrusted, yet you continue to make your case as if that's a given (you state "he's not a 'trusted editor' in way of advanced permission"). I would like you to expand on the specifics for why you are arguing this or abandon the premise. Also, though I appreciate the labor that goes into writing effective filters, I don't see how stating that fact has any bearing on Dane's request - unless of course we take as a given that Dane is untrusted and is thus a risk for undoing all that work, which is the point I am contesting here. -- FastLizard4 (talk•contribs) 08:17, 5 October 2017 (UTC)
* Outsider perspective here too. I don't have a strong opinion on this, but I was wondering, this is a new user group, I am getting an impression that this is being vetted as if it were a WP:EFM request rather than EFH? Just a thought. Alex ShihTalk 08:24, 5 October 2017 (UTC)
This isn't a hill I want to die on, but my point is being misunderstood. Dane is perfectly trusted, I think he should have passed RfA and that isn't the issue I have. Granting criteria #1 highlights a requirement for "need". I don't see a need here when other trusted editors (read "Administrators, EFMs" as I clarified above - that was my poor wording) are available on IRC and through a mailing list. Perhaps I am using this as a point to highlight the inadequate definition of "need" (the major concerns from the RfC were creep), and that's not fair on Dane, so I apologise there. Consider my oppose struck, but a discussion needs to happen over things like this. This was the wrong place to have that discussion -- There'sNoTime (to explain) 08:41, 5 October 2017 (UTC)
* Okay, I see the point you're making now. After our discussion on IRC, I can see the question of need itself being valid even when trust is disregarded, but that's an area where I'm thoroughly unqualified to comment, so I'll leave it to others to decide. -- FastLizard4 (talk•contribs) 08:54, 5 October 2017 (UTC)
* I'm still not sure that ACC yields enough of an ongoing need for the access. The logs won't tell you why a filter was tripped, just that it was... you'd need to dig into the regex to determine why. And since the number of EFs dealing with ACC is small compared to the total (Meta prefers to handle name blocks now), it seems like an email with the regex would cover 99% of the issues, with that 1% being new additions to the filter. Crow Caw 22:33, 4 October 2017 (UTC)
* I think this argument can be reversed and be equally as valid - even if there isn't a hard ongoing need, if there aren't any specific issues that lead to the candidate user to be considered untrusted despite their long-time status on Wikipedia, as long as they are competent in regular expressions and know not to break things, and as long as there are even potential gains to be had, is there harm in granting the user group? To me, the potential usefulness of this access is at least some kind of positive factor, and there don't seem to be any negative factors beyond lack of precedent which seems like should it should be a relatively minor factor - though this is admittedly very much an outsider perspective (with respect to edit filters). -- FastLizard4 (talk•contribs) 07:51, 5 October 2017 (UTC)
* Support - this is a perfectly reasonable request IMO. This is such an inconsequential right that I can't imagine why we would turn away anyone with a potential use for it. -- Ajraddatz (talk) 00:19, 5 October 2017 (UTC)
* As for this being an inconsequential right, I draw your attention to the closing caveats, namely community and/or the granting administrator are adviced to carefully evaluate the candidates before granting the flag due to the huge fallouts of any misuse. -- There'sNoTime (to explain) 07:23, 5 October 2017 (UTC)
* There is almost no fallout for misuse. The absolute worst-case scenario is that an LTA is able to figure out what the filter conditions are, so they can bypass it a few minutes earlier than they could by trial and error. And when any sort of trusted editor is the one requesting the right, we can be pretty sure that the worst-case scenario won't happen. -- Ajraddatz (talk) 08:31, 5 October 2017 (UTC)
* Pinging .Any comments? I am sure he could address your point lot better than me! Winged Blades of Godric On leave 17:34, 5 October 2017 (UTC)
* Support - Per Ajraddatz. Perhaps the demonstrated need (#1) is not strong enough, but I would be satisfied if there are potential uses (indicated in the response above) by a trusted editor. Alex ShihTalk 06:44, 5 October 2017 (UTC)
* Can you comment on how your use case exceeds that of a typical vandal fighter who could perhaps be benefited by viewing private logs? We decided rather resoundingly that such editors should not receive access to this right, and I am very worried about precedents being set with this user right. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 10:19, 6 October 2017 (UTC)
* I hope to hear from Dane before committing one way or another, but put me down as oppose until I'm convinced further. I'm not sold on this use case, mostly because there are many admin ACC volunteers and this isn't frequent in the ACC workflow. (I hope no admin will close this until I get a response.) ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 19:32, 6 October 2017 (UTC)
* Sorry for the delay, i've been mobile most of the day. In regards to my usage vs. a typical vandal fighter, my usage of EFH will allow me to identify potential issues prior to giving someone a way to access en-wiki via an ACC request. On requests that do get deferred, our CU's have requested as much information as possible when we defer to them (they typically have a large backlog at ACC and a very detailed comment is helpful to their research) and this will allow me to present more robust comments to them regarding tripped filters. In my most recent example, I would have deferred a request without any idea why I was deferring and thus unable to give additional information to the CU - whereas with this right I could've supplied an explanation that would be helpful. -- Dane <font color="#00AC1D">talk 20:22, 6 October 2017 (UTC)
* At the risk of sounding like a judge: Is it your contention that all ACC volunteers automatically qualify for this right? If not, how are you distinct from the general group? If so, I have other questions. PLEASE DON'T CLOSE THIS FOR ANOTHER 24 HOURS. I think it's important to get the ACC precedent right. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 01:37, 7 October 2017 (UTC)
* I am not attempting to set any sort of "precedent" here and think that the discussion regarding whether ACC volunteers do or do not automatically qualify for the right is best fit for an RfC and not my individual request for the permission. Until that RfC, I think it should be evaluated based on individual need as demonstrated until any such RfC happens, and I believe i've covered my individual need above a few times. -- Dane <font color="#00AC1D">talk 02:37, 7 October 2017 (UTC)
* Well, at least in my opinion, your need does not exceed that of a typical ACC volunteer. It's hard to separate your case from a potential precedent, as if we say yes to you, I see us saying yes to all ACC volunteers. That's a somewhat large group – certainly larger than who I anticipated getting this right. While I may not be opposed to expanding the use cases to include ACC, I think we need a larger discussion surrounding that with more time to ask questions and probe your recruiting process to determine if we can justify giving this highly-sensitive right to a potentially large group of people. Until such a discussion is held, and without seeing how your need exceeds that of a typical ACC volunteer, I must oppose. (I would support an RfA, as a side note. You are clearly qualified.) ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 03:20, 7 October 2017 (UTC)
* Unsure Crow thoughts and seeking more discussion. On the positive side, I see zero issues with trust, and the Nonpublic data agreement is a huge plus. On the flip side, I'm still having trouble with the ongoing need for the right. This may very well be due to my not understanding the ACC workflow, which is (to me): a user sends a request in to ACC because they were blocked from creating an account. They likely will state the name they tried to submit. ACC volunteer looks at the EF log for their IP (is it always going to be the same?) and sees that an EF blocked it. Without EFH that's as far as you can go. With EFH, you check the specific filter, pour through a huge ugly regex, see the match and say "Yep, you were blocked alright." There's not going to be much more context than that to tell you what to say to a CU other than "This guy tripped a filter and might be a sock of any of a hundred different people or could just be a troll, or might just be an innocent user." (Please elaborate or correct me on any of this).
* So even with that degree of utility, the ongoing need still eludes me. Those few EFs don't change often, and (again from my own POV), it would seem easier to copy the huge ugly regex to a text document and sort/alpha/annotate/de-regex/etc to make it an easier lookup than opening the huge ugly regex every time. (I keep saying that, you'll see what I mean!). In fact that's what I do to a couple of the larger aggregated ones... I often get lost parsing the H.U.R. so keep offline copies sorted into a much easier format. Thus my point above about a periodic dump of the handful of filters that would be of any use in ACC would be just as meaningful.
* I did support the EFH permission creation, (and may have had some part in kickstarting the RFC) but I respect and concur with the concerns expressed during it. As Rob alluded to, "ease of access" was a huge concern, as was "real ongoing need", which is where I'm stuck at the moment. I don't think access to the data itself is problematic, but that data being fairly static, the ongoing need for tool is the hangup. Free discussion welcome! Crow Caw 15:33, 6 October 2017 (UTC)
* Just a comment regarding "a user sends a request in to ACC because they were blocked from creating an account. They likely will state the name they tried to submit. ACC volunteer looks at the EF log for their IP (is it always going to be the same?) and sees that an EF blocked it": I've handled a few ACC requests and I haven't come across one that was disallowed due to 527. 579 isn't disallow and afaik there are no other account creation-related filters. Dat GuyTalkContribs 16:16, 6 October 2017 (UTC)
* There is 102 that has the H.U.R. which is sort of related. Crow Caw 16:29, 6 October 2017 (UTC)
* Regretful oppose In the absence of further discussion to my concern, and with the timer expired. Striking default qualifier as discussion followed. As DatGuy mentioned, there doesnt seem to be efs of concern to ACC that are both Private and Disallow. Since Meta handles username blacklisting now, it looks like we let them to free the cycles. To the initial use case given, if an action only gave a filter number then that filter was already public as are all its logs. So I land as oppose due to still not seeing the ongoing need wrt ACC. I'm still open to discussion to help me see something that I'm not understanding. Crow On The Go! Caw 16:22, 8 October 2017 (UTC)
* In regards to the ACC use need, providing checkusers with a summary similar to "Request XXXXXX had an IP that tripped filter X correctly" is where this comes in handy to me. Just yesterday I was speaking with a CU who reiterated this would be way more helpful than "IP X tripped X", as we can actually confirm whether it was a positive (correct) trip of the filter. -- Dane <font color="#00AC1Dcf">talk 16:33, 8 October 2017 (UTC)
* Thanks for replying. The thing in that scenario is, all youre going to get with efh is the regex that tripped the filter. Without getting too beansy, youre unlikely to get much guidance to what spi it is from. I kno you cant use a real world case for privacy reasons but can you give an example of an actual filter trip leaving out the pii? As i mentioned i think most of the acc filters are public already. Crow On The Go! Caw 19:38, 8 October 2017 (UTC)
* Abuse Filter 855 is an example of one that has tripped that I was unable to view/evaluate properly to give additional information. As you said, I know all about the WP:BEANS involved in this so I don't want to say much more - but viewing the filter to give the additional data behind what it's stopping/whether it appears valid or invalid trip. Without that, basically my only comment can be "IP X tripped filter XXX" instead of "IP X tripped filter XXX; appears to be a valid trip according to the details of XXX". -- Dane <font color="#00AC1D">talk 19:51, 8 October 2017 (UTC)
* Interesting, 855 has nothing to do with account creation. It covers specific editor(s) against a small set of pages (and not their own) so should not be showing up at ACC. Unfortunately I'm still not seeing the need vis. ACC given the lack of private-&-disallow filters here, and that Meta now handles username blacklisting so we're likely to defer any future EF requests along those lines to Meta. — Preceding unsigned comment added by Crow (talk • contribs) 16:22, 9 October 2017 (UTC)
* Without sharing too much, I can tell you that the data from 855 is relevant to our checks at ACC when deferring to a CU as previously discussed. -- Dane <font color="#00AC1D">talk 16:43, 9 October 2017 (UTC)
* I can probably guess why, but in this particular case the only question is whether the filter is too broad, which only a CU can answer anyway. EFH/EFM can only add the specific consideration which brings it to CU's attention in the first place, and leave it to them to see if its a FP/Valid. It saves CU or SPI clerk a click or 2, and while I'm not one to push more work on them, a SPI clerk needs to endorse before a CU will look, and that is the main use-case that was driving the EFH creation. Crow Caw 17:01, 9 October 2017 (UTC)
* Support - Dane is a trusted user and I can see how this would be beneficial for ACC purposes and having more eyes on things will be useful from an SPI standpoint. CHRISSY MAD ❯❯❯ ¯\_(ツ)_/¯ 03:51, 10 October 2017 (UTC)
* Oppose per lack of demonstrated need and per Crow. Users above who voted merely because a user is trusted are reminded of the concerns raised during the EFH RfC. This cavalier attitude to hat collecting and ease of access is problematic. <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 04:03, 10 October 2017 (UTC)
* With all due respect, is active on the ACC tool and an existing edit filter helper, so she likely is able to relate to the statements i've made above for need/usage of this right. Your comment overlooks her statement regarding how she see's the benefit for use for the ACC tool and implies she voted simply because she see's me as a "trusted user". -- Dane <font color="#00AC1D">talk 04:29, 10 October 2017 (UTC)
* My comment was not directed at her, but rather, all the users above me who voted support. <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 08:58, 10 October 2017 (UTC)
* I would counter by saying that the whole concept of requiring a "need" for the tools is problematic. Nobody needs any advanced permissions here. Nobody needs to be here at all. Instead, we have thousands of volunteers spending their time here, and the least we can do is give them the technical access necessary to fully do the jobs they've signed up for. We should look for whether a candidate has a potential use for the tools, without going near language as strong as "need". The candidate has clearly defined how he will use this permission - looking at filter tripping by IPs when evaluating certain ACC requests. As someone who formerly volunteered at ACC, I can attest to giving these users as much view access as possible so they can have the full picture when handling requests. All that remains is figuring out whether I trust the candidate to use the tools properly. In this case, proper use means looking at private filter logs from time to time, and not revealing the contents of the filters to long-term abusers who would then be able to bypass the filters 10 seconds faster than their usual trial-and-error method. I think I can make that leap of faith here. -- Ajraddatz (talk) 08:51, 10 October 2017 (UTC)
* The reason "need" keeps coming up is that it is the first consideration when considering the grant. See also the archives at RFPERM where "no need for" is often given when declining. And I won't even bring up RFA (though I guess I just did). Need was an important consideration and sticking point during the RFC as well. Now that all said, thanks to for continuing to explain... it's not obvious to one outside the ACC environment, and it's really hard to explain things completely with a mouthful of WP BEANS, but I do now see the relevant use case where this is useful outside of action=accountcreate in EFs. So one more question if I may: when you defer a request to CU, how is that done? A button in the tool, mailing-list, SPI, an "on-call CU", etc? Crow Caw 14:57, 10 October 2017 (UTC)
* There's basically a 'defer to checkusers' button, that when pressed moves the request to a CU queue. Dat GuyTalkContribs 15:19, 10 October 2017 (UTC)
* We don't have an SPI process (like clerks) and in my time at ACC we haven't ever discussed a CU case in the mailing list. We have a CU queue in ACC that we defer to using the tool and when we get a request that requires CU intervention, we make a note in the tool (a note can be set to "Tool User" or "Tool Admin" for visibility). The note usually contains a description of why we are deferring the request for CU (e.x. "What sock does it match? Is the IP CU Blocked without an ACC Ignore note? Did an Edit Filter trip? Is there something suspicious that needs to be evaluated?") and then CU processes the requests. The feedback from CUs has been that the descriptions with more information cut down the time for the CU to process (especially when the CU queue on ACC is frequently in the 40s to 60s with a couple weeks backlog). In evaluating a normal request that doesn't appear to be directly CU, for example, recent vandalism and edits within a certain timeframe goes into the CU queue. Filter trips are looked at as well when we evaluate requests, so this doesn't limit the use case to just CU-Blocked IPs. I hope this helps clarify a bit more. -- Dane <font color="#00AC1D">talk 15:32, 10 October 2017 (UTC)
* Thanks and yes this does fill in a huge gap in my understanding about the use case and associated need. I shall ponder this, but for now I've struck through my oppose. Crow Caw 15:40, 10 October 2017 (UTC)
* Comment I fear this request is derailing slightly into overall comments on ACC volunteers having EFH. I've discussed this extensively off-wiki with Dane, and having recently become a checkuser I can appreciate where his comments and need comes from. Not having even a basic "looking at the filter I can see this was caught because X" adds significant time onto processing a request (not to mention trying to weigh up if a check is a good idea). I'm mindful of seeming insincere if I now support after my heated oppose above, but my sentiment remains one of supporting this request. Regardless of how this request ends, I'd like to propose we have a proper discussion on EFH for ACC (perhaps it could be dealt with in a similar way to SPI clerks?). Additionally, I would like to offer Dane mentorship should he be granted this right, as a compromise against the wholly valid concerns brought up regarding access and understanding of syntax -- There'sNoTime (to explain) 15:47, 10 October 2017 (UTC)
New function available for use
We have added ccnorm_contains_any. It is a convenience function 'cause it literally translates to contains_any(ccnorm(param1), ccnorm(param2), ...) It can be used when we need to find multiple strings within another string and we want to use their canonical representation for comparison.
Here are some examples
DMaza (talk) 02:40, 14 October 2017 (UTC)
* for the examples above, what is the reference string? — xaosflux Talk 02:56, 14 October 2017 (UTC)
* You would use it like this . Just like it will search for 'foo', 'bar' in added_lines, only that in this case it will ccnorm everything. Makes sense? DMaza (talk) 05:08, 14 October 2017 (UTC)
* In the example table above - why is row 2 false? What was the example added line? — xaosflux Talk 09:32, 14 October 2017 (UTC)
* is equal to, which is always (for any edit) since "WIKIPEDIA" doesn't contain any of "FOO", "BAR" or "BAZ". And similarly, if someone adds a line saying "w1k1p3d14" so that , then would be for that particular edit, but would be for an edit where someone adds a line saying "tw0 ducks w3nt t0 th3 b4r!!!!". Κσυπ Cyp 14:17, 14 October 2017 (UTC)
* Thank you, so in the examples above the first value is compared against all subsequent values correct? That is what I was missing. — xaosflux Talk 14:31, 14 October 2017 (UTC)
* Yes, that's correct. Κσυπ Cyp 14:56, 14 October 2017 (UTC)
What can edit filters on en.wp know about Commons images?
In a discussion (not on Wikipedia) about images used for vandalism, it was noted that edit filters are a good way of preventing some vandalism. This got me wondering what edit filters here can know about Commons images? Obviously they can know the filename of the image added, but is that it? Can it know what categories it is in? What other pages it is used on? Anything else?
This is not a request for an edit filter, it is a request to learn what an edit filter could theoretically do. Any questions about how it would be used, and whether using it for that is a good idea or not are for much later. Thryduulf (talk) 15:24, 14 October 2017 (UTC)
* Far as I know, local edit filters only get information from local wiki. So not Commons categories wouldn't be included, nor usage. Jo-Jo Eumerus (talk, contributions) 15:28, 14 October 2017 (UTC)
* This. We can also usually know the display size. To explain a bit further, we can detect uploads, and we can detect page edits. When you upload an image locally we can check file size, height, MIME, etc. When you make an edit we know basically nothing about anything linked in that edit, including local files, only the text being added. -- zzuuzz (talk) 16:05, 14 October 2017 (UTC)
Filter 384 2
Can we add to 384 to prevent this type of false positive? <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 02:53, 9 October 2017 (UTC)
* Done – I assume you meant "\b[A-Z][a-z]+\sDick\b". Κσυπ Cyp 12:48, 9 October 2017 (UTC)
* Yep. Lazy copy paste on my part. :/ Thank you! <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 13:13, 9 October 2017 (UTC)
* Another false positve. Can we exclude cases of "Dick's Sporting" as it's both a franchise name and on some stadiums/arenas? Should also catch false positives of the possessive Dick's when referring to someone's name. <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 20:25, 15 October 2017 (UTC)
* Ok, added, which should be equivalent. Κσυπ Cyp 05:44, 16 October 2017 (UTC)
* That will work for the "Dick's Sporting" but won't work for any possessive form of "Dick's". See examples such as "Dick's works" and "Philip K. Dick's poetic". <b style="padding:2px 2px;font-variant:small-caps;whitespace:nowrap;color:#000;letter-spacing:-0.5px">Nihlus</b> 14:05, 16 October 2017 (UTC)
* Sorry, hadn't seen the a-z in your . How about now; John Q. Dick and Dick Q. Johnson should be able to take Dick's kitten Mr. Dick to Dick's Vet to be checked by Dr. Dick, without triggering 384. Κσυπ Cyp 08:58, 17 October 2017 (UTC)
Filter 680 (again)
Could someone exempt ✰ ? The jpop stars demand it. FP: https://en.wikipedia.org/wiki/Special:AbuseLog/19529628 What's the deal with stars tho... --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 16:36, 18 October 2017 (UTC)
* If it's alright. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 05:41, 20 October 2017 (UTC)
* ✅ All the best: Rich Farmbrough, 11:55, 20 October 2017 (UTC).
Filter 812 didn't disallow edits
(contribs) (a non-autoconfirmed user) made 5 edits, each increased page sizes by 2.7 million bytes, and for some reason filter 812 didn't disallow any of them. Is there any reason why? Do filters sometimes miss edits? — MRD 2014 Talk • Edits • Help! 00:37, 14 September 2017 (UTC)
* If I had to guess, it was because the edit was commented out? Other than that, I have no idea. Seems to be working properly everywhere else. Primefac (talk) 00:48, 14 September 2017 (UTC)
* It's enabled and hasn't been changed since December 2016. — MRD 2014 Talk • Edits • Help! 01:18, 14 September 2017 (UTC)
* Sorry, I meant that the edits themselves were inside of comments. My second comment was regarding the fact that the filter was tripped 2-3 days ago, and about once a week since it was implemented. In other words, "it's working, and this is my only theory why it missed these edits". Though I do notice that they were all "new section" edits - maybe that threw it off? Primefac (talk) 01:22, 14 September 2017 (UTC)
* According to the filter, it doesn't matter what the edit summary says. — MRD 2014 Talk • Edits • Help! 02:42, 14 September 2017 (UTC)
* Another major AbuseFilter bug...??? It should definitely 100% have stopped this, and indeed I can test the filter against that user at Special:AbuseFilter/test and it matches. I think there was some breaking change that happened a while back, because we've had several filters malfunction, where apparently the variables being read have the wrong values, are for the wrong edits, other weirdness. I'll create a task and propose rolling back the extension to a stable version — MusikAnimal talk 16:30, 14 September 2017 (UTC)
* Created T175933 — MusikAnimal talk 17:04, 14 September 2017 (UTC)
* Bit off topic suggession. I suppose a specific warning message that has links about copyright issue, referencing and encyclopedic writing style to this filter may benefit users who are unaware off copyright issues.
* Mahitgar (talk) 12:21, 1 October 2017 (UTC
Looks like a new filter is needed. I'll go and request one.TomBarker23 (talk) 10:40, 19 October 2017 (UTC)
* Nothing wrong with the filter as far as I know. There is a bug with this filter that is being tracked at T175933, as shown at the top of this thread. — MRD 2014 Talk • Edits • Help! 02:56, 23 October 2017 (UTC)
Request for EFH bit for Nihlus
I'd like to have Edit Filter Helper assigned to. They clearly meet the "requirements for granting" #2 through #5. For criteria #1, need, I would like to highlight his work in finding false positives over at WP:EF/FP and the improvements he has suggested (such as the threads above). The Edit Filter Helper page describes one of the groups of editors the right will be useful to as Those interested in helping with edit filters but who do not meet the thresholds required to be able to modify them - Nihlus shows a clear interest in helping out with our filters. His contributions to the noticeboard, mailing list, the regex used in his bot () and countless personal conversations with myself (which I can attest to) has show he has the required competence with syntax and regex. -- There'sNoTime (to explain) 20:57, 20 October 2017 (UTC)
* do you "want" this? — xaosflux Talk 21:46, 20 October 2017 (UTC)
* I believe it will allow me to be more productive while also saving the EFM's time, so I accept the nomination. Nihlus 22:30, 20 October 2017 (UTC)
Slow filters
Community Tech set up a new log to record cases where specific filters take longer than half a second to execute. It's only been running for a few hours, but here are some early results: Clearly, filters 755 and 765 are the most laggy. Looks like MusikAnimal has already disabled 765 :) Anything we can do to optimize 755? Kaldari (talk) 20:03, 25 October 2017 (UTC)
* 755 has been disabled as well. Nihlus 20:21, 25 October 2017 (UTC)
* Is it feasible to build a "test" feature into the abuse filter extension that takes the most recent 500 edits to the wiki, runs them through the filter (possibly with pauses in between to prevent performance issues, if that's a concern), and returns the average, median, and maximum time the filter took to process for those edits? This may help edit filter managers (especially new ones) to ensure their filters aren't too expensive before enabling them. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 22:39, 25 October 2017 (UTC)
* Way back when we had something like this, but it was ironically removed because it was hurting performance. Times have changed, and I think we might soon get it back. The Anti-Harassment Tools team is currently testing this on ptwiki (T177641) and if all goes well, it hopefully will make it's return to enwiki (T177017). As for the data you see above (logging of slow filters), there are hopeful plans to surface this within AbuseFilter, too (T176895) — MusikAnimal talk 02:50, 26 October 2017 (UTC)
* Sorry I missed the "test" part. That's a good idea, and probably feasible, since the current batch testing tool essentially does the same thing minus performance measuring. As a workaround, once per-filter profiling is back you could just put your filter in log-only and test it that way — MusikAnimal talk 02:56, 26 October 2017 (UTC)
Weird filter trigger
The filter log for this user shows a trigger that I haven't seen before - "CheckUser Sock block" with no filter number shown. Is this normal? Home Lander (talk) 21:55, 30 October 2017 (UTC)
* That filter is hidden, so the log won't tell you which filter number it hit, but that's the name of the filter. Sam Walton (talk) 22:22, 30 October 2017 (UTC)
* OK, should have figured as much. Is there any particular reason why that edit triggered the filter, or is that not publicly releasable either? (Just trying to determine whether triggering of that filter should generally be reported or not.) Home Lander (talk) 22:25, 30 October 2017 (UTC)
* That filter is being used by a specific admin/checkuser - who will already be monitoring it as needed. — xaosflux Talk 23:08, 30 October 2017 (UTC)
Filter 384 3
This filter seems to be catching a few false positives with words that contain the word bitch in them. Some songs and anime have it in their title. Can we add something like to permit false positives such as this and this? That should still disallow words like bitches. Nihlus 21:10, 27 October 2017 (UTC)
* We could just wrap it in \b and that would help. I should mention filters like this one will never be free of false positives. It is simply the nature of the disruption it is designed to prevent, where there will always some good-faith addition that would trigger it. E.g. many songs outright have the word "bitch" in them. I would first investigate how much vandalism resultantly would get through with this proposed change, and also note each clause to prevent false positives adds more complexity to the filter and its effect on runtime performance. I suspect many new editors are not surprised their edits containing profanity don't go through. Another thing to consider is showing a more informative warning that explains how to request the edit be made on their behalf — MusikAnimal talk 17:50, 30 October 2017 (UTC)
* That might be the preferred method. Perhaps we should guide them to make an edit request with a warning since, as you said, it should make sense to new editors that it would be filtered out. My only hesitation is that spammers would then just go to the talk page and make a mess there, but we can cross that bridge when we get to it. I can work on the message as I think that would be more productive (since more people watch the talk pages of the articles and are more likely to have familiarity with the topic). Nihlus 18:02, 30 October 2017 (UTC)
* See a drafted warning message at my sandbox. I would recommend MediaWiki:Abusefilter-profanity as the sensible choice for its location. However, I don't know if we should expand WP:EDITREQ to include an "edit filter" variant or if a simple request on the talk page would suffice. Nihlus 20:01, 30 October 2017 (UTC)
* MediaWiki:Abusefilter-warning-profanity, you mean, I think. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 18:25, 31 October 2017 (UTC)
874 changed and disallowing again
Pretty evident from the filter + comments as to why. I believe its a good temporary alternative, hopefully you can agree given the issues at hand. Pinging as the primary editor of the filter before I changed it -- There'sNoTime (to explain) 08:32, 1 November 2017 (UTC)
* I agree with that completely. Crow Caw 16:40, 1 November 2017 (UTC)
Disallowing CSD removal by article creator
I was wondering if 29 is a filter we can upgrade to Warn or possibly create an additional filter to go with it. I honestly think we should disallow CSD removals by the creator of the article since my recent experience has consisted of them edit warring and constantly removing it until they get blocked. I see that as more bite-y than something like a stern warning or just a Disallow that advises them of the proper avenue of disputing CSDs (pointing to the talk page). It will also save other users time so they don't have to play games with them by reverting and warning and reverting and warning etc. Nihlus 04:05, 11 November 2017 (UTC)
* It used to issue a warning, back in 2009. See the discussion at Wikipedia talk:Edit filter/Archive 2. The closer of that discussion was User:Xeno. I can see the argument for restoring the warning, at least as an experiment, because the filter gets 5-15 hits per day. EdJohnston (talk) 05:41, 11 November 2017 (UTC)
* Just for clarity, the filter in 2009 was disallowing all non-confirmed editors, not first contributor (wasn't possible). –<b style="font-family:verdana;color:#000">xeno</b><sup style="color:#000">talk 16:22, 12 November 2017 (UTC)
* Since the conclusion of that discussion, the edit filters tool has added article_first_contributor. It's been discussed since, see Edit_filter_noticeboard/Archive_2. – Train2104 (t • c) 13:17, 11 November 2017 (UTC)
* There's a bot (Cyberbot, I think) that restores the AfD templates, so this process is already automated. Even so, I don't see a problem with at least upping the filter to show a warning. We do however need to allow them to blank the page, as that would qualify as G7 — MusikAnimal talk 05:27, 12 November 2017 (UTC)
* Yeah, I'm not too worried about AfD, since as you said, a bot assists there. I would want, at minimum, a warning that directs them to the talk page. I really think we should create a new filter to disallow, but I would be satisfied with trialing a warning first to see if that makes any improvement. Nihlus 06:31, 12 November 2017 (UTC)
* I'd say a constructive warning with suitable advice is the only idea I'd support. A CSD tag can be added by anyone but not removed by the creator of the article, it's only suitable to let them have their IAR and taggers will more than often have the chance to point out when an article qualifies under CSD through AfD or otherwise. Either way, even if an article creator is proving to be disruptive (just wrt the CSD tags), I'd say the content is mostly salavageable (my personal experience). --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 14:17, 12 November 2017 (UTC)
Filter 384 4
Is intended to catch "Kilroy was here" and variants type of additions? Think we should streamline it — while the edit I'm referring to is not the pinnacle of what you can probably call a false positive, I was just thinking. --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 • 海 ) 08:25, 13 November 2017 (UTC)
Filter 225 and external links
We've had several recent false positive reports for Filter 225 hits (Vandalism in all caps), where the only ALL CAPS present was in the URLs of external pages. Is there any practical way to fix the filter in such a way that it will allow these URLs, but which won't allow users to get around the filter with plain text? עוד מישהו Od Mishehu 09:37, 14 November 2017 (UTC)
* Wouldn't be perfect, but maybe something like would reduce the false positives a bit. Κσυπ Cyp 11:03, 14 November 2017 (UTC)
Filter 885
Why is this filter public? Normally, filters that target specific sockpuppeteers and LTAs should be private per WP:BEANS. — MRD 2014 Talk • Edits • Help! 16:07, 14 November 2017 (UTC)
* Good question. Don't know why, but now it's not… Κσυπ Cyp 17:08, 14 November 2017 (UTC)
* Per BEANS, please email the main author of the filter (in this case, Special:AbuseFilter/history/885; in other cases, just replace the number - this page is visible to anyone authorized to see the filter) and leave a simple You've got mail message on their user talk page. עוד מישהו Od Mishehu 07:32, 15 November 2017 (UTC)
More per-filter statistics now available
We have re-enabled per-filter metrics (run-time and number of conditions) on English Wikipedia. Check it out as part of the Statistics on each filter's edit page. As a side-effect, the link to the recent actions graph has been moved to the subtitle above the Edit form. DMaza (talk) 20:06, 13 November 2017 (UTC)
* Ooooh, so that's what is causing the new Of the last x actions, this filter has matched 0 (0.00%). On average, its run time is 0.07 ms, and it consumes 1 condition of the condition limit. thing - awesome work! -- There'sNoTime (to explain) 10:20, 15 November 2017 (UTC)
Type casting
I thought I'd share a new revelation that I somehow overlooked all this time: You can do type casting! A prime example is when checking a set of namespaces. Currently in many filters, to reduce condition count we're doing something like (because we want to capture namespaces 1, 8 and 11, but not 118). Neat-o — MusikAnimal talk 06:51, 10 November 2017 (UTC)
* According to mw:Extension:AbuseFilter/Rules_format the data type of article_namespace is already integer, did you perhaps mean for your example? However, would return true, which is not what you want. Or have I misunderstood you, and you are saying that the function has an undocumented integer matching feature when all arguments are integers? —RP88 (talk) 17:47, 10 November 2017 (UTC)
* Testing with the debugging tools, (and too) returns 1, even though it might be more useful if it didn't. Κσυπ Cyp 18:42, 10 November 2017 (UTC)
* Aw shucks, actually yes I've got this wrong. What I think happens here is contains_any casts to an iterable (string in this case), so indeed my above example does not work. However we could do, or even cleaner — MusikAnimal talk 22:23, 11 November 2017 (UTC)
* While seems like a good idea, testing unfortunately evaluates to true. Κσυπ Cyp 17:08, 14 November 2017 (UTC)
* Okay so it just does't know how to handle arrays at all, even though it supports the syntax. I've created T181024. Feel free to edit if anything I said is wrong. Making arrays act like arrays will cause massive regressions, I think, but anyway to me that's how it should work — MusikAnimal talk 04:49, 21 November 2017 (UTC)
* The report seems fine. Testing, ⇒ false, ⇒ true, actually seems to work (but would break if array handling is fixed), but I think it's probably better just to fix it to handle arrays sanely. Κσυπ Cyp 07:19, 21 November 2017 (UTC)
* In all probability, they did it to reduce complexity but that just made handling it more difficult. :/ --<span style="font-family:'Trebuchet MS',Geneva,sans-serif"> QEDK ( 愛 ☃️ 海 ) 14:52, 30 November 2017 (UTC)
Filter 650 and disambiguation pages
I just triggered filter 650 by creating the Bachvarov disambiguation page. Could the filter be tweaked to ignore pages with disambiguation and more specific variants thereof, e.g. surname and geodis? I expect the point is to find pages that should get categories, not pages that need no categories other than what a template transcludes. Nyttend (talk) 01:31, 13 December 2017 (UTC)
How can we better surface performance data about AbuseFilter
Hello Edit filter managers;
Over the past few months the Anti-Harassment Tools team at the Wikimedia Foundation has added some additional forms of performance measurement to AbuseFilter to better understand the impact it is causing on users’ edits.
* We are measuring both runtime in milliseconds for the 75th and 99th percentiles on the AbuseFilter profiling Grafana dashboard.
* We are measuring the total count of conditions being hit and the number of filters hit on the AbuseFilter profiling Grafana dashboard.
* We are logging slow filters that take over 800 milliseconds on Logstash (which is unfortunately permissioned, but some EFMs have permissions to view.)
* We measured the impact of and determined the per-filter statistics do not cause a performance impact, so we’ve reenabled them on the filter parameters page. These statistics show the average runtime of each filter, but do not often show anomalously slow incidents, which is why we've added the Logstash logging.
Now that this data is being measured, I’d like to talk about how we can make it more easily available to you as you manage filters. We can make this minimally intrusive (e.g. just add links) or could make some more significant changes with your approval and permission. Here are a few ideas to start the discussion:
* Expand the “Of the last N actions…” sentence to include the average condition count.
* Add a “Statistics” section on Special:AbuseFilter and show all the existing statistics as well as new data from Grafana and Logstash.
* Display an icon by the slow filters on the All filters list
* On the Filter parameters page, indicate if the filter is taking over 700 milliseconds.
* …something else?
Would any of these be helpful to you? Or do you have any suggestions? We won’t make any changes without your consensus, but I want to make our team available if these changes (or similar) would be helpful.
Thank you! — Trevor Bolliger, WMF Product Manager (t) 21:52, 7 December 2017 (UTC)
* Trevor is already aware of my thoughts, but to share with others -- the things I'd like to see the most are bullets 3 and 4 (exposing slow filters in the interface). I have access to the logstash dashboard, so I've been working with some filter authors here to improve performance. The main issue obviously is they don't have logstash access and can't tell if the changes helped performance or not, since the "average" run time is still reasonably low. So basically on the filter parameters page, I'd like it to say something like "In the past hour, this filter took over 700ms to execute for N actions". That message would only show if N is greater than zero. Perhaps it'd also link to the Statistics page (bullet #2 above), that would list each individual action for which the filter took over 700ms to run. If it linked back to the Special:AbuseLog entry, we could then debug and find out why it took so long for that particular edit, etc. That'd be pretty amazing, but again for me the priority is just exposing which filters are frequently "slow", regardless of the average run time — MusikAnimal talk 22:14, 7 December 2017 (UTC)
* Random question about performance – if two filters use the exact same expensive subexpression, is the result from the first filter cached for the second filter? Κσυπ Cyp 06:17, 8 December 2017 (UTC)
* I don't believe so, because the most expensive subexpressions are evaluating long pieces of wikitext (e.g. the previous revision of a long page vs. the submitted revision.) These aren't cacheable. — Trevor Bolliger, WMF Product Manager (t) 19:53, 13 December 2017 (UTC)
Article age variable
Hi. On edit filters, is there some way to use the article's age as a variable? I'm not only talking about new page creation; suppose that for some reason, you wanted to restrict your filter to articles less than an hour (or 3,600 seconds) old. I don't see any such variable listed on the documentation page, but could there be a work-around of some sort? Just wondering. Thank you. Biblio (talk) 17:15, 27 December 2017 (UTC)
* There's an edit filter noticeboard that I would guess has the people to answer that question. --Izno (talk) 17:41, 27 December 2017 (UTC)
Hi. I was just wondering if there's some way to use an article's age as a variable. Suppose, for instance, that you wanted to restrict your filter to articles less than an hour (or 3,600 seconds) old, or to articles older than a month. The documentation page doesn't really address that, but is there some way to do this? Thank you. Biblio (talk) 18:54, 27 December 2017 (UTC)
* Sorry no, however if you wanted to hardcode it for a specific time you could hit most pages by examining the as it is an integer and newer pages get a higher number. — xaosflux Talk 19:45, 27 December 2017 (UTC)
* Eg pick a page made a month ago, then if the article id is less than it, it is older than that - unfortunately this is not dynamic, but you could use it to say include/exclude all pages made before 2017 for example (and could update the comparison value in the future to move it forward). — xaosflux Talk 19:53, 27 December 2017 (UTC)
Desysopping edit filter managers under a cloud
Following a January 2016 discussion, if the Arbitration Committee desysop an admin who has self-granted edit filter manager rights then the clerks will leave a note here (EFN) for review. I've just request that 'crats do the same if they desysop someone under a cloud who has self-granted the EFM permission. Comments about this request should probably be left at WP:BN rather than here.
The January 2016 discussion was not formally closed, but there was consensus against automatically removing the right from all desysopped admins, but a review did find favour explicitly and implicitly. I don't see a need to revist that, but if anyone else does then here or Wikipedia talk:Edit Filter is the place to do so (link from whichever venue you don't choose).
AFAICR no such review has yet needed to take place, Salvidrim! would have been the first had he not resigned his bit before the arbcom case with a passing desysop remedy closed. Following a discussion between him and xaosflux at user talk:Salvidrim! the EFM permission was replaced with EFH, negating the need for a review here. Thryduulf (talk) 12:29, 6 January 2018 (UTC)
Filter Descriptions in messages
A discussion is open at Wikipedia_talk:Edit_filter regarding the possible addition of filter names to the disallow warning (MediaWiki:Abusefilter-disallowed). — xaosflux Talk 01:00, 7 January 2018 (UTC)
|
WIKI
|
Sean McAloon
Sean McAloon (1923–1998) was a piper and pipe maker from Northern Ireland. Originally from the Rosslea area of County Fermanagh, McAloon's first instrument was the fiddle. However, he is best known as a master of the uilleann pipes. He emigrated to the United States in 1964, but after a year he returned to Ireland. He spent eight months working as a builder's labourer in Dublin, but moved to Belfast in 1966 to be closer to his family. There, he got a job working for the Corporation Parks Department.
His major inspirations as a piper were Phil Martin, whom he saw playing at a feis in Rosslea, and Leo Rowsome. In addition to being a fine player, McAloon eventually became a respected pipe repairer and a highly regarded reed-maker. He produced about twenty sets of the instrument in his lifetime. Desy McCabe from Craobh plays a McAloon half set
Discography
Various artists, "Ulster's Flowery Vale", B.B.C. Radio Enterprises REC28M, no date (a compilation of traditional songs and music originally broadcast on the Northern Ireland Home Service, July and August 1968)
* John Rea & Sean McAloon, Drops of Brandy, Topic 12TS287, 1976
* Various artists, Irish Traditional Music, Temple COMD2079, 2000 (compilation culled from three Topic releases, including 12TS287)
* Sean McAloon, Stor Piobaireachta (Piping from the Archives), Na Píobairí Uilleann, 2004
|
WIKI
|
Frequently Asked Questions - Water Quality
Is Fluoride added to MAWC water?
MAWC does not add fluoride to the water that is produced at our three (3) water treatment plants.
The water that MAWC receives from Greater Johnstown Water Authority to supply the Ligonier service area does contain fluoride.
Why does the water have a “chlorine” smell in the winter time?
MAWC adds chlorine to the drinking water to prevent water-borne disease outbreaks such as cholera, typhoid, giardiasis, etc. The chlorine must remain in the water for its entire journey to your spigot.
In the summertime MAWC combines ammonia with the chlorine to help carry the chlorine over the entire distribution system and reduce taste and odors caused by the warmer water. In the winter, MAWC eliminates the ammonia and adds only chlorine to the water. This chlorine eliminates any free ammonia in the system which left unchecked can cause bacterial growth. This “free” chlorine residual creates the off odors that you smell.
Is there anything I can do to eliminate the chlorine taste in my water?
Yes, place a pitcher of water in your refrigerator for cool, fresh water anytime. Chlorine will dissipate with time and the water will taste fresh. Reverse Osmosis and activated carbon filters are also effective in removing chlorine from water, but choose a reputable vendor and be sure to follow the manufacturer’s instructions for installation and maintenance.
Why does my drinking water sometimes look cloudy when first taken from a faucet and then clear up?
The cloudy water is caused by tiny air bubbles in the water similar to the gas bubbles in carbonated soft drinks. AFTER a while, the bubbles rise to the top and are gone. This type of cloudiness occurs more often in the winter because the colder water holds more dissolved air.
Air can be introduced into the water after pipe repairs or other service disruptions. Call customer service for a main line flush if air is excessive after a leak.
There is a “pink slime” in my shower. Is it from the water?
No, certain species of airborne bacteria gravitate towards and thrive in a moist environment, such as showers, toilet bowls, sink drains, tiles and dog dishes. These bacteria are naturally occurring and unattractive, but are generally harmless. The best way to avoid this problem is to keep the surfaces free from bacterial film through regular cleaning using Lysol or a chlorine-based product.
What are the black spots, rings or lines in toilets and shower stalls?
Mold and mildew grows in places that are continually damp and is treated the same as the pink slime.
|
ESSENTIALAI-STEM
|
Page:The Slave Struggle in America.djvu/27
Elijah P. Lovejoy was a native of Maine, who, in 1832, established a religious paper in St. Louis, in which he published such strictures on slavery as to raise a perfect outcry against him. In answer alike to entreaties and menaces he asserted his right to discuss the slave problem. "We have slaves, it is true," he said, "but I am not one." He affirmed the liberty of the press and refused to submit to dictation. The proprietors were frightened, and requested him to resign his editorship. The Observer, as the paper was called, fell into other hands as payment for a debt, and the new owner gave it to Mr. Lovejoy. Four years later a mulatto was in jail for fatally stabbing one man and wounding another who had arrested him. An infuriated mob broke into the prison, and, seizing the mulatto, carried him beyond the city, where they chained him to a tree and burned him. Judge Lawless, in charging the grand jury, said that if a mob were carried away by "mysterious, metaphysical, and almost electric frenzy" to deeds of violence and blood, the participators are absolved from guilt and not proper subjects for punishment. Lovejoy was not slow to comment on the judge's jesuitical justification of this atrocious deed. An angry crowd entered and destroyed Lovejoy's office. He removed his press to Alton, but it was seized on the banks of the river and broken into fragments. A number of citizens met and agreed to reimburse Lovejoy for his loss. He told them that it was a religious, and not an abolition, press that he wished to establish. Although an enemy to slavery, he was no Abolitionist; he was opposed to immediate emancipation. He would, however, hold himself at liberty to write and speak what he pleased on any subject.
St. Louis threatened Illinois with loss of the trade of the Slave States unless she could find some means of staying Lovejoy's pen. His office and press were again destroyed. Another press was purchased, this too was seized by a furious mob, and thrown in fragments into the Mississippi. Lovejoy was mobbed and insulted. To quote his own words, he was "hunted up and down like a partridge on a mountain." He was "threatened with the tar-barrel," "waylaid every day." His life was "in jeopardy every hour." It was demanded that he should leave Alton. To this, after a moving allusion to his sick wife kept in "continued alarm and excitement," and, "driven night after night from her sick-bed into the garret to save her life from brickbats and the violence of the mob," he replied: "I know you can tar and feather me, hang me up, or put me in the Mississippi. But what then? Where shall I go? I have been made to feel that if I am not safe in Alton I am not safe anywhere." No, he would not leave. "If I die I am determined to make my grave in Alton." The city was intensely excited—vile epithets, fierce invective, and abuse of all kinds were freely indulged in, and the arrival of another press was a signal for turning violent words into
|
WIKI
|
Page:Once a Week Volume V.djvu/332
. 14, 1861.] by some considered anterior to even Merlin, that “he who spends a night in the chair or Cader Idris will be found mad, dead, or a poet.” Tradition relates that Merlin sat there, and that Taliesin also went through the dread ordeal that touched his lips with the fire of prophecy.
“You know,” broke in young Herbert Griffith, “the gap cut in the live rock, on the high peak where the cairn is, just above the cliff? It looks like the throne of some queer old king. I showed it to you when we went shooting dotterils. Beg your pardon, Ellen!”
Ellen went on to relate how, long ago, in the thirteenth century, the lady of the manor, a beautiful and wilful heiress, called by her vassals the Lady of Cader Idris, had resolved to undergo this terrible trial in the hopes of becoming imbued with the spirit of poetry. How, being a lady of rare courage and headstrong will, she had persisted in her resolve, in spite of the entreaties of her kindred, the prayers of her tenants, and the authority of her confessor. How she had gone up alone to the haunted hill-top, where, as legends tell, spectres keep a world-long watch over buried treasure, and had faced storm, and darkness, and all the terrors of the visible and the viewless. Finally, how she had been found in the morning, stark and dead, seated in the rocky throne on blue Idris, with her long dark hair floating over the stones as she sate in an attitude that mocked life, and with an expression of awful fear stamped on her open eyes and fair pale face. The tradition added that, on account of her rebellion against the priest’s commands, the pitiless church had denied her poor body Christian burial, and that she had been laid, in silence and stealth, by the hands of sorrowing kinsmen, under a cairn of loose pebbles on the hill-top.
Then Ellen went to her harp, and sang us first the wild Welsh ditty that some bard had composed in elder days, and then the polished verses which Mrs. Hemans had penned on the same theme. Nor was it till the last notes of the harp and the sweet voice had long died away that we recovered from the impression of the weird and mournful tale, and began to question its authenticity and to challenge its probability. I remember we all took part, in a sportive way, against Ellen and the legend. Our wish was, no doubt, to tease, harmlessly, the darling and spoiled child of the household, and also perhaps to atone to ourselves for having been for a time more completely under the spell of romance than we cared to acknowledge. But to start a discussion is like rolling a stone down-hill. It starts gently, sliding down grassy banks and springing daintily from mound to mound, then leaps with huge bounds, gaining force every instant, till it thunders from crag to crag, and crashes into the valley below. Our controversy grew warm and lively, almost bitter. Ellen was piqued and ruffled. She had told us one of her favourite tales, one which she had loved and dwelt upon, and which was grown to be almost a part of herself, and we had listened—and laughed. She had not the experience that riper years impart, and which would have made her suspect that our derision was in a measure defensive and over-strained, and she was vexed, and showed it. She was quite angry with her jeering brothers, but I came in for the full weight of her indignation.
“Why was I incredulous? Did I think woman’s nature so frivolous and cowardly that nothing brave or self-devoted could be looked for from a woman?”
To this I replied, with provoking gravity, “That I thought the story a pretty one, but that it was as improbable as the adventures of King Arthur and his knights, and that I never saw or heard of any female capable of confronting so much risk and discomfort.” Finally, I declared the “Lady of Cader Idris” a pure invention of some crack-brained harper. Ellen’s scornful eyes flashed, and she tossed her golden ringlets as she turned away. All might have gone well had not some mischievous fiend whispered to me to improve my victory. So I did. I waxed very witty and satirical, and the company applauded, all but the squire, who was asleep, and Ellen, who stamped her little foot angrily on the floor, exclaiming:
“I will show you that a woman dares do more than you fancy. I will go through this ordeal, that you believe impossible. We shall see who is right, you or I.”
And she left the room at once. When she came back, half an hour later, she was quite calm and unruffled: she joined in the conversation as usual, and spoke pleasantly of the projects for pike fishing in the Llyn, for a late pic-nic to some celebrated point of view, and a ride to the county town. But there was a feverish restlessness in her air, and she broke off rapidly from talking on one subject to diverge to another. She sat down, when asked, to harp or piano, but she played but a few bars, and then rose again, saying she could not remember a tune. This change of manner caused me some concern, and I went up to her, and said in a low tone:
“Ellen, are you ill?”
“Ill? No,” she answered, in an abstracted manner, and moved away.
“You are not offended with me?” I began. “I did not mean—”
“No, I am not offended,” she answered, with some constraint, and then began to take the keenest interest in the artificial flies Herbert was tying.
We exchanged no other word until every one had retired to rest, and it came to my turn to wish her “Good night,” as usual. She took my hand between her own little white fingers, and for a moment gazed in my face with a strange look that has haunted me ever since—that will haunt me to my dying hour. Sorrow, reproach, affection, and an under-current of firm but hidden determination, were blended in that glance,—the last that I ever received from those fond blue eyes that I had hoped would be a sunshine in my home from youth till age. And her lips murmured the old trivial phrase, “Good night,” as if it had a new meaning. She turned away.
“Ellen!” said I, springing after her, “one moment, Ellen!”
She did not seem to hear. She glided from me, and was gone. One moment I stood irresolute.
|
WIKI
|
Dallas Smith
Dallas Hendry Smith (born December 4, 1977) is a Canadian singer and songwriter, who performs both as a solo country music artist and as lead singer for the hard rock band Default. He is currently signed to Big Loud Records. Smith is the current record holder of most number one hits among all male Canadian artists on Billboard's Canada Country chart, at eleven. With Side Effects, Smith also became the first Canadian country artist in the Nielsen BDS era to chart four consecutive number one singles from one album (Shania Twain charted three consecutive number one hits from her 1997 release Come On Over), a feat he would then top with his next album, Timeless.
At the end of 2012, Mediabase named Smith the most played Canadian country act and number eight overall at the format.
Early career
Dallas Smith always had a passion for music growing up. Some of his main influences were The Beatles and female country singers Reba McEntire and The Judds. Due to his shyness, Smith was reluctant to express his musical talent until he made the decision to face his fear and play cover songs with a band consisting of some of his friends. He signed his first record deal when he was 21.
1999–2009: Default
Before his solo career, Smith was the lead singer of multi-platinum band Default, a Canadian hard rock/post-grunge band from Vancouver, British Columbia. Formed in 1999, it continued until 2013. Default's debut 2001 album, The Fallout, achieved instant success due to strong radio play of "Wasting My Time" and "Deny". In 2002 Default won the Juno Award for "Best New Group". On April 30, 2003, the record achieved a platinum album RIAA certification, signifying a million records sold. The band also released the album Elocation (2003) which was certified gold, One Thing Remains (2005) and Comes and Goes (2009).
2011–2012: Jumped Right In and Boys of Fall Tour
Jumped Right In was released on May 22, 2012, via 604 Records under the production of Joey Moi. The album features tracks written by Smith along with Moi, Rodney Clawson, Craig Wiseman, Dustin Lynch, Chris Tompkins, Zac Maloy, Chad Kroeger and more. It peaked at number 19 on the Canadian Albums Chart and has generated five charted singles on the Canadian Hot 100. The album was nominated for Country Album of the Year at the 2013 Juno Awards and was also nominated as Album of the Year for the 2013 Canadian Country Music Association Awards. The album has sold over 100,000 digital singles to date.
In November 2012, Smith performed on his first solo tour, co-headlining with Chad Brownlee. The tour was billed as the Boys of Fall Tour and traveled across Canada, hitting 22 cities. The tour sold out on 20 of its dates, including the Commodore Theatre in Vancouver. Smith performed at many Canadian country festivals through 2012 and 2013. In March 2013, Smith went on a sold-out Canadian tour with Bob Seger.
Stemming from the success of the Boys of Fall Tour, Smith and Brownlee teamed up to create the annual Boys of Fall Charity Golf Tournament and Concert. The tournament took place at the Redwoods Golf Course in Langley, British Columbia on August 27, 2013, and was sponsored by the radio station JRfm. Proceeds from the event were donated to Basics for Babies, an organization that assists families coping with the challenges of raising a young infant by providing them with needed food, formula, and diapers. The tourney's fifth year took place on Tuesday, August 22, 2017.
2013: Tippin' Point EP
In October 2013, Smith signed with Republic Nashville and released his first American single, "Tippin' Point". It was written by Brian Kelley and Tyler Hubbard of Florida Georgia Line with Jaren Johnston. In 2013, Smith was nominated for Male Artist of the Year, Single of the Year and Album of the Year by the Canadian Country Music Association. Smith performed on the CCMA broadcast award ceremony, which took place on September 8, 2013.
Smith released an extended play, Tippin' Point, on March 4, 2014, in the US and Canada. Three singles have been released from the EP so far. The title track was a top 5 single on the Canadian country radio chart and was pronounced the fastest country single to be Gold certified by Music Canada. Since then, the single has been certified Platinum in Canada and the "Tippin' Point" video was ranked number 1 on CMT Canada. In the US, the song "Tippin' Point" was ranked number 1 on Sirius XM's The Highway Hot 45 Countdown and has sold over 120,000 singles. Smith followed up the success of the first single by releasing "Slow Rollin'" in March 2014. The track was a top 5 single at Canadian country radio. A third single, "A Girl Like You", was released in June 2014.
Smith's single "Slow Rollin'" is performed by Lady Antebellum on the deluxe edition of their album 747.
2014–2017: Lifted and Side Effects
In 2014, Smith entered a recording studio in Nashville to record his second full-length studio album with producer Joey Moi. The album, Lifted, was released on November 25, 2014. Smith released the first single off the album, "Wastin' Gas", on October 28, 2014, followed by album's lead track "Lifted" and finally "Cheap Seats". "Wastin' Gas" became Smith's first #1 Canada Country hit, as well as his first charting entry on the Billboard Country Digital Songs and Country Indicator airplay charts in the United States.
In 2016, Smith released his third solo album Side Effects. The singles released from the album included "Kids with Cars", "One Little Kiss", "Autograph", lead title track "Side Effects" and "Sky Stays This Blue". In September 2016, Smith also joined Keith Urban for the Canadian leg of his Ripcord World Tour.
2018–2020: The Fall EP and Timeless
In March 2019, Smith released his EP The Fall. The EP featured four straight #1 singles, "Make 'Em Like You", "Rhinestone World", "Drop", and "Timeless". Smith co-headlined the Friends Don't Let Friends Tour Alone Tour with Dean Brody across Canada in the Fall of 2020.
In July 2020, a Nielsen Music study found Smith to be the sixth-highest played Canadian artist on domestic radio in the first half of 2020, ahead of Drake and Chad Brownlee, and slightly behind Virginia to Vegas and Justin Bieber.
Smith's fourth studio album, Timeless was released on August 28, 2020, and contains all previously released material from The Fall, as well as the singles, "Like a Man" and "Some Things Never Change". In November 2020, Smith released his first Christmas single "Classic".
2021–present: Self-titled album and Some Things Never Change Tour
In August 2021, Smith signed a global recording deal with Big Loud Records. Along with Big Loud, and producer Scott Cooke, Smith launched the joint venture Local Hay Records which signed Shawn Austin as their flagship artist. In September 2021, Smith hosted and headlined the "Lifted Hotel Festival" in Vancouver, British Columbia, with all proceeds from the event going towards his organization, the Lifted Dallas Smith Charitable Foundation which supports mental health. Other featured performers included Austin, Jojo Mason, Andrew Hyatt, and Kelly Prescott. In November 2021, Smith announced his headlining Some Things Never Change Tour, which ran in early 2022 and included James Barker Band, Meghan Patrick, Jojo Mason, and Shawn Austin among the opening acts.
Smith released "Hide from a Broken Heart" as his first global single on Big Loud on November 29, 2021. Smith debuted the song at the 2021 Canadian Country Music Awards that day, where he won Entertainer of the Year, Male Artist of the Year, Single of the Year for "Like a Man", and best selling Canadian album for Timeless. He then featured on the Josh Ramsay single "Best of Me" in February 2022. In June 2022, Smith released the single "One Too" with fellow Canadian country singer MacKenzie Porter. He was subsequently named Male Artist of the Year and won the Fans' Choice at the 2022 Canadian Country Music Awards. In January 2023, Smith released the single "Singing in a Beer". The song was included on his self-titled fifth studio album Dallas Smith, which was released on October 27, 2023. Smith released two instant gratification tracks "Fixer Upper" and "CRZY" alongside the opening of pre-orders for his self-titled album. The album's first track, "Use Me", became its fifth single to Canadian country radio, and was released to radio formats in Australia and the United Kingdom as well.
In October 2023, it was announced that Smith will take his first acting role, appearing alongside Allan Hawco and Charlie Gillespie in Soul's Road, the forthcoming debut film of music video director Joel Stewart.
Personal life
Smith married his longtime girlfriend Kristen in 2012 and the couple has two daughters together. He also has a son from a previous marriage.
Discography
* Jumped Right In (2012)
* Lifted (2014)
* Side Effects (2016)
* Timeless (2020)
* Dallas Smith (2023)
|
WIKI
|
Talk:War of Northern Aggression
Argument over usage of term
To <IP_ADDRESS> and <IP_ADDRESS>: If you feel like arguing over the article's wording, please debate it out here on the talk page before editing the article itself. Do not update the article until you two have sorted out your differences and can agree on a clear, NPOV, and informative version. Thanks. -Mysterius 21:56, 1 May 2007 (UTC)
|
WIKI
|
User:Kkeebone
hello
I'"m Kaone Keebone, a qualified librarian from Botswana University of Agriculture and Natural aresources.
|
WIKI
|
Thomas Thompson (businessman)
Thomas Thompson (c. 1797 – 1869) was an American businessman and art collector, who also set up one of the oldest charitable foundations in the United States.
Background
Thomas Thompson was born in about 1797 in Boston, Massachusetts.
MThompsons father, who was also named Thomas Thompson, originally came from Nantucket and was of a quaker family. The family was wealthy. In a Boston pamphlet published in 1846 entitled Our First Men, which lists the names of the most prominent and wealthiest people of the city, one can find the Thompson family.
Thompson was sent to Harvard University in 1817, and was the classmate of George Barrell Emerson, Caleb Cushing, and George Bancroft. He was an honors student, and already from a young age interested in art and nature.
Art collection
Thompson started collecting art early, and the first inventory of his collection is dated 1844. Unfortunately, most of his art collection was stored at the Tremont Temple in Boston, which was divested in a fire in March 1852. Thompson writes on April 5, 1852, to the secretary of the city's Board of Engineers;
''At your request I transmit a statement of my loss by the late fire in the Tremont Temple. I have been twenty years making the collection recently deposited there. My estimate of the loss – that is, the lowest cost – $92,456 on the pictures, although I do not think that they could be replaced to-morrow for a hundred and fifty thousand.''
However, Thompson almost immediately started building up a new collection, and it was said that his aim was to gift his collection to the city of Boston. However, Thompson moved from Boston to New York, and the gift to Boston was never materialized. Instead, the collection was sold of after his death at an auction witch started in New York on February 7, 1870. The sale was organized by his estate, and conducted by Thompson's brother-in-law, George Presbury Rowell, who also served as the estate executor to his sister, Thompson's widow, Elizabeth Rowell Thompson.
All lots in the sale was marked on the back with:
''Thompson Collection / New York – 1870 / Geo. P. Rowell.''
Gallery
These pictures was among them sold from Mr. Thompsons collection in New York in 1870.
The Thomas Thompson Trust
Thompsons will was set up in 1857 and it stipulates how his charitable trust would be set up. His wife, Elizabeth, survived him by more than 30 years and soon after the turn of the 20th Century, his trustees began making grants and have continued to do so for over a hundred year. The instruction to the trustees, made by Thompson simply states that;
''apply the net income of the trust fund... for or towards the relief and support, of poor seamstresses, needle-women and shop girls, who may be in temporary need from want of employment, sickness or misfortune, in the towns of Brattleboro, Vermont, and Rhinebeck, Duchess County, New York.''
It also stated that:
And I empower my said trustees...to apply surplus to such kindred charitable purposes in said towns or elsewhere, but not however in the City of Boston, as shall be determined by my said Trustees.
|
WIKI
|
Usage of private repo in build.zig.zon
Question is it possible to reference a private repo in the build.zig.zon file?
Currently I am getting 404 unless I make the repo public.
I am using the latest build of zig.
No, at least not at the moment.
1 Like
Maybe a bit late and not with perfect solutions, but you can try with:
• a git submodule (or a simple project subfolder) and add the library in build.zig.zon:
.dependencies = .{
.ztester = .{
.path = "external/private_repo",
},
},
• or, make a local archive with your code and:
.dependencies = .{
.ztester = .{
.url = "file:///home/some_path/project/archives/private_repo.tar.gz",
.hash = "some_hash",
},
},
• or, make an archive, store it in your email drive and:
.dependencies = .{
.ztester = .{
.url = "https:///some_path/archives/private_repo.tar.gz",
.hash = "some_hash",
},
},
More or less these are “testing” solutions, not very suitable for production.
|
ESSENTIALAI-STEM
|
(195e) The Effects of Ionic Liquid Structure on the Thermodynamics of Cellulose Dissolution | AIChE
(195e) The Effects of Ionic Liquid Structure on the Thermodynamics of Cellulose Dissolution
Authors
Rabideau, B. D. - Presenter, RWTH Aachen University
Ismail, A. E., RWTH Aachen University
A big challenge in the production of lignocellulosic biofuels lies in the selection of an optimal pretreatment solvent. A number of ionic liquids (ILs) have been identified that can dissolve cellulose effectively and many more are theoretically possible. Tailoring these solvents has the potential to increase performance and reduce costs, however without a much deeper understanding of the structure-property relationships within ILs this remains a difficult task. Using molecular dynamics we systematically examine the effect of chemical structure on the free energy of dissolution of crystalline bundles of cellulose. We focus on 15 different ionic liquid combinations and calculate the thermodynamic differences between the crystalline and dissolved states. Anions of 3 different sizes are paired with 5 different imidazolium-based cations with differing tail length. Entropies are calculated using the two-phase thermodynamic (2PT) method, allowing us to identify each of the contributions arising from the anion, the cation and cellulose as well as their translational, rotational and vibrational contributions. In doing so we show how changes to the chemical structure affects the overall energy and enthalpy as well as quantify the role that solvent entropy plays in the dissolution process. The free energy differences obtained from the simulations agree well with experimental solubility measurements and we show how these methods can be used to accurately predict solubilities a priori.
Topics
|
ESSENTIALAI-STEM
|
Talk:Solarplicity
Toto
There is a new company, Toto, taking over TudorTulok (talk) 12:56, 30 July 2019 (UTC)
* The article was updated accordingly. --Wire723 (talk) 15:27, 30 July 2019 (UTC)
* Thank you Wire723 TudorTulok (talk) 09:54, 31 July 2019 (UTC)
Useful Documents
* Notice of reason
* Ofgem ban energy supplier Solarplicity from taking on new customers for three months
* Energy firm Solarplicity banned from taking on new customers
* 'I drove to Solarplicity, and I'd do it again' - Customer hits road in bill row
* Working at Solarplicity on Glassdoor
* Working at Solarplicity on Indeed
* Confirmed Provisional Order - Solarplicity Supply Limited - 8 August 2019
-- TudorTulok (talk) 10:06, 31 July 2019 (UTC)
Dr Bob Middleton & David Elbourne
Should Bob Middleton & David Elbourne have their own pages, in order to protect future companies and future clients for not being informed about their business practices.
David Elbourne had a twitter account.
Links
* David Stuart ELBOURNE on Companies House
TudorTulok (talk) 08:46, 2 August 2019 (UTC)
Elbourne blames Ofgem
In this article Solarplicity energy supply business collapses amid Ofgem row. Elbourne blames Ofgem, but their system was lazy and in trouble already in 2017. Poor customer service started years ago, not in 2019.
Than you. TudorTulok (talk) 08:38, 15 August 2019 (UTC)
Advice to customers
From here
''Solarplicity Supply Limited is ceasing to trade and Ofgem, the energy regulator, will appoint a new supplier to look after its customers.
''Ofgem’s advice to our customers is not to switch, but to sit tight and wait until it appoints a new supplier for you. This will help make sure that the process of handing customers over to a new supplier, and honouring credit balances, is as hassle free as possible for customers.
''You can find support and advice on the Ofgem website. Alternatively, if you need additional support, you can call Citizens Advice on 03454 04 05 06 or email them via their webform. Advice will also be shared through Ofgem’s Twitter @ofgem and Facebook channels. If you are a business customer, then please read Ofgem’s business consumers guide.
''link for domestic customers https://www.ofgem.gov.uk/ofgem-safety-net
''link for business customers https://www.ofgem.gov.uk/ofgem-safety-net-business
''All of our remaining customer supplies are secure and any domestic credit balances on these accounts will be protected. Ofgem will shortly appoint a new supplier to look after you.
''The rest of the Solarplicity Group is not affected and will continue to do what it has always done best – provide innovative Renewable Technology to cut the cost of energy for Local Authority and Housing Association tenants. We will update you about our future plans in the coming days.
''Solarplicity deeply regrets the impact that this decision will have on its remaining customers that did not transfer to TOTO, and its loyal suppliers. The large number of small energy suppliers and the harsh way the market is regulated make it difficult for companies like Solarplicity to survive. Ofgem’s recent actions stopped it from raising the funding it needed, unfortunately leaving it no option but to cease trading.
Customers that transferred to TOTO in the last two weeks – including all those on our Community Energy Scheme in Stoke are not affected.
TudorTulok (talk) 08:02, 16 August 2019 (UTC)
No acces to the accounts on 8/16/2019
The page that was supposed to login is down on 8/16/2019. No message on their website why is the page down, no email for the reason. The company is diving into a mistake-after-mistake whirlpool, without informing people in time.
TudorTulok (talk) 09:51, 16 August 2019 (UTC)
Credit balances for past and current customers will be honoured by EDF energy.
* This guide gives more information: Solarplicity customers: Your questions on new supplier EDF
* more news from EDF
TudorTulok (talk) 08:14, 17 August 2019 (UTC)
BBC articles
* Article 1
* Article 2
* Article 3
TudorTulok (talk) 14:55, 20 August 2019 (UTC)
Solarplicity collapse: advice for customers and update on complaints from Ombudsman
Solarplicity collapse: advice for customers and update on complaints (UPDATED) TudorTulok (talk) 14:41, 29 August 2019 (UTC)
|
WIKI
|
Dirhash
Dirhash is a feature of FreeBSD that improves the speed of finding files in a directory. Rather than finding a file in a directory using a linear search algorithm, FreeBSD uses a hash table. The feature is backwards-compatible because the hash table is built in memory when the directory is accessed, and it does not affect the on-disk format of the filesystem, in contrast to systems such as Htree. Free space for new entries is also tracked in-memory, allowing addition of new entries without having to scan the directory.
Dirhash was implemented by Ian Dowse early in 2001 as an addition to UFS, operating in parallel with higher-level file system caching. It was imported into FreeBSD in July 2001. It was subsequently imported into OpenBSD in December 2003 and NetBSD in January 2005.
|
WIKI
|
Treasury chief says any ZTE penalty changes won't hurt security
WASHINGTON (Reuters) - U.S. Treasury Secretary Steven Mnuchin said on Tuesday that any changes to stiff Commerce Department penalties on Chinese telecommunications equipment maker ZTE Corp will ensure that U.S. national security is maintained and sanctions are enforced. Mnuchin, testifying before a U.S. Senate Appropriations subcommittee, said that any consideration of changes for ZTE “was not a quid-pro-quo or anything else” related to trade. “I can assure you that whatever the Commerce Department decides, the intel community has been part of the briefings and we will make sure that we will enforce national security issues,” Mnuchin said. “If there are any proposed changes on ZTE, the objective was not to put ZTE out of business, the objective was to make sure that they abide by our sanctions programs.” Reporting by David Lawder and Lindsay Dunsmuir; Editing by Chizu Nomiyama
|
NEWS-MULTISOURCE
|
Homonoia riparia
Homonoia riparia, the willow-leaved water croton, a mangrove species, belongs to the family Euphorbiaceae. The plant is widely distributed through South Asian and South East Asian countries such as Cambodia, China, Indonesia, Laos, Papua New Guinea, Philippines, Sri Lanka, Taiwan, Thailand and Vietnam. It is grown in wet soil near river banks and flooded plains.
Description
* Bark - brownish
* Leaves - simple, and alternate
* Flowers - wind pollinated monoecious flowers and bracts sub-ovate
* Height - 1–3-metre-tall evergreen shrub
* Ecology - A rheophyte
* Uses - medicine
Common names
The names are according to Asian Plant.net and Indian Flowers
* Borneo - Bongai tidong, Parang-parang
* Burma - Kyauk(a)naga, Momaka, Nyin ye bin.
* Cambodia - Rey tuck.
* China - Shui liu, shui yeung mui.
* English - Willow-Leaved Water Croton.
* India
* Hindi - Sherni (शेरनी)
* Marathi - Raan kaner (रान कणेर)
* Tamil - Kattalari (காட்டலரி)
* Malayalam - Neervanchi, Puzhavanchi
* Telugu - Adavi ganneru (అడవి గన్నేరు)
* Kannada - Hole nage, Niru kanigalu (ಹೊಳೆ ನಗೆ)
* Sanskrit - Kshudrapashanabheda (क्षुद्रपाषाणभेद)
* Java - Kajoe soebah, Keding djati, Soebah/Sobah,
* Laos - Kek khay.
* Philippines - Agooi, Agoioi, Agukuk,
* Thailand - K(l)ai nam, Klai hin, Mai kerai, (Ta)kri nam.
* Sri Lanka - Omi (ඕමි), Werawala (වැරවල)
* Sumatra - Sangka, Sangkir
* Vietnam - Cây rù rì nước, Rì rì, Rù rì.
|
WIKI
|
File talk:Ruins of a burnt apartment building in Gori.jpg
Request for deletion
The picture would receive RFD tag unless it has any working links to both the source, with the copyright ibnformation, and the source of the text with claims of 16 killed. It is now used itself in 2009 south ossetia war as a source for 16 killed, but where does this information comes from? FeelSunny (talk) 07:34, 7 May 2009 (UTC)
|
WIKI
|
Solutions by Industry
The LoRa Protocol
Overview
LoRa is short for “Long Range”. LoRa modulation scheme is a modulation technique combined with a data encoding technique that gives a broad-band spread-spectrum radio the receive sensitivity of a very narrow-band long range radio. Many people are not looking into what is LoRa, and this document describes LoRa and the advantages the LoRa technology has brought to the communication world.
LoRa techniques give LoRa receivers unprecedented sensitivity levels. LoRa radio modems can receive signals 10 times weaker than most radios.
When a receiver’s sensitivity is increased by 10 times, that is the same communication range improvement as increasing the transmitter power 10 times. But with LoRa you get the great range improvements without any increase in power consumption or transmitter power. And most license-free bands restrict transmit power, so LoRa is the best way to increase the communication range of a wireless data link.
Raveon is one of the many early implementers of the LoRa technology in the USA, and one of the first to get a full-power LoRa device FCC certified. LoRa is a radio modulation technique and protocol that enables a device to have an unprecedented long-range. See our LoRa products at www.iot.raveon.com
Forward Error Correction
FEC is commonly used to increase a receiver’s sensitivity by reducing the bit-error rate of the system. LoRa radios have integrated FEC into the protocol. FEC effectively increases the energy per bit and enables the device to correct for bit errors. By adding extra overhead bits to groups of bits being transmitted, the data throughput gets reduces but the bit-error-rate is lower with weak signals, increasing the sensitivity of the receiver.
Interference Immunity
There are a number of different types of interference all wireless systems must deal with:
1. Co-channel interference. This is where there is some other transmitter on the exact same frequency that the system is currently utilizing. Many RF systems stop working if the interference is even 10dB weaker than the signal being received. With LoRa, the interference can be as much as 19dB larger than the signal being received and the receiver will still get the signal. This means LoRa systems will keep working reliably as the frequency channels get crowded.
2. Blocking Rejection. Sometimes a system needs to operate in a location where there is a powerful interfering signal nearby. For example, in the USA the 906-924MHz ISM band that LoRa uses is only 50mHz away from the 800MHz radio bands where powerful narrow-band transmitters emit 100watts, or 2watt cellular 869-894MHz transmitters. Even though LoRa is 10 time more sensitive, it is even 20 X less susceptible to overload from these powerful out of band signals.
Link Margin Comparison
When one compares a LoRa radio system to a traditional UHF or VHF radio modem, we see that the communication range for LoRa is very similar to VHF and UHF, but it achieves this with much less RF power. The spreadsheet calculations below show the theoretical link margin for LoRa 900MHz compared to VHF and UHF radio systems.
LoRa 200mW LoRa 10mW UHF 2W VHF2W
Operating Frequency (MHz) 915 915 460 160
Transmitter Output Power 23 dBm 10 dBm 33 dBm 33 dBm
Link Distance, km 180 km 40 km 150 km 450 km
Link Distance, miles 111 mi 24 mi 93 mi 279 mi
Transmit Antenna Gain (dBi) 5 5 3 3
Antenna feed loss (both ends) 1 dB 1 dB 1 dB 1 dB
Receive Antenna Gain (dBi) 5 5 3 3
Receiver Sensitivity -128dBm -128dBm -115dBm -115dBm
System Gain (dB) 151 138 148 148
Link Fade Margin (dB) 22.2 22.3 22.8 22.4
Link Path Loss (dB) -136.8 -123.7 -129.2 -129.6
Effective Radiated Power 27 14 35 35
The theoretical calculations show that a 200mW LoRa radio will work about as long-range as a 2watt UHF radio. A 2watt VHF will work a bit longer range but it is using 2 watts. Raveon’s field tests support these theoretical calculations. We’ve seen VHF and UHF reliably go 50-100 miles line of site, and LoRa can easily go 20-50 miles (at 1/10th the power consumption).
Although, building, forest, and foliage penetration is much better with VHF and UHF radio technology, so 900MHz systems will typically require taller antennas at the base stations and more base stations to get good coverage. This is offset by the cost and power of LoRa radios being so much lower than traditional VHF and UHF systems so building out large area networks with LoRa is a very good approach.
LoRa Modulation
The over-the-air modulation method that LoRa uses is a type of Direct Sequence Spread Spectrum (DSSS) they call Chirp Spread Spectrum (CSS). Each bit is spread by a chipping factor. The number of chips per bit is called the spread factor. Lora also sweeps the modulation across the channel, so that the occupied bandwidth of the transmitted signal matches the choose bandwidth.
The larger the spreading factor, the slower the over-the-air data rate. And as mentioned before, the slower the data rate, the better the receiver sensitivity and the longer the potential communication range. For an example, here is how a spreading factor of 7 affects the bits sent over the air.
CHipPatterns
Typically, a LoRa radio uses 125kHz, 250kHz, or 500kHz radio channels.Below is a table showing the over-the-air data rates at the various commons spreading factors LoRa uses on these three channel bandwidths.
LoRa Over the Air (OtA) Baud Rates
The OtA data rates listed below are in kilobits per second. This table assumes the LoRa coding chip rate is set to 1.
Spreading Factor 125kHz B.W. 250 kHz B.W. 500 kHz B.W.
5 15.625 31.25 62.5
6 9.375 18.75 37.5
7 5.46875 10.9375 21.875
8 3.125 6.25 12.5
9 1.757813 3.515625 7.03125
10 0.976563 1.953125 3.90625
11 0.537109 1.074219 2.148438
12 0.292969 0.585938 1.171875
LoRa RF Power Output
In the USA, LoRa systems typically use a combination frequency hopping and direct sequence modes, to keep in compliance with FCC requirements. A hybrid system can use some 125kHz channels and one direct sequence as long as the power limits and dwell limits of the regulations are met.
Hybrid
To keep the transmit power level in compliance with the PSD limits, a 125kHz channel has 41 3kHz windows, so the max power is 41 X 6.3mW = 258mW (24dBm). If 500kHz channels are used, then the transmit power can be 4X that (1watt) on the 500kHz channel. To account for modulation peaks and some bandwidth margins, typical LoRa power levels are about ½ the theoretical limit which will ensure regulatory compliance.
Multi-Channel
Raveon’s LoRa base stations utilize LoRa chips that have the ability to receive 8 channels all at the same time. No other long-range wireless technology has this multi-channel receiver capability.
By having the ability to receive 8 channels, 8 wireless nodes can report in at the same time, and as long as they are on different RF channels, the base station can receive them.
LoRaWAN Frequencies
The LoRaWAN protocol specifies that certain frequencies in certain countries shall be supported by every device. These are listed as:
• EU 868.1, 868.3, and 868.5 MHz
• EU 433.175, 433.375 and 433.575 MHz
• China 779.5, 779.7 and 779.9 MHz.
• North America US 902-928MHz.
Be sure to visit the Raveon Blog for more information.
Filed under: Uncategorized | Posted on August 15th, 2016 by John Sonnenberg
Leave a Reply
You must be logged in to post a comment.
|
ESSENTIALAI-STEM
|
User:Hartboy
New articles in progress
* /List of Copyright Agency
* /Arnstein v. Porter
* /Copyright
* /sandbox
* /Notability (proposed legislation)
* /Arthur Fisher
|
WIKI
|
Efficacy of six-week extended-dose nevirapine varies by infant birth weight with greatest relative efficacy in low birth weight infants
Post Date:
2016-09-30
|
Countries:
|
Clinical Sites:
Publication:
PLOS One
Summary:
Low birth weight (LBW), defined by the World Health Organization (WHO) as birth weight less than 2500 g, is a significant public health issue in resource-limited settings, particularly in Sub Saharan Africa and South Asia where the estimated annual incidence is 14% and 28–31%, respectively, and the HIV burden among women of reproductive age is high [1,2]. Maternal HIV infection is an independent risk factor for LBW [3,4], and LBW infants of HIV-infected women are at increased risk for mother-to-child transmission (MTCT) of HIV and death [5,6,7]. Amidst a rapidly evolving landscape, optimizing maternal and infant drug regimens for prevention of MTCT (PMTCT) of HIV infection remains a research priority. LBW infants, however, have been understudied.
Most recent WHO HIV PMTCT guidelines recommend lifelong combination antiretroviral treatment (ART) for pregnant and breastfeeding HIV-infected women (national PMTCT programme Option B or B+) and six weeks of daily weight-based nevirapine for all breastfed, HIV-exposed infants [8,9]. To date, several trials support extended nevirapine prophylaxis in infancy to prevent breast-milk MTCT of HIV infection [6,10–15]. However, safety and efficacy data in LBW infants are limited as most studies have either excluded or enrolled LBW infants in small numbers [6,11,15–20]. Notably, based on their relative physiologic immaturity, LBW infants may metabolize and respond differently to nevirapine than normal birth weight infants. Specific cytochrome P-450 enzymes isoforms with varying activity levels are differentially expressed throughout development, which leads to differences in nevirapine elimination in fetuses, neonates, and throughout infancy [21,22]. Thus, the impact of extended nevirapine prophylaxis may vary by infant birth weight and optimal dosing may not be known.
The present study aims to assess whether the impact of six-week extended-dose nevirapine (SWEN) prophylaxis varies with infant birth weight. The India SWEN study, a randomized clinical trial of SWEN versus single-dose nevirapine (SD) for PMTCT of HIV-1 infection via breast milk, presents a unique opportunity as LBW infants comprise approximately 40% of the study population, infants were randomized to treatment arm at birth, and HIV-1 transmission was assessed through age 12 months [10,12]. We report our secondary safety and efficacy analyses of the India SWEN study stratified by infant birth weight.
Citation:
Gupte N, Kinikar A, McIntire KN, Bhosale R, Patil S, Survayanshi N, Mave V, Kulkarni V, Bollinger RC, Gupta A. Efficacy of six-week extended-dose nevirapine varies by infant birth weight with greatest relative efficacy in low birth weight infants. PLOS One. 2016 Sept 30. DOI:10.1371/journal.pone.0162979.
|
ESSENTIALAI-STEM
|
Mrs Jones, who is 60 years old, says that HRT keeps her looking youthful and wants to stay on it. What does the evidence suggest?
The menopause represents a natural process that occurs once a woman has experienced 12 months of amenorrhoea and, on average, occurs at 51 years of age. It is associated with many symptoms, including vasomotor problems (i.e., hot flushes and night sweats which affect around 75% of women),1 vaginal dryness, as well as an impairment of sexual function. While predominately used to provide relief from menopausal symptoms, the evidence suggests that hormone replacement therapy (HRT) can also preserve bone density (preventing osteoporosis) and may offer benefits for colorectal cancer, depression and cognitive decline.2
The loss of oestrogens during the menopause leads to accelerated aged-related changes in the skin. The thickness of both the epidermis and dermis is reduced, collagen and elastin levels decrease, and the cumulative impact of these changes lead to dryness and pruritus, wrinkles and fragility, which increases the risk of skin trauma. Given that these changes are due to the menopause, how effective is HRT at reversing these structural changes and thus improving skin health?
Oestrogens and the skin
The skin consists of two layers, an upper epidermis and lower dermis, which is mainly composed of two fibrous proteins, elastin and collagen. The latter accounts for approximately 80% of the dry weight of skin3 and provides tensile strength to the dermis (i.e., resistance to being torn by stretching). There are at least 20 different types of collagen and the three most common are types I,II and III. Although the skin contains as many as 14 different collagens, the most common are type I (80%) and type III (15%).3 In contrast, although elastin makes up only 2 to 4% of the dermis volume, it has a central role in providing resilience and suppleness,4 restoring the skin to its initial shape after stretching. The skin also contains various glycosaminoglycans (GAG), such as hyaluronic acid, which is a humectant, i.e. a compound able to bind water, which helps to maintain hydration.
The fact that oestrogens have an influence on the skin is recognised through its effect on various cutaneous diseases. For instance, the increased levels encountered during pregnancy are associated with a reduction in the severity of psoriasis,5 but can worsen atopic eczema.6 Furthermore, oestrogens in the combined oral contraceptive pill, suppresses androgen production, leading to improvements in acne7 and the hyperpigmentation disorder melasma can be induced during pregnancy and through the use of oestrogen containing contraceptives.
The importance of oestrogens in the maintenance of healthy skin during the menopause was first suspected in 1941, when it was observed that elderly women who had experienced an osteoporotic fracture had thin skin.8 Later work in 1985 revealed how up to 30% of dermal collagen was lost in the first 5 years after the menopause9 and that levels subsequently reduce at a rate of 2% per menopausal year.10 Although levels of collagen naturally reduce with age, there is a suggestion that in women, this decrease is related to the lack of oestrogen rather than chronological aging.11 Moreover, skin elasticity has been estimated to decrease in postmenopausal women at a rate of approximately 0.55% per year.12
During the 1990s, the discovery of oestrogenic receptors on dermal fibroblasts (which are responsible for the production of collagen) and keratinocytes provided a mechanism through which the hormone could exert an effect on the skin. Oestrogen stimulates keratinocyte proliferation, which leads to a thickening of the epidermis and therefore reduced water loss.
The influence of HRT on skin changes in postmenopausal women
The importance of oestrogens in maintenance of skin health offers the possibility that HRT could reduce the menopausal signs of atrophy (thinning), dry skin and wrinkles. Moreover, one observational study in more than 3,000 women found that compared to non-users, HRT use was associated with a statistically significant reduction in dry skin and wrinkling but not atrophy.13
HRT appears to boast dermal collagen levels and thereby improves skin health. This has been the subject of several trials,14 in which all but one demonstrated an improvement in collagen levels. It has been suggested that HRT was ineffective in one trial because the women had been amenorrhoeic for a short period of time (between 4 months and 2 years) and that any hypoestrogenic effects would have been small during this initial period of time.15 The longest study of topical HRT continued for 4.8 years and used 0.06% estradiol gel or transdermal patches to maintain a daily estradiol dose of 1.5mg. The trial observed increases of skin thickness of between 7% and 15% in several areas of the body.16 In contrast, a randomised, double-blind trial with oral conjugated oestrogen therapy, detected a 30% increase in dermal thickness after only 12 months.17
Whether or not the use of HRT can improve the appearance of wrinkles on sun-exposed areas of the body is equivocal
An increase in skin hydration has been demonstrated after 6 months use of topical 0.01% estradiol and 0.3% estriol for six months.18 Although the mechanism through which oestrogens increase skin hydration is unclear, studies in mice indicate that estradiol increases the level of hyaluronic acid and thereby the water content of the skin.19
Reducing wrinkles
Collagen is broken down in the skin by a group of enzymes termed metalloproteinases, which have an important role in tissue repair and remodelling. A reduction in the amount and integrity of collagen within the dermis leads to progressive slackness of the skin, a loss of elasticity and subsequent wrinkle formation. This process is exacerbated on sun-exposed areas of skin such as the face, which is subject to photo-aging.
Whether or not the use of HRT can improve the appearance of wrinkles on sun-exposed areas of the body is equivocal. One study found that HRT was able to reduce skin slackness20 (and potentially wrinkle appearance, but this was not assessed). Another study using Premarin cream (0.625mg conjugated oestrogens) in women aged between 52 and 70 for 24 weeks did produce a significant improvement in fine wrinkles.21 A third study in women using HRT for at least 5 years also produced improvements in skin elasticity with less pronounced wrinkling.22 In contrast, however, other trials have failed to demonstrate any benefits. In the largest of these studies, Phillips et al23 enrolled 485 patients using oral HRT for 48 weeks and found no difference in facial wrinkling. Similarly, Yoon et al,24 using topical oestrone 1% or placebo on sun-exposed skin for 24 weeks, found no difference compared to placebo. In a third study, application of topical estradiol 0.05% cream to photo-exposed skin (face) for 30 days did not observe changes in the expression of metalloproteinase-1 enzyme (which degrades collagen).25
More recent studies have demonstrated that alternatives to HRT, such as selective oestrogen receptor modulators (SERMS) (for example raloxifene), are able to increase collagen synthesis26 in dermal fibroblasts and increase skin elasticity.27
In summary, there is no doubt that oestrogens exert several beneficial effects on the skin. The reduction in oestrogen levels during the menopause has a detrimental impact on the skin, which can be corrected to some degree through the use of HRT. Whether HRT can improve the appearance of wrinkles, especially on sun-exposed areas such as the face, appears to be less likely.
HRT is not licensed for the management of cutaneous symptoms and women should therefore not make the decision to use HRT solely for the improvement of skin problems induced by the menopause.
References
1. Hamoda H et al. Post Reprod Health 2016; 22(4): 165-183
2. Minelli C et al. BMJ 2004; 328: 371
3. Phuoung, C et al in Farage MA et al (eds). Textbook of Aging Skin. Berlin Heidelberg: Springer-Verlag (2017): 764-772
4. Waller JM et al. Skin Res Technol 2006; 12(3): 145-54
5. Danesh M et al. Int J Women’s Dermatol 2015; 1(2): 104-107
6. Danesh M et al. Obstet Gynecol Int J 2015; 2(3): 2-4
7. Ebede TL et al. J Clin Aesthet Dermatol 2009; 2(12): 16-22
8. Albright F et al. JAMA 1941;116(22): 2465-2474
9. Brincat M et al. Br J Obstet Gynaecol 1985; 92(3): 256-59
10. Brincat M et al. Obstet Gynecol 1987;70: 123-127
11. Affinito P et al. Maturitas 1999; 33: 239-247
12. Sumino H et al. J Am Geriatr Soc 2004; 52(6): 945-49
13. Dunn LB et al. Arch Dermatol 1997; 133(3): 339-342
14. Brincat MP et al. Climacteric 2005; 8: 110-123
15. Archer DF. Gynecol Endocrinol 2012; 28(Suppl 2): 2- 6
16. Callens A et al. Dermatology 1996; 193(4): 289-94
17. Maheux R et al. Am J Obstet Gynecol 1994; 170(2): 642-49
18. Schmidt JB et al. In J Dermatol 1996; 35(9): 669-74
19. Sobel H et al. Steroids 1970; 30: 458-64
20. Pierard GE et al. J Am Geriatr Soc 1995; 43(6): 662-65
21. Creidi P et al. Maturitas 1994; 19(3): 211-23
22. Wolf EF et al. Fertil Steril 2005; 84: 285-288
23. Phillips TJ et al. J Am Acad Dermatol 2008; 59: 397-404
24. Yoon et al. Acta Derm Venereol 2014; 94: 4-8
25. Neder L. An Bras Dermatol 2012; 87(1): 70-75
26. Surazynski A et al. Int J Mol Mol 2003; 12(5): 803-39
27. Sumino H et al. Maturitas 2009; 62(1): 53-57.
Rod Tucker
Pharmacist with a special interest in dermatology
|
ESSENTIALAI-STEM
|
MAY 16, 2023 7:30 AM PDT
Keynote Presentation: How Do We Enable Precision Health at Scale for All? With Live Q&A
C.E. Credits: P.A.C.E. CE Florida CE
Speaker
Abstract
The last 20 years have seen an explosion of genetic information and data. New technological advances have made it faster and less expensive to understand the human genomes but most of those resources have focused on northern European communities.
Throughout his keynote speech, Dr. Bustamante elaborates on the major challenge to enabling precision health at a global scale, and the bias between those who enroll in state sponsored genomic research and those suffering from chronic disease. More than 30 million people have been genotyped by direct-to-consumer (DTC) companies such as 23andMe, Ancestry DNA, and MyHeritage, providing a potential mechanism for democratizing access to medical interventions and thus catalyzing improvements in patient outcomes as the cost of data acquisition drops. In this keynote speech, Dr. Bustamante presents a novel geno-pheno platform that integrates heterogeneous data sources and applies learnings to common chronic disease conditions.
He further covers how the SARS-CoV-2 pandemic has differentially impacted populations of varied race, ethnicity and socioeconomic status. His research team leveraged a pandemic tracking strategy in which they sequenced viral and host genomes, and transcriptomes from nasopharyngeal swab residuals and integrated them with digital phenotypes from electronic health records. They demonstrated over-representation of individuals possessing Oceanian and Indigenous American ancestry in SARS-CoV-2 positive populations. This work demonstrated the power of multi-omic pandemic tracking and genomic analyses to reveal distinct epidemiologic, genetic and biological associations for those at the highest risk.
The next phase of this work will leverage clinical-grade biobanking, research and clinical genomics, paired with best-in-class ancestry and genome annotation algorithms towards better understanding the genetic architecture of underserved populations and powering the next generation of precision medicine studies.
Learning Objectives:
1. Discuss the need for diversity in advancing the future of precision medicine.
2. Uncover the adverse effects caused by the deficiencies in the approach to drug production today.
3. Explore unique mechanisms for enhancing currently employed biobanking practices.
|
ESSENTIALAI-STEM
|
haskell-src-exts-1.8.2: Manipulating Haskell source: abstract syntax, lexer, parser, and pretty-printer
Portabilityportable
Stabilitystable
MaintainerNiklas Broberg, d00nibro@chalmers.se
Language.Haskell.Exts.Pretty
Contents
Description
Pretty printer for Haskell with extensions.
Synopsis
Pretty printing
class Pretty a Source
Things that can be pretty-printed, including all the syntactic objects in Language.Haskell.Exts.Syntax and Language.Haskell.Exts.Annotated.Syntax.
Instances
Pretty SrcSpan
Pretty SrcLoc
Pretty Tool
Pretty GuardedAlt
Pretty GuardedAlts
Pretty Alt
Pretty FieldUpdate
Pretty QualStmt
Pretty Stmt
Pretty PatField
Pretty RPat
Pretty RPatOp
Pretty PXAttr
Pretty Pat
Pretty RuleVar
Pretty Rule
Pretty Activation
Pretty OptionPragma
Pretty CallConv
Pretty Safety
Pretty Splice
Pretty Bracket
Pretty XAttr
Pretty XName
Pretty Exp
Pretty Literal
Pretty Asst
Pretty FunDep
Pretty Kind
Pretty TyVarBind
Pretty Type
Pretty GuardedRhs
Pretty Rhs
Pretty BangType
Pretty InstDecl
Pretty ClassDecl
Pretty GadtDecl
Pretty ConDecl
Pretty QualConDecl
Pretty Match
Pretty IPBind
Pretty DataOrNew
Pretty Annotation
Pretty Decl
Pretty Assoc
Pretty ImportSpec
Pretty ImportDecl
Pretty ExportSpec
Pretty Module
Pretty CName
Pretty Op
Pretty QOp
Pretty IPName
Pretty Name
Pretty QName
Pretty SpecialCon
Pretty ModuleName
SrcInfo loc => Pretty (GuardedAlt loc)
SrcInfo loc => Pretty (GuardedAlts loc)
SrcInfo loc => Pretty (Alt loc)
SrcInfo loc => Pretty (FieldUpdate loc)
SrcInfo loc => Pretty (QualStmt loc)
SrcInfo loc => Pretty (Stmt loc)
SrcInfo loc => Pretty (PatField loc)
SrcInfo loc => Pretty (RPat loc)
Pretty (RPatOp l)
SrcInfo loc => Pretty (PXAttr loc)
SrcInfo loc => Pretty (Pat loc)
Pretty (WarningText l)
Pretty (RuleVar l)
SrcInfo loc => Pretty (Rule loc)
Pretty (Activation l)
Pretty (OptionPragma l)
Pretty (CallConv l)
Pretty (Safety l)
SrcInfo loc => Pretty (Splice loc)
SrcInfo loc => Pretty (Bracket loc)
SrcInfo loc => Pretty (XAttr loc)
Pretty (XName l)
SrcInfo loc => Pretty (Exp loc)
Pretty (Literal l)
Pretty (Asst l)
Pretty (Context l)
Pretty (FunDep l)
Pretty (Kind l)
Pretty (TyVarBind l)
Pretty (Type l)
SrcInfo loc => Pretty (GuardedRhs loc)
SrcInfo loc => Pretty (Rhs loc)
Pretty (BangType l)
SrcInfo loc => Pretty (InstDecl loc)
SrcInfo loc => Pretty (ClassDecl loc)
Pretty (GadtDecl l)
Pretty (FieldDecl l)
Pretty (ConDecl l)
Pretty (QualConDecl l)
SrcInfo pos => Pretty (Match pos)
SrcInfo loc => Pretty (IPBind loc)
Pretty (Deriving l)
Pretty (InstHead l)
Pretty (DeclHead l)
Pretty (DataOrNew l)
SrcInfo loc => Pretty (Annotation loc)
SrcInfo pos => Pretty (Decl pos)
Pretty (Assoc l)
Pretty (ImportSpec l)
Pretty (ImportSpecList l)
SrcInfo pos => Pretty (ImportDecl pos)
Pretty (ExportSpec l)
Pretty (ExportSpecList l)
Pretty (ModuleHead l)
SrcInfo pos => Pretty (Module pos)
Pretty (CName l)
Pretty (Op l)
Pretty (QOp l)
Pretty (IPName l)
Pretty (Name l)
Pretty (QName l)
Pretty (ModuleName l)
SrcInfo loc => Pretty (PAsst loc)
SrcInfo loc => Pretty (PType loc)
SrcInfo loc => Pretty (PContext loc)
SrcInfo loc => Pretty (ParseXAttr loc)
SrcInfo loc => Pretty (PFieldUpdate loc)
SrcInfo loc => Pretty (PExp loc)
prettyPrintStyleMode :: Pretty a => Style -> PPHsMode -> a -> StringSource
pretty-print with a given style and mode.
prettyPrintWithMode :: Pretty a => PPHsMode -> a -> StringSource
pretty-print with the default style and a given mode.
prettyPrint :: Pretty a => a -> StringSource
pretty-print with the default style and defaultMode.
Pretty-printing styles (from Text.PrettyPrint.HughesPJ)
data Style
A rendering style.
Constructors
Style
Fields
mode :: Mode
The rendering mode
lineLength :: Int
Length of line, in chars
ribbonsPerLine :: Float
Ratio of ribbon length to line length
style :: Style
The default style (mode=PageMode, lineLength=100, ribbonsPerLine=1.5).
data Mode
Rendering mode.
Constructors
PageMode
Normal
ZigZagMode
With zig-zag cuts
LeftMode
No indentation, infinitely long lines
OneLineMode
All on one line
Haskell formatting modes
data PPHsMode Source
Pretty-printing parameters.
Note: the onsideIndent must be positive and less than all other indents.
Constructors
PPHsMode
Fields
classIndent :: Indent
indentation of a class or instance
doIndent :: Indent
indentation of a do-expression
caseIndent :: Indent
indentation of the body of a case expression
letIndent :: Indent
indentation of the declarations in a let expression
whereIndent :: Indent
indentation of the declarations in a where clause
onsideIndent :: Indent
indentation added for continuation lines that would otherwise be offside
spacing :: Bool
blank lines between statements?
layout :: PPLayout
Pretty-printing style to use
linePragmas :: Bool
add GHC-style LINE pragmas to output?
data PPLayout Source
Varieties of layout we can use.
Constructors
PPOffsideRule
classical layout
PPSemiColon
classical layout made explicit
PPInLine
inline decls, with newlines between them
PPNoLayout
everything on a single line
Instances
defaultMode :: PPHsModeSource
The default mode: pretty-print using the offside rule and sensible defaults.
|
ESSENTIALAI-STEM
|
Semtek International Inc. v. Lockheed Martin Corp.
Semtek v. Lockheed Martin, 531 U.S. 497 (2001), is a United States Supreme Court case in which the Court held that the claim preclusive effect of a federal judgment on a claim over which subject matter jurisdiction is based solely on diversity is determined by the common law of the state in which the federal district court rendering the decision is located.
Background
Petitioners Semtek International Incorporated filed a complaint against Lockheed Martin in California state court, alleging a breach of contract. The case was removed to the local federal district court due to the diversity of citizenship in the case. The trial judge then dismissed the complaint, writing that California's 2-year statute of limitations made the claim "barred".
Semtek International had also filed a claim in Maryland's state court. The court here also dismissed the complaint, but on the grounds that "the res judicata effect" precludes this separate claim in a different state. Since another federal court had dismissed a similar action already, Semtek could not proceed in a different court on virtually similar contentions.
Opinion of the Court
Justice Antonin Scalia wrote the unanimous decision of the Supreme Court, reversing the decision of the Maryland courts. Scalia wrote that there was no final "judgment on the merits" in the California case and thus the Maryland trial was not precluded. A reading of the appropriate rule could be seen as still permitting other actions. Therefore, Semtek was entitled to a trial before the Maryland courts and the case was remanded with such instructions.
|
WIKI
|
Activation Energy in an Endergonic Reaction
Endergonic reactions are often synthetic.
••• laboratoire image by razorconcept from Fotolia.com
In a chemical reaction, the starting materials, called reactants, are converted to products. While all chemical reactions require an initial energy input, referred to as the activation energy, some reactions result in a net release of energy into the surroundings, and others result in a net absorption of energy from the surroundings. The latter situation is called an endergonic reaction.
Reaction Energy
Chemists define their reaction vessel as the "system" and everything else in the universe as the "surroundings." Therefore, when an endergonic reaction absorbs energy from the surroundings, the energy enters the system. The opposite type is an exergonic reaction, in which energy gets released into the surroundings.
The first part of any reaction always requires energy, no matter the reaction type. Even though burning wood gives off heat and spontaneously occurs once it gets started, you do have to start the process by adding energy. The flame you add to start the wood burning provides the activation energy.
Activation Energy
To get from the reactant side to the product side of the chemical equation, you must overcome the activation energy barrier. Each individual reaction has a characteristic barrier size. The height of the barrier has nothing to do with whether the reaction is endergonic or exergonic; for instance, an exergonic reaction may have a very high activation energy barrier, or vice-versa.
Some reactions take place in multiple steps, with each step having its own activation energy barrier to overcome.
Examples
Synthetic reactions tend to be endergonic, and reactions that break molecules down tend to be exergonic. For example, the process of amino acids joining to make a protein, and the formation of glucose from carbon dioxide during photosynthesis are both endergonic reactions. This makes sense, as processes that build bigger structures are likely to require energy. The reverse reaction--for instance, cellular respiration of glucose into carbon dioxide and water--is an exergonic process.
Catalysts
Catalysts can reduce the activation energy barrier of a reaction. They do so by stabilizing the intermediate structure that exists between that of the reactant and product molecules, making the conversion easier. Basically, the catalyst gives the reactants a lower-energy "tunnel" to pass through, making it easier to get to the product side of the activation energy barrier. There are many types of catalysts, but some of the best-known ones are enzymes, catalysts of the biology world.
Reaction Spontaneity
Regardless of activation energy barrier, only exergonic reactions occur spontaneously, because they give off energy. Yet, we still need to build muscle and repair our bodies, which are both endergonic processes. We can drive an endergonic process by coupling it with an exergonic process that provides enough energy to match the difference in energy between reactants and products.
Related Articles
What Role Does Heat Play in Chemical Reactions?
What is an Endergonic Reaction?
What Happens in Exergonic Chemical Reactions?
Role of Enzymes in Chemical Reactions
What Happens When Chemical Bonds Break And New Bonds...
What Happens to Chemical Bonds During Chemical Reactions
What is an Endothermic Reaction?
What Is Runaway Polymerization?
What Is the Difference Between Reactants & Products...
How ADP Is Converted to ATP During Chemiosmosis within...
Why Are Transition Metals Good Catalysts?
What Is the Role of Enzymes in Metabolism?
The Effect of Temperature on Activation Energy
What Is Activation Energy?
Products Produced by Anaerobic Respiration
What Are Causes of Chemical Reactions?
Similarities Between Combustion & Cellular Respiration
How are Chemical Bonds Important in Metabolism
What Determines the Amount of Chemical Energy a Substance...
How to Write & Balance a Decomposition Reaction
Dont Go!
We Have More Great Sciencing Articles!
|
ESSENTIALAI-STEM
|
Allegiant (ALGT) Jumps on the Fuel Price Hike Bandwagon
The recent upsurge in oil price is not a favorable development for airline stocks, especially as far as their bottom-line growth is concerned. This is because fuel expenses represent one of the most significant input costs for aviation. The oil price spike prompted many airline stocks to increase their respective estimates for first-quarter fuel price per gallon.
The latest to be included in this list is Allegiant Travel Company ALGT. ALGT, currently carrying a Zacks Rank #5 (Strong Sell), expects fuel price per gallon to be $3.05 in the first quarter of 2022 (earlier guidance was $2.67).
You can see the complete list of today’s Zacks #1 Rank (Strong Buy) stocks here.
Like other carriers, Allegiant lowered its capacity growth forecast for the first quarter due to the oil price rise. Available seat miles (a measure of capacity), both for scheduled service and system wide, is expected to increase in the 17-19% range from the first-quarter 2019 actuals (earlier guidance was for an increase in the 19-23% range).
Due to the cut in the capacity growth forecast, ALGT increased the lower limit for first-quarter 2022 non-fuel unit cost growth projection. The metric is now expected to rise in the 3-5% range from first-quarter 2019 actuals (earlier guidance was an increase of 1-5%).
Per Gregory Anderson, executive vice president and chief financial officer of Allegiant, "Due predominantly to the volatile fuel environment as well as some staffing challenges, we expect to reduce planned capacity by roughly ten percent for the second quarter. We will continue to manage capacity to maximize profitability." Average fuel price per gallon for February is estimated to be $2.92.
However, owing to strong air-travel demand, the picture with respect to revenues is bright. Per Drew Wells, senior vice president, revenue, "After a slow start to the quarter, attributable to the Omicron variant, we saw a significant step-up in leisure demand beginning mid-February and persisting into March. We finished February with a load factor (% of seats filled with passengers) of 77.8%, a more than eight-point improvement over January. Load factor during the month of March is currently trending above levels observed in 2019, with several weeks exceeding 90 percent booked loads, marking the first time we've seen loads at this level since the onset of the pandemic”.
Management now expects first-quarter 2022 operating revenues to improve in the 7.5-9% band from first-quarter 2019 actuals (earlier guidance was an increase in the 5-9% band).
Given this changing scenario, let’s briefly recapitulate the revised first-quarter projections of some other carriers.
American Airlines AAL now expects first-quarter revenues to decline roughly 17% from first-quarter 2019 actuals, better than its previous outlook of a 20-22% fall. Like other carriers, AAL decreased its first-quarter capacity growth outlook. The metric is now expected to be down 10-12% compared with the 8-10% decline anticipated earlier.
First-quarter non-fuel unit cost is now expected to be up approximately 11-13% compared with the earlier projection of an approximate 8-10% increase. Fuel price per gallon is now expected in the $2.73-$2.78 range compared with the $2.41-$2.46 band, anticipated earlier.
Like other airlines, JetBlue Airways JBLU raised its revenue guidance but trimmed its capacity outlook for first-quarter 2022 due to increasing oil price. JBLU now expects revenues to decline in the 6-9% band compared with an 11-16% decrease, expected earlier.
Capacity is expected to dip 1% from the first-quarter 2019 actuals. The same is compared with the earlier expectation of a range of 1% decline to an increase of up to 2%.
Breakout Biotech Stocks with Triple-Digit Profit Potential
The biotech sector is projected to surge beyond $2.4 trillion by 2028 as scientists develop treatments for thousands of diseases. They’re also finding ways to edit the human genome to literally erase our vulnerability to these diseases.
Zacks has just released Century of Biology: 7 Biotech Stocks to Buy Right Now to help investors profit from 7 stocks poised for outperformance. Recommendations from previous editions of this report have produced gains of +205%, +258% and +477%. The stocks in this report could perform even better.
See these 7 breakthrough stocks now >>
Want the latest recommendations from Zacks Investment Research? Today, you can download 7 Best Stocks for the Next 30 Days. Click to get this free report
Allegiant Travel Company (ALGT): Free Stock Analysis Report
JetBlue Airways Corporation (JBLU): Free Stock Analysis Report
American Airlines Group Inc. (AAL): Free Stock Analysis Report
To read this article on Zacks.com click here.
Zacks Investment Research
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.
|
NEWS-MULTISOURCE
|
User:Damodar Kamat Ghanekar/sandbox
Well known lexicographer, editor and grammarian. The BEST proof reader in Konkani. Versatile Konkani grammar proponent, and Konkani Grammar trainer.
|
WIKI
|
Manuel II of Constantinople
Manuel II (Μανουήλ; died 3 November 1254) was the Patriarch of Constantinople from 1244 to 1255. Because of the Latin occupation of Constantinople (1204–61), Manuel resided at the temporary Byzantine capital in Nicaea. He worked in close collaboration with Emperor John III Ducas Vatatzes, particularly in negotiations concerning possible union with the Roman Church. In 1249, Manuel II was likely involved with the delegation from Pope Innocent IV and led by the Franciscan friar John of Parma, which arrived at the temporary Patriarchal seat in Nymphaeum in 1249 and until 1250, there to debate the filioque against the Orthodox spokesman Nikephoros Blemmydes. The delegation from the Pope returned to him with a note from the Patriarch which exhorted unity under Christ as the only head of the Church, avoiding the term "Schism" and referring only to the "separation" of the Churches. In 1253, the Emperor and Manuel sent envoys to Pope Innocent IV to more formally discuss ecclesiastical union, renewing these negotiations. These were conducted in Perugia, and appear to have achieved some entente, with Innocent acknowledging the sincerity of the Orthodox Church's desire for union. Despite continued disagreement about the filioque clause in the Nicene Creed, negotiations continued, which resulted in an initial offer of formal recognition of the Greek patriarchate. No further progress was made after 1254, however, as the architects of the entente—Pope Innovent IV, the Emperor John Vatatzes, and the Patriarch Manuel II—all died within a few months of each other, and the impetus was lost.
In 1247–48 he wrote to the Armenian King Hethum I and the Catholicos regarding their relations with the Byzantine Church, and in July 1250 he composed a series of responses to canonical questions. In 1253–54 he received solemn assurance, under pain of censure, from the regent Michael VIII Palaeologus, that he would not intrigue against the Emperor of Nicaea, Theodore II Lascaris (1254–58); and early in 1254 he addressed a letter to the emperor instructing him on his duties.
Manuel held, before his patriarchate, the position of protopapas among the ecclesiastics of the Byzantine court, then fixed at Nicea. Noted as a man of piety and holiness, "though married," Akropolites comments sourly that he was a man "who had no experience of letters, nor was able to unravel the meaning of what he read". The three Sententice Synodales of the patriarch Manuel given in the Jus Graeco-Romanum undoubtedly belong to this patriarch.
Manuel's death is distinctly fixed as having occurred two months before that of the Emperor John III Ducas Vatatzes, on 30 October 1255. The duration of his patriarchate is fixed by Nikephoros Kallistos Xanthopoulos, at eleven years. George Akropolites and Xanthopoulos both suggest the throne was vacant "for some years" before Manuel was appointed. It is therefore relatively certain Manuel died in office that year, before 3 November 1255.
|
WIKI
|
Raspberry Pi IRC Server: Setup your own Chat Network
In this project, we will be showing you how to set up a Raspberry Pi IRC Server.
Raspberry Pi IRC Server
An IRC server is perfect for the Raspberry Pi as compared to most other servers, as it is not hugely performance draining on the Raspberry Pi’s limited resources.
IRC for those who don’t know stands for Internet Relay Chat, it is one of the oldest chat protocols and even though it has fallen in popularity in recent years it is still the backbone of many communities.
Even the popular streaming service, Twitch makes use of an IRC server to handle its chat. In fact, we use the IRC protocol to interact with Twitch’s Chat network in our Raspberry Pi Twitch Bot tutorial.
There are quite a few different servers that you can set up on a Raspberry Pi, and this is just one of them. If you like the idea of this, then be sure to check out some of our other server tutorials for the Raspberry Pi.
For this project, we will be utilizing Ircd-Hybrid as it is the most lightweight, high-performance and reliable IRC server that we have tested.
Equipment List
Below are all the bits and pieces that I used for this Raspberry Pi IRC Server tutorial, you will need an internet connection to be able to complete this tutorial.
Recommended
Raspberry Pi 2 or 3
Micro SD Card
Power Supply
Ethernet Cord or Wifi dongle (The Pi 3 has WiFi inbuilt)
Optional
Raspberry Pi Case
Installing and configuring the IRC Server
1. Before we get started with installing and setting up our Raspberry Pi IRC server we will first run an update and upgrade to ensure the Raspbian operating system is completely up to date.
To do this run the following two commands in the terminal on your Raspberry Pi.
sudo apt-get update
sudo apt-get upgrade
2. With our Raspberry Pi now up to date, we can proceed with installing the IRC Server software onto it.
We are using a piece of software called Ircd-Hybrid which is a very lightweight, stable and high-performance IRC server. All three of which are perfect characteristics for the Raspberry Pi’s limited resources.
To install the software for our Raspberry Pi IRC Server, type the following command into the terminal.
sudo apt-get install ircd-hybrid
3. To setup oping on our IRC Server, we will also need to set a password. ircd-hybrid requires this password to be encrypted, and we can use the following command to encrypt the password. Make sure you switch out password for your own and save the result as we will need this later
/usr/bin/mkpasswd password
4. Once the installation has completed, we can proceed with configuring the Ircd-Hybrid software. To do this, we will need to edit the ircd.conf file within the /etc/ircd-hybrid folder.
To do this, we can simply run the following command in terminal to load up nano and begin editing the file.
sudo nano /etc/ircd-hybrid/ircd.conf
5. Within this file, you will notice a huge amount of different options that you can configure in here. We will quickly change some of these configurations and explain why to give you an idea what they are for.
Thankfully the configuration file is pretty easy to understand due to a large number of comments so if there is anything you ever need to edit, just read the comments around it.
Within the serverinfo { block
Find
name = "hybrid8.debian.local";
Replace With
name = "pimylifeup.irc";
This line defines the name for your IRC server, and you can set this to whatever you like. As an example, for our tutorial, we will set this to pimylifeup.irc.
Find
description = "ircd-hybrid 8.1-debian";
Replace With
description = "Raspberry Pi IRC Server";
This line sets the servers description and will be what people see when they connect to your server.
Find
network_name = "debian";
network_desc = "This is My Network";
Replace With
network_name = "pimylifeup";
network_desc = "This is my Raspberry Pi IRC Network";
This line is for describing the name and description of the network that your server is on.
Find
max_clients = 512;
Replace With
max_clients = 128;
This line defines the maximum amount of people that can be connected to the IRC Server.
Within the operator { block
Find and remove
#
This section requires uncommenting, remove the first layer of # if you see ## only remove the first one.
Find
name = "sheep";
Replace With
name = "op";
This line defines the name of the operator group, and we will use op as it is easiest to remember, you can set this to whatever you want.
Find
user = "*@192.0.2.240/28";
Replace With
user = "*@*";
This line will change it so that anyone connecting to the server can run the oper command. If you want to restrict this to local users only you can try using something like *@192.168.*.*
Find
password = "xxxxxxxxxxxxx";
Replace With
password = "REPLACE WITH YOUR ENCRYPTED PASSWORD";
Here we will want to replace the default password with the one that we encrypted earlier in the tutorial with the /usr/bin/mkpasswd tool. Remember this is not the plain text version of your password, it is the scrambled form.
6. Now we can save and quit out of the file by pressing Ctrl +X then pressing Y and then Enter.
7. With that now done you can modify the message of the day (MOTD) for the IRC Server. This message is relatively easy to change as the ircd-hybrid software reads it from a file called ircd.motd that is located in the /etc/ircd-hybrid folder.
You can begin modifying this file by running the following command in terminal.
sudo nano /etc/ircd-hybrid/ircd.motd
For our tutorial, we will skip modifying this file, but basically whatever is in it will be displayed to a user upon connecting with the server.
8. Now that we have done our initial configuration of our Raspberry Pi IRC Server we will need to restart the server software. This restart is easily done by running the following command in terminal.
sudo /etc/init.d/ircd-hybrid restart
Connecting to your IRC Server
Now that we have configured our Raspberry Pi IRC Server we can now test to make sure it works. We will go through steps on connecting to the server using an IRC client on Windows to give you an idea of how to utilize your server.
For Windows, we will be utilizing the popular mIRC client.
1. To start off, first download and install the mIRC client, you can download it by going to mIRC’s homepage.
2. Once mIRC has finished installing, launch it. Once launched click File -> Select Server (Or press Alt + E)
3. A new windows should now pop up, on here you want to click the Add button.
4. Yet another window should load up, this time you will need to fill out the Description: and the Address: textboxes.
For Description: we chose to use pimylifeup, make sure you choose something that makes it stand out from the rest of the IRC servers.
For Address: we need to set this to the IP of our Raspberry Pi, if you don’t know the IP of your Raspberry Pi, try typing the command hostname -I into its terminal. In our example, we will be using 192.168.0.143.
Once you have filled out this information, click the Add button.
5. Your server should now be added to mIRC’s list of IRC servers. It should also already be selected, and if it isn’t, then look for your new addition. It will be under the name you set for Description: in our case, we would find it under the name pimylifeup.
Once you are certain you have it selected, press the Select button.
6. You will finally be brought to one final screen before making the connection, and here you will want to set your Nickname: to whatever you want. Now before you jump ahead and press the Connect button make sure your server description name is next to Server:
Once you are sure it is correct, click the Connect button.
7. Finally, type in the channel name you want to use, this can be anything as long as it starts with a #, once typed in all you need to do is click the Join button.
If all has gone well, you should now be successfully connected to your Raspberry Pi IRC Server.
OPing yourself on your Raspberry Pi IRC Server
1. To OP yourself on your IRC server you need to remember the group name and the unencrypted password that you set earlier in this tutorial.
Once you have both handy, connect to your IRC server.
2. Once connected to your IRC server and you are in a channel, type in the command below into chat. Make sure that you replace op with your group name and replace password with the password you set earlier in this tutorial when you ran the /usr/bin/mkpasswd command.
3. You should see You are now an IRC operator appear in chat if you have been successfully made an operator.
Hopefully, by now, you have a fully functioning IRC Server running on your Raspberry Pi, including the ability to be able to set yourself as an operator. It’s quite a cool way to have your own private chat server that you can share with your family and friends.
Don’t forget to drop a comment below if this Raspberry Pi IRC server tutorial helped you out or whether you run into any issues. Don’t forget to check out our numerous other fun Raspberry Pi projects available on our website.
4 Comments
1. Avatar for Andre
Andre on
This guide is missing an important command. At the very end of the article, it doesn’t show the command we should use to make ourselves an OPerator.
Thanks @Justin for mentioning it here in the comments! /OPER username password worked for me! thanks
2. Avatar for Virgilio Rodriguez
Virgilio Rodriguez on
I was able to connect a Windows PC but I tried the same with a Mac, iPhone, Linux and I kept getting a load ident error and those clients could connect.
I am trying to resolve this before Tuesday so I can use it as a project for a class. Please help.
3. Avatar for Zsombor
Zsombor on
What command do I need to type in to op myself in the server?
1. Avatar for Justin
Justin on
I got stuck here too, found this on GeekShed. Syntax: /OPER userid password
Leave a Reply
Your email address will not be published. Required fields are marked *
|
ESSENTIALAI-STEM
|
Discussions
View Only
• 1. Formula query for total
Posted 08-11-2022 14:54
Edited by Annalise Sansouci 08-11-2022 15:34
**EDITTED- I figured it out! But now I can't figure out how to delete this post...there is not enough caffeine in the world today...
Hi All- my brain is fried and I can't figure out this but hoping one of ya'll knows this easy peasy (Looking at your genius Mark Shnier!). Basically I have a table that I want to create a formula query to get totals from another table after a certain date.
So there is a total field on one table [Total Ride Cost] and a date field [Date of Ride]. I want it to pull and total all of the total ride costs after April 1 and put that into a second table.
Thoughts?
------------------------------
Annalise Sansouci
------------------------------
• 2. RE: Formula query for total
Posted 08-11-2022 16:59
Can you post your successful formula?
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
• 3. RE: Formula query for total
Posted 08-12-2022 08:56
SumValues(GetRecords("{9.GT.'"&Date(2022, 3, 31)&"'}",[_DBID_RIDES]),11)
How did I do Mark!?
------------------------------
Annalise Sansouci
------------------------------
|
ESSENTIALAI-STEM
|
Template:Did you know nominations/Hanging Sword Alley
The result was: promoted by Cwmhiraeth (talk) 06:17, 3 March 2018 (UTC)
Hanging Sword Alley
* ... that Hanging Sword Alley (pictured) was also known as "Blood Bowl Alley" after its infamous night life?
* Reviewed: Catlin Brook
* Comment: The hook can be verified in the London Encyclopedia. I'll continue to polish the page but need to get it nominated today.
Created by Andrew Davidson (talk) and Ritchie333 (talk). Nominated by Andrew Davidson (talk) at 20:23, 5 January 2018 (UTC).
* Symbol voting keep.svg New enough, long enough, meets core content policies. Hook cited to RS. Jakob ( talk ) 21:21, 7 January 2018 (UTC)
* Symbol question.svg QPQ still needed. Yoninah (talk) 22:22, 7 January 2018 (UTC)
The QPQ has been done. It was interesting that there were very few nominations waiting for a review as I'm used to there being more choice. Andrew D. (talk) 22:26, 7 January 2018 (UTC)
* Symbol voting keep.svg QPQ done, thanks. Restoring tick per Jacob Coles' review. Yoninah (talk) 22:51, 7 January 2018 (UTC)
* Symbol possible vote.svg I have pulled this from prep because the supplied source doesn't support the hook. Gatoclass (talk) 09:56, 19 January 2018 (UTC)
* Pinging, . Gatoclass (talk) 10:38, 10 February 2018 (UTC)
* I'll try to get back to this this weekend. There's a London Wikimeet tomorrow and so I might look in on the alley, as it's nearby. Andrew D. (talk) 11:15, 10 February 2018 (UTC)
* No source applied in 2 weeks time. Symbol delete vote.svg — Coffee // have a ☕️ // beans // 13:41, 24 February 2018 (UTC)
* It has been a busy couple of weeks and people have been chasing for action on other DYKs. I'll get to this one this weekend. Andrew D. (talk) 13:51, 24 February 2018 (UTC)
I've made another pass through this, expanding and adjusting the article. I'm not quite understanding the objection which was made by but here's an ALT which should be uncontroversial. Please take another look.
* ALT1 ... that Hanging Sword Alley (pictured) wound through the infamous rookeries of Alsatia and was named after the sign of a fencing school?
* This is supported by the quote from Walter Bell's Fleet Street in Seven Centuries and the entry in the London Encyclopedia. Andrew D. (talk) 00:59, 26 February 2018 (UTC)
Considering the objection appeared to be more on technical grounds (the hook apparently wasn't supported by the source), and this new hook is supported by sources (AGF), I suppose this is good to go. Narutolovehinata5 tccsdnew 04:29, 2 March 2018 (UTC)
|
WIKI
|
Christina Hammer
Christina Hammer (born 16 August 1990) is a German boxer. As a professional, she has held multiple world championships in two weight classes, including the WBO female middleweight title from 2010 to 2019, becoming the youngest boxer to win a WBO world title; the WBC female middleweight title between 2016 and 2018; and the WBO female super-middleweight title in 2013. She also challenged once for the WBO female light-middleweight title in 2014 and once for the undisputed female middleweight championship against Claressa Shields in 2019.
Since Hammer's victory against Zita Zatyko, she has earned Fighter of the Year by the WBF and WBO; she was awarded BDB's Female Boxer of the Year; and the WBO awarded her with the WBO Diamond Ring for exceptional performance. As of February 2019, Hammer is ranked as the world's second best active female middleweight by The Ring and BoxRec, and the seventh best active female, pound-for-pound, by ESPN.
Hammer is known for her patient and methodical boxing style, wearing her opponents down with jabs and increasingly aggressive follow-up rights. Since November 2021 she is signed by Wasserman Boxing and managed by Daniel Todorovic of O1NE Sport GmbH.
Early life
Christina Hammer was born 16 August 1990 in Nowodolinka, Kazakh SSR, before emigrating with her parents to Sontra, Germany, in 1991. Her parents left Kazakhstan as they saw a better future for the whole family in Germany, with the quality of education and quality of life, while Hammer spoke of being raised to never give up. She developed a passion for sports through football, running, swimming, and at the age of 13, she was introduced to boxing after her uncles allowed her to accompany them to boxing gyms. She trained in Eschwege under Robert Staar, while going on to become a junior champion three years later. At the age of 18, Hammer was discovered by her coach and trainer, Dimitri Kirnos, to which she stated: "Although I grew up in a small town, at age 18 I decided to become a professional boxer and moved away from home [...] Of course, it was not easy at first, but I knew I could do it if I pulled it off." When Hammer was growing up, she admired Gennady Golovkin and Wladimir Klitschko as athletes, while stating she too admired "strong women like Jennifer Lopez who built their own empire".
Amateur career
Hammer competed for Eschwege Boxing Club at a number of German tournaments, in which she defeated the 2007 German junior champion, receiving a unanimous victory over former German champion Manon Rohrbach at 63 kg, and winning the International German Junior Championships in Berlin by defeating Madelyn Cibis (BC Oberhavel) RSC–1 at 75 kg. In August 2008, she went to Eichstätt in which she competed in the German Women's Championships, where she won silver after defeating Silke Huenecke 28–7 and Janine Hoffmann 19–12, however, once proceeding to the final she lost by one point against Nikolina Orlovic 13–14. Hammer initially finished her amateur career with a record of 22 wins and 1 loss. In February 2021, she returned to the amateur ranks with the intention of competing at the Tokyo Olympics. She failed to qualify for the Tokyo Olympics.
International German Junior Championships
2007
* Defeated Madelyn Cibis (Germany) RSC–1
German National Championships
2008
* Defeated Silke Huenecke (Germany) (27–2)
* Defeated Janine Hoffmann (Germany) (19–12)
* Lost to Nikolina Orlovic (Croatia) (13–14)
Early career
After winning her silver medal at the German National Championships, Hammer had briefly considered competing in the 2012 London Olympics, but her ambition to become a super champion was greater. Hammer made her professional debut at the age of 19 on 12 September 2009 at the Gewerbehof Schlutius in Magdeburg against German fighter Melisa Koktar, whom Hammer defeated via technical knockout (TKO) in the second round. On 24 October 2009 at the Anhalt Arena in Dessau, Hammer won a four-round unanimous decision over Czech fighter Sarka Stoklaskova, who fell to 2-8 (1 KO) with the loss. Until 23 October 2010, she went on to have five more fights in the space of eleven months, defeating Marija Pejakovic, Daniela Bickei, Patricia Braesick, Marie Riederer, and Mihaela Dragan all via knockout within five rounds.
Hammer vs. Perozzi
On 23 October 2010, Hammer stepped up her level of competition and faced Teresa Perozzi for the vacant WBO middleweight title at Erdgas Arena in Riesa, Germany, with the fight shown on Sport1. Southpaw Perozzi began the fight by applying a lot of pressure and setting a fast pace which forced Hammer to think more about defense than in her previous fights. The action was even at first, however, Hammer began to score repeatedly to the head of Perozzi in the later rounds. Perozzi kept trying to press her offense but Hammer's right delivered the better shots in a fight that often looked closer than the scorecards suggested. Hammer won a ten-round unanimous decision 98–92, 97–93, and 97–93 to become the youngest German boxing world champion, and the youngest boxer in history to win a WBO title.
Hammer vs. Kiss
On 18 February 2011, Hammer added the vacant WBF middleweight title to her belt collection, on the undercard of Jan Zaveck defending his IBF welterweight title against Paul Delgado at the Stožice Sports Park in Ljubljana, Slovenia, when Kiss retired in her corner between the seventh and eighth rounds of a scheduled ten-rounder. Hammer started aggressively and used her reach to control the action. In the second half of the fight Hammer increased the pressure and Kiss began to bleed from her nose. During the round break, Kiss signaled to her trainer that she was no longer willing to continue, thus Hammer winning by a TKO.
Hammer vs. Lindberg, Living
On 27 May 2011, at Zlatopramen Arena in the Czech Republic, Hammer defended her WBO and WBF middleweight titles in a ten-round contest against the reigning undefeated WIBA & WIBF light-middleweight champion Maria Lindberg, which Hammer won by unanimous decision, however, Lindberg spoke to WBAN of how she felt the fight was much closer than the official scores 97–93, 97–93, and 98–92. On 21 October 2011, at the Brandenburg Halle in Frankfurt, Germany, Hammer won a ten-round unanimous decision over American Vashon Living, defending her the WBO and WBF middleweight titles. Living, who was at a significant size disadvantage, was mobile and agile as she attempted to get to close quarters and work inside, but Hammer was still able use her reach advantage to control the pace. Hammer landed two accurate uppercuts in the seventh and Living appeared to be worn down by the taller Hammer's blows in the closing rounds.
Hammer vs. Tshabalala, Hernandez
On 5 April 2012, at the Sportovní hala Vodova in Brno, Czech Republic, Hammer made her third defense of her WBF and WBO middleweight titles, in which she impressively dominated the proceedings to retain her titles with a unanimous decision win over Julie Tshabalala of South Africa. Hammer had predicted a knockout victory, with Tshabalala taking the fight on the inside to avoid the long range and hard straight shots from Hammer, who adjusted nicely and countered with hooks and uppercuts. Tshabalala had her best moments in rounds six and seven, and seemed to be catching her second wind, but Hammer was back on top in the final three rounds, making Tshabalala miss and pay for her mistakes. The judges Zoltan Enyedi, Manuel Oliver Palomo, and Andre Van Grootenbruel scored the fight 99–91, 100–90, and 100–90 all in favour of the defending WBF and WBO middleweight champion.
After Hammer beat Tshabalala, it was announced that Hammer would defend her titles at the RWE Rhein-Ruhr Sporthalle in Muelheim, Nordrhein-Westfalen, Germany against Yahaira Hernandez on 7 September 2012. Hammer came in at 70.3 kilograms, while Hernandez weighed a few grams too much in first gear, to which her manager, Daniel Born, acted resolutely and cut off the boxer's pigtails, which resulted in the weight being corrected to the point. Hammer won an overwhelming ten-round unanimous decision over Yahaira Hernandez. Hammer's technical superiority was clear despite a game effort by Hernandez, who was knocked down in the fourth, ninth, and tenth rounds. Hernandez, who had two points deducted for holding as well as 10–8 losing rounds because of the three knockdowns. Afterwards, Hammer spoke of her intention to knock Hernandez out, but she could not do so, though she stated she was happy with her performance. Hernandez was complimentary of Hammer, in which she stated "I was surprised by the toughness of Hammer, and she really hits hard. Her punches felt as if she had rocks in her gloves."
Hammer vs. Zatyko
In April 2013, Hammer announced that she would fight 32 year old undefeated Zita Zatyko, who was considered the best female super-middleweight boxer in the world, on 4 May 2013 for the WBF and vacant WBO female super-middleweight titles. Of the scheduled encounter, Hammer stated that "My goal is to become the best champion in boxing, pound-for-pound, and winning my second world title in two weight classes by beating Zatyko will be another step towards realizing that goal." The date set for the return would mean Hammer would be fighting on the undercard of Wladimir Klitschko defending his WBA (Super), IBF, WBO, IBO, The Ring, and lineal heavyweight titles against Francesco Pianeta at the SAP Arena in Mannheim. Hammer put on a dominant performance and used her superior boxing skills to outbox the heavier Zatyko. In round four, Hammer scored a knockdown, and only the bell saved the visibly hurt, but brave, Zatyko. In the following rounds Hammer went on the attack, but Zatyko weathered the storm and after ten rounds of top-class boxing, judges Patricia Morse Jarman, Zoltan Enyedi, and Oliver Brien scored the fight 100–89, 99–90, and 99–90 all in favour of the new super-middleweight champion.
Hammer vs. Lauren
It was announced on 14 June 2013, Hammer was to drop the extra five and a half pounds to 157 and challenge Mikaela Laurén from Sweden on 13 July 2013, on the undercard of Robert Stieglitz's defense of his WBO super-middleweight title against Yuzo Kiyota at the EnergieVerbund Arena in Dresden. The fight was fought against a backdrop of antagonism displayed by the contender Lauren kissing Hammer at the weigh in, though Hammer laughed off the behavior stating "I have never witnessed anything like this. I hope I could punish her a bit for the kiss." Lauren adopted a particularly aggressive style and by no means hid herself, to which a violent exchange in blows ensued. While it was a tough battle between two world class boxers it was clear that Hammer was the better fighter in almost every round. Lauren tried everything she could to get the upper hand, but Hammer was effective with hard counter combinations and rarely let her opponent get the better of the exchanges. After ten entertaining rounds of boxing, judges Frank Michael Maass, Terry O'Connor, and Alejandro Lopez scored the bout 100–90, 99–91, and 98–92 all in favour of the defending champion, who improved her spotless record to 15–0. As Hammer made her fifth defense of the WBO title by defeating Lauren, the WBO President Francisco Varcarcel awarded her with the WBO Diamond Ring for her exceptional performance.
Hammer vs. Toscano
Following Hammer's middleweight comeback win against Mikaela Laurén in June 2013, Hammer spoke of her desire to fight Nikki Adler next at 168 pounds, albeit excuses on Adler's part, as well as possibly facing Cecilia Brækhus at a catchweight. Hammer remarked that both fighters are in her sights whilst stating "[...] I want to be the considered best female fighter around! I had my step up to super-middleweight and show I can be successful in more than one division but now I am back at middleweight, closer to Anne Sophie's weight class. We are similar in size and this fight can be made [...]" On 6 December 2013, Hammer retained her WBO and WBF female middleweight titles with a first-round knockout over Carmen Garcia Toscano at the Brandenburg Halle in Frankfurt. Both Hammer and Garcia weighed in at an equal 72.5 kg. Toscano found difficulties in approaching Hammer due to her size disadvantages and had already received hard hits in the immediate starting phase. Within the middle of the round, Toscano could no longer avoid the blows of Hammer and was unable to defend himself on the ropes, which is why Referee Ingo Barrabas intervened. After the fight, Hammer stated that a knockout is always the best option, whilst remarking "I'm sorry for the audience that things went so fast. I still have many goals and would like to see some super-middleweight opponents standing in front of me. The future is open."
Hammer vs. Balogun
It was announced on 27 January 2014, that Hammer was set to make her seventh title-defense against challenger Jessica Balogun on 1 March 2014, at the GETEC Arena in Magdeburg. Balogun will be moving up from 147 pounds, but she insisted that the added weight will only make her stronger, that Hammer has never faced anybody with her style, while having full of confidence that she has what it takes to cause an upset. The fight would take place as an undercard fight to the WBO super-middleweight title fight between Robert Stieglitz and Arthur Abraham. Hammer enjoyed a four-inch height advantage over Balogun, a trait which she exploited over the course of the ten-round fight. Hammer appeared relaxed throughout keeping her hard-charging opponent at arm's distance landing at will with straight punches from the outside. Balogun tried to take the fight to the inside against Hammer, but ran into uppercuts and hooks when Hammer adjusted to her tactics, resulting in a one-sided unanimous decision victory 100–90 on all three judges' scorecards. Hammer spoke highly of Balogun's will to fight, whilst remarking "I've shown what I can do, it's not made it easy for me. But I was able to take advantage of my strengths, especially my height.", and Balogun was complimentary of Hammer's boxing ability. With the win, Hammer improved her record to (17–0, 8 KOs), while essentially cleaning out the middleweight division. The match up was promoted by SES Boxing and televised live in Germany on Sat.1, which averaged 4.20 million viewers while obtaining 23.9% of the market share.
Hammer vs. Mathis
On 8 June 2014, Hammer was on Cecilia Brækhus' list as a possible opponent, alongside Alejandra Oliveras and Ivana Habazin, to which Brækhus stated "[...] she also want me in the ring. She has said she will not box outside Germany, now I boxed in Germany, so maybe she will be more interested now." In June 2014, it was announced that Hammer would face the former multiple world and European champion Anne Sophie Mathis (27-3-0, 23 KOs) for the WBF and vacant WBO junior-middleweight titles on 26 July 2014 at the Anhalt Arena in Dessau. On 23 June 2014, at the SES Boxing Gala, Hammer spoke of her of love challenges and to set new standards in women's boxing, while also speaking of Mathis "I want to set new standards in women's boxing. Mathis is, of course, in this new weight class for me a real size with a huge knockout ratio. I put out the challenge to fight the best. There are enough women who runaway repeatedly in front of me." Hammer moved her training camp from Germany to the mountains of Tyrol, Austria, for a few days to engage in high-altitude training with coach Dimitri Kirnos in preparation.
In a relatively balanced fight between Hammer and Mathis, Hammer was clinching after an exchange in the fifth round, to which Mathis landed several blows with her right hand to Hammers left ear. Suddenly, Hammer went down to the canvas and struggled to come back to her feet. The assigned referee, Manfred Kuechler, failed to count Hammer out who required 25 seconds to erect herself properly from the canvas. Instead, Kuechler ruled the punch that knocked Hammer down an illegal blow to the back of the head and disqualified Mathis. Hammer won the WBF and vacant WBO junior-middleweight titles via a controversial DQ over Mathis. Due to Hammer's excessive clinching, Mathis legally used her free hand to land blows to the side of Hammer's head, sending her to the canvas. The slow motion replay showed that it was Hammer who was fouling by holding Mathis' left arm and still got knocked out. Fans were outraged and declared that Mathis had been robbed of a KO victory. Mathis herself was very upset about being disqualified, as she knew that her punches were legal. "It's shameful! I never imagined it could end like this [...] For me, I won this fight. I won it by knockout! I began to build up and I felt that she was out of breath. She spent the first four rounds hanging her arm and she was not notified. [Rene Cordier] kept telling me: hit anyway with the other arm! And by the time I get past my hook [...] I touched her in the ear, that's why she fell." Hammer celebrated her titles, however, she was saddened by the result, in which she stated: "That was an unfair thing to do with her [...] but I can not leave such a victory on me - the thing needs to be sorted out.", while remarking she does not want to become a champion through disqualification.
On 28 July 2014, the World Boxing Federation's declared the bout a 'no-contest' and restored the WBF light-middleweight title to Mathis, with Martin André, the president of the French Boxing Federation, stating he was going to make a complaint to the WBO, to validate the victory of Mathis and that he was ready to ban the WBF in France. On 29 July 2014, The sanctioning commission, the Bund Deutscher Berufsboxer (BDB; Association of German Professional Boxers), followed the WBF decision and officially changed the bout outcome to 'no-contest'. BDB President Thomas Pütz apologised for the "bad decision" and stated that there will be an investigation of the said event and a hearing of Manfred Küchler to decide whether he will be suspended. On 7 August 2014, after reviewing the bout, the WBO agreed with the WBF and BDB and declared it a 'no-contest' and did not order a rematch since Hammer is the organization's reigning middleweight champion.
Hammer vs. Reis, Lazar
On 23 January 2015, it was announced that SES Boxing will present its milestone 100th boxing event on 7 March at the Maritim Hotel in Magdeburg, with Hammer being included on the card. On 27 January 2015, it was announced that Hammer would make her eighth defense of her WBO title at the Maritim Hotel in Magdeburg against world No. 2 Kali Reis. In March 2015, the flu epidemic in Germany had caused Hammer and several other fighters to cancel their scheduled fights at the Maritim Hotel for 7 March, which was later changed to 5 May. At the weigh-in, Reiz, 29 at the time of the fight, weighed in at 155 and a half pounds, the heaviest she had weighed professionally; Hammer, 24, came in heavier at 157 and three-quarter pounds. After the weigh-in, Hammer spoke of Reis' habit of "[going] forward, is aggressive and usually wants to take the fight in. But she will not succeed with me, I'm better and I'm number 1 [...] I'm merciless." Hammer dominated Reis in all respects for nine rounds, being much faster on her feet. And she took advantage of her greater range, built with the grueling left-hand guide, with which she kept her opponent at a distance, being a significant advantage round after round. However, just before the end of the tenth round, a right hook from Reis hit the temple of Hammer and she went down. Hammer came to her feet quickly, bringing the fight controlled to an end, with Jose Ignacio Martinez Antunez, Frank Michael Maass, and Matteo Montella scoring the bout 98–91 to secure Hammer a unanimous decision victory. After the fight, of her knockdown, Hammer stated: "That's how it is in boxing, one second of inattention, and it's all over. You can only learn from it."
In February 2016, at the Dortmund Sportsman of the Year awards, Hammer spoke of her intention of fighting for the WBC title, as well as possibly moving up to super-middleweight, with conformation in June 2016 that Hammer will have an eight-round bout and within October a world title fight. Hungarian Melinda Lazar became a front runner to challenge Hammer, to which, on 20 June, it was confirmed to take place at the Ballhaus Forum in Munich on 15 July. This would make Hammer's first time fighting at the arena and her first fight in fourteen months. Lazar already sent Hammer to the canvas in round two, though otherwise Lazar struggled against the better technique, greater range and strength of Hammer, to whom moved through the ring dynamically and aesthetically, but ultimately Lazar could not keep up. In the sixth round, Lazar's trainer threw in the towel to protect his fighter. Speaking after the fight, Hammer said, "It was not that big of an opponent, but everything was going according to plan for me and now it can only go up and now I want to fight Nikki Adler and become world champion again."
Hammer vs. Reis II
In September 2016, Hammer mentioned possible opponents for her next bout being WBC Silver champion Kelly Morgan, while mentioning a rematch with WBC champion Kali Reis to unify the WBO and the WBC titles. On 20 October 2016, it was announced that Hammer would face WBC champion Kali Reis at the Ballhaus Forum in Munich on 5 November. The smaller Reis was very aggressive from the opening to the final bell, kept moving forward and had her moments landing hard hooks to Hammer's head and body. But for most of the ten rounds Hammer managed to keep the distance, establish her jab and fight well from the outside. After ten entertaining rounds judges Ed Pearson, Fernando Laguna, and Grzegorz Molenda unanimously scored the bout 98–93, 98–93, and 100–90 all in favour of Hammer. According to CompuBox, Hammer's usage of her mobility and prolific jab allowed for 24.4 attempts/3.8 connects per two-minute round, while slowing the pace to a comfortable level in wh/ich she averaged 39.7 punches per two-minute round and limited Reis to 33.4. Speaking after her unification, Hammer said "I have been waiting for this moment for a very long time [...] Like every fighter in the world I dreamed of becoming a WBC world champion and winning the green and gold Belt. This is a very special moment for me. I thank all my fans and my team for the fantastic support."
Hammer vs. Lindberg II, Ankrah
On 27 February 2017, it was announced that Hammer would rematch Maria Lindberg (15-2-2, 8 KO) to make her first defense of both the WBO and WBC unified middleweight titles, on the undercard of Marco Huck's defense of his IBO and vacant WBC cruiserweight titles against Mairis Briedis at the Westfalenhallen in Dortmund on 1 April. Of the encounter, Lindberg stated that "Hammer is difficult to box. But I'm a better boxer than 2011 and I think I'll have a good chance against her. This is my last chance for a big title and I'm ready to use it." While Hammer also noted that Lindberg is indeed a tough opponent "[...] And of course I know that I can not rely only on the support of the audience. I'm going to work so hard like never before and get ready to get in the ring." At the weigh-in, Lindberg, 29 at the time of the fight, weighed in at 154 and a quarter pounds, the heaviest she had weighed since 2015; Hammer, 24, came in heavier at 158 and three-quarter pounds. Hammer had no issues whatsoever with Lindberg, handily outboxing her shorter opponent from range. In front of a crowd of 17,000 in attendance, Lindberg simply could not get past Hammer's stinging jab and the combinations she put together behind them, ultimately losing all ten rounds on all three scorecards, with judges Massimo Barrovecchio, Guido Cavalleri, and Eddie Pappoe scoring the fight 100–90 all in favour of the defending WBO and WBC champion. In the post-fight interview, Lindberg stated, "Hammer is difficult to box [...] I tried to get in to her but it didn't succeed and it didn't get any better when I got her skull in the middle of my nose, thinking it was in the fourth round. One is not particularly keen on going into stroke switching with a broken nose. It made a lot of pain during the rest of the match." After the fight, Hammer spoke of how fighting in her hometown of Westfalenhalle was a dream come true, while stating she wants to realise her next dream and go to the US. At the subsequent press conference, Hammer's manager Harald Pia announced that Hammer's next series of fights will take place in America, to eventually culminate with an eventual showdown with Olympic champion Claressa Shields. On 31 October 2017, it was reported by Pia that Hammer has a concrete offer for four bouts in America, all being transmitted by either HBO or Showtime.
On 4 November 2017, Hammer retained her WBO and WBC middleweight titles with a fourth-round knockout win over Gifty Amanua Ankrah at the SportScheck Allwetteranlage in Munich. Of her encounter with Ankrah, Hammer stated: "[...] I have to beat [Ankrah], step by step, fight by fight [...] I am very well prepared, I know what I have to do, I am in my area in the ring, I feel good there." Hammer brutally stopped Ankrah with a brutal right at the end of the fourth round, which sent her to the canvas. Ankrah stood up, trying to continue in the contest, but her legs were shaking and the fight was suspended by referee Juergen Langos. In the post-fight interview, Hammer praised Ankrah's toughness by stating, "[Ankrah] is a very tough boxer, I've never felt a head harder than hers. My hands hurt, it was a good test and a good warm-up for my trip to the United States.", while hoping that Shields watches fight tape to know what is coming for her.
Hammer vs. Nelson
On 14 December 2017, The Ring reported that Hammer will make her U.S. debut on 12 January, against Lisa Noel Garland (15–9, 8 KOs), with the fight to take place at the Turning Stone Resort & Casino, in Verona, New York, with Hammer stating: "The U.S. debut is very important for me; I want to show that I'm the real deal in female boxing. Ever since I won my first title, it has always been a dream of mine to fight in the U.S.A [...] I want to fight both Cornejo and Shields in the future. I train hard and I'm ready to fight everyone." On 18 December 2017, Dmitriy Salita announced of Hammer to a multi-fight promotional contract with Salita Promotions, with Hammer making her US debut 12 January 2018 at the Turning Stone Resort Casino in Verona, New York. In January 2018, The Ring reported that Hammer was due to appear on the undercard of Claressa Shields vs Tori Nelson on 12 January, however, due to a delay in her work via, Hammer will have to wait to the spring for her United States debut. On 24 April 2018, The Guardian announced that Hammer was set to defend her WBO and WBC middleweight titles against former champion Tori Nelson at the Detroit Masonic Temple in Detroit, Michigan, on 22 June, with the fight shown on Showtime.
After the announcement, Hammer had revealed she spent much of her camp in Tyrol, Austria, to engage in high-altitude training in preparation for Nelson. At the official weigh-in, a day before the fight, Hammer tipped the scales at 159.5 lbs, while Nelson weighed 157.5 lbs. Hammer smartly exploited her height and reach advantages by keeping the fight at long range but moving inside just often enough to win the majority of the exchanges. Her typically excellent jab landed with frequency, and with heavier force than in past fights, and her right hand connected with enough impact to make the point but not enough to upend Nelson, ultimately resulting in judges Katealia Chambers, Benoit Roussel, and Pasquale Procopio scoring the fight 99–91, 99–91, and 100–90 all in favour of the defending WBO and WBC champion. Hammer's defeat of Nelson made her the first German fighter to successfully defend a world title in the US since Max Schmeling successfully defended his heavyweight title against Young Stribling at the Municipal Stadium, Cleveland, Ohio, in 1931. Statistically speaking, according to The Ring, Hammer was superb: Averaging 46.6 punches per round, while limiting Nelson to 31.8, she prevailed 103-56 overall, 44-18 jabs and 59-38 power. The accuracy figures were sub-par (22% overall, 19% jabs, 26% power) but her defensive skills limited Nelson to just 18% overall, 16% jabs and 19% power. Also with the fight already in hand, Hammer throttled down from 53 punches in round nine to 36 in the 10th. In the post-fight interview, Hammer spoke of attempting to get the knockout, though praising Nelson's toughness, though she continued by stating: "I'm really looking forward to fighting [Shields]. She will try and fight me on the inside but my footwork and my reach will make the difference [...] It will be the biggest women's fight ever. I would like to fight her at a neutral site." On 24 April 2018, Dan Rafael of ESPN stated that Hammer and Shields, both being victorious, will fight for the undisputed middleweight title this fall on Showtime.
Hammer vs. Shields
From March 2017 up until the end of August 2018, both camps of Hammer and Shields were in deep talks around the super fight to finally take place. On 25 September 2018, The Ring announced that Hammer and Shields will fight for undisputed middleweight championship at the Adrian Phillips Theater at Boardwalk Hall in Atlantic City, New Jersey, on 17 November, with the winner becoming the second woman of the four-belt era to hold all the titles in one division. Of the announcement, Hammer remarked: "I am the best middleweight in the world and will make that point very clear when we get in the ring. It's been my dream to fight in the biggest women's fight of all time and raise women's boxing to an all-time high. I will be crowned the undisputed middleweight queen [...]" On 2 October 2018, Dan Rafael of ESPN reported that an undisclosed medical condition had forced Hammer to postpone her fight with Shields for the undisputed championship. On 5 October the WBC stated that Hammer suffered from a digestive ailment, making her medically unfit to box for the foreseeable future. The WBC named Hammer champion in recess, while Shields will fight for the vacant title on 17 November against Hannah Rankin.
On 27 January 2019, it was announced that Hammer would fight Elene Sikmashvili at the Verti Music Hall in Friedrichshain on 9 February, as Hammer wished to box in Germany before fighting Shields sometime in 2019. The eighth-round fight was decided by technical knockout in the second round after thirty-five seconds, with Hammer stopping Sikmashvili. On 12 February 2019, it was announced that Hammer and Shields will meet for the undisputed championship on 13 April at the Adrian Phillips Theater at Boardwalk Hall in Atlantic City, New Jersey, with The Ring female middleweight title also being contested. After the announcement, Hammer revealed she spent much of her camp at Seefeld in Tyrol, Austria, to engage in high-altitude training in preparation for Shields. The official press conference took place on 26 February, with Hammer remarking the big risk to come from Germany to the U.S, while stating: "[...] I believe the best should fight the best and I did what I had to so that this could happen. This fight can be a game changer for our sport."
On 13 April 2019, Hammer lost the WBC and WBO titles via unanimous decision in her bid to become the undisputed women's middleweight champion. All three judges scored the bout 98–92 in favour of Shields.
Personal life
Hammer has lived in Dortmund, Germany, since 2009. In July 2012, Hammer received her certificate of having passed her Abitur, which allowed her to study sports science at the University of Applied Management in Unna. While in her sixth-semester at the University of Hagen, in 2016, she stated she makes a great effort to complete her studies while boxing. She is a brand ambassador for the underwear line Anita, for which she occasionally models, while also being a part of Movement130, which encourages females of all shapes, sizes, and lifestyles to embrace their own distinctive beauty. In 2017 Christina Hammer and SOFTSWISS launch an iGaming service in partnership with WBC. Hammer is a patron of Vive Žene, a facility for refugees, threatened girls, and young women at the Ossenbrink in Herdecke, with the Dortmund Equality Office suggesting that "a female boxer is just right to express power and power." While becoming the first female boxer to own an online casino, she donates 5% of her online casino income to World Boxing Cares and to the Jose Sulaiman Relief Fund for needy boxers, to which she became a WBC Ambassador, whereby she stated: "My Casino will use its popularity also as a platform for good works. I am very impressed with WBC Cares and their work for global good, particularly children [...] it's my privilege to give back."
|
WIKI
|
Wilmington Mesothelioma Cancer: Symptoms, Causes, and Treatment
A Rare and Aggressive Form of Cancer
Asbestos has been widely used in various industries worldwide for decades. While its use has declined in recent years, the consequences of past exposure remain a concern. One of the most severe health risks associated with asbestos exposure is mesothelioma cancer. Wilmington, a city in Delaware, is currently facing one of the highest incidences of mesothelioma in the US. This article provides essential information on the causes, symptoms, and treatment of wilmington mesothelioma cancer.
What is Wilmington Mesothelioma Cancer?
Mesothelioma is a rare but deadly form of cancer that affects the lining of the lungs, heart, and abdomen. It develops due to prolonged exposure to asbestos fibers, which can cause abnormal cell growth and mutations. The cancer has a long latency period, with symptoms typically appearing many years after exposure.
Causes of Wilmington Mesothelioma Cancer
Asbestos exposure is the primary cause of mesothelioma cancer. Wilmington has a high incidence of mesothelioma cases due to the city’s heavy industry and shipyards, which used asbestos extensively. People who worked in these industries or lived in areas contaminated with asbestos were at significant risk of developing the disease.
Asbestos Exposure at Work
People who worked in shipyards, construction sites, and manufacturing industries that use asbestos-containing products are at high risk for mesothelioma. Workers may have been exposed to asbestos fibers through the air, water, or soil. Even short-term exposure can cause mesothelioma cancer to develop.
Secondary Asbestos Exposure
Family members of workers who were exposed to asbestos may also develop mesothelioma. For instance, a worker may bring home asbestos fibers attached to their clothing, causing secondary exposure to their loved ones.
Environmental Exposure
Asbestos naturally occurs in the environment, and people living near asbestos mines or contaminated areas are at risk of developing mesothelioma cancer.
Symptoms of Wilmington Mesothelioma Cancer
Mesothelioma symptoms can vary depending on the type of cancer and the location of the tumor. Early detection is crucial in treating mesothelioma cancer effectively. The following are the most common symptoms of wilmington mesothelioma cancer:
Symptoms Description
Chest pain A sharp, persistent pain in the chest
Shortness of breath Difficulty breathing, even during rest
Fatigue A feeling of extreme tiredness or weakness
Coughing A persistent cough that worsens over time
Weight loss An unexplained loss of weight
Diagnosis of Wilmington Mesothelioma Cancer
Mesothelioma is challenging to diagnose due to its long latency period and the fact that the symptoms may mimic those of other respiratory diseases. A doctor may order the following tests to confirm a mesothelioma diagnosis:
X-Rays and CT Scans
Imaging tests such as X-rays, CT scans, or MRIs can detect the presence of tumors in the lungs or abdomen.
Tissue Biopsy
A biopsy involves removing a small sample of tissue from the affected area and examining it under a microscope. This test can confirm the presence of cancer cells and determine the type.
Treatment of Wilmington Mesothelioma Cancer
The treatment options for mesothelioma cancer depend on the stage, location, and type of cancer. The following are the most common treatments for wilmington mesothelioma cancer:
Surgery
Surgeons may remove part or all of the affected lung, lining of the chest, or abdomen to treat mesothelioma.
Chemotherapy
Chemotherapy involves using drugs to destroy cancer cells in the body. It can be used before or after surgery or as a stand-alone treatment.
Radiation Therapy
Radiation therapy uses high-energy radiation to shrink tumors and destroy cancer cells. It may be used in combination with surgery or chemotherapy.
FAQs About Wilmington Mesothelioma Cancer
Q: What is the average life expectancy for mesothelioma patients?
A: The average life expectancy for mesothelioma patients ranges from 12 to 21 months.
Q: Can mesothelioma cancer be cured?
A: Currently, there is no cure for mesothelioma cancer. However, early detection and treatment can significantly increase the patient’s lifespan.
Q: Can mesothelioma cancer be prevented?
A: The only way to prevent mesothelioma cancer is to avoid exposure to asbestos fibers.
Q: Is wilmington mesothelioma cancer hereditary?
A: No, mesothelioma cancer is not hereditary.
Q: Can mesothelioma cancer be treated with alternative therapies?
A: While some alternative therapies may help manage mesothelioma symptoms, they should not be used as a substitute for conventional medical treatment.
Q: Can asbestos exposure cause other health problems besides mesothelioma?
A: Yes, exposure to asbestos fibers can cause other respiratory diseases such as lung cancer and asbestosis.
Q: Are all types of asbestos dangerous?
A: Yes, all types of asbestos are dangerous and can cause mesothelioma and other respiratory diseases.
Conclusion
Wilmington mesothelioma cancer is a deadly disease that affects many lives each year. While there is no cure for the disease, early detection and treatment can significantly increase the patient’s quality of life. If you or your loved one has worked in an industry that used asbestos or may have been exposed to asbestos fibers, it’s essential to seek medical attention immediately.
Don’t wait until it’s too late. Contact a mesothelioma specialist today for diagnosis and treatment options.
Disclaimer
This article is not intended to be a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or other qualified healthcare providers with any questions you may have regarding a medical condition. Do not disregard professional medical advice or delay seeking it because of something you have read in this article.
|
ESSENTIALAI-STEM
|
using tee to echo to a system file with sudo privileges
It is always a good practice not to execute privileged by logging as root. We can avoid
that by executing with sudo privileges. Many times , we need to change kernel parameter
for changing the behaviour of a Linux system . Like recently there was a need for me to
change the CPU governor from 'userspace' to 'ondemand' on a Linux system.
I have to use the following command to complete the task .
$ sudo echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
We have to execute the command as priviliged user , so I was trying to do it using sudo . But it was failing with the following error. But if I do by logging with uid=0 , then it succeeds . But I want to su - to root.
$ sudo echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
-bash: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: Permission denied
This was because the above command has two parts and we are using sudo on the first part (sudo echo userspace) , which itself does not need sudo as we are just echoing. In the second part , we are writing to a system file ( > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ) as a normal user
which will not be allowed.
tee is the command which can help us to execute the above command without logging as root. As per man page, tee read from standard input and writes to standard output and files.
$ echo ondemand | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand
$ sudo cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
ondemand
So, in the above command , tee is reading from pipe and write to the system file with sudo . Using cat , I verified the value of the system file and I could see the value changed from userspace to ondemand.
That's it , we are done.
Comments
Popular posts from this blog
PSSH : Parallel SSH to execute commands on a number of hosts
How to add check_http as a service in Nagios Monitoring using NRPE
Using lsof to identify deleted files:
|
ESSENTIALAI-STEM
|
Sibiryakov
Sibiryakov is a Russian (Сибиряков) or Ukrainian (Сібіряков) surname.
Notable people with the surname include:
* Alexander Sibiryakov (1849-1933), Russian gold mine and factories owner and explorer of Siberia
* Andrei Sibiryakov (1964-1989/1990), Russian serial killer
* Eduard Sibiryakov (1941–2004), Russian volleyball player
* Serhiy Sibiryakov (born 1982), Ukrainian-born Russian footballer
|
WIKI
|
Ureteropelvic junction obstruction with primary lymphoedema associated with CELSR1 variants
Many genes have been linked to primary lymphedema, yet they currently explain only about 30% of the patients. Moreover, there is no cure for the disease yet. A better understanding of the underlying causes should enable the development of novel therapeutic approaches. In this study, we have detailed the clinical phenotype of patients with CELSR1 pathogenic variants, a confirmed higher penetrance in females compared to males, identified an unrecognized association with renal defects, and suggested CELSR1 as the gene behind renal problems observed in the Phelan-McDermid syndrome. We suggest CELSR1 to be included in routine genetic testing for patients with lymphedema and/or renal anomalies. (By Murat Alpaslan, M.Sc., https://jmg.bmj.com/content/early/2023/05/24/jmg-2023-109171 )
(Visited 11 times, 1 visits today)
|
ESSENTIALAI-STEM
|
B4J Tutorial What is B4J?
Erel
Administrator
Staff member
Licensed User
Unless you are calling any platform specific APIs then your program should run as is on any of the supported platforms.
Currently it is not possible to remote debug an application. Though if there is a real need then it can be added in the future.
Erel
Administrator
Staff member
Licensed User
Most of the libraries are included in the installation file. You should be able to download the other B4J libraries from the forum (don't confuse Basic4android libraries with B4J libraries).
Erel
Administrator
Staff member
Licensed User
The UI apps are based on JavaFX. JavaFX is not available in j2me.
Mwinsor
Member
Licensed User
Erel, You said that a B4 tool wasn't on the agenda for iPhone. Is that something we members can change since I would be more then interested to buying it, even if its just for mac?
I would agree. One environment to create android and ios apps would be awesome. I presume there are some Apple applied obstacles in the way of this however.
Erel
Administrator
Staff member
Licensed User
You should post it in a new thread. This thread is about B4J...
Erel
Administrator
Staff member
Licensed User
You are referring to Java applets. Java applets are not supported. Java applets is more or less a "dead" technology due to endless security issues.
You can however implement a web server with B4J. Soon it will be quite simple to create web apps with B4J (requiring a server as well).
spaceman
Member
Licensed User
Top
|
ESSENTIALAI-STEM
|
3 Reasons to Invest in Renewable Energy Stocks
It can be hard to ignore politics. But for investors, focusing on the performance and prospects of a business is the best way to beat the market regardless of administration or policy. That's even true for companies operating in the renewable energy space.
Most governments have some policy of reducing their carbon emissions. And the International Energy Agency (IEA) says now is the time for massive investment in clean energy if we are going to meet those targets. That creates an opportunity for companies like First Solar (NASDAQ: FSLR), Siemens Gamesa Renewable Energy (OTC: GCTAY), and NextEra Energy (NYSE: NEE). They are harnessing renewable sources to replace fossil fuels as our growing energy needs. Here's why I think they can be winners.
Image source: Getty Images.
1. The earth is getting hotter
That fact is indisputable. According to reports published in Scientific American, it's hotter than it has been in 125,000 years, and the planet is heating up at the fastest rate in tens of millions of years.
The sun is the source of heat, but it can also be the savior. One of the most innovative companies harnessing its power is First Solar. It is the leading producer of thin film solar panels using cadmium telluride. That material makes the panels significantly thinner than silicon cells. They are also more efficient. Panels with cadmium telluride only supply about 5% of the global solar market, but they make up 40% of the installed base in the U.S.
Years of dealing with cheap silicon-based imports from China have made holding the shares feel like a yo-yo. The stock has made little progress since 2014. But the Trump administration placed tariffs on some Chinese imports in 2018, and the Biden administration banned others over concerns about forced labor.
In February, the White House extended some of the tariffs -- but not all of them. CEO Mark Widmer expressed disappointment in the decision. And analysts expect sales to remain volatile. But over the long term, First Solar is still well-positioned as the technology leader. If the U.S. is successful in meeting its carbon reduction goals, it's likely that an investment in First Solar will be successful too.
2. Countries have pledged to be carbon neutral
Although countries have debated the details, most have committed to becoming carbon neutral at some point in the future. Unfortunately, even if all of the commitments in place as of 2020 were fulfilled, the planet would still warm by 3.2 degrees Celsius by the end of the century, according to a recent United Nations report. It will take both commitment and innovation to achieve the goals.
And a European partnership is thinking big about how to use the wind to generate more power. Siemens Gamesa was formed when the German conglomerate took a stake in a Spanish firm making wind turbine blades. Together, they formed the largest windfarm builder in the world.
Things haven't gone smoothly. Supply chain issues and problems with an onshore turbine design have put the firm in the red and led to the CEO's ouster. A buyout to gain control could be in the cards.
Despite the problems, there is reason to be excited. In Denmark late last year, the company installed the world's most powerful -- and largest -- turbine. The diameter of the rotor measures 222 meters, with each 108-meter blade being cast in one piece. The company hopes to make them commercially available by 2024. Innovation like that -- at scale -- could go a long way toward meeting the world's energy needs.
3. Fossil fuels still dominate electricity production
Change doesn't happen overnight. And traditional energy sources like coal and natural gas still dominate global electricity production. But the U.S. is making progress.
Since the turn of the century, nearly all of the extra electricity generation in the U.S. has come from wind and solar. And NextEra Energy has played a big part in that.
In 2000, management attributed 15% of its power generation to wind and did not even mention solar as a source. By 2020, the combination of solar and wind had grown to more than 27%. That's made it the world leader in energy generation from wind and solar. As the U.S. tries to set an example for the world, NextEra is setting an example for the U.S.
Technology to the rescue
Over time, humans have consistently employed new technologies to solve our most important problems. Famine, drought, and disease spring to mind. Now we face what most scientists consider to be an existential threat. A recent United Nations report -- considered the gold standard -- showed how global warming is affecting the planet's ecosystem. It estimated that 14% of earth's living species are at risk of going extinct.
That leads me to believe society will eventually coalesce around a strategy that increasingly relies on wind and solar. When that happens, the companies already leading the industry stand to reap outsized rewards. And according to most scientific bodies, the investment can't start too soon.
10 stocks we like better than NextEra Energy
When our award-winning analyst team has a stock tip, it can pay to listen. After all, the newsletter they have run for over a decade, Motley Fool Stock Advisor, has tripled the market.*
They just revealed what they believe are the ten best stocks for investors to buy right now... and NextEra Energy wasn't one of them! That's right -- they think these 10 stocks are even better buys.
See the 10 stocks
*Stock Advisor returns as of March 3, 2022
Jason Hawthorne has no position in any of the stocks mentioned. The Motley Fool owns and recommends NextEra Energy. The Motley Fool recommends First Solar. The Motley Fool has a disclosure policy.
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.
|
NEWS-MULTISOURCE
|
Wikipedia talk:Articles for deletion/List of League of Legends Champions
Why deleting it? imo should be linked to the League of Legends page because it's NOT a game guide as you said, these voice helps to explain the lore of League of Legends
|
WIKI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.