You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to see a way to pair ZNC with Palaver thru some kind of QR code format (perhaps displayed on a ZNC admin page?), as the form-filling can be tedious and error-prone. I'd be happy to contribute something like this, but was wondering if this feature would belong in this codebase or in a separate one. Of course it would require client-side support, but I hope that cocodelabs would think the UX benefit be worth while! ☺️
The text was updated successfully, but these errors were encountered:
Hey @dongcarl, thanks for your enthusiasm! :) We are already working on features to make the ZNC setup process easier. This feature should land within the next couple of releases. QR pairing for ZNC might be a nice addition to that, but that is not quite specific to Palaver. Perhaps you could start with ZNC and see if you can convince/help them to add some sort of pairing QR code in the web admin. As soon as such feature is available we would be happy to integrate support for that into Palaver.
This is somewhat possible already, you can craft a URL such as ircs://:username%2Fnetwork%[email protected] (note username%2Fnetwork%3Apassword is URL encoded username/network:password since some characters must be escaped).
You can scan the picture and it will open in Palaver:
The one caveat, is that we de-duplicate URIs based on other information so right now the current released version of Palaver will only allow you to add a single network this way. We'll make a future update of Palaver to address that.
Uh oh!
There was an error while loading. Please reload this page.
I'd like to see a way to pair ZNC with Palaver thru some kind of QR code format (perhaps displayed on a ZNC admin page?), as the form-filling can be tedious and error-prone. I'd be happy to contribute something like this, but was wondering if this feature would belong in this codebase or in a separate one. Of course it would require client-side support, but I hope that cocodelabs would think the UX benefit be worth while!☺️
The text was updated successfully, but these errors were encountered: