Photo


I found out that my gloves had some dark stains on them, so I decided to refresh them a bit :D It was fun! Used alcohol-based marker for drawing.
10K notes
·
View notes
Text




ARTHUR TOROS 'Tears Of An Angel' Mask if you want to support this blog consider donating to: ko-fi.com/fashionrunways
2K notes
·
View notes
Text
marie claire korea
822 notes
·
View notes
Text









KATERINA SHUKSHINA Accessories if you want to support this blog consider donating to: ko-fi.com/fashionrunways
427 notes
·
View notes
Text

Edwardian 15ct Gold Pair of Butterflies brooch set with a Ruby, Sapphire & Natural Split Pearls
c. 1910
406 notes
·
View notes
Text










Star eyes makeup inspo
19K notes
·
View notes
Photo

CHANEL Couture Spring/Summer 1997 if you want to support this blog consider donating to: ko-fi.com/fashionrunways
289 notes
·
View notes
Text


Chinese windmill (Byasa alcinous), male and female
18 notes
·
View notes
Text
qntm on time
In order to set a clock to display the correct time, you need to know what time zone it's in. With discrete time zones this is a matter of referring to local law and custom. With continuous time zones, you need to know the precise longitude of the clock.
In fact, you need to know the precise longitude of two clocks; the one you are setting, and the one against which you are setting it. In extreme cases, that other "clock" may be a fountain of captured, vibrating caesium atoms, but the basic principle is the same. You then need to convert the longitude difference to a time offset and set your clock's time to be the reference clock's time plus the offset.
I love leap seconds. I love the unsolvable problem which birthed leap seconds, I love the technical challenge of implementing leap seconds, I love that they are weird and delightful and that they solve a problem, and I love that this solution is hugely irritating to a huge number of people who have more investment in and knowledge of time measurement than I do. It is a huge hassle to deal with leap seconds and I love that there is no universal agreement on how to deal with them. What should Unix time, for example, do during a leap second? Unix time is a simple number. There's no way to express 23:59:60. Should it stall for a second? Should it overrun for a second and then instantaneously backtrack and repeat time? Should it just blank out and return NaN? These days it seems like a popular choice is the Google-style 24-hour linear smear from noon to noon UTC. That is: a full day of slightly longer-than-normal "seconds". Should a clock do that? Is a clock allowed to do that? I love that. I think it's highly amusing.
Transforming the old calendar into the new calendar is a two-phase process. In the first phase, we broaden the capabilities of the existing Gregorian calendar by explicitly extending the days of every month, the months of every year and the years of both the Common Era and... erm, the Before Common Era... forward and backward indefinitely.
Examples:
• "2020-12-32" is legal, and refers to the same day as "2021-01-01".
• "2020-12-99", "2021-01-68", "2021-02-37" and "2021-03-09" all refer to the same day.
• "2021-01-00" is legal, and refers to the same day as "2020-12-31".
• 2000-00-00 is 1999-11-30, 2020-11-30 is 2021-00-00, 29 November is New Year's Eve and 30 November is now New Year's Day.
0 notes