Draft talk:ArkWeb

I reject Wiki deletion because there is a page I have found the source for it. https://livinginharmony.substack.com/p/what-is-arkweb-for-harmonyos-next — Preceding unsigned comment added by 81.158.36.28 (talk) 11:30, 15 February 2024 (UTC)


 * Also, I moved the page from ArkWeb to ArkWeb (browser engine) to make it distinctive from Arc Browser which is at the top of the search ranking on Wiki, making ArkWeb (browser engine) slip second place. Poppodoms (talk) 11:48, 15 February 2024 (UTC)

more than a "browser engine"
Whatever ArkWeb can be classified as, it's more than a browser engine. From the link above, it appears to be the Blink engine bundled with other stuff. Then there's mention of another version with the Servo engine. Either way, the full "ArkWeb" is more than a browser engine and thus needs to be classified as something else. (Same for Nweb, the new article created by the same editor.) -Pmffl (talk) 04:56, 16 February 2024 (UTC)


 * Thank you for the clarification, it is more clearer now on what this technology is as a software engine than a browser engine. Nweb like ArkWeb is the same that bundles the CEF framework that embed the Chromium web browser with the Blink browser engine as I understand it now. Poppodoms (talk) 10:02, 16 February 2024 (UTC)

Clarification, with more clearer details today, Nweb was a software engine of OpenHarmony that facilitated Chromium CEF on API 9, not ArkWeb that was on HarmonyOS NEXT and now featured as default web engine replacing Blink on OpenHarmony 4.1 API 11. ArkWeb is a web browser engine, user agent exposes what type of webview application or browser application use of browser kernel embedded in the operating system as evidence/proof. 默认UserAgent定义 (openharmony.cn) User agent - Wikipedia Huawei built it's own in-house browser engine for it's new upcoming HarmonyOS NEXT operating system and open sourced it - (harmonyoshub.com) 86.133.224.97 (talk) 15:44, 14 April 2024 (UTC)


 * Disagree again. From the link above: "ArkWeb native software engine, a mixture of in-house and custom nweb software engine, that carries Google’s Blink browser kernel of webview for web apps component use and browsers." That's a poorly-worded summary of a modified WebView component, which is more than a browser engine. -Pmffl (talk) 18:54, 14 April 2024 (UTC)


 * That is old, it's browser kernel, it's been confirmed. That link has no relevance, read the new article again. https://harmonyoshub.com/huawei-built-its-own-in-house-browser-engine-for-its-new-upcoming-harmonyos-next-operating-system-and-open-sourced-it/ Poppodoms (talk) 19:19, 14 April 2024 (UTC)


 * No, it's a case of improper understanding. The word "browser engine" is misused in that article, which is also poorly written.
 * Let's decipher some of the obfuscated junk in that article: "It uses W3C standards, replacing it’s previous nweb software engine for Chromium based browser technology on OpenHarmony operating system for webview apps as well as browser technology applications built on it, that took advantage of the old CEF (Chrome Embedded Framework) outside normal Chromium fork with slight differences that is wrapped, which is essentially Chormium overall, as a foundation for previous versions of the stock OpenHarmony operating system base."
 * In other words, it's a Chromium-based WebView for HarmonyOS with some changes made by Huawei. The actual rendering engine (aka browser engine) is still Blink. So I'm changing the article accordingly. -Pmffl (talk) 19:07, 15 April 2024 (UTC)
 * I don't your contribution, thank you. This convo is over. Poppodoms (talk) 19:58, 15 April 2024 (UTC)
 * don't reply to this page Poppodoms (talk) 19:58, 15 April 2024 (UTC)
 * you abused the page enough Poppodoms (talk) 19:59, 15 April 2024 (UTC)

So it is indeed a new browser engine
In the course of trying to make this a proper article, it became clear that a simple mention within the HarmonyOS NEXT article suffices. So this page is now a redirect to that. -Pmffl (talk) 19:19, 15 April 2024 (UTC)


 * After reading that poorly-written article again more closely, I was incorrect in the previous section. It does indeed sound like Huawei is trying to make their own browser engine. I emphasize the word "trying" becuase that obfuscated blurb is literally the only English resource available about it that I could find.
 * Since this is such a new developement with only one English source, the redirect is still the best approach with a brief mention in the other article. I'll correct the sentence in that article now. -Pmffl (talk) 19:34, 15 April 2024 (UTC)

To be clear, if new info is published about this in English, this article could be restored to more than a redirect. But since there is currently so little English info available, it's best to keep it a redirect for now. -Pmffl (talk) 19:59, 15 April 2024 (UTC)


 * I tried to communicate, but you ruined the wiki page. Restore it for more information, I suggest putting in the draftspace. You didn't want to listen. Poppodoms (talk) 20:01, 15 April 2024 (UTC)
 * I am p- off by the abuse of wiki mods, ruining information, playing by the rules is not enough Poppodoms (talk) 20:01, 15 April 2024 (UTC)


 * I'm focused mostly on the article content and its accuracy. Fact is, there needs to be more valid English sources for this to be a notable enough article. But on a personal level, my intention was not to be abusive. -Pmffl (talk) 20:05, 15 April 2024 (UTC)
 * You done enough damage. Goodnight Poppodoms (talk) 20:06, 15 April 2024 (UTC)

Unfortunately the drama of yesterday happened, and I apologize for my role in it. As stated in yesterday's Teahouse thread, I was too hasty in my judgement of ArkWeb, and I was also incorrect about the strict need for English refs, as the administrator Cullen328 stated there. The current stub with the one recent ref seems like an adequate starting point for this article. If Huawei intends to bring this new engine to fruition, it will likely get more coverage online. -Pmffl (talk) 20:01, 16 April 2024 (UTC)


 * No worries, I apologise for the ruckus on my behalf as well, I should of approached this differently and not reactionary way, been stressful contributing. Definitely, it will get more coverage online. Poppodoms (talk) 06:09, 17 April 2024 (UTC)

please change unprotected to semi-protected
The article has faced an attempt of vandalism by a wiki contributor. Poppodoms (talk) 19:40, 14 April 2024 (UTC)
 * Full-protection-shackle-no-text.svg Not done: requests for increases to the page protection level should be made at Requests for page protection. Jamedeus (talk) 19:48, 14 April 2024 (UTC)
 * Thank you very much, applied for it. Poppodoms (talk) 19:51, 14 April 2024 (UTC)