home.social

#radicle — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #radicle, aggregated by home.social.

  1. This says rns.recipes/forum/general/re-d #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

  2. This says rns.recipes/forum/general/re-d code is to be taken off or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using as a robust meshed git repo system & so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the code over reticulum itself seem not beginner-friendly.

  3. This says rns.recipes/forum/general/re-d #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

  4. This says rns.recipes/forum/general/re-d #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

  5. This says rns.recipes/forum/general/re-d #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

  6. Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

  7. I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.

    #TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.

    I also read a very important blog post for me there: "combat LLM spam by building a web of trust" blog.tangled.org/vouching/ .

  8. The prolonged attack on servers is affecting updates. I’ve been wondering whether a system like could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

  9. #Sydbox is on #Radicle with ID rad:z38HCnbmcDegA2BMxuPaPRPMdp6wF seed it and share the love! Huge thanks to #HardenedBSD folks for seeding! #exherbo #linux #security #git

  10. Lorenz Leutgeb: We got a new release of cypheraddr a few days ago, and I just rebased Patches > ec8bf7a2: #I2P Support. I encourage all the I2P enthusiasts to try it out ASAP, so that we can hopefully get some feedback before the next release from y'all.

    radicle.zulipchat.com/#narrow/

    #Radicle

  11. I was using with to play with and it became a bit of a mess, to say the least, for what I was trying to do. By accident my radicle server lost power & I had to restart & lost my claude session. So I took the opportunity to claude to and used github.com/ryoppippi/claude-co too in my . The results were astounding. The updated claude code explained the problem correctly (I had guessed what the issue was) & fixed it in minutes. Super.

  12. Anyone using to manage a “mother flake” across multiple machines?
    I’m trying to confirm something: since Radicle is built on , does rad init still leave you with a normal .git working tree that nixos-rebuild switch --flake . is happy with?
    Or does Nix require a standard Git repo and can’t treat a rad://… repo as a flake input without an HTTP/SSH Git mirror? If you do this or similar, what’s your actual workflow?

  13. Йа таки не втримався не грішити #P2P на заряді від акумулятора і запердолив свій #gemlog на #Radicle: https://app.radicle.xyz/nodes/iris.radicle.xyz/rad%3Az4FoMnoSve6Ku6gz4qiuSpzmGr1YE

    Додатково, оновив гайд, виправивши там приклади команд і доповнивши зауваженнями з перевареного часом досвіду:
    https://devzone.org.ua/post/radicle-detsentralizovanyy-p2p-khostynh-gitdvcs

  14. 🥳 Behold! Radicle: the revolutionary, sovereign, decentralized, peer-to-peer, blockchain-inspired, Git-based utopia that nobody asked for! 🤔 Because who doesn't want to spend hours running obscure shell commands just to avoid the tyranny of those dastardly centralized platforms? 🎉 Just don't forget your repository ID: #randomstringofgibberish.
    radicle.xyz #Radicle #Decentralization #Blockchain #Git #PeerToPeer #OpenSource #HackerNews #ngated

  15. @momo works! is an easy way to ensure you have all files of interest available even in aeroplane mode, because the repositories you chose to follow are stored locally & automatically kept at their most recent version from when you were last online. Easy setup. Practical for dev ops (systems that keep working when web is unreliable or services disappear). repoducible.org (app.radicle.xyz/nodes/radicle. /features/radicle) has a part example for setup.

  16. Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

    I mean, I don't care for your 5 person project, do what you want.

    But for large projects, that really is the only way to develop that truly scales.

    Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

    That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

    #git #github #shithub #gitlab #shitlab

  17. Finally I found some time to continue work on the #unsynn #rust #crate. Lots new features coming:

    * quote!() somewhat different flavor than quote::quote.
    * format_*!() macros for constructing tokens by format strings.
    * the unsynn!() macro got a lot work:
    * type generics, attributes, are supported now
    * ergonomic syntax extension for 'impl'
    * pass-trough for some rust code
    * a transform module with parsers that can modify the AST on the fly

    I hope I can stabilize this soon an make a 0.2 release. Along this i am working (non released) on the unsynn-rust crate which is the grammar/parser for rust. Things are starting to work there as well.

    We are also moved to #radicle the gitea will eventually be phased out.

    seed.pipapo.org/nodes/seed.pip got replaced by
    seed.pipapo.org/nodes/seed.pip

  18. I'm finally moving over to Radicle (radicle.xyz) instead of switching to another centralized code forge (like GitHub, GitLab, Codeberg, etc.). I definitely love the idea behind a #P2P code forge and I'm hopeful for Radicle's future, but I do have some reservations starting off:

    1) Despite talking a lot about freedom and privacy in the tutorial, the group building Radicle (radworks.org/) is planning to sell hosting and make a profit via an Ethereum-based cryptocurrency (tally.xyz/gov/radworks) as well as NFTs and smart contracts. Some big Libertarian red flags there.

    2) At some point there was a Swiss nonprofit "Radicle Foundation", but this now seems to be a for-profit venture (see radicle.xyz/history). I wish it could just be a nonprofit.

    3) In the user guide chapter on private repos (radicle.xyz/guides/user), it says that I need to use a public DNS address trusted seed node to share the repo. I understand there's no DHT here, but I hope it's not too much of a pain to run this over my local network instead of the internet. (And yeah, I know I can use git locally, I just want to test Radicle locally.)

    Overall, I think that if radworks turns out to be evil it will be a way easier transition to fork Radicle than it has been to leave GitHub, but I still wish I didn't have to worry.

    #Programming #CodeForge #Radicle #GitHub #GitLab #Codeberg #FOSS #FreeSoftware #VersionControl #crypto #Cryptocurrency #NFT #DAO #SmartContract #Ethereum #Libertarian