specs
whitepaper
specs | whitepaper | |
---|---|---|
17 | 47 | |
1,492 | 151 | |
0.5% | -0.7% | |
6.5 | 5.2 | |
11 days ago | about 1 month ago | |
JavaScript | ||
- | GNU General Public License v3.0 only |
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.
specs
-
Filecoin Foundation Successfully Deploys IPFS in Space
The beauty of ipfs is the transport protocols are completely modular. They do a pretty good job supporting a lot of variety a separating concerns via https://github.com/libp2p/specs
-
BlockChain Engineers
For p2p networking, I'd say things are pretty interesting and boring at the same time. (Read: https://github.com/libp2p/specs if you're interested and decide for yourself)
-
Theseus DHT Protocol
At the bottom is the link to the more technical specification: https://github.com/libp2p/specs/blob/master/kad-dht/README.m...
-
Avoiding HTTP/3 (for a while) as a pragmatic default
The problems you described are specific to implementations, not the protocol itself. I have read all of the QUIC specs in full (since I'm working on an implementation) and have seen nothing in any of them that mandates a centralised certificate infrastructure (caveat: I have not read the HTTP/3 spec, perhaps you point out the relevant section if its in there). Of course, the most common use case requires this, but in that respect it's no different to HTTPS.
IPFS uses QUIC as one of its supported transport protocols, and this works in the most common implementation, Kubo [1]. The spec for the QUIC transport used in IPFS [2] indicates the same certificate trust policy as for the TLS protocol [3]. The latter, in turn, relies on peer-to-peer authentication with automatically-generated self-signed certificates and the use of an additional extension.
IPFS is particularly well suited to the use case of personal websites you've mentioned, as it's specifically designed to operate without any form of centralisation.
[1] https://github.com/ipfs/kubo.
[2] https://github.com/libp2p/specs/tree/master/quic
[3] https://github.com/libp2p/specs/blob/master/tls/tls.md
-
What about a Zig implementation of lib2p2?
Yes, there is already a Rust version (https://github.com/libp2p/rust-libp2p) that behaves well at this level but I think we can reach a higher level of performance on this point with Zig. Also, if you look at the long term roadmap of libp2p (https://github.com/libp2p/specs/blob/master/ROADMAP.md), the mobile devices and IoT integrations for example are part of the considerations.
-
IPFS Relay server
A standalone daemon that provides libp2p circuit relay services, for both protocol versions v1 and v2.
-
Does peer B (has access to the internet) help other peer A (who is behind the nat) to transfer data from peer C (has access to the internet) using ipfs?
Interestingly, that section also links to one about relay connections, which seems to be closely related to the original question: https://github.com/libp2p/specs/blob/master/relay/circuit-v2.md
-
Call HN: Decentralized Nat Hole Punching Measurement Campaign
Hi HN,
during December 2022, we are running a measurement campaign to investigate decentralized NAT hole punching success rates using the libp2p DCUtR protocol [0]. Ubiquitous peer-to-peer connectivity is still a big challenge. If successful, NAT Hole Punching can be a game-changer for decentralised applications and networks!
For that we are searching for participants who would run a lean client on their machines that performs hole punches with other peers and then reports back the results to our server. We explained the measurement methodology in this video [1] and the linked repository above.
Running such a client certainly has privacy implications which are documented here [2]. Most importantly, we record public IP addresses, successful NAT port mappings, and the login router page (to draw conclusions about which routers work better than others).
Optionally, you can also sign up here [3] and provide additional information about your personal network and receive a personal API key so that we can link your data to your information. Obviously, this has stronger privacy implications - but this is totally optional.
The most frictionless way to participate is to head to the releases page [4] and download a client that suits your platform and needs. No sign-up required.
[0] https://github.com/libp2p/specs/blob/master/relay/DCUtR.md
-
CCS Proposal: XMR-BTC Atomic Swaps GUI Desktop App - Continued development for 4 months
Rendezvous point: The rendezvous protocol is a lightweight mechanism for generalized peer discovery. It allows for the discovery of peers in a decentralized fashion. We operate a community rendezvous point through which swap providers can make themselves known to users, and through which users can find swap providers with whom they want to swap.(/dns4/discover.unstoppableswap.net/tcp/8888/p2p/12D3KooWA6cnqJpVnreBVnoro8midDL9Lpzmg8oJPoAGi7YYaamE)
-
This dude made an alternative Reddit on a blockchain. Crazy
It's not regular pubsub, it's "peer to peer pubsub". It's a pubsub, but p2p, anyone can join, subscribe, publish. The libp2p project has an implementation of this https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.0.md
whitepaper
-
Not trying to bring this or anyone down, But let's be honest, Lemmy sucks.
P2P by definition cannot be banned. For example no one can "ban" a user from download or uploading a file with bittorrent. We've been working on a fully P2P reddit alternative for 2 years, if you're interested in the design we have a whitepaper https://github.com/plebbit/whitepaper/discussions/2
-
Why Lemmy and Tildes are Doomed, and How You Can Prevent It
I've been working on a fully P2P reddit alternative that doesn't have "instances" that can block each other. Demo: https://plebbit-test.netlify.app Whitepaper: https://github.com/plebbit/whitepaper/discussions/2
-
We need a highly distributed alternative to Reddit that is beyond the ability of anyone to control and manipulate. Let our devices do the lifting whenever possible, somehow.
demo: https://plebbit-test.netlify.app/#/ whitepaper: https://github.com/plebbit/whitepaper/discussions/2
-
Aether, an open source P2P community board with mod elections and spam prevention
Plebbit seems to be a crypto 4chan idea of Reddit. From the FAQ
-
Switch to lemmy, its federated, privacy respecting reddit
Can't recommend Aether based on this discussion thread. Way too many hard sells listed for an unmaintained alternative. The latest forum thread even tells people to use a different platform, Plebbit (demo) (whitepaper), altogether.
-
Demo: Fully P2P and open source Reddit alternative we been workin on for 2 years
high level whitepaper: https://github.com/plebbit/whitepaper/discussions/2
the protocol is a light protocol over IPFS/IPNS/Libp2p Gossipsub
IPFS files (JSON/base64): https://github.com/plebbit/plebbit-js#schema
- Plebbit – Decentralized Reddit/4chan made with IPFS+ENS
-
Reddit may force Apollo dev and other third party clients to shut down
we have a high level whitepaper on our github https://github.com/plebbit/whitepaper/discussions/2
-
Which data is currently decentralized stored on IPFS?
For more info you can check the whitepaper https://github.com/plebbit/whitepaper/discussions/2 and also the upcoming design change for the mutable comment data https://github.com/plebbit/plebbit-js/issues/12
-
r/CryptoPunksDev Has Been Banned / Shutdown - Please, Help
Unrelated but we've been working on a P2P reddit alternative for more than a year, here's the whitepaper https://github.com/plebbit/whitepaper/discussions/2
What are some alternatives?
tribler - Privacy enhanced BitTorrent client with P2P content discovery
orbitdb.org - The website for OrbitDB
py-ipv8 - Python implementation of Tribler's IPv8 p2p-networking layer
Remmel
komodo-wallet-desktop - Komodo Wallet Desktop GUI
plebbit-js - A Javascript API to build applications using plebbit
xmr-btc-swap - Bitcoin–Monero Cross-chain Atomic Swap
RedReader - A SaidIt fork of RedReader, an unofficial open source Reddit client for Android
komodo-defi-framework - This is the official Komodo DeFi Framework repository
lemmy-ui - The official web app for lemmy.
0x-mesh - A peer-to-peer network for sharing 0x orders
voat - The code that powers Voat