For whatever reason, Chrome ignores #Brusque's settings and notifies you of all your mentions the first time it runs, where FF doesn't. FF also integrates with Cinnamon DE, and Chrome doesn't.
@nitinkhanna I think I can redirect to a fictional page, and have the extension listen for the page, then hijack it to get the token and rediect. Cool.
@nitinkhanna Mozilla creates a random UUID for the extension for every PC that it is installed on (unlike Chrome). I can't add every unique possible endpoint as a valid Redirect URI for Brusque on the pnut end.
@nitinkhanna It's a documented issue with extensions that use oauth. They're deciding that making browser fingerprinting harder is more valuable than allowing devs predict/know what the extension's URI is going to be.
@33MHz so what's the solution? Your system just takes the UUID its being sent, validates the login information and assumes it'll hit the right endpoint after auth? I don't see a problem with that...