Language Selection

English French German Italian Portuguese Spanish

Fluxbox

Mozilla: More on IRC (or Less of IRC), Firefox Nightly and Mozilla's 'IoT'

Filed under
Fluxbox
  • The Rust Programming Language Blog: Mozilla IRC Sunset and the Rust Channel

    The Rust community has had a presence on Mozilla’s IRC network almost since Rust’s inception. Over time, the single channel grew into a set of pretty active channels where folks would come to ask Rust questions, coordinate work on Rust itself, and just in general chat about Rust.

    Mozilla recently announced that it would be shutting down its IRC network, citing a growing maintenance and moderation burden. They are looking into new options for the Mozilla community, but this does leave the question open as to what the Rust project will do.

    Last year a lot of the teams started exploring new communication platforms. Almost all the Rust teams no longer use IRC as their official discussion platform, instead using Discord or Zulip (as well as a variety of video chat tools for synchronous meetings). The few teams that do use IRC are working with us to find a new home, likely a channel on Discord or Zulip.

    This leaves the #rust and #rust-beginners channels on Mozilla’s IRC network, which are still quite active, that will need a new home when Mozilla’s network shuts down. Rust’s official Discord server does have the #users, #help, and #beginners channels that fill in this purpose, and we recommend people start using those.

  • irc.mozilla.org

    I remember the very first time I used IRC. It was 2004, and earlier in the week I had met with Mike Shaver at Seneca, probably for the first time, and he'd ended our meeting with a phrase I'd never heard before, but I nodded knowingly nevertheless: "Ping me in #developers."

    Ping me. What on earth did that mean!? Little did I know that this phrase would come to signify so much about the next decade of my life. After some research and initial trial and error, 'dave' joined irc.mozilla.org and found his way to the unlisted #developers channel. And there was 'shaver', along with 300 or so other #developers.

    The immediacy of it was unlike anything I'd used before (or since). To join irc was to be transported somewhere else. You weren't anywhere, or rather, you were simultaneously everywhere. For many of these years I was connecting to irc from an old farm house in the middle of rural Ontario over a satellite internet connection. But when I got online, there in the channels with me were people from New Zealand, the US, Sweden, and everywhere in between.

  • Firefox Nightly: These Weeks in Firefox: Issue 58

    Continuing on fixing regressions in QuantumBar, including improvements for RTL, less visual flicker and lots more.

  • Mozilla's IoT relaunches, sun-based GPS, and more news

    As you might expect, Mozilla has irons in a number of open source fires. Over the last two weeks, Mozilla has gone public with two significant projects.

    The first one is Pyodide. It's an "experimental Python project that’s designed to perform computation" from within a browser window. While other projects are also attempting to bring Python interpreters to the web browser, Pyodide "doesn’t require a rewrite of popular scientific computing tools (like NumPy, Pandas, Scipy, and Matplotlib) to achieve adequate performance."

    The second project is an IoT platform called Mozilla WebThings. WebThings isn't new. It's the grown up version of the organization's Project Things platform "for monitoring and controlling connected devices." The latest version of WebThings add features for logging and visualizing data from your smart devices, as well as monitoring and triggering alarms from internet-connected detectors. You can learn more at the Mozilla IoT site.

Mozilla: Mozilla Developer Roadshow, Mozilla Localization, A "moral obligation to use Firefox" and Release for Vista 10

Filed under
Fluxbox
  • Developer Roadshow 2019 returns with VR, IoT and all things web

    Mozilla Developer Roadshow is a meetup-style, Mozilla-focused event series for people who build the web. In 2017, the Roadshow reached more than 50 cities around the world. We shared highlights of the latest and greatest Mozilla and Firefox technologies. Now, we’re back to tell the story of how the web continues to democratize opportunities for developers and digital creators.

  • Mozilla Localization (L10N): Implementing Fluent in a localization tool

    In order to produce natural sounding translations, Fluent syntax supports gender, plurals, conjugations, and virtually any other grammatical category. The syntax is designed to be simple to read, but translators without developer background might find more complex concepts harder to deal with.

    That’s why we designed a Fluent-specific user interface in Pontoon, which unleashes Fluent powers to localizers who aren’t coders. Any other general purpose Translation Management System (TMS) with support for popular localization formats can follow the example. Let’s have a closer look at Fluent implementation in Pontoon.

  • It is your moral obligation to use Firefox

    While both Google Chrome and Microsoft Edge themselves are proprietary products they are based on the open source Chromium project utilizing Blink and V8 engines. This means that in practice the entire browser market is currently based on free and open solutions. This is obviously a wonderful thing and Google Chrome itself appears to be a good and nice to use product. Unfortunately as always the world is not as beautiful as we would like it to be.

    As the Chromium project is largely financed by Google and used by Chrome, the most popular browser in the world, Google exerts a significant political pressure over the project and de facto controls it. This control can at this point effectively be used in order to shape the web and push it in the desired direction.

  • Mozilla Future Releases Blog: Firefox Beta for Windows 10 on Qualcomm Snapdragon Always Connected PCs Now Available

Mozilla: Rust, Privacy, and Ad-Blocking

Filed under
Fluxbox
  • This Week in Rust 213

    Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us a pull request. Want to get involved? We love contributions.

  • Firefox 57 delays requests to tracking domains

    Firefox Quantum – version 57 – introduced number of changes to the network requests scheduler. One of them is using data of the Tracking Protection database to delay load of scripts from tracking domains when possible during the time a page is actively loading and rendering – I call it tailing.

    This has a positive effect on page load performance as we save some of the network bandwidth, I/O and CPU for loading and processing of images and scripts running on the site so the web page is complete and ready sooner.

  • Taking a break from Adblock Plus development

    After twelve years of working on Adblock Plus, the time seems right for me to take a break. The project’s dependence on me has been on the decline for quite a while already. Six years ago we founded eyeo, a company that would put the former hobby project on a more solid foundation. Two years ago Felix Dahlke took over the CTO role from me. And a little more than a month ago we launched the new Adblock Plus 3.0 for Firefox based on the Web Extensions framework. As damaging as this move inevitably was for our extension’s quality and reputation, it had a positive side effect: our original Adblock Plus for Firefox codebase is now legacy code, not to be worked on. Consequently, my Firefox expertise is barely required any more; this was one of the last areas where replacing me would have been problematic.

  • Don Marti: quick question on tracking protection

    One quick question for anyone who still isn't convinced that tracking protection needs to be a high priority for web browsers in 2018. Web tracking isn't just about items from your online shopping cart following you to other sites. Users who are vulnerable to abusive practices for health or other reasons have tracking protection needs too.

AntiX Linux: A Brief Review

Filed under
Fluxbox
Reviews

Certain factors like systemd are polarizing the Linux community. It seems that either you like it or you hate it. Some of the Debian developers are getting nervous and so a fork of Debian called Devuan has been announced.

I'm always looking at other distros that emphasize compactness and the ability to run on old hardware. I was also intrigued by the Debian controversy with systemd so when I saw AntiX 13.2 was based on Debian Wheezy I had to give it a try. AntiX comes on a single CD so installing it was easy enough.

Read more

Fluxbox 1.3.7 Released With Few Changes

Filed under
Fluxbox

Fluxbox 1.3.6 was released last month after this lightweight window manager went two years without a new release. It looks like the rate of development of Fluxbox is ticking back up as Fluxbox 1.3.7 was just tagged this morning.

Read more

Wayland & Weston 1.5 Officially Released

Filed under
Graphics/Benchmarks
Fluxbox

Wayland 1.5 features a new internal event queue for Wayland display events, which allows for the client library to dispatch delete and error events immediately. On the build front, Wayland now uses non-recursive Makefiles.

As usual, the Weston compositor changes tend to be more interesting these days and includes more work on XDG-Shell, the Weston input stack is now split out into libinput, there's support for the new XWayland Server to be found in this summer's release of X.Org Server 1.16, the full-screen shell was added, an animate window closing event, support for different color depths on different outputs, and other changes.

Read more

Trimming the fat with Fluxbox

Filed under
Fluxbox

omgsuse.com: One of the oft touted reasons to use openSUSE is the stellar support and packaging for a wide-variety of desktop environments. While the amount attention focused on the "big four" is certainly the lion's share, there is still a lot of attention paid towards less popular window managers and desktop environments like Enlightenment, Openbox, Window Maker or Fluxbox.

What is Your Favorite Desktop?

Filed under
KDE
Fluxbox
Software

ostatic.com: Every few years I run a poll on my personal Website to gauge Linux users' favorite desktop. When analyzing the results over the years, some trends do emerge. Is KDE or GNOME king? What has come in third or fourth consistently over the years? How about you, what is your favorite desktop?

Fluxbox 1.3 Released | What’s new | Compile

Filed under
Fluxbox
HowTos

linuxnov.com: Fluxbox is a great lightweight X window manager that does not require a high machine performance to use it. Been a long time since last Fluxbox stable release from two years, finally Fluxbox 1.3 has been released today with quite a few new features.

Flexible for a Fluxbox? – Lightweight X Window Manager

Filed under
Fluxbox
HowTos

thegeekstuff.com: One of the many great things about using UNIX or a UNIX-like operating system is the ability to tailor your environment to your liking. If you want something less resource intensive that offers a greater degree of control then Fluxbox Window Manager is what you’re looking for.

Syndicate content

More in Tux Machines

Programming: GAction, Research on Developers, JavaBeans and Python

  • Sébastien Wilmet: Providing GActions in a library

    GAction represents an action that the user can do in an application, it’s usually present in a menu item or a button. It’s not just a function to launch, it’s a little more involved than that. Overall, providing GActions in a library can be done quite naturally, once the library provides a framework for the application. TeplApplication and TeplApplicationWindow both provide GActions in their public API. They are namespaced with the "tepl-" prefix, to avoid conflicts with other libraries or the application; so the full name of the GActions are "app.tepl-something" or "win.tepl-something". And all the GActions are documented in the class description. Note that TeplApplication and TeplApplicationWindow are not subclasses of GtkApplication and GtkApplicationWindow, because several libraries might want to extend those GTK classes and an application needs to be able to use all those extensions at the same time. A nice solution that doesn’t require to hold a new object in the application: use this design pattern that I’ve already described on my blog.

  • Research: Developers are trusted by the business but the alignment is not felt evenly across different generations

    Welcome to the first in a series of in-depth articles looking at the developer’s role in the modern organisation. In this first post: a new generation has arrived. As organisations shift to becoming technology-focused, developers’ roles have evolved so that they are now playing a crucial role in decision making across their businesses. However, all this newfound alignment isn’t so keenly felt across the whole developer workforce…

  • Jakarta EE: Creating an Enterprise JavaBeans timer

    Enterprise JavaBeans (EJB) has many interesting and useful features, some of which I will be highlighting in this and upcoming articles. In this article, I’ll show you how to create an EJB timer programmatically and with annotation. Let’s go! The EJB timer feature allows us to schedule tasks to be executed according a calendar configuration. It is very useful because we can execute scheduled tasks using the power of Jakarta context. When we run tasks based on a timer, we need to answer some questions about concurrency, which node the task was scheduled on (in case of an application in a cluster), what is the action if the task does not execute, and others. When we use the EJB timer we can delegate many of these concerns to Jakarta context and care more about business logic. It is interesting, isn’t it?

  • Python Dictionary Comprehension

    In this tutorial, we will learn about Python dictionary comprehension and how to use it with the help of examples.

Mozilla and Curl Leftovers

  • Ending QA community events, for now

    QMO events have been around for several years now, with many loyal Mozilla contributors engaged in various types of manual testing activities– some centered around verification of bug fixes, others on trying out exciting new features or significant changes made to the browser’s core ones. The feedback we received through them, during the Nightly and Beta phases, helped us ship polished products with each iteration, and it’s something that we’re very grateful for. We also feel that we could do more with the Testday and Bugday events. Their format has remained unchanged since we introduced them and the lack of a fresh new take on these events is now more noticeable than ever, as the overall interest in them has been dialing down for the past couple of years. We think it’s time to take a step back, review things and think about new ways to engage the community going forward.

  • Tips to improve your Ring camera security

    We cannot stress this enough. Weak and reused passwords are a serious vulnerability to your personal security and privacy. The software that the Nulled crew is using to tap into Ring feeds can be used to take over other things like, say, a Disney+ account. Or your bank account.

  • The Mozilla Blog: Petitioning for rehearing in Mozilla v. FCC

    Today, Mozilla continues the fight to preserve net neutrality protection as a fundamental digital right. Alongside other petitioners in our FCC challenge, Mozilla, Etsy, INCOMPAS, Vimeo and the Ad Hoc Telecom Users Committee filed a petition for rehearing and rehearing en banc in response to the D.C. Circuit decision upholding the FCC’s 2018 Order, which repealed safeguards for net neutrality. Our petition asks the original panel of judges or alternatively the full complement of D.C. Circuit judges to reconsider the decision both because it conflicts with D.C. Circuit or Supreme Court precedent and because it involves questions of exceptional importance.

  • Daniel Stenberg: Reporting documentation bugs in curl got easier

    After I watched a talk by Marcus Olsson about docs as code (at foss-sthlm on December 12 2019), I got inspired to provide links on the curl web site to make it easier for users to report bugs on documentation. Starting today, there are two new links on the top right side of all libcurl API function call documentation pages. File a bug about this page – takes the user directly to a new issue in the github issue tracker with the title filled in with the name of the function call, and the label preset to ‘documentation’. All there’s left is for the user to actually provide a description of the problem and pressing submit (and yeah, a github account is also required).

today's howtos

Fedora, Red Hat and IBM: Flatpak 1.5.2, Cockpit 209, OpenShift, Java and More

  • Flatpak 1.5.2 Continues Work On Authentication Support In Push To Handling Paid Apps

    Introduced last month was the Flatpak 1.5.1 development build that provided initial support for protected/authenticated downloads of Flatpaks as the fundamental infrastructure work towards allowing paid or donation-based applications within Flathub or other Flatpak-based "app stores" on Linux.  Flatpak 1.5.2 is out this Friday morning and it has continued work on this focus for authenticated/protected downloads. There has been new API coverage around the authentication code, an OCI authenticator is now bundled, a simple user/password authentication-driven option similar to HTTP-based authentication, and related work towards opening up new use-cases for Flatpak. 

  • Cockpit 209

    Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 209. A new design for the Overview page The landing page has been completely redesigned. Information is grouped into easier to understand panels, health information is much more prominent, the resource graphs have been moved to their own page, and the hardware information page should now be easier to find.

  • We’re headed for edge computing

    Every week seems to bring a new report on how edge computing is going to take over the world. This crescendo has been building for the past few years, so it’s no surprise that edge computing sits near the peak on the Gartner hype cycle for emerging technologies. But the question remains—will the edge computing phenomenon take over the world as predicted and, if so, how can businesses benefit from it? In this and future articles, we’ll demystify edge computing, examine its motivations, and explore best practices in creating scalable edge deployments and the role of open source at the edge. We’ll also look at 5G and its impact to the telco industry, remote office/branch office, IoT, and other use cases.

  • Persistent data implications for apps and microservices

    Speed and agility are the name of the game, whether you are running track in a triathlon, racing to find cures to the world’s most nefarious diseases, or developing new applications that are changing the way society interacts. Application development teams can have a profound effect, not only on their organizations’ ability to differentiate themselves, but also the world we live in. [...] While just a few years ago, some organizations were still concerned with the viability of running production workloads in containers, the benefits of capitalizing on faster development cycles has garnered favor among developers. And, with enterprise-class enhancements delivered by platforms such as Red Hat OpenShift Container Platform, containers have grown from nifty developer projects, to scalable, more manageable infrastructure environments that enable DevOps for the hybrid cloud.

  • Cloud Pak for Applications supports IBM Z

    The latest version of Cloud Pak for Applications, Version 4.0, extends support for Red Hat OpenShift Container Platform 4.2 onto the IBM Z platform. Now users can extend their hybrid cloud deployments to include Red Hat OpenShift clusters on IBM Z hardware, taking advantage of the container orchestration platform and tools to bring a consistent experience for development of cloud-native workloads. Support for OpenShift on IBM Z in this release of IBM Cloud Pak for Applications is limited to the container platform only. IBM runtimes continue to provide support for IBM Z, including container deployments where appropriate.

  • Exploring OpenShift 4.x Cluster

    In this video we will explore the cluster installed during the last video, log into the cluster, configure an authentication provider. We will understand the structure of the cluster and the architecture overview of HA installation. We will get deep understanding of what runs on the master node vs worker node, how the load balancers are setup. We will also look at the cloud provider to see all the infrastructure components that got created by the installer.

  • Celebrating 20 years of enterprise Java: Milestones

    As we celebrate the last 20 years of enterprise Java, it is important to look back at the platform's history to better understand where it came from and how we arrived where we are today. Enterprise Java emerged during a pivotal time in the history of enterprise computing. When Java 2 Platform, Enterprise Edition (J2EE) 1.2 was introduced in December 1999, it not only marked the birth of enterprise Java, but also signaled an important shift in how organizations were thinking about the web. Roughly five years earlier, in May 1995, the Java programming language had been publicly released. The language was originally developed to address obstacles faced by a stealth innovation team at Sun Microsystems building the Star7, an interactive handheld home entertainment controller; however, after a tepid response from the television industry, the team instead set its sights on the internet. Web browsers were making the web more accessible to users, and when the Java language was first announced by Sun, it came with a crucial endorsement: Netscape, one of the leaders in the nascent Web browser market at the time, announced in 1995 that it would include support for Java in its namesake browser.