{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-chat
ninjin has quit [Ping timeout: 256 seconds]
ninjin has joined #nixos-chat
drakonis has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 268 seconds]
drakonis1 has joined #nixos-chat
<elvishjerricco>
is freedesktop.org down for anyone else?
<samueldr>
curl: (7) Failed to connect to freedesktop.org port 80: Connection refused
<elvishjerricco>
that's odd
<drakonis1>
its up
<drakonis1>
well, kind of.
<samueldr>
how kind of?
<drakonis1>
i pinged it and i'm getting replies
<drakonis1>
but not from the main domain, i'm getting pingbacks from annarchy.freedesktop.org
<samueldr>
that's probably fine
<samueldr>
the IP reverse-resolved to that domain
<samueldr>
just like when you ping google.com it resolves a 1e100.net domain
<samueldr>
and yeah, looks like their server just doesn't respond to requests
<jasongrossman>
I can't ping it from here in Australia.
<jasongrossman>
Oh no, wait, I can, but it was VERY slow to start responding.
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 246 seconds]
Myhlamaeus has quit [Ping timeout: 252 seconds]
pie___ has joined #nixos-chat
pie__ has quit [Ping timeout: 246 seconds]
jackdk has quit [Ping timeout: 245 seconds]
<infinisil>
Oh god are you serious
<infinisil>
appleid.apple.com gives me 502 Bad Gateway if I'm using my VPN..
<infinisil>
???
endformationage has quit [Ping timeout: 272 seconds]
jasongrossman has quit [Quit: ERC (IRC client for Emacs 26.1)]
jasongrossman has joined #nixos-chat
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 245 seconds]
drakonis1 has quit [Ping timeout: 252 seconds]
noonien has quit [Quit: Connection closed for inactivity]
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
Myhlamaeus has joined #nixos-chat
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 252 seconds]
Myhlamaeus has quit [Ping timeout: 252 seconds]
johanot has joined #nixos-chat
obadz has quit [Ping timeout: 246 seconds]
__monty__ has joined #nixos-chat
jasongrossman has quit [Quit: ERC (IRC client for Emacs 26.1)]
jasongrossman has joined #nixos-chat
__Sander__ has joined #nixos-chat
drakonis has quit [Remote host closed the connection]
jasongrossman has quit [Remote host closed the connection]
johanot has quit [Read error: Connection reset by peer]
jasongrossman has joined #nixos-chat
drakonis has joined #nixos-chat
waleee has joined #nixos-chat
Jackneill has quit [Ping timeout: 245 seconds]
Jackneill has joined #nixos-chat
<srhb>
Any obvious way to "cage" the mouse pointer so that it cannot escape my current main monitor? Using xmonad.
<srhb>
Or, um, nonobvious :-)
<gchristensen>
looks like there are some gnarly x application hacks you can do ...
<srhb>
I'm alrady hooked deep into the X bindings, what could go wrong...
* gchristensen
chooses to not enumerate the ways
drakonis_ has joined #nixos-chat
<joepie91>
srhb: far as I know everything (mouse-locking games, synergy, etc.) just does the hack of "if mouse moved, and position outside bounds, then reset to bounds"
<gchristensen>
making r13y.com's update process an automatic background job is really really annoying due to things not working the same without a TTY, + the huge build time
<srhb>
joepie91: Yuck, of course... :-)
<joepie91>
srhb: caveat: I believe it was Firefox that used to check on screen bounds for mouse locking, instead of locking it in the center, and this caused some fun bugs when combined with stuff like Synergy that moves the pointer to another monitor when it is moved offscreen
<joepie91>
which manifested as "anything that mouselocks goes absolutely spinning crazy when you move your mouse"
<srhb>
Oh yeah...
<joepie91>
so now it locks in the center of the screen instead I think :P
<srhb>
:|
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 255 seconds]
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-chat
drakonis_ has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-chat
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-chat
<sphalerite>
gchristensen: really, are there other broken parts than diffoscope?
<gchristensen>
rsync + ssh identities etc.
<gchristensen>
every test run is like 1hr40min
<gchristensen>
so finding out you typo'd ssh-key instead of ssh.key is pretty gnarly
drakonis has quit [Read error: Connection reset by peer]
<sphalerite>
ouch
jcrben has quit [Quit: Ping timeout (120 seconds)]
jcrben has joined #nixos-chat
endformationage has joined #nixos-chat
noonien has joined #nixos-chat
drakonis has joined #nixos-chat
__Sander__ has quit [Quit: Konversation terminated!]
<manveru>
looks like the browser in steam isn't working anymore :(
<manveru>
they updated the chrome in the steam beta yesterday, probably the issue...
<manveru>
and i think there was a new steamos release
obadz has joined #nixos-chat
Myhlamaeus has joined #nixos-chat
waleee has quit [Quit: WeeChat 2.4]
<gchristensen>
the system I moved r13y's build over to seems to be muuuch slower than my laptop :|
<gchristensen>
always look on the briight side of rootkits
<samueldr>
aren't most desktop hardware subject to the same kind of issue? (genuing question)
<samueldr>
hm maybe not
<samueldr>
probably some kind of system to check if the thing is genuine when flashing from the OS
<samueldr>
though, thinking about it, maybe it means easily brickable, rather than corebootable; if bootguard is active, and you modify the firmware, it won't validate
<samueldr>
>> FPFs are typically used to store platform parameters. Setting FPFs requires Intel’s ME to be in the Manufacturing Mode. As part of a two-step process, the FPFs are first stored to temporary memory and are then “burned” when the Manufacturing Mode is closed. If a system remains in Manufacturing Mode, that means the FPFs have never been initialized because the process hasn’t been completed.
<tilpner>
combined seems a little overloaded though
__monty__ has quit [Quit: leaving]
<colemickens>
I guess NexDock is trying again. I'd be curious to see how well this + Librem5 works out for someone who offloads CPU-intensive tasks anyway.
<colemickens>
(It's on Kickstarter, but I don't want to link it, it's easy to find.)
<samueldr>
ah, raspi support is through hdmi in
<samueldr>
(still interesting)
<samueldr>
they don't specify which type-c alternate mode is required to be supported
<samueldr>
(this, stupidly, could also be used with another laptop to dual screen in the most absurd way, in theory)
<samueldr>
oh, it's in the list of other cool uses later on
<samueldr>
colemickens: you seemed to know them from, probably, the first device
<samueldr>
anything to know?
<samueldr>
>> NexDock 2 USB-C port works over displayport
<colemickens>
samueldr: ah, no, sorry, I've always been holding out for the 1 port dream. This is the first device of it's kind that hasn't had some sort of obvious flaw, and/or seems to have some momentum behind it. Some others I've seen are very far behind schedule, etc.
<samueldr>
the fact that they shipped previously tempts me to back
* colemickens
nods
<colemickens>
If I understand correctly Linux supports DP alt mode even if the HW doesn't have special support for it. And I assume Librem5 will be able to handle a stockish, new-enough kernel. I'm probably going to pull the trigger on it. Esp since the Librem5 purchase was long enough ago to write off in my head.