4 ms·

We fucked up here, and I apologize. Many thanks to robbiet480 for writing a script to help clean it up. We've just pushed new client and server versions to cle

by kogir 10y ago

We fucked up here, and I apologize. Many thanks to robbiet480 for writing a script to help clean it up. We've just pushed new client and server versions to cleanup hooks when the last admin user logs out. New downloads will be the latest version, and current users can update now using the Ship -> Check for Updates menu option. After that, you can logout using Ship -> Account -> Logout. If you used the app earlier and want to be sure all hooks are cleared out, you can log back in once more and then logout again to trigger the removal. There is also updated documentation here: https://www.realartists.com/docs/2.0/uninstall.html https://www.realartists.com/docs/2.0/uninstall.html So about hooks - Hooks are added so that Ship is alerted when new repos are created, issues/labels/milestones/comments are added/modified/deleted, issue templates change, etc. The user experience without hooks is acceptable, but not great. Presumably if you're using Ship, you want it to show the most up to date information. We disclose when you authorize Ship that you're granting repository and organization webhook permissions. This appears to be insufficient notice. We'll think about that next. If anyone is still having trouble or needs personalized help, we're reachable at support@realartists.com.

zyxzkz 10y ago
So..., why did you have to install the webhooks in the first place?
- pault 10y ago
  > Hooks are added so that Ship is alerted when new repos are created, issues/labels/milestones/comments are added/modified/deleted, issue templates change, etc.
lemming 10y ago
Have you considered only adding webhooks per-repo, and not globally? I have access to numerous repos that I don't want or need real-time updates from, as well as repos from organisations that have added me which I would really rather not touch. They would probably not be happy that their repos are suddenly sending data to a third party that they didn't consent to. I would love something like Ship for my main public repo, and in fact would prefer to just use Ship for that repo.
farnsworth 10y ago
People are used to granting access to an app without assuming that it's going to take full advantage of that access. I have access to a lot of repos. Like, a LOT of repos with a lot of collaborators. And I just had some app add webhooks to every single one. I'm glad I could remove them with 'logout', but I would have really appreciated a more obvious message.
hobarrera 10y ago
I wish we'd see this more often. You fucked up, but came clean about it, apologized, and gave a working solution. Congrats!

by kogir 10y ago

zyxzkz 10y ago

So..., why did you have to install the webhooks in the first place?

pault 10y ago
> Hooks are added so that Ship is alerted when new repos are created, issues/labels/milestones/comments are added/modified/deleted, issue templates change, etc.

lemming 10y ago

Have you considered only adding webhooks per-repo, and not globally? I have access to numerous repos that I don't want or need real-time updates from, as well as repos from organisations that have added me which I would really rather not touch. They would probably not be happy that their repos are suddenly sending data to a third party that they didn't consent to. I would love something like Ship for my main public repo, and in fact would prefer to just use Ship for that repo.

farnsworth 10y ago

People are used to granting access to an app without assuming that it's going to take full advantage of that access. I have access to a lot of repos. Like, a LOT of repos with a lot of collaborators. And I just had some app add webhooks to every single one. I'm glad I could remove them with 'logout', but I would have really appreciated a more obvious message.

hobarrera 10y ago

I wish we'd see this more often. You fucked up, but came clean about it, apologized, and gave a working solution. Congrats!