Event JSON
{
"id": "3a172650314fd63f79f4e1fe70f50a82f188a7578830f97e3b3ceb217ca313b7",
"pubkey": "cba5347761ed3c5a4d3c59976156bb3bdda1584a1050818f466913e8a6b5af95",
"created_at": 1709733061,
"kind": 1,
"tags": [
[
"p",
"50b353e989ff9259d94c8766fe3fdf1b7cb4ce3e49db206464fbf825c3163fd7",
"wss://relay.mostr.pub"
],
[
"p",
"ce346cd9d2ae2ff7c8f0083a8448b6aae8599ab3bcd6e9d10ffbc966ebe88823",
"wss://relay.mostr.pub"
],
[
"e",
"160c77e59e4b45bdd2580cccc7defebd7d8f48716877c6c63487e8b99dde9905",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mstdn.games/users/chris/statuses/112049065946965208",
"activitypub"
]
],
"content": "nostr:npub12ze486vfl7f9nk2vsan0u07lrd7tfn37f8djqeryl0uztsck8ltsyyhunm Uh, you'd think a $3 trillion technology company would be able to handle a recurring issue like a leap year 🤔 You could look into the Windows10 time and date settings, maybe Teams is still pulling a wrong system date? I had similiar issues with a wrong daylight saving time in the past (on Windows, not Teams) and had to disable all the automatic \"get time \u0026 date from the internet\" settings.",
"sig": "cb27465d69c4d7836c6b0d1c4b64423efa05852f61264338fa5d2791ecf02761e959e54bad108f774634d15aa3bf3c3db8611f5224460957b620115deaf7371d"
}