Ryan Barrett
Ryan Barrett
turns out this will take a nontrivial amount of work to OAuth-protect with all of the silo OAuth dances, so i probably won't prioritize it after all. @drikkes feel free...
notes to myself: i'd probably do this by adding a generic set of handlers that can oauth-protect any arbitrary bridgy code. something like a new `/silo-auth` handler that starts the...
@drikkes thanks, done.
so this is fully implemented, except for auth. ie if i deployed it, anyone could add or remove domains to any bridgy account. :/ auth is doable, but nontrivial, so...
Some options for auth here: * **Redo the whole silo OAuth dance.** Pro: we already to this for interactive publishing and deleting accounts. Con: it's bad UX. It's surprising and...
...and a workaround punt option. Don't do any of the auth ideas. Instead tell people to temporarily remove the site(s) from their Twitter profile, auth with Bridgy, and then add...
@manton in the meantime, I've removed micro.blog from https://brid.gy/twitter/mantonsblog manually.
[I've expanded on the workaround above in the docs.](https://brid.gy/about#add-remove-url)
this is harmless, everything still works. deprioritizing.
hard to check whether this is still happening, since [the google cloud log browser doesn't support regexp search](https://cloud.google.com/logging/docs/view/logs_viewer_v2?hl=en_US#searches_that_dont_do_what_you_expect).