I often read Slashdot using Safari on my iPhone 6+. The mobile site has several very intrusive problems. Really, it's the most broken website I regularly browse. Many features that I can take for granted as working on other websites due to the nature of web browsers (e.g. the browser "back" button) simply don't work. I often resort to using the iPhone's features to bypass the mobile site to go to the desktop site instead. (If anybody is wondering how to do this: Hold down the "reload" button, and then choose "Request Desktop Site"). Specific problems with the mobile site include:
1) The 'back' button is broken. If I am on the home page, and I click on an article title, and then click some sort of option (e.g. "Outstanding") to filter down the returned articles, and then want to go back to the home page, the browser's 'back' button does not work. (Clicking it typically takes me to the site I was browsing before I started browsing Slashdot.) This is hugely irritating. If I want to go back to the home page and pick another story, I typically have to use the on-screen keyboard to type slashdot.org into the URL control again. Please Don't Break The Back Button!
2) In a situation such as described in 1), the "Stories" button at the top of the page doesn't work either. Clicking the "Stories" link to go back to the homepage only seems to work if no other links have been clicked since the story was clicked on from the homepage. If other options (e.g. "Outstanding") have been clicked, the Stories button either does nothing, or my click goes "through" it to whatever was under the button (which may be a random link from within the story comments, resulting in some surprising destinations.) The fact that the Stories button doesn't work is actually kind of ironic, since a simple link to "slashdot.org" would be trivial to implement, work just fine, and not have the problems that the current implementation does. Instead, it seems to be trying to keep some sort of memory as to what the previous page was, but whatever it's doing doesn't work.
3) The set of default filtering options when I enter a story page, even without logging in, should be such that I see a small but reasonable number (say, 20-30) of top-rated comments. As things currently stand, I usually have to click something like "Outstanding" to get to a resonable filtering state, which triggers problem #2 that I mentioned above.
4) When I attempt to use filtering on a story's comments, the site attempts to filter out comments that are too low for the currently set threshold. However, the header of the filtered-out comments are displayed quite large, and the text "Filtered due to preferences" is also displayed quite large, with excess whitespace around it. The net effect is that the filtered-out comments take up almost as much space as they would have if they hadn't been filtered out, which defeats the purpose of filtering them out in the first place. I think filtered out comments should have their headers displayed in font large enough to be (barely) legible, but otherwise use minimal space, and preferably be displayed completely on one line. They should not try to draw attention to themselves: They should be unobtrusive so I can focus on the comments that haven't been filtered out, and click on the filtered-out ones only if I want to get more details on a particular thread.