Language Selection

English French German Italian Portuguese Spanish

Tux Machine's editorial picks are...

Good as they are
54% (73 votes)
Need improving
10% (13 votes)
Too many
6% (8 votes)
Too few
3% (4 votes)
Need commentary
28% (38 votes)
Total votes: 136

too many links

Take a look at this for example. http://i.imgur.com/MQ21f8r.png way too many links and it actually keeps going if I scroll down.
No one is going to read all of that. People should be easily able to recognise new content on the website.

Front page

Is shortened summaries, especially of such posts, were to appear in the front page, would that be an improvement? It would necessitate more clicking (to expand the post) but it would save space.

front page

Yes definitely Smile The short summary can include small headlines "New releases from so and so' and "Learn new tricks to fix this and tips to do that" or "New howtos for...." or "Guides for compiling this and that and migrating from software A to B etc.." then when the readers click 'read more', they see the full set of links.

And again, thank you for your dedication towards making the website more user friendly Smile

Shortening

I will be shortening long posts with many links from now on.

the leftovers

the leftovers thing with many links is way too annoying in my opinion.

Suggestion

Do you suggest that they don't get posted at all or just not in this current form?

Not in it's current form.

Not in it's current form. Perhaps make a separate page for "tutorials", or left overs. call it something like 'back news' or short news. And then keep the major articles on the front page Smile

(and thank you for replying)

Feeds

The problem is, how will people subscribe to those pages or be made aware of their existence? it would basically fragment the flow, wouldn't it? Some sites like FAIR.org do this (splitting to sections) and it complicates syndication.

More in Tux Machines

Black Hat 2014: Open Source Could Solve Medical Device Security

On the topic of source code liability, Greer suggests that eventually software developers, including medical device development companies, will be responsible for the trouble their software causes (or fails to prevent). I think it’s fair to say that it is impossible to guarantee a totally secure system. You cannot prove a negative statement after all. Given enough time, most systems can be breached. So where does this potential liability end? What if my company has sloppy coding standards, no code reviews, or I use a third-party software library that has a vulnerability? Should hacking be considered foreseeable misuse? Read more

Does government finally grok open source?

Yes, the government -- one U.S. federal government employee told me that government IT tends to be "stove-piped," with people "even working within the same building" not having much of a clue what their peers are doing, which is not exactly the open source way. That's changing. One way to see this shift is in government policies. For the U.S. federal government, there is now a "default to open," a dramatic reversal on long-standing practices of spending heavily with a core of proprietary technology vendors. Read more

The OS LinuX Desktop

Reader Oliver wanted to make his Linux Mint desktop look as much like a Mac as possible so others would find it easy to use. Given some of our previous Linux featured desktops, we know it wasn't tough, but the end-result still looks great. Here's how it's all set up. Read more

A Linux Desktop Designed for You

Desktop environments for Linux are not released ready-made. Behind each is a set of assumptions about what a desktop should be, and how users should interact with them. Increasingly, too, each environment has a history -- some of which are many years old. As you shop around for a desktop, these assumptions are worth taking note of. Often, they can reveal tendencies that you might not discover without several days of probing and working with the desktop. Read more