4 ms·
That's certainly not what I want to share. One of the things that good video sites provide is context. E.g.: Who made this? What else have they done? How can I
by wpietri 11y ago
That's certainly not what I want to share. One of the things that good video sites provide is context. E.g.: Who made this? What else have they done? How can I find them? Has this been widely seen? What do people say about it?
Raw streaming urls don't get me any of that. URLs aren't just pointers to bytestreams. From a user sharing perspective, they're humans pointing to a unique thing. And what they're pointing to is often much more complex than a single raw file.
- the8472 11y ago> What do people say about it? you want to share youtube comments with people? they are a significant value-add to you?
- snowwrestler 11y agoYoutube comments are great for finding out the name of songs in the background of the video.
- towelguy 11y agoAnd all of them are Darude's Sandstorm.
- 15155 11y agoYou mean 009 Sound System.
- ethbro 11y ago> Youtube comments are great for finding out the name of songs in the background of the video. And here I'd concluded the comments section existed to allow pre-teens to practice their ability to make racist remarks.
- x0x0 11y agoand post-teens
- sevenadrian 11y agofalse, comments are always terrible, including this one.
- yellowapple 11y agoYou could easily address those concerns without turning what should be a simple video into a clusterfsck of Javascript. For example: https://mytube.com/$username/my_first_video.ogg With such a scheme, you immediately know who made it - $username - and (if this hypothetical mytube.com built a proper website) navigating to mytube.com/$username would return a list of videos (maybe with some additional routes for playlists or categories). Sure, now the user would have to go through the additional work of editing URLs if they want to access this endpoint manually, but then this article's points come into play: if your users expect more functionality than what the World Wide Web does well - delivering content - then a native app is probably preferable for everyone involved (and, indeed, exists for sites like YouTube).
- nucleardog 11y agoURLs are opaque strings to the typical user.
- marssaxman 11y agoSo are most other schemes for information organization, but that does not make them inherently less useful.
- yellowapple 11y agoMy point was that the typical user would be better served with a native app that turns that URL into less-opaque data. And even with the URL alone, that's still significantly less opaque than YouTube's current method of https://youtube.com/$some_random_gibberish https://youtube.com/$some_random_gibberish. At least someone could see something like https://mytube.com/j_random_hacker/how_to_computer.mp4 https://mytube.com/j_random_hacker/how_to_computer.mp4 and guess that "j_random_hacker" is a username and "how_to_computer.mp4" is a video uploaded by that user. This isn't much different from, say, reddit, where URLs are actually part of normal discussion; a redditor will talk about a subreddit called "/r/mylittlepony" or a user named "/u/Unidan" or somesuch, directly referencing paths (to https:/reddit.com/r/mylittlepony and https://reddit.com/u/Unidan https://reddit.com/u/Unidan, respectively). Granted, reddit's userbase is somewhat more tech-savvy on average than, say, Facebook's or YouTube's, but it shows that URLs are not necessarily opaque to typical users, and it's certainly not hard to even manually demonstrate such things to new users. This also isn't much different from many (most?) news sites, which provide URLs that resemble the name of the article (with some adjustment to make everything lowercase, turn spaces into underscores, strip or substitute special characters, etc.).