iiinova — where your digital self keeps evolving

Mistakenly entered Open League for #umamusume #libracup and thought I had really messed up. Made a team of B-ranks as fast as possible. My Taishin is a bit OP....

Picture of umamusume race results wherein My Narita Taishin came in 1st at distance.

010

Margot Kraus @markekraus.com · 25/11/2025

Woot! Got 1st place in Virgo Cup Group B! Taiki Shuttle got 1st, Vodka got 2nd, and Nice Nature got 8th. #umamusume

screent cap of Virgo Cup victory

Champions Meeting
Virgo Cup
GRADED LEAGUE
GRIUP B
1st
/ 4,025

screencap of Virgo Cup twinkly monthly
Twinke Monethly Extra
An Unprecedented Event
Taiki Shuttle
Achieves the Incredible!
Taiki shuttle delivers Margot victory at the Virgo Cup finals! Fast, powerful, and with fortune on her side--there wasn't a single gap in her armor to exploit. it has been an honor to witness her running.
A+
Rank
Ipeccable | Taiki Sguttle | Details
Margot
Oh.. we're gonna throw us a big ole shindig!
Everyone's welcom--so feel free to bring a friend!

000

Margot Kraus @markekraus.com · 08/11/2025

The first champions meeting I didn't try to make good aces for ended up being the only CM I got 1st place in so far. The Tokai Teio from my first Teio career won the day. LOL #umamusume #leocup

Screenshot of Umamusume Champions results screen. Text:
Champions Meeting
Leo Cup
GRADED LEAGUE
GROUP B
1st
/ 1,683

010

Margot Kraus @markekraus.com · 13/04/2025

It is a consistent pattern of bad behavior. I have even called him out on it just to be blocked by him. Some examples:

360

Margot Kraus @markekraus.com · 13/01/2025

Let me just leave this bit of chaos riiiight here...

$${Get-ChildItem -Recurse c:\ | Remove-Item -Force} = "winning!"$

030

Margot Kraus @markekraus.com · 09/01/2025

I'll just leave this bit of chaos riiiiight here.

$demo code using a utf-8 hyphen alternative to create a misleading -not operator in PowerShell. PS C:\Users\MarkLocal> function −not {$true} PS C:\Users\MarkLocal> −not $true True$

210

Margot Kraus @markekraus.com · 15/12/2024

The aka.ms link redirects to a download.microsoft.com url as well.

010

Margot Kraus @markekraus.com · 15/12/2024

in fact.. all the ps*1 files are signed there.. It doesn't rule out it being an exploit.. but given this is the same link provided int he doc for this tool, and it's signed by MSFT, I think the probability is really low.

$The picture shows the code signing for TSS PowerShell files. Get-ChildItem *.ps*1 | %{ [PSCustomObject]@{"File"= $_.name; "Cert"=(Get-AuthenticodeSignature -FilePath $_.FullName).SignerCertificate.Issuer}} File Cert ---- ---- TSS_ADS.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_Containers.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_CRM.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_DEV.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_DND.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_INT.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_LKG.ps1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_MCM.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_NET.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_PRF.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_SEC.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_SHA.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_SPS.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS_UEX.psm1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, C=US TSS.ps1 CN=Microsoft Code Signing PCA 2011, O=Microsoft Corporation, L=Redmond, S=Washington, ...$

210

Margot Kraus @markekraus.com · 13/12/2024

I'll just leave this less intuitive version here as my contribution to the conversation...

$Shows PowerShell command line code to get the Friday 13ths of a given year using the the first day of the week of the previous 12 years to detect for years starting on Sundays and using that iterator as the month in the current year that contains a Friday 13th. PS C:\temp> $y=2025; 1..12 | where {!(date $y-$_).DayOfWeek} | Foreach {date "$y/$_/13"} Friday, June 13, 2025 12:00:00 AM PS C:\temp> $y=2026; 1..12 | where {!(date $y-$_).DayOfWeek} | Foreach {date "$y/$_/13"} Friday, February 13, 2026 12:00:00 AM Friday, March 13, 2026 12:00:00 AM Friday, November 13, 2026 12:00:00 AM$

121

Margot Kraus @markekraus.com · 09/12/2024

What Alex Jones's lawyer sounds like in his opening in today's hearing on the sale of FSS to Global Tetrahedron

Charlie from Always Sunny in Philidelphia in front of a corkboard with red string

000

Margot Kraus @markekraus.com · 07/12/2024

Yeah, it's okay when you use the command line interactively, but it starts to hurt if you do it in a loop or something. at n=10,000, the difference between get-date and date is measured in MINUTES

$Image demonstrates the extreme difference in execution times between get-date and date at n = 10,000. PS C:\Users\MarkLocal> $n = 10000 PS C:\Users\MarkLocal> (Measure-Command{1..$n | %{$null = date}}).TotalMilliseconds 270625.4923 PS C:\Users\MarkLocal> (Measure-Command{1..$n | %{$null = get-date}}).TotalMilliseconds 323.3579 PS C:\Users\MarkLocal> [timespan]::FromMilliseconds(270625.4923) - [timespan]::FromMilliseconds(323.3579) Days : 0 Hours : 0 Minutes : 4 Seconds : 30 Milliseconds : 302 Ticks : 2703021345 TotalDays : 0.00312849692708333 TotalHours : 0.07508392625 TotalMinutes : 4.505035575 TotalSeconds : 270.3021345 TotalMilliseconds : 270302.1345$

140

Margot Kraus @markekraus.com · 02/12/2024

Couple that with the DontShow Parameter Attribute Setting. The param will no longer be available via tab completion.

Example using the DontShow parameter attribute setting.
param (
[Parameter(DontShow)]
[System.Obsolete("The NoTypeInformation parameter is obsolete.")]
$NoTypeInformation
)

030