Support publishing channel descriptions, cover photos and other metadata #561

New issue

Closed

opened 2017-09-13 23:57:39 +02:00 by tzarebczan · 5 comments

tzarebczan commented

2017-09-13 23:57:39 +02:00

(Migrated from github.com)

The Issue

The current channel page looks a bit empty with the "Channel pages are empty for all publishers currently, but will be coming in a future update." message. Can we add this issue to the Publishing Epic to at least add some descriptions to channels?

In the future, other channel data could include:
Channel Image
Stats (creation date, total subscribers, total videos, total views, etc)
Tip Button (channel side vs content side)
Contact information
Linked channels?


        Create a new channel by generating a channel private key and establishing an '@' prefixed claim.

        Usage:
            channel_create (<name> | --name=<name>) (<bid> | --bid=<bid>)
                           [--allow_duplicate_name=<allow_duplicate_name>]
                           [--title=<title>] [--description=<description>] [--email=<email>] [--featured=<featured>...]
                           [--tags=<tags>...] [--languages=<languages>...] [--locations=<locations>...]
                           [--website_url=<website_url>] [--thumbnail_url=<thumbnail_url>] [--cover_url=<cover_url>]
                           [--account_id=<account_id>] [--claim_address=<claim_address>] [--preview]

        Options:
            --name=<name>                  : (str) name of the channel prefixed with '@'
        --allow_duplicate_name=<allow_duplicate_name> : (bool) create new channel even if one already exists with
                                              given name. default: false.
            --bid=<bid>                    : (decimal) amount to back the claim
            --title=<title>                : (str) title of the publication
            --description=<description>    : (str) description of the publication
            --featured=<featured>          : (list) claim_ids of featured content in channel
            --tags=<tags>                  : (list) content tags
            --languages=<languages>        : (list) languages used by the channel,
                                                    using RFC 5646 format, eg:
                                                    for English `--languages=en`
                                                    for Spanish (Spain) `--languages=es-ES`
                                                    for Spanish (Mexican) `--languages=es-MX`
                                                    for Chinese (Simplified) `--languages=zh-Hans`
                                                    for Chinese (Traditional) `--languages=zh-Hant`
            --locations=<locations>        : (list) locations of the channel, consisting of 2 letter
                                                    `country` code and a `state`, `city` and a postal
                                                    `code` along with a `latitude` and `longitude`.
                                                    for JSON RPC: pass a dictionary with aforementioned
                                                        attributes as keys, eg:
                                                        ...
                                                        "locations": [{'country': 'US', 'state': 'NH'}]
                                                        ...
                                                    for command line: pass a colon delimited list
                                                        with values in the following order:

                                                          "COUNTRY:STATE:CITY:CODE:LATITUDE:LONGITUDE"

                                                        making sure to include colon for blank values, for
                                                        example to provide only the city:

                                                          ... --locations="::Manchester"

                                                        with all values set:

                                                 ... --locations="US:NH:Manchester:03101:42.990605:-71.460989"

                                                        optionally, you can just pass the "LATITUDE:LONGITUDE":

                                                          ... --locations="42.990605:-71.460989"

                                                        finally, you can also pass JSON string of dictionary
                                                        on the command line as you would via JSON RPC

                                                          ... --locations="{'country': 'US', 'state': 'NH'}"

            --email=<email>                : (str) email of channel owner
            --website_url=<website_url>    : (str) website url
            --thumbnail_url=<thumbnail_url>: (str) thumbnail url
            --cover_url=<cover_url>        : (str) url of cover image
            --account_id=<account_id>      : (str) id of the account to store channel
            --claim_address=<claim_address>: (str) address where the channel is sent to, if not specified
                                                   it will be determined automatically from the account
            --preview                      : (bool) do not broadcast the transaction

        Returns: {Transaction}

Sample:

    "address": "bVyKHLxRHnjPKW4C4GUCQz67ynGZSfveZ1",
    "amount": "0.001",
    "claim_id": "04c91cf3dd1dfcb4414efc3eca24dc449fc28d4b",
    "claim_op": "create",
    "confirmations": 2,
    "height": 556665,
    "is_change": false,
    "is_mine": true,
    "name": "@NewMetadataChannel",
    "nout": 0,
    "permanent_url": "lbry://@NewMetadataChannel#04c91cf3dd1dfcb4414efc3eca24dc449fc28d4b",
    "txid": "b8f0eb451f648d360204efdc26173de33a8b7cbe0b66db21f84def2039868f45",
    "type": "claim",
    "value": {
      "cover": {
        "url": "https://spee.ch/5/tom-banner.jpg"
      },
      "description": "My Channel Description",
      "email": "tom@lbry.com",
      "featured": [
        "cda25338628bada976a78e7d04367ca075bde397"
      ],
      "languages": [
        "en",
        "es"
      ],
      "locations": [
        {
          "latitude": 429906050,
          "longitude": -714609890
        },
        {
          "city": "Manchester"
        }
      ],
      "public_key": "3056301006072a8648ce3d020106052b8104000a034200042030108c1670b7c204c8a30643e8779699978d8aa6556de154fb231bfc72c369a48c4c97f71de9a3dc5afa7ad020231c3051e933b5598816434d8680de21d6b1",
      "tags": [
        "tag1 chan",
        "tag2 chan"
      ],
      "thumbnail": {
        "url": "https://spee.ch/4/tom-z.jpg"
      },
      "title": "My Channel Title",
      "website_url": "lbry.com"
    },
    "value_type": "channel"
  },

System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

## The Issue The current channel page looks a bit empty with the "Channel pages are empty for all publishers currently, but will be coming in a future update." message. Can we add this issue to the Publishing Epic to at least add some descriptions to channels? In the future, other channel data could include: Channel Image Stats (creation date, total subscribers, total videos, total views, etc) Tip Button (channel side vs content side) Contact information Linked channels? ``` Create a new channel by generating a channel private key and establishing an '@' prefixed claim. Usage: channel_create (<name> | --name=<name>) (<bid> | --bid=<bid>) [--allow_duplicate_name=<allow_duplicate_name>] [--title=<title>] [--description=<description>] [--email=<email>] [--featured=<featured>...] [--tags=<tags>...] [--languages=<languages>...] [--locations=<locations>...] [--website_url=<website_url>] [--thumbnail_url=<thumbnail_url>] [--cover_url=<cover_url>] [--account_id=<account_id>] [--claim_address=<claim_address>] [--preview] Options: --name=<name> : (str) name of the channel prefixed with '@' --allow_duplicate_name=<allow_duplicate_name> : (bool) create new channel even if one already exists with given name. default: false. --bid=<bid> : (decimal) amount to back the claim --title=<title> : (str) title of the publication --description=<description> : (str) description of the publication --featured=<featured> : (list) claim_ids of featured content in channel --tags=<tags> : (list) content tags --languages=<languages> : (list) languages used by the channel, using RFC 5646 format, eg: for English `--languages=en` for Spanish (Spain) `--languages=es-ES` for Spanish (Mexican) `--languages=es-MX` for Chinese (Simplified) `--languages=zh-Hans` for Chinese (Traditional) `--languages=zh-Hant` --locations=<locations> : (list) locations of the channel, consisting of 2 letter `country` code and a `state`, `city` and a postal `code` along with a `latitude` and `longitude`. for JSON RPC: pass a dictionary with aforementioned attributes as keys, eg: ... "locations": [{'country': 'US', 'state': 'NH'}] ... for command line: pass a colon delimited list with values in the following order: "COUNTRY:STATE:CITY:CODE:LATITUDE:LONGITUDE" making sure to include colon for blank values, for example to provide only the city: ... --locations="::Manchester" with all values set: ... --locations="US:NH:Manchester:03101:42.990605:-71.460989" optionally, you can just pass the "LATITUDE:LONGITUDE": ... --locations="42.990605:-71.460989" finally, you can also pass JSON string of dictionary on the command line as you would via JSON RPC ... --locations="{'country': 'US', 'state': 'NH'}" --email=<email> : (str) email of channel owner --website_url=<website_url> : (str) website url --thumbnail_url=<thumbnail_url>: (str) thumbnail url --cover_url=<cover_url> : (str) url of cover image --account_id=<account_id> : (str) id of the account to store channel --claim_address=<claim_address>: (str) address where the channel is sent to, if not specified it will be determined automatically from the account --preview : (bool) do not broadcast the transaction Returns: {Transaction} ``` Sample: ``` { "address": "bVyKHLxRHnjPKW4C4GUCQz67ynGZSfveZ1", "amount": "0.001", "claim_id": "04c91cf3dd1dfcb4414efc3eca24dc449fc28d4b", "claim_op": "create", "confirmations": 2, "height": 556665, "is_change": false, "is_mine": true, "name": "@NewMetadataChannel", "nout": 0, "permanent_url": "lbry://@NewMetadataChannel#04c91cf3dd1dfcb4414efc3eca24dc449fc28d4b", "txid": "b8f0eb451f648d360204efdc26173de33a8b7cbe0b66db21f84def2039868f45", "type": "claim", "value": { "cover": { "url": "https://spee.ch/5/tom-banner.jpg" }, "description": "My Channel Description", "email": "tom@lbry.com", "featured": [ "cda25338628bada976a78e7d04367ca075bde397" ], "languages": [ "en", "es" ], "locations": [ { "latitude": 429906050, "longitude": -714609890 }, { "city": "Manchester" } ], "public_key": "3056301006072a8648ce3d020106052b8104000a034200042030108c1670b7c204c8a30643e8779699978d8aa6556de154fb231bfc72c369a48c4c97f71de9a3dc5afa7ad020231c3051e933b5598816434d8680de21d6b1", "tags": [ "tag1 chan", "tag2 chan" ], "thumbnail": { "url": "https://spee.ch/4/tom-z.jpg" }, "title": "My Channel Title", "website_url": "lbry.com" }, "value_type": "channel" }, ``` ## System Configuration   - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else  ## Screenshots

👍 1

unclejed613 commented

2017-09-14 04:15:04 +02:00

(Migrated from github.com)

Yes, I have the same request. Having a channel without a description of the channel really doesn't do much for the content, except give the publisher a place to put it. Also, I noticed that doing a search for a channel name (@whatever) doesn't return any meaningful results, just a list of files that has a portion of the search string in the file name or title.

MSFTserver commented

2017-09-14 04:28:10 +02:00

(Migrated from github.com)

@unclejed613 search is being worked on i heard it was almost finished

seanking2919 commented

2017-09-14 05:44:14 +02:00

(Migrated from github.com)

You definitely could do a linked channels list, but I'd like a social media links list better IMO.

liamcardenas commented

2017-11-17 18:15:44 +01:00

(Migrated from github.com)

neb-b commented

2019-05-07 21:11:52 +02:00

(Migrated from github.com)

Displaying new channel metadata on pages was added in #2462

Support for publishing/editing channels with these fields will come later. But it's possible to do it from the sdk cli right now.

Displaying new channel metadata on pages was added in #2462 Support for publishing/editing channels with these fields will come later. But it's possible to do it from the sdk cli right now.