multiaddr
Peergos
multiaddr | Peergos | |
---|---|---|
3 | 36 | |
416 | 1,887 | |
0.5% | 1.5% | |
2.8 | 9.4 | |
11 days ago | 5 days ago | |
Go | Java | |
MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
multiaddr
-
Filecoin Foundation Successfully Deploys IPFS in Space
> because, right here right now, that is such a hypothetical situation that I have absolutely no idea why it needs a real-world demonstration of proof of concept using currently-available technology.
So I just want to point out that IPFS was fairly deliberately designed to have numerous, forward-compatible features that could be swapped out in the future : like https://multiformats.io/ and in particular https://multiformats.io/multiaddr/ .
In the IPFS community, there's always been a fairly heated discussion about which bit of the entire system should be stuck with the term IPFS. Like, if you took away the libp2p protocol, and just served CIDs over http, would it be IPFS? What if you took away CAR files (the merkle-tree file format used to define multi-item content)? What if you're a private IPFS network, with no shared nodes with the public network (like https://github.com/TryQuiet/quiet ). What if you didn't use bitswap, the file transfer protocol (Filecoin doesn't use bitswap, and mostly doesn't interconnect with the main public IPFS network). What about if you didn't use a DHT to find providers of a CID. What if you're not using any of the "IPFS" software stack, but your implementation still uses bits and pieces of content-addressability as defined in the standard?
Interestingly, right now, there are a bunch of experiments going in all of these directions: I think it's fair to say that if you wanted to test out content-addressable networks across the solar system, they probably wouldn't be IPFS as it is now, but their nature could probably be described using the primitives the IPFS stack uses, and learning about what needs to change would give a useful direction to some part of the extended IPFS ecosystem.
-
TXT Flood
I'm not sure where they are coming from, but this looks like related to this project: https://github.com/multiformats/multiaddr
-
A mostly complete guide to hosting a public IPFS gateway
If you want people to be able to connect to your gateway via ipfs swarm connect /dnsaddr/ipfs.example.org, then you need to add some TXT records. You can type ipfs id to get the list of addresses associated with your node.
Peergos
-
S3 Is Showing Its Age
AWS SDK is huge yes, but you can implement an S3 client in 300 lines of Java.
https://github.com/Peergos/Peergos/blob/master/src/peergos/s...
-
Dropbox Sign Hacked
Would love to hear your thoughts on Peergos - https://peergos.org
https://github.com/peergos/peergos
-
Tim Bray's De-Google Project
A good Dropbox alternative is Peergos (founder here). Peergos is an E2EE P2P storage, sharing and application protocol. Fully open source, including the server, self-hostable, no VCs.
https://peergos.org
- Skiff Is Joining Notion
- I Moved My Blog from IPFS to a Server
- Filecoin Foundation Successfully Deploys IPFS in Space
- Peergos: A P2P, secure file storage, social network and application protocol
-
Amino – The Public IPFS DHT Is Getting a Facelift
You can do that with peergos [1]- mount a peergos folder locally using FUSE. Or login to the web interface and share easily and privately.
[1] https://github.com/peergos/peergos
-
The problem with federated web apps
You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.
You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.
This is the beauty of content addressing plus public key based addressing.
[0] https://peergos.org
-
Stop the proposal on mass surveillance of the EU
Totally agree! Shameless self promotion: have a look a Peergos - https://github.com/peergos/peergos
Our tech book might be a better starting point for this group: https://book.peergos.org
What are some alternatives?
ipfs-companion - Browser extension that simplifies access to IPFS resources on the web
slate - WIP - We're building the place you go to discover, share, and sell files on the web.
infra - Tools and systems for the IPFS community
CoreDB - Take back control of your data with a self-hosted network node for your digital identity. The IndiView app works with this node allowing you to share contact details, photos, and videos only with the people you specify.
ipfs-w3auth-gateway - A web3 authentication service on IPFS gateway
ipfs-chat - Real-time P2P messenger using go-ipfs pubsub. TUI. End-to-end encrypted texting & file-sharing. NAT traversal.
Go IPFS - IPFS implementation in Go [Moved to: https://github.com/ipfs/kubo]
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
ipfs-desktop - An unobtrusive and user-friendly desktop application for IPFS on Windows, Mac and Linux.
solid - Solid - Re-decentralizing the web (project directory)
skynet-cli - a lightweight cli to interact with Skynet
meshenger-android - P2P Voice/Video phone App for local networks.