Language Selection

English French German Italian Portuguese Spanish

Tux Machine's editorial picks are...

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

KDE Frameworks 5.61, Applications 19.08 in FreeBSD

Recent releases were KDE Frameworks 5.61 and KDE Applications 19.08. These have both landed in the official FreeBSD ports tree, after Tobias did most of the work and I pushed the big red button. Your FreeBSD machine will need to be following current ports – not the quarterly release branches, since we don’t backport to those. All the modern bits have arrived, maintaining the KDE-FreeBSD team’s commitment to up-to-date software for the FreeBSD desktop. The one thing we’re currently lagging on is Qt 5.13. There’s a FreeBSD problem report tracking that update. Read more

Dev branch moving towards Qt 6

As you know, Qt 5.14 will be branched pretty soon. After that I would expect that most new development work would start to be aimed towards Qt 6. As it looks right now, 5.15 will be a smaller release where we polish what we have in 5.14, and prepare some things for Qt 6. To reflect that and help us all understand that the development focus is now towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6 back into dev). We can then either create a 5.15 branch at the same time, or slightly later, once 5.14 has stabilised a bit more (e.g. after the beta or RC). Read more Also: Qt's Development Branch To Begin Forming Qt 6

Today in Techrights

How to Check Which Debian Version are you Running

Wondering which Debian version are you running? This tutorial teaches you several ways to check Debian version in the terminal. Read more