Open ThatOneCalculator opened 1 year ago
Sounds like a Calckey issue though?
Other clients handle it perfectly fine though, maybe see if nodeinfo
shows software
is "calckey", open the auth window in the browser instead of the embedded WebView?
Can you tell me what calckey instance I can use to debug this please? I don't think we will add special handling just for calckey though.
https://stop.voring.me (recommended) or https://bz.pawdev.me
Update: someone in the comments to my post pointed out that you can hit the 3 dots in the top right to log in with browser -- this option works great! I think a simple nodeinfo check to see if software
is calckey
, then to use that option if true would be enough to provide a smooth option for Calckey users.
For whatever reason Calckey login needs Local Storage to work, but if I enable that it fails with another JS error
We should switch back to Custom tab being the default login I guess
I'm not sure what the service worker error is about, but custom tabs would work.
@connyduck any chance we can see an update on this? Should be a relatively simple fix, and Calckey is even more compatible with the Mastodon API now.
@ThatOneCalculator Object.fromEntries is a relatively new ECMAScript API, so the error here could be that that version of the browser being used by the operating system doesn't support — it may need a polyfill
In the development branch of Calckey, we added inital support for Mastodon auth and API, and it works in apps like Megalodon, tooot, Elk, etc. It seems the URL tusky uses for authentication causes Calckey to error out though.