You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Anders %iWG4NoEf94gQ/cn9Q/JjdlVtORs69WI1w6GWPJt8BHU=.sha256

@moid there definitely is overlap, I think the most important distinction is what guarantees they provide. Metafeeds, because you only have 1 writer, can have a simpler model to dictate what the truth is. Like if a feed is no longer used it can tombstone it. Fusion identities on the other hand are more complicated because you are dealing with multiple physical devices. We didn't want to end up with a leader, so instead we ended up with: if something happens the identity is gone and you have to create a new one. Because the identities are light (basically just a read/identity key), its not that big of a deal. The biggest problem is determining what the new fusion identity for that person is, this is where we have redirects and attestation.

@Anders %+oXYFy7uo34X+WU2vf+fjG5HWL8JvHizM65fJZQ6Jyo=.sha256

You could argue that for a single person with multiple devices the difference is probably not that big, but consider a fusion identity for a larger group, say the ngi pointer team, then these things becomes important.

User has not chosen to be hosted publicly
Join Scuttlebutt now