<sora>
laudecay: you would be very welcome, for sure. :)
<laudecay>
yeah idk i wanna learn more about the unikernel
<laudecay>
"diversity based constraints" well i got those so
<sora>
i dont think that matters as much as the webpage suggests, my impression was that the retreats are not heavily overbooked, and "wg in ocaml" sounds _hellalot_ interesting. :)
<laudecay>
yeah i wrote it for JS as an intern project this smmer
<sora>
(but thats just an impression from the outside)
<laudecay>
trying to do more soon
<sora>
so even if you dont attend, and dont care about the "qubes" part, if you could push your wg-in-ocaml stuff by then, i know 1-3 people who would be interested in qubeizing it as part of a retreat session.
<laudecay>
talking more w wireguard people about lie
<sora>
even better! thanks!
<laudecay>
we're working on adapting the zinc kernel module for userspace and getting it compiling right
<laudecay>
im doing so in haskell and ocaml w/ dune & cabal/ghc
<sora>
harhar. you dont pick easy targets.
<laudecay>
so that i dont have to have hella crypto libraries that im jankily writing wrappers for
<laudecay>
i just like functional languages
<sora>
my only personal exp with ghc is "darcs", and i dont think i ever had problems figuring out "whats code, whats comment" before or after.
<laudecay>
mood
<sora>
anyways, if no one else speaks up about your async-lib question, i would recommend to use whatever q-m-fw uses for purely selfish reasons, and can supply a "switch export" list if that helps to answer the question.
mahmudov has joined #mirage
<laudecay>
i think lwt right
<laudecay>
but
<laudecay>
yea
<sora>
(kicking off a clean q-m-f build, just to be sure its ... clean.)
<laudecay>
okay i applied!!! fingers crossed marrakesh would be SO COOL
<sora>
mirage-wireguard would be cool enough that you got my vote even if that means you go and i dont. :)
<sora>
(and yes, if "lwt" is a possible answer to your question, it is the one q-m-f would give. it just installed that.)
<sora>
and one of the reasons i keep pointing at that particular usecase ... it is one that is seeing actual use. like, "daily production use". not just "someone tried it as part of a two week workshop on functional languages in academia".
jnavila has quit [Remote host closed the connection]
mahmudov has quit [Read error: Connection reset by peer]
<laudecay>
oh sorry connected to vpn
<laudecay>
yeah i think more wg adoption is so important ugh
<laudecay>
vpns succ
<sora>
no worries at all. some people here can use irc in a super-async way. :)
<sora>
i dont have much preference either way. my main personal vpn is still openvpn. but _any_ working vpn in ocaml would be cool. bonus if it is one that is cross platform, which wireguard very much is.
<laudecay>
yeah exactly
<laudecay>
and wg doesn't support 9 million features that are mutually fucked up between implementations etc etc etc
<laudecay>
just standard....
<sora>
*shrug* ... see current rambling about "version" next door.
<sora>
there are ways to support a reasonable number of hashes and ciphers _without_ going x509 level batshit crazy.
<sora>
we are very much not talking about protocoal detail negotiations like ssl or so.
<laudecay>
yeah
<laudecay>
its not like SSL bad but
<sora>
with wg, it is about compat between cooperating peers.
<sora>
so even if there is _nothing_ about it in the protocol, but only in the implementation, that still works. mostlsy.
<laudecay>
also wg is zooooom
<sora>
if you configure one of your three peers with the wrong hash/cipher? well, it wont work. shocker.
<laudecay>
yeah
<laudecay>
i mean theres only one cipher
<laudecay>
you just put pubkey and ip
<sora>
so sane defaults? super.
<laudecay>
and off you go
<laudecay>
yeah sane and /good/
<laudecay>
noise protocol god bless
<sora>
otoh, i never had to bother with that setting up openvpn either. and it _probably_ uses "ok" defaults too.
<sora>
(because for most of us, the thread model doesnt include three letter agencies or aliens with quantum computers...)
<sora>
threat model. thank you, autocomplete.
<sora>
(or booze level. who knows.)
<sora>
reynir: not sure you got pinged. i tossed you an issue and PR for the GUI issue. feel free to reject/close the PR if you can find your fix for it, i wont complain. :)
<laudecay>
lol
<sora>
why are you laughing already? did you hack me? because that q-m-f build just aborted with a weird message about lwt versions. X)
<laudecay>
oh no just "three letter agencies" bc for most crypto nerds thats exactly the threat model
<laudecay>
no hax
<sora>
did you use "crypto" for "cryptography" there or for "cryptocurrencyscams"?
<laudecay>
cryptography ew
<laudecay>
duh
<sora>
ok. :)
<laudecay>
fuck cryptocurrencies idk the tech's cool but the people suck
<sora>
wait. that indicates you are older than 15 too! :)
<laudecay>
21
<laudecay>
yeehaw
<sora>
(hmm. the build rambled about lwt 5.x, but that doesnt seem to be the actual error. that looks more like that ppx* thing i ran into two weeks ago, in a slightly different way. *digs some more*)
<sora>
hm. its installing mirage-qubes 0.7.0 again (0.8 contains the "fix" for the ppx problem...)
* sora
pulls hard on that deps chains to see what rattles on the other end
<laudecay>
lmao
<sora>
no really. that thing worked a week ago. i swear.
<sora>
*more swearing*
<sora>
*more creative swearing* ... it works if i remove all pins.
<sora>
actualy, the only pin was mirage to 3.5.2
<sora>
and i am somewhat sure i added that a week ago because it wouldnt work without it.