We have the same issue with Glowing Bear ( https://github.com/glowing-bear/glowing-bear ).
We have the same issue with Glowing Bear ( https://github.com/glowing-bear/glowing-bear ). It's a web frontend for an IRC client (WeeChat) that connects directly to WeeChat via WebSockets. Sort of like self-hosted irccloud without a cloud. We really want everyone to use encrypted connections [0] and push people onto the TLS version of Glowing Bear. But some people host their WeeChat on their local network, and you can't (realistically) get a certificate for a local IP. So for those people we need to open an unencrypted websocket (ws://1.2.3.4), which isn't possible from an https site. Ideally we'd like to disallow unencrypted connections to non-local destinations but that's practically impossible to determine in JS. It's a super annoying problem. Disallowing unsafe websockets from secure origins is one of those policies that is a really good idea 99.5% of the time but for those last 0.5% of use cases, it's a major pain in the bum. [0] WeeChat has a /exec command to execute arbitrary commands, and the client has access to that --- not great when you transmit your password in plain text.
Posted by lorenzhs on Jul 12, 2017, 3:03 PM
Tags
Related issues
- (1) Because it doesn't actually solve the problem.
- Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
- My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
- Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
- There aren't many situations today that make one think: Why doesn't this business have a website?
- > IAM can stay MS That's leaving the most critical component still with a US company.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
hackernews (Network)
(1) Because it doesn't actually solve the problem.
Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
There aren't many situations today that make one think: Why doesn't this business have a website?
> IAM can stay MS That's leaving the most critical component still with a US company.
I am very petty about this one bug and have a very old axe to grind that this reminded me of!
Not just the edge router.
We have the same issue with Glowing Bear ( https://github.com/glowing-bear/glowing-bear ).
We have the same issue with Glowing Bear ( https://github.com/glowing-bear/glowing-bear ). It's a web frontend for an IRC client (WeeChat) that connects directly to WeeChat via WebSockets. Sort of like self-hosted irccloud without a cloud. We really want everyone to use encrypted connections [0] and push people onto the TLS version of Glowing Bear. But some people host their WeeChat on their local network, and you can't (realistically) get a certificate for a local IP. So for those people we need to open an unencrypted websocket (ws://1.2.3.4), which isn't possible from an https site. Ideally we'd like to disallow unencrypted connections to non-local destinations but that's practically impossible to determine in JS. It's a super annoying problem. Disallowing unsafe websockets from secure origins is one of those policies that is a really good idea 99.5% of the time but for those last 0.5% of use cases, it's a major pain in the bum. [0] WeeChat has a /exec command to execute arbitrary commands, and the client has access to that --- not great when you transmit your password in plain text.
Comments (0)
No comments yet. Start the discussion.