Update authpswd.md to make it clear not to use authpswd

[Finley224]

I wrote a client using this to login, it should be more clear that this should not be used.

[Finley224]

let me fix this

[Finley224]

"nodeModulesDir": "auto", is breaking it

[williamhorning]

"nodeModulesDir": "auto", is breaking it

please update to the latest deno 2 rc using deno upgrade --rc

[Finley224]

"nodeModulesDir": "auto", is breaking it

please update to the latest deno 2 rc using deno upgrade --rc

ok, let me give that a go

[Finley224]

ok. if you re run the checks it should work now.

[Finley224]

ok. if you re run the checks it should work now.

Yep, checks passed.

[williamhorning]

alright, despite the checks passing, authpswd isn't completely replaced by the api route. in the majority of cases, you should use the api route and then pass the token to cloudlink using the token query parameter when connecting (with a url like wss://server.meower.org/?v=1&token=no, however, without that documented anywhere, just saying "don't use authpswd" is bad.

[Finley224]

alright, despite the checks passing, authpswd isn't completely replaced by the api route. in the majority of cases, you should use the api route and then pass the token to cloudlink using the token query parameter when connecting (with a url like wss://server.meower.org/?v=1&token=no, however, without that documented anywhere, just saying "don't use authpswd" is bad.

ok, is there a way It could be worded better?

[Finley224]

@williamhorning what about adding a note like, Instead of using authpswd, get a token using the REST API then connect to the web socket with your token "wss://server.meower.org/?v=1&token={your token from api}".

[williamhorning]

yes, that'd work

[Finley224]

ok, let me add that to the pull request

[Finley224]

Ok, I updated it based on your feedback @williamhorning.

[williamhorning]

please remove package-lock file

[Finley224]

@williamhorning done