with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1

with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about these details, but it helps to understand Notebook (jupyter notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel security by using PROTOCOL_TLS which selects the highest ssl/tls protocol version avail- able that both the client and server support. When PROTOCOL_TLS is not available use PROTOCOL_SSLv23. • Add ?no_track_activity=1