Dirty programming idea of the moment: websocket is actually a socket on an always open port (http/s) that mean I can now write distributed services without having to bother about allowing another port and just needed something exposed to http(s) somewhere :3

It's nonsense to use thousands of ports, just use one for everything, it makes everything easier and more clear :troll:

@8bits or as meredith told us

But yeah, in practice it makes everything so easier to configure and it sucks.

Sign in to participate in the conversation

This is an open mastodon instance for social justice activists, LGBTQIA+ people, and people who are aware of such subjects and care about them.

See the Goals, rules, and technical details for more information