Perry Mitchell

If you're still working around this error, can you please include your code for review? Obviously after having removed any credentials (please leave the structure the same, however).

@bitrevo You're right, collections should be queried with a trailing slash. Several sources I've checked (no RFC that I found, yet) seem to suggest to do so to remove ambiguity...

Hi @PVince81 - I'm looking into this now. From a first glance it looks quite easy to solve - adding such a function to support safe decoding of all values...

Thanks @PVince81 - I'd missed your [comment on the Nextcloud issue](https://github.com/nextcloud/server/issues/28243#issuecomment-931598407). So it seems that the issue stems from the XML parser I'm using. What would you recommend? Changing parser...

I had a play and couldn't find any alternate configuration for the parser that seemed to work in every test case I have. I'd be happy if someone wanted to...

At least 4Shared is free - Someone might choose to help by debugging the response (XML) to the quota request. Perhaps it's not available, or perhaps it's not a standard...

Seems that this is still an issue:  I believe it's caused by the lack of checking which choice was made when selecting a version, as processing just continues here:...

Also good to check if the current commit is tagged, perhaps `git describe --exact-match HEAD` helps here. But perhaps this can be entirely avoided by checking the commit status, as...

Works fine for me with import: ```typescript import bcrypt from "bcrypt"; // later await bcrypt.compare(password, hash); ```

I'm stuck on this as well. How is it possible to implement standard Authorization code flow if the client secret is always required? It can't be securely passed in the...