It’s time for governments to address the reality that five tech companies—not everyday consumers—control our online experiences today. Updated competition laws are essential for the internet to be private, secure, interoperable, open, accessible, transparent, and a balance between commercial profit and public benefit. This is Mozilla’s vision for the internet. For a number of years, we have shared our views supporting government competition efforts globally to achieve it.

One such proposal now under discussion in the US Congress is the American Innovation and Choice Online Act (AICOA). This bill is an important step in correcting two decades of digital centralization by creating a level playing field for smaller, independent software companies to compete. We support this bipartisan effort led by Senators Amy Klobuchar and Chuck Grassley and Representatives David Cicilline and Ken Buck.

We believe that AICOA will facilitate innovation and consumer choice by ensuring that big tech companies cannot give preference to their own products and services over the rich diversity of competitive options offered by others. Mozilla—and many other independent companies—cannot effectively compete without this antitrust law. We are disadvantaged by the fact that current and future Firefox users, many of whom are privacy and security focused, cannot easily install and keep Firefox as their preferred browser because of confusing operating system messages and settings. We are further challenged by app store rules designed to keep out Gecko, our independent browser engine that powers Firefox, Tor and other browsers. We are stuck when big tech companies do not offer us and other developers open APIs and other functionality needed for true interoperability.

A fair playing field is vital to ensure that Mozilla and other independent companies can continue to act as a counterweight to big tech and shape the future of the internet to be more private and more secure. We understand that the bill sponsors intend AICOA to regulate only gatekeeper companies and their controlled products. It is not intended to regulate or impact the agreements or product offerings of non-regulated independent companies like Mozilla that partner with gatekeepers for critical services. Nor does it require trading off privacy and security in order to enhance competition.

At the exhibition stand you will have the opportunity to perform some real black-box testing, learn about Salience bias, Peltzman effect and Wason's experiments and take a photo with our lovely mascot.

The Kiwi TCMS team will be there to answer all of your questions regarding open source, community, support, various integrations and the differences between Self-Support, SaaS and Enterprise subscriptions!

If you want to view certain media files, such as photos and videos from your computer, or mobile on your TV, then you need to have enabled UPnP and DLNA-compliant devices, as well as, to set up a media server.

In this article we will give brief explanations about DLNA, and UPnP devices, streamers, and servers.

Here also you can find a rich list of free, and open-source DLNA and UPnP servers, and streamers which you can use freely to set up your own home entertainment system.

Gaurav Singh, acting as Circuit Valley, has designed an open-source hardware USB 3.0 Type-C industrial camera with three boards: one to capture data through a CMOS sensor, another based on a Lattice Crosslink NX FPGA to handle image processing, and finally, a board equipped with an Infineon FX3 USB 3.0 controller for sending the video data to the host.

OIS 2022 is over, but the OpenInfra community stays tuned for the next OpenInfra Summit, taking place in Vancouver in 2023! This year’s summit in Berlin offered a lot of insightful keynotes and technical sessions. Speakers discussed the most recent trends in the industry, including composable infrastructure and sustainable computing, and set the pace for the next releases of the OpenInfra-hosted project, including OpenStack. It was a great opportunity to reconnect in person after the pandemic.

[...]

During my keynote on Day 1, I discussed the fact that OpenStack has just entered the Slope of Enlightenment phase of its Hype Cycle. Most organisations have realised that OpenStack and Kubernetes are in fact complementary technologies rather than competing ones. Canonical happens to be well-positioned, as Ubuntu is a platform that integrates OpenStack, Kubernetes and applications very well.

Parrot (popularly/formerly known as Parrot Security OS or Parrot OS) is a free and open-source Linux distribution derived from the well-known Debian Linux.

Designed for security, privacy, and development, Parrot ships with an assortment of IT security and digital forensics tools, utilities, and libraries; development and programming tools; as well as privacy protection tools.

It comes by default with MATE Desktop Environment (DE), however, users can install other DEs.

Last year, Tesla issued an update that made its vehicles easier to start after being unlocked with their NFC key cards. Now, a researcher has shown how the feature can be exploited to steal cars.

For years, drivers who used their Tesla NFC key card to unlock their cars had to place the card on the center console to begin driving. Following the update, which was reported here last August, drivers could operate their cars immediately after unlocking them with the card. The NFC card is one of three means for unlocking a Tesla; a key fob and a phone app are the other two.

EasyOS has an "update" icon on the desktop, that checks if a later version online, and if so offers to download and update the local installation.

The problem we have been having is that it uses rsync, which reduces the size of the download by only downloading the difference between current and latest version; however, it disconnects, seemingly randomly. Perhaps it is a problem with ibiblio.org getting too busy, as the problem does seem dependent on the time-of-day.

Folks,

Here's a summary of the Gitlab experiment discussion, with some
additional comments. Thanks to everybody who sent their feedback!


* Things that people like:

- Fetching commits directly with git instead of applying patches from
  emails (Huw, Jacek, Paul, Zeb). Indeed that's a major help for me as
  well.

- Better tracker, easy to see the list of pending reviews (Huw).

- Possibility to host more Wine projects, as well as private Wine trees
  to share WIP patches (Jacek). Indeed it would be nice to have all Wine
  projects in one place instead of the current mix of
  github/sourceforge/etc.

- Potential for automation (Jacek). Gitlab offers many services that we
  will be able to take advantage of, the most obvious being CI for the
  testbot. Having all the data in a proper database instead of free-form
  emails should make it possible to do other interesting things as well.


* Some other things I like:

- Updating status doesn't need to go through me, people can assign
  reviewers, supersede patches, etc. directly. That reduces my workload
  and improves the bus factor. Once we have figured out how to make
  testbot results reliable, we could also have maintainers merge commits
  directly.

- The full discussion thread for a given MR is readily accessible, it
  doesn't require hunting down the multiple revisions of a patch and
  associated threads in the mailman archive.


* Things that could be improved:

- Signoffs are a bit cumbersome (Rémi). We should change the
  requirements to something better adapted to Gitlab.

- It's only possible to approve the whole MR, not individual commits
  (Huw, Zeb). I think that's an acceptable trade-off, but we could
  imagine other approaches.

- The mailing list gateway creates too much noise; mixing comments from
  Gitlab and mailing list isn't very clean (Jacek, Rémi, Alex).  We can
  make some tweaks, or use a separate list, or even rethink the approach
  of the mail gateway.

- Gitlab threading support is limited, nested comment threads are not
  supported (Zeb). That's true, but looking through the past few months
  of patch reviews, it seems that we almost never use nested threads, so
  I think we can live with that limitation.

- Reviewers can push fixups to commits, but that requires the author to
  grant explicit permission (Jacek). Hopefully we can tweak access
  rights to allow this by default.


* Conclusion

I think Gitlab is working well for us, and most people seem generally
happy with it. So my plan is to go forward and make Gitlab the main
development platform for Wine.

I'll start working on the transition, and on the improvements mentioned
above. Any help will be welcome! I'll be posting a roadmap shortly.