Right! Been a while since I did a #fedidreams. So: last night, I dreamed that my work created a new security policy. All employees must use bloodlock on any device that contains work related data. What's bloodlock? Glad you asked! Obviously, it's a feature that requires you to prick your finger and deposit a drop of blood on the sensor every time you want to unlock your device. In the meeting this was announced, we were told that we would be supplied 60 needles and bandages a month for this purpose, and if we needed more, we'd have to pay for them ourselves. Also, the "auto-lock" policy would be reduced from 60 seconds to 15 seconds. Lastly, Microsoft, Apple, and Google would all use our DNA (as collected from our blood) for AI training purposes. So I did this on my work device. However, I got a meeting scheduled with our HR team. They told me that "Your first and last name are work related data. Any device that contains your first and last name must comply with the bloodlock policy." So then I had to put it on all my personal devices, too. The dream ended with me trying to log into my work device for a critical meeting, but it wasn't working! I had pricked my finger so many times to unlock my devices that no blood would come out! I woke up to find my left hand had fallen asleep. Obviously that was the trigger for...all of this nonsense. LOL

Happy Petrov Day to those who celebrate. On September 26, 1983, Stanislav Petrov made the correct decision to not trust a computer.

The early warning system at command center Serpukhov-15, loudly alerting of a nuclear attack from the United States, was of course modern and up-to-date. Stanislav Petrov was in charge, working his second shift in place of a colleague who was ill.

Many officers facing the same situation would have called their superiors to alert them of the need for a counter-attack. Especially as fellow officers were shouting at him to retaliate quickly before it was too late. Petrov did not succumb.

I've attached a short clip from a reenactment of the situation in the documentary The Man Who Saved the World.

The computer was indeed wrong about the imminent attack and Petrov likely saved the world from nuclear disaster in those impossibly stressful minutes, by daring to wait for ground confirmation. For context one must also be aware that this was at a time when US-Soviet relations were extremely tense.

I've previously written about three lessons to take away from Petrov's actions:

1. Embrace multiple perspectives

The fact that it was not Stanislov Petrov's own choice to pursue an army career speaks to me of how important it is to welcome a broad range of experiences and perspectives. Petrov received an education as an engineer rather than a military man. He knew the unpredictability of machine behavior.

2. Look for multiple confirmation points

Stanislav Petrov understood what he was looking for. While he has admitted he could not be 100% sure the attack wasn't real, there were several factors he has mentioned that played into his decision:

- He had been told a US attack would be all-out. An attack with only 5 missiles did not make sense to him.
- Ground radar failed to pick up supporting evidence of an attack, even after minutes of waiting.
- The message passed too quickly through the 30 layers of verification he himself had devised.

On top of this: The launch detection system was new (and hence he did not fully trust it).

3. Reward exposure of faulty systems

If we keep praising our tools for their excellence and efficiency it's hard to later accept their defects. When shortcomings are found, this needs to be communicated just as clearly and widely as successes. Maintaining an illusion of perfect, neutral and flawless systems will keep people from questioning the systems when the systems need to be questioned.

We need to stop punishing when failure helps us understand something that can be improved.

reshared this

I've finally managed to cut Chrome out of my life on PC, and I've switched to WaterFox exclusively. Next on the docket is to try Libre Wolf and determine which is better, though I doubt there will be too much of a difference, considering the fact that they're both Firefox forks. After I have my PC Browser of choice, it's time to switch on Android. Has anyone else tried WaterFox or Libre Wolf on Android yet?

For any Canadians who want to pressure the government to force Canada Post to the table, NOT to force postal workers back to work, you can follow these steps!

If you wish to send something to Patty Hajdu directly:

If you are in Thunder Bay-Superior North, she's your MP! Write patty.hajdu@parl.gc.ca

If not, you can try writing the Ministry of Jobs and Families directly at edsc.min.ef-jf.min.esdc@hrsdc-rhdcc.gc.ca

You can call (819) 654-5546 as well.

This is what I wrote in my email (and I said something similar on the phone).

The pastebin is to provide alt text (since it breaks the 3000 alt-text limit) - you CAN use it as a template, but I encourage you to write it in your own words, especially if she's your MP!

pastebin.com/ndiBuWMd

#CanadaPost #CanPol #CanadianPolitics #CdnPoli #CUPW

#AndroidAppRain at apt.izzysoft.de/fdroid/?radd=1… today brings you 18 updated and 1 added apps:

* PrivacyScanner: scans installed applications for potentially risky permissions, and helps you review their privacy-related details 🛡️

RB status: 718 apps (54.7%)

4 #Magisk modules have been updated at apt.izzysoft.de/magisk

Enjoy your #free #Android #apps with the #IzzyOnDroid repo :awesome:

in reply to mdv

@mdvhimself Magisk modules have their own "experimental" repo here, yupp. I say "experimental" not because it's flaky or something, but because it doesn't get "scrutinized" the same way as our app repo does – so no additional screening, no reproducible builds, etc. It's more for your convenience, to make it easier to find FOSS modules.

Folks who rooted their devices should know about the risks, and will take special care I hope 😉

@mdv

Jsem zvědavej, jak #Plzeň nastaví intervaly těch semaforů u Makra.

Představa, že když si vezmu #kolo, tak budu čekat na každý větvi minutku-dvě, tak to bude zatracený zpomalení na "turbokřižovatku" :)

Schématický plán křižovatky v Plzni u Makra
plzen.eu/o-meste/aktuality/akt…

fsync(2) is an example of a poor interface resulting from the design decisions that went into Unix, and thus POSIX.

Why do I say this? Glad you asked. `fsync(fd);` will block its caller until dirty in-memory data associated with the file referred to by the given file descriptor (both file data and metadata) are written to "a permanent storage device", or an error occurs. And that's all well and good, but often, you want to sync multiple files: with `fsync`, you have to either serialize this, or farm multiple `fsync` calls out to separate (OS-managed) threads.

Consider that these days, data is _usually_ written to a storage device asynchronously: a block write request means filling in some data structure understood by the storage device (or its controller) and sending that to the device. The device will fetch the data from the host via DMA, write it, and set a status bit or generate an interrupt or something when it's done.

Typical devices these days can support multiple (indeed, many) outstanding IO requests, internally handle scatter gather IO, etc; so in theory, multiple fsync's could be proceeding in parallel. But the highly synchronous nature of the POSIX interface prevents us from doing this effectively, and AIO support is often buggy and incomplete.

If we had a system interface that let you initiate synchronization, but didn't block and instead immediately returned a completion token of some kind, coupled with another interface that could take a list of such tokens and block until they all completed, you could kick off all of the sync requests at once, and then barrier on their completion.

That'd be a lot simpler.

Canada's Communication Security Establishment's (CSE) Centre for Cyber Security joined its international counterparts urging organizations to take immediate action to patch up vulnerabilities following a widespread hit on the technology security company #Cisco... cbc.ca/news/politics/cisco-cyb… #cdnpoli #polcan #technology #CSE #FAIL

Oh right ... now I remember why I never set up @thunderbird to work with my email - Microsoft does everything in its own proprietary way. So I can get email up and running but only if I'm happy without my contacts or calendar.

You know maybe it's time for a change ... I just have to figure out if I can do forwarding away from Outlook without continuing to pay for it.

in reply to mausmalone

We have info about the latest Exchange updates coming in next month's Thunderbird 144. While initial support will only include email, adding address books and calendar are very much on our roadmaps. You can ready about it in our latest development digest! blog.thunderbird.net/2025/09/t…

I ordered an Adafruit Fruit Jam RP2350-based single-board computer (adafruit.com/products/6200) last weekend, and it arrived yesterday. Unlike most microcontroller boards, this one includes HDMI, USB, and analog audio output, so it can be used as a stand-alone personal computer. At least, a retro-style personal computer; the processor has no MMU after all.

The CAQ - zero courage. montreal.citynews.ca/2025/09/2…

#noplanetb #gasguzzlers #CAQASTROPHE #polQC #QCpoli #despicable

Montreal cyclist in critical condition, collision on Décarie Blvd.

montreal.citynews.ca/2025/09/2…

> vehicle was circulating north on Décarie,” said Dubuc. “When he got to Paré, he hit a cyclist.

No CityNews. The car does not have he/him pronouns. Nor was the car self-driving.

Your editing to erase the driver from the facts is showing.

in reply to tessarakt

Done: github.com/thunderbird/thunder…

#фалыстыннаш

просто поразительно. английские нейтив спикеры не уловили НИ ОДНОГО важного заявления биби. ни. сука. одного. видимо, ивритский акцент им помешал, а мне помог.

именно ТАК работают сейчас геббельс-медиа. ты можешь кричать с трибуны оон но тебя ни кто не услышит просто потому что смотреть онлайн видео сложно - надо ссылку найти и время потратить.

это сука лютый пиздец. если честно мне немного не по себе…

bbc.com/news/live/cdxqe17njggt…

Я поняла. Раз переселить всех в счастливое будущее не удаётся, нас возвращают в счастливое детство.
Так, в детстве нельзя было говорить слово "жопа". А если очень хотелось, надлежало зайти в комнату, проверить, что рядом никого нет, быстро и полушёпотом крикнуть и тут же выбежать, пока ничего не случилось.
Сейчас то же самое, только слова другие.

Já prostě nemám slušných slov.

zpravy.aktualne.cz/domaci/gast…

in reply to Tritol

@tritol128 @OttovonWenkoff @piratzbrna O tom nepochybuju. Ale je dulezite pochopit ten problem a pochopit, jak velka dira tam ted je. To proste v zadnym scenari nejde jen tak preskocit a zacit platit 45% statu. Minimalne ne plosne.

Ze vsech reseni jak tu propast preklenout je "docasne" posunout (2) smerem k (1) celkem dobre. Pak se muze ten benefit ruzne zastropovat a postupne zmizi (priklad tohohle postupu je ruseni stravenek v Britanii).