[Placeholder][Draft] Extending Friendship Certificate Design

[yisiliu]

I have been thinking about a feasible implementation and extension of this mechanism. The following lied in my considerations:

• BitTorrent trackers or implementing a DHT (distributed hash table) for tracking requests
• "Buses" in CPU architecture, in which different types of data go through them with corresponding privileges. We can potentially build different "buses" based on GunDB with different functionalities and privileges. E.g., address bus for tracking, signal/control bus for transmitting operations and data bus for holding temporary friendship certificate issuing/renewing requests. This is an efficient design, and I would like to explore more on a distributed implementation of this.
• Using FB's graph API to get a user's friend list directly?
• Zero knowledge in certificates
• To be continued

[neruthes]

Are there updates after the introduction of #34?

[Jack-Works]

Are there updates after the introduction of #34?

Nope

[yisiliu]

This might take longer than expected I guess

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.