Notices by AndStatus (andstatus@loadaverage.org), page 28
-
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 10:27:00 UTC 
AndStatus
@maiyannah The point of view is incorrect, but it doesn't mean that this is a client's error or bug! And this why I proposed an intelligent fix at a server side... -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 08:12:57 UTC
AndStatus
@maiyannah@community.highlandarrow.com I agree, and as I wrote, AndStatus resends only those posts, which were not successfully delivered to the server from the application's point of view. -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 05:57:00 UTC
AndStatus
@maiyannah There could be many reasons, why a client application resends a message, not only its own error ;-)
Another quote from the old discussion:
---
In this case, I guess, we need to decide on the expected behavior of AndStatus first.
My intention is to ensure that messages, posted via AndStatus, will be actually delivered to the server. Hence it is expected that in a case of an error while sending a message, AndStatus will retry sending the message later (up to 10 times for now).
There may be different errors during sending, including errors sending delivery confirmation (actually, synchronous response with a posted message) back from the server to the client resulting in re-sending of the message that was already successfully delivered to the server (because AndStatus doesn't know that the message was successfully delivered). This is a normal situation and it should be handled by communicating systems...
Do you agree so far?
---
@gargron -
harmlessgryphon (harmlessgryphon@sealion.club)'s status on Tuesday, 08-Nov-2016 12:48:09 UTC 
harmlessgryphon
@dwmatiz @andstatus I'd like to see AndStatus automatically jump to the top of the timeline when opened.
I do most of my reading here on the website, so the application gets several weeks behind at times. -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 05:48:03 UTC
AndStatus
@harmlessgryphon "when opened" isn't clear enough. Currently AndStatus stores last viewed position of each timeline in a database i.e. forever. Twidere stores timeline position until Android system or a User kills it, this can be a minute or a day...
I can add an option ”Store timeline position for one user session only" making that ”session" dependent on both actual application loading and on time passed since the timeline was last viewed (position expiration in, say, 2 hours)
?!
@dwmatiz -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Nov-2016 05:35:56 UTC
AndStatus
@maiyannah As written in the above mentioned discussion, I think this behaviour of the server would be much better, even better than Twitter does ;-):
---
Meanwhile I checked how Twitter responses to posting the message ("tweet") with duplicated text. It returns HTTP error "Forbidden", even if the duplicated message is not the last message sent by this user.
It will be far more intelligent to respond not with an error but as a successful sending of that previous message.
Thus a client application (and a User of that application! ) will know that the message it's trying to resend was actually sent earlier. And stop resending!
---
See https://github.com/andstatus/andstatus/issues/83
What do you think?
@gargron -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 08-Nov-2016 20:00:22 UTC
AndStatus
@maiyannah @gargron On duplicated posts please read this discussion: https://github.com/andstatus/andstatus/issues/83 -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 08-Nov-2016 16:17:27 UTC
AndStatus
@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... ?! -
dewoo~ (dwmatiz@sealion.club)'s status on Tuesday, 08-Nov-2016 10:06:57 UTC 
dewoo~
@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. -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 08-Nov-2016 06:01:12 UTC
AndStatus
@dwmatiz What's better there for you personally, except your own Timeline background? -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 07-Nov-2016 16:24:17 UTC
AndStatus
@mcscx Do you mean custom background or something else? -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 06-Nov-2016 11:38:55 UTC
AndStatus
@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? -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 06-Nov-2016 10:45:00 UTC
AndStatus
@markov What Performance test suite do you mean? -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 31-Oct-2016 15:30:04 UTC
AndStatus
@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 -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 30-Oct-2016 20:42:48 UTC
AndStatus
@maiyannah@community.highlandarrow.com I think GNU Social SHOULD change its client API to allow fully use advantages of its federation. Please read this discussion on a new API: https://github.com/andstatus/andstatus/issues/419
@lambadalambda -
AndStatus@Quitter.no (andstatus@quitter.no)'s status on Wednesday, 26-Oct-2016 18:08:45 UTC 
AndStatus@Quitter.no
@tuxxus I'm a developer of AndStatus Android client for GNU social, and looking at your Fediverse map at https://www.fediverse.org I thought that maybe it would be a good idea to allow AndStatus to load information on working GNU Social instances from your site (on a User's request) in order to ease configuration of user accounts in AndStatus.
For about a year I used the service at http://gstools.org/api/get_open_instances for this but it is down for a long time already...
What do you think?
Please see here, how this was done using gstools service: https://github.com/andstatus/andstatus/issues/84
--
Yuri,
AndStatus, http://andstatus.org https://quitter.no/attachment/659813 -
AndStatus@Vinilox (andstatus@status.vinilox.eu)'s status on Wednesday, 26-Oct-2016 04:30:39 UTC 
AndStatus@Vinilox
@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 Volkov
I'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 -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 24-Oct-2016 15:33:20 UTC
AndStatus
@clacke Only logs can tell, why there is no any sign of that attachment :-) -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 23-Oct-2016 19:11:33 UTC
AndStatus
@lasagna We only need to define, how exacly we will do this. Are you ready for the discussion on the design?
@xikufrancesc
All Bobinas P4G content and data are available under the 