User talk:Sarangbot

This user has an alternate account named Sarang.

As mentioned in Commons:Bots#Bot accounts (...Semi-automated tools (e.g. Javascript tools) are not normally considered to be bots and do not require a separate account, but some users choose to use a separate account for non-bot but high-speed editing) I am trying to use a bot account without the bot flag, to "prevent my contribs lists from being swamped by edits" (Commons:Bots#Bot flag). I intend to use this account for the semi-automated tool VFC.
This account is rather an official sock puppet of user Sarang than a real bot - I understand the information that this is not very usual but conforms more or less to the rules? Sarangbot (talk) 14:22, 20 May 2017 (UTC)[reply]

(contributions)

디터 (talk) 10:55, 4 March 2023 (UTC)[reply]

Was hat es mit Sarang auf sich? Auf jeden Fall führt sie dazu, dass man folgende Warnung bekommt: "Warnung: Template:Created with CorelDRAW/hsb ruft Template:T mit mehr als einem Wert für den Parameter „1“ auf. Nur der letzte angegebene Wert wird verwendet." Kann man da was machen? --Arnd (talk) 10:07, 24 August 2018 (UTC)[reply]

@Aschroet: Ja, da kann man sehr wohl etwas machen: die Vorlage Created with CorelDRAW/hsb löschen. Das sollte schon vor Monaten erfolgt sein, aber delete requests - vor allem mass deletes - scheinen ihre Zeit zu brauchen. Mich wundert nur, wie du da ran gekommen, bzw darüber gestolpert bist? Verrätst du es mir? -- sarang♥사랑 13:10, 24 August 2018 (UTC)[reply]

I don't think it is appropriate to remove all mention of the account that uploaded an image. For example, in this edit, Sarangbot changed "Author=Ed ([[User talk:Edgar181|Edgar181]])" to "author=Ed", removing my username and removing link to my userpage. This causes loss of essential information regarding authorship. Regards, Ed (Edgar181) 15:57, 9 September 2018 (UTC)[reply]

@Edgar181: Sorry, I didn't see it, it was done by the script. Because many users write their user name and also their user talk page link (e.g. by their signature ~~~), which should not be (an author is always the user but not his talk page) the script automatically removes the talk page link. In your case, it should be |author=Ed - without the talk page. Sarangbot (talk) 16:14, 9 September 2018 (UTC)[reply]

I understand. I will change the template I use for uploads to include a link to my user page rather than my user talk page. Regards, Ed (Edgar181) 16:18, 9 September 2018 (UTC)[reply]

This will be a perfect solution! I think it is not so bad, at the moment Wikimedia does not have any tool driven analysis of the Infobox-fields, and when it will come, some bot runs may be necessary to rectify the field values. The script makes a lot of cleanup, even for the future. Kind regards, Sarangbot (talk) 16:30, 9 September 2018 (UTC)[reply]

When I encounter your (old) user link, I change it to |author={{U|Edgar181|Ed}}. I can as well change it to |author={{U|Edgar181}} (Ed) or |author={{U|Edgar181|Edgar181 (Ed)}}, if you prefer. -- sarang♥사랑 09:06, 23 February 2019 (UTC)[reply]

Hi, some of your bot edits moved files into the mentioned catgory. Example: [1]. --Arnd (talk) 13:21, 10 May 2019 (UTC)[reply]

Thanx, I know; I am trying to get help, from admins, but I am waiting for answer since that morning. Sarangbot (talk) 13:30, 10 May 2019 (UTC)[reply]

I am reverting a bunch of your edits, for you are flooding Category:Images without source without any need. Please check your edits. Jcb (talk) 21:37, 13 May 2019 (UTC)[reply]

@Jcb: thank you for your help. All started when I got the request to change a category. When it happened that I made a mistake with VFC, I asked at the Admins Noteboard for help, for a mass revert of my last ~500 edits. I waited for 12 hours but never got a reply. Finally I got another help, because the damaged files became categorized to Pages using Information template with parsing errors, so I could access them again and do some reparations. This happened at May 10.

The deprecated and now empty Category:Valid SVG created with Inkscape-COAElement was deleted upon my request at May 11.

Too late came your 76 reverts at May 13. At that time they were more or less in good shape, until your revert took them again to the now deleted category. I will correct them by hand, with that number it will be possible. -- sarang♥사랑 05:40, 14 May 2019 (UTC)[reply]

They were not in good shape, they were flooding a maintenance category. Jcb (talk) 05:46, 14 May 2019 (UTC)[reply]

Hello. I just wanted to let you know that I have granted autopatrol rights to your account; the reason for this is that I believe you are sufficiently trustworthy and experienced to have your contributions automatically marked as "reviewed". This has no effect on your editing, it is simply intended to make it easier for users that are monitoring Recent changes or Recent uploads to find unproductive edits amidst the productive ones like yours. In addition, the Flickr upload feature and an increased number of batch-uploads in UploadWizard, uploading of freely licensed MP3 files, overwriting files uploaded by others and an increased limit for page renames per minute are now available to you. Thank you. -- ~riley (talk) 00:35, 13 October 2019 (UTC)[reply]

Hello,

Google Code-In, Google-organized contest in which the Wikimedia Foundation participates, starts in a few weeks. This contest is about taking high school students into the world of opensource. I'm sending you this message because you recently edited a documentation page at Wikimedia Commons.

I would like to ask you to take part in Google Code-In as a mentor. That would mean to prepare at least one task (it can be documentation related, or something else - the other categories are Code, Design, Quality Assurance and Outreach) for the participants, and help the student to complete it. Please sign up at the contest page and send us your Google account address to google-code-in-admins@lists.wikimedia.org, so we can invite you in!

From my own experience, Google Code-In can be fun, you can make several new friends, attract new people to your wiki and make them part of your community.

If you have any questions, please let us know at google-code-in-admins@lists.wikimedia.org.

Thank you!

--User:Martin Urbanec (talk) 22:04, 23 November 2019 (UTC)[reply]

Sarangbot hello ! SarangMan hello too !
I just did an userright request for my ShufaBot and bumped into your Sarangbot request, funny :D ! What tech do you use ? I use Node / Wikiapi and it's fairly easy to code. I will calmly do some work on the SOP, ACC projects in coming years. Yug (talk) 18:49, 25 March 2021 (UTC)[reply]

Sarang, I'm coding my first bot this week and just coded one script for mass rename. Are you familiar with javascript, regex and nodejs ? Would you like to be mentored to move Sarangbot into a bot ? Yug (talk) 14:31, 26 March 2021 (UTC)[reply]

Oh - it would be great to let the work made by a bot! Thank you. But I do not want to change my 2nd account to a real bot, I need it for other mass edits, as with VFC.

My JS knowledge is too poor, I am maintaining an essential and often used script because nobody else does it, with a lot of trial & error, more or less successful (rather less ...). Regex is a fine thing, even with my poor knowledge I can do fine work with it. No, I am not at all familiar with JS, sorry. Yes, I always like to learn more.

There exists yet a script User:Perhelion/massrename.js but Perhelion left wikipedia, and it seems that nobody knows how to use that script. Reading the code I could not find out which input the script needs, i could not even find out how the script can be used that it accepts parameter input.

About your stroke order, ACClicense and other tasks: I had been trying to continue your work, but got troubles with another user. -- sarang♥사랑 15:00, 26 March 2021 (UTC)[reply]

User:Perhelion/massrename.js use the raw Javascript API.

Kanasimi's Wikiapi is an intermediary, so things are simpler to write.

Mass edit content example:

// PURPOSE: For a given a category, gets the list of pages, edits existing content.
const Wikiapi= require('wikiapi');
const logins = require('./logins-ShufaBot.js');

// Login credentials from .login*.js
var USER = logins.commons.user,
	PASS = logins.commons.pass,
	API  = logins.commons.api;

(async () => {
    // Connect
    const targetWiki = new Wikiapi;
    await targetWiki.login(USER, PASS, API);
    console.log(`Username ${USER} is connected !`);

    // List of targets
    const list = await targetWiki.categorymembers('ShufaBot test: upload');   // <--- get all the pages in [[Category:ShufaBot test: upload]]

    // Loop on targets
    for(i=0;i<list.length;i++){
        console.log(list[i]);
        var currPage = list[i], // target page's page_data
            wikititle= currPage.title;
        // Page exist ?
        let pageData = await targetWiki.page(wikititle, {});
        
        if(pageData.wikitext!=='') {

            //CORE: Edit page, replace string:
            await targetWiki.edit_page(wikititle, function(page_data) {
                return page_data.wikitext.replace(/toto/g,'')         // <------- regex match and replacement
                    + `\n[[Category:ShufaBot test: edit]]`;
            }, {bot: 1, nocreate: 1, minor: 1, summary: 'ShufaBot test: edit'});
            console.log('Done.');
        }

    }
})();

The difficult part is to install node, git, npm, but I could write a tutorial for this as well.

Change the 5 lines under //CORE: and you can get a file mover script. Yug (talk) 16:28, 26 March 2021 (UTC)[reply]

I'am preparing something… Yug (talk) 18:59, 26 March 2021 (UTC)[reply]

deleted upon my request -- sarang♥사랑 12:26, 13 April 2021 (UTC)[reply]

Category:Superfluous images Please do NOT tag images as "superfluous" unless:

• there is a better version available

and

• the better version does not have a more restrictive license

Examples of bad edits:

• https://commons.wikimedia.org/w/index.php?title=File%3ABroadcast_icon.png&type=revision&diff=632063881&oldid=492887771 no better version and not even other version at all available
• https://commons.wikimedia.org/w/index.php?title=File%3AHidden_icon.png&type=revision&diff=632095825&oldid=462139191 alternative version suggested is inferiour and has a more restrictive license

Taylor 49 (talk) 22:47, 25 February 2022 (UTC)[reply]

@Taylor 49: The criterion for that category is not that better images (or vector versions) exist; it contains images that have been drawn (mostly as very poor PNG) but are not used anywhere.

In some cases where one or the other was used it could be replaced by an SVG version.

Depending your examples, Broadcast icon.png is nowhere used, it is superfluous.

For Hidden icon.png I will draw a non-restrictive-licensed better SVG version and replace its usages, making it superfluous.

All or most images had been drawn without any need by Lycopene579 two years ago. Where he made large PNG, better SVG with a few hundred bytes seem more useful — when a need exists.

As long there is no need, I see no advantage for "production in stock"; the fact that a poor PNG exists is not enough justification for generation of a better image - that nobody will use. It is not any advantage for Wikipedia to make superfluous poor images, but making superfluous better images won't help either. -- sarang♥사랑 07:10, 26 February 2022 (UTC)[reply]

Hello

Broadcast icon.png is of good quality, thus it is NOT superfluous. I can buy your reasoning for images that are of poor quality, but this one does not belong to that class.

> for Hidden icon.png I will draw a non-restrictive-licensed better

> SVG version and replace its usages, making it superfluous

Good idea. Done: Hidden icon.svg

> see no advantage for "production in stock"

Well, "currently not used" is certainly NOT a criteria for deprecation or deletion. I frequently search for suitable images for my wiktionary work, and I appreciate to have well categorized good images "in stock". Commons:Project_scope#Not_used.

There are trillions of unused icons here on commons (example: Category:Iconoir), and neither "unused" nor PNG format are inherently evil.

I would like to have a broader discussion about a deprecation policy for unused PNG icons.

Taylor 49 (talk) 11:35, 27 February 2022 (UTC)[reply]

Hi, ​ in my opinion Broadcast icon.png:  is a very poor image; the SVG Noun Project broadcast icon 761688 cc.svg:  is now a better one, if you need an antenna Sarangbot (talk) 14:54, 27 February 2022 (UTC)[reply]

Commons:Categories for discussion/2022/02/Category:Superfluous images. Multichill (talk) 17:26, 27 February 2022 (UTC)[reply]

Thank you User:Sarang[bot] for creating high-quality low-bloat images, but still please stop moving from ordinary categories to "Category:Superfluous images". File "Broadcast_icon.png" is not "very poor" ... maybe it si just simply inferior to your version now. Taylor 49 (talk) 21:55, 27 February 2022 (UTC)[reply]

More problematic editing: Broadcast_icon.png Fluss-lbach.png and many more. It is most likely NOT useful to move from specific categories to desperately crowded Category:Icons. Taylor 49 (talk) 16:41, 26 March 2022 (UTC)[reply]

Please see the Discussion and take action Shipsview (talk) 10:38, 5 September 2022 (UTC)[reply]

@Shipsview: There is no link I can follow; impossible to find the mentioned discussion, and there is not such a category. Tell me more ! Sarangbot (talk) 11:42, 5 September 2022 (UTC)[reply]

My apologies - I got the wrong editor. This is the page: https://commons.wikimedia.org/wiki/File:Arms_of_William_Hew_Douglas,_Lord_of_Ardgour_House.svg Shipsview (talk) 09:07, 6 September 2022 (UTC)[reply]

This type of edit should probably mean "artist", not "aerist", cf. Category:Pages using Artwork template with incorrect parameter. Could you have a look? Thanks in advance, --Marsupium (talk) 13:51, 29 March 2023 (UTC)[reply]

Thank you @Marsupium: for telling, I could correct my typo -- sarang♥사랑 00:27, 30 March 2023 (UTC)[reply]

Your edits marked "other vers - Doing 1 replacements." have broken a bunch of files, like here: this, this, and this. You'll notice that this has put the content from "other versions" into permissions. I can see no reason you decided to do this and hope you will fix the mess you've made of all these files. Cakelot1 (talk) 06:51, 18 April 2023 (UTC)[reply]

File:Twemoji12 1f1f7-1f1fp.svg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you! Afrikaans ∙ العربية ∙ беларуская ∙ беларуская (тарашкевіца) ∙ български ∙ ပအိုဝ်ႏဘာႏသာႏ ∙ বাংলা ∙ bosanski ∙ català ∙ čeština ∙ dansk ∙ Deutsch ∙ Deutsch (Sie-Form) ∙ Zazaki ∙ ދިވެހިބަސް ∙ Ελληνικά ∙ English ∙ Esperanto ∙ español ∙ eesti ∙ فارسی ∙ suomi ∙ français ∙ galego ∙ עברית ∙ hrvatski ∙ magyar ∙ հայերեն ∙ Bahasa Indonesia ∙ íslenska ∙ italiano ∙ 日本語 ∙ 한국어 ∙ 조선말 ∙ македонски ∙ മലയാളം ∙ Bahasa Melayu ∙ မြန်မာဘာသာ ∙ norsk bokmål ∙ Plattdüütsch ∙ Nederlands ∙ norsk nynorsk ∙ norsk ∙ occitan ∙ polski ∙ پښتو ∙ português ∙ português do Brasil ∙ română ∙ русский ∙ sicilianu ∙ slovenčina ∙ slovenščina ∙ shqip ∙ српски / srpski ∙ svenska ∙ ไทย ∙ Türkçe ∙ українська ∙ Tiếng Việt ∙ 中文 ∙ 中文（简体） ∙ 中文（繁體） ∙ +/−

MBH 10:53, 24 May 2023 (UTC)[reply]

Sarang might have been interested in my comments at Template talk:PD-wpdc regarding the usage of that template. TheFeds 00:40, 25 October 2024 (UTC)[reply]