Cake
  • Log In
  • Sign Up
    • I don't know of anything other than the ability to share your profile or a conversation.

      You can get a link to a conversation by clicking the button next to FOLLOW at the top of the conversation. You can then use that link in a post on your blog to link back to the conversation.

      You can link to your profile by using the link you see in your browser when on your profile page, https://www.cake.co/users/<your name>.

    • I'm not really sure how embedding your profile here in a blog would help people to share a post here... ?

      I'm not aware of an API which is a shame because I have a few places that I'd love to put a 'discuss on cake' button.

      iframe maybe depending on the header security options here (I haven't looked).

    • Btw, side note: I do feel Cake has potential to be a nice place for bloggers to connect and share their ideas/content.

      So, I'm glad to see that some other folks are oriented to this type of thinking!

    • Btw, side note: I do feel Cake has potential to be a nice place for bloggers to connect and share their ideas/content

      We are just finishing building a site for a client that is a sustainability news site and ethical company directory, and I'd love to include a 'share to Cake' button on each post next to Twitter and Facebook if that was an option.

    • I believe that more external visibility is very much what Cake needs - especially considering the conversations about Cake's future we had just over a month ago - but I guess that a "share to Cake" button wouldn't work as well as a "share to Facebook/Twitter/..." button.

      While it is expected on Facebook or Twitter to see the same resource shared multiple times, each time spawning a mini-conversation among one's own followers (if any), the expectation on Cake would probably be more along the lines of getting one conversation to which all subsequent "shares" are added as additional replies. In fact, the best phrase would probably be "discuss on Cake" instead of "share to Cake".

      This would make an API much more complicated, of course. Instead of just setting some URL value so that the eventual post or tweet ends up containing a rich snippet, in Cake's case this URL would need to act as an ID to determine whether a new conversation needs to be created or the eventual post be added to an existing one. In the best case, this should even work after the URL has been changed for SEO or whatever reasons.

    • This would make an API much more complicated, of course. Instead of just setting some URL value so that the eventual post or tweet ends up containing a rich snippet, in Cake's case this URL would need to act as an ID to determine whether a new conversation needs to be created or the eventual post be added to an existing one. In the best case, this should even work after the URL has been changed for SEO or whatever reasons.

      Yep, it would need to be a lot more complex API and I imagined it working exactly as you've just said.

      It would be pretty great though :-)