3 ms·
I was about to post the same link. I wonder if 'dang' followed the same process I did: click the submitted link; read the interesting abstract; scroll to the
by nkurz 12y ago
I was about to post the same link.
I wonder if 'dang' followed the same process I did: click the submitted link; read the interesting abstract; scroll to the bottom only to be scared by the embedded video; recover for a second from the panic of being without plain text; scroll back up scrutinizing the small print for a link to actual paper; then click with an awkward urgency, feeling relief at having found my way back to safe ground.
Then I asked myself, "Why did the submitter link to the container page rather than to the real content? Maybe 'dang' should change the link?" But then I wondered, "What if there are people who actually prefer the video? It's hard for me to picture, but presumably such people exist. How will they be able to watch the video if the link goes straight to the PDF?"
So as a survey for my sanity, I have to ask: How many people watched the video without looking at the paper first? How many looked at the paper without giving any consideration to the video? Second, does this correlate with the first 'sin' in the paper? Do those who prefer linear text also frequently wonder if unnecessary distributed parallelism tends to hamper performance?
- ams6110 12y agoWhile my reaction to content posted as a video (whether it be a tutorial, paper, how-to, etc.) is more what I'd call annoyance than panic, I rarely watch them. I find I can skim written content and within about 30 seconds decide if it's worth spending more time on. Not so easy with a video.
- kordless 12y agoHigher density data as well. Given I have the ability to scan high amounts of data quickly, it makes more sense to go for the time saving function.
- jcr 12y agoNate, we don't really have a convention or guideline for this situation. The guidelines only tell us to add [pdf], [video], and similar to the title if it's a link to a media file. Though it's not exactly stated, it means a direct link to the media file itself, rather than a link to the page where the media files can be downloaded. For example, we (almost?) never see "[video]" tags in the titles of stories linking to youtube or vimeo. On previous USENIX submissions I've put some variation of "[pdf/slides/video]" in the title to indicate multiple things are available, but this just created unnecessary work for poor `dang` who had to edit the title to remove it. I really do try to avoid causing work for the moderators, so this time, I did not put the extra info in the title. I was proud of myself for learning from my mistake... until I saw `dang` adding a comment with a direct link to the paper pdf. (sigh, I'll probably never learn ;) If there is a "right" answer, then I still haven't figured it out yet. As for my access pattern, I actually found the USENIX page from another site listing various papers, so that's what I was looking for when I loaded the page. I made sure the USENIX actually did provide a download link to the full paper PDF (sometimes they don't/can't), and then started downloading the video with wget in the background while I read the paper... I still haven't watched the video yet, but I will.
- nkurz 12y agoI appreciate the insight. I wasn't trying to criticize your choice of link, just wondering if others shared my personal reaction. Similar to linking to the abstract page for arXiv papers, I think you chose the "right" option. I think the FAQ is out of date with regard to adding an explicit [PDF], as the system now adds this automatically for links where the type is apparent. But I'm always impressed at how efficient the new 'dang' API is for adding publication dates to submitted papers!