User talk:RexxS/Archive 48
 | This is an archive of past discussions about User:RexxS. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 45 | Archive 46 | Archive 47 | Archive 48 | Archive 49 | Archive 50 | → | Archive 55 |
Diver rename
Hello. I renamed these pages to someone who reading understand what means and native abbreviations can be with name in english in template with connection for page in english page who have and original name in article. This is english wikipedia for english language and mostly users dont understand frensh, spanish or german here. But if this that i do out the rules, i accept mistake. Greetings :) --Filipid011 (talk) 13:35, 14 March 2019 (UTC)
- Hi, Filipid011 I agree with your intention, and it is laudable to attempt to make things easier for English readers. I think that in this case however, anybody wanting to learn more about the French (or Spanish) underwater federations would almost certainly recognise their names, although I think that the abbreviations, FFESSM and FEDAS would be the most recognisable. We don't have rules on Wikipedia; we just try to do our best. How about if we tried French underwater federation (FFESSM) and Spanish underwater federation (FEDAS) for the template? Do you think that might meet both of our concerns? --RexxS (talk) 16:34, 14 March 2019 (UTC)
I agree that you for abbreviations with native names, if people will knows more what they means. Greetings! :) --Filipid011 (talk) 00:35, 14 March 2019 (UTC)
- @Filipid011: I've made the change to Template:Diver organisations. Let's see if anybody objects. --RexxS (talk) 00:38, 15 March 2019 (UTC)
- @RexxS: if mostly abbreviations are agree with names, i think that be more better and others two gone in same level in this way. they will know and without translate :) --Filipid011 (talk) 00:56, 15 March 2019 (UTC)
- @RexxS: It was usefully talking. it me help to more knowledge for future articles here. Thanks :) --Filipid011 (talk) 01:02, 15 March 2019 (UTC)
Help with image in parent/child template
I'm having a problem at the Silver Quilty article, where both the parent infobox and the child module are displaying the photo entered. I can't figure out why. Can you help? Thanks.
- @Flibirigit: the child infobox, Template:Infobox CFL biography, fetches the image and caption from Wikidata by default if those parameters are omitted. You have to supply a blank parameter like
|image=to suppress that behaviour. It wasn't documented, so you weren't to know. I've added that to Silver Quilty now, and I've updated the template documentation to explain the behaviour, but it really needs an overhaul to require explicit permission at the article level to fetch Wikidata. --RexxS (talk) 19:31, 15 March 2019 (UTC)- Thanks for the explanation and the help! Flibirigit (talk) 22:37, 15 March 2019 (UTC)
NPR Newsletter No.17
Hello RexxS,
- News
- The WMF has announced that Google Translate is now available for translating articles through the content translation tool. This may result in an increase in machine translated articles in the New Pages Feed. Feel free to use the {{rough translation}} tag and gently remind (or inform) editors that translations from other language Wikipedia pages still require attribution per WP:TFOLWP.
- Discussions of interest
- Two elements of CSD G6 have been split into their own criteria: R4 for redirects in the "File:" namespace with the same name as a file or redirect at Wikimedia Commons (Discussion), and G14 for disambiguation pages which disambiguate zero pages, or have "(disambiguation)" in the title but disambiguate a single page (Discussion).
- {{db-blankdraft}} was merged into G13 (Discussion)
- A discussion recently closed with no consensus on whether to create a subject-specific notability guideline for theatrical plays.
- There is an ongoing discussion on a proposal to create subject-specific notability guidelines for chemicals and organism taxa.
- Reminders
- NPR is not a binary keep / delete process. In many cases a redirect may be appropriate. The deletion policy and its associated guideline clearly emphasise that not all unsuitable articles must be deleted. Redirects are not contentious. See a classic example of the templates to use. More templates are listed at the R template index. Reviewers who are not aware, do please take this into consideration before PROD, CSD, and especially AfD because not even all admins are aware of such policies, and many NAC do not have a full knowledge of them.
- NPP Tools Report
- Superlinks – allows you to check an article's history, logs, talk page, NPP flowchart (on unpatrolled pages) and more without navigating away from the article itself.
- copyvio-check – automatically checks the copyvio percentage of new pages in the background and displays this info with a link to the report in the 'info' panel of the Page curation toolbar.
- The NPP flowchart now has clickable hyperlinks.
Six Month Queue Data: Today – Low – 2393 High – 4828
Looking for inspiration? There are approximately 1000 female biographies to review.
Stay up to date with even more news – subscribe to The Signpost.
Go here to remove your name if you wish to opt-out of future mailings.
--MediaWiki message delivery (talk) 23:18, 15 March 2019 (UTC)
Nomination of Rapid Onset Gender Dysphoria for deletion
A discussion is taking place as to whether the article Rapid Onset Gender Dysphoria is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.
The article will be discussed at Wikipedia:Articles for deletion/Lisa Littman until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. Safrolic (talk) 09:27, 19 March 2019 (UTC)
ANI Notice
There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. — MarkH21 (talk) 22:58, 20 March 2019 (UTC)
Hoping you could help me out
Hey, I've tested theory to see if some sort of OOP with inheritance can be done in modules and with some simple code managed to get it working at User:Gonnym/sandbox. This is just a simple string replacement atm. So my next step is to see if I can get a complete infobox to work with inheritance. For that I've imported the French infobox module which allows creating (clean) infoboxes through modules (which ours doesn't). I'm currently trying to decipher the code and see what I need to change to get it to work here. As you have a lot of experience with Lua and created WikidataIB (this module has some calls to Wikidata which I'm not sure what to do with), I was hoping you could help me out here. The basic setup is at Module:Sandbox/Gonnym/infoboxFR and Module:Sandbox/Gonnym/Localdata. --Gonnym (talk) 08:22, 24 March 2019 (UTC)
- @Gonnym: Lua has fairly robust documentation. You might start with [1] and start reading from there. :) --Izno (talk) 15:50, 24 March 2019 (UTC)
- Thanks Izno, I know Lua enough to code on Wikipedia. What I don't know is how we implement templatestyles and how to convert the FR wikidata calls to WikidataIB calls. The documentation you linked does neither as far as I remember last time I checked it. Also, as a side note, a general documentation about Lua does not really help with advance Wikipedia modules from my experience. If you have any other documentation that can help with that I'd be happy to read it. --Gonnym (talk) 19:03, 24 March 2019 (UTC)
- @Gonnym: Sorry I'm late replying, but I've been at a WMUK board meeting all day. It's certainly an ambitious undertaking to try to create a complete infobox, so kudos for attempting.
- 1. Can I suggest you check out the documentation on mediawiki, specifically for the Scribunto implementation at mw:Extension:Scribunto/Lua reference manual, and the Wikibase client at mw:Extension:Wikibase Client/Lua.
- 2. What you really need to do is to get familiar with how Wikidata stores stuff. Once you know that, you're not limited to how the Wikibase client does the higher-level functions. In other words, you write those functions yourself to do the job as you see it. There is a utility function to dump an entire Wikdata item: you paste
{{#invoke:Wikidata|Dump}}into a section of an article on enwiki and preview it. You'll see the entire thing, statements, descriptions, labels, sitelinks, and so on, in a pretty-print-style output. If you want to just look at a statement you can use a function I wrote that has a wrapper temple called {{examine}}. If you want to see how instance of (P31) is stored for Douglas Adams (Q42), you just use:{{examine | P31 | Q42}}→
- Thanks Izno, I know Lua enough to code on Wikipedia. What I don't know is how we implement templatestyles and how to convert the FR wikidata calls to WikidataIB calls. The documentation you linked does neither as far as I remember last time I checked it. Also, as a side note, a general documentation about Lua does not really help with advance Wikipedia modules from my experience. If you have any other documentation that can help with that I'd be happy to read it. --Gonnym (talk) 19:03, 24 March 2019 (UTC)
table#1 {
table#2 {
["id"] = "Q42$F078E5B3-F9A8-480E-B7AC-D97778CBBEF9",
["mainsnak"] = table#3 {
["datatype"] = "wikibase-item",
["datavalue"] = table#4 {
["type"] = "wikibase-entityid",
["value"] = table#5 {
["entity-type"] = "item",
["id"] = "Q5",
["numeric-id"] = 5,
},
},
["property"] = "P31",
["snaktype"] = "value",
},
["qualifiers"] = table#6 {
["P805"] = table#7 {
table#8 {
["datatype"] = "wikibase-item",
["datavalue"] = table#9 {
["type"] = "wikibase-entityid",
["value"] = table#10 {
["entity-type"] = "item",
["id"] = "Q42395533",
["numeric-id"] = 42395533,
},
},
["hash"] = "eed7690a3685dc7a62a579e7222b5e9a367d8192",
["property"] = "P805",
["snaktype"] = "value",
},
},
},
["qualifiers-order"] = table#11 {
"P805",
},
["rank"] = "normal",
["references"] = table#12 {
table#13 {
["hash"] = "a4d108601216cffd2ff1819ccf12b483486b62e7",
["snaks"] = table#14 {
["P248"] = table#15 {
table#16 {
["datatype"] = "wikibase-item",
["datavalue"] = table#17 {
["type"] = "wikibase-entityid",
["value"] = table#18 {
["entity-type"] = "item",
["id"] = "Q19938912",
["numeric-id"] = 19938912,
},
},
["property"] = "P248",
["snaktype"] = "value",
},
},
["P268"] = table#19 {
table#20 {
["datatype"] = "external-id",
["datavalue"] = table#21 {
["type"] = "string",
["value"] = "11888092r",
},
["property"] = "P268",
["snaktype"] = "value",
},
},
["P407"] = table#22 {
table#23 {
["datatype"] = "wikibase-item",
["datavalue"] = table#24 {
["type"] = "wikibase-entityid",
["value"] = table#25 {
["entity-type"] = "item",
["id"] = "Q150",
["numeric-id"] = 150,
},
},
["property"] = "P407",
["snaktype"] = "value",
},
},
["P813"] = table#26 {
table#27 {
["datatype"] = "time",
["datavalue"] = table#28 {
["type"] = "time",
["value"] = table#29 {
["after"] = 0,
["before"] = 0,
["calendarmodel"] = "http://www.wikidata.org/entity/Q1985727",
["precision"] = 11,
["time"] = "+2022-10-09T00:00:00Z",
["timezone"] = 0,
},
},
["property"] = "P813",
["snaktype"] = "value",
},
},
},
["snaks-order"] = table#30 {
"P248",
"P268",
"P407",
"P813",
},
},
table#31 {
["hash"] = "f38b0c50096908694fe215d33497be11eb3f9d3b",
["snaks"] = table#32 {
["P227"] = table#33 {
table#34 {
["datatype"] = "external-id",
["datavalue"] = table#35 {
["type"] = "string",
["value"] = "119033364",
},
["property"] = "P227",
["snaktype"] = "value",
},
},
["P248"] = table#36 {
table#37 {
["datatype"] = "wikibase-item",
["datavalue"] = table#38 {
["type"] = "wikibase-entityid",
["value"] = table#39 {
["entity-type"] = "item",
["id"] = "Q36578",
["numeric-id"] = 36578,
},
},
["property"] = "P248",
["snaktype"] = "value",
},
},
["P407"] = table#40 {
table#41 {
["datatype"] = "wikibase-item",
["datavalue"] = table#42 {
["type"] = "wikibase-entityid",
["value"] = table#43 {
["entity-type"] = "item",
["id"] = "Q188",
["numeric-id"] = 188,
},
},
["property"] = "P407",
["snaktype"] = "value",
},
},
["P813"] = table#44 {
table#45 {
["datatype"] = "time",
["datavalue"] = table#46 {
["type"] = "time",
["value"] = table#47 {
["after"] = 0,
["before"] = 0,
["calendarmodel"] = "http://www.wikidata.org/entity/Q1985727",
["precision"] = 11,
["time"] = "+2022-10-09T00:00:00Z",
["timezone"] = 0,
},
},
["property"] = "P813",
["snaktype"] = "value",
},
},
},
["snaks-order"] = table#48 {
"P248",
"P227",
"P407",
"P813",
},
},
table#49 {
["hash"] = "caec066cc354e31c5e0a0178463b47a0590b40da",
["snaks"] = table#50 {
["P248"] = table#51 {
table#52 {
["datatype"] = "wikibase-item",
["datavalue"] = table#53 {
["type"] = "wikibase-entityid",
["value"] = table#54 {
["entity-type"] = "item",
["id"] = "Q50358336",
["numeric-id"] = 50358336,
},
},
["property"] = "P248",
["snaktype"] = "value",
},
},
["P813"] = table#55 {
table#56 {
["datatype"] = "time",
["datavalue"] = table#57 {
["type"] = "time",
["value"] = table#58 {
["after"] = 0,
["before"] = 0,
["calendarmodel"] = "http://www.wikidata.org/entity/Q1985727",
["precision"] = 11,
["time"] = "+2024-02-17T00:00:00Z",
["timezone"] = 0,
},
},
["property"] = "P813",
["snaktype"] = "value",
},
},
["P950"] = table#59 {
table#60 {
["datatype"] = "external-id",
["datavalue"] = table#61 {
["type"] = "string",
["value"] = "XX1149955",
},
["property"] = "P950",
["snaktype"] = "value",
},
},
},
["snaks-order"] = table#62 {
"P248",
"P813",
"P950",
},
},
},
["type"] = "statement",
},
}
- That's a lot of stuff, isn't it? just to store
{{wdib |fwd=ALL |osd=n |P31 |qid=Q42}}→ human
- Actually, there's a bunch of references to prove he was human, and that takes up most of the stored value for that statement.
- 3. Anyway, once you've got your head around that, why not take a look inside Module:WikidataIB? You'll find routines to scan through the values of a statement and its qualifiers; to render the value for wikidata-items; for dates; for quantities; for monolingual text; and for strings. The module works with getBestStatements() and getAllStatements() which are not expensive calls, unlike getEntity() when not reading from the connected Wikidata item. Of course, if you're making a whole infobox, it may be quite reasonable to use getEntity(), rather than the individual calls to get properties. You may have to experiment. Any of those routines is freely available to re-use either as code, or by requiring Module:WikidataIB – you may have to make copies of any local functions you're interested in exporting by adding a line near the end of Module:WikidataIB like
p.rendersnak = rendersnak, etc. - 4. Template styles is a bit of non-entity in Lua: you just literally add a class to an html element. Then you use the corresponding template style.css to define how to style that class. If you haven't used templatestyles, have a look at Template:Thermometer which I made as a teaching demo.
- The only other thing I can suggest is to do some basic stuff yourself and ping me if something doesn't work how you expected, or you can't see how to implement some feature. I'm always happy to help, but it's much easier to help if it's an absolutely specific point, rather than something as nebulous as an entire infobox in Lua. Happy coding! --RexxS (talk) 21:05, 24 March 2019 (UTC)
- That's a lot of stuff, isn't it? just to store
mystique
Regarding this edit: I'm having a bit of trouble parsing While we attempt to retain a mystique about modules compared with templates, we're discouraging capable coders from getting started on using Scribunto.
Do you mean to say something like "By retaining a mystique about modules compared with templates..."? "While we attempt" sounds like a positive affirmation that some set of persons is promoting a mystique, and I'm not clear that is the case, beyond the natural tendency of those unfamiliar with a particular bit of technology to treat it as magic (a la Clarke's third law). isaacl (talk) 17:45, 26 March 2019 (UTC)
- @Isaacl: The Wizard of Oz maintained his authority by maintaining a mystique about his abilities. He jealously guarded the little bit of extra knowledge he had in order to keep his position. The same mindset is commonplace among programmers. Many times I've observed coders who try to keep their knowledge to themselves, so that they become indispensable at work. I worry that the same applies to the adoption of Scribunto modules, through a reluctance to encourage potential coders to use Scribunto, preferring to steer them towards templates and parser functions. I see that regularly on Wikipedia, so I think I'm entitled to express the opinion that it's a real effect.
- We know there's nothing "magical" about Lua, and anyone familiar with JavaScript or Python can pick it up in very short time. Even those new to programming usually find Lua a good introduction. For the last two years, I've been a mentor for Wikimedia at Google Code-in with the remit to introduce pre-university students to programming in Lua. Of the dozens who participated, the vast majority achieved decent competence in the language in the space of a few days, even with no previous experience in any language.
- I think we ought to be going out of our way to positively encourage editors to experiment with modules and Scribunto, and I'm very suspicious of those who take the line that "this could be done in a template". --RexxS (talk) 18:12, 26 March 2019 (UTC)
- Yes, I understood your objections to the mystique from the start. I suppose it's the "we attempt" part that is confusing to me, because that appears to include you, as the author of the sentence, which is at odds with the rest of the paragraph. isaacl (talk) 18:36, 26 March 2019 (UTC)
- @Isaacl: Thanks, I get our point now. When I used the expression
"While we attempt to retain a mystique about modules ..."
, I intended to use "we" to indicate the editing community as a whole. I suppose that my inclusion of myself would make sense subconsciously, because I think that had I failed to speak out against creating a mystique, I would have been effectively endorsing it. I'm sorry I wasn't clear. --RexxS (talk) 19:22, 26 March 2019 (UTC)
- @Isaacl: Thanks, I get our point now. When I used the expression
- Yes, I understood your objections to the mystique from the start. I suppose it's the "we attempt" part that is confusing to me, because that appears to include you, as the author of the sentence, which is at odds with the rest of the paragraph. isaacl (talk) 18:36, 26 March 2019 (UTC)
Facto Post – Issue 22 – 28 March 2019
Facto Post – Issue 22 – 28 March 2019
 The Editor is Charles Matthews, for ContentMine. Please leave feedback for him, on his User talk page.
To subscribe to Facto Post go to Wikipedia:Facto Post mailing list. For the ways to unsubscribe, see the footer.
Half a century ago, it was the era of the mainframe computer, with its air-conditioned room, twitching tape-drives, and appearance in the title of a spy novel Billion-Dollar Brain then made into a Hollywood film. Now we have the cloud, with server farms and the client–server model as quotidian: this text is being typed on a Chromebook. The term Applications Programming Interface or API is 50 years old, and refers to a type of software library as well as the interface to its use. While a compiler is what you need to get high-level code executed by a mainframe, an API out in the cloud somewhere offers a chance to perform operations on a remote server. For example, the multifarious bots active on Wikipedia have owners who exploit the MediaWiki API. APIs (called RESTful) that allow for the GET HTTP request are fundamental for what could colloquially be called "moving data around the Web"; from which Wikidata benefits 24/7. So the fact that the Wikidata SPARQL endpoint at query.wikidata.org has a RESTful API means that, in lay terms, Wikidata content can be GOT from it. The programming involved, besides the SPARQL language, could be in Python, younger by a few months than the Web. Magic words, such as occur in fantasy stories, are wishful (rather than RESTful) solutions to gaining access. You may need to be a linguist to enter Ali Baba's cave or the western door of Moria (French in the case of "Open Sesame", in fact, and Sindarin being the respective languages). Talking to an API requires a bigger toolkit, which first means you have to recognise the tools in terms of what they can do. On the way to the wikt:impactful or polymathic modern handling of facts, one must perhaps take only tactful notice of tech's endemic problem with documentation, and absorb the insightful point that the code in APIs does articulate the customary procedures now in place on the cloud for getting information. As Owl explained to Winnie-the-Pooh, it tells you The Thing to Do.
If you wish to receive no further issues of Facto Post, please remove your name from our mailing list. Alternatively, to opt out of all massmessage mailings, you may add Category:Wikipedians who opt out of message delivery to your user talk page.
Newsletter delivered by MediaWiki message delivery |
MediaWiki message delivery (talk) 11:45, 28 March 2019 (UTC)
Oops... thank you
... for re adding the ref I inadvertently removed on Fermat's Last Theorem. Missed it completely! That spinning cube is quite effective. Makes me want to run aw...Zzzzzzzzzzzzzz. Littleolive oil (talk) 23:19, 31 March 2019 (UTC)
Edit summaries
Hi, RexxS - how difficult would it be to add a 👍🏻 or ❤️ in addition to "thank" as options in the revision history? Atsme Talk 📧 02:05, 2 April 2019 (UTC)
- While you're at it, please add an "lol" option too. Lourdes 03:58, 2 April 2019 (UTC)
- 🤮 💩 Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:53, 2 April 2019 (UTC)
- How about changing "thank" to "emoji" so that it generates a pop-up of various emojis to choose from?
Atsme Talk 📧 13:13, 2 April 2019 (UTC)
- @Atsme: Sorry for the late reply; I was a tad busy over at RfA last night. Anyway, I think that might be more awkward than it first seems. I haven't looked in detail yet, but the [thank] link has quite a lot of work to do – not only issuing the "X thanked you for your edit..." notification, but also logging it for reference. If you included other similar links like wikilove, you would need to set up a duplicate logging system. I'm pretty sure the intention is hold folks accountable if they go on a "thanking" spree, and I guess the same would be true for any other similar link. Because the functionality is built in to the MediaWiki software, i.e. it's available on all wikis, we might have a problem in gaining acceptance from all of the other projects to make changes to the core code. The option would be to write an extension that could be installed on just the wikis that wanted it, but that would be a lot of work, and I'm not sure the devs would assign any priority to a minor feature like this. Nevertheless one of the talk=page watchers might come up with a brilliant idea and prove me wrong. It wouldn't be the first time. Cheers --RexxS (talk) 14:18, 2 April 2019 (UTC)
- (+1) There's practically zero chance of developers bothering any about it and I will bet that you would not get any consensus over VPT either. To be succinct; it's too much work (and esp. visual clutter) for too little gain. I don't know whether Atsme means Wikilove as to the proposed ❤️ button but if you want to avail a facility that allows you to easily send wiki-love to a user from the diff-view/history-view (and comes with some boilerplate message along with the part. diff), that can be most probably done. ∯WBGconverse 17:53, 2 April 2019 (UTC)
- No, just wanted to embellish the Thank feature a tiny bit. When looking at a diff, our only option is to edit, undo, or thank. I was just hoping instead of just "thank" we could embellish with a few emoji choices, like ❤️, 😂, 👍🏻.
- Bear in mind that not everybody can see those characters. For me, only one of them (❤️) is meaningful; two are invisible, and the other five show up as a plain white rectangle outlined in black. Putting those characters through an external tool allows me to find the hex codepoints and thereby use another website to work out what they're supposed to look like, i.e. ❤ 'HEAVY BLACK HEART' (U+2764); ️ 'VARIATION SELECTOR-16' (U+FE0F); 🏻 'EMOJI MODIFIER FITZPATRICK TYPE-1-2' (U+1F3FB); 👍 'THUMBS UP SIGN' (U+1F44D); 💩 'PILE OF POO' (U+1F4A9); 📧 'E-MAIL SYMBOL' (U+1F4E7); 😂 'FACE WITH TEARS OF JOY' (U+1F602); 🤮 'FACE WITH OPEN MOUTH VOMITING' (U+1F92E). --Redrose64 🌹 (talk) 20:59, 2 April 2019 (UTC)
- Oh my...that's downright 💔 (a heart breaking) - but what about these? Atsme Talk 📧 21:09, 2 April 2019 (UTC)
- SVG images (or their PNG representations) are not a problem but for accessibility reasons you should have alt text. --Redrose64 🌹 (talk) 21:45, 2 April 2019 (UTC)
- Oh my...that's downright 💔 (a heart breaking) - but what about these? Atsme Talk 📧 21:09, 2 April 2019 (UTC)
- Bear in mind that not everybody can see those characters. For me, only one of them (❤️) is meaningful; two are invisible, and the other five show up as a plain white rectangle outlined in black. Putting those characters through an external tool allows me to find the hex codepoints and thereby use another website to work out what they're supposed to look like, i.e. ❤ 'HEAVY BLACK HEART' (U+2764); ️ 'VARIATION SELECTOR-16' (U+FE0F); 🏻 'EMOJI MODIFIER FITZPATRICK TYPE-1-2' (U+1F3FB); 👍 'THUMBS UP SIGN' (U+1F44D); 💩 'PILE OF POO' (U+1F4A9); 📧 'E-MAIL SYMBOL' (U+1F4E7); 😂 'FACE WITH TEARS OF JOY' (U+1F602); 🤮 'FACE WITH OPEN MOUTH VOMITING' (U+1F92E). --Redrose64 🌹 (talk) 20:59, 2 April 2019 (UTC)
- No, just wanted to embellish the Thank feature a tiny bit. When looking at a diff, our only option is to edit, undo, or thank. I was just hoping instead of just "thank" we could embellish with a few emoji choices, like ❤️, 😂, 👍🏻.
- (+1) There's practically zero chance of developers bothering any about it and I will bet that you would not get any consensus over VPT either. To be succinct; it's too much work (and esp. visual clutter) for too little gain. I don't know whether Atsme means Wikilove as to the proposed ❤️ button but if you want to avail a facility that allows you to easily send wiki-love to a user from the diff-view/history-view (and comes with some boilerplate message along with the part. diff), that can be most probably done. ∯WBGconverse 17:53, 2 April 2019 (UTC)
- @Atsme: Sorry for the late reply; I was a tad busy over at RfA last night. Anyway, I think that might be more awkward than it first seems. I haven't looked in detail yet, but the [thank] link has quite a lot of work to do – not only issuing the "X thanked you for your edit..." notification, but also logging it for reference. If you included other similar links like wikilove, you would need to set up a duplicate logging system. I'm pretty sure the intention is hold folks accountable if they go on a "thanking" spree, and I guess the same would be true for any other similar link. Because the functionality is built in to the MediaWiki software, i.e. it's available on all wikis, we might have a problem in gaining acceptance from all of the other projects to make changes to the core code. The option would be to write an extension that could be installed on just the wikis that wanted it, but that would be a lot of work, and I'm not sure the devs would assign any priority to a minor feature like this. Nevertheless one of the talk=page watchers might come up with a brilliant idea and prove me wrong. It wouldn't be the first time. Cheers --RexxS (talk) 14:18, 2 April 2019 (UTC)
- How about changing "thank" to "emoji" so that it generates a pop-up of various emojis to choose from?
Need to alert your page stalkers
So...I see you haven't posted a talkpage notice that you have an RfA pending...? How modest of you, but c'mon. Let your friends know! ;) Montanabw(talk) 22:09, 2 April 2019 (UTC)
The medical claims section looks pretty poorly sourced and violation of WP:MEDRS. I removed it, but it's been added back. Harizotoh9 (talk) 01:22, 11 April 2019 (UTC)