GM Farcasters 🌅 Today's protocol explainer covers the dilemma between trustworthy and decentralized identities and our solution to the problem. https://youtu.be/ISRyNh6Zd8g
Re: impersonation and the farcaster governance dao How can a farcaster name be governed by a decentralized system where TM/IP are not programmatic? Looking at jurisdictions laws and ownership doesn’t work on the Internet. Google may own the TM in 189 countries but not the 190th.
Events would have to be ephemeral, but what/who/how is lifetime decided? For example, a "hello world" message event. wouldnt need to have as long of a life cycle as a "subscribe" event. A "like" event would need a max life cycle of the remaining life cycle of the event which was liked, etc.
I’m curious to know more about the FNames governance procedures on who decides what for which names. Thanks for the video, it’s very good.
I’ve got 2 questions: How many fnames can be connected to an fid at any given moment? Is it possible to use different fnames on different clients if we own multiple fnames or do we have to use the same fname across all clients?
love how well this pairs with petnames which are imo more powerful but harder to bootstrap
The explainers are great! At 3:20m, who and how is the name space governed? Do app devs & hub operators get any say in this? Also pls confirm, merklem currently controls FID ‘trusted registration’ but you can’t revoke registration nor recover 🙏✌️
Awesome video again. Also could share some light on how FC account is "whitelisted"? Because I assuming the FC eth account is generated in the app, but the whitelist already happen before app is installed. So I assume FID is only generated afterwards.
So basically decentralized identifiers with namespace controlled aliasing? IIUC, the aliases are also stored in a contract which would allow for viewing alias history for a given ID? Would love a pointer to the two contract addresses!
This is great intro to farcaster name space. Questions: Is the choice to have separate name spaces driven by previous examples of speculation? i.e. ENS Would you consider using DIDs for the primary ID? e.g. to enable private credentialing, multi platform interop, binding multiple IDs May add more questions later