Language Selection

English French German Italian Portuguese Spanish

OSS Leftovers

Filed under
OSS
  • YouTube Begins Rolling Out AV1 Support In Beta

    YouTube has begun transcoding videos into the new royalty-free AV1 video codec.

    So far just a handful of videos are available with this AV1 beta support on YouTube. The Google company is supporting AV1 in MP4 within the Media Source for Chrome 70+ and the newest Firefox Nightly builds as of today. The Firefox Nightly support also requires media.av1.enabled and media.mediasource.experimental.enabled preferences enabled.

  • The Evolving Role of Build Engineering in Managing Open Source
  • NetBSD 7.2 comes with Security & Stability Enhancements as well as USB 3.0 Support

    NetBSD has come out with a new release for the 7.x series. The second feature update of NetBSD 7, NetBSD version 7.2, comes with a few new features and enhancements including, most prominently, the support of the USB 3.0 device as well as improvements for the Linux emulation. The latest release also supports the Raspberry Pi 3 computer range, adapting the release to be compatible for running on those devices, and the release ramps up updates for several drivers to make all of this possible.

    The release announcement for the NetBSD 7.2 states that this update incorporates substantial bug fixes and enhancements for overall improvement of the stability and security of NetBSD. The update also introduces new features such as the few mentioned above and other fixes in binary compatibility for ancient NetBSD executables. The iwm(4) driver for Intel Wireless 726x, 316x, 826x, and 416x has also been incorporated and a legacy network adapter has been improved to resolve a setup interruption found in the Hyper-V VMs.

  • LibreJS 7.17 released

    GNU LibreJS aims to address the JavaScript problem described in Richard Stallman's article The JavaScript Trap*. LibreJS is a free add-on for GNU IceCat and other Mozilla-based browsers. It blocks nonfree nontrivial JavaScript while allowing JavaScript that is free and/or trivial.

  • What We Mean When We Say "Data Portability"

    “Data portability” is a feature that lets a user take their data from a service and transfer or “port” it elsewhere. This often comes up in discussions about leaving a particular social media platform and taking your data with you to a rival service. But bringing data to a competing service is just one use for data portability; other, just-as-important goals include analyzing your data to better understand your relationship with a service, building something new out of your data, self-publishing what you learn, and generally achieving greater transparency.

    Regardless of whether you are “porting” your data to a different service or to a personal spreadsheet, data that is “portable” should be easy to download, organized, tagged, and machine-parsable.

    EFF supports users’ legal right to obtain a copy of the data they have provided to an online service provider. Once you move beyond that, however, the situation gets more complicated. Data portability interacts, and sometimes even conflicts, with other digital rights priorities, including privacy and security, transparency, interoperability, and competition. Here are some of the considerations EFF keeps in mind when looking at the dynamics of data portability.

  • Hortonworks plans to revamp Hadoop and its big data tools with cloud best practices in mind

    One big disadvantage that comes with a hybrid cloud strategy is forcing your developers to learn and understand the different techniques required by cloud providers and on-premises software vendors for lots of applications. Hortonworks, the company behind several tools for big-data darling Hadoop, plans to revamp its software over the next few years in order to make modern cloud-native development practices part of its on-premises tools, giving hybrid cloud developers one less thing to worry about.

    Hortonworks plans to announce the Open Hybrid Architecture Initiative Monday, kicking off the project that will allow customers running Hadoop and Hortonworks tools on their own servers to take advantage of newer infrastructure ideas that have become popular since the big-data analysis software was created, said Arun Murthy, co-founder and chief technical officer of Hortonworks. It’s yet another sign that while self-managed servers aren’t disappearing as fast as people once thought they might, the infrastructure concepts of the cloud-native era are going to eventually become de facto standards.

More in Tux Machines

today's howtos

Games: Ashes of the Singularity: Escalation, Humble Monthly and DXVK Updates

FOSS, standard essential patents and FRAND in the European Union

As part of the research project on “The Interaction between Open Source Software and FRAND licensing in Standardisation”, a workshop was organised by the European Commission, Joint Research Centre (JRC) in collaboration with Directorate General Communications Networks, Content and Technology (CONNECT) to present and discuss the intermediate results to date. The workshop took place in Brussels on September 18, 2018. I presented a set of observations from the research on the case studies performed as part of the project that are outlined below. Other speakers where Catharina Maracke on the issue of legal compliance between Open Source and FRAND licenses, Bruce Perens on “Community Dynamics in Open Source”, and Andy Updegrove on “Dynamics in Standardisation”. You may ask what the relevance of this debate is for the wider Free and Open Source Software community. The obvious answer is that to distribute software “without restriction”, the user needs all the usage rights associated with the program. While most FOSS contributors assume that this is naturally the central motivation for anybody to contribute in the first place, there is a long history of attempts to maintain some sort of exclusive control over a piece of FOSS code, possibly using other rights than copyright. Read more

Today in Techrights