[02:28:33] [telegram] I do not know such policy. But you can import certain oldid and then upgrade it to the new revision manually if there are concerns. I guess in case of a userscript in any case. (re @jhsoby: Is there a global policy on importing user scripts to the MediaWiki namespace? There is a gadget in nnwiki which imports a user script from Meta. It kind of feels like a circumvention of the spirit of the whole interface admin thing) [02:29:21] [telegram] What is cross editing? Editing one after another? Editing within some timeframe? (re @ramzymuliawan: Is there any tool that could show the level of cross-edit between two/more users/IP in certain article(s)?) [06:54:59] [telegram] If I understand the reason for wanting it, then perhaps both? (re @Thecladis: What is cross editing? Editing one after another? Editing within some timeframe?) [06:55:18] [telegram] If I understand the reason for wanting such a tool, then perhaps both? (re @Thecladis: What is cross editing? Editing one after another? Editing within some timeframe?) [07:49:05] [telegram] ❤️Next generation of Bitcoin—Wrapped RavencoinWRVN is the GEM coin that you can't miss, WRVN bring RVN into DeFi, and now is the best time to buy! If you miss WRVN, you will be regret for the rest of your life.Uniswap: https://info.uniswap.org/pair/0xc320fa0a2c2c6bcee99ddb8b60f79338e9d11c0e : https://tools-static.wmflabs.org/bridgebot/f0c87ed7/file_3267.jpg [07:51:45] [telegram] You're correct. Put it simply, I would like to see with whom I cross my path most often, in which article. (re @mahir256: If I understand the reason for wanting such a tool, then perhaps both?) [09:21:44] [telegram] Maybe https://interaction-timeline.toolforge.org/ ? (re @ramzymuliawan: You're correct. Put it simply, I would like to see with whom I cross my path most often, in which article.) [13:06:58] [telegram] Yes. Just start a private @wikilinksbot and type /start , and it will give you a list of commands you can use in the group (you can try them out in the private chat beforehand). But note the commands are only available to group admins (or myself) to avoid accidental breakage (re @silente08: Regarding the wikilinksbot: I have just added it to an Italian-language wiki group. Is there any way to have it link to itwiki directly (wit [13:07:08] [telegram] Yes. Just start a private chat with @wikilinksbot and type /start , and it will give you a list of commands you can use in the group (you can try them out in the private chat beforehand). But note the commands are only available to group admins (or myself) to avoid accidental breakage (re @silente08: Regarding the wikilinksbot: I have just added it to an Italian-language wiki group. Is there any way to have it link to itwiki dir [13:07:52] [telegram] Ah, thanks! I will forward that to our admins [13:09:21] [telegram] You can tell them that the two commands they are likely to need are: [13:09:23] [telegram] /setwiki normallinks https://it.wikipedia.org/ [13:09:24] [telegram] and [13:09:26] [telegram] /setlang it (re @silente08: Ah, thanks! I will forward that to our admins) [13:15:51] [telegram] It worked, nice! 😁 [13:15:57] [telegram] 👍 [13:17:22] [telegram] game, set and match! [14:41:45] [telegram] Is there a "page header preview" planned? I mean the kind of thing you automatically get with application such as mattermost when you send a link. Actually, as I'm asking, I wonder if it really makes sense, it would rather be the work of the discussion application I guess. (re @jhsoby: in fact (almost) all links from [[m:Special:Interwiki]] work. Even stuff like [[dbdump:mediawikiwiki]] and [[iso639-3:nob]]) [15:16:07] [telegram] No – and that's a feature, not a bug. 😊 That is actually the default behaviour for links in Telegram, but I turned it off for all links the bot makes, because it would be very annoying – especially in groups like the Wikidata group where the bot is used a great deal. So a goal of mine was to keep the messages as small as possible (re @Psychoslave: Is there a "page header preview" planned? I mean the kind of thing you auto [17:05:23] [telegram] Oh I see [17:44:21] [telegram] GitLab is for code hosting and review; issue tracking will stay on Phabricator (re @Psychoslave: By the, I saw that Gitlab was introduce in the Wikimedia PaaS, but didn't go deep about how it was intended to be used. Does phabricator stay the main point to track tasks or is there a plane to move that into Gitlab?) [17:45:16] [telegram] (possibly tools&bots hosted there will be allowed to use GitLab for issue tracking if they want, I don’t know, but Phabricator will remain the primary issue tracker for MediaWiki) [19:10:52] [telegram] Ok thanks for the feedback. [19:30:03] [telegram] I like the Gitlab issue tracker, but both having a too much dispersion of task tracking or move massively to something else so shortly after the phabricator migration would have seem a large spend in effort without probably more cons than pros. [20:06:48] [telegram] Phabricator happened in 2014, it wasn't that recently. But sure [20:07:16] [telegram] To be fair it's still the case that not everything got moved to Phabricator [20:09:14] [telegram] Well, everything is relative. Five years is sure a whole era in digital innovation. On the other hand, change management is always [20:09:53] [telegram] a difficult challenge, as far as at least one human is implicated ❣️ [20:10:04] [telegram] 😋 [20:13:41] [telegram] Look all this cobol still at the foundation of critical business services out there. And it's not even something on which many user are directly attached to from a front end point of view, like an issue tracker.