# RFC: Outgoing websocket connections

**URL:** <https://forum.electromage.com/t/rfc-outgoing-websocket-connections/4066>\
**Category:** Feature Ideas + Requests\
**Created:** [April 4, 2025, 5:36pm UTC](https://forum.electromage.com/t/rfc-outgoing-websocket-connections/4066 "2025-04-04T17:36:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sorceror](https://forum.electromage.com/user_avatar/forum.electromage.com/sorceror/32/735_2.png) [@sorceror](https://forum.electromage.com/u/sorceror)\
**Post date:** [April 5, 2025, 4:59pm UTC](https://forum.electromage.com/t/rfc-outgoing-websocket-connections/4066/3 "2025-04-05T16:59:56Z")

</div>

Sounds ok, but doesn’t really interest me.

I don’t want to need anything other than a bunch of pixelblazes with a lazy asynchronous shared variable space as imagined in [Pixelblaze for Burning Man 2025 ? Sync/Wifi + New product roadmap? - #8 by sorceror](https://forum.electromage.com/t/pixelblaze-for-burning-man-2025-sync-wifi-new-product-roadmap/3997/8)

---

_[View the full topic](https://forum.electromage.com/t/rfc-outgoing-websocket-connections/4066)._
