#p2p

See tagged statuses in the local BookWyrm community

📣Jami team is pleased to introduce the new version of Jami: Εἰρήνη.☮️

As you'll discover, this release brings remarkable advances from months of silent work, sure to delight loyal Jami users and newcomers after the announcement of Skype's shutdown.

We invite you to update and try the latest version of Jami! 🙇

👀 Want to know more about Εἰρήνη? Read our article : https://jami.net/eirene-to-make-new-user-onboarding-simple-and-intuitive/

Can somebody point me to some link, tutorial, example code, etc... for a application? I roughly understand how do they work, but I would prefer to see some basic code because some parts are like magic for me. What I plan to build is similar to a torrent client, but I don't understand how clients search each other and how do they connect to each other.

If you can point to some Python or C/C++ code, that would be awesome.

Mindful of recent developments in the world, is there any technology to distribute hosting, so the data is shared between many small peers around the world and requests to a site are load balanced across all or some of them and split over "safe" geographies? For common good sites like Wikipedia, The Internet Archive, that sort of thing?

Surely I'm not the only person to have thought of this 🤔 Boosts for reach gratefully received 🙏

Er det noen som har noen klar formening om hvorvidt det er greit å ha p2p-modusen til Peertube slått på som standard, med tanke på personvernslovgivningen? Det antydes jo på https://docs.joinpeertube.org/admin/privacy-guide at den bør være slått av, men jeg har aldri klart å slå meg helt til ro med dette. Det er jo en såpass fordel å ha det påslått, så da er det dumt hvis det ikke benyttes uten grunn.

Decentralizers, attention! :)

Last releases introduced stable group membership not found in any other messenger. Members can add/remove peers also while being offline, and when everything comes online again, everyone has the same consistent membership view. We formalized and ran a simulation model using + (invented by Leslie Lamport of vector clock fame):

https://github.com/chatmail/models/tree/main/group-membership

and a complementary model with more corner cases tested here:

https://github.com/chatmail/models/blob/main/gmc/test_gmc.py

Peer-to-Peer and the Promise of Internet Equality, Phil Agre, 2003

"The peer-to-peer movement understands that architecture is politics, but it should not assume that architecture is a substitute for politics. Radically improved information and communication technologies do open new possibilities for institutional change. To explore those possibilities, though, technologists will need better ideas about institutions."

https://pages.gseis.ucla.edu/faculty/agre/peer.html

Is there a good reference of scaling with more users/clients, servers, content exchange, network topology etc. What happens when everything and everywhere is connected?

Looking for a more or less rigorous *model* to compare and contrast with e.g., how and protocols scale (at least in theory) and put some mathematical meat behind the recent "message passing" vs "shared heap" discussions.

Have been looking for this with little success so time to

community milestones:

Dec 2023: first server

Feb 2024: iOS push notifications

March 2024: ETH Zuerich analysis

June 2024: Instant onboarding on all clients

Nov 2024: realtime and home-screen apps

Dec 2024: rPGP audit, 20 known servers world-wide

Jan 2025: new store, UI integrated app-picker, webxdc push notifications.

Spring 2025: is coming :)

money used: ~600K EUR, a tiny amount compared to other messengers.

Even before the arrival of was the question of what of the web means quite murky, with multiple competing protocols at different abstraction layers. As frequently said, at one level the web is already decentralized so envisaging pure is also conceivable, why the need for (or whatever) "servers"?

We come to realize that the problem is not well defined. First of all it does matter what you assume about the distribution of silicon and networks...

1/