Farcaster

What's something you find confusing about Farcaster or Warpcast?

No dumb questions—if it's confusing to you, likely confusing for others.

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

FC decentralisation, I don't understand fully how (in terms of control) is FC different than a web2 website managed by a private company (other than that it is based on web3 solutions)

What parts of FC, protocol, nodes, etc  are decentralised  (as in controlled by community, or immutable) vs controlled by Merkle

1/ We should update our videos and docs, but this is current: 

https://docs.farcaster.xyz/protocol/architecture.html

Starting next week (after sign ups go permissionless) the only thing controlled by Merkle / Warpcast is the Warpcast app.

Hubs are decentralized and and onchain contracts are non-upgradeable.

 working on @pixelnunc  hosting /pixelnunc /sci-fi /roman-empire




3/ How do you make changes to Farcaster if it's decentralized?

Rough consensus and working code (emphasis on the working code part)

https://docs.farcaster.xyz/protocol/governance.html

This is similar to Ethereum or Bitcoin. If you don't like Warpcast decisions, starting next week you can avoid Warpcast completely.

4/ But what about the Hubble and smart contract repos?

Hubble is an implementation of the protocol spec like Geth is for Etheruem. @haardikkk actually started working on a Rust implementation of a Hub.

We'd like to have more full-time indpt contributors to Hubble and contracts over time

2/ If you want to really get into the details.

- Merkle / Warpcast is a team of 13 people

- Protocol has 100 unique contributors, but most of the code for Hubs and the onchain smart contracts has been written by Warpcast team

- We also have the keys to the fname server but offer ENS as user-controlled alternative