DHI Group, Inc., parent company of Slashdot and SourceForge, has announced that it plans to sell its Slashdot Media business, which includes the Slashdot and SourceForge sites. The reason for this decision is that the Slashdot Media business no longer aligns with the broader DHI strategy, which has been refined to focus on providing digital recruitment tools and services to connect employers and recruiters with talent in multiple professional communities.

With Slashdot's and SourceForge's established positions, iconic brands, and loyal and passionate followings of technology professionals in the Open Source community, DHI Group believes Slashdot Media will ultimately have greater opportunity to capitalize on its brand equity and unique assets -- and, therefore be able to realize greater success -- as part of a business that is focused primarily on media and software solutions.

Today's announcement does not change our product roadmap or any of our priorities towards the community or clients, and we will continue to stay focused to deliver on commitments made to our community and clients. The company is committed to ensuring that the transition is seamless and transparent to its community and clients, while working to maintain high levels of quality as it does today. Slashdot and SourceForge will continue their strategy of providing relevant content and services while continually striving to improve the experience for their communities.

Starting now, a small change we hope you'll like: you'll see polls appear on the front page of the site, mixed in with the rest of the Slashdot omelet, scrolling down from the top. It's a corner of our site where you can expect more improvements, too: if you have ideas about how you'd like polls to look, please let us know. Have a poll idea you'd like to see on the page? Browse some of the back catalog, or just the news, for inspiration and then -- for now -- please use the submissions form, and suggest away, by naming a question and up to eight potential answers. (It's always good to include an "escape valve" question, too, whether it's "None of the above," or anotherappropriateoption.)

As many of you noted, there were a number of bugs introduced yesterday. We've just fixed the first round of them:

The Post button (and similar) should no longer be hidden on /story/ pages.

The Older/Newer buttons on the front page should be back.

Tags should now be visible.

The left-hand navigation on user pages should be back.

We've fixed some of the responsiveness issues with the new header (more to do yet).

Contrast on Slashbox titles should be fixed.

There's more work to do, and we're going to keep squashing bugs.

We also wanted to take a moment and talk more about yesterday's changes. This is not a full redesign — far from it. We got rid of the left-hand nav bar because it just wasn't getting used very much. One of the biggest pieces of feedback from the Beta test was that the community didn't want us to waste screen real estate. The left-hand nav bar wasted a lot, particularly on smaller browser widths. Aside from gaining more space on the page, all the comments and stories are the same as before.

The most noticeable change was to the header. We didn't want to take away navigation functionality altogether, so we put it there, and made the header look and scale a bit better. We're not done working on it, and we're cleaning up the places in which it breaks.

We appreciate all the bug reports and feedback we've gotten over the past day. Another big thing we learned from the beta was that the community preferred to have changes roll out incrementally so they had a chance to evaluate them and provide feedback on a case-by-case basis. That's what we're trying to do here — when we make updates, they'll be small, and we'll open up a discussion about them. Let us know what you think at feedback@slashdot.org.

Slashdot Engineering has been on a cycle of continuous improvement and continuous deployment for the past few months -- ten code launches so far this year. Today we're announcing a few feature enhancements, and another announcement we think you'll welcome.

First, we've smoothed the way videos show up on the site. Whatever's on the other side of a given link (text or video), Slashdot itself is about conversations. So we've made our videos fit better into the page and the Slashdot comment system, rather than feeling like they're on a separate site. Please check out the new video page. (Also, stay tuned: we'll be bringing you video from other sources, too, with reviews, product close-ups, how-tos, and more.)

Secondly, we've removed the left-hand navigation links and tuned the top-of-page navigation bar. We recognize folks access the site with a huge range of browsers and platforms, and this provides more real estate, sacrificing links that metrics show were largely unused.

And effective today, we've jettisoned the Slashdot Beta platform out the side portal. Slashdot has always been a bit quirky, and "user friendly" is sometimes in the eye of the beholder. After heavily experimenting on the Beta platform and splitting traffic between Classic and Beta, we've made some decisions about which platform changes ultimately make sense: starting today, we're unifying users back on our Classic platform.

If you had fallen in love with Beta and are now seeing Classic for the first time, our apologies. But if you were one of the users who commented on the superiority of the Classic UX, we agree. In any case and as much as ever, your feedback is welcome at feedback@slashdot.org. If you notice any weirdness that might be due to our efforts to reconcile URLs that reach specific parts of the Beta site, please let us know. A screenshot is always worth a thousand words, and sometimes it seems as though the Devil lives in URLs.

If you use Slashdot's social login feature (which lets you log into Slashdot by means of an external account, such as one at Facebook or LinkedIn), you've probably noticed that this feature has recently been disabled. We've taken this step because of an exploitable bug in such systems (reported here and here, for instance) which could have let a malicious user log into a Slashdot account to which they should not have access. (To exploit this, an attacker would also have needed to know the email account used to sign up for a Slashdot username as well as create an account claiming that email address on an exploitable third-party social network; we have no reason to think that any reader's account was maliciously exploited.) If you use the social login feature, we apologize for the inconvenience. If you have reason to think that your account has been compromised, please let us know by emailing help@slashdot.org.

What is Slashdot Deals? It's pretty simple: Slashdot Deals is an online storefront with merchandise that's chosen, stocked, and fulfilled by a third-party; the products are intended to be ones that might interest you. To amplify that: We might have used some of the products on offer, but can't offer an endorsement of any that we haven't. Many readers may remember that Slashdot was for a long time linked to ThinkGeek, and there are some similarities: Slashdot makes money if you buy any of these products through the store, and that helps us bring you more news and discussions; that said, Slashdot Deals is not Slashdot, and vice versa, but we hope you enjoy it.

Security researcher Manikandan Rajakumar (See his Twitter feed) reported and provided enough information for us to identify and close a cross-site scripting vulnerability. We appreciate his attention and time; his efforts have made everyone in the Slashdot community safer. We always appreciate readers who provide useful feedback on Slashdot, and even more so when readers (ethically!) identify potential security holes. Many thanks!

----------Spot a security problem on Slashdot? We'd like to give you credit on our security attribution page for helping to protect everyone in the community. Send us email, to feedback@slashdot.org, and include as much detail as you can; screenshots, proof-of-concept code, and details about affected platforms are all useful and appreciated.

You may have noticed that OpenID is no longer a login option on Slashdot. (You can still login or create an account directly, or in conjunction with an existing social media account at Twitter, Facebook, etc.) Why not? In large part, because of a valuable warning we received about a possible security flaw in our OpenID login system from two researchers (Christian Mainka and Vladislav Mladenov) from Ruhr University Bochum.

This and other security concerns with OpenID (here's one relevant story), as well as the fact that relatively few readers have preferred OpenID to other login methods, mean that we're unlikely to re-add OpenID as a login method. Security here trumps the additional convenience.

The code that runs Slashdot, like all software, contains code that might be exploited. We always appreciate readers who provide useful feedback on Slashdot, and even more so when readers (ethically!) identify potential security holes. By "ethically," we mean that actually exploiting any security holes, or probing our systems, burdening the servers, engaging in a DDoS just to test things out, doesn't count. Spotting a problem and letting us know does, and we value that contribution highly.

A special thanks go out to Vladislav and Christian. We greatly appreciate their efforts and patience, as we do all readers who pass along suggestions, concerns, or ideas for the site. When readers find and diligently report possible security flaws, we're very grateful for their generosity in doing so.----------

Spot a security problem on Slashdot? We'd like to give you credit on our security attribution page for helping to protect everyone in the community. Send us email, to feedback@slashdot.org, and include as much detail as you can; screenshots, proof-of-concept code, and details about affected platforms are all useful and appreciated.

Our new Build section is a work in progress, but it's already a good place to scroll through for ideas and inspiration. Expect a bigger announcement (and more stories in there) soon, but don't hesitate to submit stories, ideas, and suggestions, via our submissions form (or via feedback@slashdot.org). We want to see your project!

It's been a long road. We've been asking for your opinions and suggestionsfor a while now, to help guide the creation of a new, cleaner look for Slashdot. (Many of the changes are below the surface, too.) What we've arrived at so far in our Beta looks and acts differently in several ways than the early iterations did, thanks to your ongoing input. That input has come in the form of thousands of comments, a few phone calls, many hundreds of emails, and even a fax(!).

Slashdot's been evolving for a very long time, with just a few major redesigns along the way. Looking at the site as it appeared in 1998, 2004, 2006, or even 2010, you can watch this evolution take place. Most of the changes (especially the look of the front page) have been fairly subtle; you can poke through these (and other snapshots) at the amazingly useful Wayback Machine to see when this or that element on the page appeared, disappeared, grew some rounded corners, or moved into an AJAX element. The front page of Slashdot shows how much (but also how little!) has changed in the course of our redesign: Here's that front page in Classic, and in the Beta as it stands.

Unlike our typical changes over the years, though, the Beta has been co-existing with the current look for a long time. That's because the Beta consolidates quite a few changes, and changes have a way of stepping on each others' toes sometimes, so it's important to have the whole thing getting prodded by users. Since we asked for public feedback two short months ago, we've been steadily adding features, tweaking the design, and fixing bugs. Your suggestions have helped us prioritize the important things. Here are some examples:

You said: The comment section is too narrow.

Yup, you were right. Originally the page was divided into two rails (like the front page is, currently). The wider left rail had all the comments, and the right rail held widgets and ads. We've tweaked this now, to let comments stretch all the way across the page. Ads may keep the lights on, but the site is for discussions, and this makes them easier to read.

You said: We can't see comments below our score threshold.

We've added the ability to see that there are comments below your current threshold, and clicking on the 'hidden comments' link will expand those so you can view them. We're not done building this out, yet -- we fully intend to make it easy to drill down into an interesting comment thread.

You said: I don't want images

One of the most polarizing features of the beta site was the addition of pictures to the news feed. We had a view selector that let people switch to basic text, without images, but even after making it bigger and replacing the icon with text, too many users had trouble finding it. So, we've simply made Text-Only the default setting. The view selector remains, at the top of the story column. It also has a headlines-only option, if you want to cram more stories onto the page.

You said: Stop truncating the summaries.

Now that will only happen if you intentionally switch to the Pictures view.

You said: I prefer to see the page denser with text than most of the Beta pages make it. Why is there so much white space?

This is a big area that we're working on, starting with the front page of the site. Getting the fonts, spacing, and elements just right is a tricky business, but we're working on making both front page and story pages easy to scan on a variety of devices and screen types. After a lot of improvements on this front to the front page, we'll next be digging into the look of the comments attached to each story.

You said: Bring back the department lines on the front page.

Ok. They're back. We've also tweaked the formatting on the summaries to be a lot closer to the classic look, which should make them easier to read.

You said: Moderation doesn't work.

It's implemented, and it works now. If you find bugs, please let us know.

You said: Let us link to individual comments.

Ok. Comment links work now.

You said: Where are the daily quotes, the UIDs next to commenter names, indication for mod points?

All implemented. You can see you have mod points on your profile page. We're also going to have a notifier show up in a more prominent place so you don't have to check every day.

Some users were also having an issue with choppy/blinky scrolling, which has been fixed. We've cleaned up the navigation bar, and fixed some of the text formatting.

You said: The beta site's not working on my mobile device.

You're right. Even though the beta has some features intended to be useful on phones, tablets, and other small devices, for right now it's got some rendering glitches that make it the wrong choice there. Until we automatically redirect mobile readers there, we suggest using instead either the site view meant specifically for mobile devices (m.slashdot.org) or -- as many people prefer -- the Classic view of the page.

We're not done.

We've got a giant list of suggestions from the community and a number of minor features that need to be implemented on the new version. We've knocked out a bunch of them, but there's plenty left to do.

And where does that leave the âoeclassicâ Slashdot page?

The Beta's not *finished* (we'll keep working on the code no matter what!), but as of now it's a site we're happy to point readers to, whether they're new readers or long-time users. For a while now, the Beta is where the bulk of development attention has gone, and that will continue. (New features that show up in Beta may never make it to the old look of the site, and features in the old look may appear in different form in the Beta; for instance, the beta's user pages are much easier to read than are the ones on the current look, and in the Beta you'll see a lot less in the way of scattered options and preferences, as we try to make the options that people actually use easier to find and manipulate.)

Many readers prefer to read with the current (as of early 2014) look of the site -- what we've taken to calling Slashdot Classic. We welcome that -- the editors all still use Classic quite a bit, and for all the work that the Beta's seen, we know there are still some features that aren't yet translated to the Beta. So don't panic: Slashdot Classic is going to stick around for quite a while. Feel free to read the site there, to make it your default (just make sure you have cookies active), or to alternate between the old and the new to see how they differ, and how the Beta continues to improve.

What kind feedback is the most helpful?

As we continue to bring the new site up to feature parity with the Classic site, one thing we need to do is prioritize the different bits of functionality. What we'd like from you is to hear what features you can't do without. (For example: linking to individual comments was one of the biggest requests last time around, so we made sure to prioritize that.) Your continued impressions of the current look and feature set are quite welcome as well.

Note: the best feedback is also the kind with details and concrete descriptions. There are a lot of combinations out there of not only hardware and software, but reading preferences and styles. Knowing the details of your OS, browser, and screen resolution can help us replicate problems or better understand your ideas.

In the weeks to come, you'll see Slashdot's ongoing redesign picking up several of the vital features that thelong betaperiod has been used to craft, as a new, cleaner look is implemented by default for more readers: quite a few of those "coming soon" info bubbles are finally being swapped out for genuine functioning tools that mean improved interfaces for some vital tasks and settings. Of note, since the last time we noted the progress in this blog, these features include:

A functioning moderation system

Comment filtering and threshold setting

Account sign-up

Password recovery (for when the inevitable happens)

Further improvements to responsive design, and general UI cleanup, as rendering and other kinks get straightened out thanks to your ongoing feedback

By the end of the month, we aim to have in place profile update, newsletter signup, and even more UI cleanup and assorted big fixes!

Watch this space for more details; for most readers, we hope that the elements we've redesigned mean a page that's gentler on the eyes, and has controls that are fewer, more useful, and easier to manipulate. Your feedback is very valuable to us during this redesign, so please tell us if you run into things that don't work for you on Slashdot Beta. If you would like to keep track of the latest updates for Beta, what's in it so far and what's in progress, bookmark our Beta News page, where the evolution is being chronicled.

Here's the official statement from Slashdot's parent company, Dice Holdings:

"We were alerted to these reported government agency actions by a
submission on Slashdot made by the community Sunday evening linking to
news stories. To be clear, we have not been asked to cooperate with
any government agency related to this matter and have not provided
access to Slashdot systems or user information. We know of no
unauthorized Slashdot code manipulation, or attempts to effect any.
We do not approve of this reported activity and if true, it's unfortunate that we are yet another in a long line of internet businesses to suffer this type of intrusion."

This is probably something that should surprise no one: claims, many of them credible and recent, point to various ways in which some well-known web sites and online services (Microsoft, Google, Yahoo, AT&T, Facebook, AOL, Skype, Apple, YouTube, and more) have all been affected by alleged government surveillance of one kind or another.

Being offended (as we on the editorial and coder team at Slashdot all are) by even a hint at spying on readers doesn't help in itself, so here are some practical notes: Nothing here involves Slashdot's code base or user data: the allegation is of transparent proxies between website (LinkedIn and Slashdot happen to be mentioned, but most likely many others) and user. The spoofing and malware injection said to have taken place relies on the fact that between practically any server on the internet and the end user, there are compromisable links. However, it's probably a wise policy to assume that you never know all the possible ways your privacy may be compromised online.

Please keep in mind, too, that Slashdot has long enabled and encouraged anonymous participation; you are welcome to read the site, leave comments, and submit stories, without logging in. (Logged in readers can read with SSL turned on, though.)

After a red-eye flight (my first trip to the UK) I've spent today in London at AppsWorld, live editing Slashdot for everyone who wants to see the sausage get made. "AppsWorld" sounds like a conference all about (you guessed it) mobile apps, and it is that -- but there's also a lot of interesting hardware, hackathons, etc. (It turns out, there's also some enthusiastic synchronized dancing from the Microsoft Surface crew, just across the aisle; but since we have a large screen TV set up, and access to YouTube, I couldn't resist looping in some dancing Steve Ballmer in the background as a sort of enthusiastic instructor.)

At the Slashdot booth, we've gotten some volunteer spam-whacking and department-line suggestions, too, of which more is always welcome, and some good suggestions on ways to keep improving our ongoing Beta page. The conference continues tomorrow; hopefully, you'll see some video on Slashdot soon with some interesting conversations and projects. And if you're here at the conference, come by and have a drink on us, while supplies last.

The ongoing Slashdot redesign effort has drawn a few notes from the outside world; here's what
TweakTown
and Business Insider have to say. Important to remember: the Beta siteworks — but it's transparently, inherently a work in progress, and the engineers are putting a lot of effort into
bringing to the new page feature parity and more. The existing site isn't going away anytime soon, but the more ideas
and bug reports we get (on the Beta, and in general) the more robust the next generation of Slashdot is going to be.
As we revamp comments, submissions, and other aspects of the site (down to how text flows on various screen sizes),
your reactions are crucial.

You can play with the site in the privacy of your own home, of course, too, but in person (at LUG meetings, etc) we enjoy
giving "factory tours" of the backend of the site. We've gotten the chance to show off the evolving new design to readers
(and passers by) at
Interop and at the NYC Tech Meetup earlier this month. If you happen to be in the neighborhood, we'll be at
AppsWorld, too, from October 22-23 in London. Stop by and get some swag (while
it lasts) and perhaps help us reject some spam or hit Save on a story.

A few days ago, we opened the curtains to give everyone an early glimpse of what Slashdot is going to look like. More than a thousand comments and hundreds of emails have poured in, offering some very useful feedback and advice: thanks. As you'd expect, Beta is work in progress — we have a long way to go not only in integrating all the features we want, but in smoothing over inevitable rough edges. This blog post is to give a few updates on the state of the Beta, and tips on using it. As we sifted through your feedback we noticed some common areas of critique:

One group of readers we've heard a lot from are those who don't like seeing the images that the new Beta introduces in its Standard view. Good news: seeing images is a preference that's easy to change. Just select "Classic" from the view-selection widget on the menu that appears near the top of the page. (You can see an illustration here.) You can always change your view, and your choice is persistent until you select a new one.

Likewise, many readers have raised (understandable!) objections to the Beta's fixed-width; expect changes in the near future that will address this. We're aiming for a page that displays cleanly on as many devices, screen sizes, and browsers as possible.

We're only partway into this redesign; a lot of stuff is coming. One big example: the commenting system is only partly in place, which means many of the features currently available on the regular page haven't been implemented yet on the Beta. Likewise, the submissions and login systems are under active development, and you'll see enhancements rolled out in weeks to come as the beta gets closer to production.

We know there are some general problems with readability in the Beta, too; In the coming weeks we'll be experimenting with various fonts, texture and styles to make the page easier on your eyes.

You make Slashdot what it is — so please keep the feedback coming. (Details, including screenshots, make bug reports and suggestions much easier to act on). Watch this space: We'll be giving more updates via this blog on improvements as they're worked on.