How have I lived to the Year of our Lord 2026 without having seen this meme before now?

#StarWars #memes #ReneMagritte

This is me, arguing with rustc about various ways of setting one bit in memory:

https://www.youtube.com/watch?v=Hz1JWzyvv8A

so this password manager paper: https://eprint.iacr.org/2026/058 starts with:

> We examine the extent to which security against a fully malicious server holds true for three leading vendors who make the Zero Knowledge Encryption claim: Bitwarden, LastPass and Dashlane

with https://sphinx.pm, we consider it - half-jokingly, with some caveats - normal, the server being fully malicious and it's fine have it hosted by the nsa/u8200/gru/prc

1/n

@alphastrata The root of the issue is that the library I'm using is not originally in/for Rust, so such best practices simply don't exist in their world...

I've seen a lot of people asking for an option for "are" in the marshdeer xkcd-2501 generator... so I made one! Yay open source.

https://foone.github.io/xkcd2501-generator/

(pull request about to be in progress, but this is my fork of my changes)

@addison Thanks, that's in line with @alphastrata's suggestion and the advice I got afk.

I'm quite new to Rust and it's strange that something as simple as moving a couple of lines of code into a function (I'm still considering a macro actually) can require this much consideration, but I guess this is the price we pay for stability.

@addison Thanks, that makes sense, but I can't touch Session as it comes from a dependency. There is definitely a lifetime issue here too (esp. because the actual tree of objects goes ~5 levels deep).

I think the root of my Q is if there is a way to create a "will" for Rust functions/scopes that would say "after my death my caller will inherit all that I own (so please don't free shit up)"?

@kstrlworks Oh sry, I'm on 25.7<whatever is the latest patch>. I simply use two bridged interfaces on Proxmox. Based on my above observations I think this is more of a design issue of moving around files during the upgrade process, and *maybe* something you can mitigate with some ZFS magic (I'm on UFS).

@addison From a different branch of this convo:

"Imagine that initialization is more complex and I want to provide a library that hides that complexity, exposing something like setup_widget() and deinit_all()."

https://infosec.place/notice/B3RIRrdtPQog3eUc2y

@edmcbane Imagine that initialization is more complex and I want to provide a library that hides that complexity, exposing something like setup_widget() and deinit_all().

You can see an E0515 here (among other things), but I intentionally refrained from providing my attempts because I suspect there is a completely different Rust pattern for similar cases:

https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=0f4a1eeba2c33741fafc059d717e87bb

It's important that I can't touch Session or Widget as they are provided by a library (with FFI).

@alphastrata Thanks! I'll probably end a up a solution like that but still wonder if this can be achieved without Box/refcounts (should've added to the question)?

ブースト、お気に入り大歓迎！yuya_maekadoさんの投稿作品です。

【yuya_maekadoさん】
https://tokyocameraclub.com/mstdn/yuya_maekado/

【投稿作品】
https://tokyocameraclub.com/mstdn/yuya_maekado/111940073051394315

【登録はこちら：東京カメラ部インスタンス】
https://mstdn.tokyocameraclub.com/

東京カメラ部インスタンスに登録いただき、ハッシュタグ「#tokyocameraclub」を付けていただいた投稿が対象となります。ぜひ、気軽にご参加ください。

※各種法令、マナー、関係者の指示に従った撮影をお願いします。
*Please ensure that your photography adheres to all relevant laws, etiquette, and instructions issued by authorized persons.

Today in This Should Be Easy But in #Rust It Apparently Isn't: how do I encapsulate the widget initialization (without triggering E0515) in this example, so it becomes reusable?

https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=f31dd1ecf5530b11e301bb19af85b0fa

[RSS] Cryptographic Issues in Matrix's Rust Library Vodozemac

https://soatok.blog/2026/02/17/cryptographic-issues-in-matrixs-rust-library-vodozemac/

[RSS] Building a Secure Electron Auto-Updater

https://blog.doyensec.com/2026/02/16/electron-safe-updater.html

@kstrlworks It looks like a transient error, most likely a corrupt download. Shit happens ofc, but he only acceptable reason for bricking the system would be hardware error which is very unlikely because other VMs on the same host run just fine.

🎥 PTML: emitting rich decompiled code

Jack introduces PTML and how rev.ng goes beyond raw text, enriching decompiled code (e.g., decompiled C, disassembly, etc.) with HTML-like markup to provide richer and useful information for the viewer.

https://www.youtube.com/watch?v=_Xtwu_EaRJg

@kstrlworks Clean install from ISO (latest minor) -> firmware update from webUI to latest patch. The updater removed basic files, then failed to extract the updated ones so everything just stopped working.

Happy Presidents Day.

Two weeks ago, the CIA shut down the World Factbook - a public
domain reference on every country, used by 6 million people
monthly since 1997.

We built a replacement:
https://openfactbook.org

261 countries · Instant search · Country comparisons

Public data should stay public.

#OpenData #CivicTech #OpenSource #PresidentsDay
#PublicDomain #DataRescue

#wh40k #windows