[RFC] PersonaAutobiography v1.0.1.1 #194

neruthes · 2019-09-19T03:52:07Z

Metadata

Field	Value
Manifest	Meta/Article-3
Purpose	Data Management
Feedback deadline	2019-12-19 12:00:00 UTC
Explicitly designated reviewers	@yisiliu @Jack-Works

Abstract

PersonaAutobiography is designed to provide a universal description format for every person, which should cover all scenarios and be compatible with all transportation methods.

Scenarios include persona backup, database backup, and persona export.

Transportation methods include QR, Base64 text, and JSON File.

Background

Payload Structure

Generic

{
    "Meta": {
        "PayloadSpec": "DeadSeaOldScroll",
        "Version": 1
    },
    "Content": {
        "_": {
            "AppLabel": "maskbook.com--persona-autobiography",
            "AppVersion": 1,
            "Time": 1569374955715,
            "Name": "Neruthes 0x5200DF38",
            "PersonaPrivateKey": null,
            "PersonaPublicKey": {
                "_": "ArxApPYD24e+RjrKyYMpG/2QemXLfxsISb+aFFbltJ1f",
                "encoding": "base-64"
            },
            "PersonaPublicKeyFingerprint": {
                "_": "BCD1FF19582A9B8D5CE9CB780E18C651318756B6",
                "hash": "SHA-1",
                "encoding": "hex"
            },
            "Profiles": {
                "facebook.com": [ "neruthes.5200DF38" ],
                "twitter.com": [ "neruthes" ]
            }
        }
    },
    "Signature": {
        "_": {
            "BaseSig": {
                "_": "WFceyl2VOyvyeaqkTodUI1XulcXQkRVQvh3U65vvMUuRq2ln9ozlECaZYLkKq9HHWKucm9sc2e52y32I1Foikg==",g
                "encoding": "base-64"
            }
        }
    }
}

Since there is no private key in this type, PersonaPrivateKey field should be null.

Including Private Key

{
    "Meta": {
        "PayloadSpec": "DeadSeaOldScroll",
        "Version": 1
    },
    "Content": {
        "_": {
            "AppLabel": "maskbook.com--persona-autobiography",
            "AppVersion": 1,
            "Time": 1569374955715,
            "Name": "Neruthes 0x5200DF38",
            "PersonaPrivateKey": {
                "_": "the natural law of privacy is now enforced by maskbook and tessercube",
                "encoding": "mnw"
            },
            "PersonaPublicKey": {
                "_": "ArxApPYD24e+RjrKyYMpG/2QemXLfxsISb+aFFbltJ1f",
                "encoding": "base-64"
            },
            "PersonaPublicKeyFingerprint": {
                "_": "BCD1FF19582A9B8D5CE9CB780E18C651318756B6",
                "hash": "SHA-1",
                "encoding": "hex"
            },
            "Profiles": {
                "facebook.com": [ "neruthes.5200DF38" ],
                "twitter.com": [ "neruthes" ]
            }
        }
    },
    "Signature": {
    }
}

Example

Over QR code

The text was updated successfully, but these errors were encountered:

Artoria2e5 · 2019-09-30T08:53:07Z

Are we going to consider the case where one persona corresponds to multiple accounts/identifiers on a network? I mean, with the strict URL-like identifier encoding, adding a $1 $2 prefix will do because these things are gonna be invalid. Just don't call it FACEBO~2.com.

update: the new consensus is to use

[network: string]: string[]

neruthes · 2019-09-30T11:41:14Z

Its feasibility remains uncertain, but I do wish to have it possible in data level for now.

Jack-Works · 2019-11-21T15:11:33Z

I'm sorry but where will we use this?

neruthes · 2019-11-21T15:37:25Z

@Jack-Works This is designed for persona backup with mnemonic words, where metadata needs a storage other than the sequence of mnemonic words.

Jack-Works · 2019-11-25T02:59:12Z

@Jack-Works This is designed for persona backup with mnemonic words, where metadata needs a storage other than the sequence of mnemonic words.

We're not saving mnemonic words currently. Should we do this? Does it safe enough to do?

Tedko · 2019-11-25T03:01:22Z

For mnemonic words: better generate some encrypted file protected by a simple password?

…

On Mon, Nov 25, 2019 at 10:59 Jack Works ***@***.***> wrote: @Jack-Works <https://github.com/Jack-Works> This is designed for persona backup with mnemonic words, where metadata needs a storage other than the sequence of mnemonic words. We're not saving mnemonic words currently. Should we do this? Does it safe enough to do? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#194?email_source=notifications&email_token=ABTAVTKRGRDR3RPSCSYHF5LQVM5QBA5CNFSM4IYGB522YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA6OVA#issuecomment-557967188>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTAVTJCSB7XL7INP7CHCW3QVM5QBANCNFSM4IYGB52Q> .

neruthes · 2019-11-25T03:04:06Z

@Jack-Works This is designed for persona backup with mnemonic words, where metadata needs a storage other than the sequence of mnemonic words.

We're not saving mnemonic words currently. Should we do this? Does it safe enough to do?

We should.

Safety remains open for discussion. Maybe @yisiliu has ideas to share on this topic.

neruthes · 2019-11-25T03:06:17Z

For mnemonic words: better generate some encrypted file protected by a simple password?
…

Requiring a password on persona creation is not a good idea. We may introduce "Upgrade Persona Safety" feature in a later version. Device honesty is beyond our concern at this stage; we must assume that all devices are safe enough.

neruthes · 2019-12-03T06:38:56Z

Update:

An optional password field has been added in the interaction design draft. A user may optionally give a password if he feels necessary.

neruthes · 2019-12-03T06:49:52Z

Update:

Now the autobiography may optionally include persona private key or mnemonic words. This can be used as a text-based full backup of a persona, like the "Base64" option in #369.

neruthes · 2019-12-05T10:00:17Z

Update:

With this RFC ratified, optical transfer over QR will be possible, and it could remain.

neruthes · 2019-12-05T10:08:55Z

Updated:

According to discussions in #407, password is now a mandatory field.

neruthes · 2019-12-09T05:53:42Z

Since RFC #223 is ratified and #224 requires this RFC as a dependency, we can now work on this.

neruthes · 2019-12-09T07:54:51Z

This RFC relies on #225. Should ratify #225 fast.

neruthes · 2019-12-09T08:00:28Z

Update:

RFC #225 has been ratified.

neruthes · 2019-12-09T08:02:42Z

TO: @Jack-Works

You may want to introduce the latest design in RFC #223 here. Feel free to update the structure design in the RFC document content.

neruthes · 2019-12-09T08:09:59Z

I will mark this as Ratified if there is no further discussion before today 12:00 UTC.

cc @yisiliu @Jack-Works @SunriseFox @guanbinrui

Jack-Works · 2019-12-09T12:00:41Z

Objection. This format is too verbose.

Why prefer "Meta": { "PayloadSpec": "DeadSeaOldScroll", "Version": 1 },, instead of "version": 1? I'll draft a competitive format that is more concise but still extendable.

(By the way capitalized field name make it somewhat like the classic XML format)

neruthes · 2019-12-09T12:12:37Z

Objection. This format is too verbose.

Why prefer "Meta": { "PayloadSpec": "DeadSeaOldScroll", "Version": 1 },, instead of "version": 1? I'll draft a competitive format that is more concise but still extendable.

I believe that verbosity is better than trivialization. We have a lot of JSON-based payloads. Preventing trivialization is more important than reducing verbosity. RFC #225 has been ratified already. Everyone has been granted sufficient time to review.

Tedko · 2019-12-09T16:50:58Z

I'm √ for the idea of RFC and seems it's indeed necessary.
Also love to see @Jack-Works 's opinion beside verbose.

@Jack-Works @neruthes If you have time take a look of SOLID (and many w3c related) persona designs you might find them helpful. This is an issue under long debating.

Done is better than perfect. -- quote from someone.

Jack-Works · 2019-12-10T02:59:08Z

A format that so verbose is not necessary.

A shorter version

{
  "meta": {
    "version": 1,
    "type": "file_type",
    "maskbookVersion": "1.8.0",
    "timestamp": 1569374955715
  },
  "datatype": [
    {
      "field1": "value1"
    }
  ]
}

Tedko · 2019-12-10T04:31:33Z

👍

…

On Tue, Dec 10, 2019 at 10:59 Jack Works ***@***.***> wrote: A format that so verbose is not necessary. A shorter version { "meta": { "version": 1, "type": "file_type", "maskbookVersion": "1.8.0", "timestamp": 1569374955715 }, "datatype": [ { "field1": "value1" } ] } — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#194?email_source=notifications&email_token=ABTAVTOFBAQ5CDW472LBBQLQX4AX3A5CNFSM4IYGB522YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGMJYEQ#issuecomment-563649554>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTAVTNOM4GQLMTHWLXGLGDQX4AX3ANCNFSM4IYGB52Q> .

neruthes · 2019-12-10T04:37:56Z

Feel free to introduce an alternative to #225. But be hurry.

Jack-Works · 2019-12-10T07:59:15Z

Feel free to introduce an alternative to #225. But be hurry.

I have drafted a cleaner alternative. And we can even change between proposals (before we ship it to user)

Jack-Works · 2019-12-10T08:35:58Z

Draft based on current database structure.

interface BackupJSONFileVersion2 {
    _meta_: {
        version: 2
        type: 'maskbook-backup'
        maskbookVersion: string // e.g. "1.8.0"
        createdAt: number // Unix timestamp
    }
    personas: Array<{
        identifier: string // PersonaIdentifier.toText()
        mnemonic?: {
            word: string
            parameter: { path: string; withPassword: boolean }
        }
        publicKey: JsonWebKey
        privateKey?: JsonWebKey
        localKey?: JsonWebKey
        nickname?: string
        linkedProfiles: Record</** ProfileIdentifier.toText() */ string, LinkedProfileDetails>
        createdAt: number // Unix timestamp
        updatedAt: number // Unix timestamp
    }>
    profiles: Array<{
        identifier: string // ProfileIdentifier.toText()
        nickname?: string
        localKey?: JsonWebKey
        linkedPersona?: string // PersonaIdentifier.toText()
        createdAt: number // Unix timestamp
        updatedAt: number // Unix timestamp
    }>
    userGroups: Array<{
        groupName: string
        identifier: string // GroupIdentifier.toText()
        members: string[] // Array<ProfileIdentifier.toText()>
        banned?: string[] // Array<ProfileIdentifier.toText()>
    }>
    posts: Array<{
        postBy: string // ProfileIdentifier.toText()
        identifier: string // PostIVIdentifier.toText()
        postCryptoKey?: JsonWebKey
        recipients: Record</** ProfileIdentifier.toText() */ string, RecipientDetail>
        recipientGroups: string[] // Array<GroupIdentifier.toText()>
        foundAt: number // Unix timestamp
    }>
}

neruthes · 2019-12-10T10:34:43Z

I am closing all my RFCs since Meta/Article-3: RFC Peer Review Convention has been abolished. I assume that everyone agrees that this is not worth discussing for now. Some discussions may be restarted, if necessary, after Meta/Bill-4: DSD Peer Review Convention is ratified. In the meantime, if there is any question with documentation and workflow, please consult @yisiliu. Thanks for everyone who has engaged in the discussions so long.

neruthes added Type: Feature Discussion: General labels Sep 19, 2019

neruthes self-assigned this Sep 19, 2019

neruthes mentioned this issue Sep 19, 2019

[RFC] Persona Key Export with Mnemonic Words #195

Closed

neruthes assigned yisiliu and Jack-Works Sep 19, 2019

neruthes mentioned this issue Sep 25, 2019

[RFC] Database Backup Specification v1.0.0.0 #224

Closed

neruthes changed the title ~~[RFC] Persona Metadata Exchange Format v1.0.0.0 [Draft]~~ [RFC] Persona Metadata Exchange Format v1.0.1.0 [Draft] Sep 30, 2019

neruthes changed the title ~~[RFC] Persona Metadata Exchange Format v1.0.1.0 [Draft]~~ [RFC] PersonaAutobiography v1.0.1.0 [Draft] Sep 30, 2019

neruthes added the RFC: Draft label Nov 11, 2019

neruthes added RFC: Open Component: GUN Gun.js related and removed RFC: Draft Type: Feature Discussion: General labels Nov 19, 2019

neruthes changed the title ~~[RFC] PersonaAutobiography v1.0.1.0 [Draft]~~ [RFC] PersonaAutobiography v1.0.1.0 Nov 19, 2019

neruthes mentioned this issue Nov 25, 2019

Dashboard Revamp (Stage 2) #369

Closed

neruthes changed the title ~~[RFC] PersonaAutobiography v1.0.1.0~~ [RFC] PersonaAutobiography v1.0.1.1 Dec 3, 2019

neruthes removed the Component: GUN Gun.js related label Dec 9, 2019

neruthes mentioned this issue Dec 9, 2019

[Demand] Implement RFC 194 #481

Closed

Jack-Works mentioned this issue Dec 10, 2019

Next backup format (Part 1) #501

Merged

neruthes closed this as completed Dec 10, 2019

neruthes added RFC: Dismissed and removed RFC: Open labels Dec 10, 2019

Jack-Works added the Kind: Protocol label Feb 10, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[RFC] PersonaAutobiography v1.0.1.1 #194

[RFC] PersonaAutobiography v1.0.1.1 #194

neruthes commented Sep 19, 2019 •

edited

Loading

Artoria2e5 commented Sep 30, 2019 •

edited

Loading

neruthes commented Sep 30, 2019

Jack-Works commented Nov 21, 2019

neruthes commented Nov 21, 2019

Jack-Works commented Nov 25, 2019

Tedko commented Nov 25, 2019 via email

neruthes commented Nov 25, 2019

neruthes commented Nov 25, 2019

neruthes commented Dec 3, 2019

neruthes commented Dec 3, 2019

neruthes commented Dec 5, 2019

neruthes commented Dec 5, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019 •

edited

Loading

neruthes commented Dec 9, 2019

Jack-Works commented Dec 9, 2019

neruthes commented Dec 9, 2019 •

edited

Loading

Tedko commented Dec 9, 2019

Jack-Works commented Dec 10, 2019

Tedko commented Dec 10, 2019 via email

neruthes commented Dec 10, 2019

Jack-Works commented Dec 10, 2019

Jack-Works commented Dec 10, 2019

neruthes commented Dec 10, 2019 •

edited

Loading

[RFC] PersonaAutobiography v1.0.1.1 #194

[RFC] PersonaAutobiography v1.0.1.1 #194

Comments

neruthes commented Sep 19, 2019 • edited Loading

Metadata

Abstract

Background

Payload Structure

Generic

Including Private Key

Example

Over QR code

Artoria2e5 commented Sep 30, 2019 • edited Loading

neruthes commented Sep 30, 2019

Jack-Works commented Nov 21, 2019

neruthes commented Nov 21, 2019

Jack-Works commented Nov 25, 2019

Tedko commented Nov 25, 2019 via email

neruthes commented Nov 25, 2019

neruthes commented Nov 25, 2019

neruthes commented Dec 3, 2019

neruthes commented Dec 3, 2019

neruthes commented Dec 5, 2019

neruthes commented Dec 5, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019

neruthes commented Dec 9, 2019 • edited Loading

neruthes commented Dec 9, 2019

Jack-Works commented Dec 9, 2019

neruthes commented Dec 9, 2019 • edited Loading

Tedko commented Dec 9, 2019

Jack-Works commented Dec 10, 2019

Tedko commented Dec 10, 2019 via email

neruthes commented Dec 10, 2019

Jack-Works commented Dec 10, 2019

Jack-Works commented Dec 10, 2019

neruthes commented Dec 10, 2019 • edited Loading

neruthes commented Sep 19, 2019 •

edited

Loading

Artoria2e5 commented Sep 30, 2019 •

edited

Loading

neruthes commented Dec 9, 2019 •

edited

Loading

neruthes commented Dec 9, 2019 •

edited

Loading

neruthes commented Dec 10, 2019 •

edited

Loading