specs
plebbit-js
specs | plebbit-js | |
---|---|---|
17 | 9 | |
1,492 | 38 | |
0.5% | - | |
6.5 | 9.9 | |
11 days ago | 4 days ago | |
TypeScript | ||
- | 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
plebbit-js
-
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
-
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
-
plebbit - Bi-Weekly updates - Weeks 6-7, 2022-03-25 - 2022-04-08
Continued working on the implementation of Plebbit's backend, including rigorous tests for each functionality.
-
Plebbit Weekly updates - Weeks 4-5
Continued working on finalizing the design for Plebbit's APIs, including the mod API. Our final aim is to recreate reddit exactly, then expand to different types of clients, for example that look like 4chan or discourse, all using the same underlying protocol and all interoperable. The underlying data and protocol is completely open, so you can display the data any way you want to your users.
-
Plebbit Weekly Updates - Week 3
Updating code in plebbit-js to follow design as specified by README.md
-
This dude made an alternative Reddit on a blockchain. Crazy
https://github.com/plebbit/plebbit-js -> "wrap around the IPFS APIs used by Plebbit."
-
Doing some looking into this project help needed.
Check the github for development progress
- Track development of Plebbit here
What are some alternatives?
tribler - Privacy enhanced BitTorrent client with P2P content discovery
whitepaper
py-ipv8 - Python implementation of Tribler's IPv8 p2p-networking layer
Cacophony - An experimental video sharing platform on top of IPFS
komodo-wallet-desktop - Komodo Wallet Desktop GUI
plebbit-cli - An interface to Plebbit API through command line
xmr-btc-swap - Bitcoin–Monero Cross-chain Atomic Swap
web3.storage - DEPRECATED ⁂ The simple file storage service for IPFS & Filecoin
komodo-defi-framework - This is the official Komodo DeFi Framework repository
nft.storage - 😋 NFT.Storage Classic (classic.nft.storage) offers free decentralized storage and bandwidth for NFTs on IPFS and Filecoin. April 2024 Update: Existing NFT.Storage Classic account holders can add data through their Classic accounts. New account holders can transition to the new version at NFT.Storage that preserves data in Filecoin for a small fee.
Mastodon - Your self-hosted, globally interconnected microblogging community