Aaron Parecki

My first thought is concerning potentially writing posts offline. I think I would like to be able to query my micropub endpoint and get an array of contacts, in the same way I can get an array of syndication targets. This allows the ability to be writing a post offline and to power either person tagging or @-mentioning.

Right now you can only have one draft post at a time (if you click cancel while writing a post, it will ask if you want to save you post as a draft, if so it will auto-fill the form when you open it back up again).

Eventually I would like if you are offline to click "Post" and to have it auto-post when it gets internet again. So in those cases I would want to be able to handle all nickname cache stuff on device after the initial login (and maybe periodically refetching the cache every couple of days or something).

I can see how it could be useful to query the server with the string so far in a situation where you know you have internet.

Yeah, exactly. On timeline can you provide both a before AND after token? You definitely would want to be able to specify both in the "timelineCounts" method.

Excellent. I think the "unread counts" property is useful based on common reader approaches. So I think that is definitely valuable, I can see a lot of people wanting to use that. For my use-case, my unread status will likely be based on if the updated property has been "updated".

I'm gonna have to think about this further because there are three options I could do. Regardless of the option I use, Indigenous' default will always be based on if new posts have come in. However, there are some additional features I might implement:

• I could provide an account-wide setting that changes all Channel Unread indicators to be based on if there are any unread posts in the channel. This would be helpful for people that are completionists.
• One potentially interesting idea is instead of the above option, I could provide a per-channel setting of the "Unread Status" of the channel. This would be helpful because some channels I might want to read completely (more article based channels), whereas other channels I might want to be able to just scroll to the top and only have it be marked as unread when a new post comes in.

I think I'm leaning towards that last approach:

• All channels default to showing as read when the user has scrolled to the top and showing as unread when the channel has been updated with at least one new post.
• Each channel can be edited to have it's read/unread indicator be based on if there are any unread posts in the channel.