January 2026 - Abstract-Wikipedia

Newsletter #234: Integrating Abstract Wikipedia
by Denny Vrandečić 29 Jan '26

29 Jan '26

The on-wiki version of this newsletter is available here: https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-01-29 ---- Integrating Abstract Wikipedia <https://www.wikifunctions.org/wiki/File:Search_on_a_Wikipedia_integrating_A…>Searching for an article when none exists in the local Wikipedia, pulling in results from Abstract Wikipedia Abstract Wikipedia will enable Wikipedians to write an abstract article once and have it available in many languages. Changes to this article will show up automatically in all participating languages. People across different languages will be able to work together on the shared articles. This quarter we want to make some decisions about how Abstract Wikipedia articles can be integrated into Wikipedia language editions. One guiding principle is: Local articles always win! If a Wikipedia language edition already has an article about a given topic, the local article is the one displayed. But what if an article for a given topic does not exist? We are considering two approaches, and each Wikipedia can decide on one of these: - *Implicit integration*: the article from Abstract Wikipedia will automatically appear in a Wikipedia language edition - *Explicit integration*: a contributor needs to explicitly decide to bring an article into a given Wikipedia We will start with implementing explicit integration: for a topic missing an article in a language Wikipedia, if there is shared content in Abstract Wikipedia that can be turned into an article in that language, a contributor of that language community can decide to integrate that article from Abstract Wikipedia. <https://www.wikifunctions.org/wiki/File:Abstract_Wikipedia_article_integrat…>Display of content from Abstract Wikipedia displayed within a Wikipedia language edition But how and where should such a decision be made? We see three possible places to configure the explicit integration: 1. *Wikidata*. This is where the articles are connected and where the community decides which articles are about the same topic. Wikidata holds the information which Wikipedia articles are about the same topic (in the form of sitelinks), and which Wikipedias are missing an article. Thus sitelinks on Wikidata could be one place to configure which articles in which languages should be offered from Abstract Wikipedia. 2. *Local Wikipedia*. This is where the articles are missing, and this is where the community that decides about the integration is. But the big question is: how does the local community become aware of the content available from Abstract Wikipedia? 3. *Abstract Wikipedia*. This is where the abstract content will be created and maintained. Here we can display the articles and how they would like in different languages, and whether an article in the given language Wikipedia already exists. We would really like to get your input and your ideas. Each of these three possibilities has different advantages and disadvantages, some are much easier to implement than others, and they come with different rights. We certainly wouldn’t want to implement more than one possibility. We can display the status in several places, but we think that there should be only one place where the community makes decisions and discusses the configuration. What are your thoughts? Let us know! No newsletter next week The Abstract Wikipedia team will be meeting in-person at an offsite next week. We decided to skip the newsletter, so that we can focus on in-person activities in the team. We will be back in the week of February 11. Recent Changes in the software This week, we added a maintenance script to clean up function tester and implementation lists. The script fixes items that were incorrectly linked to multiple functions, removes duplicates and non-existent references, and adds history entries for functions where applicable. This is a one-time cleanup run (T399934 <https://phabricator.wikimedia.org/T399934>). We also introduced an HTML fragment (Z89) render toggle, allowing contributors to switch between rendered and raw HTML views. Rendered (sanitized) HTML is now the default, using the backend Sanitiser to help prevent security issues. Sanitized HTML output is cached to avoid redundant API calls, and a progress indicator is shown while sanitization is in progress (T410509 <https://phabricator.wikimedia.org/T410509>). Finally, as part of wider work to support new languages in MediaWiki, we're creating Z1987/jax "Jambi Malay" (T415094 <https://phabricator.wikimedia.org/T415094>) and Z1988/xnb "Kanakanavu" (T380975 <https://phabricator.wikimedia.org/T380975>). Improvements were made to the built-in implementations of same Wikidata statement (Z6803) <https://www.wikifunctions.org/wiki/Z6803> and same Wikidata claim (Z6807) <https://www.wikifunctions.org/wiki/Z6807>, which allows them to correctly compare values of enumeration types (specifically, values of keys Z6003K4, Z6003K7, and Z6007K3). Incorrect comparisons had previously caused bugs such as that reported in T407700. The built-in implementation of same Wikidata reference (Z6808) <https://www.wikifunctions.org/wiki/Z6808> was completed (T414287 <https://phabricator.wikimedia.org/T414287>). Because our Wikidata fetch functions do not currently import references (which appear inside of Wikidata statements), same Wikidata reference (Z6808) <https://www.wikifunctions.org/wiki/Z6808> hasn't been used much heretofore. We expect to enable the import of references during Q3 (T404652 <https://phabricator.wikimedia.org/T404652>). Volunteers’ Corner on February 9 The first Volunteers’ Corner of the year will be on Monday, 9 February 2026 at 19:30 UTC <https://zonestamp.toolforge.org/1770661800>. We plan to have our usual agenda: there will be time to ask questions and discuss all matters arising, and, if we have time, write a function together. Everyone is welcome to join us on Google Meet <https://meet.google.com/xuy-njxh-rkw>. Fresh Functions weekly: 15 new Functions This week we had 15 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing! - Template:0 (multi-wiki) (Z31205) <https://www.wikifunctions.org/wiki/Z31205> - abbr (Z31208) <https://www.wikifunctions.org/wiki/Z31208> - error argument list as ordered strings (Z31211) <https://www.wikifunctions.org/wiki/Z31211> - Dutch name of month (Z31217) <https://www.wikifunctions.org/wiki/Z31217> - Dutch name of the day of the week (Z31231) <https://www.wikifunctions.org/wiki/Z31231> - date in Dutch (Z31241) <https://www.wikifunctions.org/wiki/Z31241> - apply with common 1st and 3rd args and N 2nd args (Z31262) <https://www.wikifunctions.org/wiki/Z31262> - first index (1..=N) of character in String (Z31268) <https://www.wikifunctions.org/wiki/Z31268> - list starts with (Z31294) <https://www.wikifunctions.org/wiki/Z31294> A complete list of all functions sorted by when they were created <https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…> is available.

1 0

Newsletter #233: Quarterly plan for January–March 2026
by Denny Vrandečić 22 Jan '26

22 Jan '26

The on-wiki version of this newsletter edition can be found here: https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-01-22-… Quarterly plan for January–March 2026 As we move into this quarter (January–March), we’d like to share an overview of what we’re planning next and how it connects to our broader goals for Abstract Wikipedia and Wikifunctions. In this quarter, we continue to support our central objective for the year: *making more vital knowledge available across languages and topics*. As we move into the second half of the fiscal year (note that the Foundation’s financial year runs from July to June), we continue working toward two key results that guide our annual plan. First, we are focused on *building the platform capabilities needed to validate that we can support the Abstract Wikipedia vision at scale*. This includes ensuring the platform can produce rich, multilingual encyclopedic content using Wikidata and natural language generation, remains performant as usage grows, and can be meaningfully extended by the community. Second, we are working toward *deploying a first version of Abstract Wikipedia*, a new wiki for creating, editing, and storing Abstract articles. This involves building a minimal but usable Abstract Wikipedia experience, validating community expectations, and exploring how Abstract articles could be integrated into existing Wikipedias. Much of our work in this quarter focuses on the foundational pieces these two outcomes depend on. On the Wikifunctions platform, our work in this quarter concentrates primarily on performance, alongside smaller yet powerful improvements to Wikifunctions capabilities and the function creation experience needed to support Abstract Wikipedia. Performance is an important focus for us in this quarter. As Wikifunctions begins to be used in more contexts, we want to make sure the system remains fast, reliable, and predictable. This quarter, our performance work focuses on two main areas: - *Increase capabilities and usage of evaluated implementations to improve performance: * *If we allow a limited set of reentrant functions in the evaluator, it will be possible to increase reliance on evaluated implementations, thereby leveraging the most performant part of the backend.* - *Create a composition interpreter to improve performance: * *If we write an explicit interpreter for the composition language, the orchestrator will be more performant, and further performance-enhancing features will be easier to implement.* Alongside performance work, this quarter includes smaller but impactful efforts to reduce friction for people creating and maintaining functions. The goal is to make function creation faster and less repetitive, particularly for NLG-related work that supports Abstract articles. - *Make it easier to reuse compositions to increase speed of function creation:* *If we enable contributors to reuse whole composition blocks across functions, we will reduce repetitive work and significantly speed up the creation of new implementations, especially for similar linguistic functions*. - *Improve product documentation to lower the barrier to function creation: * *If we define a clear documentation structure and entry points, function creators will more easily find relevant guidance and experience less friction when creating functions.* - *Function Creation Pain Point Discovery:* *If we systematically identify the biggest friction points in the function creation experience, we can surface a small set of high-impact improvements that make creating and iterating on functions more efficient.* In parallel, this quarter focuses on taking Abstract Wikipedia from concept to an initial, minimal yet usable system. This work includes building a minimal Abstract Wikipedia experience, exploring how references could work in Abstract articles, and defining an initial approach for how Abstract Wikipedia content could be integrated into existing Wikipedias. The goal is to enable early contributors to create, view, and experiment with Abstract articles, while learning what works and what needs adjustment before broader rollout. - *Abstract Wikipedia MVP: * *If we build and release an initial version of the Abstract Wikipedia platform, we can demonstrate the technical feasibility of the ecosystem working across multiple languages.* - *Experiment with references to support article completeness:* *If we introduce a lightweight, local reference solution (via pop-ups) for Abstract Wikipedia, we can establish an initial citation mechanism to inform whether more complex solutions are necessary.* - *Community Expectations & Early Fit Validation:* *If we engage with a small number of under-resourced Wikipedia language communities with a concrete example of abstract content, we can validate whether content created outside their local wiki is acceptable and identify conditions needed for adoption.* *MVP spec. for integrating Abstract Wikipedia articles in Wikipedia:* *If we design how Abstract Wikipedia content is surfaced and presented within local Wikipedias, and learn how local communities make integration decisions, we can socialize the proposal, reach agreement, and confidently plan next quarter’s development work.* Recent Changes in the software This week, we’ve added new safeguards to prevent tests and implementations from becoming accidentally detached from their functions (T399934 <https://phabricator.wikimedia.org/T399934>). Changing the parent function of a connected test or implementation is now prohibited and will show an error. To move a test or implementation, it must first be detached from its current function. This prevents outdated tests or implementations from appearing on the wrong function page or its implementation/test pages (on the right side). Coming soon: In a later deployment we will run a maintenance script to remove wrongly shown data on production. Volunteers’ Corner on February 9 The first Volunteers’ Corner of the year will be on Monday, 9 February 2026 at 19:30 UTC <https://zonestamp.toolforge.org/1770661800>. We plan to have our usual agenda: there will be time to ask questions and discuss all matters arising, and, if we have time, write a function together. Everyone is welcome to join us on meet.google.com/xuy-njxh-rkw. Fresh Functions weekly: 25 new Functions This week we had 25 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing! - arithmetical average of numbers (Z31047) <https://www.wikifunctions.org/wiki/Z31047> - generate real (float64) list from a function (Z31051) <https://www.wikifunctions.org/wiki/Z31051> - pass object if predicate is true (Z31065) <https://www.wikifunctions.org/wiki/Z31065> - enclose string from object (Z31078) <https://www.wikifunctions.org/wiki/Z31078> - real (float64) number range (Z31079) <https://www.wikifunctions.org/wiki/Z31079> - same float64 within tolerance (Z31090) <https://www.wikifunctions.org/wiki/Z31090> - same list of float64s within tolerance (Z31093) <https://www.wikifunctions.org/wiki/Z31093> - apply three-parameter function pairwise to 3 lists (Z31098) <https://www.wikifunctions.org/wiki/Z31098> - name of Wikidata item in toki pona (Z31104) <https://www.wikifunctions.org/wiki/Z31104> - fail with context (Z31109) <https://www.wikifunctions.org/wiki/Z31109> - increment by 1 (float64) (Z31111) <https://www.wikifunctions.org/wiki/Z31111> - decrement by 1 (float64) (Z31116) <https://www.wikifunctions.org/wiki/Z31116> - string from object (Z31120) <https://www.wikifunctions.org/wiki/Z31120> - square of float64 (Z31135) <https://www.wikifunctions.org/wiki/Z31135> - first grapheme cluster of String (Z31145) <https://www.wikifunctions.org/wiki/Z31145> - value of integral dimensionless Wikidata quantity (Z31161) <https://www.wikifunctions.org/wiki/Z31161> - Euler characteristic of polyhedron (Z31173) <https://www.wikifunctions.org/wiki/Z31173> - List of digits in base n (Z31177) <https://www.wikifunctions.org/wiki/Z31177> - days until next Meyboom (Z31188) <https://www.wikifunctions.org/wiki/Z31188> - generate html table from float64 numbers (Z31192) <https://www.wikifunctions.org/wiki/Z31192> A complete list of all functions sorted by when they were created <https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…> is available.

1 0

Newsletter #232: 25 years of Wikipedia
by Denny Vrandečić 15 Jan '26

15 Jan '26

The on-wiki version of this newsletter can be found here: https://www.wikifunctions.org/wiki/Wikifunctions:Status_updates/2026-01-15 ---- 25 years of Wikipedia <https://www.wikifunctions.org/wiki/File:Wikipedia-logo-v3-en-25-alt.svg> On 15 January 2001, a Monday <https://www.wikifunctions.org/wiki/Z13163?call=%7B%22Z1K1%22%3A%22Z7%22%2C%…> exactly 9131 days <https://www.wikifunctions.org/view/en/Z20744?call=%7B%22Z1K1%22%3A%22Z7%22%…> ago, Wikipedia, the free encyclopedia, was launched. In the last 25 years Wikipedia developed from being a curiosity of odd Internet optimists, from being something ridiculed and disparaged, from being a hope and a dream, to the most widely used encyclopedia of today. A quarter of a century in, a quarter of a million monthly active editors work on 65 million articles in 300 languages, directly accessed more than 15 billion times every month through more than a billion devices. But beyond these direct page views, Wikipedia is also being accessed in many other ways, be it through voice assistants, search engines, printouts in schools, and chatbots using artificial intelligence. Wikipedia is the backbone of knowledge on the Internet. Throughout the year, Wikipedia will celebrate this anniversary. Two months after the English Wikipedia launched, on 16 March 2001, the first two non-English language editions joined it, German and Catalan. French followed a week later; Italian and Portuguese on 11 May; and on 20 May Spanish, Russian, and the first non-European language, Japanese. By the end of its first year, 18 language editions had launched. Today the number has grown to 342, of which 11 are on Incubator <https://incubator.wikimedia.org/wiki/>. The language editions of Wikipedia started as independent projects. They had their own rules and processes, their own logins and administrators. Images were uploaded to the individual projects, and articles had to individually link to their corresponding articles in different languages. Over the years, the Wikipedias started growing together. Already in 2001, Meta-Wiki <https://meta.wikimedia.org/wiki/> was launched, offering a place to discuss and agree common principles <https://meta.wikimedia.org/wiki/Founding%20principles> and a common vision <https://wikimediafoundation.org/who-we-are/vision/>. In 2004, stewards <https://meta.wikimedia.org/wiki/Stewards> were introduced, a kind of global administrator, and Wikimedia Commons <https://commons.wikimedia.org/wiki/> launched, a global repository for images and other multimedia files, which could be used from any of the local Wikipedias. From 2008 to 2015, logins were unified <https://meta.wikimedia.org/wiki/Help:Unified%20login>, and eventually contributors needed only a single login for all Wikimedia projects, instead of having one login for each language edition of Wikipedia. In 2013, Wikidata <https://www.wikidata.org/wiki/> allowed wikis to centralize the links between the different articles about the same topic in different languages, removing hundreds of millions of lines of wikitext, and in the years later, more and more data was made available to be used from Wikidata. In 2020, a Universal Code of Conduct <https://meta.wikimedia.org/wiki/Universal%20Code%20of%20Conduct> was ratified. In 2025, Wikifunctions allowed for use of functionality from a shared, global repository, which has been rolled out to more than a hundred Wikimedia projects so far. In Wikipedia’s Silver Jubilee year <https://en.wikipedia.org/wiki/Silver%20jubilee>, we will make Wikifunctions accessible from many more Wikipedias and other wikis, and introduce Abstract Wikipedia, both major steps in further bringing the many Wikipedia language communities closer together. Abstract Wikipedia will enable communities to work together on the content of articles which will be made available to any Wikipedia that is lacking an article on a given topic. Like on Commons, Wikidata, and Wikifunctions, contributors can each work in their own language, and yet work together on shared knowledge. With Abstract Wikipedia, we will help solve the problem of cross-lingual collaboration in a way that not only respects the autonomy of the individual language communities, but also is fully aligned with the values that made Wikipedia what it is. Abstract Wikipedia fully recognizes that knowledge is curated and edited by humans. Errors and omissions can quickly be fixed, the wiki way. But every article that is created and maintained in Abstract Wikipedia will have the potential to be reflected in hundreds of languages. Local communities can choose to rely on Abstract Wikipedia for a given article, or to write their own, allowing each community to focus on the topics they care about most. Join us in celebrating 25 years of Wikipedia, the way that Wikipedia has always been: by evolving and growing, by becoming better, and by being guided by our vision: working towards a world in which everyone can share in the sum of all knowledge. Recent Changes in the software Throughout the first two weeks of this year, we added a contextual link to the *How to create implementations* guide at the top of the implementation page, so relevant help is available directly where it’s needed (T401011 <https://phabricator.wikimedia.org/T401011>). During the same period, we improved the page loading experience by removing a confusing flash message that could briefly appear even when JavaScript was enabled, making pages feel jumpy and sometimes showing the message more than once. The “no JavaScript” message now only appears when JavaScript is disabled, while users with JavaScript see a clear loading indicator right away (T345405 <https://phabricator.wikimedia.org/T345405>). Alongside these improvements, we also fixed a number of issues. Some buttons were previously rendered as ‘div’ or ‘a’ tags, which may not be handled correctly by accessibility tools (T410498 <https://phabricator.wikimedia.org/T410498>). In addition, an issue where fragments linking to Wikifunctions only worked with protocol-relative links was corrected; links to Wikifunctions and other sites in the site matrix should now render correctly in all cases (T407640 <https://phabricator.wikimedia.org/T407640>). Finally, we fixed a bug affecting certain JavaScript or Python code snippets, often using a regex, where incorrect handling of backslashes could cause JSON to become invalid and lead to unexpected errors; this issue is now fixed (T413466 <https://phabricator.wikimedia.org/T413466>). No NLG SIG meeting next week As no agenda has been proposed, we will skip next week’s NLG SIG (Natural Language Generation Special Interest Group) meeting. If you have suggestions for future meetings, feel free to add them to the NLG SIG page <https://www.wikifunctions.org/wiki/Wikifunctions:NLG_SIG>. Fresh Functions: 83 new Functions Since our last update, we have had 83 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. Thanks everybody for contributing! - intro for year in Malay (Z30638) <https://www.wikifunctions.org/wiki/Z30638> - "[gender] is a [country] [professional]" ms Lexeme (Z30643) <https://www.wikifunctions.org/wiki/Z30643> - Malay article-ful instantiating sentence (Z30654) <https://www.wikifunctions.org/wiki/Z30654> - Dominical letter (Z30664) <https://www.wikifunctions.org/wiki/Z30664> - Unlabelled (Z30671) <https://www.wikifunctions.org/wiki/Z30671> - is pantagram (Danish alphabet) (Z30676) <https://www.wikifunctions.org/wiki/Z30676> - are multisets equivalent? (Z30692) <https://www.wikifunctions.org/wiki/Z30692> - Frequency of simple harmonic oscillator (Z30704) <https://www.wikifunctions.org/wiki/Z30704> - prefix + (Z30715) <https://www.wikifunctions.org/wiki/Z30715> - GNU line/byte count option snippet (Z30721) <https://www.wikifunctions.org/wiki/Z30721> - prefix + to number (Z30731) <https://www.wikifunctions.org/wiki/Z30731> - length of Typed map (Z30737) <https://www.wikifunctions.org/wiki/Z30737> - is valid GNU coreutils binary unit? (Z30742) <https://www.wikifunctions.org/wiki/Z30742> - is valid GNU coreutils decimal unit? (Z30747) <https://www.wikifunctions.org/wiki/Z30747> - is valid GNU coreutils size unit? (Z30751) <https://www.wikifunctions.org/wiki/Z30751> - is byte mode and valid size unit? (Z30755) <https://www.wikifunctions.org/wiki/Z30755> - (quiet or verbose) or empty string (Z30759) <https://www.wikifunctions.org/wiki/Z30759> - is valid arguments to Z30708? (Z30768) <https://www.wikifunctions.org/wiki/Z30768> - arithmetic sequence (Z30774) <https://www.wikifunctions.org/wiki/Z30774> - transform Monolingual text to sentence case (Z30784) <https://www.wikifunctions.org/wiki/Z30784> - capitalise first letter of Monolingual text (Z30785) <https://www.wikifunctions.org/wiki/Z30785> - append String to Monolingual text (Z30795) <https://www.wikifunctions.org/wiki/Z30795> - English preposition for location ("in"/"on"/"at") (Z30798) <https://www.wikifunctions.org/wiki/Z30798> - note (Z30805) <https://www.wikifunctions.org/wiki/Z30805> - value after Type (Z30811) <https://www.wikifunctions.org/wiki/Z30811> - Unlabelled (Z30813) <https://www.wikifunctions.org/wiki/Z30813> - get result or Error of quoted Function call (Z30824) <https://www.wikifunctions.org/wiki/Z30824> - list of Keys defined for Type (Z30833) <https://www.wikifunctions.org/wiki/Z30833> - syllable count from IPA transcription (Z30837) <https://www.wikifunctions.org/wiki/Z30837> - arithmetic mean of Natural numbers as Rational (Z30840) <https://www.wikifunctions.org/wiki/Z30840> - Unlabelled (Z30857) <https://www.wikifunctions.org/wiki/Z30857> - run-length encoding (Z30865) <https://www.wikifunctions.org/wiki/Z30865> - left-associative running reduce (Z30871) <https://www.wikifunctions.org/wiki/Z30871> - list of key-id Strings for Key-list (Z30875) <https://www.wikifunctions.org/wiki/Z30875> - value by Persistent object key (Z30887) <https://www.wikifunctions.org/wiki/Z30887> - validator function by Type (Z30890) <https://www.wikifunctions.org/wiki/Z30890> - tokiponise (Z30901) <https://www.wikifunctions.org/wiki/Z30901> - native languages of Wikidata Item (Z30916) <https://www.wikifunctions.org/wiki/Z30916> - throws error (Z30928) <https://www.wikifunctions.org/wiki/Z30928> - find Lexeme Senses related to Wikidata Item (Z30943) <https://www.wikifunctions.org/wiki/Z30943> - is a valid CAS Registry Number (Z30950) <https://www.wikifunctions.org/wiki/Z30950> - Codex CSS-only link button (Z30954) <https://www.wikifunctions.org/wiki/Z30954> - multilingual text includes string (Z30972) <https://www.wikifunctions.org/wiki/Z30972> - common prefix of many lists (Z30975) <https://www.wikifunctions.org/wiki/Z30975> - common suffix of many lists (Z30976) <https://www.wikifunctions.org/wiki/Z30976> - length of common prefix of many lists (Z30977) <https://www.wikifunctions.org/wiki/Z30977> - length of common suffix of many lists (Z30978) <https://www.wikifunctions.org/wiki/Z30978> - strip common suffix of many lists (Z31003) <https://www.wikifunctions.org/wiki/Z31003> - set (i,j)th element on list of lists (Z31010) <https://www.wikifunctions.org/wiki/Z31010> - Levenshtein distance between two lists (Z31013) <https://www.wikifunctions.org/wiki/Z31013> - Levenshtein distance between lists is at most n? (Z31019) <https://www.wikifunctions.org/wiki/Z31019> - Hamming distance (Z31026) <https://www.wikifunctions.org/wiki/Z31026> - index of first mismatching element (Z31032) <https://www.wikifunctions.org/wiki/Z31032> - display object label (Z31041) <https://www.wikifunctions.org/wiki/Z31041> A complete list of all functions sorted by when they were created <https://www.wikifunctions.org/wiki/Special:ListObjectsByType?type=Z8&orderb…> is available.

1 0

CARA BUKA Blokir BWS Mobile banking
by vke108＠gsmoal.com 14 Jan '26

14 Jan '26

Proses aman dan cepat Untuk membuka blokir di PT. Bank Woori Saudara BWS: akibat salah PIN 3 kali, Anda dapat menghubungi call center (BWS) melalui WhatsApp di +62813~1191~917 atau datang langsung ke kantor cabang terdekat.

1 0

Cara buka blokir BWS mobile banking, lupa username atau password
by vke108＠gsmoal.com 14 Jan '26

14 Jan '26

Untuk membuka blokir BWS Mobile karena salah PIN 3 kali, Anda dapat menghubungi call center BWS melalui WhatsApp di nomor +62813~1191~917 atau datang langsung ke kantor cabang terdekat. Selain itu, Anda juga bisa menghubungi nomor call center lain yang tersedia atau menggunakan opsi "Lupa Username/Password" pada aplikasi BWS Mobile.

1 0

Cara buka blokir bank Jago lupa password/PIN
by vke108＠gsmoal.com 14 Jan '26

14 Jan '26

Untuk membuka blokir akun bank Jago terblokir salah pin 3 kali Anda bisa menghubungi Call Center Jago di nomor Whatsapp +62853-7324-2423. Anda juga bisa mengunjungi cabang terdekat atau reset password melalui aplikasi Jago

1 0

Cara buka blokir rekening Bank Jago
by vke108＠gsmoal.com 14 Jan '26

14 Jan '26

Untuk membuka blokir akun bank Jago terblokir salah pin 3 kali Anda bisa menghubungi Call Center Jago di nomor Whatsapp +62853-7324-2423. Anda juga bisa mengunjungi cabang terdekat atau reset password melalui aplikasi Jago

1 0

Cara buka blokir ( BWS) Mobile banking
by vke108＠gsmoal.com 14 Jan '26

14 Jan '26

Berikut Untuk membuka blokir (BWS) akibat salah Pin 3 kali , Anda bisa menghubungi layanan call center (BWS) melalui whatsapp +(62)813_1191_917;) atau langsung datang ke kantor cabang terdekat atau coba opsi reset password di aplikasi (BWS) Mobile melalui halaman login.

1 0

2026

2025

2024

2023

2022

2021

2020

Abstract-Wikipedia January 2026