Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Flickr integration

Comments

19 comments

  • Mike Conley

    I notice that the latest release of Capture One has integration with Glass. Glass is very nice, but expensive and not particularly well-known. Flickr has been around forever. It absolutely would be much more helpful to have Flickr integration; I can't quite understand why this hasn't happened yet.

    2
  • syborg

    I also don't understand, why prioritize support for some exotic hosting services (and for Mac only) not noticing an elephant in the room.

    3
  • Mike Conley

    Presumably one could write an AppleScript script to do this. Maybe I'll have a go; clearly, it's not going to be built-in anytime soon.

    0
  • Marcin Mrzygłocki
    Top Commenter

    If only the entire process up until export was already polished and covered all possibilities... what happens after is not C1P's responsibility, so I don't understand viability of spending resources on post-export actions in light of numerous improvements that did not fit into backlog despite high count of votes, that would have an effect on WHAT is exported and using how much effort, which is primary focus of the application.

    2
  • Walter Rowe
    Moderator
    Top Commenter

    The Glass plugin was probably written by Glass. If you want a Flickr plugin you should talk to Flickr.

    It would be great for Capture One to pursue Flickr to do this.

    0
  • syborg

    There's such thing in software development world as API. Most of the free and commercial services/products have open APIs allowing developers to build integrations. Flickr is not an exception - https://www.flickr.com/services/developer. There's no need to 'pursue' anybody.

     

    1
  • syborg

    @SFA I don't mean just automated uploads, I mean full integration (collections mapping/sync, ratings/comments retrieval etc.).

    1
  • Walter Rowe
    Moderator
    Top Commenter

    @syborg .. you need to ask Flickr to do this.

    -1
  • syborg

    No, I don't.

    I explained why in the comment above, but it's still shown in Pending state (because of hyperlinks, I guess)...

    1
  • BeO
    Top Commenter

    I was very surprised about the Glass integration.

    But I guess I am not the only one who does not see C1 as an image publishing system to (maybe hip but) proprietary website. I see it rather a raw converter/editor, and maybe a photographer-client conversation tool about photo shoots, which is missing much even in its core functionality.

    1
  • Walter Rowe
    Moderator
    Top Commenter

    BeO .. people see social media publishing plugins in other apps and then want Capture One to do it too. Those plugins are likely written by the social media companies and not the app owners. This is why I am advocating for people to ask Flickr to do this. I bet Glass did the heavy lifting with Capture One's help.

    The reason you see those plugins in other apps is because those other apps have huge market shares and the social media companies feel the return is worth the investment. With Capture One being a fraction of the market size of some other apps the social media sites likely don't see the return worth the investment to do a plugin for Capture One.

    One company that previously supported Capture One removed their plugin.

    0
  • syborg

    >>Those plugins are likely written by the social media companies and not the app owners

    No, they are not. Have you ever used any open REST/GraphQL API in your code?
    Walter, please stop writing about topics you have no idea about. You made your point.

    1
  • Walter Rowe
    Moderator
    Top Commenter

    I have nearly 40 years of experience in this field I know exactly what I am talking about. Capture One has a plugin SDK they can use.

    0
  • BeO
    Top Commenter

    Yes, I think think so too, heavy lifting on the 3rd party side.

    Plug-ins - Export and Publish
    Capture One 12 introduces a new Plug-in platform for developers wishing to build content and  functionality for the Capture One community. For more information on developing Capture One plug-ins, see the developer portal on www.phaseone.com

    As part of the new Plug-in platform, “Edit with...” and “Open with...” are re-factored as plugins.  These can now be configured with your favorite applications from the Preferences menu, which will then only show those applications in the respective menus.

    from

    https://support.captureone.com/hc/article_attachments/360010792917/capture-one-12-0-4-release-notes.pdf

    0
  • syborg

    *sigh*
    Capture One SDK is intended for creating integrations with Capture One. It's just one side of the process.

    Let me quote C1 API documentation, IPublishingPlugin interface description, in particular:

    "The protocol allows plugins to implement publishing capabilities. Publishing plugins are plugins that take the path of processed variants as inputs, publish them to a remote service and produce a PluginActionPublishResult upon successful completion. This protocol defines the action and result layers in the Action-Task-Result paradigm, for publishing plugins. Plugins that adopt this protocol provide PluginAction definitions that Capture One uses to populate its UI, allowing users to start the tasks required by those actions."

    So, to interact with that "remote service" plugin uses the service API, in this case, Flickr - flickr.com/services/developer. Plugin basically acts like a black box to C1, wrapping all REST API interactions with the service, and communicates with Capture One by using documented SDK interfaces (public interface IPublishingPlugin : IFileHandlingPlugin), and implementing required methods (e.g., GetPublishingActions, that returns a collection of possible PluginAction's, depending on the service used).

    Flickr developers don't need to build plugins for every app out there, they already provided all the interested parties with open API (and that's the point of APIs). It's up to C1 devs (or any other enthusiasts) now to implement required publishing functionality.

    -1
  • BeO
    Top Commenter

    So, that does mean that any party can utilize the public APIs from both C1 and Flickr and create a plugin, right? Surely with at least permission of C1.

    This party can of course be C1, Flickr or any 3rd party, correct?

    Do you see the author or a copyright hint for the Glass plugin in the C1 preferences?

    Btw, the more you convince me that C1 staff would be needed the less likely I am going to upvote :-)

     

    1
  • syborg

    >> So, that does mean that any party can utilize the public APIs from both C1 and Flickr and create a plugin, right?
    Finally...

    >>Do you see the author or a copyright hint for the Glass plugin in the C1 preferences?

    No, I don't, because I don't have Glass plugin.

    >>Btw, the more you convince me that C1 staff would be needed the less likely I am going to upvote :-)

    I'm not convincing anybody, I just explained how it usually works. Sapienti sat.

     

    1
  • Walter Rowe
    Moderator
    Top Commenter

    syborg

    You seem determined to convince us this is Capture One's responsibility. It is not. They provide the publishing plugin SDK. The social media sites can leverage that and their own API to make a plugin for Capture One. I am sure Capture One would be willing to help and coach them.

    0
  • Martin Tolley

    I personally use photomechanic. Final images exported from C1 can be opened directly into PM and from there they can be uploaded in a variety of formats to many different Web sites and clients, and PM handles Flickr addressing, album creation adding metadata etc seamlessly.

    0

Please sign in to leave a comment.