Today was spent generating a new release of both the extension and the local client.
The changes were mainly related to updating the binaries in the local client to the latest versions of ant, dweb & anttp. I also updated the default ports for dweb & anttp.
When you type in a port number to the websocket field, all that does is check if there is a valid connection to that port. It does not confirm if it’s actually the correct port for the websocket on the local client. So if you are running anttp for example, typing in 18888 would show connected - but it still wouldn’t be connected to the local client. Perhaps I should put some different popup message for if people type 18888 and 5537.
The reason for this is that it’s impossible for the extension to know the websocket port before hand (as the user might have updated it on the local client - which means it wouldn’t be able to connect). But once the extension is connected, it can retrieve the ant, anttp and dweb ports from the local client - even when they are changed by the user on the local client.
So the default port for the websocket connection to the local client is 8084, which if you are running the local client should just work when you test the local connection.
Using the local client means you can upload files from the extension (and webpages soon via extension) through the local client, which has wallet details.
Because the extension is kind of in a secure enclave, it needs this websocket to be able to pass data (file to be uploaded) down to the ant binary for upload (which I include in the local client).
I’ll have better instructions tomorrow that might make things a little clearer!
Just a note that on installing, I only have Anttp on the windows version of the extension on brave, and no Dweb (Edit: just read this is only available in local mode - I will get the client running and retry!). Wallet says coming soon, and upload is greyed out, probably because I don’t have a wallet loaded.
Looking forward to seeing this develop
Edit: I tried again today, and have the local client running, a wallet registered, and browsing Atlas through it. All good!
Yes would be good to try with the local client, as it’s required for some features (uploading etc) - and some more to come!
Glad to hear it worked out for you!
I’m working on the shortcodes feature now and will hopefully have it out in a few days. There was an issue with one of the available endpoints but that should be solved soon. I’ll be adding another endpoint server in the next release of the extension too - but you can always just add endpoint servers manually anyway.
