@esoteric_programmer How long it's been worked on? since early 2000s. How long it's been in public view? closer to ten years. It's not marketed as much as it is leaving behind a trail of crumbs.

See the index of articles: fossil.arcan-fe.com/ for how deep this hole goes.

Is it a custom interface on top if the linux kernel? Well anything above kernel level is fair game, though it also works on BSD kernels and, at least last I tested, OSX. It is about as 'different' architecturally as Android is - other IPC system, network protocol, Low level APIs, Mod-level APIs, several WMs..

The beeps are not continuous, they were mapped to the mouse cursor but binned to a timer instead of event driven as well, that triggered my tinnitus something fierce with a 1KHz mouse.

The meta modifier and a11y bindings being forced to be pressed repeatedly was to a. avoid accidental presses, b. cover for running nested (VM, inside another windowing system, ...) where a long press could get cancelled from keyrepeats not being correctly disabled or from hardware keys with contact bounce problems.

GTK applications would run through the arcan-wayland protocol bridge, or the Xarcan one (used in the clip with chromium) but those are so far just pixel soup so feedback comes from OCR and other sight to sound mapping.

I'm not sure if you can use rust, but if so, for now you can just make an at-spi viewer or however you called it there, the same way you'd do one for access kit, if nothing else, because access kit isn't implemented widely enough yet, and access kit translates to at-spi anyway. Here's the atspi crate we use as part of odilia, the same one access kit depends on. I dk how old the crates.io version is, so I'll give you the thing straight from the source

github.com/odilia-app/atspi

GitHub - odilia-app/atspi: A fast, zbus-based, permissively licensed AT-SPI library written in pure Rust!

A fast, zbus-based, permissively licensed AT-SPI library written in pure Rust! - odilia-app/atspi

^GitHub

@esoteric_programmer @matt not necessarily, that comes from the AT-SPI compatibility and Unix platform. I'd substitute in another platform for arcan-shmif and avoid that.

This was my first attempt at an aural only demo, and still no idea how to convey the haptic parts -- like moving the mouse around, combined with the wrist mounted piezo I use to feel when the cursor crosses horizontal/vertical edges.

I'm sighted (though this work has been blindfolded), so the audio profile used is what I learned to use with some notes from watching @zersiax 's twitch streams, yet as you hear, different enough from what others might be used to. That's also why I opted to not show any of the HRTF/positional audio or seeing-with-sound bits.

ahh, interesting, so you want to make your own platform for which accesskit builds an adaptor? I wonder, would that help the current situation with chromium and similar? whoe, you have that much support for esoteric devices like those? linux doesn't have them even now, not as advanced as your thing, awesome! Also, I know the name sounded familiar from somewhere, now I found it, this popped up in my articles list when I was researching something about wayland. Reading some of your building clients with arcan articles, especially the part where you apparently have to clone arcan and build your apps into its source tree somewhere to make them found by the thing, I came to the conclusion that you're using wayland in some very, very weird ways, dk if that's awesome or not. Anyway, this is the article I read back then, but as I had no context, I dismissed it because it sounded weird

arcan-fe.com/2017/12/24/crash-…

Crash-Resilient Wayland Compositing

A commonly held misbelief about one of the possibly negative consequences with migrating from X11 to Wayland is that the system as a whole will become more brittle due to the merger of the display …

^Arcan

@esoteric_programmer What exactly do you mean by "the current situation with Chromium and similar"?

@letoram