Notices by AndStatus (andstatus@loadaverage.org), page 27
-
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 14-Jan-2017 19:47:46 UTC 
AndStatus
@denommus No. Which exactly notice has this problem? (URL please) -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 12-Jan-2017 16:06:16 UTC
AndStatus
AndStatus v.31.02 "Conversation view and Search enhancements” is available in f-droid https://f-droid.org/repository/browse/?fdfilter=AndStatus&fdid=org.andstatus.app&fdpage=1 , in addition to Google Play.
See the Change log: http://andstatus.org/changelog.html -
dalme (dalme@lactomeda.tk)'s status on Thursday, 05-Jan-2017 17:45:18 UTC 
dalme
GnuSocial Clients:
For desktop:
- Gwibber http://gwibber.com/ (GTK)
- Choqok http://choqok.gnufolks.org/ (Qt)
For shell:
- GnuSocialShell (coded by me): http://gnusocialshell.amayaos.com/
- Identicurse https://github.com/identicurse/IdentiCurse
- Gitn http://linuxinthenight.com/ (By @fanta )
For Android:
- AndStatus: http://andstatus.org/
Of course there are a lot of clients: http://wiki.gnusocial.net/doku.php?id=clientes_de_gnusocial
cc/ @alijee -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 08-Jan-2017 09:42:54 UTC
AndStatus
@6gain See the FAQ on sync issues: https://github.com/andstatus/andstatus/issues/295 -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 04-Jan-2017 10:24:44 UTC
AndStatus
@herrgnatz One correction: the latest AndStatus version is 31.02 (available at https://play.google.com/store/apps/details?id=org.andstatus.app). It has some improvements of the Conversation view, see http://andstatus.org/changelog.html
Unfortunately, it looks like I didn't inform f-droid on this release, will fix this next week, when I return from vacations.
Currently greetings from Flores island, Indonesia. https://loadaverage.org/attachment/3382023 -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 04-Jan-2017 09:50:20 UTC
AndStatus
@herrgnatz I don't see any duplicates in your posts at https://github.com/andstatus/andstatus/issues
Did you delete them? The clue on duplication is here: https://github.com/andstatus/andstatus/issues/83
Regarding Conversation view please start with upgrading to !AndStatus v.30.02 https://loadaverage.org/attachment/3381994 -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 23-Dec-2016 05:30:37 UTC
AndStatus
@skpacman Of cause, constructive criticism is better :-)
Please look up known problems, solutions and ideas at the "Issues" page: https://github.com/andstatus/andstatus/issues
And join discussions, which are interesting for you. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 22-Dec-2016 20:08:30 UTC
AndStatus
@potter You can see AndStatus change log here: http://andstatus.org/changelog.html -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 22-Dec-2016 05:55:15 UTC
AndStatus
@skpacman We need something more concrete to make AndStatus better. Could think of any simple thing(s) to start with in that direction? -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 21-Dec-2016 17:37:15 UTC
AndStatus
@japananon I like that you already got acquainted with a Command queue of AndStatus :-)
Regarding duplicated posts: this is an effect of the "guaranteed message delivery" from AndStatus side and "duplication problem ignorance" from the GNU Social server side. More on this here: https://github.com/andstatus/andstatus/issues/83 -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 20-Dec-2016 06:21:09 UTC
AndStatus
@6gain We do have "Messages by someuser@somehost" menu item in the context menu. So you can see messages, posted and reposted by a User that you found in any other timeline. This works even for users, mentioned in a message: select "Users of message" menu item, see a list of users, and then select "Messages by ..." in the context menu of that User.
Unfortunately, due to current !gnusocial restrictions, it is not possible to request full user's Timeline from a server for a Remote User (not implemented on a server side). In this case in AndStatus you will see only messages by this user that were downloaded earlier in other ways (e.g. as parts of some conversations...)
There is no separate interface to search for a user. The simplest way is to find his message by his username (where he is an author or is mentioned/replied to) and then goto "Messages by thisUser” https://loadaverage.org/attachment/3361396 -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 19-Dec-2016 06:16:01 UTC
AndStatus
@takeshitakenji In addition to that, in v.31.02 (now in Beta testing), as @archaeme@gs.archaeme.tech suggested, users who only favorited something in the conversation, are not included in the list, created by ”Reply to conversation participants".
@theru @vinzv -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 19-Dec-2016 05:42:54 UTC
AndStatus
@hikerus I feel that smaller buttons will be harder to click. But if you like to see more information on a screen my advice is to hide the whole Button bar completely: message context menu gives you much more options anyway.
Turn it off in AndStatus Settings -> Timeline -> "Show Reply, Repost and Favorite buttons below message" https://loadaverage.org/attachment/3359685 -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 10:50:43 UTC
AndStatus
@verius Having a Message URI generated by a Client application allows to avoid any message body comparisons. For the case, when this is not an intentional duplication/spam. But spam is another topic, out of scope of this conversation.
@maiyannah -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 10:34:19 UTC
AndStatus
@takeshitakenji Implemented in AndStatus v.31.01: one existing "Reply to all” action is replaced with two, to avoid confusion: ”Reply to all conversation participants" (what we actually had before) and "Reply to all mentioned users”.
@theru @vinzv @archaeme@gs.archaeme.tech https://loadaverage.org/attachment/3357546 -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 10:23:39 UTC
AndStatus
@maiyannah I would say that the best response to posting of a duplicated message will include that existing message object, which the new message duplicates. So the client app will know for sure that the message was successfully sent already and will have that sent message without additional requests.
@verius @thefaico -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 10:06:53 UTC
AndStatus
@verius As @maiyannah explained, currently I'm proposing a new point of message UID/URI creation to help solving a problem of sending duplicated messages from a client to a server.
Message URI is exactly that field that can be universally used for deduplication in different cases. Including deduplication of messages that a client application received from different fediverse instances (using different accounts). -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 09:45:57 UTC
AndStatus
@mmn No problem with "opaque" URIs. They simply won't be parsed and hence will be useless for discovery of the !fediverse. Old clients/servers won't parse any URIs anyway.
Actually we are discussing future client API for GNU Social that @maiyannah is planning to implement. I'm referring to Twitter-compatible API only for comparison.
@verius -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 17-Dec-2016 05:50:37 UTC
AndStatus
@maiyannah Regarding unique Message IDs and global messages' identification/matching/reduplication.
It came to me that the root of messages duplication problem that we are periodically discussing, lies in the message ID generation at a server side. This is why messages, which were not posted yet from a client to a server, cannot be easily identified: they have to be matched both by a Sender and by their body. This causes, in particular, duplicated messages.
I think that as we are discussing new client-server API, we should improve this also: Globally unique message ID should be generated at its actual creation point: in a client application (whether it is a Web client or a mobile device client...)
This means that Message UID should include not GNU Social instance UID, but a User account UID AND User device ID - the latter has not to beglobally unique:
User's Device - unique for this Account.
My account UID at loadaverage could be "acct:andstatus@loadaverage.org:5263" (see my previous post)
Thus, messages, posted from my "andstatus" account using mobile device "d1" will be automatically assigned (by that "d1" device) such IDs:
msg:17625@d1@andstatus@loadaverage.org:5263
The first number "176625" is local ID of the Client, which created this message
next device ID goes: "d1"
and the full User UID is appended (without "acct:")
As you can see, in this my message UID proposal "local ID of this GNU Social instance" is not included in the message UID. This allows both a Client and a server identify duplicated posts easily AND interpret repeated sending of a message with the same UID as e.g. a change/editing of the message (if a server supports such an action) or simply ignore the duplicate.
Main point of this post are parts, comprising the Message ID, and a point of its creation. Not the exact format of the UID.
?!
@archaeme @verius @mmn -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 16-Dec-2016 20:09:59 UTC
AndStatus
@deavmi I agree, thank you for suggestion. Changed "Open on Internet" to "Open in browser"
All Chirp! content and data are available under the 
