Move posts from one channel to another (was: 'Read later' channel)

[swentel]

After giving it some more thoughts myself, being able to move posts from one channel to another (I would actually copy it internally I think on the Drupal side) using the API would probably solve it more easily. Users can create their own 'Read later' or 'Saved later' channel and I can add settings to Indigenous for instance that channels are not automatically marked as read for instance. Maybe at some point #29 could help here as well, but that's not really necessary here.

From an API perspective, the action would be timeline, method 'move' and an additional property 'channel_target' so the server knows to which channel to move/copy this post.

My original brainstorm idea underneath

The idea is that you would be able to move a post to this channel so that it comes in there to read later. Currently I sometimes mark a post as unread, but when new posts arrive, they get marked unread again when I hit the channel so I 'forget' them. (Indigenous automatically marks them unread when entering a channel - this is configurable though on a global level where you have to manually hit the 'mark read' button for each post, but that's too tedious for me).

Main question:

• would this be an addition on the microsub endpoint which stores this on the microsub endpoint
• or should I only keep this in indigenous.

The latter means I have to store the complete object in a table somewhere, which should be fairly easy. But an API addition on the microsub spec could work too so that any client can start implementing this.

In my mind I see a new action 'later' which has a few methods: 'add', 'remove' and 'read' (the default in case method is not passed in). Not sure then whether 'later' would be reserved channel name or not, just like notifications is.

I know of indiepaper for instance, but that's not entirely what I want here, it's really about an existing item in one of my feeds.

Thoughts? I'm totally fine if this would only be a client thing, just wonder if other people might find this interesting as an addition to the spec or not.

[swentel]

Found in #24

For example I have a “Saved” channel where I use it as a Read it later channel.

@EdwardHinkle is this is a channel you created in your microsub server just like any other, or is it hard coded? And how do you move posts in there, is there an option in Indigenous to move posts from one channel to another? (which seems unlikely as there isn't an API call for that afaics, so I presume it's a custom command)

[EdwardHinkle]

Saved is just a regular Microsub channel. Aperture allows me to add posts via Micropub. So I use the Share Sheet (in either Indigenous or Safari) to send a post to Indiepaper. Indiepaper then saves the post via Micropub into my Saved channel

[swentel]

Thinking about it some more, this could also just be an addition to the spec to be able to move posts from one channel to another using the API. That might work for me too. I would add something to the the settings in Indigenous then to be able to mark a channel as not being automatically being read.

[swentel]

Closing in favor of #40