Reposts with deletions/edits V2#3697
Conversation
detect whether a repost actually contains modifications.
|
leaving a note since im assigned as reviewer: we decided to go with a simple string->[]string mapping instead of protobuf.Any |
Rework helpers in attrs.py. TEMP: Add ext.Descriptor.
|
State of this is I need to remove the dynamic extension type stuff, and add some code to catch |
|
To see the claim.proto changes go here: The latest is I am storing extensions in a map instead of a repeated field. (Got that idea from: #2983) For these Also, the values in StringMap are lists of strings. (Got that idea from: https://github.com/bb-msf-dd/types/pull/1/files#diff-4d1a25cbe9fc3b724c4dd38caf452672c542838cdc0cd567dc12460804534fc5R97) |
Only the ext.StringMap extension is supported for now.
|
Latest .proto changes look like: |
|
Planning some further simplification after talking to @lyoshenka. |
|
Closed in favor of #3706 |
Context: lbryio/types#49
This based on a different claim.proto schema that limits modifications to only reposts of streams and only within a specific set of "Stream.Extension" fields. This is enforced at the level of the protobuf.
The Stream.Extension message contains a protobuf.Any. Right now I check the type name to make sure it's a type that 1) is known when the SDK is built, and 2) comes from a limited list of messages that are intended to be used as extensions. But I think it would be possible to put a claim ID as the "type_url_prefix" of protobuf.Any and download the "descriptor" needed to understand the type. For example, if the "@type" field of the Any message contains "<claim_id>/pb.Cad", the SDK can try to download the contents pointed to by <claim_id>.
To see the claim.proto changes go here:
https://github.com/moodyjon/types/commits/repost_modify
Hub changes that would index the extension fields are TODO.