Australian man interrogated at LA airport and deported back to Melbourne for his writings about pro-Palestine protests. His social media posts, too, which he said he deleted before flying, were used as material.
"Clearly, they had technology in their system which linked those posts to my Esta … a long time before I took them down,” he said. “Because they knew all about the posts, and then interrogated me about the posts once I was there.”
theguardian.com/australia-news…
Australian deported from US says he was ‘targeted’ due to writing on pro-Palestine student protests
Alistair Kitchen says he was detained and questioned about views on Israel and Palestine before being deported from LA to MelbourneCatie McLeod (The Guardian)


miki
in reply to Mitchell Hashimoto • • •Mitchell Hashimoto
in reply to miki • • •@miki I’m not totally sure. Right now our behavior mostly mimics iTerm. It’s admittedly not optimized for humans right now and more for AI (I note that in the PR), but the foundational work is all the same. It’s just all the last mile to get to the next spot.
My thinking thoigh was to break down the terminal into more accessibility groups e.g per command then per N lines of output, and notify AX framework that new data exists.
miki
in reply to Mitchell Hashimoto • • •Autoreading on Mac is though (see that writeup I made on Github at one point) because Voice Over has no built-in queuing mechanism, and you really need one in a terminal. This is not a problem on any other platform, most screen readers let you decide whether you want new speech to interrupt all existing utterances or to queue up.
This means you basically need to handle speech yourself (Mac OS and all other platforms have APIs for that and they're decent), but that opens another can of worms, as then you need a way to manage speech preferences somehow.