home.social

#rngit — Public Fediverse posts

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

  1. @emd @Taffer Well I have my repo on #codeberg pushed from each branch; and identically (in a raid 1 cron job type arrangement LOL) to #rngit markqvist.github.io/Reticulum/

    and then also #radicle mirrors codeberg to keep one source of truth. This is just for resilience in case strange things happen....

  2. @emd @Taffer Well I have my repo on pushed from each branch; and identically (in a raid 1 cron job type arrangement LOL) to markqvist.github.io/Reticulum/

    and then also mirrors codeberg to keep one source of truth. This is just for resilience in case strange things happen....

  3. @emd @Taffer Well I have my repo on #codeberg pushed from each branch; and identically (in a raid 1 cron job type arrangement LOL) to #rngit markqvist.github.io/Reticulum/

    and then also #radicle mirrors codeberg to keep one source of truth. This is just for resilience in case strange things happen....

  4. @emd @Taffer Well I have my repo on #codeberg pushed from each branch; and identically (in a raid 1 cron job type arrangement LOL) to #rngit markqvist.github.io/Reticulum/

    and then also #radicle mirrors codeberg to keep one source of truth. This is just for resilience in case strange things happen....

  5. @emd @Taffer Well I have my repo on #codeberg pushed from each branch; and identically (in a raid 1 cron job type arrangement LOL) to #rngit markqvist.github.io/Reticulum/

    and then also #radicle mirrors codeberg to keep one source of truth. This is just for resilience in case strange things happen....

  6. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on . It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use & as a backup for Codeberg as it is flaky.

  7. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on #codeberg. It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested #nixos #flakes that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use #radicle & #reticulum #rngit as a backup for Codeberg as it is flaky.

  8. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on #codeberg. It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested #nixos #flakes that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use #radicle & #reticulum #rngit as a backup for Codeberg as it is flaky.

  9. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on #codeberg. It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested #nixos #flakes that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use #radicle & #reticulum #rngit as a backup for Codeberg as it is flaky.

  10. @tomgag I agree. Thanks for speaking up. There is much positive feedback about the move to ban LLM code on #codeberg. It risks strengthening liberal big tech by leaving it dominant. I use LLMs to help build tested #nixos #flakes that run my machines, yet I now worry my fleet setup processes using codeberg could be ruined by other's decisions. That is why dependence on large platforms is risky & this move has proven this. I use #radicle & #reticulum #rngit as a backup for Codeberg as it is flaky.

  11. Seems that to share and/or use a immediately as similarly as possible to / (know of it, find it, read it, obtain it) needs 3 prerequisites:
    1) know of the repository somehow e.g. from a / / tip
    2) running reticulum >= 1.3.4
    3) means to read nomadnet (#Nomadnet , .. )
    & 3 pieces of info:
    4) address
    5) repo nomadnet / page address
    6) settings that give a sure route to 4.&5 1/3

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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.

  17. 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.

  18. 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.

  19. 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.

  20. 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.