ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
kasper93_ has joined #wayland
mclasen has quit [Remote host closed the connection]
eruditehermit has quit [Ping timeout: 480 seconds]
eruditehermit has joined #wayland
Dami_Lu has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
eruditehermit has quit [Ping timeout: 480 seconds]
Consolatis_ has joined #wayland
Consolatis_ is now known as Consolatis
mxz_ has joined #wayland
eruditehermit has joined #wayland
rv1sr has joined #wayland
eruditehermit has quit [Ping timeout: 480 seconds]
kts has joined #wayland
eruditehermit has joined #wayland
Hypfer has joined #wayland
kts has quit [Quit: Leaving]
DodoGTA has joined #wayland
abhimanyu has joined #wayland
sima has joined #wayland
coldfeet has joined #wayland
coldfeet has quit []
kts has joined #wayland
kts has quit []
kts has joined #wayland
Consolatis_ has joined #wayland
Consolatis is now known as Guest4869
Consolatis_ is now known as Consolatis
Guest4869 has quit [Ping timeout: 480 seconds]
rv1sr has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
mechanical_jellyfish has joined #wayland
ShapeShifter499 has quit [Quit: Leaving]
<mechanical_jellyfish>
what does /run/user/1000/wayland-0 do?
<mechanical_jellyfish>
when i share it between a container and the host, the container can access the host's wayland server
<vyivel>
mechanical_jellyfish: that's the wayland socket
<mechanical_jellyfish>
is all communication between wayland clients and the wayland server done with that socket
<vyivel>
yes
kts has quit [Quit: Leaving]
<mechanical_jellyfish>
is the data going through that socket defined to the byte by the wayland spec? or does the spec talk about things on a more abstract level and leave some communication details implementation-dependent