"People who are really serious about software should make their own hardware. Because software fucking sucks. I hate software and I hate people who make it." - Alan Kay
@usernameswift@ShadowJonathan@skye 💡 aridoodle fact: i've actually written a very simple shell before while working on my own OS kernel. i called it ash! literally short for "ari shell"
@arimelody.space@Fubu it looked cool!! admittedly, i got a little overenthusiastic by assuming a lot of things about the software (it's an android emulation frontend- i had assumed it was for desktop, and thus would support launching PC games, too)
i feel worse for the mobile retro game emulation community who would have benefit from such a project, though i've also heard from some that many of iiSU's key offerings are available in other frontends. the social features and visual sauce were the main differentiators.
@guilevi as someone who's been sharpening my skills to write good image descriptions for a long while now, i'd love to know what kinds of descriptions are most accessible to you!
my goal lately has been a balance of contextual awareness and concise wording. for example, i might simply write "spongebob pointing at TV" to quickly nod to the scene of him spotting himself in a small role in an ad; generally used when i spot myself on something interesting and external to me. my hope is this works for things like memes, where the audience is likely to have context awareness to pick up what i'm communicating.
for more niche memes, or a more detailed screenshot of something, i may skip over details that aren't particularly relevant to the subject. for example, i generally neglect timestamps from message screenshots unless the timing is specifically relevant to the discussion.
the idea is that my descriptions should allow screen reader users to participate in the conversation, while not bombarding them every laboured detail of the image, when all anyone needs to know is a few key things.
@vozercozer i love how they're like "omg airdrop is coming to android!!" and not "specifically google pixels. given google's recent track record, it seems unlikely this will ever hit AOSP"