qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
pie_ has quit [Ping timeout: 248 seconds]
pie_ has joined #spectrum
xwvvvvwx- has joined #spectrum
puckipedia has joined #spectrum
qyliss_ has joined #spectrum
ehmry_ has joined #spectrum
ardea has joined #spectrum
xwvvvvwx has quit [*.net *.split]
andi- has quit [*.net *.split]
puck has quit [*.net *.split]
ehmry has quit [*.net *.split]
aranea has quit [*.net *.split]
qyliss has quit [*.net *.split]
qyliss_ is now known as qyliss
xwvvvvwx- is now known as xwvvvvwx
puckipedia is now known as puck
pie_ has quit [Ping timeout: 248 seconds]
andi- has joined #spectrum
pie_ has joined #spectrum
ehmry_ is now known as ehmry
xwvvvvwx has quit [Quit: ZNC 1.7.5 - https://znc.in]
xwvvvvwx has joined #spectrum
<qyliss> tazjin: this site is currently working and has the info I need, but I'm guessing it's no more guaranteed to be stable than the other one? https://cros-updates-serving.appspot.com/
<tazjin> qyliss: I dug into it and these two have slightly different behaviours
<tazjin> cros-updates-serving shows you what the latest available build is, whereas omahaproxy shows you what the latest update that is being *served to users* is (omaha is Google's auto-update system)
<tazjin> if that's fine for you, afaict cros-updates-serving does not suffer from what causes the errors on omahaproxy - both are at similar levels of "best effort" support, but this one is less likely to randomly break
<qyliss> Well, it's certainly better than nothing!
<qyliss> It's probably what I want anyway tbh
<qyliss> So I'll switch to that
<qyliss> Thanks very much
<tazjin> np
<qyliss> wooo! crosvm in nixpkgs
<tazjin> \o/
tilpner_ is now known as tilpner