<ekleog>
well… it's already a one-liner, isn't it?
<ekleog>
but doesn't `nix-env -iA nixGLIntel -f https://[...]` work?
<colemickens>
it tries to extract it as a tarball, unfortunately.
<infinisil>
Youtube added a chat feature??? Why???
<infinisil>
Is this going to be the replacement by google for Google+ now that it's gonna shut down??
<etu>
infinisil: Maybe related to live-streaming? A chat makes sense then.
<colemickens>
it was used slightly during nixcon
<ekleog>
colemickens: hmmm, you can likely do with `nix-env -iE '(import (builtins.fetchurl { url = https://[...]; })).nixGLIntel` or something like that? (fetchurl without sha256 works and caches only for like 1hr)
<ekleog>
infinisil: that's Google's way of saying YouTube will soon be EOL'd, as it has reached its goal of accumulating enough video data :p
<jasongrossman>
Every web service attempts to expand until it has streaming video and chat rooms (to misquote Jamie Zawinski ... or actually to misquote whoever first said that thing, since Wikiquote says it wasn't Zawinski).
<infinisil>
Youtube streams had chats before already and that makes sense
<infinisil>
But now there's something different
<infinisil>
Like a normal whatsapp/telegram chat in the youtube app itself. With groups and friends and stuff
<infinisil>
Their reasoning is "You can now share videos and chat about them with friends faster and easier on YouTube! 😎"
<infinisil>
We have different applications for different things, don't do this shit google
<colemickens>
Only idea I have is it's some "web of trust" sort of thing for trying to improve the perceived comment quality
<etu>
Blockchain-comments!
<colemickens>
but yeah, Google and chat apps is just a bad meme at this point
alienpirate5 has quit [Ping timeout: 250 seconds]
alienpirate5 has joined #nixos-chat
drakonis has quit [Ping timeout: 240 seconds]
drakonis has joined #nixos-chat
peterHK has quit [Ping timeout: 256 seconds]
peterHK has joined #nixos-chat
dmc has joined #nixos-chat
__monty__ has joined #nixos-chat
__Sander__ has joined #nixos-chat
<srhb>
Anyone perchance have a supercharged hydra-notify lying around somewhere? /me dreads correcting it
<gchristensen>
are phone cards a thing still? I need to call the US today and Three won't let me without having a UK credit card :|
peterHK has quit [Ping timeout: 256 seconds]
drakonis has quit [Ping timeout: 268 seconds]
drakonis has joined #nixos-chat
<jasongrossman>
gchristensen: They are still a thing, although maybe harder to find than they used to be. There are also all sorts of schemes for phoning intermediary companies who proxy your call (although they don't call it that). I recommend lots of web searching.
<jasongrossman>
gchristensen: I'm in Australia so don't know details local to you.
<elvishjerricco>
srhb: Moving here, off-topic
<srhb>
Ah, yes. :-)
<elvishjerricco>
I guess the best part about secrets in environment variables is that they're ephemeral. They die with the process.
<srhb>
Yes. Though what I _really_ want is a bit more involved
<elvishjerricco>
And what is that?
<srhb>
I want a wrapper that I can simply shove into ExecStart that 1) watches some secrets 2) wraps the configuration for $whateverservice and looks for placeholder variables in it
<srhb>
Then, when the secret changes, it relaunches the service, templating out the configuration file into a tmpfs or something, secrets included, and relaunches the service
<srhb>
This would cover like 99% of my use cases.
<elvishjerricco>
srhb: Hm... Can systemd do anything like that? Like a service for vault or something that notifies systemd that a secret has changed, causing any units depending on that secret to restart?
<srhb>
elvishjerricco: Possibly, I'm not sure. But I'm also not sure that's exactly what I want. I guess it is if I just always point the actual service at the rendered config file.
<srhb>
Whenever that changes, do the reloady.
<srhb>
Hmm!
<srhb>
That might actually be quite nice.
<srhb>
Then the vault-renderer basically becomes the analog to the nixops -keys services.
<elvishjerricco>
Yea, I'm just thinking that the units would use vaultenv or something
<elvishjerricco>
And then some daemon restarts any relevant vaultenv unit.
<elvishjerricco>
That way secrets still die with processes, and there's no risk of a file changing before a unit that uses it has been killed
<srhb>
I think this would be quite nice.
<elvishjerricco>
Doesn't sound too hard either
<elvishjerricco>
Just a matter of figuring out how that daemon would work, and how to define the systemd dependencies
<srhb>
Yep.
<srhb>
Anyway, lunch, then work, then more fiddling with plugins or this. :-)
<elvishjerricco>
Heh nice
<elvishjerricco>
srhb: Let me know if you ever get that working btw. I'd l
<elvishjerricco>
I'd love to see that as a nixos module somewhere