Hi guys,
This is a really interesting point, and just want you to know that weâre discussing how we might be able to make it better. I agree that the widget set-up/ownership situation when working for a client doesnât fit great with how our settings are organised.
Honestly I have no idea what kind of graceful solution weâll come up with, there are a few different ways we could go. But right now itâs noted and on the backlog.
For the time being though, the simplest approach to this situation is to use a third Twitter account: Create a new account for your clientâs widget, use that account to create and configure the widget, and then hand over that account and the password for it to the client along with the other site deliverables. That way they donât need to do the configuration themselves, and you donât need to own the widget config on your own account.
Thanks for the feedback, I appreciate it.
Ben