Dutch governments builds alternative for Microsoft based on NixOS
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Dutch governments builds alternative for Microsoft based on NixOS
Unofficial Hacker News client; not affiliated with Y Combinator.
ricardobeat · · focus · HN ↗
[1] <a href="https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html" rel="nofollow">https://blog.codeberg.org/protecting-our-floss-commons-from-...
gagik_co · · focus · HN ↗
edit: looks like this was originally the case and then they moved?
utopiah · · focus · HN ↗
embedding-shape · · focus · HN ↗
- <a href="https://codeberg.org/forgejo/forgejo/issues/59" rel="nofollow">https://codeberg.org/forgejo/forgejo/issues/59 ("[FEAT] implement federation")
- <a href="https://forgefed.org/" rel="nofollow">https://forgefed.org/
athrowaway3z · · focus · HN ↗
We can do big federated/distributed development with git at the project level. See the linux kernel.
If the goal is fancy UI then there are alternatives.
If the goal is to do a big multi-git with cross repo issue tracker, then that implies either:
- you're a public site for random repos like codeberg
- you're a special purpose forge and identity management is a big issue you want full control over.
IMO - For this to work, they should go with the latter and not try to offload identity into some federated scheme.
xvilka · · focus · HN ↗
[1] <a href="https://radicle.dev/" rel="nofollow">https://radicle.dev/
[2] <a href="https://tangled.org/" rel="nofollow">https://tangled.org/
embedding-shape · · focus · HN ↗
Radicle seems better in that regards, but instead is on top of their own cryptocurrency, which comes with its own issues.
Personally my best hope is still "real" federation across centralized services, ala ForgeFed, but ideally we can make all these approaches interoperate in the future, that would be really awesome.
iamnothere · · focus · HN ↗
embedding-shape · · focus · HN ↗
I think the notion persists because they are seemingly still using a DAO as the governance structure, so the organization sits on top of a cryptocurrency (is the idea of DAOs at least, in practice it isn't always so).
iamnothere · · focus · HN ↗
poulpy123 · · focus · HN ↗
amiga386 · · focus · HN ↗
It amuses me that Mastodon Central uses corpo-friendly labels for the sites they won't federate with, e.g. (<a href="https://mastodon.social/about" rel="nofollow">https://mastodon.social/about)
Whereas the more free-wheeling sites, like the ones Mastodon Central blocks, tell it exactly how it is: (<a href="https://tsundere.love/about" rel="nofollow">https://tsundere.love/about)fc417fc802 · · focus · HN ↗
numpad0 · · focus · HN ↗
You'd think "no lolis" would be reasonable. It falls apart when people look 14 into 50s, to you and your local police, but not to themselves.
Akronymus · · focus · HN ↗
mitxela · · focus · HN ↗
Where did we get this idea that federated instances should never block anything? Even warez sites have rules.
amiga386 · · focus · HN ↗
I'm not sure, but the OP was postulating that Forgejo instances could federate to solve the problem that the Dutch government runs its own instance to develop its software (including using AI extensively) but wants to engage with the wider community so is currently hosting things on Codeberg's centralised instance of Forgejo, and Codeberg's administrators hate AI.
Adding federation doesn't solve that problem, it just moves it one level up. To collaborate with the Dutch government, you either need to directly register on their site, or set up an entire copy of Forgejo, publicly hosted, so you can federate your one-user instance with them, or you need to find a different instance that someone else hosts, and be at the mercy of that instance's admins, who may be even more cruel and capricious than Codeberg's.
What I predict is a future codeberg.org/about saying
And a future code.overheid.nl/about being full of dodgy Forgejo instances that host porn gamesmitxela · · focus · HN ↗
They don't care if someone wastes their own resources.
amiga386 · · focus · HN ↗
Mastodon servers defederate because the people (or rather, the admins) of instance A don't want anything to do with the people (who toot at the discretion and policies of the admins) of instance B.
Codeberg's AI position, as stated and voted upon, does not mention resource usage at all. That's completely invisible from the discussion. It is exclusively argued against on accord of 1) unclear copyright ownership, and 2) users have no idea what's in the code, therefore it could be full of security flaws or harmful code.
<a href="https://codeberg.org/Codeberg/org/pulls/1253" rel="nofollow">https://codeberg.org/Codeberg/org/pulls/1253
So they would not want to federate with another host that used a lot of AI-generated code, even if it claimed an open license, even if that federation caused little-to-no usage of their CI. They would fundamentally disagree with any other instance that allowed mostly-AI-generated projects. They would therefore block such instances, if federation was a thing.
mitxela · · focus · HN ↗
iamnothere · · focus · HN ↗
The Fediverse has the whole model backwards as a result of its design. Either individuals need to run their own instances, or identity needs to be completely ephemeral and flow through many servers as it does in Nostr. A Nostr admin can choose not to host data from a given identity, they could even use an identity whitelist, but users normally subscribe to multiple relays. In the end, the data gets through, while the relay admin can keep their own hands clean if they have a problem with the data.
Note that having this freedom does not preclude you from voluntarily signing up for blocklists. But this is an active choice, and it can’t be suddenly imposed on a set of users.
mitxela · · focus · HN ↗
iamnothere · · focus · HN ↗
If I want to, I can opt in to any number of spam blocklists. That’s kind of the point—it’s opt in.