oh forgot the second part.
first of all. .pub
files are not microsoft owned keyfiles, but Microsoft Office Publisher documents. this is irrelevant now, but this is the only connection of microsoft with .pub
files
second of all, .pub
files can also be OpenPGP public key files. do you use SSH? look into your ~/.ssh/
directory and you will see them there too. also in /etc/ssh/
You can find multiple instances when they are revoked keys and people on stack exchange are figuring out how to update them to use the toolkit after the change.
yeah, signing keys expire from time to time and then they need to be replaced or updated. but these are not per-user, these are public and cannot be kept in secret. this is not a subscription code, not a DRM either, it’s one of those very few exceptions when they are provided for actual security. the packages you download are already signed with the key, if you don’t accept the key your package manager just wont be able to verify if they have been tampered with while in transit. if you don’t accept the key, you can still install the packages, but then you also need to pass the parameter to your package manager that tells it to not verify the packagesthis time, which is 99.999% of the cases a bad idea.
these warnings are interesting, but -Wno-deprecated-gpu-targets
makes me think maybe your card is nearing end of support for CUDA. after that youll need to install an old version of cuda manually (or pin the package versions and risk them silently keeping back other packages too)
what card is it?
also, please take screenshots with the system’s screenshot tool because this is so bad. I mean, multi-megabyte screenshots…
on my distro its common that all repositories use their own signing keys to sign the packages they provide. this includes the nvidia repository. I think here you are prompted to save their key so that your package manager can accept their packages.
I might be wrong, though. next time you could check what happens if you type N. my expectation is that the package manager will throw errors about unverifiable packages
no, it isn’t for
the client shouldn’t be dealing with issues between servers. that’s the servers responsibility. if the server has told the client that it got the message, what is there anymore for the client to do?
The issue with AP objects not making it to other clients / servers is more about federation discovery.
I don’t think so. if you know the recipient, you know it’s servername too. and then your server can forward it to theirs.
I think the problem here is that messages are not always delivered.
I mostly use bluetooth, but the jack of my phone is not sitting there unused. I have wired headphones too, and I frequently use my phone as a microphone (because it is one) by connecting it to my computer by a jack cable.
Also, the next headphone of mine will probably be wired. Always keeping it charged is not really a problem, but the privacy aspect of Bluetooth has started to disturb me.
With a wired connection, you exactly know and control who connects to your devices, and at the same time you don’t announce to the world that you are here.
Also, as I understand you can’t use USB-C for audio and charging or data transfer at the same time, or even all 3 at the same time. Is that right?
That is critical functionality for me. Audio is not just entertainment, it could be an online meeting or other things too, and at one point I’ll have to change my phone, or transfer files from it. However I don’t have a USB-C phone so I can’t test it, so I would appreciate if someone could confirm if this is actually the case.
I think that’s a windows feature