Home | Notifications | New Note | Local | Federated | Search | Logout
Cassandrich@dalias@hachyderm.io
C librarian, purveyor of the language's eldritch horrors. Poppin' shells 🦪
GitHub: https://github.com/richfelker/
GitHub Sponsors: https://github.com/sponsors/richfelker/
Patreon: https://www.patreon.com/musl
Joined: 2026-07-22 12:41:14
9 notes, 0 following, 0 followers
Reply to @dalias@hachyderm.io
Cassandrich@dalias@hachyderm.io (2026-07-30 07:08:02)
Like, even if the arguments for why it's less harmful than people think it is were true... LET US HAVE THIS.
Let activists fighting AI have the narrative that Anthropic is burning the Library of Alexandria.
You don't need to step in and WELL ACKSHUALLY... that shit.
Cassandrich@dalias@hachyderm.io (2026-07-30 07:06:39)
I see someone I once respected who's been very AI-pilled is now dedicated to defending Anthropic's book-burning... 🙄 😢
Reply to @seuros@mastodon.bsd.cafe
Cassandrich@dalias@hachyderm.io (2026-07-23 23:07:55)
@seuros Right, but in those other cases, the device in question was a fixed installation inside the computer's enclosure that you had chosen to trust, not an external device. I've always deemed bus-mastering DMA a design flaw in all of those other things too, though IOMMU mostly fixed it on hardware new enough to have an IOMMU that's an actual security boundary and not just advisory like some early ones were.
None of this detracts from what you're doing, and I'm glad you'll be wiring up the IOMMU stuff.
Reply to @seuros@mastodon.bsd.cafe
Cassandrich@dalias@hachyderm.io (2026-07-23 22:44:39)
@seuros My impression of FireWire was always that it was inherently insecure and gave the device a backdoor to the host. Was this inaccurate or later fixed or is it just something you have to accept using that ecosystem?
Reply to @Ember@blobfox.coffee
Cassandrich@dalias@hachyderm.io (2026-07-22 22:10:47)
@Ember @joepie91 Yes absolutely. For certain accessibility needs, working "muscle memory" is critical. Forcing people to abandon and relearn that is an assult on accessibility.
Reply to @joepie91@fedi.slightly.tech
Cassandrich@dalias@hachyderm.io (2026-07-22 21:44:33)
@joepie91 @lanodan Exactly. Ability to hook up UI to a screenreader and have it work well is only a tiny part of UI accessibility. It's important to the people who need it, but there are other aspects that matter just as much to people with other needs.
Limited vision, limited ability to maintain eye tracking, limited motor precision, inability to use some or most kinds of input devices, ...
Reply to @rysiek@mstdn.social
Cassandrich@dalias@hachyderm.io (2026-07-22 09:55:59)
@rysiek Is the 432 claim actually legitimate or is it slop vendor propaganda? What portion of them are a single issue split down into the smallest pieces possible to inflate the number of CVEs, hype up the "tools" behind them, waste responder time, and make defenders feel hopeless? What portion are even legitimate severity levels?
Reply to @lanodan@queer.hacktivis.me
Cassandrich@dalias@hachyderm.io (2025-07-01 01:20:48)
@lanodan I wish GTK wouldn't keep making UI/accessibility regressions. The shit they've done with scrollbars is unusable.
Cassandrich@dalias@hachyderm.io (2025-07-01 01:18:09)
TIL in Firefox about:config:
widget.gtk.overlay-scrollbars.enabled = false
widget.non-native-theme.gtk.scrollbar.thumb-size = 1
widget.non-native-theme.scrollbar.style = 4
widget.non-native-theme.scrollbar.size.override = 16
Gets you scrollbars that are actually visible and clickable with the mouse.