❌

Reading view

↗️

Como instalar o LXQt 1.4 no Lubuntu 22.04 LTS

✇Blog do Edivaldo
By: Edivaldo Brito

Descubra como instalar o LXQt 1.4 no Lubuntu 22.04 LTS, usando o repositório Lubuntu Backports PPA dos desenvolvedores do Lubuntu.

Leia o restante do texto "Como instalar o LXQt 1.4 no Lubuntu 22.04 LTS"

O post Como instalar o LXQt 1.4 no Lubuntu 22.04 LTS apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.

  •  
  • ↗️
↗️

Como instalar o VMware Workstation no Ubuntu e derivados

✇Blog do Edivaldo
By: Edivaldo Brito

VMware Workstation no Ubuntu é uma solução poderosa para virtualização. Aprenda como configurá-la facilmente!

O post Como instalar o VMware Workstation no Ubuntu e derivados apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.

  •  
  • ↗️
↗️

Woodpecker CI 3.17 traz suporte a AppArmor em pipelines Docker e melhorias de segurança

✇Blog do Edivaldo
By: Edivaldo Brito

Woodpecker CI 3.17 reforça segurança com AppArmor em containers Docker e ajustes em Kubernetes para pipelines mais seguros.

O post Woodpecker CI 3.17 traz suporte a AppArmor em pipelines Docker e melhorias de segurança apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.

  •  
  • ↗️
↗️

Como instalar a versão mais recente do HandBrake no Ubuntu e derivados

✇Blog do Edivaldo
By: Edivaldo Brito

HandBrake é um dos mais poderosos conversores de vídeo. Se você quiser experimentar ou atualizar o programa, veja como instalar a versão mais recente do HandBrake no Ubuntu e derivados.

Leia o restante do texto "Como instalar a versão mais recente do HandBrake no Ubuntu e derivados"

O post Como instalar a versão mais recente do HandBrake no Ubuntu e derivados apareceu primeiro em Blog do Edivaldo - Informações e Notícias sobre Linux.

  •  
  • ↗️
↗️

JetBrains open sources KotlinLLM runtime code generator

✇InfoWorld

KotlinLLM, a research prototype for delegating runtime logic to a large language model (LLM) from Kotlin code, is now going open source and public, JetBrains announced.

Revealed July 28, KotlinLLM is an IntelliJ IDEA plugin prototype for experimenting with LLM-driven “Smart macros” in Kotlin, enabling code generation, runtime updates, and hot-reloading. In software engineering, LLMs are commonly used during development for code completion, code generation, and program comprehension, JetBrains noted, but using an LLM at run time of a compiled application is much less common. The existing options for doing this have the following trade-offs, according to JetBrains:

  • Direct runtime delegation is slow, non-deterministic, and costly, and makes the application depend on an LLM service at run time.
  • External agent workflows keep the generated logic outside the codebase, where it is harder to review, test, and ship.
  • Most prior work (byLLM, nightjar, Healer) targets interpreted languages like Python, not a compiled, statically typed language like Kotlin.

KotlinLLM addresses these limitations in three ways, JetBrains said:

  • The call site shows that a feature is LLM-backed, so it is visible in code review.
  • Generated behavior is saved as an ordinary Kotlin source, not kept only in the runtime session. It can be committed, reviewed, tested, and distributed like any other code.
  • Once generated, the code runs as plain Kotlin without the plugin. For scenarios that are already covered, there is no further LLM call, so no added latency or cost, and the result is reproducible.

KotlinLLM is open source under Apache License 2.0. The repository contains the KotlinLLM IntelliJ IDEA plugin, the Smart macro API, and example projects.

  •  
  • ↗️
↗️

Hidden Gambling Apps in Brazilian App Store

✇Michael Tsai
By: Michael Tsai

Marcus Mendes:

Last April, Brazilian officials notified Apple and Google over an alleged lack of age controls in betting apps on their respective app stores.

9to5Mac:

Brazilian users browsing the App Store rankings in categories such as Navigation, Travel, and Weather have noticed a growing number of poorly made games appearing among the top results, many of them featuring AI-generated illustrations of animals as their app icons. Many carry an AL age rating, making them available to users of all ages, including children.

As it turns out, these are so-called jacket apps, which are just a front for hidden betting and gambling apps.

[…]

The repository also includes explicit instructions intended to prevent the apps from being flagged as suspicious during App Store review. These include giving each app uniquely named startup and remote-configuration codes, making it harder for reviewers to identify them as part of the same group.

Ironically, the App Store’s own recommendation system appears to have little trouble grouping the apps together, as the “You Might Also Like” section on several of these apps points users toward other suspicious apps more frequently than they point to genuine apps.

John Gruber (Mastodon):

Obviously the main problem is that these apps disguise themselves Trojan Horse-style, and slip through App Store review undetected. I don’t think it’s reasonable to think App Store review could catch every attempt at this sort of thing though — if the horses are disguised well-enough, some of them are going to slip through. That’s actually fine.

I agree that it’s unreasonable to expect App Review to catch all those, but then Apple should not be pretending that it can. This was all obvious from day one. The public perception of App Review is completely at odds with what it actually can and does do.

But the first example 9to5Mac cites isn’t well disguised at all. What sense does it make that “PotatoPlot Puzzle” — a game featuring a rabbit potato farmer — is a weather app? How is that not a red flag right there?

[…]

I always mention that the point of such a squad shouldn’t be to make the App Store 100 percent scammer-free — which I believe is an impossible goal that would set the team up for failure. The point should be only to make the App Store free of successful scams. Focus on the most popular apps and the most lucrative apps.

The App Store is more than 18 years old. The idea of patrolling the top charts probably occurred to Apple before it even shipped. They just don’t want to do it.

Nick Lockwood:

Apple only took 24 hours to approve my iOS app update that crashed instantly on launch. Such a blessing to have that extra level of reliability and security that only a manual review process can provide 🙏

Incidentally, the crash was due to a missing dylib - something that could easily have been detected by the automated scan process, if only that scan were designed to protect users’ and developers’ interests instead of Apple’s.

Kyle Hughes:

There is simply no other way to maintain a modern, healthy software ecosystem without making sure that apps that have been around for 7 years and 20 major versions can’t get a build looked at within 48 hours. There’s no other way. Probably needs to be longer, honestly.

I had to file an Expedited Review Request because this update is a legitimate emergency. Four hours later, App Review rejected the build because they didn’t follow the first sentence of the testing instructions (which haven’t changed in 7 years). Back to Waiting for Review! There’s no other way.

Previously:

Update (2026-07-30): Kyle Hughes:

We got rejected in the Expedited Review again, this time for not having an account deletion feature. Except we do, and it’s one button press away from the screen that the reviewer was on. And it has always existed. Is this how the expedited review works? Malicious incompetence?

Update (2026-07-31): Kyle Hughes:

If you were wondering how long one of the “you can ask us to approve this build and can fix this issue in the next release” App Review errors takes to resolve when you’re in the Expedited Review Queue… me too! So far, 18 hours. (Ignoring the fact that we have the feature the rejection was for.)

Kyle Hughes:

Certainly it means “within a week,” right? “Within a month,” please? “In your lifetime,” I can only hope.

  •  
  • ↗️
↗️

Why open source matters in an AI world

✇InfoWorld

I’m an old Borland guy. I started using Borland tools in the early 1990s, from Turbo Pascal through Delphi. I dabbled in Paradox. I even tried to stick with Borland Office. I wandered through the Inprise years, and the Kylix endeavor, and I was actually a Borland employee during the CodeGear/Embarcadero migrations. 

You could write a book about the rise and fall of Borland. Suffice it to say that things got dodgy when Borland strayed from its focus on developer tools, and they never really recovered.  

One of Borland’s missteps came with the open-sourcing of InterBase, its RDBMS. In the early 2000s, open-source software emerged from the academic shadows and began to commercialize. With the IPO of Red Hat, everyone was jumping on the Linux and open-source bandwagon. Borland made their move into this arena with InterBase. 

Two things soon happened. First, the Firebird project was created as a fork of the InterBase source. Second, Borland retreated from the open-source project and reincorporated InterBase as a closed-source product. One might mark this as the beginning of developers losing faith in Borland.

It was developers, then

And it always ends up being about the developers, right? I mean, who can forget a sweaty, maniacal Steve Ballmer jumping around onstage screaming “Developers, developers, developers”? For many years, Microsoft was notoriously anti-open-source, but even they eventually recognized the power of open-sourcing major tools like .NET and Visual Studio Code. 

But Microsoft didn’t do that out of the goodness of their heart — they clearly saw those tools as a means to bringing developers to their Azure cloud platform. When Amazon launched AWS, they clearly were sidestepping the IT procurement process, making it easy for developers to spin up VMs with just a credit card. Apple shipped the iPhone without an SDK, expecting developers to figure things out.  That didn’t last long, and they soon course-corrected.

Open source is great — but always remember that it offers benefits to companies beyond the software development process. Borland fumbled the ball with their open source efforts, but it soon became obvious how to leverage open source for corporate success. Or, as Stephen O’Grady argues in his book The New Kingmakers, developers are the ones who decide what technologies succeed. Companies quickly recognized that courting developers with open-source software and other free resources was the way to bring them into the fold. Because developers write all the software that makes a tool, platform, or application successful, it’s always a smart move to make developers happy.

It’s developers, now

AI hasn’t changed this equation. The latest incarnation can be seen from the company Nvidia. We think of Nvidia as a hardware company, cranking out GPUs as fast as they can. But GPUs don’t sell unless there is software that runs on them. Coding against a GPU in plain C++ was miserable, so Nvidia developed CUDA, a proprietary layer that made building for their hardware relatively easy. And the more CUDA is used, the more people depend on Nvidia hardware. This is not an accident. As Nader Khalil, Nvidia’s Director of Developer Technologies, told me, “You have to make the best hardware that you can, and you have to make the best software to utilize it. Software is the part of the stack that touches the user.”

Today, of course, developers are all about agentic coding, and Nvidia is eyeball deep in that world. As such, Nvidia provides a set of open-weight models called Nemotron that developers can use, inspect, and fine-tune for their own purposes. And of course Nemotron runs really well on top of CUDA. 

Nvidia, like Microsoft and Amazon, is doing this because they want to sell their products to more people. Nvidia can’t make enough GPUs for Anthropic and OpenAI to keep up with demand, but they also want to sell GPUs to us developers by enabling us to run our own models on our own computers. 

The open source movement began with pure hearts and noble ideals. But the reality of open source is that its nobility is easily melded with business needs. Open source software is really the bait — and developers are the real catch.

  •  
  • ↗️
↗️

MailMaven 1.2

✇Michael Tsai
By: Michael Tsai

SmallCubed:

AppleScript support makes it possible to automate message processing and connect Maven with other applications such as Hookmark, EagleFiler, Filemaker, and DEVONthink. Almost anything you normally do by interacting with MailMaven’s interface, such as searching for messages, tagging, filing, flagging, and composing, can now be automated.

[…]

AppleScript makes it possible to control Maven using the natural language capabilities of AI assistants such as Claude and ChatGPT via a MCP server. […] To connect AI assistants to Maven, we have developed a basic MCP server that implements over 25 end points. This can be downloaded and installed from our MailMavenMCP repository on GitHub. With the MailMavenMCP you can instruct your assistant to access and process messages without the need to write any AppleScript. For example, if you want a summary of the conversation you are reading, simply instruct the assistant to “Summarize the conversation of the currently selected message in MailMaven”.

The AppleScript support is really impressive. It’s extensive and thoughtfully designed and implemented, with performance in mind:

A query is a temporary AppleScript-based smart mailbox that can are used to locate and examine/manage messages.

Using queries is much faster than iterating through messages in mailboxes because it uses Maven’s internal mechanism for locating messages that smart mailboxes use.

Depending on the scope and nature of an iterative search which can take seconds, if not minutes to process, queries are almost instantaneous. Moreover, queries have the ability to sort messages and filter duplicates.

[…]

Scripts can be performed from Maven’s inbox, outbox, and keystroke rules via the Run AppleScript Rule action.

I’m excited to see a new app leaning into this old technology, which remains unsurpassed. EagleFiler is already taking advantage of the AppleScript support to enable importing messages (with all their metadata) just by pressing a hotkey. I also expect it to enable some great new features in future versions of SpamSieve.

Previously:

  •  
  • ↗️
❌