I’ve been wondering over the years when being at #Airport check-ins how come these #PowerShell scripts can possibly ever work.

I know this because I’ve seen numerous times over the years crashed check-in machines. Latest one was late Spring when I visited #Ethprague at #Prague Airport.

I miss the “OS/2” and “Guru Meditation” times of my late 90s and early 00’s in vending machines etc. ;-)

Your local airport is actually airport.bat!

#CrowdStrike

Wrote a pretty good Windows emulator in {fmt}:

#include <fmt/color.h>

int main() {
fmt::print(bg(fmt::color::blue),
"{:1600}", "Your PC ran into a problem and needs to restart.");
}

#crowdstrike

Things that Mastodon spam accounts following me have put in their profiles today:

• "Passionate crypto trader, let's vibe"
• "Full Stack Digital Marketer Consultant"

What a world.

@jwz I'm considering adding "let's vibe" to my own resume after reading this ;-) Hilarious, love it. Totally late 90s kitsch.

`mmap` struggles with #Rust: https://github.com/enarx/enarx/issues/2580

#enarx #rustlang

https://www.digitaltrends.com/computing/southwest-cloudstrike-windows-3-1/

https://imgs.xkcd.com/comics/crowdstrike.png

So if anyone who as any responsibility causing the bug reads this: don't feel too bad of yourself, not throwing the first rock! This scenario should have been projected beforehand.

I'm assuming they have a staging environment already for new patches, and not referring to that.

In addition it would probably save some money to have some well-crafted rollback for patches that have went from staging to live outside the CrowdStrike's internal environments.

I mean it is exactly kind of bug where a single hour loss in rollback probably costs some unimaginable sum of money, so thus I think it'd be a business-smart "local maximum" to optimize ;-)

In #CrowdStrike outage biggest surprise is not the bug but instead how unprepared they were for rollback.

Lessons learned IMHO from the whole thing is that companies running these platforms should have a test suite, and exercised rollback process for faulty patches.

I.e. I'd focus to the only thing that can be fixed permanently, i.e. the rollback process at scale. Faulty patches come and go.

#infosec

@pinkforest In the scope of features address book called khard and calendar tool called khal are pretty good reference models in this area. I think the interface could be just smoother.

@pinkforest Like for instance, use something like https://github.com/kawasin73/prsqlite and create sqlite db and Rust traits for importing and exporting different contact formats including vCards and abook, could be one robust and ubiquitous approach.

@pinkforest Well I used mutt 1999-22, and email workflow is the most critical thing in my life almost ;-) But I can still try it out and comment if I have anything to say.

What made me try out aerc in the first place was this blog post: http://www.kroah.com/log/blog/2019/08/14/patch-workflow-with-mutt-2019/, i.e. if aerc made any sense to Greg K-H, it might make sense to me, as Greg is a long-time mutt user :-)

IMHO, one place where there is a lot of room for improvement, and I don’t really have a fixed choice per se, is command-line / TUI address book with vCard support, which would integrate smoothly with these popular clients:

1. Aerc
2. Alpine
3. Mutt

ATM, I’m using https://github.com/lucc/khard but I do not love it particularly.

Courtesy of https://blog.sergeantbiggs.net/posts/aerc-a-well-crafted-tui-for-email/

#Microsoft #Crowdstrike #egg 🤣

https://bsky.app/profile/liaofthebay.bsky.social/post/3kxmu7gmxxc2h

@janantos BTW, only auto-complete I tend to use is CTRL-x-CTRL-f which auto-completes path in a vim buffer ;-) For symbol lookup in Rust I use rusty-tags.

rusty-tags also lookup through the sources of the external crates, stdlib etc., given that I have this in .zprofile:

# rusty-tags
[ `command -v rustc` ] && RUST_SRC_PATH=$(rustc --print sysroot)/lib/rustlib/src/rust/library/
[ -d $RUST_SRC_PATH ] && export RUST_SRC_PATH

And in my .vimrc I have:

# rusty-tags
autocmd BufRead *.rs :setlocal tags=./rusty-tags.vi;/,$RUST_SRC_PATH/rusty-tags.vi
autocmd BufWritePost *.rs :silent! exec "!rusty-tags vi --quiet --start-dir=" . expand('%:p:h') . "&" | redraw!

I think it like that if I downshift the phase of code I write then I think it through better, and in the end I tend to save time, and have more in-depth understanding of the system I’m working with. With ctags integration I still get quickly to the API references given that they are inline the source code.

My philosophy is that it is better to use software that does not require any plugins in order to work it for you. E.g. I’d rather install VSCode than try to make vim/neovim work like VSCode. This is why I have Sublime Text license for meetings, doing graphs with Mermaid and stuff like that.

@pinkforest @johnnydecimal @danderson Because we live in open source supermarket ATM ;-)

Back in the day when software was not working, you read the manual, and learned all the details, and finally mastered software.

These days something not working as expected:

1. Install a plugin
2. Switch the software and join the rival camp.

Quite often plugins just dumb down the feature that was pre-existent already in the original software, if the manual was read ;-)

#Playtime 2 aka #Ableton session alike extension for #REAPER: https://www.helgoboss.org/projects/playtime

Nice trick in Aerc that I just learned to share IMAP account for personal and kernel.org account:

~ main
❯ cat .config/aerc/folder-maps/kernel.map 
personal = INBOX
INBOX = kernel

~ main
❯ grep folder\-map .config/aerc/accounts.conf
folder-map		= ~/.config/aerc/folder-maps/kernel.map

Should be self-explanatory ;-)

#linux #kernel #aerc #imap #email

@janantos Still I think hx is the best I've tried from modern editors. E.g. Zed I could use only meeting notes because it does not work in terminal, making it totally useless for my workflow.