3 ms·
Having the url point to an utterly huge file instead of a landing page can cause problems for some people. The default behavior on my phone in chrome, for examp
by justin66 12y ago
Having the url point to an utterly huge file instead of a landing page can cause problems for some people. The default behavior on my phone in chrome, for example, is to start downloading in the background.
- q3k 12y agoIt's perfectly fine to link to a large file directly - it seems like your browser is broken.
- tombrossman 12y agoThe browser isn't broken, this is the expected behavior. When you click a link for a downloadable file, your browser fetches it in the background since there is no page to display. The problem in this instance is that there is no 'landing page', it's just there on Cryptome in a big list of pages and other downloads. The real issue is Cryptome's spartan UX gives no easy way to handle this, it's either link to the home page with no context, or link to the file directly.
- justin66 12y agoIt's cute that you think so but this has always been the default behavior and this is the first time it has ever been an issue for me. It's not difficult to see why: ordinarily when you click on a link to huge file, you know you are clicking on a link to a huge file. I wonder if anyone who did so in this case knew what they were getting. (realistically, if you were on a desktop browser you would mouse over the url and notice it was linked to something stupid, but not on a touchscreen device)
- mrmondo 12y agoI think that's just pretty poor behavior on your browser / OS' behalf.
- reledi 12y agoHappened to me as well on my Android. Linking to a file is fine as long as the title makes that clear; maybe the title can be edited?