protocol
rebased
Our great sponsors
protocol | rebased | |
---|---|---|
12 | 1 | |
1,736 | 42 | |
6.9% | - | |
6.4 | 9.1 | |
1 day ago | 16 days ago | |
JavaScript | Elixir | |
- | GNU General Public License v3.0 or later |
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.
protocol
-
Centralization Possibilities
We have already have a clear stack. there's Gitcoin Passport for sybil resistance, git (and wrappers like Radicle) for version control, Lit PKPs & Gelato for account abstraction, Farcaster/Orbis/Lens for social architecture, OpenStreetMaps for geographic markets, OPStack, etc.
-
Nostr.how – A Complete Guide to Nostr
These services exist outside of the protocol and depend on a few centralized and trusted authorities.
Another solution that is arguably more resistant to capture and censorship would be to use a blockchain to manage user name aliases - like Farcaster is doing with fnames.[1]
[1] https://github.com/farcasterxyz/protocol#22-farcaster-names
-
Mastodon.technology Is Shutting Down
That's sad to hear, but it makes total sense to shut down the server given its sensitive data, rather than hand it off to another person.
Mastodon/ActivityPub is a poor fit for a social network IMHO.
- Accounts should not be tied a single server and their continued maintenance.
- Private data and DMs should be end-to-end encrypted rather than entrusted with a single administrator.
- People don't want to self-host.
The core problem of a lot of social networks comes down to name aliasing, and who controls the name registry. In the case of nostr[1] this is not a problem because everything is using public keys. Another protocol is Farcaster[2] which plans to use a smart contract to maintain a name registry without requiring a single controller.
-
Sufficient Decentralization for Social Networks
a simple mechanism is using a smart contract to map your key (0x123) to an identity (@alice). the contract can allow you to transfer that identity to a different key (important for key rotation) and also to set up a recovery key that is also authorized to transfer the key if the primary key is lost.
our recovery system for Farcaster has a few more bells and whistles, and you can read about it here: https://github.com/farcasterxyz/protocol#33-recovery
author here - happy to answer questions folks have.
we've also been building a sufficiently decentralized protocol called Farcaster, and you can check it out here: https://github.com/farcasterxyz/protocol
we've also built the first clients for this protocol, which are still in beta. if you have an ENS name and are interested in trying them out, DM me on twitter https://twitter.com/varunsrin
rebased
What are some alternatives?
Mastodon - Your self-hosted, globally interconnected microblogging community
rpmsg-lite - RPMsg implementation for small MCUs
soapbox - Software for the next generation of social media.
nostr - a truly censorship-resistant alternative to Twitter that has a chance of working
multihash-serialise - Haskell libraries for interacting with IPFS
misskey_ynh - Misskey package for YunoHost
freebird - matrix based twitter clone
matrix-spec - The Matrix protocol specification
electricui-embedded - Add communications functionality to connect your hardware to a local user interface.
fedbox - Reference implementation of an ActivityPub service using go-ap packages (mirror repository)
aether - Aether client app with bundled front-end and P2P back-end