WeChat ID
aaronpk_tv
Monday, February 12, 2018
| bicycle |
28 min
|
|
4.9 miles
|
bicycle |
-
-
-
-
š¤¦āāļø Thanks. I think I'll add new channels to the top! -
I'm implementing a draft of this in Aperture right now. Here is the current API.
Every entry now includes a unique system ID, meant for internal identification of the item (not global identification). This is returned in the timeline response as the parameter
_id, and there is now also_is_read. For example:{ "items": [ { "type": "entry", "url": "http://example.com/100", ... "_id": "41003", "_is_read": false ] }These new
_idvalues are meant to be opaque to clients, and must always be a string. Some servers will likely use integer database IDs, but other servers may use other string identifiers for entries depending on the implementation.Retrieving the list of channels now also includes the number of unread entries in the channel:
{ "channels": [ { "uid": "notifications", "name": "Notifications", "unread": 0 }, { "uid": "YPGiUrZjNM36LNdpFy7eSzJE7o2aK82z", "name": "IndieWeb", "unread": 7 } ] }To mark an individual entry as read:
action=timelinechannel=examplemethod=mark_readentry=1234
To mark multiple entires as read:
action=timelinechannel=examplemethod=mark_readentry[]=1234entry[]=5678
Both of the above also work with
method=mark_unread.To mark an entry read as well as everything before it:
action=timelinechannel=examplemethod=mark_readlast_read_entry=1234
This is to address the use case of streams, where you really only care about knowing where in the stream you've scrolled to and whether there are any new entries since then.
This is mostly inspired by the Feedly Markers API Mark one or more articles as read and Mark a feed as read
-
-
This has been implemented in Aperture and documented in the spec: https://indieweb.org/Microsub-spec#Set_Channel_Order
-
The
unreadproperty has been documented in the spec, and implemented in Aperture.I am not sure the
updatedproperty is useful, so I'm leaving it out for now. I'm going to close this issue as most of the discussion is taking place in #4. -
With the work in tracking read state, I've started implementing these additional properties by prefixing them with
_. I felt like that was the least obtrusive way to include them while also making it obvious they are not part of the post vocabulary.Additional brainstorming around other per-item data should be discussed in new issues.
-
EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 12
Not that it has to be implemented right now, but I do want to make a case for the āupdatedā field of a channel. In order to reduce āhigh noise signalā, for most of my channels, Iāll want the channelās āunread indicatorā to disappear when I reach the top of the timeline (even if things are unread). When a channel is updated (receives new posts), I would want to be able to re-enable the unread indicator. Essentially saying āthere are new posts hereā rather than saying āthere are unread posts hereā. In fact now that I say it, I might make the indicator a different color as well. That said, the purpose of such a channel is, I want to be able to know what I have and havenāt read, while only being prompted to open the channel if there are new posts. The ānew postsā indicator essentially upping the priority of time looking at that channel than one without new posts. That said, when I have more time, to be able to go back to an existing channel and still know what I havenāt read (which is why this canāt just use the ālast_read_entryā, even though that is a useful method).
(Originally published at: https://eddiehinkle.com/2018/02/12/7/reply/)
Now that you mention it, I think Facebook's notifications work this way.
They show a little number over the notification icon with the number of new notifications. However, they also track whether you've clicked on individual notifications separately. If you click the icon with the number, then the number is cleared and won't show again until there is new content. If you click on an individual notification, then the next time you drop down the notification bar that notification will be white instead of blue. -
Add option to remove entries when unfollowing a source
When removing a source from a channel, Aperture provides an option in the UI to either remove all the existing entries or just stop adding new entries. It may be useful for this to be an option for Microsub clients as well.continue reading... -
EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 12
Not that it has to be implemented right now, but I do want to make a case for the āupdatedā field of a channel. In order to reduce āhigh noise signalā, for most of my channels, Iāll want the channelās āunread indicatorā to disappear when I reach the top of the timeline (even if things are unread). When a channel is updated (receives new posts), I would want to be able to re-enable the unread indicator. Essentially saying āthere are new posts hereā rather than saying āthere are unread posts hereā. In fact now that I say it, I might make the indicator a different color as well. That said, the purpose of such a channel is, I want to be able to know what I have and havenāt read, while only being prompted to open the channel if there are new posts. The ānew postsā indicator essentially upping the priority of time looking at that channel than one without new posts. That said, when I have more time, to be able to go back to an existing channel and still know what I havenāt read (which is why this canāt just use the ālast_read_entryā, even though that is a useful method).
(Originally published at: https://eddiehinkle.com/2018/02/12/7/reply/)
Here's a question. Do you imagine this additional state being something that only individual clients are aware of, or should that be synced to the server as well?
If the server returns the "updated" date, then the client has enough information to show the indicator itself. But as far as other clients are concerned, they wouldn't know about whether you've seen those posts in another client.
I'm kind of leaning towards it being a client-only thing, at least for now.
If that's going to end up getting pushed to the server then I think we need to better define the different kinds of states. Maybe "read" vs "seen", where "seen" is the soft indicator that the client has displayed the post to the user, and "read" means they've opened it up (or maybe even explicitly marked it as read). -
Aaron Parecki
https://aaronparecki.com/
•
Feb 12
I'm implementing a draft of this in Aperture right now. Here is the current API...
I should add that the `_id` values are meant to be an identifier for this instance of the entry in the channel, not an identifier for the entry across channels. This means if you're following the same feed in multiple channels, entries may have a different `_id`. -
Channel icons?
I just added emoji in the channel names, and now I'm wondering if there should be a way to choose/upload an actual custom icon for channels.continue reading...
