Jan Tennert

@eb-ib Both of the issues you pointed out will be fixed in #1278 (the overriding & history). If you can't upgrade you have to mimic the functionality: Get the OAuth url like this: ```kotlin val urlToOpen = supabaseClient.auth.getOAuthUrl(Provider, deeplink) ``` Then just open the url correctly as a temporary workaround.

#1161. One drawback is of course all clients have a synchronized default log level

> The loggers being statically initialized in the plugins makes it hard for me to see how to make the non-ABI breaking Yea they are static because passing the logger down to every corner of every util function is really tiresome. Thought about making it non-static before but that didn't really work in the end that well. We could think about doing a similar thing like the default log level, provide a default logging backend or something like that. Upon checking the current code, some recent PR seemed to broke the default log level mechanism. I'll fix that

Sorry I'm currently really busy with supabase-kt and university, I wouldn't expect anything soon. Obviously if anyone else wants to start working on a plugin, feel free.

@eb-ib Right, in the past were some problems where the URL was replaced by localhost by Ktor for some reason, but maybe we can just show the first two characters and mask the rest

Also @eb-ib I agree that the apikey and Authorization header should be masked, but the URL doesn't seem very sensitive to me

They should probably be masked. Can you create an feature request? Will look at it later