@kaveinthran @menelion @jcsteh @Scott @cachondo @josh @matt @pneumasolutions @hartgenconsult @pixelate @doubletap @brian_hartgen @Tamasg @ppatel @tspivey Context: some of the add-ons brought up in the initial post (which I replied to) are recent add-ons when in fact parts of what was proposed was implemented by older add-ons (as in first released years ago). We owe Tyler for giving us a form of layer commands management facility.
J
joslee@mastodon.world
@joslee@mastodon.world
Posts
-
Full of Keyboard Commands, So Many of Them, and It Breaks My heart -
There is a point brought up in the #nvda add-on mailing list on AI slop being added to the store@Orinks @kaveinthran @NVAccess @Tamasg @FreakyFwoof So, what can happen is that the add-on author accepts whatever is generated without realizing that: 1. someone already did it before (there are ad-dons with duplicate functionality but written quite differently), or 2. the code isn't quite formatted according to expectations from NVDA/add-on comunity (tabs for indentation versus spaces, for example).
-
There is a point brought up in the #nvda add-on mailing list on AI slop being added to the store@kaveinthran @Orinks @NVAccess @Tamasg @FreakyFwoof Some come from vibe coding, others come from more traditional AI assisted coding. Remember that AI generated code gets part of their "power" from data (or for LLM's, a large corpus) wihch includes example code scattered around the net and the world.