Slashdot reader BrianFagioli writes: GIMP has officially launched its own Snap package for Linux, finally taking over from the community-maintained Snapcrafters project. The move means all future GIMP releases will now be built directly from the team's CI pipeline, ensuring faster, more consistent updates across distributions. The developers also introduced a new "gimp-plugins" interface to support external plugins while maintaining Snap's security confinement, with GMIC and OpenVINO already supported.

This marks another major step in GIMP's cross-platform packaging efforts, joining Flatpak and MSIX distribution options. The first officially maintained version, Version 3.0.6GIMP 3.0.6, is available now on the "latest/stable" Snap channel, with preview builds rolling out for testers.

Mozilla plans to introduce a suite of paid professional services for its open-source Thunderbird email client, transforming the application into a comprehensive communication platform. Dubbed "Thunderbird Pro," the package aims to compete with established ecosystems like Gmail and Office 365 while maintaining Mozilla's commitment to open-source software.

The Pro tier will include four core services: Thunderbird Appointment for streamlined scheduling, Thunderbird Send for file sharing (reviving the discontinued Firefox Send), Thunderbird Assist offering AI capabilities powered by Flower AI, and Thundermail, a revamped email client built on Stalwart's open-source stack. Initially, Thunderbird Pro will be available free to "consistent community contributors," with paid access for other users.

Mozilla Managing Director Ryan Sipes indicated the company may consider limited free tiers once the service establishes a sustainable user base. This initiative follows Mozilla's 2023 announcement about "remaking" Thunderbird's architecture to modernize its aging codebase, addressing user losses to more feature-rich competitors.

An anonymous reader quotes a report from Ars Technica: Thousands" of complaints about the volume of TV commercials have flooded the Federal Communications Commission (FCC) in recent years. Despite the FCC requiring TV stations, cable operators, and satellite providers to ensure that commercials don't bring a sudden spike in decibels, complaints around loud commercials "took a troubling jump" in 2024, the government body said on Thursday.

Under The Commercial Advertisement Loudness Mitigation (CALM) Act, broadcast, cable, and satellite TV providers are required to ensure that commercials "have the same average volume as the programs they accompany," per the FCC. The FCC's rules about the volume of commercials took effect in December 2012. The law also requires linear TV providers to use the Advanced Television Systems Committee's (ATSC's) recommended practices. The practices include guidance around production, post production, metadata systems usage, and controlling dynamic range. If followed, the recommendations "result in consistency in loudness and avoidance of signal clipping," per the ATSC [PDF]. The guidance reads: "If all programs and commercials were produced at a consistent average loudness, and if the loudness of the mix is preserved through the production, distribution, and delivery chain, listeners would not be subjected to annoying changes in loudness within and between programs."

As spotted by PC Mag, the FCC claimed this week that The Calm Act initially reduced complaints about commercials aggressively blaring from TVs. However, the agency is seeing an uptick in grievances. The FCC said it received "approximately" 750 complaints in 2022, 825 in 2023, and "at least" 1,700 in 2024 [PDF]. Since The Calm Act regulates a commercial's average loudness, some advertisers may be skirting the spirit of the law by making commercials very loud at the start (to get viewers' attention) before quieting down for the rest of the ad. In response to growing complaints, the FCC is reexamining its rules and this week announced that it's seeking comment from "consumers and industry on the extent to which The CALM Act rules are effective." The FCC is also asking people to weigh in on what future actions the FCC, the TV industry, or standard developers could take. The FCC is considering whether to extend the Calm Act to online streaming services, which are increasingly offering plans with ad-supported models and live event broadcasts.

U.S. Director of National Intelligence Tulsi Gabbard has condemned a British order requiring Apple to break its encrypted storage worldwide as an "egregious" violation of American rights that could breach the CLOUD Act facilitating cross-border investigations. In a letter [PDF] to Senator Ron Wyden and Representative Andy Biggs, Gabbard revealed she has directed a legal review of the secret order, which she learned about through media reports.

"This would be a clear and egregious violation of Americans' privacy and civil liberties, and open up a serious vulnerability for cyber exploitation by adversarial actors," Gabbard wrote. The UK Home Office, under the Investigatory Powers Act, prohibited Apple from disclosing the order to Congress or U.S. regulators. The directive would have forced Apple to compromise its Advanced Data Protection encryption, enabling officials to access individual data. Apple refused compliance, instead withdrawing the secure storage option from UK customers while maintaining it elsewhere globally. Despite Apple's pullback, the UK demand for backdoor creation remains. Gabbard pledged to ensure UK actions protect American privacy rights "consistent with the CLOUD Act and other applicable laws."

An anonymous reader quotes a report from The Hill: In the wake of the COVID-19 pandemic, the dynamics of the workplace have undergone a seismic shift. While some heralded the return to the office as a sign of normalcy, evidence suggests that for many, this transition has been far from smooth sailing. Nowhere is this struggle more evident than in the case of the U.S. federal government employees, particularly those within the Department of Justice. At the beginning of the year, the Justice Department initiated a return-to-office policy requiring much of its workforce to be present in person for up to six days per pay period or about three days per week. However, there were more stringent requirements for assistant U.S. attorneys. While approximately 70 percent of AUSAs currently enjoy the flexibility of two days per week of telework, recent changes in telework policies within certain offices have left many feeling stranded.

A survey by the National Association of Assistant U.S. Attorneys (NAAUSA) reveals a stark contrast in job satisfaction between those with telework options and those without. In offices where routine telework has been curtailed, a staggering 81 percent of respondents admitted they were actively seeking alternative employment opportunities. This dissatisfaction stands in contrast to offices where some level of telework is maintained, where only 42 percent of respondents expressed a desire to leave their current positions. NAAUSA Vice President Adam Hanna aptly summarizes the situation as a "workforce revolt." It's a sentiment echoed by employees across various offices, underscoring the critical importance of telework in retaining talent and maintaining morale. This is yet another testament to the value placed on flexibility and work-life balance -- crucial factors in the recruitment and retention of top talent. In response to the survey findings, NAAUSA has urged Justice Department leadership to implement consistent telework policies across all offices. The organization recommends a minimum baseline of two telework days per week, citing the importance of treating employees as responsible professionals capable of balancing in-person and remote work effectively.

The issue extends beyond individual preferences, resonating with broader concerns surrounding recruitment, retention, and workplace culture. Employee organizations within the Justice Department have united in calling for a review of return-to-office mandates, citing potential negative impacts on productivity and workforce retention. These findings align with broader evidence of telework's positive effects, including the Office of Personnel Management's annual report (PDF) about telework in the federal government. That report showed that a staggering 68 percent of teleworking federal government employees intend to remain in their current positions, in contrast to a mere 53 percent of non-telecommuters. This underscores the pivotal role of telework in fostering employee loyalty and commitment.

Andrew Tarantola reports vai Engadget: Just seven months after its beta debut, Adobe's Firefly generative AI is set to receive a trio of new models as well as more than 100 new features and capabilities, company executives announced at the Adobe Max 2023 event on Tuesday. The Firefly Image 2 model promises higher fidelity generated images and more granular controls for users and the Vector model will allow graphic designers to rapidly generate vector images, a first for the industry. The Design model for generating print and online advertising layouts offers another first: text-to-template generation.

Firefly Image 2 is the updated version of the existing text-to-image system. Like its predecessor, this one is trained exclusively on licensed and public domain content to ensure that its output images are safe for commercial use. It also accommodates text prompts in any of 100 languages. Adobe's AI already works across modalities, from still images, video and audio to design elements and font effects. As of Tuesday, it also generates vector art thanks to the new Firefly Vector model. Currently available in beta, this new model will also offer Generative Match, which will recreate a given artistic style in its output images. This will enable users to stay within bounds of the brand's guidelines, quickly spin up new designs using existing images and their aesthetics, as well as seamless, tileable fill patterns and vector gradients.

The final, Design model, is geared heavily towards advertising and marketing professionals for use in generating print and online copy templates using Adobe Express. Users will be able to generate images in Firefly then port them to express for use in a layout generated from the user's natural language prompt. Those templates can be generated in any of the popular aspect ratios and are fully editable through conventional digital methods. The Firefly web application will also receive three new features: Generative Match, as above, for maintaining consistent design aesthetics across images and assets. Photo Settings will generate more photorealistic images (think: visible, defined pores) as well as enable users to tweak images using photography metrics like depth of field, blur and field of view. The system's depictions of plant foliage will reportedly also improve under this setting. Prompt Guidance will even rewrite whatever hackneyed prose you came up with into something it can actually work from, reducing the need for the wholesale re-generation of prompted images.

Thunderbird blog: Before we really dig in, let's start with the future. We believe it's a bright one! With this year's release of Thunderbird 115 "Supernova," we're doing much more than just another yearly release. It's a modernized overhaul of the software, both visually and technically. Thunderbird is undergoing a massive rework from the ground up to get rid of all the technical and interface debt accumulated over the past 10 years. This is not an easy task, but it's necessary to guarantee the sustainability of the project for the next 20 years. Simply "adding stuff on top" of a crumbling architecture is not sustainable, and we can't keep ignoring it. Throughout the next 3 years, the Thunderbird project is aiming at these primary objectives:

1. Make the code base leaner and more reliable, rewrite ancient code, remove technical debt.
2. Rebuild the interface from scratch to create a consistent design system, as well as developing and maintaining an adaptable and extremely customizable user interface.
3. Switch to a monthly release schedule.

Inside those objectives there are hundreds of very large steps that need to happen, and achieving everything will require a lot of time and resources.

Roblimo once called it "a tradition, not just a speech" -- Bryan Lunduke's annual "Linux Sucks" presentations at various Linux conferences. But before you get too upset, in his 2014 interview with Slashdot Lunduke admitted "I love Linux, I have made my whole life around Linux. I work for Linux companies. I write for Linux magazines, but it really blows..."

This year he's releasing a special YouTube version of Linux Sucks 2020, the first time Lunduke has attempted the talk without a live audience, "And it feels really wicked weird." But he's still trying to get a rise out of his audience. "Follow me on this into Journey Into Graphs and Numbers Land," Lunduke says playfully, pulling up one of his 160 x 90 pixel slides showing current market share for Windows, Mac, and then Linux "You might notice that some platforms have a higher market share than Linux does," he says with a laugh, describing one slide showing Linux as "scooping up the bottom of the barrel at 1.6%..."

"But here's the thing. These numbers have been either consistent, or for Linux, slowly dropping." And then he puts up a graph showing the number of searches for Linux. "If you look back at 2004 -- the year 2004, 16 years ago -- that was the high point in interest in searching for the word Linux (or Linux plus other things). 2006 it was about half that -- so about two years later it had dropped down to about half. Here in 2020 it is so low, not only does it not fill up the first bar of pixels there, it's like only three pixels in. That doesn't happen -- that sort of decline does not happen -- unless the platform sucks. That's just the truth of the matter. That's just how it goes, right?"

And there's also some very specific reasons why Lunduke thinks Linux sucks:

nut (Slashdot reader #19,435) writes: A study by economists Sergio Correia, Stephan Luck and Emil Verner suggests that the best way to save your economy is to save your people. The authors looked at the economic impact of the Spanish influenza pandemic of 1918 on different U.S. cities. They concluded that the earlier, more forcefully and longer cities responded, the better their economic recovery.
A faculty affiliate from the Harvard Department of Economics writes in Bloomberg: [C]ities that implemented aggressive social distancing and shutdowns to contain the virus came out looking better. Implementing these policies eight days earlier, or maintaining them for 46 days longer were associated with 4% and 6% higher post-pandemic manufacturing employment, respectively. The gains for output were similar. Likewise, faster and longer-lasting distancing measures were associated with higher post-pandemic banking activity...

[T]his is at least consistent with the arguments my Bloomberg Opinion colleagues Noah Smith and Michael Strain have already put forward for why easing distancing measures too early would be potentially devastating for the economy... [I]t looks like the things we should be doing to save lives are also what we should be doing to save the economy.

An anonymous reader quotes a report from ZDNet: A software engineer pulled a personal project down after he found out that one of the companies using it had recently signed a contract with the U.S. Immigrations and Customs Enforcement (ICE). The engineer, Seth Vargo, cited the ICE's "inhumane treatment, denial of basic human rights, and detaining children in cages," as the reason for taking down his library. The project was called Chef Sugar, a Ruby library for simplifying work with Chef, a platform for configuration management. Varga developed and open-sourced the library while he worked at Chef, and the library was later integrated into Chef's source code.

Earlier this week, a Twitter user discovered that Chef was selling $95,000-worth of licenses through a government contractor to the ICE. The news didn't go well with Vargo, who, yesterday, September 19, took down the Chef Sugar library from both GitHub and RubyGems, the main Ruby package repository, in a sign of protest. "I have a moral and ethical obligation to prevent my source from being used for evil," Vargo wrote on the now-empty Chef Sugar GitHub repository. Vargo's actions didn't go unnoticed, and in a blog post published later in the day, Chef Software CEO Barry Crist said the incident impacted "production systems for a number of our customers." The Chef team fixed the issue by scouring some of the older Chef Sugar source code and re-uploading it on their own GitHub account. Following public criticism of the contract, Chef Software CEO Barry Crist responded by saying the company had been a long-time ICE collaborator for years, since the previous administration, long before ICE became the hated agency it is today.

"While I understand that many of you and many of our community members would prefer we had no business relationship with DHS-ICE, I have made a principled decision, with the support of the Chef executive team, to work with the institutions of our government, regardless of whether or not we personally agree with their various policies," Crist said.

"I want to be clear that this decision is not about contract value - it is about maintaining a consistent and fair business approach in these volatile times. I do not believe that it is appropriate, practical, or within our mission to examine specific government projects with the purpose of selecting which U.S. agencies we should or should not do business," Crist added.

President Donald Trump signed the Music Modernization Act (MMA) into law Thursday, officially passing what is arguably the most sweeping reform to copyright law in decades. From a report: The bill revamps Section 115 of the U.S. Copyright Act and aims to bring copyright law up to speed for the streaming era. These are the act's three main pieces of legislation:
1. The Music Modernization Act, which streamlines the music-licensing process to make it easier for rights holders to get paid when their music is streamed online.
2. The Compensating Legacy Artists for their Songs, Service, & Important Contributions to Society (CLASSICS) Act for pre-1972 recordings.
3. The Allocation for Music Producers (AMP) Act, which improves royalty payouts for producers and engineers from SoundExchange when their recordings are used on satellite and online radio (Notably, this is the first time producers have ever been mentioned in copyright law.).

What does all this mean? First, songwriters and artists will receive royalties on songs recorded before 1972. Second, the MMA will improve how songwriters are paid by streaming services with a single mechanical licensing database overseen by music publishers and songwriters. The cost of creating and maintaining this database will be paid for by digital streaming services. Third, the act will take unclaimed royalties due to music professionals and provide a consistent legal process to receive them. Further reading: Billboard.

jsuda (822856) writes "Most of us know that making money is difficult and saving it is even harder, but understanding money is easy–it's just coins and folding certificates, a mere medium of exchange. That's wrong! according to Felix Martin, author of Money: The Unauthorized Biography. Not only is that understanding wrong but it's responsible (in large part) for the 2007 Great Recession and the pitiful 'recovery' from it as well as a number of previous financial and credit disasters." Keep reading for the rest of Jsuda's review.

TheSilentNumber writes "A member of Students for Free Culture has just published a thorough and detailed post calling for the retirement of the non-free clauses, NoDerivatives (ND) and NonCommercial (NC). They state, 'The NC and ND clauses not only depend on, but also feed misguided notions about their purpose and function.' and that 'Instead of wasting effort maintaining and explaining a wider set of conflicting licenses, Creative Commons as an organization should focus on providing better and more consistent support for the licenses that really make sense.'" Note that the opinions expressed are of the author alone and not necessarily the entire organization. More info on the process of revising the CC licenses.

John Cowan recently gave a talk on the progress of R7RS (slides), the next revision of the Scheme language standard, at LispNYC. After the R6RS debacle, the community stepped back and is now basing the next standard on R5RS; the work has been split into two languages — R7RS-Small and R7RS-Large. The first working group is preparing to issue a final draft of the R7RS-Small language (PDF; clocking in at 73 pages vs. R5RS's 50) within the next few weeks. Read on for a summary of the planned changes to R7RS (more or less in the order of presentation).

Since the release of Baldur's Gate in 1998, BioWare has cultivated a strong reputation for quality role-playing games, exploring various aspects of the genre ranging from traditional D&D roles and rules to space marine and Jedi Knights. Dragon Age: Origins is a shift back to traditional swords-and-sorcery standards, unashamedly embracing the archetypes that made RPGs what they are, and using them to tell a complex, interesting story in a familiar yet unexplored world. In addition, BioWare has done yet another iteration of their combat system to make it deeper and allow the player to dictate the level of engagement. The result is that Dragon Age: Origins is one of the best RPGs in recent history. Read on for the rest of my thoughts.

andrew cooke writes "Java 6 was recently released, but many programmers are still exploring the features introduced in Java 5 — probably the most significant changes in the language's twelve year history. Amongst those changes (enumerations, auto-boxing, foreach, varargs) generics was the most far-reaching, introducing generic programming in a simpler, safer way than C++ templates and, unlike generics in C#, maintaining backwards (and forwards) compatibility with existing Java code." Read on for the rest of Andrew's review.

Michael J. Ross writes "Experienced and conscientious Web developers, in their efforts to learn from the mistakes of others and to avoid repeating them on their own projects, tend to accumulate tips and recommendations for the many aspects of successfully creating Web sites. These best practices take the form of bookmarked Web pages, saved articles, downloaded PDF files, scribbled notes on scraps of paper, and hastily created documents that will be better organized one of these days, when the developer's schedule becomes less hectic (sure...). Being difficult if not impossible to find later, these pearls of wisdom are rarely consulted before or during each new Web site project. What the developer needs is a book that brings together as many of these best practices as possible, without being overwhelming. Deliver First Class Web Sites: 101 Essential Checklists may be the answer." Read the rest of Michael's review.

Here are OSDL CEO Stuart Cohen's answers to your questions, many of which were spurred by the recent release of an OSDL co-sponsored Linux TCO study (that anti-open source commentator Rob Enderle has already/inevitably questioned).

Slashdot readers both contributed and helped moderate questions for the New Voters Project Presidential Youth Debate. You can read the answers below, but if you'd like to see an expanded introduction, thumbnails of the candidates, and different formatting, go to the Youth Debate page. And that's not all: We're supposed to get candidates' rebuttals on or about October 17, so don't touch that dial!

A long, long time ago, you asked lobbyist Morgan Reed questions about lobbying, undue industry influence on United States laws as they apply to the tech sector, the future of internet taxation, and more. Reed, in the meantime, has switched jobs: he's now working for the Association for Competitive Technology (as he candidly and lightheartedly acknowledges, "the enemy" to many Slashdot readers, since they lobby for large software corporations, notably Microsoft), and is finally free to answer your questions. Read on for about as inside a viewpoint as you can find on how you can affect your elected representatives, from someone whose job is to do just that. Update: 08/01 19:24 GMT by M : That's Morgan Reed, not Reed Morgan. We suck.