waleee-cl has quit [Quit: Connection closed for inactivity]
travankor has joined #river
voroskoi has quit [Quit: Bridge terminating on SIGTERM]
ifreund_ has quit [Quit: Bridge terminating on SIGTERM]
Bonicgamer[m] has quit [Quit: Bridge terminating on SIGTERM]
samhsmith[m] has quit [Quit: Bridge terminating on SIGTERM]
travankor has quit [Remote host closed the connection]
travankor has joined #river
ifreund has joined #river
ifreund1 has joined #river
ifreund has quit [Disconnected by services]
ifreund1 is now known as ifreund
ifreund_ has joined #river
<ifreund>
travankor: RE ext-workspace I'm not a huge fan of how much more complex it would be than the current river-status protocol. Interoperability would be nice though if clients arise
<travankor>
that sounds like a reasonable position
<travankor>
So you basically be interested if there's adoption from client applications?
<travankor>
you would*
voroskoi has joined #river
samhsmith[m] has joined #river
Bonicgamer[m] has joined #river
<ifreund>
I'm somewhat skeptical that clients will implement the protocol in a way that makes sense with tags
<ifreund>
I'd love to be proven wrong though :D
<travankor>
yeah, it is kind of difficult to havea generic protocol for this
travankor has quit [Remote host closed the connection]