want to help bring digital autonomy using #NixOS?https://fediversity.eu is hiring (EU-based) developers
-
@S0AndS0 thanks for asking! i take it this isn't technically strict, tho rather "it depends". as a dev, that legal side isn't my forte, but feel free to apply.
@kiara Heh, yeah, legal stuff is special... especially for international work x-)
But, from my experience attorneys have it a bit easier when contracts are B2B; so from a certain Org, a certain so-and-so, may be power-sliding into certain email inboxes
-
want to help bring digital autonomy using #NixOS?
https://fediversity.eu is hiring (EU-based) developers!
we'll also be at #fosdem's #nix track next week.@kiara I have been (over)thinking about tech sovereignty the last few weeks and isn't NixOS kind of the worst case?
Fastly (US company) is used as a CDN and AWS S3 (US company) as storage for the binary cache. If someone pulls the plug over a conflict, we can only resort to build without the main binary cache, but then a huge chunk of the source tarballs are fetched GitHub, so we are done anyway.
Most traditional Linux distros have European mirrors for everything.
-
want to help bring digital autonomy using #NixOS?
https://fediversity.eu is hiring (EU-based) developers!
we'll also be at #fosdem's #nix track next week.@kiara EU-only or would e.g. Switzerland also work?
-
@kiara EU-only or would e.g. Switzerland also work?
@das_g it depends - feel free to submit a brief application with this question!
-
@kiara I have been (over)thinking about tech sovereignty the last few weeks and isn't NixOS kind of the worst case?
Fastly (US company) is used as a CDN and AWS S3 (US company) as storage for the binary cache. If someone pulls the plug over a conflict, we can only resort to build without the main binary cache, but then a huge chunk of the source tarballs are fetched GitHub, so we are done anyway.
Most traditional Linux distros have European mirrors for everything.
@danieldk good question, thank you!
this concern is valid, and for workstations i think it's easier to prioritize this consideration.
on servers, i think there are different challenges.
a sysadmin for example would be likely to follow your considerations on this. for companies, that's great.for smaller non-technical users however, i think the (open-source) server software's need for systems admininistration makes for a technical barrier - or financial, if delegated.
this need derives from the fact that traditional distributions (and their wrapping containers) are not reproducible. any code you write, you cannot trust will build tomorrow, if today. this is a problem, since security updates, compatibility concerns if not features mean that life-cycle process is non-optional.
shifting such burden to nix addresses this. so nix's role in digital autonomy isn't getting sysadmins off certain infra, it's about bringing open-source closer.
-
@danieldk good question, thank you!
this concern is valid, and for workstations i think it's easier to prioritize this consideration.
on servers, i think there are different challenges.
a sysadmin for example would be likely to follow your considerations on this. for companies, that's great.for smaller non-technical users however, i think the (open-source) server software's need for systems admininistration makes for a technical barrier - or financial, if delegated.
this need derives from the fact that traditional distributions (and their wrapping containers) are not reproducible. any code you write, you cannot trust will build tomorrow, if today. this is a problem, since security updates, compatibility concerns if not features mean that life-cycle process is non-optional.
shifting such burden to nix addresses this. so nix's role in digital autonomy isn't getting sysadmins off certain infra, it's about bringing open-source closer.
for the record, to those interested in improving this situation for nixos, there is discussion on this at https://github.com/NixOS/infra/issues/939.
on getting source repos off github, hopefully they will take the hint as well. the forgefed effort may alleviate pain there a bit, tho for projects under nixpkgs size, i imagine the step to forgejo (e.g. codeberg) may be doable these days, with their compatible CI system.
-
@kiara I have been (over)thinking about tech sovereignty the last few weeks and isn't NixOS kind of the worst case?
Fastly (US company) is used as a CDN and AWS S3 (US company) as storage for the binary cache. If someone pulls the plug over a conflict, we can only resort to build without the main binary cache, but then a huge chunk of the source tarballs are fetched GitHub, so we are done anyway.
Most traditional Linux distros have European mirrors for everything.
@danieldk Would be much easier if we had proper retention policies (e.g. nothing older than 3y) and could fan out to multiple S3 stores. Luckily fanning out will become possible with the new queue-runner, so we just need to convince some people that funding an independent S3 bucket in the EU is worthwhile.
-
@danieldk Would be much easier if we had proper retention policies (e.g. nothing older than 3y) and could fan out to multiple S3 stores. Luckily fanning out will become possible with the new queue-runner, so we just need to convince some people that funding an independent S3 bucket in the EU is worthwhile.
@hexa All I can say is - that sounds great! Even just a little over 6 months (or since the last stable release) would probably be enough for most people.
-
@danieldk Would be much easier if we had proper retention policies (e.g. nothing older than 3y) and could fan out to multiple S3 stores. Luckily fanning out will become possible with the new queue-runner, so we just need to convince some people that funding an independent S3 bucket in the EU is worthwhile.
-
The option I favour is a selfhosted Garage S3 cluster on three Hetzner SX135 and backing that by another Fastly URL
https://www.hetzner.com/dedicated-rootserver/matrix-sx/
750 EUR/mo, 9k EUR/yr
-
N necrosis@chaos.social shared this topic
P pmj@social.pmj.rocks shared this topic
