Recent searches
Search options
#p2p
24 posts23 participants5 posts today
Before BitTorrent and even before LimeWire took off, there was AudioGalaxy. It was the unsung hero of peer-to-peer music discovery in the early 2000s, offering remote searching, smart filtering, and community-curated playlists. The RIAA inevitably came knocking, but those who used it still remember it as one of the slickest, smartest sharing tools of its era.
Unlike Napster, AudioGalaxy leaned heavily on decentralized file sharing, letting users build enormous libraries across connected systems. It quietly shaped how future services would think about music discovery and sharing.
Seekee App: Die neue Suchmaschine für Serien- und Filmfans
#Filesharing #Streaming #Datenschutz #p2p #Seekee #StreamingAlternativen #TorrentApps https://sc.tarnkappe.info/ebd0b9
TARNKAPPE.INFO · Seekee App: Die neue Suchmaschine für Serien- und FilmfansWie sicher ist Seekee? Wir werfen für euch einen Blick auf die neue und kostenlose Torrent-Such-App für Serien- und Film-Junkies.
#stigmerge update!
The stigmerge-peer crate has been heavily refactored into an actor-based architecture, a very CSP-like design with supervisors. i have a strong aversion to frameworks, so I implemented my own model inspired by https://ryhl.io/blog/actors-with-tokio/.
I still need to implement much of that advice.. Deal with backpressure, etc. but...
Last night I sent a file through successfully with share announcer, resolver, seeder and fetcher actors!
Hoping for a new major version release in the next couple of weeks. It will likely be a protocol and CLI breaking change.
ryhl.ioActors with Tokio – Alice RyhlThis article is about building actors with Tokio directly, without using any actor libraries such as Actix. This turns out to be rather easy to do, however there are some details you should be aware of:
@radicle looks like an interesting Free Software to check out: it’s a peer-to-peer, local-first git forge for the decentralized Web! 
#Radicle #p2p #DWeb #decentralization #decentralized #git #gitForge #software #FreeSoftware #openSource #localFirst
radicle.xyzRadicleSovereign code infrastructure.
starting out with #Radicle
if you know good repos to seed, hit me up!
radicle.xyzRadicleSovereign code infrastructure.
Replied in thread
@cunyxa , лучше #aTox (Тох-клиент для #Андроид)? Этот тоже #P2P, текстовые сообщения в офлайн ставятся в очередь и когда оба в Сети - делается доставка. По-моему, #Tox распространён даже немного лучше, чем #Jami(?) E-mail и номер телефона тоже не просит. Но в свете последних событий (#РКН) всё же выбрал #Signal - как зарегаться теперь там и другие подробности: https://tinyurl.com/signalpm (9kb, txt)
Today’s fellow for #DWebFellowFriday is Taslim Oseni!
Taslim is a software engineer who contributed to the development of #CenoBrowser, a #DWeb browser built to bypass censorship using #p2p technologies.
Check out Taslim’s talk about it @ DWeb Camp 2024: https://archive.org/details/taslim-presentation
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
idens.netIDEN 0.1.0 PaperIDEN is a lightweight decentralized identity and publishing platform. It provides a small, efficient foundation for building distributed, coordinated systems around self-generated identities. An `iden` serves as a portable, public address—readable by anyone, writable only by its owner. At its cor...
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.
cocalc.comCollaborative Calculation and Data ScienceCoCalc landing pages and documentation
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 :)
I'm now going through a loop of reading text and trying to recognize what actually needs to be stated somewhere that I'm used to just thinking of as implied. ~4,500 words in and I realize that I never actually explicitly expressed that the system was designed to be able to function in an extended #P2P environment or how the basic mechanisms work in that context. That was just the basic environment my thinking started in, but it just occurred to me to mention it to the hypothetical reader.
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
Replied in thread
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:
Replied to jonny (good kind)
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?
Continued thread
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
Neuromatch Socialjonny (good kind) (@jonny@neuromatch.social)(Also obviously I am eliding all the other decisions bittorrent makes that make that possible and ways that it doesnt work. trackers are a great idea both technically and socially, even if the tracker model is direly in need of an update. Trackers are nucleating hubs that make recognizable communities, end user search systems, and reduce the complexity of peer routing by a billion times. Omitting another hundred pages on the sociotechnological economy of bittorrent, but bittorrent is like the Hegel of p2p - you can't do p2p without reconciling your disposition towards bittorrent)