#radicle — Public Fediverse posts

@dazo @lattera Which is fine as I actually WANT all my nixos closure downloads to be kept locally for resilience... so I can see a #nixos cache seed for my flake having to take shape on a machine in my lan .... very very interesting project #radicle. And I can see that finding the rad key/hash thingy I needed on a different URL seems not to be a solved problem.

@dazo @lattera Which is fine as I actually WANT all my nixos closure downloads to be kept locally for resilience... so I can see a #nixos cache seed for my flake having to take shape on a machine in my lan .... very very interesting project #radicle. And I can see that finding the rad key/hash thingy I needed on a different URL seems not to be a solved problem.

@dazo @lattera Which is fine as I actually WANT all my nixos closure downloads to be kept locally for resilience... so I can see a #nixos cache seed for my flake having to take shape on a machine in my lan .... very very interesting project #radicle. And I can see that finding the rad key/hash thingy I needed on a different URL seems not to be a solved problem.

@dazo @lattera Which is fine as I actually WANT all my nixos closure downloads to be kept locally for resilience... so I can see a #nixos cache seed for my flake having to take shape on a machine in my lan .... very very interesting project #radicle. And I can see that finding the rad key/hash thingy I needed on a different URL seems not to be a solved problem.

@dazo @lattera Which is fine as I actually WANT all my nixos closure downloads to be kept locally for resilience... so I can see a #nixos cache seed for my flake having to take shape on a machine in my lan .... very very interesting project #radicle. And I can see that finding the rad key/hash thingy I needed on a different URL seems not to be a solved problem.

@lattera Just a question as it seems you really use this repo tooling for real: how does an install use a #radicle repo without failing e.g. because the seed that provides the URL used is down, but others are available with that repo but have a different URL ? Cheers.

@lattera Just a question as it seems you really use this repo tooling for real: how does an install use a #radicle repo without failing e.g. because the seed that provides the URL used is down, but others are available with that repo but have a different URL ? Cheers.

@lattera Just a question as it seems you really use this repo tooling for real: how does an install use a #radicle repo without failing e.g. because the seed that provides the URL used is down, but others are available with that repo but have a different URL ? Cheers.

@lattera Just a question as it seems you really use this repo tooling for real: how does an install use a #radicle repo without failing e.g. because the seed that provides the URL used is down, but others are available with that repo but have a different URL ? Cheers.

@lattera Just a question as it seems you really use this repo tooling for real: how does an install use a #radicle repo without failing e.g. because the seed that provides the URL used is down, but others are available with that repo but have a different URL ? Cheers.

Day three on #radicle in progress.

Things learned:

- if you want search functionality via radicle-httpd API, you need radicle-search and Meilisearch installed and configured.
- if you use a static allow list, you need to have clients in the allow list too

This was discovered by examining code and binaries, I could not find the actual documentation for this on the radicle website. 😵‍💫

Day three on #radicle in progress.

Things learned:

- if you want search functionality via radicle-httpd API, you need radicle-search and Meilisearch installed and configured.
- if you use a static allow list, you need to have clients in the allow list too

This was discovered by examining code and binaries, I could not find the actual documentation for this on the radicle website. 😵‍💫

Day three on #radicle in progress.

Things learned:

- if you want search functionality via radicle-httpd API, you need radicle-search and Meilisearch installed and configured.
- if you use a static allow list, you need to have clients in the allow list too

This was discovered by examining code and binaries, I could not find the actual documentation for this on the radicle website. 😵‍💫

And my first #radicle seeder is live

https://radicle.network/nodes/seed.wowemu.dev

If you are interested in #worldofwarcraft emulation, specifically for the modern Classic clients, bookmark this.

And my first #radicle seeder is live

https://radicle.network/nodes/seed.wowemu.dev

If you are interested in #worldofwarcraft emulation, specifically for the modern Classic clients, bookmark this.

And my first #radicle seeder is live

https://radicle.network/nodes/seed.wowemu.dev

If you are interested in #worldofwarcraft emulation, specifically for the modern Classic clients, bookmark this.

And my first #radicle seeder is live

https://radicle.network/nodes/seed.wowemu.dev

If you are interested in #worldofwarcraft emulation, specifically for the modern Classic clients, bookmark this.

And my first #radicle seeder is live

https://radicle.network/nodes/seed.wowemu.dev

If you are interested in #worldofwarcraft emulation, specifically for the modern Classic clients, bookmark this.

Next #homelab adventure for me: I will be migrating from #forgejo to #radicle for reasons:

- the web interface is useless for someone like me who basically lives in a tmux shell
- running a node / seeder and selective seeding to backup nodes is a dead easy backup compare to Forgejo dumps
- the fact Radicle supports a full terminal only workflow is just sweet

Bonus points for the web interface style.

Next #homelab adventure for me: I will be migrating from #forgejo to #radicle for reasons:

- the web interface is useless for someone like me who basically lives in a tmux shell
- running a node / seeder and selective seeding to backup nodes is a dead easy backup compare to Forgejo dumps
- the fact Radicle supports a full terminal only workflow is just sweet

Bonus points for the web interface style.

Next #homelab adventure for me: I will be migrating from #forgejo to #radicle for reasons:

- the web interface is useless for someone like me who basically lives in a tmux shell
- running a node / seeder and selective seeding to backup nodes is a dead easy backup compare to Forgejo dumps
- the fact Radicle supports a full terminal only workflow is just sweet

Bonus points for the web interface style.

Next #homelab adventure for me: I will be migrating from #forgejo to #radicle for reasons:

- the web interface is useless for someone like me who basically lives in a tmux shell
- running a node / seeder and selective seeding to backup nodes is a dead easy backup compare to Forgejo dumps
- the fact Radicle supports a full terminal only workflow is just sweet

Bonus points for the web interface style.

Next #homelab adventure for me: I will be migrating from #forgejo to #radicle for reasons:

- the web interface is useless for someone like me who basically lives in a tmux shell
- running a node / seeder and selective seeding to backup nodes is a dead easy backup compare to Forgejo dumps
- the fact Radicle supports a full terminal only workflow is just sweet

Bonus points for the web interface style.

One nice thing about #radicle & #reticulum is that I can switch off my servers running a reticulum backbone (reticulum.me is off ; but reticulorum.net is still up on Hetzner) or radicle seed (repoducible.org is off in August as it runs on a laptop with a battery and I'd rather not leave it alone) when going on holiday or doing maintenance & not worry that you are breaking some infrastructure. They are self-healing: the same service or task will be available in/via another corner of the mesh.

One nice thing about #radicle & #reticulum is that I can switch off my servers running a reticulum backbone (reticulum.me is off ; but reticulorum.net is still up on Hetzner) or radicle seed (repoducible.org is off in August as it runs on a laptop with a battery and I'd rather not leave it alone) when going on holiday or doing maintenance & not worry that you are breaking some infrastructure. They are self-healing: the same service or task will be available in/via another corner of the mesh.

One nice thing about #radicle & #reticulum is that I can switch off my servers running a reticulum backbone (reticulum.me is off ; but reticulorum.net is still up on Hetzner) or radicle seed (repoducible.org is off in August as it runs on a laptop with a battery and I'd rather not leave it alone) when going on holiday or doing maintenance & not worry that you are breaking some infrastructure. They are self-healing: the same service or task will be available in/via another corner of the mesh.

One nice thing about #radicle & #reticulum is that I can switch off my servers running a reticulum backbone (reticulum.me is off ; but reticulorum.net is still up on Hetzner) or radicle seed (repoducible.org is off in August as it runs on a laptop with a battery and I'd rather not leave it alone) when going on holiday or doing maintenance & not worry that you are breaking some infrastructure. They are self-healing: the same service or task will be available in/via another corner of the mesh.

One nice thing about #radicle & #reticulum is that I can switch off my servers running a reticulum backbone (reticulum.me is off ; but reticulorum.net is still up on Hetzner) or radicle seed (repoducible.org is off in August as it runs on a laptop with a battery and I'd rather not leave it alone) when going on holiday or doing maintenance & not worry that you are breaking some infrastructure. They are self-healing: the same service or task will be available in/via another corner of the mesh.

Just heard of #radicle last week from @abynox
I find this project really cool and decided to make a quick docker setup for it which aims to be easy to self host. Primarely to act as a seed for your own repos. The idea is to have a seed which you can use to feature all the repos you like. It works by periodically checking which repos your personal node seeds and then it also seeds them: https://app.radicle.at/nodes/seed.radicle.at/rad:z4UyBodrr8XMw5rKqsToLdY2Xd3mM

More information about radicle: https://radicle.xyz

Just heard of #radicle last week from @abynox
I find this project really cool and decided to make a quick docker setup for it which aims to be easy to self host. Primarely to act as a seed for your own repos. The idea is to have a seed which you can use to feature all the repos you like. It works by periodically checking which repos your personal node seeds and then it also seeds them: https://app.radicle.at/nodes/seed.radicle.at/rad:z4UyBodrr8XMw5rKqsToLdY2Xd3mM

More information about radicle: https://radicle.xyz

radicle.network seems to be blocked by default when visiting radicle.network pages with Malwarebytes Browser Guard enabled.

#radicle

radicle.network seems to be blocked by default when visiting radicle.network pages with Malwarebytes Browser Guard enabled.

#radicle

radicle.network seems to be blocked by default when visiting radicle.network pages with Malwarebytes Browser Guard enabled.

#radicle

radicle.network seems to be blocked by default when visiting radicle.network pages with Malwarebytes Browser Guard enabled.

#radicle

radicle.network seems to be blocked by default when visiting radicle.network pages with Malwarebytes Browser Guard enabled.

#radicle