glowing-bear

This works just fine too in Glowing Bear on my phone (Firefox on Android 10). https://github.com/glowing-bear/glowing-bear

I use glowingbear (https://glowing-bear.org/, https://github.com/glowing-bear/glowing-bear) to connect to a weechat session running on a VPS. The setup is not non-tech-person approachable, but its generally been untouched aside from updates in this setup since 2013. For non-tech people https://www.irccloud.com/ seems one of the best on offer.

Let me add Glowing Bear, a project I contribute to that builds on top of WeeChat: https://github.com/glowing-bear/glowing-bear

I sort of have the reverse problem. I would like to use a websocket to connect to an insecure host on the local network from a secure context. I realise that this is incredibly niche and would probably need independent confirmation through the browser to prevent abuse. But it's needed to connect to a local weechat instance from Glowing Bear, which is essentially a web UI for WeeChat, an IRC client: https://github.com/glowing-bear/glowing-bear. Right now we have an https and a non-https-version of the website, which is arguably even worse.

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 goo

I use WeeChat (https://weechat.org/, running on my server) and Glowing Bear (https://github.com/glowing-bear/glowing-bear) to connect to it from wherever I am (desktop or mobile), it works very nicely. Because it's self-hosted, it has higher setup overhead than signing up to slack, of course. But it does solve IRC's mobile and multi-device problems for me wonderfully. (I'm one of the Glowing Bear developers)

Examples for what? There are some screenshots of Glowing Bear on the GitHub page (https://github.com/glowing-bear/glowing-bear) and in a blog post I once wrote (https://4z2.de/2014/04/10/glowing-bear, probably outdated). I use it with a sans-serif font on the Desktop, too. The UI is quite hackable, you can add custom CSS rules to override things to your liking in the settings (simply changing the font doesn't require that, though). Some useful scripts include colorize_nicks.py (colourises nicks in messages, to make them stand out over the text) and grep.py (easily and efficiently search logs). Matrix.lua (https://github.com/torhve/weechat-matrix-protocol-script) allows you to use the Matrix protocol with WeeChat, and by extension Glowing Bear. Trigger-wise, I have triggers that remove colour from status messages (most of them are just noi

I agree with the author on many points, but he's wrong about mobile support. WeeChat has a relay plugin (built-in) that allows mobile clients to connect to your existing WeeChat session. There are even some options to choose from: WeeChat-Android has recently gotten some love again (I hear it works nicely), and Glowing Bear works on every device that has a modern browser and has a nice responsive UI, along with some neat features like embeds and direct imgur upload. Both connect to your WeeChat instance directly, so there's no cloud provider you have to trust, as the relay works as a socket and websocket. This allows Glowing Bear to work in the browser (Disclosure: I'm one of the devs) https://github.com/glowing-bear/glowing-bear https://github.com/ubergeek42/weechat-android Oh and the point about long URLs being unclickable has been addr

I can only offer one data point, but I've managed to crash Chrome for iOS a lot (good example: it doesn't seem to like websockets much, see https://github.com/glowing-bear/glowing-bear/issues/597). I don't recall ever crashing Chrome for Android even though it's the default browser on my phone.

If you're already running weechat, you might be interested in checking out Glowing Bear which accomplishes a very similar goal, but without reinventing the weel - it simply connects to you existing weechat (probably running on a server somewhere). https://github.com/glowing-bear/glowing-bear https://latest.glowing-bear.org One of the biggest advantages of this approach is that you get the whole functionality of a mature IRC client. You also don't have to trust a third party with your data, as you're connecting to your own client, no middleman involved. It's just a bunch of static files.

If what you really want is a pretty web-based way to access IRC, then you might want to check out Glowing Bear -- it connects to your WeeChat IRC client via websockets and works nicely on the Desktop and on mobile. It doesn't have a voice recorder, but it gives you the infinite possibilities of a mature IRC client. It's a project I've been contributing to for a while now and I still absolutely love using it. https://github.com/glowing-bear/glowing-bear https://latest.glowing-bear.org/

There already are a number of IRC client web frontends. The one I'm working on is Glowing Bear -- https://github.com/glowing-bear/glowing-bear . It uses a proper IRC client running on a server (WeeChat in a terminal multiplexer) and connects to that via WebSockets. Minimal reinvention of the wheel, and you can continue using all those nice scripts, triggers, and filters that WeeChat offers. The frontend (Glowing Bear) is completely static and runs 100% in your browser, connecting to your server directly. I really don't get those projects that consist of a designer frontend and a terrible half-baked IRC client in nodejs.

If it could be ingrated with [WeeChat] [1], it could be a way to provide iMessage support as a [web browser chat client] [2] and to [Android devices] [3]. [1]: https://weechat.org/ [2]: https://github.com/glowing-bear/glowing-bear [3]: https://github.com/ubergeek42/weechat-android