I've tagged the development version of Dianara, my Pump.io client, as "alpha", in preparation for a release by the end of the month, hopefully.
The most noticeable changes are these two:
I'd like to get some feedback for these new features and default settings. Let me know what you think.
You can file bug reports in the issue tracker, though you might want to comment here first.
By the way, Italian and German translations have been stuck for a while. If anyone would like to help updating them, that'd be very appreciated ;)
(or, you know, providing any other new translation, of course!)
Cheers! =)
EDIT: Now tagged as "Release Candidate", with estimated release on June 11th.
Douglas Perkins, sazius, Face, soloojos and 5 others likes this.
Face, Face, Face, juancuyo and 5 others shared this.
>> Kete Foy:
“one thing I noticed is that any comments aren't loading until after I make a comment. Most of the time, I see the comments, so it might apply after staying on the 1st page all day.”
If I understand you correctly, you're not seeing all comments for some posts until you comment on them?
It's possible that those comments come from people you don't follow. If someone you don't follow comments on a note that isn't yours, usually the comment won't be "addressed" (in the protocol sense, using the To/Cc fields) to you, so you won't get it in your "Meanwhile" feed. And if a comment doesn't come through there, it won't appear on the parent post until you click "reload comments" (which is also triggered after you comment on the post).
When you go to an older page, each post is received full, in its current state, with up to 4 replies included, regardless of who are the authors of those replies.
This is mostly a limitation of how Pump.io works at the moment. Or design decision, depending on how you look at it.
>> Kete Foy:
“Similarly, maybe new posts should bump old posts to the next page.”
This actually happens. The "rule" is, once the timeline has more than double the number of configured "posts per page", the ones older than those get removed from the visible timeline, so they get effectively "moved" to the older pages.
So if you have the default "20", your timeline will show up to 40 posts. If an update then brings 5 new posts, the older 5 at the bottom, will be removed from view.
Maybe I should rename that setting to something like "Maximum posts per update" or something. The current name made more sense prior to v1.3.0, when timelines were simply completely reloaded each time.
>> JanKusanagi:
And if a comment doesn't come through there, it won't appear on the parent post until you click "reload comments" (which is also triggered after you comment on the post).
Maybe I should rename that setting to something like "Maximum posts per update" or something. The current name made more sense prior to v1.3.0, when timelines were simply completely reloaded each time.”
Great answers, I'll try to start reloading comments before commenting. Another thought I just had—when I make a comment, Dianara could mark the note read
>> Kete Foy:
“[...] Another thought I just had—when I make a comment, Dianara could mark the note read [...]”
Yes, that should happen. I made a note of it, thanks for pointing it out =)