@dwmatiz Thank you for the feedback. It's a pity that you didn't decide to hep by raising issues at https://github.com/andstatus/andstatus/issues and testing the fixes :-( Regarding your notes on problems: 1. Sync on pulling timeline down works only if the "Top” downloaded timeline item is already shown. In other case another newer "page of messages” is being loaded from the local cache. Of course something can be improved here, but focused discussion is needed on how exactly this should work in all cases... 2. I just successfully reposted your reply from the Conversation view. It looks like ”repost icon/button" wasn't updated though... 3. If you don't like vertical lines in the Conversation view (this is actually, an image, which can be changed...) please provide its better alternative or simply turn off ”Show threads of a conversation” option via a Navigation drawer. 4. Regarding long threads: yes, special Conversation API is not used yet to retrieve entire conversation. So AndStatus retrieve related messages from a server one-by-one. In todo... https://github.com/andstatus/andstatus/issues/328 5. Multiple attachments are not supported yet. This is in the queue: https://github.com/andstatus/andstatus/issues/189 I didn't think that this is a priority task... ?!
@andstatus The general comfort of use. In Twidere I can scroll up, and it automatically syncs and updates the timeline. In AndStatus scrolling up only seems to update the timeline after either an automatic or manual sync. The way it actually does it still puzzles me.
Each new update brings a lot of fixes and improvements, but it also tends to break something else, at least on my end. I haven't been able to favourite and repost notices ever since the last one, and the favourite and repost buttons on the new conversation view don't even work at all. Before you ask: doing it from the context menu doesn't work either.
Speaking of conversations, AndStatus seems to struggle when it comes fetching notices from (long) threads. I either have to constantly refresh the thread or hunt down individual posts on my timeline to have it display the whole conversation in its entirety.
The threaded view for conversations still remains a mess. Pixel-wide lines don't look elegant, and the needless padding around them only takes up valuable space.
AndStatus has also been struggling with multiple attachments. In past versions it would display a notice multiple times with a different attachment, but now it just picks one at random. Sometimes it also adds a lot of padding around attachments, which usually disappears after refreshing the timeline.
Sorry, I know AndStatus is pretty much a one-man operation, but after months of using it I've simply grown tired of its quirks.
@gargron @dwmatiz I see that the bot combines parts of similar/related messages to create its own message. This should be a scientific project?! :-) Do you know if the bot is evolving, becomes smarter?
@maiyannah I think it would be overkill for us to invent some completely new API. From this position I see two main ways of current API improvement, and we can go both ways, implementing them separately: 1. Improvement of "Twitter” compatible API. The change that I propose is easily described and it may seem not that deep, but for some reason even @gargron, who, as I thought, is building a new API now, took a long pause on it: in ALL API calls get rid of ALL "local IDs" (IDs of people, messages etc...), replacing them with URIs, which are the same for the same identifiable things (i.e. for the same objects) in all GNU Social instances. This requirement is easy to implement, if an URI: 1.1. Contains unique hostname of the GNU Social instance. 1.2. Contains type of the identifiable object, e.g. ”acct:andstatus@loadaverage.org” - for an "account" ("person"), like in Pump.io. The hard part of this change is that it requires changes in request parameters and (or) in data returned of all API calls. I mean we should go through all API calls and replace all local IDs with URIs, which I suspect not always exist in GNU Social for some objects... 2. Complete and document an API, based on Activity Streams and JSON format. As @mmn wrote me, Activity Streams + JSON are already implemented in GNU Social. But absence of documentation and working examples is a blocker here. This could be the second step of changes... @lambadalambda @pennyfortheguy @mcscx
@aegirs These servers are there historically. Today I see that the list of servers is much longer: http://skilledtests.com/wiki/List_of_Independent_GNU_social_Instances The problem is that previously working GNU Social instances' discovery service stopped working, and you will need to configure new servers manually in AndStatus...
Yuri Volkov (yvolk@loadaverage.org)'s status on Monday, 24-Oct-2016 18:15:30 UTC
Yuri VolkovI'm beginning to rediscover Pump.io After the report https://github.com/andstatus/andstatus/issues/425 by clacke@microca.st I realised that due to some error in identi.ca I stopped receiving messages from the people, that I follow, at least 6 months ago. Instead, I was receiving messages by some other person, whom I didn't follow (the same in my Timeline of AndStatus and at the identi.ca web site). After re-following all of my Friends, I started to get something interesting, at last. Although not many new posts are created on Monday :-) And you know, I received two posts from another unknown person :-) This time I decided to figure out, why I see these posts and it appeared that these posts were "favorited" by one of my friends. AndStatus, unfortunately, doesn't show me this reason like it shows "shared" (reblogged/retweeted) posts. And it came to me that AndStatus really needs to show that the post is shown, because it is "liked/favorited". The same way as reblogs are shown, only starting with the "heart" 💛 icon. ?! -- yvolk@identi.ca URL: https://identi.ca/yvolk/note/LSYanK2vTlGiwSuem4eF9Q
@hikerus Freezing on loading a Timeline page may mean that there is some problem accessing the AndStatus local database. In _my_ local database I have almost 200000 messages, yet I don't see such freezes... Maybe you could try to move your database to internal storage to improve access time?! (see Settings-> Storage)
@hikerus I meant that after update of AndStatus it could start syncing just when You started to use it. Hence bad responding sometimes... This can mean that your device is not good at multitasking. I would recommend you turning off "Sync while using AndStatus“ Regarding your question on "Don't sync old messages.." it clearly says "hours ago", see the screenshot. Maybe translation improvement is needed at https://crowdin.com/project/andstatus ?! https://loadaverage.org/attachment/3274648
@hikerus How much time passed since you updated the application? I mean, maybe this is temporary event due to some heavy background downloading?! BTW, do you have automatic sync turned on?
@lasagna Maybe in the Home combined timeline we could mark somehow, for which account each message was downloaded?! Some of messages can be downloaded by both accounts...
@5n1pp3r5 Please don't turn automatic syncing off for AndStatus. Far better is to set "Default syncing frequency ” to several hours to avoid high load of the device and your waiting, when you start using it @mcscx