I also have some ideas  for a new display server. The main diff is moving away from pixels and away from windows. A visual-haptic-audio representation of a process's output should be 'porous'

I'll call it GipesCompProcessPorousCovers (GsCPPC). . Cover since its the superficial aspect of a process. GsCPPC could easily adapt it's data ui representations for accesibility. . GsCPPP will have pixel's as a visual representation choice but not as priority. Can a pixel transform easily into accessibilty compatible types? Dont think so.

As for security i will rephrase it into different semantics of isolation of something happening .Like dont wont to be distrurbed but lets not keep sharing out. An importand core semantics swift.

So if you want to become more adventurous and have time to kill please take a look on my thoughts and let's see how a display server could evolve towards some novel ideas.

->How X started.

->Copy paste... a hard problem ?

-> Should a display server contain a drawing API ?

->What is X ?   // As you'll read X is what 'you' want it to be. The needs change. For 80s MIT's Athena project X meant distributed computing and collaboration . Today for gaming industry X or Wayland means impressive addictive graphics to make money. (not necessarily interesting games) .   (like Angèle is implying in her song What You Want -- X is what YOU want... :-)  )

->To X or not to X ?

-> The need for cooperation as central motivation in Unix and GNUproject