We chat about our time with the new Plasma 5 desktop from KDE, then using the latest situation with Manjaro we discuss the poor state of Linux news, root causes, and what the real solution is that has major ramifications for the open source community.
Plus some fantastic feedback, a Command Line challenge update, and our big plans for next week!
We love when our community shares screenshots and stories of what they create on elementary OS. When you share how you use elementary OS, you’re sharing the fact that it’s something real people use every day—that it’s something both five-year-olds and professional programmers can use. Your stories and the community you create is a big part of what brings people to elementary OS.
KDE proudly announces the immediate availability of Plasma 5.0, providing a visually updated core desktop experience that is easy to use and familiar to the user. Plasma 5.0 introduces a new major version of KDE’s workspace offering. The new Breeze artwork concept introduces cleaner visuals and improved readability.
Michael came by some information about Manjaro developers leaving the distribution. No big deal, that happens; people move on. But that’s not sexy enough to drive clicks. So what we need here is a really flagrant title, one like: “Manjaro Linux Developers Experience A Mass Exodus”.
Now in the real world of news reporting, there is this thing called ‘Verification’, wherein, you try to independently verify from multiple sources the information you are researching. You contact multiple people, you get the story from different angles, and then you decided what you are going to write. But in todays fast paced ‘Get the story out first’ online news reporting, that step gets lost. Sites want to be the first one to release news, why…? Because the first to report gets the clicks, and in this world. Clicks = Money. We have sacrificed Truth for convenience and money.
But there’s a more ugly deceitful side; intentionally NOT verifying information can sometimes create a lot of drama. And drama my friends… well… Drama = Clicks. So whats our mantra? – Get the story out first! – If its wrong and creates drama no problem — that’s a plus, it’ll drive more traffic to our site. We can later ‘retract’ any false information once we’ve actually been presented with the correct information.
It’s simple math.
Drama = Clicks. Click = Money. Thus: Drama = Money.
- Join us on Sunday for a chat with Rob from Manjaro to get the story straight from the source.
Runs Linux from the people:
- Send in a pic/video of your runs Linux.
- Please upload videos to YouTube and submit a link via email or the subreddit.
Join us for Unplugged 50 on Monday the 21st 1pm West 4pm East
New Shows : Tech Talk Today (Mon – Thur) HowTo Linux (Fridays)
A security researcher has warned that there are cases where the LibreSSL PRNG will produce identical output two or more times when running on Linux systems, something he called a “catastrophic failure.” The same data can be returned when an application process is cloned—or “forked,” in computing parlance—something that can happen when an operating system repeats a similar task over and over, like each time a Web server opens a new connection, for example. In most cases, LibreSSL will detect that a process has been forked because its identifier, known as a PID, will differ. In those cases, LibreSSL will automatically reseed the random numbers to ensure they’re unique to the new process.