Should we remove vosk support

[bittiez]

Since implementation I haven't heard anyone ask or comment about this, so I'm wondering if we should remove the feature?

(voice to text support for chatting)

Don't have a github account to vote?

Here's a google forms -> https://forms.gle/ixPVuwvqLayZeMEZ8

Results

Zero votes on google forms

While most people voted yes to remove it, there was enough people voting to keep it that I think we'll leave it in place for now!

[orffen]

This is an accessibility feature, so my vote would be to keep (even though I don't use it). Is there more context as to why you'd like it removed?

I can imagine someone with a disability that requires voice to text may have less likelihood of participating in Discord and GitHub discussions. Then again, someone with that kind of disability is likely to use a different voice to text program.

I guess a broader question might be about adding telemetry to the client that could tell devs whether features are being used. That would be a lot more reliable way of finding this type of thing out.

[bittiez]

Telemetry would be fantastic, but also requires a hosted server or service and Id o my best to not put my personal $$ into this project more than I already do/have, so this is the next best thing 🤷

This poll is my way to see if anyone is using or interested in it, if you have not tried it I will just say that it does work, but vosk isn't particularly good =/ I had hoped to used a bigger voice model like something from google but they don't have a free option =/

That being said, I am surprised with the results and plan to keep it after seeing the results

[orffen]

We already have tazuo.org, couldn't that just host whatever is needed for telemetry? I think we can probably be a bit clever about how this is done; it's pretty trivial to host a service that will listen for a heartbeat. All we really care about is whether a feature is enabled; should be enough for the client to do a POST (or something) against a specific script and capture a "+1".

We already have relatively unique user-ids we can use: Data/Profiles/<username>/<profilename>/<character>.

I doubt that TazUO (or even ClassicUO) is popular enough for anything more heavyweight than that - and in some of these cases we don't need a lot of data accuracy, just a general idea of how many users have specific settings enabled.

[bittiez]

Thanks for the motivation, I found a free option for in-game polls so that will be in dev soon!

[orffen]

Awesome!

[bittiez]

TazUO.org is hosted for free by GitHub, I just pay for the domain

…

On Wed, Jul 15, 2026, 7:05 AM Steve Simenic ***@***.***> wrote: We already have tazuo.org, couldn't that just host whatever is needed for telemetry? I think we can probably be a bit clever about how this is done; it's pretty trivial to host a service that will listen for a heartbeat. All we really care about is whether a feature is enabled; should be enough for the client to do a POST (or something) against a specific script and capture a "+1". We already have relatively unique user-ids we can use: Data/Profiles/<username>/<profilename>/<character>. I doubt that TazUO (or even ClassicUO) is popular enough for anything more heavyweight than that - and in some of these cases we don't need a lot of data accuracy, just a general idea of how many users have specific settings enabled. — Reply to this email directly, view it on GitHub <#692?email_source=notifications&email_token=AA5OHQMDIKW2MB5TZJZ3NF35E56SJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGQ4TEMRXUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17649227>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5OHQJKVVG2UQORZVWDQAL5E56SJAVCNFSNUABIKJSXA33TNF2G64TZHM4TGNZWG4ZDKOJRHNCGS43DOVZXG2LPNY5TCMBUGE2DINJXUF3AE> . You are receiving this because you authored the thread.Message ID: ***@***.***>