<infinisil>
Hahaha, quote from that page ^^ " Never, ever expect hackers to be able to read closed proprietary document formats like Microsoft Word or Excel. Most hackers react to these about as well as you would to having a pile of steaming pig manure dumped on your doorstep."
<infinisil>
If only we could force everybody to read this document before they can ask any question online :P
<gchristensen>
I used to really like that page. I remember hearing there was a better version of it, but I don't remember where
<gchristensen>
it was definitely super important for me, a new person on the internet
<infinisil>
Why "used to"?
<gchristensen>
I guess the part I stopped liking is how people would beat newbies over the head with it, not the actual document. not saying any one in the Nix community has done that, of course
<infinisil>
Well I'm close to it lol, but yeah, it would be a bit rude to link this all the time anybody is asking a stupid question
pie_ has quit [Ping timeout: 272 seconds]
<samueldr>
infinisil: why can't you answer me?
* samueldr
wonders if it'll woosh
<infinisil>
An initial woosh has been felt
<infinisil>
Yeah I don't get it lol
<samueldr>
that was a terrible question, that's it
<samueldr>
I don't think it was good and if I could I would delete that :)
<infinisil>
I'll just pretend I got what you meant
<infinisil>
samueldr: I muted iqubic btw, and looking at the logs at what he's saying I'm glad, again
<infinisil>
I really feel like that user could have some general learning problem
<infinisil>
They seemingly haven't learned anything in all this time they've been here
<infinisil>
Sorry for the chit-chatter, I'll stop now
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
sir_guy_carleton has joined #nixos-chat
<samueldr>
🎉 got EDK2 / OVMF.fd cross-built!
<gchristensen>
:o
<samueldr>
tangent to a thing I'm working on involving EDK2, couldn't start doing the other thing before making this work :)
<colemickens>
I'm looking for prior art on disk image construction without qemu if anyone has pointers. Seems like it should be more than possible, just thinking about it...
<samueldr>
colemickens: what are you looking for? not sure I see what requires qemu to make disk images
<samueldr>
the boot was excruciatingly slow, but I let it go all the way through just for the sake of it :)
<samueldr>
(I boted the aarch64 iso downloaded from hydra, no I did not cross-build it)
<colemickens>
Hm. I thought make-disk-image used it, but I only see it using it for the image conversion. I'm normally building Azure images, maybe they're doing something special.
<colemickens>
actually, a PR for my overlay builds a VM disk image, I'll see if it's using qemu or not, it's a good example of one that shouldn't need it.
<samueldr>
make-disk-image seems to use a VM, `pkgs.vmTools.runInLinuxVM`
<samueldr>
make-ext4-fs though doesn't
<samueldr>
though #52760 changes if to use lkl instead of debugfs; hopefully it should be possible to refector to make-fs and add a parameter for the fs
<colemickens>
aha, interesting. good, very relevant stuff, thx
<samueldr>
I didn't know about lkl before looking at that PR
<samueldr>
(and this reminds me I need to check something about that PR and then merge it)
<colemickens>
It boggles my head sometimes to think that "boot a qemu vm and perform steps there" is easier than composing some other tools. I appreciate why it is the case, but still it feels funny.
<samueldr>
russian dolls all the way down
lassulus_ has joined #nixos-chat
lassulus has quit [Ping timeout: 244 seconds]
lassulus_ is now known as lassulus
sir_guy_carleton has quit [Quit: WeeChat 2.2]
boredom101 has joined #nixos-chat
boredom101 has quit [Quit: Page closed]
<samueldr>
hm, re-targeting to another branch in a PR can be noisy :/
jasongrossman has joined #nixos-chat
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
endformationage has quit [Ping timeout: 272 seconds]
hedning has quit [Quit: hedning]
pie_ has quit [Ping timeout: 268 seconds]
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
pie_ has quit [Read error: Connection reset by peer]
pie_ has joined #nixos-chat
pie_ has quit [Excess Flood]
pie_ has joined #nixos-chat
qyliss^work has quit [Ping timeout: 246 seconds]
qyliss^work has joined #nixos-chat
__monty__ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie__ has joined #nixos-chat
pie__ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
pie_ has quit [Excess Flood]
pie_ has joined #nixos-chat
pie_ has quit [Read error: Connection reset by peer]
jD91mZM2 has joined #nixos-chat
<infinisil>
samueldr: Not if you do it fast enough! That is, switching it in both places at the same time
<infinisil>
At least this worked for me once
pie_ has joined #nixos-chat
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-chat
endformationage has joined #nixos-chat
jD91mZM2 has quit [Quit: WeeChat 2.2]
hedning has joined #nixos-chat
pie_ has quit [Ping timeout: 250 seconds]
jasongrossman has quit [Ping timeout: 250 seconds]
<gchristensen>
I've been wondering what it'd be like to have a background daemon shared across all your terminals, doing background processing on what you're doing ... like reminding you to commit changes if you haven't committed for a bit... or if rustc complees successfully after a series of failures... or adding git status info to your prompt, even if your repo is big and the git commands are slow (a reason I don't
<gchristensen>
use them)
<MichaelRaskin>
The commit reminder doesn't even need to care about your terminals
<samueldr>
I was thinking about ways to remind myself to check on $anything when it's been going for a while
<samueldr>
e.g. maybe notify-send and/or kdeconnect to my phone
<gchristensen>
yeah, that'd be cool
<MichaelRaskin>
Mine just wakes up from time to time and updates my Complicated Shell-generated Status Line with the information about directories with uncommited changes
<samueldr>
though now thinking about it, it can probably be done through ctrl-z, and bg+wait
<gchristensen>
MichaelRaskin: ooh, can you share more about that? I have a thing like that, and I'd be interested in making it nicer.
<gchristensen>
samueldr: clever!
<samueldr>
nah, samueldr: samueldr
<MichaelRaskin>
Which one?
<MichaelRaskin>
My commit-reminder is monotone-only but this is easy to change
<samueldr>
yeah, now I can probably do a cool script; didn't think about wait, and I would always forget to start it upfront
<gchristensen>
MichaelRaskin: that part, but the general "complicated shell-generated..." bits as a whole
<MichaelRaskin>
It searches for _MTN directories in ~/src (not a problem to add .git to the list, of course)
<MichaelRaskin>
Then cd/status/grep and all that goes to ~/.mtn-pending-changes
<MichaelRaskin>
I use a tiling window manager (StumpWM) and in the bottom of the main screen I have a frame with xterm
<gchristensen>
ah
<MichaelRaskin>
That xterm runs a shell loop with adjustable sleep in it
<samueldr>
MichaelRaskin: I seem to recall you wanted to give a talk about your system config, but it didn't go through; anything since to show and tell?
<MichaelRaskin>
As for the Complicated Shell Generated Status Line: it mostly does a lot of simple things. WiFi network name. Number of unread IM messages (separately IRC and XMPP; I hope to get a Matrix client compatible with that approach one day…) and a random channel/contact name with pending messages; number/sample of uncommitted repos; mail counts (unread/deferred/long-deferred-topics) and web feed counts
<MichaelRaskin>
IP addresses, RAM usage, battery status, date, times in a few timezones
<samueldr>
"programs I actually expect to work" lol
<infinisil>
First impression "What's wrong with that?", only then I saw "in the cloud"
<gchristensen>
yup
<simpson>
"They're stored in Bashhub's database. All commands are private. Bashhub's command database is encrypted at rest using storage level encryption. Commands are encrypted in transit using HTTPS." And, for more info, this basic doc: https://github.com/rcaloras/bashhub-client/wiki/Security-and-Privacy
<infinisil>
The idea isn't too bad, it would be cool to share the history over multiple machines. (But I'd want to use my own server for it)
<MichaelRaskin>
Isn't the actually horrifying moment when you understand there is password reset?
<gchristensen>
the whole thing is a bit of a nightmare I think
<MichaelRaskin>
Well, with client-side encryption with PBKDF and good passphrases…
<gchristensen>
not as bad
<MichaelRaskin>
But password reset page shatters all hope
<infinisil>
Why do they need the data anyways
<MichaelRaskin>
It should be a treasure trove of misentered passwords
<infinisil>
This would even work if they only have the encrypted data
<MichaelRaskin>
Password resets wouldn't work
<infinisil>
Just a simple data sync between all machines, computers are fast enough to do indexing themselves in milliseconds
<infinisil>
See fzf..
<samueldr>
yeah, "encrypted at rest" often means "encryption key on the API server, all data encrypted with it" :/
<gchristensen>
anyway, I've been thinking about this instead of accomplishing my holiday goal of committing changes on all the repos I have uncommitted changes on :|
<infinisil>
"kurly is an alternative to the widely popular curl program."
<samueldr>
`find . -name .git -exec script.sh "{}" ";"` script.sh being `cd $1; cd ..; git commit -am "new year new me; yolo"; git push --force`
<samueldr>
it's... possibly bad and break horribly
<infinisil>
No commit since 5 months. "The current authors are not security experts, but want to contribute to the fledgingmovement of replacing key tools and services with equivalents based on modernand safe languages."
<samueldr>
but hey, more time for egg nogg?
<infinisil>
samueldr: Haha
<gchristensen>
samueldr: so many secrets would get pushed
<MichaelRaskin>
I think git add . is needed for full blow
<MichaelRaskin>
Otherwise, some secrets might escape being pushed
<gchristensen>
:D
<gchristensen>
I'm tempted to reinstall my system w/ zfs and then explore with r/o /
<gchristensen>
down from 40 dirty repos to only 13.
__monty__ has quit [Quit: Mic drop]
hedning has joined #nixos-chat
<jasongrossman>
gchristensen: fish shell has a background daemon which synchonises history and variables between instances.
<jasongrossman>
gchristensen: (Neither history nor variables are kept exactly in sync - there are options to control what is and what isn't, plus there seem to be bugs.)
<gchristensen>
nice
<gchristensen>
I decided to go back to zsh after learning about preexec and precmd, plus after being annoyed by bash's history file behavior
jasongrossman has quit [Ping timeout: 250 seconds]
<infinisil>
Oh that reminds me, I once set up a zsh thing such that when I press Return and the line is empty, it repeats the last command
<infinisil>
But not sure where that went
boredom101 has joined #nixos-chat
<MichaelRaskin>
I think I have effectively done it a few times
<MichaelRaskin>
warranty replacements of HDDs in laptops kind of force it
<MichaelRaskin>
Wait, is NixOS-challenge message actually from #nixos?
<gchristensen>
yaeh
<srk>
gchristensen: heh, trying this commit all dirty repos for a few weeks already :D