Yes to both.
Initial load of all the follow lists is just heavy. Need to use graph snapshots instead, at least on web & mobile, so there's that centralization. But you can always locally recrawl when you feel bandwidth-rich.
Login to reply
Replies (3)
Negentropy or "send only matching event ids, I'll request those that I don't already have" would help with bandwidth
This is why i propose, aside from all the other stuff you can use, to also start creating musig handshake events. Still need to do the write up, and i have a rather specific usecase in mind, but:
TL:DR, using musig events as association proofs to base WoT and identity analyses on in order to facilitate key migration.
Been struggeling with a write up, so il have ass a post on it first:
Figuring out which npub is the correct npub in terms of the person/identity/thing you are looking for is a hard problem, especially if you take people migrating to a different npub (because of loss or compromise) into account.
For many reasons i wont go into i would posit that the only real way is to leverage contextual understanding, or what we broadly call 'web of trust'. This type of analyses looks at behavior, posts, mentions, reactions, follows etc. and through interconnectivity in associations you can start to make sense of things.
My idea is to add a thing, which could serve as a relatively simple efficient abstraction of these associations into single events. So instead of for example trying to look for mutual follows (bob follows alice; alice follows bob, so we infer association of some kind) , Bob and alice create a musig abstract handshake event together. This can be done between two or more people.
This way, "association" (whatever that may mean) is abstracted into easily traceable compact data.
Easy to trace because this musig interaction creates an Npub specific to the combination of the two or more participating npubs. And compact because one event represents two or more associations.
The idea is to put experation dates on these things, this way signals 'die out' the moment association stops between Npubs; this could be cause to look for other association events, and perhaps finding someone posting under a new Npub within otherwise the same 'network of associations' with the same name (indication some switched keypairs).
To be clear, this type of analyses is probably still somewhat complex, but hopefully massively simplifying the queries and comparisons.
To be clear i am not suggesting to do this with everyone, on the contrary: you are in controll of what this 'association' means, and you effectively tie your identity to it. The events themselves are just evidence of appearently a concious decision to interact in a particular moment in time. What leads up to that is up to the participants themselves. Some super fancy procedures for really important people;
just the fact your bro joined the voicechat during the weekly gaming sessions;
Or because....you live in the same house.
Bottomline is that 'you' are defined by what you do as much as who you associate with; and what npub your using is expressed in both, may change over time, and this way we have a method of keeping track of that.
Not a watertight superdeterministic objective binary perfect system, but a...practical approach.
Anyway, better write up is comming, maybe.
Any questions?
View quoted note →
Oh sorry, missed the bitchat context, nvm