Cradicle the p2p github alternative (based on Radicle) is looking for users/testers

I proposed this project to improve on Radicle’s p2p model by using Tor for universal, straightforward seeding of git repos.

Original discussion thread - https://bounties.monero.social/posts/207/

One of the project’s git repos linked in that thread - https://radicle.network/nodes/iris.radicle.network/rad:z2ydYmUCJvDfNFTVTpEbQmm55EPt1/history

Project website - https://cradicle.xyz

The dev who took the project also expanded it into a project to reimplement Radicle in C.

Since I’m not a coder and I don’t have any git repos of my own, I can only test from the viewpoint of an average layman using the GUI app to seed repos.

It’s impossible for me to properly gauge how the project is progressing without engagement from coders who try using it for their git repos.

If the project doesn’t currently interest you, your suggestions on how to start getting users on board would also be welcome.

https://barghest.asia/work/mesh/

#mesh
#privacy
#censorship
#p2p
#fdroid

**First entry into RetroShare: how to find peers**

In RetroShare you don’t “find people” in the usual sense. You don’t search — you agree. This is a fundamental mindset shift; without it, the first launch will always feel empty.

The first thing to accept: there is no global lobby in RetroShare. The emptiness after installation is not a bug, but the honest state of a network without links. Until you have trusted contacts, you literally have no network.

**The basic method — out-of-band contact.**
Peers are found outside RetroShare. These are friends, colleagues, members of thematic communities, people from Matrix, XMPP, IRC, Mastodon, forums — any place where key exchange can happen safely. RetroShare does not start with a “search” button, but with the phrase: “here is my key.”

**The second path — a control peer.**
The most reliable way for first entry is a second instance you control, or a pre-arranged experimental partner. This removes uncertainty: if the connection fails, the issue is technical, not social.

**The third path — thematic islands.**
There are small RetroShare communities built around ideas: privacy, P2P, darknet research, offline activism. They are not widely advertised because the network is not designed for random influx. Entry always starts with dialogue, not a click.

**What does not work.**
Publishing keys into the void. Waiting for someone to add you. Relying on auto-discovery. This is centralized-network thinking applied to a system where it has no meaning.

**How to know you’ve found a peer.**
The contact comes online. The connection stabilizes. Services start working: chat, forums, file exchange. At that point RetroShare stops being an abstraction and becomes an environment for communication.

**Bottom line:**
in RetroShare, people appear first —
and only then does the network emerge.

#RetroShare #P2P #Decentralization #Privacy #MeshNetworks #FOSS #CyberSecurity #DigitalRights #AnonymousNetworks #OfflineCommunication #KeyExchange #FediverseAdjacent #PeerToPeer #SecureComms #InternetArchitecture

git-bug is a standalone, distributed, offline-first issue management tool that embeds issues, comments, and more as objects in a git repository (not files!), enabling you to push and pull them to one or more remotes.

https://github.com/git-bug/git-bug

#git #p2p

Gnutella: A Protocol Outlives the World That Created It

https://rickcarlino.com/notes/p2p/gnutella-explanation.html

#P2P #History #Networking

Post-Quantum key exchange in iroh? Thanks to the amazing #rustlang ecosystem and iroh depending on industry-stanard TLS used in a p2p-friendly way this is now possible: https://www.iroh.computer/blog/iroh-post-quantum-handshakes

#pqc #p2p #iroh

RE: https://chaos.social/@delta/116605626368696989

An inquiry that makes sense due to the #security and #privacy oriented character of #deltachat!

#IT #DM #chat #social #P2P

#WebRTC was barely #P2P before, and the general direction seems to be to bury the P2P aspect further.

From a technological standpoint, that's pretty depressing. It is definitely one of the coolest transport mechanisms the web got in the last 15 years. But a lot of interesting use cases were killed off by (IMO rather arbitrary) constraints or intentional implementation choices by Google

https://github.com/w3c/webrtc-pc/issues/3109

/cc @steely_glint