Language Selection

English French German Italian Portuguese Spanish

OSS Leftovers

Filed under
OSS
  • A Recap Of The Many Interesting Presentations At FOSDEM 2018

    Over the past week and a half we have highlighted many of the interesting presentations that took place at the annual Free Open-Source Developers' European Meeting (FOSDEM) in Brussels. Here's a look back if you are behind on your Phoronix reading.

  • WebRender newsletter #14
  • Restricting AppCache to Secure Contexts

    The Application Cache (AppCache) interface provides a caching mechanism that allows websites to run offline. Using this API, developers can specify resources that the browser should cache and make available to users offline. Unfortunately, AppCache has limitations in revalidating its cache, which allows attackers to trick the browser into never revalidate the cache by setting a manifest to a malformed cache file. Removing AppCache over HTTP connections removes the risk that users could see stale cached content that came from a malicious connection indefinitely.

  • Altibase Challenges Oracle, IBM & Microsoft

    ...Altibase, an enterprise grade relational database, announced that it is now open source.

  • Putting Open Source GIS to Use
  • InfluxData scores $35 million Series C to expand time series database business

    In a world where sensors are capturing ever-increasing amounts of data, being able to collect that high volume and measure it over time becomes increasingly important. InfluxData, the startup built on top of the open source time series database platform, announced it has received a $35 million Series C investment today led by Sapphire Ventures, the investment arm of enterprise software giant, SAP.

  • EOH acquires LSD in open source drive

    The JSE-listed company says the partnership addresses an identified gap in the market by bringing the value and innovation that open source solutions provide, in enabling EOH customers' digital transformation journeys.

    LSD was founded by Stefan Lesicnik in 2001. In the early days, the company focused on supporting basic Linux servers.

  • Qt 5.10.1 Ships With More Than 300 Bug Fixes

    The Qt Company has announced the availability of Qt 5.10.1, the first bug-fix release to Qt 5.10 that shipped back in December.

    In the approximately two months since Qt 5.10.0, today's point release has more than 300 bug fixes and around 1,400 changes in total over the previous release.

More in Tux Machines

Compact, rugged IoT gateway offers dual GbE with PoE

Inforce has launched a $250 “Inforce 6320” IoT gateway that runs Linux on a quad -A53 Snapdragon 410, and offers WiFi, BT, GPS, HDMI, USB, -30 to 85°C support, and dual GbE ports with PoE. Inforce Computing’s $250 Inforce 6320 is a compact (170 x 95 x 42mm) IoT gateway that runs Ubuntu Core (Snappy) and Debian on Qualcomm’s Snapdragon 410E. Inforce promises “periodic upstream kernel based BSP releases [that] include in-depth documentation along with a host of royalty-free software.” The Debian BSP includes LXDE, drivers for all available interfaces, as and access to the Inforce TechWeb tech support services. Read more

Today in Techrights

today's leftovers

Debian and Ubuntu Leftovers

  • Listing and loading of Debian repositories: now live on Software Heritage
    Software Heritage is the project for which I’ve been working during the past two and a half years now. The grand vision of the project is to build the universal software archive, which will collect, preserve and share the Software Commons. Today, we’ve announced that Software Heritage is archiving the contents of Debian daily. I’m reposting this article on my blog as it will probably be of interest to readers of Planet Debian. TL;DR: Software Heritage now archives all source packages of Debian as well as its security archive daily. Everything is ready for archival of other Debian derivatives as well. Keep on reading to get details of the work that made this possible.
  • Canonical announces Ubuntu Core across Rigado’s IoT gateways
  • Collecting user data while protecting user privacy
    Lots of companies want to collect data about their users. This is a good thing, generally; being data-driven is important, and it’s jolly hard to know where best to focus your efforts if you don’t know what your people are like. However, this sort of data collection also gives people a sense of disquiet; what are you going to do with that data about me? How do I get you to stop using it? What conclusions are you drawing from it? I’ve spoken about this sense of disquiet in the past, and you can watch (or read) that talk for a lot more detail about how and why people don’t like it. So, what can we do about it? As I said, being data-driven is a good thing, and you can’t be data-driven if you haven’t got any data to be driven by. How do we enable people to collect data about you without compromising your privacy? Well, there are some ways. Before I dive into them, though, a couple of brief asides: there are some people who believe that you shouldn’t be allowed to collect any data on your users whatsoever; that the mere act of wanting to do so is in itself a compromise of privacy. This is not addressed to those people. What I want is a way that both sides can get what they want: companies and projects can be data-driven, and users don’t get their privacy compromised. If what you want is that companies are banned from collecting anything… this is not for you. Most people are basically OK with the idea of data collection, they just don’t want to be victimised by it, now or in the future, and it’s that property that we want to protect. Similarly, if you’re a company who wants to know everything about each individual one of your users so you can sell that data for money, or exploit it on a user-by-user basis, this isn’t for you either. Stop doing that.