<Ashy>
the main thing i like about ssds is that apps open instantly
<Ashy>
and if they don't something is wrong
<colemickens>
how does anyone survive bash and string escaping
<colemickens>
ssh + nix-shell + strings with spaces is absolute hell
<colemickens>
okay, wrote some text files to tmp space and call those instead, no one should go through this
<bqv>
colemickens: consider using pkgs.substituteAll instead
<bqv>
if you need extensive inlining
<bqv>
actually
<bqv>
what if i abused guix for this
<bqv>
nix for system infrastructure, guix profiles for system data
<bqv>
since guix has basically no useful packages anwyay
<samueldr>
colemickens: when doing something remotely complex through ssh I pipe into an interpreter (e.g. bash)
<samueldr>
echo "echo hi" | ssh $host
<samueldr>
it reduces complexity for at least one level
<colemickens>
samueldr: I was doing that too and sorta getting tripped up in the same spot. I finally got something working using printf '"%s" ' nix-build "${buildargs[@]}" ... and it did what I needed.
<colemickens>
buildargs has array elements with spaces. ugh, just ugh.
<colemickens>
gotta cart around those --option 'extra-binary-caches' and the space delimited values :(
<colemickens>
oh also, capturing output gets you the ssh stanza bleck
<drakonis>
bqv: system data?
<drakonis>
oh
<drakonis>
guix profiles already exist in some form within master nix
<bqv>
i know, that's why i started with that idea
<bqv>
see above
<drakonis>
right right
rajivr has joined #nixos-chat
<sphalerite>
colemickens: printf '%q ' nix-build "${buildargs[@]}" will work with args containing quotes as well, should you ever end up in that kind of hell
<colemickens>
Thanks! Nice
<kini>
just bought a QLC SSD but now I'm wondering, should I be worried about longevity because of churn in /nix/store ? common wisdom seems to be that QLC write endurance is more than sufficient for personal use cases, but I wonder if running NixOS means you end up writing to disk a lot more than the average person (?)
<kini>
I wonder if anyone has gathered any statistics on stuff like that
<ashkitten>
kini: how big is your nix store? i'd maybe be worried if you were running hydra but normal operation shouldn't have that much churn
<kini>
about 60GB at the moment
<ashkitten>
and how big is your ssd, for that matter?
<kini>
1TB SSD
<ashkitten>
you're fine
<kini>
thanks :)
<ashkitten>
the main thing with ssds is that they do wear leveling by moving around blocks, so the size of the ssd matters for longevity more than much else really
<samueldr>
last I checked, samsung's 1TB QVO are good for "360TB" of write, which I actually don't know how it works when "strained" under partial rewrites assuming e.g. 50% of the drive is the nix store and the rest your data
<samueldr>
though I've been wondering if the difference in price between an EVO or QVO for SATA (not NVME) really matters
<ashkitten>
also they can't do as much wear leveling if they're full, so don't let it get over like 90% or something generally... but that's common advice for filesystems too
<samueldr>
like, should I get the EVO which is not that much more expensive? or am I paying for only not much more perf?
<kini>
this QLC SSD (Crucial P1) is rated for 200TB lifetime writes, so I guess that means rewriting my nix store from scratch ~3333 times
<kini>
that gives me around a decade of life if I churn through the whole store once per day, which isn't happening, true
<ashkitten>
ssds will basically either last forever or die very suddenly and irrecoverably (if the flash controller dies)
<ashkitten>
i will always recommend redundancy
<samueldr>
ashkitten: isn't lasting forever just dying suddenly later?
<ashkitten>
samueldr: less suddenly, i would hope, if the actual flash eventually wears out
<samueldr>
oh, I thought that forever was just "hasn't died yet" :)
<ashkitten>
i always treat every drive as "hasn't died yet"
<ashkitten>
redundancy is critical
<kini>
if the flash wears out I guess it just turns into a read-only device, which is not really an issue since you can retrieve the data easily and copy it over to a replacement drive
<kini>
flash controller dying sounds a lot more painful
<ashkitten>
yes, it is more painful
<ashkitten>
your system freezes and won't come back up after a reboot, whoops all your data is instantly gone and unrecoverable
<ashkitten>
no way to predict
<kini>
currently I have my root fs (including /nix) on a non-redundant SSD and my homedir and other archival data in an HDD array with a couple mirrored pairs of drives
<ashkitten>
yeah probably fine to store non-stateful data on a single drive
<ashkitten>
i should do that...
<ashkitten>
good idea
<kini>
but after ~8 months of this I've realized that to gain qualitative improvements of life from my SSD I should really have my homedir on there too, not just /nix
<kini>
so I'm upgrading to this new SSD (my current one is only 250GB) and going to move my homedir onto it, but now I'm going to need to do periodic backups of it, at least into the HDD array if not offsite)
<bqv>
I no longer have a hdd
<bqv>
The QoL change is insane
<kini>
SSD $/GB is still not low enough for me to go 100% SSD but yeah, ideally I'll only need to put backups and rarely accessed large files on my HDDs
<ashkitten>
hmmm
<kini>
... did I just write "qualitative improvements of life" instead of "quality of life improvements", lol
<ashkitten>
yeah it'd be something like $900 to upgrade to ssds
<ashkitten>
for me
<ashkitten>
i'm gonna save it until after new gpu
<bqv>
Tbh maybe the most sensible way to achieve what I was thinking is hella btrfs subvolumes that I can snapshot and/or selectively make read-only
<ashkitten>
how's btrfs vs zfs in practice?
rardiol has quit [Ping timeout: 256 seconds]
<bqv>
Never used zfs
<bqv>
I don't feel I'm missing out
<bqv>
oh!
<bqv>
no! even better
<bqv>
because it makes more sense at the malleable and file level
<bqv>
i can use ipfs to store everything on my system
<bqv>
and just link stuff from the ipfs virtual filesystem
<bqv>
ohohoho
<bqv>
this sounds spicy
LnL has quit [Read error: Connection reset by peer]
LnL has joined #nixos-chat
xd1le has quit [Ping timeout: 260 seconds]
<elvishjerricco>
ashkitten: They have somewhat different feature sets. I think the main thing is that btrfs can rebalance and change raid modes and stuff, whereas ZFS can have multiple vdevs so that e.g. a 120 disk pool is safe from more than just 2 drive failures. The feature differences definitely don't stop there though (ZFS has a lot more AFAIK, but a most of them are primarily for enterprisey purposes; and ZFS has native encryption).
<ashkitten>
hm
<ashkitten>
change raid modes?
<elvishjerricco>
But the other main thing is that btrfs just doesn't have as good a track record with reliability. Supporters say this is basically not an issue though. raid5/6 still have a fundamental write hole that can lose data, but it's absurdly difficult to trigger, even on purpose. And it can supposedly be fixed by just setting metadata to raid1(c3), which will be negligibly different
<elvishjerricco>
ashkitten: You can convert a btrfs pool from raid1 to raid5, for example
<ashkitten>
can you expand capacity by adding more disks?
<elvishjerricco>
Yea. btrfs actually has a better feature set for that than zfs.
<elvishjerricco>
rebalancing in particular
<elvishjerricco>
And it can remove drives, whereas doing the same in ZFS is NOT recommended for perf reasons
<ashkitten>
i'm actually interested in that but i'm worried about reliability
<ashkitten>
how "not a problem" is it really?
<ashkitten>
also, can you send datasets from one pool to another like zfs?
<ashkitten>
i use that to backup my server to my desktop's disks
<elvishjerricco>
I have no idea honestly. I check in on /r/btrfs and #btrfs every now and then to see how well it works for people, and I do still see the occasional "btrfs just up and died" post. And I mean actually btrfs's fault; there's even more posts like "I did something wrong and killed it because btrfs's user interface is poorly designed and confusing"
<elvishjerricco>
And yea it has send/receive like zfs
<elvishjerricco>
Oh and btrfs raid10 is a tad more restrictive than the equivalent in ZFS; the only cases where disk layout is more flexible in ZFS
<ashkitten>
ugh i'd really like to be able to use brtfs because i legitimately think it'd be useful
<ashkitten>
but i can't if it has reliability issues like that
<elvishjerricco>
The cases where it's btrfs's fault are pretty rare, to be fair. But I literally never see that on /r/zfs or #zfsonlinux
<ashkitten>
yeah, i can't risk it
<elvishjerricco>
Plus I don't subscribe to mailing lists
<elvishjerricco>
Because... god I hate mailing lists :P
<elvishjerricco>
I think ZFS is just more reliable and robust, even if it's less flexible. Truth be told, I think the flexibility is only needed in fairly niche cases.
<elvishjerricco>
But ZFS is definitely more designed for enterprise environments, whereas btrfs is designed for more all-purpose.
<ashkitten>
it'd be nice to be able to defragment my pool
<ashkitten>
or add more storage
<elvishjerricco>
ZFS can add storage
<elvishjerricco>
It'll just be unbalanced
<elvishjerricco>
i.e. `zpool add tank mirror new-disk1 new-disk2`, but all your existing data will still be on the other vdev, and new data will be distributed between the two vdevs mostly based on how much free space is on each one
<ashkitten>
so i can have a raid5 array of 5 disks with zfs, and add another disk to expand its capacity?
<elvishjerricco>
Oh
<ashkitten>
that's what i want, i thought you said btrfs can do that
<elvishjerricco>
No you can only add new vdevs, not expand an existing raidz vdev (though this is a feature that is coming in a future version)
<ashkitten>
siiigh... almost all zfs's issues for me depend on bp rewrite huh
<elvishjerricco>
You can replace every disk in a vdev with a bigger one, and then the vdev will grow to the size of the new disks
<elvishjerricco>
Btrfs has a different concept of pool though
<ashkitten>
oh, i meant.. add another single disk
<elvishjerricco>
It's literally just a bunch of disks, and then btrfs decides how to write data based on the raid mode
<ashkitten>
wait, like unraid?
<elvishjerricco>
So you can add and remove disks willy nilly and btrfs can rebalance and stuff.
<elvishjerricco>
I have no idea how unraid works
<ashkitten>
i think unraid might work at the file level
<elvishjerricco>
But yea, you can't add one disk to a ZFS raidz vdev. Again, future version will have that, but it's a ways off.
<ashkitten>
but afaik it takes a random bunch of disks and ensures that files are duplicated across them redundantly
<elvishjerricco>
Basically yea
<elvishjerricco>
Like raid1 just says "Everything you write will have two copies among all these random disks that you've thrown in the pool"
<elvishjerricco>
By contrast, ZFS requires you to be pretty explicit via vdevs
<ashkitten>
does btrfs have actual raid as well?
<elvishjerricco>
ashkitten: What do you mean by "actual raid"?
<ashkitten>
like, with striping
<elvishjerricco>
AFAIK, ZFS and btrfs share this in common: Things are written by extent/record. In btrfs, extents are written to I think just one disk, with parity info or mirrored copies being written to different disks. With ZFS, every record is written to one vdev, and the vdev determines how that's written to its disks.
<elvishjerricco>
So you'll get "striping" in that reading a bunch of extents at once will read often read them from different disks
<elvishjerricco>
And I think the raid10 mode of btrfs (which is more rigid than its other modes) is actual striping
<ashkitten>
ah
<ashkitten>
what about bcachefs? is that any good?
<elvishjerricco>
Waaayyy too alpha quality
<elvishjerricco>
But it has a promising future
<bqv>
every time i even try and add it to my kernel, it breaks everything
<elvishjerricco>
Basically all the features of btrfs, plus the caching layer, plus encryption, and hopefully more reliable
<ashkitten>
ooh
<bqv>
that's too alpha even for me
<ashkitten>
what's the timeline look like?
<elvishjerricco>
Not a clue
<bqv>
it's a one man show
<bqv>
so it's "done when it's done"
<elvishjerricco>
Though he is being pretty well funded to work on it, fwiw
<elvishjerricco>
The showstopper at the moment, aside from basic reliability, is lack of snapshotting, let alone send/receive
<elvishjerricco>
I tried to play with it once but I couldn't even figure out how to use its raid features :P
<ashkitten>
sigh.. i'd really like zfs bp rewrite
<elvishjerricco>
Yea... I think they're just resigned to never implementing that
<elvishjerricco>
bp rewrite is the main reason btrfs has such a bad reliability track record
<ashkitten>
well, after previous attempts ended with the devs saying they thought it might end up being the last feature zfs ever got... yeah, not appealing to work on i guess
<elvishjerricco>
If I couldn't use ZFS, I'd have a hard time choosing between btrfs and `dm-integrity -> md -> LVM -> some FS`. On the one hand, btrfs isn't so reliable. On the other hand, the other setup is absolute jank and dm-integrity has some bad perf problems
<elvishjerricco>
And I have no idea if LVM can do anything like send/recv, which would be a deal breaker
<ashkitten>
even offline bp rewrite would be really good is the thing
<elvishjerricco>
I think they'd reject that because of their enterprise 100%-uptime mindset
<ashkitten>
being able to rebalance and defrag a pool without send/recv would be amazing
<elvishjerricco>
LVM can handle raid stuff and caching stuff all on its own, can't it? Can it do checksumming too?
waleee-cl has quit [Quit: Connection closed for inactivity]
<elvishjerricco>
Though IIRC LVM is realistically just a fancy frontend for a TON of different device mapper things
<elvishjerricco>
ashkitten: FWIW, defrag isn't nearly as important if you have the right recordsize set. Balancing would be good though
<ashkitten>
defrag wouldn't be important if i had ssds
<elvishjerricco>
Even on HDDs, recordsize goes a pretty long way
<ashkitten>
yeah
<ashkitten>
i think i set it wrong on my server
<ashkitten>
not much i can do about that, i'll fix it when i migrate to a new server
<elvishjerricco>
You can always change it so new data is written better
<ashkitten>
oh recordsize not ashift
<elvishjerricco>
Oh, yea setting ashift wrong is catastrophic lol
<ashkitten>
yeah
<elvishjerricco>
People just assume the drive will tell the truth about their sector size... they basically never do
<ashkitten>
i fixed some of the issues by cleaning up the 24000 snapshots
<ashkitten>
but the latency is still pretty awful
<elvishjerricco>
Oof
<elvishjerricco>
I dunno if latency would be an ashift problem though, at least for reads.
<ashkitten>
the spiky part before 08/09 is normal activity before, then there was a scrub that took almost 24 hours to get 50% through and i was like "screw this" so i decided to figure out what was wrong and ended up deleting snapshots
<ashkitten>
and then the smoother part after is what it's doing now
<elvishjerricco>
ashkitten: Oh, one of the biggest differences between ZFS and btrfs (and any linux FS for that matter) is that ARC is about a billion times better than the linux page cache for file caching. Though ZFS can fall behind in cold benchmarks, warm data is often way faster with ZFS.
<joepie91>
> Baker says Mozilla will initially focus on products such as Pocket, its VPN service, its VR chatroom Hubs, and new “security and privacy” tools.
<joepie91>
I'm confused
<joepie91>
so they want to focus on Hubs but fired their VR team?
<joepie91>
and want to focus on security and privacy and fired their threat management team?
<{^_^}>
error: syntax error, unexpected ',', expecting ')', at (string):320:67
<makefu>
i thought their new focus is "making money"
<joepie91>
well yeah but even that kinda requires "having a product" as a dependency :P
<makefu>
what i cannot see is how the 'The coronavirus pandemic “significantly impacted our revenue,”'
<joepie91>
which seems... difficult when you fire the people building it
<joepie91>
makefu: it's BS
<joepie91>
they're using it as an excuse
<makefu>
totally
<joepie91>
there have been rumblings about this for a long time now apparently
<pie_>
maybe they just had no revenue anyway? :P
<pie_>
or what
<makefu>
isn't it true that they get like 80% of their money from google for using them as the default search engine?
<pie_>
mozilla has been doing weird shit for a while but still being this on fire is probably not great
<pie_>
s/no revenue/negative revenue/
<pie_>
(idk)
<makefu>
'Revenue is the total amount of income generated by the sale of goods or services related to the company's primary operations'
<makefu>
'Income or net income is a company's total earnings or profit. '
<makefu>
so you can have negative income but no negative revenue, right?
<colemickens>
negative revenue = more returns than sales in a given period ?
<sphalerite>
that would be negative income
<pie_>
ok maybe the problem is that im assuming mozilla wasnt coming out positive
<sphalerite>
no?
<pie_>
where the fuck do they find their execs
<sphalerite>
good question
<pie_>
inb4 concerted veiled attacks on the internet
<sphalerite>
they should have laid them off
<sphalerite>
pie_: nah that's just a side effect
<pie_>
how is the .net buyout doing anyway
<pie_>
or .org
<pie_>
whatever it was
<sphalerite>
wasn't it .org? I think it failed
<pie_>
why is mozilla deliberately trying to shoot off its entire leg
<pie_>
its entire remaining leg? :P
<pie_>
from the one company i had experience with, bad execs make the company fall apart
<sphalerite>
pie_: to bleed it dry
<sphalerite>
AFAIUI mozilla still has a lot of assets.
<pie_>
fuckin whyyyyyyyyy do people gotta be like this
<sphalerite>
Mozilla Corporation was a bad idea
<pie_>
i hope this can be a push towards more public (decentralized?) infrastructure but i dont think we're there yet
<pie_>
(also decentralized sounds nice to say but im not sure its a solution for everything :P)
<pie_>
ive been feeling information sovereignity (just swiped this from some random twitter) has been going increasingly to shit but mozilla seemed at least a bit of a flagpost holding back a tide, symbolically if nothing else?
<adisbladis>
Fire the execs, keep the engineers.
<adisbladis>
Firing the Servo team seems very short sighted
<pie_>
hahahahahaaha foresight
<pie_>
:'C
<adisbladis>
It's one of the things that makes Firefox actually interesting for the future...
<adisbladis>
pie_: Sadly foresight doesn't result in $$$ this quarter :/
<leons>
A german IT news site said that they're going to focus primarily on new features such as Pocket, VPN and Machine Learning (facepalm)
<leons>
I really don't want to have to develop my own browser :)
<ashkitten>
i hate capitalism so much
<LinuxHackerman>
We need a new Mozilla Foundation without a Corporation in it
<pie_>
dont hate the system hate the CEO
<immae>
I’m quite confident (hopefully not overconfident) that a community-developped firefox will arise soon
<pie_>
idk thats a pretty heavy burden
<pie_>
you cant do a project like that without real management
<pie_>
not that i would know
<pie_>
you need full time people on something like this (but idk)
<adisbladis>
pie_: Tbf hating the system is also perfectly valid
<pie_>
yeah but in this case hating the management is tractable? :P
<immae>
You can have a kind of paid work even with a community developped software
<immae>
but well, we’ll see how it goes...
<adisbladis>
pie_: Absolutely. I hate both capitalism and management ^_^
<pie_>
so, given that browsers are what managed to bridge the platform divide, and a friend of mine just told me they think apple switchign cpus will push more things into electron, ans that chromium is an OS
<pie_>
im going to tinfoil hat real hard here and say someone wants to make sure firefox isnt a viable platform
<pie_>
not that they were even going for that but
<ashkitten>
what do we do to keep from spiraling into hopelessness, asking for a friend
<leons>
Wait why don't we make Chromium our window manag... oh, I see... :(
<adisbladis>
ashkitten: Tell me when you find something, also asking for a friend
<pie_>
adisbladis: ashkitten stop thinking about useless things and put one foot in front of the other
<pie_>
ok maybe thats more like "how to operate under hopelessness" but yeah :P
<pie_>
i havent really been able to go in the direction, but i try to stay OSS and infrastructure projects adjacent in the hope that i can help build something that will outlast the garbage
<ashkitten>
sigh
<pie_>
which reminds me, i need to do my putting one foot in front of the other for today
<leons>
pie_: That tweet has a valid point. My instant fear was being that the movement behind Rust would slow down, but I'm very certain we've passed the point of strong reliance of Mozilla
<pie_>
mozilla seems to be intent on pushing people away from needing it
<pie_>
i hope it works
<pie_>
in the sense that a better way will be found to stand :P
dtz has quit [Quit: killed]
emily has quit [Quit: killed]
bbigras has quit [Quit: killed]
aanderse has quit [Quit: killed]
vaibhavsagar has quit [Quit: killed]
danielrf[m] has quit [Quit: killed]
philipp[m] has quit [Quit: killed]
colemickens has quit [Quit: killed]
thefloweringash has quit [Quit: killed]
Irenes[m] has quit [Quit: killed]
arcnmx has quit [Quit: killed]
leons has quit [Quit: killed]
worldofpeace has quit [Quit: killed]
balsoft has quit [Quit: killed]
aterius has quit [Quit: killed]
rycee has quit [Quit: killed]
JJJollyjim has quit [Quit: killed]
jtojnar has quit [Quit: killed]
LinuxHackerman has quit [Quit: killed]
noneucat has quit [Quit: killed]
crazazy[m] has quit [Quit: killed]
puzzlewolf has quit [Quit: killed]
jneplokh has quit [Quit: killed]
CRTified[m] has quit [Quit: killed]
lopsided98 has quit [Ping timeout: 260 seconds]
lopsided98 has joined #nixos-chat
jneplokh has joined #nixos-chat
<pie_>
how bad could the next firefox release possibly be :P
<pie_>
im am kind of worried about threat management (all of it?) being gone and downstream problems for tor
<pie_>
meant that for -security but eh
JJJollyjim has joined #nixos-chat
puzzlewolf has joined #nixos-chat
philipp[m] has joined #nixos-chat
rycee has joined #nixos-chat
aterius has joined #nixos-chat
arcnmx has joined #nixos-chat
vaibhavsagar has joined #nixos-chat
colemickens has joined #nixos-chat
jtojnar has joined #nixos-chat
CRTified[m] has joined #nixos-chat
aanderse has joined #nixos-chat
danielrf[m] has joined #nixos-chat
leons has joined #nixos-chat
worldofpeace has joined #nixos-chat
thefloweringash has joined #nixos-chat
bbigras has joined #nixos-chat
dtz has joined #nixos-chat
noneucat has joined #nixos-chat
crazazy[m] has joined #nixos-chat
emily has joined #nixos-chat
balsoft has joined #nixos-chat
Irenes[m] has joined #nixos-chat
LinuxHackerman has joined #nixos-chat
<leons>
https://i.redd.it/uq2x12zdtyl41.png just got this message - I like the Multi-Account Containers, but that's almost endorsing Facebook use?
<Valodim>
so?
<Valodim>
the phrasing "it's okay to" sounds like "it's not great but we know how it is" to me, which is a reasonable stance for Mozilla imo
ky0ko has quit [Quit: killed]
<Valodim>
something like "don't use facebook" on the other hand sounds like marketing suicide :)
<Mic92>
Agreed.
ky0ko has joined #nixos-chat
<philipp[m]>
Hahaha! You can build very cheap token authentication for nginx with the remote_auth module.
<philipp[m]>
I got token auth with our gitlab running in 4 lines of config.
<Mic92>
philipp[m]: how does this work?
<Mic92>
How does the user login than?
<Mic92>
some sort of oauth would be nice sometimes for webapps that don't have users etc
<philipp[m]>
We are using it for a private composer repository, so we don't use it with browsers. Basically is what auth_remote does is proxying your request (you can drop the body) to a different URL specified in the config. If that returns 200, the auth succeeded and if not 403 gets returned.
<{^_^}>
cannot read '/nix/store/952vyd3q3x8vig3zz7z8b8fj0bx7hplr-hostname', since path '/nix/store/jw964gs78h0lcs7qgn5ifzj7z67hxvxa-hostname.drv' is not valid, at (string):320:1
<Mic92>
It's a nice experiment to reason about nix and security
<infinisil>
Hmm I wonder if I could change the bot to use flakes and allow people to import flakes
<infinisil>
Should probably be fine if it continues to run with restricted eval
<Mic92>
infinisil: do you have systemd confinment enabled for your bot, just in case?
<abathur>
found a kindred spirit lurking in the pytest changelog: "Include new disable_test_id_escaping_and_forfeit_all_rights_to_community_support option to disable ascii-escaping in parametrized values."
lopsided98 has quit [Ping timeout: 260 seconds]
JJJollyjim has joined #nixos-chat
<JJJollyjim>
lol
lopsided98 has joined #nixos-chat
<bqv>
Apparently there was a torrential storm in fyfe with 3 hour of "apocalyptic" thunder. It might be insensitive, but god that sounds exciting. I love thunderstorms on the best of days and having been promised one for the fourth day running and the record breaking temperatures makes it sound great
<colemickens>
Feeling a bit blocked or burnt out on existing projects, so it's exciting, it's new project day. :)
drakonis has joined #nixos-chat
<drakonis>
oh no its getting weird again
<adisbladis>
joepie91: I know some of these words!
<joepie91>
lol
<joepie91>
adisbladis: he's moved on to another project by now
<joepie91>
finished the cable earlier
<drakonis>
say what
<joepie91>
damn split-keyboard link cables..
<joepie91>
impossible to get compatible replacements
<joepie91>
the link cable for this keyboard is basically mini-USB on both ends, but it is not USB electrically
<joepie91>
normally one of the pins is wired to GND or VCC within the connector, to indicate host/OTG status
<joepie91>
in this cable, pins are just wired 1:1 to the other end
<joepie91>
so any kind of standard miniUSB + converter contraption will just short things out
<adisbladis>
Yay?
<joepie91>
TL;DR: nightmare
<joepie91>
and good luck finding a miniUSB-to-miniUSB cable that is electrically wired 1:1, totally non-spec-compliant and non-USB :P
<joepie91>
thus, custom cable
<samueldr>
now imagine if you ran PCIe on HDMI cables
<bqv>
oh, one neat benefit of my ipfs tricks is that i can do things to files and not have to care what path they're on
drakonis has quit [Ping timeout: 246 seconds]
drakonis has joined #nixos-chat
<drakonis>
my desktop is chugging again
__monty__ has quit [Quit: leaving]
kalbasit_ has quit [Ping timeout: 240 seconds]
cjpbirkbeck has quit [Ping timeout: 260 seconds]
cjpbirkbeck has joined #nixos-chat
kalbasit_ has joined #nixos-chat
<bqv>
why do people keep starring stuff i do that isn't cool or useful :|
<energizer>
i'm doing a big install, copying lots of things from cache.nixos.org, and it's pretty slow. each "copying path.." line takes like 5 seconds. is that normal?
<energizer>
eg `copying path '/nix/store/fc3z4hklapy9iw5i4hvpvjy40v69p989-iproute2-5.5.0' from 'https://cache.nixos.org' ` took 10 seconds
<energizer>
would somebody try `time nix run nixpkgs.iproute`
<bqv>
error: --- SysError --- nix
<bqv>
getting status of '/run/weechat/nixpkgs.iproute': No such file or directory
<energizer>
i cant remember how long this is supposed to take
<bqv>
ok on a scale of one to don't even bother, do you think i'd have much luck convincing my coworker that we should write the azure app service we're about to write in rust instead of asp net core
<bqv>
he definitely doesn't know rust, but he's not top shelf at c# either anyway
<bqv>
and M$ is draining my soul
<colemickens>
as someone who likes rust, no
<colemickens>
unless you have a secret good azure sdk I don't know about :P
<colemickens>
guess it depends on what your app service is doing, but maybe I take back what I said
<colemickens>
I'm usually doing IaaSy stuff which it does not support at all :(
<colemickens>
(then again IaaSy stuff is fairly easy to knock out with a REST client)
<bqv>
i might try it. i basically just need a thin and secure authenticatey website thing
<bqv>
and rust leans heavily into the secure part of that
<colemickens>
I might be doing something similar soon, if it's oss please send me a link. I was thinking of churning it out in Go though, but also, Idk about that.
<bqv>
oh yeah, Go would be a worthy choice, but i don't know if it has azure bindings
<bqv>
i swear to god i'd pick anything over C# though
<colemickens>
I used to work on the Go Azure SDK.
<colemickens>
It exists and is fine.
<bqv>
in that case, you have my full attention
<colemickens>
(it's autogenerated so covers IaaS well at least)
<bqv>
at least Go is real easy to pick up too
<colemickens>
I would be curious what your "authenticatey" thing means. I just filed a bug on some auth related stuff (which between you and me is related to a decision I made 4 years ago, oops) and noticed another auth related issue.
<colemickens>
anyway, ping me if you want, i'm a glutton for punishment
<bqv>
:D
<Ashy>
i remember c# not being too bad of a language overall
<Ashy>
it was never sexy or fun though
<Ashy>
i came into it from 5 years of hacking access97 vba though so that may have tinted my glasses at the time...
<bqv>
i mean i actually don't mind C# or .Net in general, as you say it's just not sexy or fun. ASP.Net(core) on the other hand, gives me acid reflux
<Ashy>
ah yeap, i've not used it
<bqv>
i generally end up doing c# stuff because it's the "industry standard" and it's the thing i've built up career experience for, which means for the most part i'm stuck with it for all eternity
<colemickens>
samueldr: how do I request a new channel be logged?
<bqv>
probably has to do it manually...
<colemickens>
well, someone in #nixos-azure asked it be logged and that probably makes sense given how much I wrote and will likely wind up repeating
<bqv>
ah, #nixos-azure, for those of us blessed with the luxury of not being cloud-native and serverless
<colemickens>
give me iaas or give me death
<bqv>
terraform is the only thing keeping me sane
kalbasit has quit [Ping timeout: 244 seconds]
<samueldr>
colemickens: you ask for it
abathur has quit [Read error: Connection reset by peer]