Recent searches
Search options
#p2p
I think I finally have this thing complete - the paper is live hosted on a little test node, also lives as README.md on the GitHub.
https://idens.net/iden://z1HRUsTNcYMkN5WPm9s1YjGaLUVs58RVRHPjBrV1kYwdAJ.642/pub
Hello Jamers! 
Missed Dev Update #12?
No worries, we’ve got you covered with all the highlights! 
Catch up now and stay in the loop.
Read our Dev update 12: https://jami.net/de/dev-update-12/
I saw today that my CoCalc (https://cocalc.com/) license was about to renew. I've been meaning to move to a more #SelfHosting or #P2P paradigm, so this was good timing for me to cancel. I left this message when doing so:
"I want to support Sage, and I like using CoCalc, but I don't want to put money towards a service that supports Microsoft, Amazon, or OpenAI in any way. I didn't care so much about this before, and I even log in to CoCalc with a GitHub account, but I'm tired of having my work scraped for profit by people who donate to fascists who are destroying my nation. I would consider returning if all ties to these corporations were cut and cloud computing services came from responsible companies, perhaps in the EU."
I'm pretty sure I already have backups of everything I want from GitHub, so I can be done with them too. I should have quit when Microsoft first arrived. My plan is to switch to Radicle (https://radicle.xyz/) rather than another centralized service. I'll be sure to post about how that goes.
Hello hello Jamers 
Spring is back and so are our Dev Updates!
You missed them? We did too!
Our team has been busy squashing bugs, enhancing the user experience, and preparing some exciting new features for all Jami users. From desktop to mobile, and deep into the core, things are moving fast.
Curious to see what’s been cooking lately across platforms?
Read our Dev update 12 : https://jami.net/de/dev-update-12/
Save the Date
We're having another edition of #BoilingTheOcean on May 24th and 25th!
Join us for two days of hacking on low-level emancipatory tech in Berlin. Agenda, location, etc. TBA :)
Selhosted P2P E2EE File Transfer & Messaging PWA
* #OpenSource
* #CrossPlatform
* #PWA
* #iOS, #Android, #Desktop (self compile)
* App store, Play store (coming soon)
* Desktop
* #Windows, #MacOS, #Linux (self compile)
* run `index.html` on any modern #browser
* #Decentralized
* #Secure
* #NoCookies
* #P2P #encrypted
* No registration
* No installing
* #Messaging
* Group Messaging (coming soon)
* Text Messaging
* #Multimedia Messaging
* #Screensharing (on desktop browsers)
* Offline Messaging (in #research phase)
* #FileTransfer
* #VideoCalls
* #DataOwnership
* #SelfHosted
* GitHub pages Hosting
* #LocalOnly storage
Check it out!
https://positive-intentions.com
(Degoogled links to the apps)
- Chat: https://chat.positive-intentions.com
- File: https://file.positive-intentions.com
- GitHub: https://github.com/positive-intentions
Better maybe, but relying on European values and regulation carries risk. Look at UK, look at others in the EU, look at how well lobbying works against both.
Where possible we need to create infrastructure that embodies these freedoms and protections so they cannot be circumvented, to give alternatives when other options begin to fail. Thid can be done through tech which empowers, such as decentralisation through #p2p rather than #fedi.
@TheProgressives
I have made a release of "git-withme" which allows peer-to-peer Git usage over #magicWormhole
This uses short, human-memorable codes to invite peers to collaborate (push, pull, etc) in real-time on a Git repository with no external hosting providers. Creates a temporary bare repository on the host so it feels like GitLab style usage.
"pip install git-withme" or see the project pages:
#PeerTube - Importation #YouTube, #transcodage #HLS avec support #P2P en 720p/1080p MP4/AAC, création des vignettes, le tout grâce à #FFMPEG
Après 
On supprime YouTube 
Mais avant, il y a encore toutes les vidéos sur #Emmabuntus et la clé magique 
in calmness > If i was designing a #P2P protocol
Bit of OT thought.. All these #LocalFirst projects are inventing their own sync mechanisms now, and Martin Kleppmann talks about trend towards having a 'generic sync' protocol as an open standard. But no moves are made yet in that direction.
I have trouble wrapping my head how that'd work in a heterogeneous social network with many actors, apps and composable services. Do we CRDT sync local states directly, or rely on a msg/event-based architecture?
quoting myself, bittorrent is like the Hegel of #P2P, it is the simplest protocol i am aware of that is quite literally just the core of the idea as a spec and then decades of history, culture, and practice crusted on top of it. hashes of chunks of data overlaid on top of the data itself to facilitate sharing it. that's it. i am a peer. i have heard of some data via its hash. i ask around for that data. i get it and check it against the hash. end of algorithm. Yes yes, choking algorithms, trackers, transport protocols, holepunching, but that's implementation details.
You can't think about P2P without taking some implicit or explicit disposition towards bittorrent because it's such a pure expression of the idea. An analogous argument is that you can't really implement a P2P protocol without accidentally making it in some way (maybe through a few steps) compatible with bittorrent. v2 makes that bar almost zero by just being literally a set of per-file merkle trees. you can just ignore the .torrent file entirely and deal with the trees directly, all you need to do is understand when someone asks for hashes at a specific level of the tree.
If i was designing a P2P protocol, which i always am in some part of my being, I would start from bittorrent v2 and branch out from there. Being able to talk to a bittorrent client is so trivial it's almost an afterthought, an afternoon of writing udp packing and unpacking functions. If you ignore the rest of the lessons like the obvious UX affordance of having a thing to trade around like .torrent files, magnet links which are an identifier and a non-definitive starting point for resolving it, trackers which are a means of coordinating the swarm, you're just throwing away an entire generation of practical experience
After some hiatus, @Jami is back on #Flathub, an easy way to have it on any Linux distro. If you miss the #p2p days of Skype, Jami is here - https://jami.net/jami-vs-skype-welcome-to-where-your-privacy-matters/ #GNU, #FOSS, #Decentralization, #DistributedSystems
Colaboração ponto a ponto (peer-to-peer) com o LibreOffice
Há algum tempo, Simon Phipps, membro do Conselho de Administração da The Document Foundation, compartilhou a ideia de introduzir a colaboração ponto-a-ponto (peer-to-peer) incorporada ao desktop LibreOffice sem a necessidade de um provedor de nuvem. Essa ideia recebeu muita atenção dentro da organização e a equipe de design começou a delinear o projeto agora.
Ce que m'évoque l'irruption de machins générés d'après le style #ghibli
Is digital piracy ethically justifiable?
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/
@gvwilson I would go a step beyond #federation and suggest that the solution for hosting the world’s #OpenSource should be a #peerToPeer one.
#p2p means even individuals can “seed” content they want to maintain on the network, so when institutions get shut down, individuals - in their numbers - can take action.
But then again, I work on @radicle , so I’m clearly biased! ;)
There is also https://github.com/n0-computer/iroh-willow which is under construction and based on the #Willow protocol. This is also a foundational #p2p technology, which received funding by @nlnet under the EU Horizons #NGI0 programs, to evolve their specifications.
Willow contains among others a specification for support of object capabilities, called Meadowcap, which is very interesting.
https://willowprotocol.org/specs/meadowcap/index.html#meadowcap