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 was wondering, if oMLX does support https inherently for its web server?
llama.cpp does provide that and would be important for STT when transcribing in real time.
Microphone input is these days only allowed in browser either by http to localhost or by utilizing https.
Ofc, alternative is to use caddy or the like.
However, a built in, super simple https setup would probably help a lot of people.
From my point of view, only self signed CA certificate would be necessary, where a CA should be created with a fqdn freely to choose from. That CA should be provided as crt export, so I one can import that to CA cert store of your browser.
All left by the user would be to feed local hosts file or even a DNS zone file, if you happen to have one at hand.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I was wondering, if oMLX does support https inherently for its web server?
llama.cpp does provide that and would be important for STT when transcribing in real time.
Microphone input is these days only allowed in browser either by http to localhost or by utilizing https.
Ofc, alternative is to use caddy or the like.
However, a built in, super simple https setup would probably help a lot of people.
From my point of view, only self signed CA certificate would be necessary, where a CA should be created with a fqdn freely to choose from. That CA should be provided as crt export, so I one can import that to CA cert store of your browser.
All left by the user would be to feed local hosts file or even a DNS zone file, if you happen to have one at hand.
All reactions