This feature request initially encompassed two different requests. What we are doing here is stating what is not possible at this time under this request, and creating a new feedback item which potentially could be possible in the future in regards to custom via for Facebook.
What’s is being declined here are two things that are against the terms of service of the networks under discussion.
1. ‘Tweet-branding’ on Twitter – Twitter’s Terms of Service states in section II.3.C: "You[Developers] should not solicit another developer’s consumer keys or consumer secrets especially if they will be stored or used for actions outside of that developer’s control. Keys and secrets that are compromised will be reset by Twitter. For example, online services that ask for these values in order to provide a “tweet-branding” service are not allowed." For this reason and after discussions with Twitter.com HootSuite will not be supporting a branded ‘via’ solution for Twitter as it is currently in contravention to Twitter’s TOS.
REFERENCE: https://dev.twitter.com/terms/api-terms/diff
2. Facebook messages appearing as if sent via Facebook – Facebook’s Terms of Service state that applications cannot brand messages as being sent via Facebook.
REFERENCE: https://www.facebook.com/brandpermissions/logos.php
HootSuite will, however, be exploring the option of branded via publisher solutions in the future for Facebook only. We have created a new request for this feature and we encourage you to vote it up here: http://feedback.hootsuite.com/forums/40182-hootsuite-com-web-dashboard/suggestions/2625284-custom-via-solutions-for-posts-to-facebook
This feature request initially encompassed two different requests. What we are doing here is stating what is not possible at this time under this request, and creating a new feedback item which potentially could be possible in the future in regards to custom via for Facebook.
What’s is being declined here are two things that are against the terms of service of the networks under discussion.
1. ‘Tweet-branding’ on Twitter – Twitter’s Terms of Service states in section II.3.C: "You[Developers] should not solicit another developer’s consumer keys or consumer secrets especially if they will be stored or used for actions outside of that developer’s control. Keys and secrets that are compromised will be reset by Twitter. For example, online services that ask for these values in order to provide a “tweet-branding” service are not allowed." For this reason and after discussions with Twitter.com HootSuite will not be supporting a branded… more