Some image viewers on smartphones let the user delete photos and videos by swiping them off the screen vertically. This causes the risk of it happening accidentally. Someone must have thought this is a smart idea.

If a gallery application has this anti-feature, I will immediately stop using it and install a third-party one without swipe-to-delete.

Iconless menus – another effect of the toxic minimalism trend. Icons in menus such as the mobile web browser and device settings help finding items faster!

In 2014, Samsung removed icons from the upper right menu of their mobile Internet browser. At some point, roughly 2017, they realized it was a bad idea and brought them back. Could've told ya that earlier. 😁

Smartphone and Android OS users in 2013:
“I wonder which features they will add this time!”

Smartphone and Android OS users in 2022:
“I wonder which features they will remove this time!”

Web designers should seriously stop using this ultra-slim Monsterrat font.

If you need a modern/futuristic-looking font for your web site, consider using Futura or Noto Sans / Open Sans, or Proxima Nova. If you really, really want Monsterrat, don't make it so slim that it becomes barely readable for the sake of trying to look wannabe-"modern". You are just humiliating yourself.

I despise it when software developers remove features because "too few people use them".

Is this what those shady telemetry features are for? So they can pick which useful features to get rid of because some computer rookies whined that it is "feature creep" rather than just ignoring it?

Now I have to fear losing useful (or at least occasionally convenient) features each time I upgrade, such as Firefox ditching RSS, FTP, and the ability to view individual cookies. The third can be done with an extension, but compatibility for it might be broken at some point, so we have to wait for someone to come up with a replacement.
Also, the performance analysis tool in the developer tools has been moved to an online service ("Firefox profiler"). I hope I don't need to explain the problems with that.

But perhaps the biggest plunge in functionality in web browser history was Opera version 15. That was when they ditched their native "Presto" browsing engine for Chromium/Blink, and in the process removed many features including the integrated session manager and page element counter.

The same applies to products such as smartphones. In the early 2010s, it was a given that a new smartphone should cover all the capabilities of its predecessors in its series, so users can upgrade without worrying a second that anything will be missing. But that blissful image was completely destroyed with the Galaxy S6. (There have been some minor feature removals before that, such as the radio and the three-level video recording bitrate adjustment on the S4, but that's nothing compared to what was removed with the S6.).

Whenever I update software to a new version or upgrade my smartphone, I would like it to become MORE capable, not LESS (and to hell with that "less is more" nonsense).

Make sure your software does not lose data when improperly quit, and does not allow deletion without a proper confirmation dialogue.

I have experienced pre-installed voice recorder applications that leave behind an unsalvageable corrupt file if the smartphone shuts down due to running out of battery charge, or powers off due to battery undervoltage (as a result of an aged battery).

As often, third-party software beats pre-installed software, and the voice recorder "ASR" by "NLL apps" leaves behind a playable file when unexpectedly quit. Might be because it uses the OGG vorbis format rather than M4A or 3GP audio.

Also, the camera software of the Samsung Galaxy Pocket smartphone from 2012 (which was crap anyway) would discard a video file if the recording was quit through the "back" navigation key.
Perhaps this was done deliberately, but it is a terrible idea due to the possibility of accidents happening.

Some gallery software for Android lets the user delete photos and videos by swiping vertically. After this, a so-called "toast" notification appears with an undo button. If not responded to within seconds, or when tapping next to it due to stress, the photo or video is gone. This is, needless to say, terrible design.

A birth defect of Google Chrome is that if one navigates away from a page or presses CTRL+S again while it is being saved, the saving of the page is cancelled. It was like this in Google Chrome since the beginning. This software birth defect was inherited by other Chromium-based browsers like Edge and Opera.

It's 2022 and people still believe USB sticks and external card readers are a replacement for memory card slots.

They're not. SD cards have a standardized form factor and do not protrude from memory card slots, but external card readers and USB sticks do.

Just like smartphones, laptops are increasingly ditching the SD card slot or replacing it with microSD, which has less capacity, lower life expectancy and data retention span due to smaller memory transistors, worse handling, and no write-protection switch.

Not only should full-sized SD cards be brought back to laptops, but also brought to smartphones. There might soon be 2 TB SD cards, meaning not one second of worrying about running out of space for years. That would be wonderful.

People want a computer for their pockets, not a locked-down glorified iPhone.
Google does not quite seem to get that.

Is there any way to view my devRant post and comment history beyond the 25 last items?

The comment page on my profile only shows the 25 last comments, and nothing loads at the bottom. How to view anything older than that?

Some mobile file managers kick me back to the beginning after selecting items for copying or moving.

When tapping on "copy" or "move" after selecting files/folders, some file managers like ES File Explorer (back when it was popular) conveniently remain in the current directory, whereas the stock Android file manager and many vendors' pre-installed file managers like that of Samsung kick me back to the initial directory. On phones with MicroSD, that's the storage selector, and on phones without, that's /storage/emulated/0/.

If I wanted to move files into a sub folder of the currently viewed directory, I have to navigate all the way back to that current directory, which is, needless to say, annoying.

Who thought it was a smart idea to kick the user back to the initial directory? But vendors' pre-installed file managers tend to be garbage anyway. Samsung's "My Files" file manager does not let me enter file names longer than 50 characters, does not let me change the extensions of files, does not support selecting files from search results or jumping to their parent directory, does obviously lack range selection, hides the status bar while opened (what's the point of that?!), its search feature is slow and sometimes crashes, and it can only search the entire device storage or memory card and not individual directories.

It's almost like Samsung deliberately tried to design a file manager as terrible as they possibly could.

I just lost a comment and had to rewrite it because I clicked a millimetre under the "post" button.

On new posts, the text remains in the box and can be edited the next time, but not on comments.

Perhaps I should get used to navigating to the "post" button with the tabulator key (↹).

It would be even better if CTRL+Enter did send.

What is your opinion on eSIM (embedded SIM)?

Now that Apple has built the first smartphone without modular SIM, it is, as history shows, only a matter of time until the same vendors who mock Apple for doing this will hypocritically follow Apple in implementing it themselves. There will be an outrage, but it will fade and the new restriction will be tolerated.

To me, "eSIM" appears like an euphemistic / euphemSIMtic (pun intended) marketing term, like calling non-replaceable batteries "eBatteries" ("embedded batteries") would be. It is less modular and more locked-down.

It's 2022 and Firefox still doesn't allow deactivating video caching to disk.

When playing videos from some sites like the Internet Archive, it writes several hundreds of megabytes to the disk, which causes wear on flash storage in the long term. This is the same reason cited for the use of jsonlz4 instead of plain JSON. The caching of videos to disk even happens when deactivating the normal browsing cache (about:config property "browser.cache.disk.enable").

I get the benefit of media caching, but I'd prefer Firefox not to write gigabytes to my SSD each time I watch a somewhat long video. There is actually the about:config property "browser.privatebrowsing.forceMediaMemoryCache", but as the name implies, it is only for private browsing. The RAM is much more suitable for this purpose, and modern computers have, unlike computers from a decade ago, RAM in abundance, which is intended precisely for such a purpose.

The caching of video (and audio) to disk is completely unnecessary as of 2022. It was useful over a decade ago, back when an average computer had 4 GB of RAM and a spinning hard disk (HDD). Now, computers commonly have 16 GB RAM and a solid-state drive (SSD), which makes media caching on disk obsolete, and even detrimental due to weardown. HDDs do not wear down much from writing, since it just alters magnetic fields. HDDs just wear down from the spinning and random access, whereas SSDs do wear down from writing. Since media caching mostly invovles sequential access, HDDs don't mind being used for that. But it is detrimental to the life span of flash memory, and especially hurts live USB drives (USB drives with an operating system) due to their smaller size.

If I watch a one-hour HD video, I do not wish 5 GB to be written to my SSD for nothing. The nonstandard LZ4 format "mozLZ4" for storing sessions was also introduced with the argument of reducing disk writes to flash memory, but video caching causes multiple times as much writing as that.

The property "media.cache_size" in about:config does not help much. Setting it to zero or a low value causes stuttering playback. Setting it to any higher value does not reduce writes to disk, since it apparently just rotates caching within that space, and a lower value means that it just rotates writing more often in a smaller space. Setting a lower value should not cause more wear due to wear levelling, but also does not reduce wear compared to a higher value, since still roughly the same amount of data is written to disk.

Media caching also applies to audio, but that is far less in size than video. Still, deactivating it without having to use private browsing should not be denied to the user.

The fact that this can not be deactivated is a shame for Firefox.

How to make productive use of computer freeze times?

Is there any way to utilize the time where a computer violates the purpose of its existence by not getting work done?

On Dailymotion, failed uploads count towards the 24-hour rate limit.

Dailymotion has a rate limit of somewhere between 10 to 15 videos (appears to vary). I experienced a glitch where I dragged 10 videos into the uploader (the highest number; years earlier it oddly was 22), and none of the uploads would start. However, it still counted towards the daily rate limit, immediately blocking me from uploading for 24 hours. I have a slight suspicion that this failure was deliberate.

Also, that rate limit is indiscriminate of video size. A gigabyte-sized 4K video counts equally towards the rate limit as a 7 MB 240p video.

Pull-to-refresh in mobile web browsers is useless and annoying.

In mid-2019, the #disable-pull-to-refresh-effect option was removed from chrome://flags on Chrome for Android (version 76) for no apparent reason. The top answer in the Google product forum was to beg for this option to be reinstated through the browser's feedback form ( http://web.archive.org/web/... ). Needless to say, that has been futile.

Why is that a problem? The pull-to-refresh gesture not only is unnecessary due to the quickly accessible refresh button in the menu right next to the URL bar, but also causes unsolicited refreshes when quickly scrolling to the top of the page. This drains both the battery and the mobile data plan, in addition to adding an annoying delay.

I would like to use my web browser like a web browser, not a social media app. Besides, the Twitter web app has its own pull-to-refresh implementation in the notification feed.

Without pull-to-refresh, the user has the freedom to scroll up quickly without risking inadvertently reloading the page. If media was playing while an unwanted pull-to-refresh occurs, the user needs to seek for the last playing position, which could take upwards of a minute if the last position is unknown.

Imagine a desktop/laptop web browser reloading because you scroll against the top. Imagine you reach the top of the page but you have not stopped turning the scroll wheel yet, and then a white circle with a blue spinning refresh icon appears at the center top of the window and the page, and then you have to wait for the page to finish loading, and you also need to seek the last playing position of a video or audio track. Wouldn't that be ridiculous?

Any web browser vendor that enforces pull-to-refresh on its users basically begs users to seek an alternative.

Any file manager without range selection is basically crippled.

Desktop PC file managers had the ability to select many files at once since at least the 1990s, yet smartphone file managers typically still lack it as of 2022. This means if I want to select a range of files, I have to tap each file individually. That's OK for - like - 20 files, but not for 1100 files. I'd need more time to select those files than the transfer would take, and if I accidentally hit anything that closes the app, I can start all over again. <sarcasm>That is how I wish to spend my day.</sarcasm>

In the early 2010s, ES File Explorer brought a dragless range selection feature, where only the first and last item had to be highlighted and a button pressed. This means over 5000 items could be selected in 10 seconds: tap item A, drag the scroll bar, tap item B, tap range selection icon, then done! But then Google came and said "sorry, you can't have nice things" (not vocally but through actions), and forcibly disabled write access to the microSD card to third-party applications. The only way to evade this restriction was through rooting.

Then, Google "blessed" us with storage access framework and then iOS-like scoped storage "to protect us". https://xda-developers.com/android-... . Oh, thank you for your protection by taking freedoms away!

The pre-installed file manager of Android still lacks range selection THIRTY YEARS after desktop computers came pre-installed with this feature. Shame on you, Google. This isn't innovative.

If Google will implement range selection, I guess they will make it half-assed by implementing drag-to-select, which is hardly more useful than individual tap selection for thousands of files. Then they tell us "you wanted range selection, here you are! Now don't bug us.". Sorry, but users don't want half-assed drag-to-select, but real tap-A-B-selection and a draggable scroll bar.

Some mobile file managers even lack a draggable scroll bar, meaning if I want to go near the center of the list, I have to swipe up like a dog or cat licks water from a bowl.

That's it, YouTube. I am turning my ad blocker on again.

After this Lion King movie advertisement https://youtube.com/watch/... SCREAMED into my ear, I have had enough. Out of generousity, I turned off my ad blocker to let ad breaks play to support creators, and also out of slight curiousity which advertisements would be served to me. But after this aural abuse, I am turning it on again for the foreseeable future.

Randomly generated CSS class names make customization of sites much more difficult.

Randomized gibberish CSS class names like "r-acJ79b" are used by some sites like the new Reddit and the new Twitter web apps, which makes it impossible to customize the appearance of the site and to hide "trending" spam. The only way hide annoying and spammy page elements is through user scripts which scan the page for it every second and then hide it. But until then, it appears on screen for a short period.

I once thought this is caused by react JS, but the react JS front end of the video platform "Odysee" does not have randomized CSS class names.

ENOSPC = random things go wrong.

There are many synonyms for ENOSPC, like "disk full", "space storage full", "space storage exhausted", "no more space left on device", and those other repulsive errors. For the sake of simplicity, I am going to refer to it as ENOSPC.

If you are in this condition on the operating system partition, get out of it quickly or random things will go wrong. Text editors which write directly to a text file rather than creating a temporary file and then replacing the text file could end up blanking the text file, softwares' configuration files might fail saving which causes a reset, and web browsers might spontaneously reset cookies and lose history.

For example, Firefox has created a gap in the web browsing history, as shown here. The history that is now memory-holed initially appeared to have been recorded successfully. Apparently, a failed write to the places.sqlite database when closing the browser created this gap.

If a video player's pause button is replaced by a loading animation, one has to wait for the buffering to finish until pressing pause.

News sites with infinite-scrolling are so damn annoying.

A new random article I am not interested in suddenly loads under the current news article when skimming through it by dragging the scroll bar, and then throws me far down into unknown territory due to the sudden change of the height of the page.

It also happens similarly on Imgur photo galleries: when I drag down the scroll bar to quickly seek through the images, the "explore posts" section suddenly loads hundreds of "trending" and "viral" (uninteresting junk and spam) photos under the gallery, and since this adds lots of height to the page, I get pulled right into it and my window is full of such posts. Both distracting and memory-consuming.

YouTube's infinite scrolling comments and video lists are acceptable as of writing, since they are on-topic, and no off-topic "trending" spam, and they do not load too much at once, which does not throw me down too far.

Quote from https://elite-strategies.com/infini... :

> The footer of a website is like the shoes of a person, it ties the whole outfit (or website) together. Footers are awesome because it gives you a chance to tell people where to go when they reach the bottom of the page.

Unix Epoch should have started in 2000, not 1970.

Those selfish people in the 1970 who made up the Unix epoch had little regard for the future. Thanks to their selfishness, the Unix date range is 1902 to 2038 with a 2³² integer. Honestly, who needs dates from 1902 to 1970 these days? Or even to 1990? Perhaps some ancient CD-ROMs have 1990s file name dates, but after that?
Now we have an impending year 2038 problem that could have been delayed by 30 years.

If it started on 2000-01-01, Unix epoch would be the number of seconds past since the century and millennium.

MTP is complete garbage. I want mass storage back.

The media transfer protocol (MTP) occasionally discovers new creative ways of failure. Frequently, directory listings take minutes to load or fail to load at all, and it freezes up infinitely (until disconnected) when renaming an item, and I can not even do two things simultaneously.

While files are being moved, I can not browse pictures or watch videos from the smartphone.

Sometimes, files are listed with the date 1970-01-01 (Unix epoch) instead of their correct date. Sometimes, files do not appear at all, which makes it unsafe to move directories from the device.

MTP lacks random access. If I want to play a two-gigabyte 4K 2160p video and seek in the video, guess what: I need to copy it to my computer's local mass storage first because MTP lacks random access.

When transferring high numbers of files, MTP has to slooooowly enumerate (or "prepare" or "calculate the time of") them all, which might even take longer than mass storage would need for the entire process. This means MTP might start copying or moving the actual files when mass storage is already finished.

Today, the "preparing to move" process was especially slow: five minutes for around 150 files! How am I supposed to find out what caused this random malfunction?

MTP sometimes drives me insane. I want mass storage back, at least for the MicroSD memory card, which uses a widely supported file system.

Imagine a 2010 $100 Android phone is better at file transfer than a 2022 $1000 Android phone (or iPhone, for that matter).

If the computer freezes during a drag-and-drop operation, you have to hold the mouse button and wait until it is unfrozen to avoid dropping the file in a wrong place.

Computer freezes can be unpredictable. For example, you might click on a location on screen that will have a different effect after the computer unfreezes because something moves or a window is opened/closed, or a keyboard press is not registered. For example, if you start dragging a file and then press CTRL during the freeze, it might not register the CTRL press and end up moving the file instead of copying it.

When file managers copy and delete files within the same partition instead of moving or renaming them…

When Google's Storage Access Framework was introduced, it did not feature a move command, so file managers just resorted to copying and deleting files within the same storage. Not only does this cause needless wear and is much slower, but it also destroys the date/time attribute (it gets changed to current).

When moving files through MTP (miserable transfer protocol, used for connecting smartphones to PC), they are also copy-deleted. This makes moving a 20-Gigabyte DCIM folder impractical. Also, if one cancels the operation, it might end up whoopsie-daisy deleting some files from the source before they have been transferred.

MTP is so bogus that it is incapable of a simple operation that would JustWork™ on mass storage devices. Not to mention, MTP lacks parallelism and its directory listing loading it S-L-O-W. Upwards of a minute for just 1000 files. Sometimes, it fails loading at all.

Also, trying to rename a file through MTP using the terminal through GVFS, even if just within the same folder, it copy-deletes it. If I want to rename a 1 GB 2160p 4K video in a highly populated DCIM folder, I can not do so through the terminal. At least, the 4K video has a time stamp in its internal metadata, but it still renames slowly and adds needless wear to the smartphone's flash memory.

Firefox and Chrome removing FTP support in 2021 was a terrible decision.

Web browsers were simply the more convenient FTP browsers, more than file managers, due to browsers' built-in multimedia capabilities like photo viewing and opening documents, distinct purple highlighting of already opened directories and files, browsing history, familiar mouse shortcuts like middle click for new tab, and no possibility of accidental writes due to a botched drag-and-drop operation or similar.

If I wanted to browse an FTP server in "read-only mode", web browsers used to be the preferred choice.

When user interface elements unsolicitedly change their position, something unexpected might be clicked.

For example, the search engine list at the bottom of the Firefox suggestion box that appears when typing something into the URL bar ("This time, search with:"). When the number of suggestions changes, the height of the box changes, and since the search engine list is at the bottom, its position changes too. This could happen milliseconds before I wanted to click on one, which causes either searching for something I did not look for, or closing the URL bar.

It also causes an uncertainty whether the buttons will remain in place, causing delays until clicking.

The same happens on the image context menu for images on the Kiwi browser. It shows a preview thumbnail on top of the options in the context menu, but since the context menu opens before the thumbnail loads, the appearance of the thumbnail pushes the options down. If this happens few milliseconds before one is going to tap on something, it causes one to tap on the wrong place.

In Firefox, refreshing and redirecting pages steal the URL bar.

When a page refreshes itself or redirects elsewhere while I am entering something into the URL bar, what I entered gets replaced with the URL of the target page that was redirected to, or the URL of the current page if it refreshes itself.

This makes the user vulnerable to spam pages that refresh themselves or keep redirecting to hijack the URL bar.

If this happens the fraction of a second before I press "Enter", Firefox web searches for the end of my search term with the target URL appended to it, for example if I entered "example search term", it would search for "ermhttps://www.example.org".

You'd think this would have been fixed by now, after over a decade, but no.