Haven’t used it [silent.link] myself. All I know is that all (or some) plans they offer include only incomming-calls, not outgoing. But good point you make about delays. That’s important. Haven’t thought about that myself.

I’m not too versed in it myself yet. You were asking about these services in general, right? Since you wrote “voip numbers”. I’ll keep tabs on your other comment then

Bluetooth and gps permissions are linked? Why in the ass of logic is that reasonable? My Bose app required gps for connecting to headphones. I didnt see the logic

Silent.link is also worth considering. I think it also works for people in the EU.

The hack is Super Saiyan God

Does it not randomly crash anymore?

You hate doing math?

If I touch furniture, I also need to touch it with my other hand at least once

Why is /mnt a “temporary” mounting point? I alwags put my permanent ones there. I’d say /media is temporary…

Sadly I don’t remember. Sometimes it comes preinstalled, sometimes not, depending on OS or something. (Maybe Manjaro gnome). I could copy and paste inside of vim, but not to/from outside vim.

For vim I had to config or install something just to be able to COPY something to use outside vim, how backwards is that? Isn’t this the most standard feature one can expect to work as default?

Calling communities subs is fine. It need not necessarily refer to reddit. Sub means under/secondary/part of.

Depends on the person. If you’re happy living in wonderland, theism is the way to go

No unfortunately not… Would’ve been a real pain.

Hey that works too! Same effect as my previous workaround, that I just posted yesterday.

I do have to repeat this command everytime, so I had to put it into ~/.zshrc so it’s executed beforehand in every new terminal.

It still does feel lile a workaround since it ‘resets’ itself (as I said) with every new terminal.

I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK

it works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase/private key

I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK

it works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase.

I am not sure I “solved” this but when I add this to my startup script for my terminal (~/.zshrc):

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK

it works then. I am not sure I’m still using the ssh agent, but at least it also does not cache my passphrase (or private key in ram)

I searched. When I change this variable (path), it works. So in the startup script for my terminal (~/.zshrc) I added this:

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK

Now it works, but I’m not sure why. Anything BUT /run/user/1000/gcr/ssh works I think

reboot makes no difference. A new terminal gives the symptoms from the start.

I think I found a bad workaround. If I add this script to ~/.zshrc (because I’m not using bash but zsh)

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK
if [ ! -S "$SSH_AUTH_SOCK" ]; then
    eval $(ssh-agent -a "$SSH_AUTH_SOCK")
fi

then it works. But I think I’m still using the ssh agent which I actually should not be using. At least it’s asking for the passphrase every time, which is nice. Even in the same terminal after ssh logout.

EDIT: The first two lines do the trick as well:

SSH_AUTH_SOCK=/tmp/ssh-agent-$USER-socket
export SSH_AUTH_SOCK

EDIT: If I change this SSH_AUTH_SOCK to ANYTHING else, it also works. So /run/user/1000/gcr/ssh does not work. I gave ample permission to this file, so that cannot be the problem. Perhaps BECAUSE this is a file. I think the SSH_AUTH_SOCK should point to a nonexisting file because then it makes temporarily a special file that it needs. Ok I’m just shooting in the dark.