Today’s Q&A focuses on the ThinStation project, which is “a basic and small, yet very powerful, Open Source thin client operating system supporting all major connectivity protocols.”
ThinLinc is one of the connectivity protocols that can be used with ThinStation. This project is maintained by @doncuppjr , who kindly agreed to participate in this Q&A as a way to share information about ThinStation.
This thread will remain open for those who wish to ask questions directly, so if you have one, please post it below. To get the ball rolling, however, I’d like to start with a few of my colleague @aaron :
Please give us a short bio - what is your background, and how long
have you been involved in the ThinStation project?
Who is the typical ThinStation user? Why do they choose ThinStation?
What are some common examples of hardware that people are running
I notice that one of our forum members Jens Maus (@j.maus ) has a
ThinStation fork on GitHub with modifications to support several
different generations of Intel NUC at their organization, HZDR. Is
this something which might be interesting to the upstream project?
 GitHub - hzdr/thinstation: A fork of the well-known linux-based thin client environment ‘Thinstation’ especially optimized for the various thin clients used at our institution (mainly “intel NUC”) and modified to act as a lightweight remote connection kiosk system to connect to ThinLinc, Windows (RDP) and VNC server systems…
What are the biggest challenges facing the ThinStation project right
What is the future direction for the ThinStation project? Which
bugs/features would you most like to see implemented?
How can people contribute to the ThinStation project?
For more information on theThinStation Project, visit https://thinstation.github.io/thinstation/
For code, support, and feature requests, visit https://github.com/ThinStation/thinstation
Don can be reached via his own website, visit http://www.doncuppjr.net