"IT WoRKs BeTter in the App "
The post critiques the Google Calendar mobile app’s inability to subscribe to calendars directly from a URL, despite the author having a compatible Android 17 device. The author notes that adding a calendar via the desktop web interface (using desktop mode on a phone) successfully syncs to the app, highlighting a functional gap in the native app. The commentary expands to a general observation that many companies favor native apps to increase user engagement, yet often deliver incomplete features that force users back to browsers. Historically, the author references early mobile platforms (Symbian, BlackBerry, Palm) and identifies the difficulty of updating apps across numerous devices as a persistent issue, suggesting that dynamic content delivery—essentially a web‑browser model—offers a more efficient solution. The author acknowledges that native apps can provide advantages such as home‑screen icons and offline capabilities, which are increasingly supported by modern web technologies, and calls for fully functional implementations when native apps are produced.
Get your Windows license refund
Giuseppe Salustri recounts a protracted MSI refund process. After shipping his computer to MSI’s Polish service center and enduring long wait times and multiple reminders, he ultimately received a €40 refund, reduced by shipping costs that MSI charged the customer. He advises future claimants to avoid using MSI’s generic support email; instead, they should register on the MSI website and open a ticket, providing the product’s serial number, personal details (first name, last name, mailing address, phone number) from the outset to streamline the procedure.
Comments express widespread frustration with laptops sold pre‑installed with Windows, describing the OS as bloated, slow, and costly, and advocating the right to refuse it and receive a refund. Several users note that only a few manufacturers (e.g., Lenovo, ASUS, Acer) readily offer non‑Windows options, while Dell and others tend to ship Windows‑only models. Many share positive experiences after switching to Linux, highlighting improved performance and ease of use, and suggest purchasing from vendors that provide OS‑free hardware or using cheap third‑party Windows keys as a workaround.
Inception-style curved map for turn-by-turn directions
Orbify’s “Demo 2 – v72” is presented under the heading “NavigationReimagined.” The page indicates the demo is being prepared and labels the release as version 72. All references note that the technology is patent‑pending, citing the international application PCT/EP2026/058725. A copyright notice states © 2026 Orbify, reiterating the pending patent status. The content consists solely of these identifiers and the preparation status, without further technical description or functional details.
The comments recognize the concept as visually striking and potentially useful for navigation, especially for illustrating upcoming turns and lane choices. Repeated concerns focus on motion‑induced nausea, especially during sharp bends, and the difficulty of estimating distances and road size from the curved view. Many suggest adjustable curvature, view‑angle controls, or hybrid overlays to improve readability, while others question practical benefits compared with conventional top‑down maps or note technical limitations on certain browsers. Overall sentiment is mixed: interest in the idea tempered by usability and comfort challenges.
Autistici/Inventati's main .org domain goes dark after US terrorism designation
The page is a Mastodon post titled “cavallette: ‘Some hours ago the domain autistici.org became un…’” hosted on the Bida.im instance. The only visible content is the title and a standard Mastodon notice prompting users to enable JavaScript to view the web application. No additional text, images, or context about the domain’s status, cause of the outage, or any follow‑up information is provided in the scraped excerpt. Consequently, the core information conveyed is that a user named “cavallette” reported that the domain autistici.org had become unavailable a few hours prior to the post. No further technical details, timestamps, or related discussion are present.
The comments convey strong criticism of the U.S. Treasury’s sanctions on the Italian provider Autistici Inventati, describing the move as alarming and indicative of overreach. Contributors highlight the service’s broad use by activist groups and non‑profit organizers, questioning the labeling of anti‑fascist activity as extremist and warning that foreign hosting could expose communications to U.S. surveillance. There is consensus that the action undermines free expression, reinforces distrust of governmental motives, and underscores the need for decentralized, end‑to‑end encryption solutions.
OpenStreetMap State of the Map 2026
State of the Map 2026 will be held in Paris and online over three days, featuring talks, workshops, discussion rounds, and related activities for OpenStreetMap contributors. Attendees—both in‑person and remote—can access logistical information (venue access, full programme, mobile programme), join community chat rooms on Matrix or Telegram, follow social channels such as Mastodon, and view social‑event details, conference posters, and live streams. Holders of Venueless tickets receive a dedicated interactive page for streams, Q&A, and breakout rooms. The event’s visual branding includes partner logos for TomTom, Michelin Mapping Factory & AI Lab, ESRI, Fédération des pros d'OSM, HERE, TOSIT, Iphigénie, Geofabrik, SOGEFI Ingénierie Géomatique, Centre Régional Auvergne‑Rhône‑Alpes de l’Information Géographique, OsmAnd, Overture Maps Foundation, Thales, Stadia Maps, and Capgemini.
The remarks convey a neutral, inquisitive tone, focusing on logistical and compliance questions. Several comments note discovering information while traveling, pinpoint an event at a specific venue, and acknowledge an implied reference or joke. A separate query raises uncertainty about whether OpenStreetMap adheres to a U.S. executive order concerning naming conventions. Overall, the discussion centers on location awareness and a request for clarification on policy compliance, without strong positive or negative sentiment.
OpenAI: Migrating to HTTPX2
The OpenAI Python SDK now uses HTTPX2 for both synchronous and asynchronous HTTP clients, replacing the previous httpx dependency. When creating an OpenAI or AsyncOpenAI client without specifying http_client, existing API calls, response models, streaming, authentication, retries, and numeric timeouts continue to work, and no extra installation is required. HTTPX2 switches the default TLS trust store from certifi to the operating‑system store; containers or environments lacking system CAs must install them or set SSL_CERT_FILE/SSL_CERT_DIR. Custom clients must be built with HTTPX2 objects (httpx2.Client, httpx2.AsyncClient, httpx2.Timeout, httpx2.HTTPTransport, etc.) or the provided helpers (DefaultHttpx2Client, DefaultAsyncHttpx2Client). Authentication hooks now receive HTTPX2 request/response objects, and raw responses, streaming, and exceptions use HTTPX2 types. Legacy httpx can still be used via a runtime “escape hatch” by casting to Any, but type checking will warn and this support may be removed. aio‑http integration is also updated to use an HTTPX2‑native transport (DefaultAioHttpClient).
The comments express skepticism toward the recent shift to an httpx‑derived client, highlighting concerns about upcoming breaking changes in httpx 1.0 and questioning why OpenAI and Anthropic did not simply fund improvements to the established requests library. Participants note the stability promised by the httpx2 fork, mention the use of the operating system TLS trust store, and ask for concrete advantages of the new approach, while also remarking on the slow adoption of HTTP/3. Overall, the tone is questioning and cautious, seeking justification for the change.
Hilariously Fast Volume Computation with the Divergence Theorem
The article derives an O(n) algorithm for computing the volume of a closed, triangulated 3‑D mesh using the divergence theorem. By selecting the vector field F = ⟨x,0,0⟩, whose divergence equals 1, the volume integral ∭₍R₎1 dV becomes the surface integral ∬₍S₎F·dS. Each triangle Tᵢ is parametrized with vertices Tᵢ₀,Tᵢ₁,Tᵢ₂, yielding edge vectors Δ₁ = Tᵢ₁−Tᵢ₀ and Δ₂ = Tᵢ₂−Tᵢ₀. The cross product Δ₁×Δ₂ is constant over the triangle; only its x‑component contributes due to F. Evaluating ∬₍Tᵢ₎ x dA gives (1/6)(Tᵢ₀ₓ+Tᵢ₁ₓ+Tᵢ₂ₓ). Substituting produces the compact volume formula
V = (1/6) ∑ᵢ (Δ₁×Δ₂)ₓ · (Tᵢ₀ₓ+Tᵢ₁ₓ+Tᵢ₂ₓ).
The algorithm requires a single loop over triangles, with seven additions and three multiplications per triangle plus one outer multiplication, totaling roughly 11 n floating‑point operations. Consequently, it can process tens of millions of triangles per frame on modest hardware (e.g., a $35 Raspberry Pi at 60 fps). The method mirrors known techniques from prior mesh‑processing literature.
The comments collectively express interest in algorithms for computing polyhedron volume and related properties, referencing historical implementations, mathematical formulas like signed tetrahedron summation and Pick’s theorem, and emphasizing geometric intuition over vector calculus. Several contributions cite resources, videos, and code, note the need for closed meshes, discuss performance limits on CPUs, and suggest pre‑computing volumes. There is mild confusion over terminology but overall a positive, educational tone acknowledging the elegance and utility of the methods.
The Twelve-Factor App
The Twelve‑Factor App is a methodology for building SaaS applications that emphasizes portability, automation, and scalability across cloud environments. It originated from extensive experience deploying hundreds of apps on the Heroku platform and aims to reduce divergence between development and production, enable continuous deployment, and support growth without major architectural changes. The core principles are:
- One codebase, multiple deploys: a single repository tracked in version control serves all environments.
- Explicit dependencies: declare all libraries and isolate them from the host system.
- Configuration in the environment: store runtime settings in environment variables, not in code.
- Backing services as attached resources: treat databases, queues, caches, etc., as external resources accessed via URLs.
- Separate build and run stages: distinct processes for compiling assets and executing the app.
- Stateless processes: each process should be disposable, with state stored externally.
- Port binding: expose services by listening on a port rather than relying on external web servers.
- Process model scaling: scale horizontally by adding more identical processes.
- Fast startup and graceful shutdown: ensure robustness and rapid recovery.
- Parity between dev, staging, production: keep environments as identical as possible.
- Logs as event streams: write logs to stdout/stderr for external aggregation.
- One‑off admin tasks: run maintenance commands as transient processes.
These factors provide a shared vocabulary and actionable guidelines for developers and operations engineers building cloud‑native services.
The comments express nostalgia for earlier, simpler cloud platforms like Heroku and lament that contemporary authentication practices feel overly complex and unsustainable. There is a sense that the twelve‑factor methodology, though dated, still holds relevance, and disappointment that many developers have not fully embraced its principles. The overall tone combines regret over lost simplicity with a reaffirmation of the enduring value of the twelve‑factor approach.
Luanti removed from Google Play due to baseless AI copyright notice
Luanti’s Android app was removed from Google Play after Tracer.AI filed a DMCA takedown on behalf of Microsoft, claiming the app used copyrighted Minecraft assets. The Luanti team asserts the claim is unfounded: the platform contains only its own engine textures, fonts, and optionally the separate Minetest Game (no longer bundled), while all other content is third‑party and manually vetted on ContentDB. The same entity submitted a similar, later‑retracted notice in 2023, and a comparable takedown affected the indie game Allumeria earlier this year. Google’s reinstatement process exceeded the DMCA‑mandated 10‑14 business‑day window for counter‑notices. Luanti, an open‑source voxel game‑creation platform used in education across Europe, remains downloadable from F‑Droid and its website. The developers request that Microsoft, Mojang, and Tracer.AI ensure AI‑generated claims are human‑verified and substantiated, and that Google improve notice verification and compliance with copyright law.
The prevailing tone is strongly critical of the DMCA filing practices described, viewing the notices as unfounded, abusive, and lacking accountability. The writer highlights perceived inconsistencies in jurisdiction claims, suggests the process enables corporate censorship, and argues that the absence of penalties encourages misuse. There is a call for legal consequences, greater enforcement, and systemic reform to prevent frivolous takedowns, with an emphasis that the current system places an unfair burden on affected developers.
Pentagon's blacklisting of Anthropic was unlawful, US judge rules
Comments overwhelmingly criticize the administration’s decision to block Anthropic’s product, describing it as legally dubious, politically motivated, and an example of government overreach. Contributors argue the Pentagon’s discretion to exclude vendors raises constitutional and anti‑competitive concerns, question the legitimacy of the judicial reasoning, and warn of harmful precedents for future contractors. Skepticism about any compensation for Anthropic and calls for accountability of officials are common, while a minority note the need for national‑security safeguards but still view the move as excessive.
The comments reveal widespread frustration with the growing requirement to install native apps for functions that could work in browsers, citing privacy worries, unnecessary updates, limited feature parity, and poor user experience. Many argue that progressive‑web apps and responsive websites would reduce development overhead and avoid platform‑specific constraints, while others acknowledge that native apps can offer smoother integration and performance on mobile devices. Overall, users desire flexible access without being forced into app ecosystems, criticize corporate control over distribution, and call for better parity and usability across web and app interfaces.