Slashdot Mirror


Experience the New Slashdot Mobile Site

After many months of effort, today we've brought the new mobile site out of beta. Featuring an interface optimized for touch devices, we think it's a huge improvement over the old mobile interface. You'll find comments easier to navigate, the most popular stories highlighted at the top of the page, and a surprisingly pleasant interface for navigating old polls. We've also spiffed up user profiles, resurrecting and improving the friend/foe system in the process. And that's not all: we're pleased to announce that you can login to Slashdot in general using various social media accounts, so if you use Facebook or Google+ there's no excuse not to enjoy the benefits of being a registered user, without the hassle of creating yet another account. Our weblog has a few more details. As always, if you encounter any issues let us know by mailing feedback@slashdot.org.

90 of 384 comments (clear)

  1. No thanks by Desler · · Score: 5, Insightful

    No thanks. It's pretty terrible. Can you also stop the chooser popup please? I want to use the classic site without constantly bombardment with a popup.

    1. Re:No thanks by motang · · Score: 4, Insightful

      I second that, the classic is great!

    2. Re:No thanks by SydShamino · · Score: 4, Insightful

      The constant popup is annoying. I would use the mobile site, though, except when I said "yes" to the popup a few weeks back, then tried to reply to a comment, Safari crashed on my phone.

      Can you let us set a user preference in our account as to whether we want the mobile site or not on mobile devices? Bonus points for letting us set it on a per-browser-string basis, so I could use the mobile site on my phone (assuming it doesn't continue to crash) but the full site on my tablet.

      --
      It doesn't hurt to be nice.
    3. Re:No thanks by Anonymous Coward · · Score: 5, Insightful

      Roll Back!!! Roll Back!!! Roll Back!!!

      abort, abort, abort!!!

      News flash, techie people prefer functionality to glitz. I prefer the desktop site on my phone. New mobile version isn't appealing.

    4. Re:No thanks by Fallon · · Score: 2

      I get to Slashdot via my RSS feed, which goes directly to the article. The pop-up then boots me back to the root website rather than staying on the article I was trying to view if I tell it to use mobile. On Android, if you scroll down at all, you can no longer click on the mobile or classic buttons too, extremely annoying. You have to scroll up to the top of the page to be able to click on the buttons & make it go away, despite the pop-up scrolling down the page to cover stuff up.

    5. Re:No thanks by jest3r · · Score: 4, Informative

      I third that. I don't understand why we need a dumbed down version of the site when my phone can display the full site just fine? I'v enever had a problem browsing the full site and prefer it.

    6. Re:No thanks by pmontra · · Score: 4, Interesting

      I fourth that. And fix the theme so it works with Firefox (mobile). It's a blank page right now. Not that I use FF on my phone often, I'm using Dolphin most of the time but I wouldn't mind if more site were compatible with more browsers.
      By the way: polls don't work in the mobile theme in Dolphin: the options don't display. I think I'll keep using Classic.

    7. Re:No thanks by NeutronCowboy · · Score: 2

      I use stock Dolphin browser, and haven't disabled cookie storage. However, I do get the pop-up every single time I view a story on slashdot.

      --
      Those who can, do. Those who can't, sue.
    8. Re:No thanks by Tempest_2084 · · Score: 3, Interesting

      Can I fifth this or is it redundant by now? The mobile site doesn't offer anything worth switching for and I'm getting tired of that damn popup.

    9. Re:No thanks by Sancho · · Score: 4, Informative

      Chrome on iOS 6.1. I've been asked over and over. Also, the cardinal sin of "redirecting from a deep link to the front page of the mobile site" was committed, apparently :(

      I'm on a discussion page and I get redirected to the front page of m.slashdot.org. Horrible, horrible!

    10. Re:No thanks by jennyscript · · Score: 5, Informative

      Hi, I'm a mobile dev responsible for the new app. The mobile site chooser popup is designed to go away and not reappear when you choose "Classic" but obviously you guys are not seeing that behavior. We'll get a fix out soon so the site will really remember you don't want to use the mobile app. Sorry about the extra popup in the meantime.

    11. Re:No thanks by Psyborgue · · Score: 2

      It only works if you're scrolled up to the top of the page. If you scroll down, you can't click the button.

    12. Re:No thanks by JWW · · Score: 2

      I second that. Why, why, why do the people who build the mobile sites assume, 'well they clicked on this link, but I'm sure they'll be fine with the home page, or this other unrelated page'

      That is awful, it renders the concept of a hyperlink, the bedrock of the web, unpredictable for mobile sites. (i.e. the user's thinking they will actually get linked to what I want or will something else completely pop up).

      Yep, its a cardinal sin of mobile sites. This meme needs to get some traction out there.

    13. Re:No thanks by jackb_guppy · · Score: 5, Insightful

      And I thought it was just me.

      Issues:
      1) does not scroll smoothly or nicely
      2) scrool is thought of 1/2 time as a cick - so off to storie no down to next page.
      3) I do not what tracking by facebook or others on Slashdot site
      4) pop overs are annoing specially when the X is to small to touch or acts like click. Touch interfaces need to big enough for touch! Fat fingers are fat fingers!

    14. Re:No thanks by UnknownSoldier · · Score: 2

      Agreed 100% !!

      The mis-scrolling and mis-clicking is the most frustrating aspect of the UI.

      The _one_ thing I DO like is the lack of margins. There is no sidebar forcing all the comments to be indented wasting whitespace.

    15. Re:No thanks by nmb3000 · · Score: 5, Informative

      It's also a blank page if you use AdBlock+ with EasyList. The rule ||googletagservices.com^$third-party breaks their requirement for Google Tag Services, and they weren't bright enough to handle this failure gracefully. Same with NoScript -- unless you've allowed googletagservices.com (and I've managed to browse the web fine for over a decade without it) then it's blank-screen for you.

      Pretty sad.

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    16. Re:No thanks by nschubach · · Score: 2

      The popup that comes up to ask you to switch to the mobile site seems to have a fixed position hit boundary. If you scroll the page a bit, the buttons no longer work for me on Android ICS.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    17. Re:No thanks by beeudoublez · · Score: 3, Insightful

      Deep linking/routing is coming soon. We're working out out the edge cases right now.

    18. Re:No thanks by beeudoublez · · Score: 3, Interesting

      We found the bug with persistent popups and we're working on a fix right now. Thanks for the feedback!

    19. Re:No thanks by beeudoublez · · Score: 2

      This is something we're working on. Soon you will be able to open the newsletter links from your device and be taken to the mobile site.

    20. Re:No thanks by beeudoublez · · Score: 2

      Hey Mr. AC, we are working on making sure you go straight to the article, it bugs us too. Thanks for your patience.

    21. Re:No thanks by jennyscript · · Score: 2

      Thanks for the bug reports. I've added tickets for them.

    22. Re:No thanks by jest3r · · Score: 3, Funny

      Best new feature of Mobile Site:

      The link at the bottom right corner that says: Full Site.

    23. Re:No thanks by Psyborgue · · Score: 2

      But I don't want the full site. I want the current mobile site that is only subtly different from the desktop site. This is a shitty replacement for something that isn't broken and actually works so well, most people like it.

    24. Re:No thanks by the.aham · · Score: 2

      I third that. I don't understand why we need a dumbed down version of the site when my phone can display the full site just fine? I'v enever had a problem browsing the full site and prefer it.

      My one annoyance with viewing the full site on a mobile browser is the comment slider doesn't work/can't be used -- that slider determines how many full/abbreviated comments I see (which, sometimes I want to modify). Using the slider requires a click+drag motion on the desktop, which isn't necessarily possible on mobile. On Chrome for Android, these two things happen: (1) tap+drag in a web browser means you scroll the page or navigate to the next tab; or (2) a long-tap+drag means you're selecting text.

    25. Re:No thanks by JWW · · Score: 3, Insightful

      I am impressed to be hearing from the developers in this thread.

      Thanks.

    26. Re:No thanks by Evtim · · Score: 2

      Sorry to report that it does not even show on my phone - I get white screen. HTC Desire. Could be that my Android version is too old (2.2) or something. Not my fault - I don't get OS updates from HTC. I hope it gets fixed.

  2. m./. /.'ed? by DogDude · · Score: 2

    Doesn't do anything on my phone. The "loading" bar just sits there loading, and no articles ever come up. Perhaps this was announced a bit prematurely...?

    --
    I don't respond to AC's.
    1. Re:m./. /.'ed? by Internal+Modem · · Score: 2

      It requires JavaScript to work.

    2. Re:m./. /.'ed? by TheSpoom · · Score: 2

      In that case, it should have a noscript element telling you to turn on Javascript, at the least.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    3. Re:m./. /.'ed? by AmiMoJo · · Score: 2

      It loads on my Galaxy S III but as soon as you try to drag and scroll it opens the article under your finger. I submitted a bug report months ago and figured it would be fixed before launch, but apparently not.

      It works okay if I switch to Chrome.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  3. Sorry, not so good by C+R+Johnson · · Score: 4, Insightful

    Every time I have tried the new mobile site my experience was not good.
    I can't even scroll down easily and when I do it jumps into an article that I didn't select.
    And it doesn't look good.
    Maybe it's opera mobile's fault. Maybe you need to think on this some more.

    --
    The alternative to limited government is unlimited government.
    1. Re:Sorry, not so good by Psyborgue · · Score: 5, Informative

      No. It behaves like shit on mobile Chrome too.

    2. Re:Sorry, not so good by beeudoublez · · Score: 3, Insightful

      What version of iOS are you running?

    3. Re:Sorry, not so good by styrotech · · Score: 3, Funny

      What version of iOS are you running?

      Hmmm... I think I've spotted the problem.

  4. Re:"New" Mobile Site? by Psyborgue · · Score: 2

    There was a mobile site. It only differed slightly from the desktop site so it wasn't too much of a shock.

  5. Re:Tried it by Psyborgue · · Score: 2

    I was thinking the same. If this is what our new overlords think we want maybe it's time to create something new.

  6. What about ipv6? by DeAxes · · Score: 2, Interesting

    Forget mobile, I'm still waiting for Slashdot to have a AAAA record.

  7. Re:I like it but... by Desler · · Score: 2

    But that would require actually expending effort to fix things. That's never been the Slashdot way. They couldn't even fix the pagination bugs in the version before they did the whole discussion overhaul. They want to chunk out new code, not do "boring" software maintenance.

  8. Hate hate hate by Anonymous Coward · · Score: 4, Funny

    I hate it and it's terrible and it sucks and I hate it and it's different and why did it change and it's terrible and it's different and it's not working on my obscure phone so it's useless to everyone and it sucks and nobody should ever ever ever ever ever use it ever again and I don't like it. It's stupid. I'm a nerd, so I know this sort of thing. I'll click the link later when I've got time to look at it.

  9. Do Not Want by SuricouRaven · · Score: 5, Insightful

    "we're pleased to announce that you can login to Slashdot in general using various social media accounts,"

    Why would I want to do this? On Slashdot, of all the sites on the internet, people value their privacy. Perhaps we don't want the data-miners at Facebook to monitor our slashdot usernames, cross-correlate post times against estimated work hours and calculate our estimated slacking-off coefficient to better target advertisments? I'm entirely happy to have lots of seperate accounts - it beats 'One Account to Rule them All.'

    1. Re:Do Not Want by Bodero · · Score: 4, Insightful

      Why would I want to do this?

      Maybe you wouldn't. And maybe someone else does. That's why it's an option.

    2. Re:Do Not Want by jones_supa · · Score: 3, Interesting

      By the way, have you guys noticed that when you open a Slashdot comment in a separate page (by clicking the message ID link) and then close that page, it shows "Working..." at the bottom for a while, possibly phoning home that you closed that comment.

    3. Re:Do Not Want by Unknown+Lamer · · Score: 5, Informative

      There's no evil conspiracy here (see the permissions the facebook "app" requests for example: just your name and email address); we just wanted to make it easier for people to login. I personally wouldn't use it (but I'm in the set of people who only grudgingly use facebook in the first place since everyone else is doing it), but folks immediately started using it, even without us mentioning that it existed.

      Luckily, it's just an option, and will never supersede the native account system. Different strokes for different folks and insert other appropriate cliches here.

      --

      HAL 7000, fewer features than the HAL 9000, but just as homicidal!
  10. Too Sensitive to Touch by Internal+Modem · · Score: 3, Insightful

    You guys did something wrong. In mobile Safari when I try to scroll down the page, it often detects my touch as a click and opens a story I don't want to read. This isn't a problem with the browser because it doesn't happen on any other mobile site. It seems to be a problem with the size of your click-able regions. I'm not sure what kind of beta testing was done, but it obviously wasn't enough.

    1. Re:Too Sensitive to Touch by chihowa · · Score: 2

      I specifically reported this during the alpha and the beta and nothing at all changed. In fact, from a user perspective, nothing at all has changed from the alpha to the launched site, so I don't think they gave a shit about bug submissions. Since alpha, the short summaries, fucked up scrolling, weird swiping behavior, etc have all been reported by many users.

      --
      If you want a vision of the future, imagine a youtube comments section scrolling - forever.
  11. Worthless! by Anonymous Coward · · Score: 3, Informative

    You IGNORED every constructive comment that people made regarding this mobile interface. You INSISTED on doing it the stupid way.

    Nobody is going to use your mobile interface when it makes browsing slashdot MORE WORK than before. We can't even get full article summaries on the front page! What kind of bullshit is that?

    And I think it's just wonderful how every mobile user gets a banner suggesting they switch to the much more heavily ad-strewn mobile interface. Congratulations slashdot, you've managed to create a mobile interface that is WORSE than the full site on just about every level. way to ignore your customers.

  12. The original site is better, because: by knarf · · Score: 5, Informative
    1. it is faster
    2. I can open a bunch of topics in new background tabs for later perusal
    3. did I mention it was faster?
    4. it works without JavaScript

    It has one disadvantage: I have to click away a popup which asks me to use the new site, time and again...

    --
    --frank[at]unternet.org
    1. Re:The original site is better, because: by beeudoublez · · Score: 2, Interesting

      We're using HTML5 local storage to save your preference for this popup - do you have that turned off?

    2. Re:The original site is better, because: by Desler · · Score: 3, Insightful

      Your code is broken, then.

    3. Re:The original site is better, because: by TheSpoom · · Score: 3, Informative

      I'll say it here too, your code is broken. It's not working. I get the popup on every page.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    4. Re:The original site is better, because: by TheSpoom · · Score: 2

      By the way, I can say this with some authority; we use localStorage (and sessionStorage) on a mobile web app here at my work, and it works fine on my phone there.

      I suggest you guys look into using store.js for a consistent interface even when localStorage doesn't work.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
  13. scrolling lag by Anonymous Coward · · Score: 2, Informative

    The mobile site lags badly while scrolling on an Android device using chrome. Any chance of fixing this?

  14. Needs work by jimpop · · Score: 5, Informative

    When following a link to /., if I answer Yes to the pop-up prompt, i get redirected to http://m.slashdot.org/ and NOT the story I was linking to

    1. Re:Needs work by Dancindan84 · · Score: 5, Funny

      Hi! I'm a server!
      http://xkcd.com/869/

      --
      "Always forgive your enemies; nothing annoys them so much." - Oscar Wilde
    2. Re:Needs work by jimpop · · Score: 3, Insightful

      Dude, Thanks for fixing this. Awesome effort!

  15. A little better by bsharitt · · Score: 3, Interesting

    The old mobile site wasn't really mobile, so I guess anything is better, though it's a pretty slow and heavy site it seems. It looks to be working in Firefox for Android now, that's an improvement over the last time I used the beta.

    So how long until /. wraps up the new mobile site in an app wrapper and advertises a "mobile app" for iPhone and Android like seemingly every other website out there?

  16. Classic by Bogtha · · Score: 3, Insightful

    WeÃ(TM)ve built the mobile user experience with the future in mind

    And yet Slashdot is still incapable of handling nonASCII characters. Unicode is over 20 years old, guys.

    Is there any reason why this was done as a separate site and not with a responsive design? Separate mobile sites are the old-fashioned way of doing things.

    --
    Bogtha Bogtha Bogtha
    1. Re:Classic by Desler · · Score: 4, Insightful

      Yes but Unicode and IPv6 are clearly just fads. They aren't nearly as important as Facebook/Google+ login and filling out the buzzword bingo card with all the fad frameworks:

      We built this app using the latest technologies and frameworks such as Backbone, Zepto, Underscore, Hamstache, Jasmine, and Sass.

  17. Go away with this crap ! by thrill12 · · Score: 2

    Finally, get ready for... [rant mode on]
    I am sick of having the message "would you like to try beta or classic" every time when I browse Slashdot on my Chrome browser under my Nexus. I want the *regular* site, or something as close to it as possible. I even cannot click on the "classic" button... First lesson for new designs: if someone says *not for me* then leave them alone or they will leave your site alone.
    Why should I have to press "request desktop site" each time I simply want to read an article ? This is not a PALM III where I zoom in with the Plus and Minus keys: my browser is more powerful than a Windows IE6 browser (feature wise), faster than many regular old Pentium IV's and pinching is good enough to get around the site.

    [rant mode off]

    --
    Slashdot: stuff for news, nerds that matter, matter for news, stuff that nerd
    1. Re:Go away with this crap ! by Psyborgue · · Score: 3, Informative

      You have to be scrolled all the way to the top of the screen to click the classic popup in mobile Chrome my Nexus. If you scroll down the popup stays on the screen but tapping it does nothing. You have to scroll back up, and then tap. It's annoying as fuck, I know.

  18. Unusably slow, UI provides no feedback by zenyu · · Score: 4, Informative

    When I click on something it takes forever for the UI to respond. There is no visual feedback so until I realized that the new UI was just 200x slower than the old one I clicked on the things 5-10 times thinking the clicks just didn't take the first n-1 times.

    I've obviously switched back to using the desktop site on my mobiles, but there is a popup on every page load asking me to try the mobile site! Sheesh!

    You need to fire the contractors involved and hire some people who know what they are doing.

  19. So so by Anonymous Coward · · Score: 3, Insightful

    I jused the (new) mobile site for the first time on an iPhone 4S and had no issues whatsoever. Although I like the overall look and feel of the site I don't think a redesign was all that necessary. Sorry, devs :) But don't listen to the haters, they wouldn't like it no matter how it had turned out!

  20. Holy crap that was awful by EmagGeek · · Score: 4, Informative

    What the fuck were you guys thinking?

    An, in general, what the fuck is going on with people designing user interfaces these days? It seems everywhere you go there's yet another abortion of a user interface.

    Seriously...

  21. scrolling is impossible by Isara · · Score: 2

    And it's making it difficult to navigate the site. Plus, there doesn't appear to be a way to get back into classic once you're in mobile. Looks ok, just needs functional work

    --
    BOOP!
  22. On a decent tablet/phone the regular site is fine. by BlueKitties · · Score: 2

    I browse /. on my Nexus 4 and iPad, both of which display the full /. site perfectly. The layout of the site downscales rather nicely, and I've never had an issues with it. The "mobile" site, on the otherhand, is not my cup of tea. It just doesn't feel very slashdotty.

    --
    "Sorrow is better than laughter, for by sadness of face the heart is made glad." [Ecclesiastes 7:3]
  23. Fire your product manager by pherthyl · · Score: 5, Insightful

    The new site is terrible. I really tried to use it for a couple weeks but had to go back (iPhone 4).

    The new site is significantly slower first of all, which essentially kills it right off the bat. Speed should be your #1 feature. If you can't make it faster on mobile, don't bother with the redesign just tweak the existing layout.

    It's also very glitchy as others have pointed out.
      - Scrolling down often results in a click.
      - After the page loads it jumps to the top again if you scroll down too fast
      - transitions are glitchy and slow. Don't use them they don't add anything.

    As for the announcement it is just full of fail.

    >> We've built this new mobile interface optimized exclusively for your touch smartphones and tablets.

    Why? The revolutionary part of the iPhone was that it could handle regular desktop sites and we could do away with WAP. Now we suddenly need a special site again? Just make sure that the layout scales well and you're done for mobile on a site that is purely about content. It's a different story if you're something like an online retailer where people want quick access to a few key functions (search, store locator, inventory, my account, etc).

    >> Read comments and stories in a mobile-friendly view (no more squinting!)

    Never had to squint on the old site. what's the problem?

    >> Most popular stories shown right at the top

    If I passed by a story earlier in the day what makes you think I want to see it again?

    >> See beautiful achievement badges

    I have no words. This is so stupid.

    >> Show off your latest Gravatar

    Yep, that's why I'm here.

    >> We built this app using the latest technologies and frameworks such as Backbone, Zepto, Underscore, Hamstache, Jasmine, and Sass.

    So you jumped on the bandwagon of stupidly named frameworks and used all of them because that's the thing to do these days. Surprise surprise, the end result is too heavy.

    >> Since there are so many mobile devices and capabilities, we targeted webkit browsers, and Android versions above 2.3.

    Sounds like browser support got worse then. Say it like it is.

    >> We didn't start sketching the blueprints based on what we thought a mobile experience should be - we asked YOU.

    Ah, that's the problem then. Design by committee and it shows.

    1. Re:Fire your product manager by jackb_guppy · · Score: 2

      Thank you for breaking this down in a very meaningful manor. Maybe they will hear and FIX it.

  24. It's fucking worthless by Pseudonym+Authority · · Score: 3, Interesting

    No thanks. It takes forever to load, it looks like shit, and its generally terrible.

    Now take that stupid popup thing that tells me to go to the mobile site. If I want to see your shitty social-web2.1-scalable-turnkey-webdesigner-solution I'll go to the god damn site myself. Whoever wrote this should be ashamed.

  25. Threshold for Classic Discussion System (D1)? by jvj24601 · · Score: 3, Insightful

    I still use the Classic Discussion System (D1) and have my Threshold set to 2 (sometimes I reset to 3 or 4 as well). How can I have the mobile site honor that preference?

    1. Re:Threshold for Classic Discussion System (D1)? by vroom · · Score: 4, Insightful

      We have a feature planned to offer a way to toggle to threshold settings saved on site.

  26. Re:Tried it by Cinder6 · · Score: 5, Insightful

    I'm using it right now (though posting from my desktop). Honestly, it's a lot faster than the old site, and navigation is more friendly to touch devices. Most importantly, comments load better than before. With that said, two things bother me about it:

    1. The aesthetic is completely different from the desktop site, to the point that I wouldn't know it's Slashdot if it didn't say so at the top. This isn't a huge deal, but brand recognition is important.
    2. The article summaries are shortened on the front page, and you have to tap the headline in order to load the whole thing along with contents. This breaks up the site's flow and makes it harder just to peruse articles. Take, for instance, the following excerpt:

    Two economists at the St. Louis Federal Reserve have published a paper arguing that the American patent system...

    The shortened summary offers nothing of value to me; the headline is actually much more informative. What I think needs to happen is either enable full, unshortened summaries, or write a summary of the summary for mobile devices. One of those options is silly, the other is reasonable.

    --
    If you can't convince them, convict them.
  27. Re: It's ok by physburn · · Score: 2, Insightful

    Posting from my phone. Works ok with android!

  28. Re:Tried it by Anonymous Coward · · Score: 3, Funny

    Yeah. We could call it Reddit and then...

  29. Too funny by Jmc23 · · Score: 3, Interesting
    It sucks and apparently everybody but the designers think so. I wonder if the downfall of slashdot was when they started trying to run it like a business. Managers and designers that know nothing about their audience or apparently don't care. Though it makes sense to build an audience of idiots because idiots buy things. Nerds and geeks will roll their own.

    I really wish slashdot had an api to access posts so we could calculate the exact turning point. Definitely 2013 is when the tide has shifted.

    --
    Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.
  30. Windows Phone 8 by Toshito · · Score: 2

    I have windows phone 8 and the browser is not recognized as a mobile device, so no annoying popup for me!

    --
    Try it! Library of Babel
  31. Re:scrolling still broken by David_W · · Score: 2

    Go to the Play Store and get Firefox. You won't look back.

    Yes you will, or at least I did. I have no idea what causes this, but I've had several pages where when you scroll below the currently visible content, the newly displayed stuff turns fuzzy/blurry. If you only scroll half a screen you get a clear top half and messed-up bottom half. I can't imagine what causes this, but it was annoying enough that for now I'm trying other browsers... Dolphin seems to be doing well, but I miss my extensions. :(

  32. Re:Tried it by TheSpoom · · Score: 2

    Please, please, please let me know if a group comes together to make a new Slashdot. I'm a professional web developer, mostly backend PHP but I know Rails, wouldn't mind learning Python, am actively learning Node, and I'm very experienced with frontend stuff (jQuery, HTML 5, CSS 3, etc. etc.)

    I'm thinking keep the karma system almost exactly the same if not exactly the same, and shift to more crowdsourced article posting. Keep editors, but their job wouldn't be to choose the articles to post, their job would be to, well, edit the submissions for clarity, spelling, grammar, etc.

    Maybe even open source the base code? I know Hacker News did that, keeping a little bit of the secret sauce back (mostly anti-voting ring stuff). That would let us benefit from the open source community at large (which would fix problems in this new mobile site pretty quickly I would imagine).

    --
    It's better to vote for what you want and not get it than to vote for what you don't want and get it.
    - E. Debs
  33. 68/100 by Andrio · · Score: 2

    I ran it through this software I have at work called "Mobile Internet Testing Environment" and it got a "MITE score" of 68/100. It's based on best practices for performance of a mobile site. The slashdot mobile site got penalized for things such as not having the JS at the bottom, for having iframes, not combining css/js, one http request error, no alt tags for images, and others.

    --
    The Internet King? I wonder if he could provide faster nudity.
  34. Re:Doesn't work in laptop web browser by jennyscript · · Score: 2

    The mobile site is designed to work on Android and iOS browsers only. We haven't tested it much on desktop browsers, so I wouldn't expect it to work there. You'll see the best experience on the latest version of mobile Chrome/Safari, but it also should function in the latest mobile Firefox and Opera.

  35. Re:m.slashdot.org Chrome on XP? by jennyscript · · Score: 3, Informative

    If you really want to use the mobile site in desktop Chrome you can check "Emulate touch events" in the web inspector, but it isn't officially supported so expect to see some oddities.

  36. Wow by roc97007 · · Score: 2

    Overwhelming negative response. It makes one wonder what the design criteria were, or the Q/A strategy.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  37. Re:Tried it by UnknownSoldier · · Score: 2

    oh please ... Reddit is the bastard step-child of Slashdot and Digg.

    That is not to say Reddit is all bad -- at least _some_ of the sub-reddits are great like /r/LucidDreaming . However, others are a just a constant circle-jerk like /r/atheism /r/politics where it is impossible to have a civil discussion without getting down-voted into oblivion simple because you refuse to spout the fan-boi's dogma and want to look at things objectively. /. may have jumped the shark a while back but at most of the trolls have moved on from /. to the latest news-fad-site and that only helps /. :-)

  38. Why not a responsive web design? by Jim+Hall · · Score: 4, Insightful

    I'm confused why anyone - especially a technology-driven site like Slashdot - would create a "separate but equal" website just for mobile devices. It doesn't make sense these days. What's better is to build a responsive web design that scales down appropriately to the device. Then we don't have to visit a separate website with different branding to get to the same content on a mobile device.

    In a responsive web design, you might still choose to detect a mobile browser, and then set the comment browsing level to "5" or maybe "4". That's arguably the only thing you'd need to do that requires knowing the type of the client device.

  39. Re:Tried it by Cinder6 · · Score: 4, Insightful

    I know this doesn't help you, but I have none of those problems here. I'm running Mobile Safari/Chrome on an iPhone 5.

    --
    If you can't convince them, convict them.
  40. Re:Tried it by styrotech · · Score: 2

    That bug might only be present on Android then. I have the same problem as the GP and it makes the mobile site practically unusable.

    I'm using the Android browser on 4.1 JellyBean (Galaxy S3 - not exactly an obscure or underpowered device).

    Whereas Ars Technica use responsive design instead of a separate site and its almost a joy to read on a phone.

  41. Re:Tried it by jest3r · · Score: 2

    YES

    If the mobile site still LOOKED like Slashdot I think people would be more open to it.

    But it looks like any Generic news site ...

    I remember when they redesigned Slashdot 5 years ago ... and the new design retained the "feel" of the old design. The mobile site does not retain the Slashdot feel. Even hardcore old school Emacs guys have a certain affinity towards the way things look and feel here. So don't mess with that.

  42. Re:I like it but... by thetoadwarrior · · Score: 2

    I assume a third a third party was hired to do it and that's why they opted not to follow the theme at all and go with something completely different and didn't care enough to make it work on desktop browsers even if really it doesn't have to.

  43. Help us fix the mobile app scrolling by jennyscript · · Score: 5, Insightful

    Hi, I see a lot of you are having trouble with scrolls in the app being detected as clicks on stories. The team here has been trying to reproduce this, but failing. Here's a list of device / browser combinations I've tested:

    • iPhone 4s Safari
    • iPad 1 Safari
    • Nexus7 Chrome
    • Nexus7 Firefox
    • Nexus7 Opera

    The concern here is that there's some kind of common scrolling motion we aren't doing that's causing them to get interpreted as clicks. Are you holding your finger down longer? Pausing somewhere in the scroll? Is there horizontal motion in there? Is your scroll more of a flick? We've tried all those things and haven't seen it, so if some of you experiencing the problem would be kind enough to record a video of yourself making it happen (preferably on one of the above devices so we can reproduce it too), that would be great. There is no Slashdot Mobile QA team and our dev team is tiny.

  44. Re:Tried it by sapphire+wyvern · · Score: 2

    Yes. I don't like the article "snippeting" on the main page either. It's the main reason why I didn't explore the beta very much; reading the articles so I know which ones I want to load the comments on is a core function.

    If all I wanted was RSS snippets, I'd read Google News instead.