Language Selection

English French German Italian Portuguese Spanish

OSS Leftovers

Filed under
OSS
  • Open-Source Single Sign-On (SSO)

    Single sign-on (SSO) solutions are a popular category within the identity and access management (IAM) sector. This is especially true when you look at the fact that SaaS adoption among small and medium sized businesses (SMBs) doubled in 2014, and has quadrupled since 2015 (Blissfully). According to the same report, SMBs use 50+ SaaS products on average, and IT admins have been adopting SSO solutions to help manage user access to these 50+ SaaS applications. However, single sign-on solutions can get extremely pricey, so it’s no wonder that IT organizations are searching for open-source single sign-on alternatives.

  • Increasing open-source inclusivity with paper circuits

    Open-source software has an inclusiveness problem that will take some innovative approaches to fix. But, Andrew "bunnie" Huang said in his fast-moving linux.conf.au 2018 talk, if we don't fix it we may find we have bigger problems in the near future. His approach to improving the situation is to make technology more accessible — by enabling people to create electronic circuits on paper and write code for them.

    Huang started by asking why we should care about making technology more inclusive. Open-source software gets its power from inclusiveness; that power is so strong that we can (quoting Chris DiBona) claim that, without open-source software, the Internet as we know it would not exist. As an engineer, he thinks that's great, but he has a concern: that means that the user base now include politicians.

  • Google gave the world powerful AI tools, and the world made porn with them

    In 2015, Google announced it would release its internal tool for developing artificial intelligence algorithms, TensorFlow, a move that would change the tone of how AI research and development would be conducted around the world. The means to build technology that could have an impact as profound as electricity, to borrow phrasing from Google’s CEO, would be open, accessible, and free to use. The barrier to entry was lowered from a Ph.D to a laptop.

  • More XEPs for Smack

    I spent the last weekend from Thursday to Sunday in Brussels at the XSF-Summit (here is a very nice post about it by JCBrand) and the FOSDEM. It was really nice to meet all the faces belonging to the JIDs you otherwise only see in the MUCs or on GitHub in real life.

    [...]

    Ge0rG gave a talk about what’s currently wrong with the XMPP protocol. One suggested improvement was to rely more on Stable and Unique Stanza IDs to improve message identification in various use-cases, so I quickly implemented XEP-0359.

  • In Digital Health, Open Source Warrants Due Diligence [Ed: FUD. None of this is not applicable to proprietary software where the risks are even greater. Lawyers or law firms can't help reminding us that they're natural enemies of FOSS because they look to just prey on it with their FUD.]
  • LLVM 6.0 RC2 Released, Retpoline Support Still Settling

    The second release candidate of LLVM 6.0 has been tagged.

    Hans Wennborg announced the availability of LLVM 6.0 RC2 a short time ago. He noted in the brief release announcement, "There's been a lot of merges since rc1, and hopefully the tests are in a better state now."

  • RISC-V Changes For Linux 4.16 Aren't As Big As Hoped For

    While initial RISC-V support was added to Linux 4.15, it was only the architecture code and not any device drivers. With Linux 4.16, the RISC-V developers admit this time around they didn't get as many changes in as they were hoping for, but they do have some improvements to land this cycle.

More in Tux Machines

today's howtos

Android Leftovers

The Spectre/Meltdown Performance Impact On Linux 4.20, Decimating Benchmarks With New STIBP Overhead

As outlined yesterday, significant slowdowns with the Linux 4.20 kernel turned out to be due to the addition of the kernel-side bits for STIBP (Single Thread Indirect Branch Predictors) for cross-HyperThread Spectre Variant Two mitigation. This has incurred significant performance penalties with the STIBP support in its current state with Linux 4.20 Git and is enabled by default at least for Intel systems with up-to-date microcode. Here are some follow-up benchmarks looking at the performance hit with the Linux 4.20 development kernel as well as the overall Spectre and Meltdown mitigation impact on this latest version of the Linux kernel. Some users have said AMD also needs STIBP, but at least with Linux 4.20 Git and the AMD systems I have tested with their up-to-date BIOS/microcode, that hasn't appeared to be the case. Most of the AMD STIBP references date back to January when Spectre/Meltdown first came to light. We'll see in the week ahead if there is any comment from AMD but at this time seems to be affecting up-to-date Intel systems with the Linux 4.20 kernel. Read more

Today in Techrights