-
Notifications
You must be signed in to change notification settings - Fork 7
Decommission #vimeo infrastructure #22
Comments
@ManfredKarrer, please privately share with me the credentials for the https://vimeo.com/getbitsquare account. I'm finishing up creating the Bisq YouTube channel (bisq-network/youtube#2) and want to download the videos from Vimeo and shut down the account so we stop paying for it etc. Note that I'll be sure to embed the YouTube version of the explainer video on our website before shutting Vimeo down. |
Ping, @ManfredKarrer. Could you send the Bitsquare Vimeo credentials to both me and @ripcurlx? thanks. |
Sent by email. |
@ripcurlx, as YouTube Admin (bisq-network/roles#56), would you be up for using Manfred's Vimeo credentials (which I can share with you) to, one way or another, clear out all our videos from Vimeo and categorize them under our YouTube channel? It may be the case that we want to drop some or even many of these videos, i.e. there may not be any value in bringing them over to YouTube. Another option would be to bring everything over to YouTube and mark some or many of them as unlisted. In any case, you can see the outline of this work I sketched out in the description of this issue. If you're up for it, I'll assign this issue to you. Thanks. |
Closing as complete. @ManfredKarrer, I've downloaded all the videos from our Vimeo account (I just have them in a folder locally, thought that would be better than fully obliterating them. Maybe I'll upload a zip somewhere, GDrive or something). I've also deleted our Vimeo account, and first I disabled auto-renewal billing, just to be safe: The explainer video has been transferred to YouTube, and per bisq-network/bisq-website#51, it is now being served from the homepage of https://bisq.network. So all should be well. |
We have an existing paid Vimeo account at https://vimeo.com/getbitsquare, but we haven't used it much over time. It doesn't justify its costs, and it's furthermore just non-ideal compared to what we can and will do with a properly-managed YouTube presence (see #21).
The text was updated successfully, but these errors were encountered: