Is there any keyboard which lets you configure the service used for voice input?
I'd like to set an URL to a selfhosted service to send my voice to be processed which then will return the transcription.

If no keyboard exists for this any app would do.
The idea is the app lets you stream the audio to the given service and will receive the response and show it for you to edit, similar on how google keyboard has the voice input.

Bonus points if it's open source :P

I'm not sure in which community to ask this, if you know of a better one let me know.

I already have squid proxy working, if I set up my browser or curl to use the proxy all sites work properly.
But when I try to make a request with axios it doesn't work.

Here are the logs of squid
The first two lines are successful google connections are from a browser.
The 3rd line is a successful to google using curl.
The 4th line is a successful to ipify using curl.
The last two ones are the ones from node using axios

squid_proxy  | 1693406310.165  12043 127.0.0.1 TCP_TUNNEL/200 56694 CONNECT www.google.com:443 - HIER_DIRECT/142.250.217.132 -
squid_proxy  | 1693406310.166  10681 127.0.0.1 TCP_TUNNEL/200 47267 CONNECT apis.google.com:443 - HIER_DIRECT/142.250.176.14 -
squid_proxy  | 1693406325.551    497 127.0.0.1 TCP_TUNNEL/200 24778 CONNECT www.google.com:443 - HIER_DIRECT/142.250.217.132 -
squid_proxy  | 1693406336.829    403 127.0.0.1 TCP_TUNNEL/200 7082 CONNECT api.ipify.org:443 - HIER_DIRECT/64.185.227.156 -
squid_proxy  | 1693406361.410  12590 127.0.0.1 TCP_MISS/503 4358 GET https://api.ipify.org/? - HIER_NONE/- text/html
squid_proxy  | 1693406361.889    385 127.0.0.1 TCP_MISS/502 3948 GET https://www.google.com/ - HIER_DIRECT/142.250.217.132 text/html

The errors sent to axios are these:

# ipify
[No Error] (TLS code: SQUID_TLS_ERR_CONNECT+GNUTLS_E_FATAL_ALERT_RECEIVED)
SSL handshake error (SQUID_TLS_ERR_CONNECT)  
This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.  

# google
The system returned: [No Error]

My code looks like this

const axios = new Axios({
	proxy: {
		host: proxyIP,
		port: proxyPort,
		protocol: 'http'
	}
});

const ip = await axios.get('https://api.ipify.org?format=json');
console.log(ip.data);


const res = await axios.get('https://www.google.com');
console.log(res.data);

Any idea what might be happening?

I'm not sure if axios handles the connection in a different way since the logs from the browser show CONNECT and axios shows GET, but maybe that's because it's failing to actually connect and it only logs the request method.

I have an implementation for an internal API, the requirement is to implement some sort of basic authentication instead of oauth (generating a token).

Do you think there's any difference between using just an API key vs using a client id + secret?
For what I see it'd be just like saying "using a password" vs "using a user and a password".

I just reinstalled windows in a new SSD and forgot to export in some way the settings for my logitech devices.
The old SSD is still around but it's cumbersome to run windows from there just to copy the settings, so I mounted with and adapter and to read the settings files.

The LGHUB storage is an sqlite DB located in C:\Users\<user>\AppData\Local\LGHUB\settings.db
And you can just query select * from data which contains the settings as a json.

It'd be better to send it to a file sqlite3 settings.db 'select file from data' > data.json (mine was 7.5MB of data)

I've been creating separate accounts for some of my selfhosted services, some are to further sub-divide the data, but for sure I always have an admin account and the account I use day to day.

What's your account creation schema?
What do you think about creating multiple accounts for your selfhosted services?

The bug allows attackers to swipe data from a CPU’s registers. […] the exploit doesn’t require physical hardware access and can be triggered by loading JavaScript on a malicious website.

The bug allows attackers to swipe data from a CPU's registers. [...] the exploit doesn't require physical hardware access and can be triggered by loading JavaScript on a malicious website.

I'm trying to install munin in my ubuntu VPS
I used apt install munin-node munin to install it.

But I can't make the web interface work.
Since I already have pihole there I'm using lighttpd with this config (for the most part the default from the documentation)

server.modules += ( "mod_alias" )
server.modules += ( "mod_fastcgi" )
server.modules += ( "mod_rewrite" )

$SERVER["socket"] == ":8467" {

alias.url += ( "/munin-static" => "/etc/munin/static" )
alias.url += ( "/munin"        => "/var/cache/munin/www/" )
server.document-root = "/var/cache/munin/www/"

fastcgi.server += ("/munin-cgi/munin-cgi-graph" =>
                   (( "socket"      => "/var/run/lighttpd/munin-cgi-graph.sock",
                      "bin-path"    => "/usr/lib/munin/cgi/munin-cgi-graph",
                      "check-local" => "disable",
                   )),
                  "/munin-cgi/munin-cgi-html" =>
                   (( "socket"      => "/var/run/lighttpd/munin-cgi-html.sock",
                      "bin-path"    => "/usr/lib/munin/cgi/munin-cgi-html",
                      "check-local" => "disable",
                   ))
                 )

url.rewrite-repeat-if-not-file += (
                   "/munin/(.*)" => "/munin-cgi/munin-cgi-html/$1",
                   "/munin-cgi/munin-cgi-html$" => "/munin-cgi/munin-cgi-html/",
                   )
}

When the service is restarted it the log shows this error even when the files have 777 permissions

(gw_backend.c.1404) invalid "bin-path" => "/usr/lib/munin/cgi/munin-cgi-graph" (check that file exists, is regular file, and is executable by lighttpd)
(gw_backend.c.1404) invalid "bin-path" => "/usr/lib/munin/cgi/munin-cgi-html" (check that file exists, is regular file, and is executable by lighttpd)

When I try to run a config with the command lighttpd -D -f /etc/munin/lighttpd.conf
The output is this

(gw_backend.c.324) child exited: 1 unix:/var/run/lighttpd/munin-cgi-html.sock-3
(gw_backend.c.468) unlink /var/run/lighttpd/munin-cgi-html.sock-3 after connect failed: Connection refused
(gw_backend.c.324) child exited: 1 unix:/var/run/lighttpd/munin-cgi-graph.sock-0
(gw_backend.c.468) unlink /var/run/lighttpd/munin-cgi-graph.sock-0 after connect failed: Connection refused

Do you guys have any clue what might be happening?

I've been putting off having a local copy of the series and movies I watch because I still can access them quickly and cheaply enough in some streaming service, I think it's time to plan ramping up my selfhosted setup.

I'm wondering what are the pros and cons about saddles with no nose like this one https://www.amazon.ca/Nose-Saddle-Comfort-Large-Bicycle/dp/B087ZBPFCH

My only thought is a bit about balance, I mean the nose can help you grip to the bike better with the thighs than trying to do it to the frame with the legs, specially for someone just learning to ride a bike (this seat will be for my wife).
Any other thought you have about that kind of seats?

All guides to deploy using docker mention typing your keys/credentials/secrets into the docker compose file, or use a .env or similar file, I'm wondering how secure is this and if there's a better option.

Also, this has the issue of having to get into the server to manage them, remembering which file has each credential.

Is there a selfhostable secrets manager? I've only found proprietary/paid ones for large infrastructures and I just need it for a couple of my servers/projects.