LBRYCommunity/ytsync

Fork

You've already forked ytsync

Code Issues 39 Pull requests 8 Projects Releases 197 Packages Wiki Activity

Ensure vanity channel URLs for higher value YouTubers #14

New issue

Open

opened 2019-01-03 00:57:33 +01:00 by tzarebczan · 0 comments

tzarebczan commented

2019-01-03 00:57:33 +01:00

(Migrated from github.com)

Copy link

We had discussed the possibility of ensuring that YouTube channel
(at least for those with X amount of subs) lbry URLs resolve at their vanity names. This recently came up as a source of confusion on Twitter: https://twitter.com/eevblog/status/1080609595289042945

This shouldn't be too hard to setup as part of the YT sync process.

We had discussed the possibility of ensuring that YouTube channel (at least for those with X amount of subs) lbry URLs resolve at their vanity names. This recently came up as a source of confusion on Twitter: https://twitter.com/eevblog/status/1080609595289042945 This shouldn't be too hard to setup as part of the YT sync process.

No Branch/Tag specified

Branches Tags

master

dependabot/go_modules/github.com/docker/distribution-2.8.2incompatible

dependabot/go_modules/github.com/gin-gonic/gin-1.9.0

dependabot/go_modules/github.com/docker/docker-20.10.24incompatible

dependabot/go_modules/golang.org/x/crypto-0.1.0

dependabot/go_modules/golang.org/x/net-0.7.0

dependabot/go_modules/golang.org/x/text-0.3.8

pseudoscalar/issue/112/v2

pseudoscalar/issue/112/v1

local

fuck-yt

latest-lbry.go

fix-travis

merge_e2e

grin

transfers

metadata_upgrade

v5.9.10

v5.9.9

v5.9.8

v5.9.7

v5.9.6

v5.9.5

v5.9.4

v5.9.3

v5.9.2

v5.9.1

v5.9.0

v5.8.13

v5.8.12

v5.8.11

v5.8.10

v5.8.9

v5.8.8

v5.8.7

v5.8.6

v5.8.5

v5.8.4

v5.8.3

v5.8.2

v5.8.1

v5.8.0

v5.7.13

v5.7.12

v5.7.11

v5.7.10

v5.7.9

v5.7.8

v5.7.7

v5.7.6

v5.7.5

v5.7.4

v5.7.3

v5.7.2

v5.7.1

v5.7.0

v5.6.38

v5.6.37

v5.6.36

v5.6.35

v5.6.34

v5.6.33

v5.6.32

v5.6.31

v5.6.30

v5.6.29

v5.6.28

v5.6.27

v5.6.26

v5.6.25

v5.6.24

v5.6.23

v5.6.22

v5.6.21

v5.6.20

v5.6.19

v5.6.18

v5.6.17

v5.6.16

v5.6.15

v5.6.14

v5.6.13

v5.6.12

v5.6.11

v5.6.10

v5.6.9

v5.6.8

v5.6.7

v5.6.6

v5.6.5

v5.6.4

v5.6.3

v5.6.2

v5.6.1

v5.6.0

v5.5.10

v5.5.9

v5.5.8

v5.5.7

v5.5.6

v5.5.5

v5.5.4

v5.5.3

v5.5.2

v5.5.1

v5.5.0

v5.4.9

v5.4.8

v5.4.7

v5.4.6

v5.4.5

v5.4.4

v5.4.3

v5.4.2

v5.4.1

v5.4.0

v5.3.17

v5.3.16

v5.3.15

v5.3.14

v5.3.13

v5.3.12

v5.3.11

v5.3.10

v5.3.9

v5.3.8

v5.3.7

v5.3.6

v5.3.5

v5.3.4

v5.3.3

v5.3.2

v5.3.1

v5.3.0

v5.2.11

v5.2.10

v5.2.9

v5.2.8

v5.2.7

v5.2.6

v5.2.5

v5.2.4

v5.2.3

v5.2.2

v5.2.1

v5.2.0

v5.1.8

v5.1.7

v5.1.6

v5.1.5

v5.1.4

v5.1.3

v5.1.2

v5.1.1

v5.1.0

v5.0.11

v5.0.10

v5.0.9

v5.0.8

v5.0.7

v5.0.6

v5.0.5

v5.0.4

v5.0.3

v5.0.2

v5.0.1

v5.0.0

v4.0.6

v4.0.5

v4.0.4

v4.0.3

v4.0.2

v4.0.1

v4.0.0

v3.6.13

v3.6.12

v3.6.11

v3.6.10

v3.6.9

v3.6.8

v3.6.7

v3.6.6

v3.6.5

v3.6.4

v3.6.3

v3.6.2

v3.6.1

v3.6.0

v3.5.8

v3.5.7

v3.5.6

v3.5.5

v3.5.4

v3.5.3

v3.5.2

v3.5.1

v3.5.0

v3.4.9

v3.4.8

v3.4.7

v3.4.6

v3.4.5

v3.4.4

v3.4.3

v3.4.2

v3.4.1

v3.4.0

v3.3.1

v3.3.0

v3.2.1

v3.2.0

v3.1.2

v3.1.1

v3.1.0

v3.0.2

v3.0.1

v3.0.0

v2.0.0

v1.0.3

v1.0.2

v1.0.1

v1.0.0

Labels

Clear labels

Work is part of a proposal

consider soon

Discuss this issue at the next planning meeting, then remove this label

dependencies

Pull requests that update a dependency file

Welcome to Hacktoberfest

help wanted

Extra attention is needed

icebox

Long-term storage

level: 1

No knowledge of the existing code required

level: 2

Some knowledge of the existing code is recommended

level: 3

Significant knowledge of the existing code is recommended

level: 4

Intimate knowledge of the existing code is recommended

needs: exploration

Solution unclear, needs research

needs: grooming

Issue needs to be groomed before work can start

needs: priority

Priority level needs to be defined

needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

needs: tech design

Needs technical design signoff before implementation can begin

on hold

Temporarily paused

priority: blocker

Issue is blocking release, do ASAP

priority: high

Work needs to be moved into sprint ASAP

priority: low

Work should be done but can stay in the backlog for now

priority: medium

Work needs to be done within 2-3 sprints

Existing functionality is wrong or broken

type: discussion

A conversation. No specific changes requested

type: improvement

Existing (or partially existing) functionality needs to be changed

type: new feature

New functionality that does not exist yet

type: refactor

Minimal user-visible changes, but significant internal work

type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

type: testing

Solution needs additional user testing

unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/ytsync#14

Reference in a new issue

Repository

LBRYCommunity/ytsync

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?