@circfruit I think the releases now are only published over #rngit but not sure tho...
Seems that to share and/or use a #reticulum #rngit #git #repository immediately as similarly as possible to #Codeberg / #GitHub (know of it, find it, read it, obtain it) needs 3 prerequisites:
1) know of the repository somehow e.g. from a #nomadnet #page / #webpage / tip
2) running reticulum #rns >= 1.3.4
3) means to read nomadnet #pages (#Nomadnet , #MeshchatX .. )
& 3 pieces of info:
4) #repo address
5) repo nomadnet #URL / page address
6) #interface settings that give a sure route to 4.&5 1/3
@ProfessorBoop #rngit does seem interesting, but I haven't played around with it just yet. #Reticulum is likely to play a large role in the censorship- and surveillance-resistant mesh network I'm (slowly) cooking up.
@lattera Do you also use #rngit over #Reticulum?
This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #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.