You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My sense is that Yarns' new post function should be designed to accommodate input from third-parties. This might be more a matter of documentation than anything else. Noting it here for further thought
The text was updated successfully, but these errors were encountered:
Actually, this will need some additional code, since it should at least account for cases where a special channel ('notifications', 'read later' etc.) does not already exist
An external plugin might also want the ability to edit/delete posts it has submitted. In some cases, it might even make sense to not store its "posts" in yarns, but fetch them from the plugin dynamically.
Very good point. Thanks Sven.
One potential challenge (though a surmountable one) is that if “posts” are
stored in a third party plugin, Yarns has to be able to pass actions from a
client to that plugin - such as marking items read, deleting, etc.
The most robust option might be to support two methods
- A plugin could tell Yarns to create a new channel and ‘posts’ in the
channel, and then leave the channel’s management up to Yarns
- A plugin could define it’s own channel(s), to be added to Yarns’ output.
In this case, Yarns must also be able to pass actions from the endpoint to
that plugin
On April 22, 2019 at 2:29:29 PM, Sven ([email protected]) wrote:
An external plugin might also want the ability to edit/delete posts it has
submitted. In some cases, it might even make sense to not store its "posts"
in yarns, but fetch them from the plugin dynamically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC5U5R5NMQQJCZP6FHZKN73PRX7YPANCNFSM4HHRP2GA>
.
Based on discussion at https://chat.indieweb.org/wordpress/2019-04-22#t1555952962729200
@sknebel suggested that a microsub server could integrate with the webmentions plugin, and display webmentions in a notifications channel
This reminded me that I'd like to add a 'read later' channel that could receive posts from https://github.com/cleverdevil/indiepaper or similar sources.
My sense is that Yarns' new post function should be designed to accommodate input from third-parties. This might be more a matter of documentation than anything else. Noting it here for further thought
The text was updated successfully, but these errors were encountered: