Dooskington[Antorum Online Dev Log #52]
Summer Progress And Fall Foundations ☀️
https://ratwizard.dev/dev-log/antorum/52
Orhun Parmaksız 👾Completed the @ratatui_rs workshop at Rust Forge! 🐀🎉
Thanks to everyone who joined 🤝🦀
Guy StreeterI've completed a few more examples from Getting Started with GTK in #rust.
I think I might be getting the hang of it.
https://gitlab.com/guystreeter/rapp1
https://gitlab.com/guystreeter/rapp1n
https://gitlab.com/guystreeter/rapp2
https://gitlab.com/guystreeter/rapp3
Second: Pinning helpers!
When doing async #Rust, there will be a point, where you'll get the ominous "Doesn't implement Unpin" error and "You need to pin your value".
First, learn about Pinning:
https://doc.rust-lang.org/std/pin/
Like, _really_ learn and understand it:
https://fasterthanli.me/articles/pin-and-suffering
And then use smol's pin! macro and the `pin_project` crate:
https://docs.rs/pin-project/latest/pin_project/
I might continue this thread with more insights I gain during this little project - stay tuned! 🙂
4/4?
Async #Rust is actually awesome! 
The last few days I've built a prototype(!) of a global "Hotkey" system e.g.:
Press & Hold `LCtrl + Space`
=> an async stream starts and only finishes if:
- another key is pressed or
- one of the Hotkeys is released
If it is not clear by now: this is a state-machine, which fits _perfectly_ into Rust's #async model!
And the best part: This is actually _the first time_ I've ever touched async #RustLang! Such a pleasant experience!
1/?
Ygor
Playground:
https://zig.fly.dev/p/lX48yJsU_Ga
This is from the (excellent!) article "The unexpected productivity boost of Rust" - by Bernard Kolobara
https://lubeno.dev/blog/rusts-productivity-curve
2/2
Kalvin 
PS (@ps) recently shared another technical project: a BitTorrent tracker/aggregator written in Rust.
👉 https://wizard.casa/objects/0198ec20-ad61-fb0a-2404-4eeeed7d56e4
From a purely technical view, the project looks interesting. But let’s not ignore the bigger picture:
⚠️ Wellbeing risks → when someone avoids accountability in community roles (like being an admin) yet runs infrastructure that distributes content, there is a danger. If they won’t take responsibility for harm in social spaces, why would they handle reports or abuse responsibly in technical ones?
⚠️ Trust risks → a tracker/aggregator operator needs trust. If admins are untrustworthy and dismissive of accountability, can we really trust their systems? Ignoring accountability in one space carries over into others.
🚨 Technical skill does not excuse ethical failure. Building networks without accountability is dangerous. Wizard.casa remains under observation for wellbeing and security concerns. Accountability is not optional.
#Accountability #Transparency #WizardCasa #Fediverse #OnlineSafety #UserTrust #DigitalEthics #Moderation #BitTorrent #RustLang #CommunityTrust #CyberSafety #SecurityMatters #NoToAbuse #DigitalRights
RustConfImagine this: you’re at #rustconf25, and suddenly the Rust ecosystem is under attack. What do you do? 🔥
On Sept 4, Christopher “CRob” Robinson hosts “Rusty and the Crate Escape”—an interactive tabletop adventure where you and fellow #Rustaceans must navigate a mock cybersecurity disaster.
It’s a playful mix of chaos, collaboration, and lessons on open source risk.
Learn more: https://rustconf.com/schedule/#1769
Anisseprogressrm does not monitor but cheats by using the process start time to estimate how much time is remaining. It only works if the rm commands has many arguments, and it uses the open directories fds to guess at which argument we are.
The output looks like this:
$ progressrm
[1452864] rm in /home/anisse/backups
29.0% (402 / 1384 args) 4.4 args/h remaining 9 days 8:12:16
as it was inspired by progress. For now anyone wanting to do monitoring should wrap it with watch.