BitDesert
BitDesert
Installing `gss-ntlmssp` as stated in #11374 solved this issue for me. I'm using `-Authentication Negotiate`.
We could use https://www.npmjs.com/package/dns-suite so the lookup is completly client side. My Nano Ninja is now an OpenCAP alias provider, would be great to have it in NanoVault as well.
There should be a seperate config entry to show the system information.
If you want you can create a PR for them @sebrock If the filename stays the same you don't have to change anything there. The base path stays `assets/*`
Which should be used for the automatic swiwtching and which should be avoided? This is defined in the environment file.
As Nault is also a browser app it's not possible to query your local DNS server for the TXT record and you would have to query a third-party DNS server...
When we have details on the implementation for Nano this would be a nice feature to have.
Unfortunately it seems from the documentation at https://www.chromestatus.com/feature/6261030015467520 and https://web.dev/nfc/ that direct device to device communication is not working and not in the current scope (HCE if I get it...
We can either cache all aliases and query locally ( https://mynano.ninja/api/accounts/aliases ) or query every address individually async: https://github.com/Nault/Nault/blob/master/src/app/services/ninja.service.ts#L66 Both is fine. Should start with local accounts --> address book...
Thank you for your contribution! We're currently in the process of converting all subpages into the new format so they can get translated. So more strings are coming soon.