User:Bawolff/Edit COI Summary/15 per page (alphabetical)/34

Cannot transclude talk pages due to post expand include size limit. Please visit individual talk pages to see the discussion.

• World Obstacle
• Worthington Enterprises
• Wyss Foundation
• XMPP Standards Foundation
• Yahya Kemal College
• Yehuda Kahane
• Yfke Sturm
• Young Democratic Socialists of America
• Yuri Buzzi
• Zelle
• Zscaler

---

← Previous page

World Obstacle

Formal COI edit request: Disputed terms OCR / World OCR, invalid AIMS.SPORT reference, and active references to a dissolved entity

We are posting from the official World OCR account and disclose that our organization is directly affected by this article. For that reason, World OCR is not directly editing the article. We request review and correction by independent editors.

This is a formal conflict-of-interest edit request concerning materially disputed statements in the article about World Obstacle/FISO, specifically where the article addresses OCR, World OCR, AIMS member status, and the current references to the European Obstacle Sports Federation.

World OCR is not requesting promotional treatment and is not asking editors to remove information about World Obstacle/FISO generally. The request is narrower: the article should not present disputed or unsupported OCR-related governance claims, AIMS affiliation claims, or European governance references as settled facts in Wikipedia’s voice.

We request review of the following points:

1. Active AIMS affiliation / membership

Current wording to review:

“World Obstacle is a member of the Alliance of Independent Recognized Members of Sports”

Requested correction:

Remove the statement, or qualify it as an attributed claim only if supported by the AIMS itself. The article should not state in Wikipedia’s voice that World Obstacle/FISO is a member of AIMS unless current authoritative evidence confirms this.

Reason:

World OCR has documentary correspondence from AIMS dated 10 September 2024 stating that there are no obstacle-sport international federations within AIMS members and that the relevant federation is not a recognized member of AIMS. If editors require verification, World OCR can provide the official correspondence between one of our law firms with the President of AIMS at that time, Mr. Stephan Fox.

2. European Obstacle Sports Federation / European governance

Current wording to review:

“World Obstacle members are composed of national member federations administering obstacle course racing in each country. Each national federation belongs to one of the four continental confederations. Each of the continental confederation offers a continental championship. As of 2022, the continental confederations are:

• The Obstacle Sports Federation of Africa (OSFA) – 12 national federations
• The Pan American Obstacle Sports Federation (PAOSF) – 22 national federations
• The Obstacle Sports Federation Asia Pacific (OSFAP) – 30 national federations with sub-continental regions including Obstacle Sports Federation South East Asia, Obstacle Sports Federation Central and Western Asia, and Obstacle Sports Federation East & South Asia and Pacific.
• The European Obstacle Sports Federation (EOSF) – 30 national federations**. Sub continental associations for Nordic Countries (Denmark, Finland, Norway, Sweden) and Central Europe (Czech Republic, Hungary, Poland, and Romania) were initiated in 2022. * Sub-continental regions for Asia-Pacific were formalized the 2021 OSFAP Congress. ** Originally formed an association of European organisations prior to the 1st OCR European Championships June 10–11, 2016, EOSF was incorporated as the European Obstacle Sports Federation on 8 April 2017 at Olbia, Sardegna, Italy.”

Requested correction:

Remove or qualify any wording that presents the European Obstacle Sports Federation as an active European confederation, governance body, or sanctioning authority unless current official registry evidence confirms that it is active and legally capable of operating in that role.

Reason:

Official Irish registry records indicate that the European Obstacle Sports Federation entity is dissolved. World OCR has also contacted the Irish Corporate Enforcement Authority (CEA) authorities concerning this issue, and they are about to be audited within the next two months. The article should not present the entity as operational or as a current sanctioning/governance body if that status is contradicted or materially disputed by official records.

3. OCR / World OCR wording references

Current wording to review, and requested for correction:

Replace broad wording that presents World Obstacle/FISO as the international governing body/authority for sporting activities defined as OCR, and eliminate World OCR-related wording. Examples:

“World Obstacle/FISO describes itself as ["...the international governing body for obstacle sports and related events. Disciplines include Ninja (similar to Sasuke and American Ninja Warrior) and obstacle course racing (OCR)."], while OCR-related governance and rights are disputed by World OCR, a separate Swiss-registered international federation, that governs the OCR as a standalone sport.” "To provide more autonomous governance of obstacle sports worldwide, World OCR changed its name to World Obstacle in October 2020. This provided a more inclusive name for the core sports of Ninja, OCR and adventure racing.[11]" For clarity, the organization identifying as World Obstacle, should provide document-based proof that is was previously registered as "World OCR". For further clarity, we are not requesting a general explanation or informal statement. We are requesting document-based evidence for the claims made publicly on Wikipedia.

We would like to point out that World OCR is a separate Swiss-registered international federation, and holds documented exclusive EU-level wordmark enforcement rights in relation to OCR, WORLD OCR, as well as OCRATHLON, through an exclusive agreement with the EUIPO registrant of the OCR and OCRATHLON marks. The article should therefore avoid stating or implying, in Wikipedia’s own voice, that World Obstacle/FISO is the uncontested global authority for OCR or World OCR-related activity, because it is highly misleading and damaging to our organization. EUIPO certificates can be provided upon request.

4. UIPM/FISO dissolution and transition

Current wording to review:

“[World Obstacle has worked with the Union Internationale de Pentathlon Moderne (UIPM) on its replacement of show jumping with obstacle racing in the modern pentathlon.]”

Requested correction:

Update the article to reflect, with attribution, that the organization presenting itself as the international governing body for all obstacle sports (FISO/World Obstacle) has voted to dissolve and integrate into UIPM, with the effective date stated by UIPM/FISO as 10 August 2026. This should be presented as a UIPM/FISO organizational transition, not as proof that all obstacle-sports-related organizations, trademarks, events, or independent OCR development pathways worldwide are absorbed into or controlled by the UIPM/FISO integration group. This is an attempt to create an overreach in international sports governance, and should not be permitted.

Reason:

While the UIPM/FISO integration may be relevant from the Obstacle Discipline perspective, which is one of the 5 disciplines of Modern Pentathlon, that should not suggest or imply - IN ANY WAY - that World OCR as an organization, or that OCR and OCRATHLON as independently developing sports, will cease to exist ,and be governed on a separate pathway.

World OCR kindly requests that independent editors to:

• remove or qualify any AIMS membership/recognition claim unless current authoritative sourcing confirms it;
• remove or qualify references presenting the European Obstacle Sports Federation as an active European governance or sanctioning body unless current official registry evidence confirms that status;
• avoid wording that presents World Obstacle/FISO as the uncontested authority for OCR, OCRATHLON, or World OCR-related matters;
• attribute broad UIPM/FISO governance claims rather than stating them as uncontested facts in Wikipedia’s voice;
• add a neutral note, if editors consider appropriate, that OCR-specific governance and rights are disputed by World OCR.

World OCR is willing to provide public links, official registry records, and documentary evidence to assist independent editors. We ask that the article be reviewed urgently because the disputed statements affect athletes, event organizers, public authorities, sponsors, insurers, and sport-governance stakeholders.

~~~~ World OCR (talk) 09:19, 7 June 2026 (UTC)

Worthington Enterprises

Edit Request

{{edit COI|R}}

I am requesting some significant updates to this Worthington Enterprises Wikipedia page, as the company has undergone many changes in the past 12 months and the information currently in place is not accurate. In full transparency, I am an employee of Worthington Enterprises (see my user page for COI designation) and will do my best, with the use of a variety of reputable sources, to present the information in an unbiased manner as my intent here is to simply to make edit requests that reflect the company more accurately.

To provide more detail (and as is included in my request below), on December 1, 2023, the company, formerly Worthington Industries, completed the planned spin-off of its Steel Processing business and officially split into two independent companies: Worthington Enterprises and Worthington Steel. Therefore, the references to metals processing and steel-related information is outdated. I have also included these reasonings in the updates to the History section. The sidebar will also need updated accordingly but I will begin with the main content.

My requested edit to the page is as follows:

Worthington Enterprises, Inc. (formerly Worthington Industries) is an industrial manufacturing company headquartered in Columbus, Ohio. The company is comprised of two business segments, Consumer Products and Building Products. Within these segments, the company designs and manufactures pressure vessels such as propane, oxygen and helium tanks, refrigerant and industrial cylinders, camping and residential use cylinders, water system tanks for storage, treatment, heating, expansion and flow control, as well as a variety of retail products under several brand names.

Worthington Enterprises has 39 facilities, including Joint Venture locations, worldwide and employs nearly 6,000 people.

Consumer Products

Worthington Enterprises is the parent company of consumer brands including Balloon Time helium tanks, Bernzomatic, Garden Weasel, General, HALO, Hawkeye, Level5 Tools, Mag-Torch,  Pactool International and more. Worthington Enterprises is the only manufacturer of disposable 1lb propane cylinders in North America, which are sold under the Bernzomatic and Coleman brand. These gas cylinders are commonly used by consumers for soldering, brazing and welding, and to fuel cooking appliances like camp stoves and grills in a variety of recreational settings like campgrounds, parks, stadium parking lots and other outdoor areas.

Building Products

Worthington Enterprises manufactures building products used in a variety of markets including heating, cooling, construction, power generation, water and other specialty areas. The company also operates two Joint Ventures within this business segment: WAVE (Worthington-Armstrong Venture), a joint venture with Armstrong World Industries, that produces all of the suspended metal ceiling grids supplied by Armstrong, and ClarkDietrich, a joint venture with ClarkWestern Building Systems and Dietrich Metal Framing that manufactures light-gauge metal framing and finishing products, systems and services for commercial and residential construction

History

Worthington Industries was founded in 1955 by John H. McConnell, a steel salesman. McConnell saw an opportunity for custom-processed steel and purchased his first load of steel by borrowing $600 against his 1952 Oldsmobile. He founded the company in Columbus, Ohio, where it is still headquartered.

In his first year of business, McConnell grossed $342,000; his profit was $11,000. Throughout the late 1950s and 1960s, he continued to add processing facilities. In 1966, he started sharing his profits with the people he worked with. In 1968, Worthington Industries made its first public stock offering of 150,000 shares at $7.50 per share. Throughout the 1980s, the company continued to expand rapidly.

In 1996, John H. McConnell's son, John P. McConnell, took over as chairman and CEO. He had worked for the company for more than 20 years, having started as a general laborer and later advancing to sales, operations and personnel.

In 2000, Worthington Industries moved to the New York Stock Exchange.

In June 2017, the company acquired Amtrol for $283 million. Amtrol produces pressure cylinders and water system components, and is the largest provider of expansion tanks to the plumbing and HVAC markets in the United States,

In September 2020, former company President Andy Rose was named Worthington Industries' President & CEO, succeeding long-time Chairman and CEO John P. McConnell.

In January 2021, the company made two acquisitions. The first was the acquisition of German valve and component company PTEC Pressure Technology GmbH. The second was the acquisition of General Tools & Instruments Company LLC (General Tools), a provider of over 1,200 feature-rich, specialized tools, primarily for measuring and marking, found in supply houses, home centers, and hardware stores worldwide.

In 2022, the company announced its intent to spin off its Steel Processing business and split into two separate, publicly traded companies. On November 9, 2023, the separation was approved by the Board of Directors^[5].

On December 1, 2023, Worthington Industries completed its planned separation into two companies: Worthington Enterprises and Worthington Steel^[6]. Andy Rose remained president and CEO of Worthington Enterprises and Geoff Gilmore, former VP and COO of Worthington Industries, was named president and CEO of Worthington Steel.

In 2024, Worthington Enterprises made two significant acquisitions. First was the acquisition of HALO, an outdoor cooking company that makes pizza ovens, griddles and pellet grills. In June, the company announced two transactions with Hexagon Composites in Norway: the partial sale of its Sustainable Energy Solutions (SES) business to create a Joint Venture, and the complete purchase of of Hexagon Ragasco, the composite cylinder division of Hexagon Composites^[7].

In October 2024, president and CEO Andy Rose announced his retirement. Joseph Hayek, who served as the company’s executive vice president and CFO, was selected to replace Rose and officially became president and CEO of Worthington Enterprises on November 1, 2024.

References

1. "Worthington Industries, Inc. Form 10-K Annual Report for the Fiscal Year Ended May 31, 2019". U.S. Securities and Exchange Commission.
2. ^ Jump up to:^{a b c} "Our Story". Worthington Industries.
3. ^ McConnell, Kitty (November 1, 2015). "Q&A: John P. McConnell, Chairman and CEO of Worthington Industries". The Columbus Dispatch.
4. ^ Knox, Tom (June 2, 2017). "Worthington Industries makes biggest acquisition in company history". American City Business Journals.
5. Cornell, Joe (November 16, 2023). “Worthington Industries to Spin-Off Worthington Steel On December 1”. Forbes.
6. Richesson, Brian (December 8, 2023). “Worthington Enterprises completes separation of Worthington Seel”. LPGas Magazine.
7. Pentasuglio, Julia (June 4, 2024). “Worthington Enterprises acquires Hexagon Ragasco, enters joint venture with Hexagon Composites”. LPGas Magazine.
8. Williams, Mark (October 9, 2024). “Andy Rose stepping down as president, CEO of Worthington Enterprises”. The Columbus Dispatch.

Analyzer-614 (talk) 21:06, 5 November 2024 (UTC)

Edit Request

I have noticed some outdated information on this page and recommending some updates in accordance with some recent acquisitions by Worthington Enterprises. Updates are listed below, followed by references to support these changes.

In the Building products section, update the first sentence to include updated market categories and more detail around Joint Ventures:

Worthington Enterprises manufactures building products used in a variety of markets including heating and cooling, cooking, construction and water solutions, and building systems including HVAC and metal roofing components, architectural and acoustical grid ceilings and metal framing and accessories. The company also operates three joint ventures within this business segment: WAVE (Worthington-Armstrong Venture), a joint venture with Armstrong World Industries, that produces all of the suspended metal ceiling grids supplied by Armstrong; ClarkDietrich, a joint venture with ClarkWestern Building Systems and Dietrich Metal Framing that manufactures light-gauge metal framing and finishing products, systems and services for commercial and residential construction; and heiserTEC, formerly Worthington Enterprises' Sustainability Energy Solutions (SES) business, formed between Worthington Enterprises and Hexagon Composites.

In addition, I propose an update to the end of the article to bring it up to date:

In June 2025, Worthington Enterprises acquired Elgen Manufacturing, a market-leading designer and manufacturer of HVAC parts and components, ductwork and structural framing, to expand its building systems and components portfolio. Later that year, the company announced its intent to acquire LSI Group, Inc, a leading metal roof components manufacturer, a transaction that finalized in early 2026 and added the metal roof market to its portfolio.

Finally, I recommend changes to the grey sidebar in accordance with these updates:

Products: Cylinders for heating, cooling, cooking, construction, water; HVAC components; metal roof components, outdoor living and celebrations products; tools

Brands: Amtrol, Amtrol-Alfa, Balloon Time, Bernzomatic, bpd, Coleman (propane cylinders), Elgen, Garden Weasel, General, HALO, LEVEL5 Tools, Logan Stampings, Mag Torch, Pactool International, Ragasco, Roof Hugger

REFERENCES:

https://tmcapital.com/transactions/elgen-manufacturing-has-been-acquired-by-worthington-enterprises/

https://www.roofingcontractor.com/articles/101705-worthington-to-buy-metal-roofing-firm-lsi-for-205m Analyzer-614 (talk) 12:54, 25 March 2026 (UTC)

Wyss Foundation

Wyss Institute for Biologically Inspired Engineering

On behalf of the Wyss Foundation, I propose adding mention of the organization's funding of the Wyss Institute for Biologically Inspired Engineering. There are several recently published sources confirming the project, including Harvard. I propose adding:

• In 2019, Wyss contributed $131 million via the foundation to Harvard University's Wyss Institute for Biologically Inspired Engineering.

References

This seems like a straightforward update, but I don't edit the main space directly so I'm seeking assistance from another editor to review and update the article on my behalf. Thanks for your consideration. Inkian Jason (talk) 20:16, 7 June 2019 (UTC)

Thanks for updating the article. Inkian Jason (talk) 15:23, 13 June 2019 (UTC)

Proposed edits to Conservation subsection

Hello! I'm here on behalf of the Wyss Foundation with an edit request. On August 28, an IP address editor added new text to the Conservation subsection. The new text claims that the Campaign for Nature is "highly criticized by indigenous rights groups, human rights organizations and the environmental movement" and is supported by two citations—a June post on a website called Open Democracy and a March article from the New York Times. Neither of these sources make any reference to the Wyss Foundation or Campaign for Nature. Both do, though, detail criticisms of the 30x30 initiative more generally.

It seems like a separate article about 30x30 would be a better place to detail endorsements and criticisms of the plan. That said, I can understand why some mention of criticisms would seem relevant here, so I've attempted to revise this paragraph so that more context is present about the Wyss Foundation's support for Indigenous-led conservation efforts. I have also replaced citations that linked to the Wyss Foundation website with third-party, reliable sources. Can someone please review this revised paragraph and, if they feel it meets Wikipedia requirements and improves the Wyss Foundation article, make the update?

New paragraph

In 2018, the Wyss Foundation launched the Wyss Campaign for Nature, pledging that it would donate $1 billion to the project. The campaign aims to protect 30% of the world's surface by 2030. The campaign is backed by the National Geographic Society and other international conservation organizations. The 30x30 plan has been criticized by some indigenous rights activists for potentially dispossessing human inhabitants from historically occupied land. Other tribal organizations and leaders have endorsed the initiative, however. The Wyss Foundation has financially supported Indigenous-led conservation efforts, including the effort to establish the Qat'Muk Central Purcell Mountains Indigenous Protected and Conserved Area in British Columbia, the Dehcho First Nations-led management plan for the Edéhzhíe National Wildlife Area in the Northwest Territories, and the Indigenous-led Gayini conservation project, a sustainable conservation area in Australia’s Murray Darling Basin. The foundation also supported the retirement of oil and gas leases within the Badger-Two Medicine area of the Lewis and Clark National Forest in support of a Blackfeet-led "Traditional Cultural District".

References

Thank you. ZH for Wyss Foundation (talk) 18:18, 9 September 2021 (UTC)

ZH, I answered you on the Wikipedia talk:WikiProject Protected areas talk page why I am unable to help despite my commitment to Indigenous conservation efforts. I also want to mention here that to remove criticism from this article to a new one may run the risk of violating WP:NPOV and WP:WEIGHT. Netherzone (talk) 18:18, 8 October 2021 (UTC)

Thank you for following up here, too, Netherzone. I've replied in full at the WikiProject but did want to underscore here that my request above is definitely not to remove criticism. I am okay with including criticism so long as it is clear what the criticism was about. The language on the page now says that the Foundation's Campaign for Nature was "highly criticized by indigenous rights groups, human rights organizations and the environmental movement." But neither of the sources cited make any reference to the Wyss Foundation or Campaign for Nature, though both do detail criticisms of the 30x30 initiative more generally. If the other details in my draft are considered promotional, then I understand not including them, but could the wording about the criticism still be addressed? ZH for Wyss Foundation (talk) 20:34, 11 October 2021 (UTC)

I did some work on this in the article. Novellasyes (talk) 22:45, 19 October 2021 (UTC)

Thank you, Novellasyes. The edits resolve my concerns about the text, so I have marked this request as being answered. Many thanks. ZH for Wyss Foundation (talk) 17:55, 21 October 2021 (UTC)

Proposed edits to infobox

Hello! I'm here on behalf of the Wyss Foundation with another edit request. Looking at other foundation pages on Wikipedia, I noticed that there is more information about the Wyss Foundation that can be included in the infobox table to give readers a quick reference for key facts.

The items I'd like to ask editors to add are:

1. The organization's logo: I've uploaded it to Wikipedia here File:Wyss Foundation logo.png
2. Type: Private foundation, non-profit
3. Legal status: 501(c)(3)
4. Purpose: Conservation, education, advocacy
5. Area served: Worldwide

References

Aside from the type and legal status, the other details are covered in the overall Wikipedia article, so I have not provided specific references for them. Can someone please review and make these additions if they are appropriate?

Thank you. ZH for Wyss Foundation (talk) 15:48, 25 March 2022 (UTC)

Partly done: (please ping on reply) Happy Editing--IAmChaos

 Not done for now: Pending a rationale for use. See the image page which states: Please add a detailed non-free use rationale for each article the image is used in, which must also declare compliance with the other parts of the non-free content criteria, as well as the source of the work and copyright information. See the image page for more links and information. Happy Editing--IAmChaos 05:00, 26 March 2022 (UTC)

@ZH for Wyss Foundation: The proposed image above has been deleted, so I am closing this request as answered. If you would like to propose another image, or upload this image with the appropriate rationale, please open a new request below and a reviewer will determine if it should be included in the article. Z1720 (talk) 13:08, 5 April 2022 (UTC)

Follow-up for logo

Hello! I am here on behalf of the Wyss Foundation with a follow-up to my last edit request. Thanks so much to IAmChaos for making the infobox changes, and thanks to Z1720 for the nudge about the logo.

The logo is re-uploaded and I've taken care to fill in the fair use rationale: File:Wyss Foundation logo.png

The note about the rationale on the image page seems to be pro-forma and it looks like someone needs to review the image and confirm that the rationale is complete. I noticed last time that if it hasn't been added to an article then it gets deleted very quickly. Could someone please review the image and add it to the article so that it doesn't get deleted again?

Also, can the Purpose parameter be added to the infobox, with the following listed: Conservation, education, advocacy

Can someone please review and make these additions if they are appropriate?

Thank you. ZH for Wyss Foundation (talk) 20:23, 8 April 2022 (UTC)

Notes for this edit request:

• Added the logo to the page after checking the rationale.
•  Not done the Purpose parameter, as a source was not provided, and purpose is not explicitly stated in the article.

Closing edit request as answered. Z1720 (talk) 21:30, 8 April 2022 (UTC)

Question about second paragraph

Hi there. I work at the Wyss Foundation and I have a question about the second paragraph in the introduction section.

My understanding is that the introduction of a Wikipedia article is intended to summarize key points from the body of the article. I asked Mathglot, Tarlby, and other editors at the Wikipedia Teahouse, and they confirmed that this is correct.

The second paragraph in this article's introduction currently concerns a separate organization, the Berger Action Fund.

Although the Berger Action Fund and the Wyss Foundation are affiliated, they are in fact different organizations. It thus doesn't make sense to have half of the introduction to the Wyss Foundation Wikipedia entry be about a different entity, especially as the information about Berger is never referenced again in the body of the article.

Could editors move this material to the Political advocacy section, maybe as the fourth paragraph? The information about Berger's relationship with Wyss could then be briefly summarized in the introduction. (Maybe: "The Wyss Foundation has an associated 501(c)(4) advocacy group called the Berger Action Fund that shares facilities and staff and has faced scrutiny.")

Thank you for reviewing this request. Please let me know if you have any questions. I'll try to answer as soon as I can. ZH for Wyss Foundation (talk) 21:51, 5 May 2025 (UTC)

This makes total sense to me, and I've implemented your request. Any other editor may contest it, if they wish. If so, please ping me so I can read the rationale. Thanks, MediaKyle (talk) 23:57, 5 May 2025 (UTC)

Thank you for looking into this, MediaKyle. ZH for Wyss Foundation (talk) 17:55, 6 May 2025 (UTC)

Why is the Wyss Foundation having any say in this article? ~2026-53805-7 (talk) 12:15, 16 February 2026 (UTC)

Edit Requests for March 2026

I have suggestions for correcting inaccuracies on this page. I have a WP:COI as an employee of the Wyss Foundation and am submitting these suggestions for review by independent editors.

1. What I think should be changed:

In the Political Advocacy section, beneath “The Hub Project” subsection, please replace the first sentence of the first paragraph:

Change from:

In 2015, the Wyss Foundation funded the establishment of The Hub Project, which seeks to help the Democratic Party be more effective at conveying their arguments through the news media and directly to voters, and to shift "...the public debate and policy positions of core decision makers".

Change to:

In 2015, the Wyss Foundation funded the establishment of The Hub Project. According to a 2021 article in The New York Times, the group was created partly to shape media coverage to help Democratic causes, and its 2015 business plan said it would work behind the scenes to “dramatically shift the public debate and policy positions of core decision makers.”

Why: The cited NYT source does not support this wording. The article doesn’t state that The Hub Project seeks to help the Democratic Party, which is a formal organization. Instead, it states that the group formed “partly to shape media coverage to help Democratic causes.” Converting “Democratic causes” to the “Democratic Party” with no supporting source constitutes WP:OR. The suggested replacement accurately reflects the scope of The Hub Project’s work as described in the source. This is a very serious error. There are major legal limitations around directly supporting political parties and Wikipedia, unlike the NYT, is not properly making this distinction.

2. What I think should be changed:

In the Political Advocacy section, beneath “The Hub Project” subsection, please replace the second sentence of the first paragraph:

Change from:

The Hub Project is part of Arabella Advisors, a leading vehicle for funneling "dark money" on the political left.

Change to:

The Hub Project is part of a network of funds managed by Arabella Advisors that the New York Times characterized as a major channel for “dark money” spending on the political left.

Why: Subjective language like “funneling” has been rewritten in a neutral manner and I’ve attributed “dark money” directly to the source.

3. In the Political advocacy section, please delete the first paragraph:

The organisation funds Democratic Party political causes through Arabella Advisors and its related entities.

Why: The cited NYT source does not support this wording. The NYT article doesn’t state that the Wyss Foundation funds any organization that is part of the Democratic Party, which is a formal organization. Instead, it states that the groups it funds help “Democratic causes” and help “advance progressive policy initiatives and the Democrats who support them.” Converting “Democratic causes” to the “Democratic Party” with no supporting source constitutes WP:OR. This is a very serious error. There are major legal limitations around directly supporting political parties and Wikipedia, unlike the NYT, is not properly making this distinction.

4. What I think should be changed:

In the Lead section, please replace the second sentence of the first paragraph:

Change from:

The Wyss Foundation funds conservation efforts as well as Democratic Party political causes through Arabella Advisors and its related entities.

Change to:

The Wyss Foundation funds conservation efforts as well as progressive causes through Arabella Advisors and its related entities.

Why: As discussed in items 1 and 3, the Democratic Party is not named in the New York Times article. Wikipedia is conflating causes with support for a formal political party. This should be corrected in the Lead, just as in the body of the article.

Thank you for reviewing. JQDC (talk) 17:59, 23 March 2026 (UTC)

References

Not being American, I have no skin in the game, but the articles do talk quite a lot about supporting Democrats, so does this not favour the Democrat Party? (I will leave US editors to apply their judgement to these requests.) Laterthanyouthink (talk) 05:25, 27 March 2026 (UTC)

I had the same thought when I first saw this. Marquardtika, could I trouble you for your opinion? This has been open for awhile now. MediaKyle (talk) 19:35, 4 May 2026 (UTC)

I don't think we should implement this COI request. The NYT says "The organization, called The Hub Project, was started in 2015 by one of Mr. Wyss’s charitable organizations, the Wyss Foundation, partly to shape media coverage to help Democratic causes." Also "Hansjörg Wyss, who recently dropped his bid to buy Tribune Publishing, has been a leading source of difficult-to-trace money to groups associated with Democrats" and "Newly obtained tax filings show that two of Mr. Wyss’s organizations, a foundation and a nonprofit fund, donated $208 million from 2016 through early last year to three other nonprofit funds that doled out money to a wide array of groups that backed progressive causes and helped Democrats in their efforts to win the White House and control of Congress last year." The NYT is clearly saying he is giving money to groups supporting the Democratic Party, not just "democratic causes". Marquardtika (talk) 13:10, 5 May 2026 (UTC)

XMPP Standards Foundation

Suggested refactoring of XMPP Standards Foundation article

• What I think should be changed (include citations):

Extended content

Replace introduction

Suggested new introduction, to replace the current paragraph that exists on the original page prior to the 'history' heading:

The '''XMPP Standards Foundation''' ('''XSF''') is a non-profit organization that develops and maintains open standards for the [[XMPP|Extensible Messaging and Presence Protocol (XMPP)]], a decentralized, real-time communication protocol.<ref>{{cite web |no-tracking=true|title=XMPP Standards Foundation |url=https://xmpp.org/about/xmpp-standards-foundation/ |website=xmpp.org |access-date=2026-02-10}}</ref>

The foundation is responsible for stewarding the core XMPP specifications in coordination with the [[IETF|Internet Engineering Task Force (IETF)]] and for managing the XMPP Extension Protocol (XEP) process, which defines optional extensions to the protocol.<ref>{{cite web |no-tracking=true|title=XMPP Standards Process |url=https://xmpp.org/about/standards-process/ |website=xmpp.org |access-date=2026-02-10}}</ref>

The organization was founded in 2001 as the ''Jabber Software Foundation'' and was renamed the XMPP Standards Foundation in 2007 to reflect the protocol's standardization under the name XMPP.<ref>{{cite web |no-tracking=true|title=XSF Organizational Documents |url=https://xmpp.org/about/xsf/organizational-documents/ |website=xmpp.org |access-date=2026-02-10}}</ref><ref>{{cite web |no-tracking=true|title=Proposal: XMPP Standards Foundation |url=https://xmpp.org/about/xsf/records/proposals/xmpp-standards-foundation/ |website=xmpp.org |access-date=2026-02-10}}</ref>

• Why it should be changed:

1. Accurate description of responsibilities: The updated intro clarifies that the XSF manages both core XMPP specifications and the XEP process, rather than only providing general oversight.
2. Improved neutrality and clarity: The current introduction lacks precise citations. The revised version cites primary XSF sources to ensure verifiable and neutral statements.

Update Section: Organization

• What I think should be changed (include citations):

Update the list of individuals, following changes in leadership.

== Organization ==

=== Board of directors ===
The Board of Directors<ref>[http://xmpp.org/xsf/board/ XSF Board]</ref> of the XMPP Standards Foundation oversees the business affairs of the organization. As elected by the XSF membership. As of 2026, the Board of Directors consists of the following individuals:

* '''Guus der Kinderen'''
* '''Ralph Meijer'''
* '''Mickaël Rémond'''
* '''Florian Schmaus'''
* '''Arne-Bruen Vogelsang'''

=== Council ===
The XMPP Council<ref>[http://xmpp.org/council/ XMPP Council]</ref> is the technical steering group that approves XMPP Extension Protocols, as governed by the [https://web.archive.org/web/20090127051940/http://xmpp.org/xsf/docs/bylaws.shtml XSF Bylaws] and [http://xmpp.org/extensions/xep-0001.html XEP-0001]. The Council is elected by the members of the XMPP Standards Foundation each year in September. As of 2026, the XMPP Council<ref>{{Cite web |no-tracking=true|title= XMPP Standards Foundation (XSF) | XMPP - the universal messaging standard|url=https://xmpp.org/about/xmpp-standards-foundation/#council}}</ref> is composed of the following members:
* '''Dan Caseley'''
* '''Daniel Gultsch'''
* '''Marvin Wissfeld'''
* '''Stephen Paul Weber'''
* '''Jérôme Poisson'''

=== Members ===
There are currently 56 elected members<ref>[https://xmpp.org/about/xsf/members XSF Member List]</ref> of the XSF.

==== Emeritus Members ====
The following individuals are emeritus members of the XMPP Standards Foundation:

* '''Peter Millard (deceased)'''
* '''Dave Smith'''
* '''Jeremie Miller'''
* '''Julian Missig'''
* '''Ryan Eatmon'''
* '''Thomas Muldowney'''

• Why it should be changed:

1. The listed information is outdated, since the Board and Council election in November 2025: https://wiki.xmpp.org/web/Meeting-Minutes-2025-11-20

Add Section: Mission

• What I think should be changed (include citations):

Suggested new section 'Mission' to be positioned as first section on the page (prior to the 'history') section:

== Mission ==
The mission of the XMPP Standards Foundation is to build and promote an open, secure, interoperable, and decentralized infrastructure for real-time communication and collaboration on the Internet. The foundation focuses on protocol specifications rather than software implementations, and its standards are intended to be implementable without licensing fees.<ref>{{cite web |no-tracking=true|title=XSF Mission |url=https://xmpp.org/about/xsf/mission/ |website=xmpp.org |access-date=2026-02-10}}</ref>

• Why it should be changed:

1. Supports reader understanding: Including the mission in its own section makes the article consistent with Wikipedia standards for organization pages, which typically include a dedicated "Mission" or "Purpose" subsection.

Replace Section: XEPs

• What I think should be changed (include citations):

Suggested new section to replace the preexisting 'XEPs section:

== Standards and specifications ==

=== Core XMPP specifications ===
The core XMPP protocol is standardized through the Internet Engineering Task Force, primarily in RFC 6120, RFC 6121, and RFC 6122, with subsequent updates and clarifications published over time.<ref>{{cite web |no-tracking=true|title=XMPP RFCs |url=https://xmpp.org/rfcs/ |website=xmpp.org |access-date=2026-02-10}}</ref>

=== XMPP Extension Protocols ===
In addition to the core protocol, the XSF maintains the '''XMPP Extension Protocol''' (XEP) series, which defines optional extensions that add functionality while preserving interoperability between implementations.<ref>{{cite web |no-tracking=true|title=XMPP Extension Protocols |url=https://xmpp.org/extensions/ |website=xmpp.org |access-date=2026-02-10}}</ref>

The XEP process is open and community-driven, allowing anyone to propose an extension. XEPs progress through defined maturity levels such as ''Experimental'', ''Draft'', ''Final'', or ''Deprecated'' under the oversight of the XMPP Council.<ref>{{cite web |no-tracking=true|title=XMPP Standards Process |url=https://xmpp.org/about/standards-process/ |website=xmpp.org |access-date=2026-02-10}}</ref>

• Why it should be changed:

1. Removes trivial and anecdotal content: The pronunciation discussion ("JEP" vs "ZEP") is informal, unsourced, and not encyclopedic.
2. Improves readability and structureL Replacing the unordered list of example XEPs with a description of the XEP system itself provides a clearer, concise explanation suitable for a general audience.

Replace Section: XMPP Summit

• What I think should be changed (include citations):

Suggested new section to replace the preexisting 'XMPP Summit section:

== Activities ==

=== Summits and events ===
The XMPP Standards Foundation organizes regular '''XMPP Summits''', typically held annually or biannually, where developers and community members meet to discuss protocol development and future directions.<ref>{{cite web |no-tracking=true|title=XMPP Summit 28 |url=https://xmpp.org/2025/11/xmpp-summit-28/ |website=xmpp.org |access-date=2026-02-10}}</ref>

=== Publications and outreach ===
The foundation publishes regular '''XMPP Newsletters''' summarizing technical developments, community projects, and ecosystem news, and participates in outreach related to open standards and decentralized communication.<ref>{{cite web |no-tracking=true|title=The XMPP Newsletter – December 2025 |url=https://xmpp.org/2026/01/the-xmpp-newsletter-december-2025/ |website=xmpp.org |access-date=2026-02-10}}</ref>

• Why it should be changed:

1. Updates frequency and scope: The previous section contains specific outdated dates and locations (e.g., FOSDEM, RealtimeConf, 2006), which may not longer reflect all current practices. The new section uses neutral language describing annual or biannual summits.
2. Improves neutrality: Removing promotional or overly detailed logistical information (e.g., "no costs attached," "open to donations") aligns with Wikipedia’s neutral tone guidelines.
3. Adds publications and outreach: Including XSF newsletters broadens the activities section, providing a more complete picture of XSF's engagement with the community.

Guusdk (talk) 13:49, 11 February 2026 (UTC)

• @Guusdk: First, thank you for following the process for COI edits! The challenge I have with your requests is that they are all supported by only primary sources from the XSF's website. The goal is for articles to primarily have secondary or tertiary sources that talk about the organization, rather than being from the organization. Can you find some reliable sources from, for instance, tech media sites, that talk about the XSF and it's work? For example, was there an article on some site talking about the latest XMPP Summit back in November? Ideally an article that talked about how this latest XMPP Summit was one in a long series of XMPP Summits, etc.

The key is that the article about the XSF is not a place to promote the XSF but rather a place to talk about the XSF - and so the sources need to be from places other than xmpp.org . If you can identify such sources, it would make it possible to do these kind of updates that you are suggesting here. - Dyork (talk) 16:13, 11 February 2026 (UTC)

Hi @Dyork, thank you for the (fair) feedback. It is correct that the edit relies on primary sources, which is not ideal. However, the article currently relies on the same type of sourcing, and this edit does not introduce a new issue in that regard. While it does not resolve the preexisting sourcing limitations, I do not believe it decreases the article's quality. In other respects, the edit improves the article, and on balance I believe it is an improvement over the prior version.

To address the usage of sources more specifically, would these sources be adequate?

IONOS article: https://www.ionos.com/digitalguide/server/know-how/xmpp/

This article describes XMPP as an open communication protocol that was standardized through the IETF and maintained/standardized with ongoing updates. It mentions that XMPP was developed by the Jabber community and became an IETF standard, and while it mentions the XSF's role in implementation and standardization indirectly, it is not focused on the organization.

Use cases in Wikipedia article (supported claims):

• Support introductory descriptive claim that XMPP is an open, extensible communication protocol standardized through IETF and used for real‑time messaging outside xmpp.org primary sources.
• Help frame a context paragraph on XMPP's history as a protocol independent of the XSF's own website (e.g., "XMPP, originally developed in 1998 and standardized by the IETF, forms the technical basis for the XSF's work.")

IETF XMPP working group page: https://datatracker.ietf.org/wg/xmpp/about/

This page is an independent confirmation that XMPP is standardized through the IETF working group process. It lists RFCs and working group activity separate from the XSF.

Use cases in Wikipedia article:

• Citation for the claim that XMPP core is standardized via the IETF and not solely internally maintained by the XSF (relevant in the 'Standards and Specifications' section).
• Supports the introductory notion of XMPP as a recognized global open standard with international community consensus beyond the XSF.

GetStream blog post: https://getstream.io/blog/xmpp-extensible-messaging-presence-protocol/

The GetStream blog post, while it is not focused on the XSF as an organization, does independently describe XMPP as an open, decentralized standard and identifies the XMPP Standards Foundation as the body responsible for maintaining and evolving the protocol.

Concretely, this source can support these sections of my proposed edit:

• The introduction paragraph describing XMPP as an open, standardized, decentralized real-time communication protocol and the XSF's role as its steward.
• The statement that XMPP is standardized via the IETF RFC process, providing independent confirmation of that relationship.
• Support high‑level statements about protocol extensibility and standards‑based design in 'Standards and Specifications' section.

FOSDEM 2025 technical program: https://fosdem.org/2025/schedule/event/fosdem-2025-5721-a-universal-and-stable-api-to-everything-xmpp/

A major open-source conference listing a talk that explicitly explains how XSF is organized and how XMPP specifications are created, including mentioning XEPs. This is an independent program description from the conference website.

Use cases in Wikipedia article:

• Independent verification that the XSF organizational and standards process is discussed at a major open‑source conference, supporting notability and factual claims about the XSF's role in standards.
• Can be cited in 'Activities' or 'Standards and Specifications' to show recognition of the XSF's work outside its own site.

FOSDEM 2026 session description: https://fosdem.org/2026/schedule/event/7XJL9E-engineering_xmpp_federation_building_messaging_voice_social_features_across_inde/

This source shows that XMPP and the ecosystem around the XSF appear in independent technical contexts, and the session describes how the XSF interacts with implementations. It directly talks about the XSF's work on specifications and ecosystem collaboration.

Use cases in Wikipedia article:

• Supports for claims that the XSF's work is recognized and discussed in major forums beyond xmpp.org, lending weight to the Foundation's real‑world relevance.
• Use in 'Activities' or 'Standards' to note real‑world implementation/ecosystem involvement beyond internal documents.

IgniteRealtime blog post: https://discourse.igniterealtime.org/t/igniterealtime-heads-to-brussels-xsf-summit-fosdem-2026/96325

Although this comes from a community site rather than xmpp.org, it is not published by the XSF itself and therefore functions as a secondary mention of XSF activity outside of the organization's own website.

• In the 'Summits and Events' section, the blog post confirms that the XSF Summit is a recurring gathering where developers, maintainers and contributors across the XMPP ecosystem come together, and that the event is organized by the XMPP Standards Foundation. This provides confirmation of the existence and continuity of these summits.

I should note that I am also the author of the Ignite Realtime blog post. Because of that, I agree it shouldn't be treated as a fully independent secondary source on its own. I'm proposing it only as supplementary confirmation of factual details.

ProcessOne blog post: https://www.process-one.net/blog/supporting-xmpp-standard-foundations-open-letter-to-meta-for-true-interop/

This blog post covers an open letter issued by the XSF calling on Meta to adopt XMPP for interoperability. It is independent reporting of an XSF action and thus counts as third‑party coverage of an organizational initiative.

Use cases in Wikipedia article:

• Independent confirmation that the XSF publishes actions of public interest (e.g., advocacy on interoperability).
• Supports a sentence in 'Activities' about the XSF engaging with broader technical community and public dialogue.
• Helps show that XSF isn't only internally documented but that third‑party blogs report on its initiatives.

Guusdk (talk) 11:22, 13 February 2026 (UTC)

@Guusdk: Thanks for all of that. It's a good start. I'll see if I have some time to work on it in the weeks ahead. (Obviously other editors may do so as well!) - Dyork (talk) 20:30, 13 February 2026 (UTC)

Hi @Dyork! Thanks for your help a few months ago on this! Sadly, @Spintendo closed this due to inactivity recently. As I'm somewhat inexperienced with Wiki-processes, can you help me get this effort to improve things restarted? Thanks! Guusdk (talk) 07:44, 28 May 2026 (UTC)

• @Guusdk: I actually don't know the process to re-open something like this. It actually doesn't matter whether it is open or not if an editor actually just does the work. What's happened by closing it is that it will no longer appear on one of the pages that lists articles with COI edit requests. So editors who look at that page wouldn't see this one as needing help.

On my end, I've been swamped with deadlines in my work life and so haven't been doing as much editing on Wikipedia. I was hoping perhaps another editor would come along and pick away at some of this. I'll see what I can do... but it's going to be a week or two until I can do anything. - Dyork (talk) 23:30, 28 May 2026 (UTC)

@Dyork thanks for the fast reply! It is absolutely fine that real life responsibilities gets in the way of volunteering activities on Wikipedia. I don't feel that there's any responsibility to you to work on this change at all. I would very much welcome your help, if you're able to give it, but I understand that things simply do not always work out.

That said, even while this change was up on the COI edit requests page, it received no perceivable help other than your feedback. It having been _removed_ from that page makes it even less likely that others will pitch in to help. With the listing removed, I doubt that people even notice that there's pending work. That's why I think that the closure of the request _does_ matter (and why I'd like to see it re-opened). Guusdk (talk) 14:03, 29 May 2026 (UTC)

A response has not yet been received for this question.

Reply 21-MAY-2026

  Request closed for inactivity  

• The above edit request has not received any responses over the past 3 weeks (22 days in total).
• Discussion is often a key component to implementing edits, and requests may be adversely affected when they fail to garner input from either reviewing or requesting editors. In light of this — and as a safeguard — this request has been declined as needing more discussion.
• The COI editor is urged to revive stalled communications by making contact with local editors on those editor's own talk pages, and then by moving those discussions back to this talk page.
• The COI editor may also wish to broadcast requests for edits at the talk pages of the WikiProjects which govern this article. Those projects are usually listed at the top of an article's talk page.

Regards,  Spintendo  01:42, 22 May 2026 (UTC)

I would like to reopen this request if appropriate. I understood the discussion to be awaiting further reviewer/editor input, rather than requiring additional action from me. If such action is required, I am more than happy to provide this. I was in the 'be extremely patient' mode as suggested by the COI overview page. Guusdk (talk) 19:28, 27 May 2026 (UTC)

Following up on my COI edit request above. This request has now been open and then closed for inactivity, over a period of several months, without an independent editor being available to action it. I'm grateful to @Dyork: for the engagement and feedback earlier, and I understand entirely that real-life commitments have made it hard for anyone to pick this up.

Given that the request has not been able to attract a reviewer, I intend to begin implementing the proposed changes myself. I want to be fully transparent about this: I have a conflict of interest, which I have declared throughout, and I will flag it clearly in each edit summary. I'll make the changes as discrete, individually-summarised edits rather than as a single sweep, so that any of them can be easily reviewed, discussed, or reverted by other editors.

My aim is the same as it has been from the start: to improve the article. I remain very happy to discuss any of these edits, adjust them, or self-revert if another editor raises a concern. If anyone would prefer to action the request themselves instead, I'd genuinely welcome that. Guusdk (talk) 08:30, 18 June 2026 (UTC)

I have now made the three most straightforward changes myself as discrete, COI-flagged edits. The two remaining proposals (intro replacement and a Mission section) are more about framing, so rather than make them myself I've opened them as two fresh COI edit requests below, where an independent editor can act on either. Happy to adjust wording. Guusdk (talk) 14:18, 26 June 2026 (UTC)

References

COI edit request: introduction (June 2026)

Requested by a COI editor (XSF-affiliated). This is a fresh, self-contained request superseding the introduction part of the earlier (closed) request above.

Proposed change: replace the current lead paragraph (everything before the "History" heading):

−

'''XMPP Standards Foundation''' ('''XSF''') is the foundation in charge of the standardization of the protocol extensions of [[Extensible Messaging and Presence Protocol|XMPP]], the open standard of [[instant messaging]] and presence of the [[Internet Engineering Task Force|IETF]].

+

'''XMPP Standards Foundation''' ('''XSF''') is a non-profit organization that develops and maintains open standards for the [[Extensible Messaging and Presence Protocol|XMPP]], a decentralized real-time communication protocol standardized through the [[Internet Engineering Task Force|IETF]]. The foundation manages the XMPP Extension Protocol (XEP) process, which defines optional extensions to the protocol. It was founded in 2001 as the ''Jabber Software Foundation'' and renamed the XMPP Standards Foundation in 2007.

Reason: The current lead is a single unsourced sentence. The replacement cites the IETF (a source independent of the XSF) for the standardization claim, and states founding/renaming facts already supported in the History section. It is intentionally brief and avoids promotional language.

Independent sources that may help here are listed in the earlier (closed) request above.

Guusdk (talk) 14:11, 26 June 2026 (UTC)

COI edit request: add Mission section (June 2026)

Requested by a COI editor (XSF-affiliated). Self-contained request; independent of the introduction request above.

Proposed change: add a short section immediately after the lead, before "History":

== Mission ==
The XSF focuses on developing protocol specifications rather than software implementations, and its standards are intended to be implementable without licensing fees.<ref>{{cite web |no-tracking=true|title=XSF Mission |url=https://xmpp.org/about/xsf/mission/ |website=xmpp.org |access-date=2026-06-26}}</ref>

Reason: Gives the article a brief, factual statement of the organization's scope, consistent with how organization articles are usually structured.

Independent sources that may help here are listed in the earlier (closed) request above.

Guusdk (talk) 14:11, 26 June 2026 (UTC)

Yahya Kemal College

Request for a neutral and factual rewrite

I work for Yahya Kemal College and therefore have a professional connection to the subject of this article.

The current article contains outdated information, obsolete school-unit details, promotional wording and old external links. I am not requesting the removal of criticism or the addition of advertising language.

I would like to propose a complete factual and neutral rewrite based on reliable sources. The proposed version would:

• remove promotional sections such as aims, mission and goals;
• update the institution’s current educational units and official website;
• retain only verifiable information about its history, locations and educational structure;
• include independent sources wherever available;
• clearly distinguish official institutional information from independent reporting.

Because of my connection to the institution, I am requesting review and implementation by an uninvolved Wikipedia editor rather than editing the article directly.

I can provide the proposed replacement text and the supporting sources here for review. Thank you. ~2026-39018-94 (talk) 00:52, 10 July 2026 (UTC)

• Specific text to be added or removed:

I propose replacing the current article body, including the sections titled “Education system” and “Enrollment policy”, with the following concise version. The existing promotional claims, outdated branch list and obsolete external link would be removed.

Content

Yahya Kemal College is a private educational institution in North Macedonia. It was established in Skopje in November 1996 and is named after the Turkish poet and writer Yahya Kemal Beyatlı, who was born in Skopje. The institution provides primary and secondary education through educational units in Skopje, Tetovo and Struga.

=Yehuda Kahane=

COI edit request: Add sources for the Bickley Founder's Award

I am Yehuda Kahane, the subject of this article, as disclosed on my user page. Per WP:COI, I am requesting changes here rather than editing the article directly.

The article's first sentence states that I am "the 2011 recipient of the John S. Bickley Founder's Award for his contribution to the theory, practice, and education of insurance and risk management" and is currently tagged with {{citation needed}}.

I would like to request that the {{citation needed}} tag be replaced with the following two independent sources, which verify the claim:

1. A news article in TheMarker (Israeli financial daily, part of the Haaretz group), published 22 November 2010, reporting that the International Insurance Society awarded me the John S. Bickley Founder's Award, noting it was the first time the award was given to an expert from Israel:

2. The official list of John S. Bickley Founder's Award recipients published by the International Insurance Society, which lists "Yehuda Kahane, Tel Aviv University, Israel (2011)":

No change to the article text itself is requested – only the addition of these references in place of the existing {{citation needed}} tag.

Thank you for your time. YehudaKahane (talk) 14:04, 13 July 2026 (UTC) YehudaKahane (talk) 14:04, 13 July 2026 (UTC)

Yfke Sturm

BLP/BLPCRIME concern: Epstein section

Disclosure: I have a personal connection to the subject and a conflict of interest, so I am not editing the article directly. I'm raising this here for independent editors. I am not being paid.

I have two policy concerns about the "Epstein Controversy" section and propose a more neutral version. I am not asking to remove the material entirely.

1. WP:BLPCRIME and sensational quotes. The section quotes "owes him two girls" and "make it up to him in Paris". These lines strongly imply involvement in serious criminal conduct. Sturm has not been charged with or convicted of any offence, and the emails are described in the sources only as "allegedly" between her and Epstein. Per WP:BLPCRIME, WP:BLPSTYLE and WP:UNDUE, reproducing these specific quotes gives the matter undue weight for a living person facing no charges. The encyclopedic facts can be stated neutrally without the most damaging phrasing.

2. Section heading (WP:CSECTION). Standalone "Controversy" headings are discouraged. I suggest merging this content into the "Private life" section rather than keeping a dedicated heading.

Proposed wording (to sit within "Private life"):

In 2026, following the release of emails from the Epstein files by the US Department of Justice, NRC Handelsblad reported a 2012 email exchange said to involve Sturm and Jeffrey Epstein. Sturm described her contact with Epstein as "naive" and a "serious error of judgement".

This keeps the reliably sourced facts and her own public response, while removing quotes that are unduly sensational and imply uncharged criminal conduct. Happy to discuss and defer to consensus. Thanks. TMeijer86 (talk) 09:35, 22 June 2026 (UTC)

BLPCRIME prevents "...any article that suggests (an unconvicted person) has committed, is suspected of, is a person of interest in, or is accused of having committed a crime." What is it about those emails, in particular, that suggests Sturm has committed, is suspected of, is a person of interest in, or is accused of having committed a crime? When ready to proceed with your answer, kindly switch the request template's answer parameter to read from |ans=y to |ans=n.  Spintendo  07:09, 29 June 2026 (UTC)

Thanks for engaging. Here is the BLPCRIME concern. Jeffrey Epstein was a convicted sex trafficker. The quoted exchange has him saying Sturm "owes him two girls", with her reported reply that she "will make it up to him in Paris". To an ordinary reader that implies Sturm was involved in procuring or supplying girls to Epstein, in other words complicity in sex trafficking. That is a serious crime. Sturm has never been charged with, arrested for, or convicted of any such offence, and the sources themselves describe the emails only as "allegedly" hers. By reproducing those specific quotes, the article suggests to readers that she is a person of interest in, or complicit in, criminal conduct. That is precisely the implication WP:BLPCRIME asks us to avoid for unconvicted individuals.

Even apart from BLPCRIME, the same change is supported by WP:BLPSTYLE, which cautions against sensationalism, and by WP:UNDUE. The direct quotations are disproportionate to the encyclopedic significance of this episode for the subject.

To be clear, I am not asking to suppress the matter. The proposed wording keeps the reliably sourced facts: that NRC Handelsblad reported a 2012 email exchange said to involve her and Epstein, and her own public response describing it as "naive" and "a serious error of judgement". It removes only the sensational quotes and the standalone "Controversy" heading. I will switch the template to |ans=n as suggested. Thanks again. TMeijer86 (talk) 09:24, 29 June 2026 (UTC)

Young Democratic Socialists of America

Proposed updates to lead, infobox, and early history

I am an active YDSA member, so I am requesting review rather than editing the article directly.

I would like to propose a first set of limited changes to the article’s lead, infobox, and early history section. The article currently has citation and primary-source tags, and some claims in the early history section are either unsourced or broadly phrased. These changes add clearer citations and narrow some wording that is currently unsourced or broadly phrased.

The main changes are:

• Update the lead to state that the organization was founded in 1982 as the Democratic Socialists of America Youth Section, changed its name to Young Democratic Socialists in 1997, and adopted its current name in 2017.
• Update the infobox with leadership and citations.
• Revise the 1980–2000 section to better source the organization’s early anti-apartheid, Central America, labor, anti-sweatshop, and prison-divestment activity.
• Replace the unsourced or under-sourced “citation needed” language with citations to Joseph Schwartz’s DSA history, the DSA Fund’s YDSA history, NYU archival records, Phoenix New Times, The Temple News, and Prison Legal News.

I have tried to keep the language neutral and to avoid adding any promotional claims. I am posting this in parts so editors can review each proposed change separately.

Proposed infobox update:

Please add the following leadership lines and update the membership line:

| membership = {{increase}} 2,735<ref name="2026-apportionment">{{Cite web |no-tracking=true|title=[PUBLIC] 2026 YDSA Convention Apportionment |url=https://docs.google.com/spreadsheets/d/1NkkFlBIuWVri3X-IfCAyMyVagEUZQZdE2DURDF80eHE/edit |access-date=April 16, 2026 |website=Google Docs |language=en-US}}</ref>
| leader title = Co-chairs
| leader = Daniel Salup-Cid<ref name="DSA-structure">{{Cite web |no-tracking=true|title=Leadership and Structure |url=https://www.dsausa.org/about-us/structure/ |website=Democratic Socialists of America |access-date=May 28, 2026}}</ref><br />Sara Almosawi<ref name="DSA-structure" />

Proposed replacement text for lead:

The '''Young Democratic Socialists of America''' ('''YDSA''') is the youth section of the [[Democratic Socialists of America]] (DSA). Founded in 1982 as the '''Democratic Socialists of America Youth Section''', the organization changed its name to '''Young Democratic Socialists''' ('''YDS''') in 1997 and adopted its current name in 2017.<ref name="Schwartz-DSA-history">{{Cite web |no-tracking=true|last=Schwartz |first=Joseph M. |date=July 2017 |title=A History of Democratic Socialists of America 1971–2017 |url=https://www.dsausa.org/about-us/history/ |access-date=May 28, 2026 |website=Democratic Socialists of America}}</ref><ref name="YDSA-history">{{cite web |no-tracking=true|last1=Duhalde |first1=David |last2=Kreider |first2=Ben |title=History of Young Democratic Socialists of America |url=https://dsafund.org/wp-content/uploads/2025/06/History-Of-YDSA-8.5-%C3%97-11-in-August-2022.pdf |publisher=DSA Fund |access-date=May 28, 2026}}</ref> As of April 2026, YDSA had 2,735 members.<ref name="2026-apportionment" />

Proposed replacement text for 1980-2000 section:

In 1980, ''Democratic Left'' reported that the Youth Section of the [[Democratic Socialist Organizing Committee]] (DSOC) had grown from 600 to nearly 1,200 members and from 15 to more than 30 chapters over the previous year.<ref>{{Cite magazine |no-tracking=true|date=October 1980 |title=Youth Parley |url=https://dlarchive.dsausa.org/wp-content/uploads/2019/01/DL_1980_V008_08_final.pdf |magazine=Democratic Left |publisher=Democratic Socialist Organizing Committee |page=12 |access-date=May 28, 2026}}</ref> Following the merger of DSOC and the [[New American Movement]] in 1982, DSOC's youth section continued as the '''Democratic Socialists of America Youth Section'''.<ref name="Schwartz-DSA-history" /> In the 1980s, the Youth Section organized against [[apartheid]] in South Africa and United States intervention in [[Central America]].<ref name="Schwartz-DSA-history" /> [[New York University]] archival records list DSA Youth Section and YDS files concerning South Africa initiatives, Nicaraguan student tours and exchanges, and Central America/Southern Africa solidarity work.<ref>{{Cite web |no-tracking=true|title=Series IV. Youth Section/Young Democratic Socialists of America: Democratic Socialists of America Records |url=https://findingaids.library.nyu.edu/tamwag/tam_105/contents/aspace_42e24784fa039770fac85d6910e2dcbf/ |access-date=May 28, 2026 |website=NYU Special Collections Finding Aids}}</ref>

During the 1990s, as DSA community chapters declined in activity, the Youth Section became one of the organization's main areas of activity.<ref name="YDSA-history" /> Youth Section chapters focused on labor organizing, opposition to the [[North American Free Trade Agreement]], protests against the [[World Trade Organization]], and involvement in the [[AFL-CIO]]'s Union Summer in 1996.<ref name="YDSA-history" /> During this period, tensions between DSA and the Youth Section contributed to the Youth Section adopting the name '''Young Democratic Socialists''' ('''YDS''') and developing a more distinct identity.<ref name="YDSA-history" /> Some YDS chapters also took part in student anti-sweatshop organizing; at [[Arizona State University]], YDS members campaigned against the university's Adidas apparel contract and pushed the university to join the [[Worker Rights Consortium]].<ref name="Phoenix-New-Times-ASU" />{{Cite web |no-tracking=true|last=Hibberd |first=James |date=March 8, 2001 |title=Big Mac on Campus |url=https://www.phoenixnewtimes.com/news/big-mac-on-campus-6418285/ |access-date=May 28, 2026 |website=Phoenix New Times}}</ref> Around 2000 and 2001, student activists opposed campus contracts with [[Sodexo|Sodexho Marriott]] because of parent company Sodexho Alliance's investments in private prison companies.<ref>{{Cite web |no-tracking=true|date=May 3, 2001 |title=Colleges Across the U.S. Protest Sodexho Marriot |url=https://temple-news.com/colleges-across-the-us-protest-sodexho-marriot/ |access-date=May 28, 2026 |website=The Temple News}}</ref> YDS members were involved in related campus campaigns, including a campaign against Sodexho Marriott's food-service contract at [[Arizona State University]] and support for a December 2000 student occupation at [[Ithaca College]].<ref name="Phoenix-New-Times-ASU" /><ref>{{Cite magazine |no-tracking=true|title=New York Students Stage Private Prison Protest |magazine=Prison Legal News |volume=12 |issue=5 |date=May 2001 |page=12 |url=https://archive.org/details/prison_legal_news_2001 |access-date=May 28, 2026 |via=Internet Archive}}</ref>

FromTheRiver0713 (talk) 19:02, 2 June 2026 (UTC)

Yuri Buzzi

Request for sourced factual updates

Hello editors,

Extended content

I am the subject of this article and would like to request a few neutral, factual updates in accordance with Wikipedia's conflict of interest guidelines.

Suggested updates:

• Addition of recent acting credits including:
  • Emily in Paris (Netflix)
  • Missing the Boat (Hallmark Channel)
  • A Taste for Murder (ITV / BritBox) as Fabio Pigozzi

• Update of occupation details to reflect current verified work as an actor.

• Addition of reliable sourced references regarding international acting work and Martini & Rossi ambassador campaign coverage.

Possible reliable sources include:

• ITV / BritBox cast coverage
• Campaign Live
• Libero
• Hallmark Channel cast coverage
• Netflix-related cast coverage and interviews

I am not requesting promotional language, only factual updates supported by reliable independent sources.

Thank you very much for your time and consideration.

Yurjb (talk) 10:24, 18 May 2026 (UTC)

Reply 16-JUN-2026

  Specification requested  

• It is not known what changes are requested to be made. Please state your desired changes in the form of "Change x to y using z".

Change x to y using z

x	A verbatim description of the old text to be removed from the article (if any)
y	A verbatim description of the new text to be added to the article (if any)
z	A reference which verifies the requested change

Example edit request:

Please change:

• The Sun's diameter is 25 miles.

↑ This is x ↑

to read as:

• The Sun's diameter is 864,337 miles.

↑ This is y ↑

using as a reference:

• Harinath, Prisha (2023). The Sun. Academic Press. p. 1.

↑ This is z ↑

Kindly open a new edit request at your earliest convenience when ready to proceed.
Regards,  Spintendo  10:45, 16 June 2026 (UTC)

Thank you for reviewing the request. I understand the previous request was too general.

Could editors please consider the following specific changes?

In the Filmography section, under Television, please change:

‘‘Emily in Paris’’ (Netflix)

‘‘Missing the Boat’’ (Hallmark Channel) as Massimo

to:

‘‘Emily in Paris’’ (Netflix)

‘‘Missing the Boat’’ (Hallmark Channel) as Massimo

‘‘A Taste for Murder’’ (ITV / BritBox) as Fabio Pigozzi

Sources:

https://www.tvguide.com/tvshows/a-taste-for-murder/cast/1060525089/

https://www.rottentomatoes.com/tv/a_taste_for_murder/s01/cast-and-crew

In the opening sentence, please change:

Yuri Buzzi (born 26 September 1978) is an Italian actor, creative director, and communication coach.

to:

Yuri Buzzi (born 26 September 1978) is an Italian actor and creative director.

This is to keep the introduction more neutral and reduce unsourced or promotional wording.

Thank you very much. ~2026-35420-62 (talk) 14:42, 16 June 2026 (UTC)

Specific sourced edit request (change X to Y using sources)

Hello editors,

I am the subject of this article. I am opening a new request following the requested "change X to Y using Z" format.

Zelle

Updating Criticism section and incorporating Regulatory action and fraud concerns content

Hey again! I was wondering if editors would consider updating the Criticism section of this article. I understand that, as a COI editor, my perspective has some bias, but I've tried to put together a coherent and well-sourced section draft that describes all the relevant criticism Zelle has faced over the past few years. My draft incorporates some content from the Regulatory action and fraud concerns section, which I think should be folded into the Criticism section. Here is my draft:

Criticism draft

Zelle has received negative publicity related to reports of scam and fraud where the service is used as a payment method, particularly where consumers are tricked into sending money by bad actors using social engineering tactics. A 2025 Reuters report identified major social media platforms as a significant source of this kind of payment fraud and account compromise. Zelle's member banks are required by law to reimburse consumers for transactions that are performed without the consumer's authorization, such as when their bank account is hacked. In 2023, Zelle announced that it would start reimbursing consumers for certain types of scams involving authorized transactions, such as when scammers impersonate government officials or a customer's bank.

In September 2022, Senator Elizabeth Warren criticized Zelle executives at a Senate Banking Committee hearing for a lack of refunds in claimed fraud cases and insufficient responses to requests for statistics.. This criticism came shortly before Warren released a report on fraud and reimbursement practices. In 2025, 99.98% of Zelle transactions were completed without report of fraud or scam.

In December 2024, the Consumer Financial Protection Bureau (CFPB) filed a lawsuit against Early Warning Services (EWS), the operator of Zelle, along with three banks: Bank of America, JPMorgan Chase, and Wells Fargo. The lawsuit alleged these entities failed to protect consumers from fraud and scams. The CFPB dropped this lawsuit in March 2025.

In August 2025, New York Attorney General Letita James filed a separate lawsuit with claims similar to the CFPB lawsuit. Zelle responded by claiming that the attorney general's office had not thoroughly investigated the company.

References

I know I'm asking for a significant restructuring and revision of the article, so I welcome feedback from non-COI folks. I think what I've put together is good and makes for a better encyclopedia article, but I defer to the judgment of independent editors. Happy to field comments or questions below! EB at EW (talk) 23:25, 10 June 2026 (UTC)

Reply 26-JUN-2026

  Edit request declined  

• Exact, verbatim descriptions of any text and/or references to be removed needs to be given.

Regards,  Spintendo  17:11, 26 June 2026 (UTC)

References

Hey, User:Spintendo! I've built a little side-by-side comparison of the existing content (on the left) and my draft (on the right). As a reminder, I'm asking to fold the Regulatory action and fraud concern section into the Criticism one, which is why content from that section is included in the comparison below:

Current sections vs. draft

−

The Zelle service has received negative publicity due to fraud incidents where bank customers’ accounts were compromised through [[social engineering (security)|social engineering]] tactics. In these cases, fraudsters set up Zelle accounts in the victims’ names and used them to transfer funds out of the victims’ accounts, often leaving the victims with limited practical or legal options for recovery. In one case, a Florida man pled guilty to defrauding victims of $250,000 by convincing them to make payments using Zelle to reverse purported fraudulent transactions. In some cases, bank customers have been compensated by the banks involved, depending upon the bank and its policies and the specifics of the incident. Banks may use secondary confirmation methods such as [[one-time password#SMS|SMS]] or otherwise place limits on newly created accounts and transfers to recently added recipients as a preventive measure. Shortly before releasing a critical report, Senator [[Elizabeth Warren]] criticized Zelle executives at a September 2022, Senate Banking Committee hearing, both for lack of refunds in cases of fraud, and lack of response to requests for statistics. In December 2024, the [[Consumer Financial Protection Bureau|Consumer Financial Protection Bureau (CFPB)]] filed a lawsuit against Early Warning Services (EWS), the operator of Zelle, along with three major banks: Bank of America, JPMorgan Chase, and Wells Fargo. The lawsuit alleges that these entities failed to protect consumers from widespread fraud on the Zelle network.The lawsuit alleges that customers of the three named banks lost over $870 million to fraud throughout Zelle's seven-year history, claiming that the banks and Early Warning Services (EWS) rushed the platform to market without sufficient safeguards to better compete with rivals like Venmo and CashApp. Despite hundreds of thousands of consumers filing fraud reports, the suit contends that these individuals were largely denied help, as banks reportedly failed to conduct proper investigations or provide the legally mandated reimbursements for fraud and errors.The CFPB sought to stop the alleged unlawful practices, secure redress and penalties, and obtain other relief. CFPB Director Rohit Chopra stated that the banks' failure to implement proper safeguards made Zelle "a gold mine for fraudsters".The CFPB dropped the lawsuit in March of 2025.

+

Zelle has received negative publicity related to reports of scam and fraud where the service is used as a payment method, particularly where consumers are tricked into sending money by bad actors using social engineering tactics. A 2025 ''[[Reuters]]'' report identified major social media platforms as a significant source of this kind of payment fraud and account compromise. Zelle's member banks are required by law to reimburse consumers for transactions that are performed without the consumer's authorization, such as when their bank account is hacked. In 2023, Zelle announced that it would start reimbursing consumers for certain types of scams involving authorized transactions, such as when scammers impersonate government officials or a customer's bank.In September 2022, Senator [[Elizabeth Warren]] criticized Zelle executives at a Senate Banking Committee hearing for a lack of refunds in claimed fraud cases and insufficient responses to requests for statistics.. This criticism came shortly before Warren released a report on fraud and reimbursement practices. In 2025, 99.98% of Zelle transactions were completed without report of fraud or scam. In December 2024, the Consumer Financial Protection Bureau (CFPB) filed a lawsuit against Early Warning Services (EWS), the operator of Zelle, along with three banks: Bank of America, JPMorgan Chase, and Wells Fargo. The lawsuit alleged these entities failed to protect consumers from fraud and scams. The CFPB dropped this lawsuit in March 2025.In August 2025, New York Attorney General Letita James filed a separate lawsuit with claims similar to the CFPB lawsuit. Zelle responded by claiming that the attorney general's office had not thoroughly investigated the company.

References

I hope this illustrates what I'm looking to achieve. I think a line-by-line justification for every single change I'm suggesting would be unreadable, but my main goals with this draft are :

1. To consolidate existing content so that the section is easy to follow
2. To add relevant context to existing claims (e.g. Zelle reimbursing customers targeted by certain types of scams)
3. Removing claims that are either irrelevant (e.g. the Florida man anecdote) or unsourced (e.g. the longish paragraph about the CFPB's allegations)

I think a holistic approach is the best one for improving this section, since it's kind of a mess as-is, but perhaps I should break this request down a bit, see if I can lay it out in multiple parts. Please let me know what you think! Thanks, EB at EW (talk) 18:24, 2 July 2026 (UTC)

It seems that I’m making some kind of mistake with the side-by-side comparison that should be appearing in the post above. When I test it out using the Show Preview function, it looks fine, but then I hit publish and the code breaks. Apologies for junking up the Talk page; I’m just trying to help editors better understand my request. If anybody can help me out with either the request or the technical issues I’m running into, I would very much appreciate it. Thanks! EB at EW (talk) 19:19, 2 July 2026 (UTC)

Zscaler

Request edit on 15 May 2026

• What I think should be changed:

The infobox containing information about key people and company financial data

• Why it should be changed:

This information is out of date. Remo Canessa is no longer Zscaler's CFO, and the financial data and employee count information is from 2024.

Here is a suggested edit for the infobox: Update the Key People section to delete Remo Canessa's name (as Remo is no longer CFO at Zscaler). Replace Remo's name with Kevin Rubin (CFO). Add Adam Geller (CPO)

Update the financial information to reflect the company's 2025 fiscal year financial data. Revenue: US$2.67 billion (2025) Operating income: US$-128 million (2025) Net income: US$-41.5 million (2025) * Note that the arrow should be green to represent positive year over year change in net income. Total assets: US$6.42 billion (2025) Total equity: US$1.79 billion (2025) Number of employees: 7,923 (2025)

Update the Industry section to be: Cybersecurity, Internet security, AI security, Zero trust, Cloud computing

• References supporting the possible change (format using the "cite" button):

For the updates to the Key people section:

For the financial information section:

For the updates to the Industry section: Zscaler focuses on zero trust and AI security, as evidenced by their receipt of the 2026 Google Partner of the Year for Security.

Benson,Julia (talk) 20:14, 15 May 2026 (UTC)

References

Request edit on 15 May 2026

• What I think should be changed:

The Acquisitions section would be easier to read in a bulleted format, instead of in paragraph format. This section would also benefit from additional information that explains what Zscaler acquired each company for.

• Why it should be changed:

It's easier to read bulleted lists, and it would provide more information for the reader.

Here is a suggested update of the Acquisitions section:

• August 2018: Zscaler acquired TrustPath’s development team and its AI and machine learning technology to add artificial intelligence and machine-learning technology to the company’s threat research and security analytics capabilities.
• May 2019: Zscaler acquired Appsulate to add browser-based isolation capabilities and remote access technology for securing web browsing and application access.
• April 2020: Zscaler acquired Cloudneeti to expand Zscaler’s cloud security posture management and compliance capabilities for public cloud workloads.
• May 2020: Zscaler acquired Edgewise Networks to add microsegmentation capabilities to the platform.
• April 2021: Zscaler acquired Trustdome to expand its cloud infrastructure entitlement management (CIEM) capabilities for governing permissions in public cloud environments.
• May 2021: Zscaler acquired Smokescreen Technologies for the company’s deception-based security technology for threat detection and investigation.
• September 2022: Zscaler acquired ShiftRight for the company’s security workflow automation technology for incident and risk response.
• February 2023: Zscaler acquired Canonic Security to expand its SaaS security, SaaS supply chain risk management, and governance capabilities.
• March 2024: Zscaler acquired Avalor to add a security data fabric that would bring together enterprise security data for analytics and prioritization.
• April 2024: Zscaler acquired Airgap Networks for the company’s agentless network segmentation capabilities.
• August 2025: Zscaler acquired Red Canary to expand into managed detection and response and related security operations capabilities.
• November 2025: Zscaler acquired SPLX to add AI security testing and governance capabilities to the platform.
• February 2026: Zscaler acquired SquareX to add browser detection and response (BDR) capabilities to the Zscaler platform.

• References supporting the possible change (format using the "cite" button):

For TrustPath:

For Appsulate:

For Cloudneeti:

For Edgewise Networks:

For TrustDome:

For Smokescreen Technologies:

For ShiftRight:

For Canonic Security:

For Avalor:

For Airgap Networks:

For Red Canary:

For SPLX:

For SquareX: Benson,Julia (talk) 20:42, 15 May 2026 (UTC)

References

Request edit on 21 May 2026

• What I think should be changed:

The introduction to this page is short and doesn't contain much descriptive information about what the company does.

• Why it should be changed:

Here is a more in-depth introduction to this page:

Zscaler, Inc. (/ˈziːˌskeɪlər/) is an American multinational cloud security company headquartered in San Jose, California. The company provides cloud-delivered cybersecurity services based on a zero trust model, including zero trust network access, data protection, and features to address AI security risks.

Zscaler’s core platform, the Zero Trust Exchange™, is based on zero trust principles and includes AI-driven cloud security functionality. The company offers AI security products such as continuous AI risk governance, protection of generative AI usage, and AI workload security.

According to VentureBeat, Zscaler has positioned growth in AI adoption as a core driver of demand for its AI security platform offerings. The company has also established partnerships with large language model developers, including Anthropic’s Project Glasswing and OpenAI's Trusted Access for Cyber program, with the stated goal of proactively identifying AI-driven vulnerabilities and security risks.

Zscaler's product development in AI-driven threat prevention was recognized when it received the 2026 Google Cloud Partner of the Year Award for Security.

• References supporting the possible change (format using the "cite" button):

References included in the suggested edits section above.

Benson,Julia (talk) 18:28, 21 May 2026 (UTC)

References

Request edit on 27 May 2026

• What I think should be changed:

The "History" section is fairly short and could benefit from some additional information. It would also be easier to read if the sentences were broken up into smaller paragraphs.

• Why it should be changed:

Here is a suggested update to the "History" section. It includes the original information in the article, with a few small additions to add updated information and improve the reading experience:

Zscaler was founded in 2007 by Jay Chaudhry and K. Kailash. The company launched its cloud native cybersecurity platform in 2008. The platform was designed to provide cloud-based security without on-premises appliances.

In August 2012, Zscaler raised $38 million in a Series A funding round. In August 2015, the company raised a $100 million Series B round led by TPG, which pushed the company’s valuation above $1 billion.

In March 2018, the company had an initial public offering (IPO) on the Nasdaq exchange under the ticker ZS, during which it raised $192 million.

In August 2018, Zscaler made its first post-IPO acquisition by acquiring TrustPath's AI and machine learning technology in addition to the startup’s development team. Zscaler then acquired the browser security firm Appsulate in May 2019.

Zscaler stock was added to the Nasdaq-100 index on December 17, 2021.

In 2023, at its Zenith Live conference, Zscaler announced new AI security capabilities. Then, in January 2026 the company released the Zscaler AI Security Suite, which included functionality to discover, secure, and govern AI usage for enterprises.

Zscaler was named a Leader in the inaugural Forrester Wave for Security Service Edge Solutions in 2024. In May 2025, Gartner named the company a Leader in its Magic Quadrant for Security Service Edge for the fourth consecutive year.

• References supporting the possible change (format using the "cite" button):

Included in suggested edits in the section above.

Benson,Julia (talk) 17:38, 27 May 2026 (UTC)

References

Request edit on 27 May 2026

• What I think should be changed:

The current section titled "Zero Trust Exchange" could be expanded with additional information that clearly explains what the company sells. Right now, the heading title "Zero Trust Exchange" doesn't make it immediately clear that it's discussing Zscaler's products, so this edit is suggesting that the "Zero Trust Exchange" heading gets renamed to "Products", with the "Zero Trust Exchange" information nested under the new "Products" section. This new structure should help readability, and the additional information will help add to the depth of the page's information.

• Why it should be changed:

Here is a suggested update of the current "Zero Trust Exchange" section:

Products

Zscaler develops AI-driven cloud security products that provide secure access to internet, cloud, and private applications for enterprise users and devices.

The Zscaler Zero Trust Exchange platform applies zero trust access controls by brokering connections between users, devices, and workloads and the applications or data they are authorized to access. The platform is positioned as an alternative to traditional VPN-based remote access and firewall-centric architectures.

The company’s offerings are commonly used to support distributed workforces and to help organizations implement secure access service edge (SASE) and zero trust security architectures.

Zero Trust Exchange Platform

The Zscaler Zero Trust Exchange is a cloud-based security platform that provides security controls as a service. The platform sits between an entity (including users, workloads, IoT/OT, and AI agents) and the resources (including public and private clouds, applications, the internet, and SaaS applications) that entity is trying to access.

Under this model, security decisions are made centrally using organizational policies and contextual signals, such as identity, device security posture, and location. Those policies are then applied to traffic regardless of where applications or users are located.

The Zero Trust Exchange inspects and governs traffic while reducing security risks associated with having direct network access to corporate environments. It applies threat protection, enable data controls, and log activity for monitoring and compliance purposes.

Zscaler positions this approach as a way to limit lateral movement of threat actors, simplify connectivity for hybrid and remote workers, and move security functions to the cloud.

• References supporting the possible change (format using the "cite" button):

References are included in the suggested edits above.

~2026-31959-76 (talk) 23:29, 29 May 2026 (UTC)

References

Request edit on 29 May 2026

• What I think should be changed:

Because the "Zero Trust Exchange" or "Product" sections of this page are currently light on detail, I'd like to suggest adding more content to those sections to help explain what products Zscaler develops and sells. This should make the page more valuable for readers.

• Why it should be changed:

Here is a suggested addition to the current "Zero Trust Exchange" or "Product" section of the page:

AI Security Capabilities (Note: this bolded title would make sense as a subsection that's nested under "Zero Trust Exchange" or "Product" section)

Zscaler develops and sells an AI security platform focused on identifying AI threats, classifying sensitive data, and enforcing AI policy controls. The platform’s machine learning capabilities analyze security telemetry, identify anomalous behavior, and provide automated responses for security teams.

Zscaler has introduced features to improve visibility and control over AI application usage, including inspection of user interactions and data protection controls to reduce exposure of sensitive information. Recent acquisitions such as Avalor, Red Canary, and SPLX brought new technologies to Zscaler’s data integration, detection, and AI lifecycle security capabilities.

Data security (Note: this bolded title would make sense as a subsection that's nested under "Zero Trust Exchange" or "Product" section)

Zscaler’s data security capabilities are cloud-delivered controls that discover, classify, and prevent unauthorized exposure of sensitive information when users and workloads access the internet, third-party SaaS applications, and private applications. The company offers data loss prevention (DLP) and related policy enforcement functions, which can inspect traffic and apply rules to reduce the likelihood of data exfiltration.

Zscaler has developed new technologies and acquired companies to expand its SaaS security posture management, cloud data security, and other data protection offerings.

Zscaler’s Data Security Posture Management offering gives visibility into where sensitive information is stored within an enterprise’s systems, how that information is accessed, and which users or applications have access to that information.

Zscaler’s DSPM product is positioned as a component of the company’s broader AI security product offerings, which manage risks associated with employee and application use of AI technologies.

The company’s DSPM technology supplies data inventory and risk context that enterprises can use to inform governance controls for AI security use cases including limiting exposure of sensitive data to AI tools, monitoring data flows to and from AI applications, and applying policy controls to reduce the likelihood of data leakage from AI application usage.

• References supporting the possible change (format using the "cite" button):

References are included in the suggested changes above.

~2026-32875-56 (talk) 22:47, 2 June 2026 (UTC)

References

Request edit on 8 June 2026

• What I think should be changed:

It would be helpful to add a new section directly above the "Acquisitions" section called "Artificial intelligence and AI security." Because AI and AI security are relevant topics within the cybersecurity industry, it would be useful for readers to have information about Zscaler, AI, and AI security in this article.

• Why it should be changed:

Here is a proposed section to add to the page:

Artificial intelligence and AI security Zscaler’s platform uses machine learning–assisted analytics to correlate telemetry and generate security insights across user, device, and application activity.

The company introduced generative AI features to support security operations workflows, including natural-language interaction and automation capabilities. Zscaler has stated that data integration initiatives such as its Data Fabric for Security are used to improve analytics and prioritization across security datasets.

For generative AI applications, Zscaler provides visibility into application usage and applies policy enforcement to reduce data leakage and other AI misuse risks. These capabilities support discovery and governance of AI tools, inspection of AI-related traffic, and policy actions that can restrict access or limit the sharing of sensitive information in AI prompts and responses.

Zscaler’s AI risk management strategy has been supported by acquisitions and research initiatives focused on AI lifecycle security. The company has cited the acquisitions of Canonic Security, Avalor, and SPLX as opportunities to expand the Zscaler platform’s capabilities related to application governance, data integration, and AI security assessments.

Zscaler publishes AI-focused threat research through its ThreatLabz team.

• References supporting the possible change (format using the "cite" button):

References were cited in the proposed edit above.

Benson,Julia (talk) 16:27, 8 June 2026 (UTC)

References

---

← Previous page