The footer of every page, the site description and the home page still said that Progmasoft builds programming-language infrastructure, languages and compilers. Since Tala and its tools are archived, they describe what Progmasoft makes now, in all four languages: - Footer: "Developer tools and data infrastructure built with durable contracts." - Site and home description: build systems, testing tools, an agentic IDE and data infrastructure. - Home hero: build systems, testing tools, agentic development environments, data infrastructure and the services around them. - The area "Languages and compilers" becomes "Data infrastructure" (columnar in-memory formats and engines for large data on the JVM); "Developer tools" drops language servers for agentic development environments. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Tala and its tools are no longer developed as of 2026-11-10; Progmasoft puts its work into Tazel, a build system for C, C++, Objective-C, Objective-C++ and Zig. ViGet follows: - /langs/tala is removed. /langs/c, /langs/cpp and /langs/objc are the language catalogs (Objective-C++ packages belong to /langs/objc), served by one page, app/viget/langs/[language], which knows only these three; any other language is 404. /langs leads to the language list on the ViGet home page. - lib/viget-catalogs.ts: three open language catalogs with their own title, description and empty state in en-US, de-DE, ru-RU and he-IL; the Tazel catalog describes Tazel as the build system for C, C++, Objective-C, Objective-C++ and Zig. - The ViGet home, header, footer and metadata name C, C++ and Objective-C; "Explore Tala" becomes "Explore Tazel" (tazel.net), and the footer links Tazel instead of Tala. The sitemap lists the three catalogs. - Tests: the catalogs, their texts in every language, no text naming Tala, and the proxy routes. pnpm test (37), lint, check and build pass; next start answers /langs/c, /langs/cpp and /langs/objc with their pages, /langs/tala and /langs/zig with 404, and /langs with 308 to the language list.
Xide is no longer developed as of 2026-11-08 (Progmasoft/xide#29), so Progmaweb stops presenting it: - product.progmasoft.com: Xide leaves the catalog, its card and its detail page; /xide on the product host is a 404 like any unknown product. The catalog's description in every language names the Tala language with its tools and Catch3. - ides.progmasoft.com served only the IDE list and the Xide page, so the whole site goes: the pages under app/ides, its texts in every language, idesRoute and its host in the proxy, and both nginx server blocks. The certificate of progmasoft.com no longer has to name it. Tests: the catalog lists the remaining products and refuses xide.
progmasoft.com/privacy and progmasoft.com/security publish the two policies in en-US, de-DE, ru-RU and he-IL, and the footer links both. The Privacy Policy says what an account keeps and that Progmasoft keeps an IP address for one purpose only: with a ViGet upload, to establish where an upload that turns out to be malicious software came from and to give it to the competent authorities. It says that no data, the IP address included, is sold, rented or traded. The Security Policy covers passwords, sessions, HTTPS, the ban on malicious software in ViGet and how to report a weakness. The registration form asks the person to accept both policies, and the API refuses a registration without that acceptance, with a password (acceptPolicies, a validation error of that field) or through Google: the start of a Google registration without acceptPolicies=true goes back to /register?google=policies-required, and the completion creates no account unless the authentication state carries the current version. An account keeps the version it accepted and the moment, in two new columns that schema step 2 adds; accounts created before it keep null. PolicyAcceptance.CurrentVersion and policyVersion on the web side name the same date, and a web test reads the C# constant to keep them equal.
tazel.tala.run only redirects to tazel.net now. The product list and the Tazel plugin catalog link the new address directly.
The pages of progmasoft.com and its hosts had no content security policy. The proxy now creates a 128-bit nonce for every request and sends the policy both ways: on the request, so that Next marks its own inline scripts with the nonce, and on the response. The layout reads the nonce for the theme bootstrap. Every page is rendered on demand already, so none is served with a stale nonce. Scripts may come from the host, carry the nonce, or be Cloudflare's Web Analytics beacon from static.cloudflareinsights.com, which reports to cloudflareinsights.com. 'strict-dynamic' is left out, because browsers ignore host sources under it and the beacon is added by Cloudflare without a nonce. Styles allow inline ones; objects, framing and other base URLs are refused. There is no form-action: sign-in and OAuth consent end in redirects to other hosts, loopback addresses included, and browsers apply form-action to them. The development server also gets 'unsafe-eval' for its hot reload. Tests check the nonce and each directive; ARCHITECTURE.md describes the policy.
The sites declared no icon and /favicon.ico answered 404, so search engines and assistants that show a site's icon (DuckDuckGo, ChatGPT) fell back to a gray placeholder; the only copy of the mark was the BIMI logo for mail. The app now has the Next.js icon files, so every page links them: - app/icon.svg: the four squares of the BIMI logo, cropped to the mark so it fills a browser tab, on a transparent field. - app/favicon.ico: the same mark at 16, 32 and 48 pixels (PNG entries), for clients that ask for /favicon.ico without reading the page. - app/apple-icon.png: 180 pixels on the white field of the BIMI logo, since iOS fills transparency with black. The proxy rewrites paths per host, which would send /icon.svg on the account, ViGet and the other hosts into their own page trees; the matcher now skips the two new files as it already skipped favicon.ico, so every Progmasoft host serves the same icons.
The API of the previous commit holds the catalog; this adds what people and Tazel reach. Pages: - /dslplugins/tazel lists the published plugins, read from the API on its loopback address, and says when there is none. - /dslplugins/tazel/<Publisher>/<Name> is the page of a plugin: its description, publisher, latest version, license, authors, homepage and repository, the plugins block that uses it, and every version with its date, plugin API, size, SHA-256, yanked mark and JAR. - /dslplugins/gradle opens the Gradle catalog. It only lists: Gradle takes com.progmasoft.tazel.plugin from the Gradle Plugin Portal. - The availability note says that Progmasoft publishes first and every account later. Texts are in the four languages of the site. Nginx (ops/nginx/progmaweb.conf): - On viget.progmasoft.com, index.json of a plugin goes to the API and the JARs come from /srv/viget/files with immutable caching; /api/ stays closed. - maven.progmasoft.com serves /srv/maven, whose /tazel holds tazel-api. ops/README.md describes the directories, their SELinux labels, the publish and yank commands, and how a release of Tazel copies the API into the Maven repository. Tests cover the texts in every language, the plugins block, the Gradle list, and that a page asks the API only for identifiers.
progmasoft.com presents Progmasoft as a pool of technology areas instead of a list of products: languages and compilers, build and packages, developer tools, quality and testing, identity and access, and infrastructure. The page has a new hero, a bento of areas, principles and a developers band that leads to the Progmasoft Console; the products are one link away in their own catalog. product.progmasoft.com lists Tala, talac, talafmt, talalint, Tazel, Xide and Catch3, each with its own page (/tala-lang, /talac, ...) that leads to the product's site and source. ides.progmasoft.com lists the IDEs and hosts the Xide site at /xide; catch3.progmasoft.com is the Catch3 site. The facts follow the READMEs and documentation of the product repositories: Xide is marked as early work, and Catch3 states that it is not an official Catch2 release. The theme switch no longer freezes or flickers. The layout rendered data-theme="light" on <html>, so every server re-render of the layout (a language switch) set it back. The control also applied the theme in an effect after the render while buttons animated their colours. The attribute now belongs to the bootstrap script and the control alone; the control applies the theme in the click, and transitions are off for the two frames of the change. All new text is in en-US, de-DE, ru-RU and he-IL. The old home messages leave localization.ts. The proxy maps the new hosts through one table, and nginx gains their virtual hosts.