The 1988 shooting down of Flight 655 as a user interface disaster
1–10 of 695 posts
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#2[flagged]
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#3I'm so conflicted reading this story. On one hand, yes, there were choices made during the design of the system that directly contributed to this tragedy. And a lot of innocent lives were lost, so saying that's "shit happens, it's an edge case" rings very hollow.
On the other hand, this was a very peculiar set of circumstances, very much an edge case. Is it reasonable to expect designers of combat systems to triple check their choices and run more test scenarios to identify and address such edge cases? I'd say yes. However, I think it's unreasonable to expect them to design a perfect system for a highly volatile and chaotic use case such as war.
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#4[flagged]
It's also quite annoying how the piece is split up into small chunks, due to tweets or toots or whatever they're called being limited in size.
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#5[flagged]
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#6[flagged]
It's also quite annoying how the piece is split up into small chunks, due to tweets or toots or whatever they're called being limited in size.
I agree. I've always hated the twitter-style threads people write. I can't stand it. There are websites that compile a thread into a better reading blog style format however.
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#7I'm so conflicted reading this story. On one hand, yes, there were choices made during the design of the system that directly contributed to this tragedy. And a lot of innocent lives were lost, so saying that's "shit happens, it's an edge case" rings very hollow. On the other hand, this was a very peculiar set of circumstances, very much an edge case. Is it reasonable to expect designers of combat systems to triple c…
Sorry, I don't see where's the edge case. In a given area there are going to be lots of planes. If there is risk of confusing them and making decisions based on non-reconciled information, it seems a pretty critical flaw.
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#8[flagged]
> Mastodon is apparently at least as bad as Meta.
Wow. Such a comparison is mindblowing.
You are apparently unaware that the default Mastodon web client is only one way of many which you can use to interface with a Mastodon instance. If you feel that there should be a plain HTTP(S) interface to its open API, feel free to advocate for one — or to create it yourself!
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#9[flagged]
It's also quite annoying how the piece is split up into small chunks, due to tweets or toots or whatever they're called being limited in size.
Mastodon is a microblogging service, so not meant for large bodies of text. This is why the text entry box is small, the columns are somewhat narrow (especially in deck mode) etc.
Platforms like https://writefreely.org/ , which are designed to be for blogging and long-form writing, are the place to write this. Write Freely federates so one can follow accounts and interact with posts via Mastodon etc.
Re: The 1988 shooting down of Flight 655 as a user interface disaster
#10Earlier quoted context omitted.
It's also quite annoying how the piece is split up into small chunks, due to tweets or toots or whatever they're called being limited in size.
I agree. I've always hated the twitter-style threads people write. I can't stand it. There are websites that compile a thread into a better reading blog style format however.
That's a good point, at least Twitter has third-party tools like Thread Reader to mitigate this annoyance. I wonder if there is an equivalent for Mastodon?