Sourav Rudra writes that the GNOME Shell Extension review process is being overwhelmed by low-quality submissions generated by large language models. In response to a continued deluge of poorly coded content despite previous guidelines, developer Javad Rahmatzadeh has drafted specific technical instructions aimed at guiding these automated models toward better coding practices. This new approach seeks to minimize manual review strain by addressing common mistakes like unnecessary error handling and improper resource cleanup directly through model prompting instructions.
- Guidance advises bots to target a single GNOME Shell version rather than attempting broad compatibility via overengineering.
- New rules require personal use LLM-generated extensions to include a specific disclaimer in the code comments.
- Common errors being addressed include failing to properly disconnect signals or destroy widgets during cleanup.
- Guidance advises bots to target a single GNOME Shell version rather than attempting broad compatibility via overengineering.
- New rules require personal use LLM-generated extensions to include a specific disclaimer in the code comments.
- Common errors being addressed include failing to properly disconnect signals or destroy widgets during cleanup.
Gemini CLI extensions can now define settings that the user will be prompted to provide upon installation, ensuring extensions have exactly what they need to function from the moment you install them. This post details the benefits of extension settings, provides a practical example with the AlloyDB extension, and explains how to define settings as an author and manage them with the config command.
Extensions load unknown sites into invisible Windows. What could go wrong?
Google is renaming 'Gemini Extensions' to 'apps' in the latest beta version of the Google app on Android. The change includes updates to the account menu and the full page for enabling and disabling each tool.
Allow user to edit web-page textareas with Emacs (and other editors).
