Wikipedia:Requests for page protection
![]() | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
Welcome—request protection of a page, file, or template here. | ||
---|---|---|
Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection) After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:Protectedpages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to get rid of obvious vandalism.
Request protection of a page, or increasing the protection level
Request unprotection of a page, or reducing the protection level
Request a specific edit to a protected page
Please request an edit directly on the protected page's talk page before posting here |
2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
Current requests for increase in protection level
Place requests for new or upgrading of article protection, upload protection, or create protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.
Semi-protection: Persistent addition of unsourced or poorly sourced content. FMSky (talk) 01:53, 10 February 2025 (UTC)
Semi-protection: Persistent vandalism – vandalism. Joeykai (talk) 02:01, 10 February 2025 (UTC)
Temporary move protection: Page title dispute/move warring – persistent WP:MOVEWAR by user following WP:RMUM revert. Happily888 (talk) 02:17, 10 February 2025 (UTC)
Temporary move protection: Page title dispute/move warring. Happily888 (talk) 02:25, 10 February 2025 (UTC)
Indefinite semi-protection: Persistent disruptive editing. This talk page is routinely used as a soapbox by users wishing to store or promote their academic articles. Some examples: 1 2 3 4 5 6 7 8 9 10, all from various IPs around the world. There has not been a constructive suggestion to the page since early 2021, since then it has been used exclusively as a soapbox hence why I think this page should be protected. I guess pending changes works too. jolielover♥talk 02:38, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism. jolielover♥talk 02:43, 10 February 2025 (UTC)
Semi-protection: Persistent sockpuppetry. - Ratnahastin (talk) 03:53, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 03:59, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 03:59, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:00, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:18, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:18, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:19, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:20, 10 February 2025 (UTC)
- Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 04:23, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:20, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:21, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:25, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 04:25, 10 February 2025 (UTC)
Pending changes: BLP policy violations – IP hopper making unsourced claims about the article subject's dating life for over a month. Aspening (talk) 06:57, 10 February 2025 (UTC)
Reason: Persistent disruptive editing from IP users BlameRuiner (talk) 07:08, 10 February 2025 (UTC)
Reason: Temporary semi-protection request; Persistent disruptive editing. The Department of Education still exists, yet it keeps receiving edits to change it to past tense. Likely due to the recent politicization (the claim that it doesn't exist by Musk). Sempiternalis (talk) 09:44, 10 February 2025 (UTC)
Reason: High level of IP vandalism Tonyy Starkk (talk) 10:13, 10 February 2025 (UTC)
Reason: High level of IP vandalism throughout page history, already been vandalised within a day of semi-protection being lifted. Subject is still active in Formula One. MB2437 10:29, 10 February 2025 (UTC)
Reason: Respected Admins, please protect this page permanently or for long duration due to Vandalism 2405:201:900C:D17F:25DF:938C:50A2:AF2 (talk) 10:34, 10 February 2025 (UTC)
Temporary semi-protection: High level of IP vandalism. 58.111.101.186 (talk) 12:35, 10 February 2025 (UTC)
Requesting semi-protection of Top Gun: Maverick
Temporary semi-protection: Persistent vandalism – An increased amount of vandalism by anonymous editors. Squawk7700 (talk) 12:49, 10 February 2025 (UTC)
Semi-protection: Persistent disruptive editing. Skitash (talk) 13:45, 10 February 2025 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Anonymized user insists on adding original research and correcting the marriage year contrary to provided source (1994 vs 1998). Hariboneagle927 (talk) 13:54, 10 February 2025 (UTC)
Reason: High level of IP vandalism. Flabshoe1 (talk) 14:40, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement – Needs CTOPS action. Filmssssssssssss (talk) 15:13, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 16:03, 10 February 2025 (UTC)
temporary semi-protection requested: Persistant weasel word into a BLP by various IPs over the long term, here are a few diffts from the last day to so. Not extremely high but the only edits actually happening on this high traffic BLP - nearly 350k views in the past 30 days and in the top 1000 Wikipedia pages for January.traffic -- IP diffs... [1][2][3] TiggerJay (talk) 16:11, 10 February 2025 (UTC)
Reason: Uptick in vandalism. Unknown Temptation (talk) 16:11, 10 February 2025 (UTC)
Indefinite extended protection: Arbitration Enforcement. WP:CT/AI. 💽 🌙Eclipse 💽 🌹 ⚧ (she/they/it) talk/edits 16:21, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism – A lot of vandalism by a lot of different anonymous editors. Squawk7700 (talk) 16:38, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Persistent vandalism since 06:07, 10 January 2025. Alith Anar 16:48, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism. Persistent blanking DACartman (talk) 17:20, 10 February 2025 (UTC)
Reason: Repeated vandalism and unconstructive edits. High-profile and controversial topic 162 etc. (talk) 17:37, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism. User:Namiba 17:45, 10 February 2025 (UTC)
Semi-protection: Persistent vandalism – Recent uptick in vandalism. Filmssssssssssss (talk) 18:50, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 18:52, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 18:52, 10 February 2025 (UTC)
Semi-protection: Persistent vandalism – Disruptive MOS issues by IP editor range. Mass rewriting article with poor to no sources, additions of nonexisting files, etc, later IPs of same range keep reinstating the content that was objected to. Zinnober9 (talk) 18:54, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Call me paranoid, but I believe this should be protected due to persistent IP vandalism and the occasional addition of "annoying" real people's names. OpalYosutebito (talk) 18:56, 10 February 2025 (UTC)
Semi-protection: Persistent sockpuppetry – Since the end of December. Skywatcher68 (talk) 19:10, 10 February 2025 (UTC)
Semi-protection: Persistent sockpuppetry – BMX is still at it. Oh, and could the protecting admin revdel some of the 'reverting edits by revdellible username (talk)' summaries where the username is revdelled?. JayCubby 19:17, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 19:28, 10 February 2025 (UTC)
Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 19:34, 10 February 2025 (UTC)
Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 19:36, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism – Sustained vandalism for the last month, adding factually incorrect information (such as fake cast members). If the article were semi'd for a month or so it will hopefully encourage the vandal to move on. Betty Logan (talk) 19:48, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 19:54, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 19:54, 10 February 2025 (UTC)
Extended confirmed protection: Arbitration enforcement. Filmssssssssssss (talk) 19:58, 10 February 2025 (UTC)
Temporary semi-protection: Persistent vandalism – IP vandalism. Doc Strange (talk) 20:00, 10 February 2025 (UTC)
Extended confirmed protection: Persistent disruptive editing – IPs adding non-NPOV information to a contentious topic despite being warned numerous times to use talk page per WP:ONUS. CNMall41 (talk) 20:08, 10 February 2025 (UTC)
Current requests for reduction in protection level
Before posting, first discuss with the protecting admin on their talk page. Post below only if you receive no reply.
- To find out the username of the admin who protected the page, click on "history" at the top of the page, then click on "View logs for this page," which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
- Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
- Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
- If you want to make spelling corrections or add uncontroversial information to a protected page, please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected, please use the section below.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.
Reason: This page has been protected for *ten years*. It is the only engine page for major US manufacturers that is. It is not an *inherently contentious* page like many on religion, sexuality, ethnic strife, and such (which can remain persistently problematic). The page has had plenty of time to ride out a spate of probematic editing/unregistered editors. It needs the opportunity to be freely edited, and settle itself down. 2601:196:180:DC0:4842:76FD:4D84:35D5 (talk) 15:26, 7 February 2025 (UTC)
- FYI Biblioworm. There's certainly a lot of disruption on car articles generally, but I'm not sure about a specific engine nowadays – I checked in the archives and the last time we had an engine-related request was in October (note that I only did a Ctrl+F check and that the Ford IP seems unrelated to this one). Sdrqaz (talk) 17:17, 7 February 2025 (UTC)
Current requests for edits to a protected page
Please request an edit directly on the protected page's talk page before posting here
Ideally, requests should be made on the article talk page rather than here.
- Unless the talk page itself is protected, you may instead add the appropriate template among
{{Edit protected}}
,{{Edit template-protected}}
,{{Edit extended-protected}}
, or{{Edit semi-protected}}
to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed. - Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the
{{Edit COI}}
template should be used. - Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
- If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
- This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.
MFA Motorways
[edit source]
MFA Motorways is a multinational fleet management solutions provider operating in Australia, New Zealand, and the United Kingdom. The company specializes in Internet of Things (IoT) technology to assist rental car companies, logistics firms, and fleet managers in vehicle tracking, asset security, and operational efficiency. Through its digital platforms; eFleetPass, eFleetTrack, and eFleetCheck—MFA Motorways provides real-time fleet monitoring and management.
Founded in 2012, the company has expanded internationally, adapting its solutions to different regional regulations and business needs.
Founded | 2012 |
---|---|
Location | Australia, New Zealand, united kingdom |
Service | Fleet Management, Vehicle tracking, asset security |
Range | eFleetpass, eFleetTrack, eFleetCheck |
Founder | Leonardo De La Vega |
Headquarters | Australia |
History[edit source]
MFA Motorways was founded in Australia and officially registered as MFA Motorways (Australia) Pty Ltd on November 30, 2012. Initially, it focused on automated tolling and fleet tracking solutions in the Australian market.
With the increasing global demand for IoT-driven fleet management, MFA Motorways expanded internationally:
New Zealand: Established MFA Motorways (New Zealand) Limited on May 7, 2021. United Kingdom: Established MFA Motorways UK Limited on December 11, 2023, extending operations to Europe. The company’s growth has been fueled by advancements in telematics, AI-powered analytics, and partnerships with automotive and logistics firms.
Products and Services
[[source]]
MFA Motorways provides a range of fleet management solutions through its proprietary platforms:
eFleetPass – A 24/7 online fleet management platform offering automated in-vehicle solutions for rental car operators and logistics firms. eFleetTrack – A telematics system using IoT to monitor vehicle locations, driver behavior, and asset utilization. eFleetCheck – A due diligence service that provides vehicle history checks, GPS tracking, and mobile app integration for enhanced security. These solutions help businesses optimize fleet performance, reduce operational costs, and ensure compliance with regional regulations.
Business Model[[source]]
MFA Motorways operates under a B2B subscription-based model, targeting rental car companies, corporate fleet operators, and logistics firms.
Revenue Streams:[[source]]
Software-as-a-Service (SaaS): Subscription fees for eFleetPass, eFleetTrack, and eFleetCheck. Hardware Sales: Revenue from telematics devices and tracking sensors installed in fleet vehicles. Consulting Services: Providing fleet optimization strategies and compliance advisory. The company differentiates itself through customized, scalable solutions adaptable to fleets of all sizes.
Corporate Affairs[[source]]
Leadership MFA Motorways is led by an experienced executive team focused on innovation and market expansion:
CEO Name – Leonardo De La Vega Headquarters and Locations[[source]]
MFA Motorways’ global headquarters is located in North Strathfield, New South Wales, Australia. It also operates regional offices in:
Auckland, New Zealand – Serving the New Zealand market with localized fleet compliance services. London, United Kingdom – Managing European operations and customer support.
Ownership & Workforce[[source]]
MFA Motorways is a privately held company. The company employs an estimated 50 of people across its global operations.
Technology and Innovation[[source]]
MFA Motorways integrates cutting-edge IoT technology into its fleet management services. The R&D team focuses on:
Advanced GPS tracking & telematics for real-time fleet visibility. AI-driven predictive analytics for vehicle maintenance forecasting. 5G integration to improve data transmission speed and reliability. Blockchain-based fleet data management for enhanced security and transparency. Current innovations project include autonomous fleet monitoring, AI-powered risk assessment tools, and collaborations with smart vehicle manufacturers.
Market Position and Competitors[[source]]
MFA Motorways competes in the global fleet management industry, where major competitors include:
Geotab – A leader in fleet telematics and data-driven analytics. Verizon Connect – A provider of GPS fleet tracking and telematics solutions. Fleet Complete – Specializes in vehicle tracking and compliance management. Despite strong competition, MFA Motorways differentiates itself through customized digital platforms, region-specific compliance solutions, and AI-powered telematics.
== Corporate Social Responsibility (CSR)
==
MFA Motorways is committed to sustainability and corporate responsibility, focusing on:
Eco-friendly fleet management – Promoting the adoption of electric and hybrid vehicles. Data security and privacy – Ensuring compliance with GDPR and other international regulations. Road safety initiatives – Supporting community programs on safe driving and fleet efficiency. The company actively invests in sustainable technology to minimize carbon emissions in fleet operations. == Financial Performance == [[source]]
As a privately held company, MFA Motorways does not publicly disclose its financial data. However, revenue growth has been driven by: == International expansion into New Zealand and the UK. == [[source]]
Increasing demand for IoT-based fleet solutions. Subscription-based recurring revenue model. Market analysts estimate the fleet telematics industry to grow significantly, positioning MFA Motorways for further expansion.
Challenges and Risks
[[[ https://en.wikipedia.org/w/index.php?title=User:Vegavista2/sandbox&action=edit§ion=13.%7Cedit source]]]
MFA Motorways faces several challenges in the fleet management industry:
Regulatory Compliance – Navigating different regional fleet and IoT regulations. Cybersecurity Threats – Protecting sensitive vehicle and driver data from cyberattacks. Economic Uncertainty – Fluctuating fuel prices, vehicle costs, and logistics budgets affecting fleet operators. The company continues to mitigate these risks through strategic partnerships, R&D investment, and enhanced security protocols.
Future Plans[[source]]
MFA Motorways has ambitious expansion and innovation goals, including:
Expansion into North America and Southeast Asia.
AI-powered analytics tools to improve fleet efficiency and predictive maintenance.
Strategic partnerships with automobile manufacturers to integrate IoT solutions into new vehicle models.
The company remains focused on scaling its digital platforms and strengthening its global market presence.
See Also [Management Telematics Internet of Things (IoT)]
References[[source]]
[[ https://au.linkedin.com/in/leonardo-de-la-vega-a6479196.%7CMFA Motrways Company profile company]]
[eFleet]
[track]
In the lede of this article second paragraph, it mentions "prompting Israeli forces to fight back and apply the Hannibal Directive against its own citizens." The mention of the Hannibal directive is gratuitous and disputed by plenty of sources. At worst, the directive, according to disputed sources, led to 14 deaths. Given its extreme minor significance in the attack by Hamas, it should be removed from the second paragraph. The next sentence also makes it seem like it was the Hannibal directive and not Hamas which killed the majority of Israelis. (Personal attack removed) Apndrew (talk) 20:34, 8 February 2025 (UTC)
- @Apndrew: I would seriously reconsider using personal attacks when making any sort of WP:CT/A-I-related request. That's a good way to get hauled to WP:Arbitration/Requests/Enforcement and have to answer pointed questions to the satisfaction of a tetchy administrator who has to deal with this shit yet again. —Jéské Couriano v^_^v threads critiques 07:26, 9 February 2025 (UTC)
- Doesn't change the fact the the page has been vandalized to include a fringe and disputed theory in the second paragraph of the entry and now implies that it was Israel who was responsible for the deaths of 1,195 Israelis. Apndrew (talk) 14:48, 9 February 2025 (UTC)
- Doesn't change the fact the the page has been vandalized to include a fringe and disputed theory in the second paragraph of the entry and now implies that it was Israel who was responsible for the deaths of 1,195 Israelis. Apndrew (talk) 14:48, 9 February 2025 (UTC)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.