Thanks for your reply.
reading e.g. a URL to the tweet or post in question and extracting the relevant content, which would be the simplest from the end-user perspective
I think, this would best be done using a web clipper browser extension, once it exists. Then the user could select how to display the post. Tweets, for example, can be text, images and/or videos. Maybe a user is interested only in a part of it and can select it via the UI of the web clipper. It would then be imported into the collection using the appropriate artwork format.
an extension that uses the Twitter API, allowing someone to e.g. ‘follow’ a twitter user via Openframe and display whatever their latest tweet is.
Yes, I think this would be great too. If there is an option to control the plugin from within the web app it would be really convenient for the user.
Do you think it would be best to combine all of those APIs into one “social” extensions? Maybe we could list all relevant services here to figure out if this makes sense and what would be a suitable name for the extension:
Not yet checked:
I’ve never written an open-source application using an API of commercial services. How is API access and keys usually handled in those cases?