Open main menu

Wikimedia Commons β

User talk:De728631

TUSC token 211033b1711e51385fa1da3b5f03b199Edit

I am now proud owner of a TUSC account!

Thank youEdit

CristianChirita (talk) for your kind support

TalkbackEdit

Please help reviewed the pictureEdit

Hi, Please help reviewed the picture. Appreciate your help.

File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium.png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (2).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (3).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (4).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (5).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (6).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (7).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (8).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (9).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (10).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (11).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (12).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (13).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (14).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (15).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (16).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (17).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (18).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (19).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (20).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (21).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (22).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (23).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (24).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (26).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (27).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (28).png
File:G-Dragon 2017 World Tour Concert Act III, M.O.T.T.E in Seoul World Cup Stadium (29).png

Thank you very much.--Amber19950120 (talk) 01:53, 16 June 2017 (UTC)

  Done De728631 (talk) 10:24, 16 June 2017 (UTC)

LTA UDEL requestEdit

I removed another request from that same LTA that tricked me earlier: [1]. I also set a 1-month soft block of 79.17.0.0/17. I doubt we have anyone else on that Rome range editing via IP. I've never seen it in recent changes, so it should be safe. If the IP sock requests keep up from another range, I'll remove this soft block. We'll see. I think I've now wheel-warred with myself!   Daphne Lantier 04:58, 18 July 2017 (UTC)

Good job, thanks a lot :) De728631 (talk) 19:33, 18 July 2017 (UTC)
@Daphne Lantier: I have just semi-protected the undeletion request because of this. Do you think another range block could help? De728631 (talk) 18:50, 20 July 2017 (UTC)
The protection is probably the most effective thing we could do, but he can still get around that by making requests at the talk pages of different admins. I've tried a short soft block of 82.50.0.0/16, but if he has a decent ISP he probably has access to at least 6 different /16 ranges. Daphne Lantier 19:26, 20 July 2017 (UTC)
Meh, that's why I'm not a fan of rangeblocks anyway. But let's wait and see how this turns out. De728631 (talk) 19:27, 20 July 2017 (UTC)

World Cup color blindness fixEdit

Color confusion for File:2015 ICC World Cup Participating Nations.png
Normal vision #FFCC00 #00CC00 dE 34.6
Deuteranopia (1-7%) #DDDD00 #B1B12A dE 11.9
 (Originally) #8F8F00 #9A9A51 dE 8.3
Protanopia (1-2%) #D3D312 #C2C200 dE 4.3

According to my simulator the new colors are better for Deuteranopia (1%)/Deuteranomaly (6%) (Green weak), it's worse for Protanopia (1%) (red weak). I can't tell that UK and America are different colors in the protanopia simulation. And the labels still need updating :-/ —Dispenser (talk) 19:14, 18 July 2017 (UTC)

@Dispenser: You're right, #FFCC00 seems to be the problem here. I've now changed all the colours with a palette from ColorBrewer and uploaded a map version that I tested with Coblis. Except for monocromacy/achromatopsia, this combination is looking quite good to me. What do you think? De728631 (talk) 20:07, 18 July 2017 (UTC)
Trying to figure out what to recommend is something I'm working on. Monocromacy (<0.01% pop?) isn't an issue—until it's printed or viewed on a e-ink Kindle. Worse there so many bad implementations for grayscale conversion and image scaling—even our own image scaler knocks dE down from 4.0 to 3.7!
I did several test prints with an HP LaserJet 1012, to find it can only really produce 6 black levels. If it was an SVG, Media Queries could change colors to patterns on grayscale output, but apparently that isn't well supported.
Anyway, thanks for the effort. It'll be another point to add when I resubmit my colorblind IEG grant. —Dispenser (talk) 00:09, 19 July 2017 (UTC)

Deletion revision requestEdit

Please help delete File:Dadao_Station_Nameborad.jpg at 19 January 2017 9:20 revision.

Image file EXIF information contains personal information (location) is the reason, thanks for your help! --SmileYuki (talk) 08:56, 20 July 2017 (UTC)

GPS data in the EXIF are nothing unusual and I don't see how this is any personal information. The coordinates of the Da Dao station are not a secret either. De728631 (talk) 18:34, 20 July 2017 (UTC)
This is the wrong GPS information, not at Dadao Station, the phone is not properly positioned.--SmileYuki (talk) 18:50, 20 July 2017 (UTC)
The locations on this interactive map and at OpenStreetMapt look alright within a reasonable accuracy. Please remember that the locations marked in such maps like the position of Dadao station may also be inacurate, and they only represent a single point while the platform where you were standing is an extended feature and may well be a hundred meters away from the "official" marker for the station. Google Maps, however, does seems to have a problem with displaying a problem. I really don't think this is the fault of the GPS location saved in the EXIF but rather a website-specific problem by Google Maps. De728631 (talk) 19:09, 20 July 2017 (UTC)
No, I am talking about the first revision at 09:20 on January 19, 2017. This is the current version is correct coordinates.--SmileYuki (talk) 02:25, 21 July 2017 (UTC)
Oh, I see. I have now hidden the first upload revision. I think we cannot really delete it because the upload history needs to remain intact for images that are potentially harmful. Anyhow, the common visitor will no longer see the first version with its faulty GPS data. De728631 (talk) 13:32, 22 July 2017 (UTC)

Please help reviewed the pictureEdit

Hi, Please help reviewed the picture. Appreciate your help.

File:Blackpink showcases(1).jpg

Thank you very much. Amber19950120 (talk) 01:02, 21 July 2017 (UTC)

  Done De728631 (talk) 13:40, 22 July 2017 (UTC)
Return to the user page of "De728631".