Multimedia of different formats are throughout the web, largely because the browsers we use today are so extensive in terms of functionality. However, there's a growing tend of thought that modern "front end" web developers are smarter than the many people who write and work on web browsers.
Case and point is made regularly with many sites, but for this article I'm looking at Imgur. Imgur is a image sharing website, for those uninitiated in internet culture.
A central repository or depot of images isn't a bad idea, especially if it is optional, and allows the same image across multiple sites to be cached. When a repository starts to do weird things, people should be looking elsewhere.
The issue with Imgur is the fact that images aren't treated as images. Major and modern browsers can handle many image formats without additional instruction. Even roughly 9 years ago Internet Explorer 9 was able to render Scalable Vector Graphics (SVGs), so there's no excuse for this behavior.
Now, as of a few months ago, you are granted the privilege of reading a single english sentence:
In the day and age of "UX Experts", one
would should question several things:
For those reading and don't believe me, take the example link or "image":
It can magically be rendered as an actual image by:
.pngto the end of the url (even though the browser will ultimately receive a JPEG file).
The result for the above gives you:
If you try
.mp4 or some other odd extension you will receive a "400 bad request error", because it is you the user, who made the bad request?
This is the question I've asked myself. The easy way is to rewrite all links for Imgur to direct links. I built a Firefox extension to do this automatically, because I would see or receive links that were not direct for some reason or another.
That being said, the first issue you will run into is that Imgur supports "albums" which I haven't reverse engineered as of yet, so all links can't be rewritten (links that contain
/a/ or such). The second and harder part to address is the "we" in the question.
Modern hardware and software has moved to a more "idiot proof" interface choice, and mobile-first design. Long gone are the simple and visually direct menu bars, replaced with hamburger menus designed for small and limited phone screens. The wide user base doesn't have an issue with this, as long as the classic primary criteria of "it just works" is met, there won't be a push to rid the web of plain stupid implementations like the aforementioned.
There are no comments to be loaded for this article.