Tootfinder

If none of this makes sense to you, don’t worry.
There is absolutely no need to understand any of this to enjoy using Mastodon
https://blog.joinmastodon.org/2026/08/mastodon-4.7/

Mastodon 4.7
This release is full of technical improvements focusing on bug fixes, performance and interoperability with other fediverse platforms.

Don't get stuck high and dry with a noncompliant swamp. To ensure proper interoperability, always ask your suppliers if they ensure compliance with ISO 414141 "Standard for Swamps, Wetlands, Marshes, and Bogs".
Better known simply as "the bog standard"

The EU issues two decisions under the DMA, requiring Google to provide rival AI assistants and search engines comparable access to Android and some Search data (Robert Hart/The Verge)
https://www.theverge.com/policy/966438/eu-google-android-ai-int…

Google ordered to open Android and Search to rivals in Europe
The EU says Google must let rival search engines and AI assistants have comparable access to Android and some Search data to comply with the DMA.

A big win for #Android interoperability
https://www.openhomefoundation.org/blog/a-big-win-for-android-interoperability/

There's a Wittgenstein's Tractatus-like confidence in that title: "Fully solving JSON Schema and JSON-LD interoperability"
https://www.sourcemeta.com/blog/json-schema-jsonld-interoperability/
"intermixing JSON Schema and JSON-LD g…

Summary of the measures relating to EVs in the EU's Electrification Action Plan (and related initiatives), alongside the general adjustments to network tariffs, connection conditions and taxation
https://energy.ec.europa.eu/publications/co…

"This ruling confirms what we have argued from the start: interoperability is not optional under the DMA, it is the law. Developers finally have legal certainty to build competitive alternatives to Apple's ecosystem, and we remain committed to monitoring enforcement of today’s decision, says Lucas Lasota, FSFE's Senior Programme Manager Legal"
@…

from my link log —
Rust and C interoperability.
https://slint-ui.com/blog/rust-and-cpp.html
saved 2022-11-14 https://dotat.at/:/2E…

from my link log —
Fuzzing Sequoia-PGP.
https://blog.hackeriet.no/fuzzing-sequoia/
saved 2020-06-03 https://dotat.at/:/PJ56H.html

SunLink was the product family for all the non-TCP/IP/Ethernet protocols. This was hugely important to get in to accounts who had not yet realized where things were heading.
The 80s was the wild west of protocols. The survivors were open and had communities dedicated to interoperability.
2/6

A Java Geek weekly 148
https://blog.frankel.ch/java-geek-weekly/148/
The Difference Between a Button and a Link. Histogram vs eCDF. ponytail. How much can you delegate to agents? The Economic Benefit of Refactoring. W. Remotely access Home Assistant via Tailscale for free. Ope…

Classical Acceptance Is Not Hybrid Authentication: Measuring X.509 Verifier Semantics in Post-Quantum Migration
Taesung Kim, Boheung Chung, Keonwoo Kim, Yousung Kang
https://arxiv.org/abs/2607.20800 https://arxiv.org/pdf/2607.20800 https://arxiv.org/html/2607.20800
arXiv:2607.20800v1 Announce Type: new
Abstract: A relying party validating a hybrid X.509 certificate --- carrying both a classical and a post-quantum credential --- must distinguish whether its accepting judgment rests on the post-quantum evidence or only on the classical path. To preserve compatibility, the separable designs place that evidence where classical path validation may ignore it. A verifier can then validate the classical path and accept while the post-quantum evidence never bears on the decision --- a valid classical result silently promoted to a hybrid conclusion it did not establish. We measure this across eight path-validation stacks (seven independent codebases), in nine validation modes, over six certificate schemes. Under a hybrid-required policy, nearly every stack parsing a separable hybrid certificate accepts on the classical path without making the post-quantum evidence outcome-bearing; one enforcing mode instead fractures interoperability over a signature-input encoding not yet interoperably profiled; and stacks that verify post-quantum signatures still do not enforce the binding by default: the gap is structural, not explained by missing primitive capability alone. Under lifecycle desynchronization the downgrade is realized: when a bound post-quantum credential is revoked while the classical certificate stays valid, the default path still accepts, because the bound credential lies outside the decision's scope. Binding success is not authentication success. We contribute a specification-derived verifier model and an executable, policy-parametric reference contract --- what a verifier must recognize, verify, make outcome-bearing, and check before reporting a validation as hybrid --- with a diagnosis of why standards do not require it.
toXiv_bot_toot