Accessibility, a year in review: Microsoft 365 Copilot support and better user experiences
Hi, Insiders! I’m Clint Covington, Group Product Manager for E+D Accessibility. To celebrate Global Accessibility Awareness Day, I’d love to share some of the biggest updates and features we’ve launched in the past year to make Microsoft 365 apps and…Clint Covington (TECHCOMMUNITY.MICROSOFT.COM)


daniel:// stenberg://
in reply to daniel:// stenberg:// • • •Impossible to use `curl` to resolve `.onion` addresses using Tor Project's `oniux` tool · Issue #17363 · curl/curl
GitHubdaniel:// stenberg://
in reply to daniel:// stenberg:// • • •Wolf480pl
in reply to daniel:// stenberg:// • • •looking at the torproject discussion about this gitlab.torproject.org/tpo/core…
and it seems like an irresolvable problem.
On one hand you have people setting up LANs that have all their outbound traffic sent through Tor, and are supposed to work with any tor-unaware device.
On the other hand, saying "the LAN you're in is behind Tor" is exactly what an attacker would say to induce user devices to leak onion lookups...
Formalize toggle override for non-Tor applications that follow RFC 7686 (#202) · Issues · The Tor Project / Core / Tor Specifications · GitLab
GitLabdaniel:// stenberg://
in reply to Wolf480pl • • •Grant Joseph
in reply to daniel:// stenberg:// • • •Petr Menšík
in reply to daniel:// stenberg:// • • •Petr Menšík
in reply to daniel:// stenberg:// • • •it seems to me this RFC cannot work with network or system level .onion support and should be replaced.
I think applications need API to query system resolver, whether DNS is handled by localhost or trusted resolver. And if .onion names are considered a special handled domain. I think we lack both on Linux now.
This RFC assumes only per-application support can be safe. Applications should query the OS support and enable it if indicated. But resolver related apis are ancient already.