AndStatus on loadaverage.org
This remote profile is registered on another site; see andstatus's original profile page on loadaverage.org.
-
AndStatus (andstatus)'s status on Tuesday, 20-Dec-2016 01:21:09 EST 
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… -
AndStatus (andstatus)'s status on Monday, 19-Dec-2016 01:16:01 EST
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)'s status on Monday, 19-Dec-2016 00:42:54 EST
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)'s status on Saturday, 17-Dec-2016 09:34:17 EST
AndStatus
@maiyannah @verius @yvolk @pedro @bobjonkman @mmn @clacke @xj9 @pedro @takeshitakenji @archaeme @deavmi -
AndStatus (andstatus)'s status on Saturday, 17-Dec-2016 05:50:43 EST
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)'s status on Saturday, 17-Dec-2016 05:34:19 EST
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)'s status on Saturday, 17-Dec-2016 05:23:39 EST
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)'s status on Saturday, 17-Dec-2016 05:06:53 EST
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)'s status on Saturday, 17-Dec-2016 04:45:57 EST
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)'s status on Saturday, 17-Dec-2016 00:50:37 EST
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 bot… -
AndStatus (andstatus)'s status on Friday, 16-Dec-2016 15:09:59 EST
AndStatus
@deavmi I agree, thank you for suggestion. Changed "Open on Internet" to "Open in browser" -
AndStatus (andstatus)'s status on Thursday, 15-Dec-2016 01:03:20 EST
AndStatus
@maiyannah 1. As we are thinking about good interoperability with !gnusocial instances that have old API only, I think we better add "local I'd part" not only to the newly formed "message/notice id", but to other IDs also. So a User UID will be: http://status.hackerposse.com/url/13370 i.e. it will include local user I'd as the third part of the UID 2. Regarding message/notice … -
AndStatus (andstatus)'s status on Tuesday, 13-Dec-2016 14:20:44 EST
AndStatus
@verius Local IDs (long numbers) may or even should be used internally to simplify local database design and improve performance. URIs are for data exchange via APIs ?!
E.g. in AndStatus we use numbers (local ids) as keys for relations between tables...
@maiyannah -
AndStatus (andstatus)'s status on Tuesday, 13-Dec-2016 13:59:50 EST
AndStatus
@maiyannah Thank you, I will definitely take part in discussions and in remote testing using AndStatus client. But currently I don't plan to setup my own server.
My personal email: yvolk1@gmail.com -
AndStatus (andstatus)'s status on Tuesday, 13-Dec-2016 12:39:57 EST
AndStatus
@maiyannah 1. I agree, adding new field into each "object" of the JSON message with UID in addition to each existing ID will be a good compromise preserving compatibility with old clients. 2. Regarding choice of the UID format/structure I strongly support a UID, which allows to identify easily the GNU Social instance that generated the UID. This way clients will be able to requ… -
AndStatus (andstatus)'s status on Tuesday, 13-Dec-2016 00:54:30 EST
AndStatus
@maiyannah 1. Conversations also need Globally unique IDs. They are local numbers also now. I'm currently testing usage of Conversation id to get full conversation in one request instead of "discovering" of previous posts one by one: and I'm really impressed by this feature of the API. 2. Another point of server load optimization: honoring since_id parameter in a search request… -
AndStatus (andstatus)'s status on Monday, 12-Dec-2016 16:11:05 EST
AndStatus
@maiyannah I think that "namespaced by instance" is OK. E.g. user ID: http://status.hackerposse.com/url/6715 message ID: http://status.hackerposse.com/url/6715 The main point is that in order to request the same user or a message from different GNU Social instances, one should use the same Global ID. I.e. the same URL path will be used to request same message from any instance,… -
AndStatus (andstatus)'s status on Monday, 12-Dec-2016 11:09:33 EST
AndStatus
@maiyannah My main wish for GNU Social API improvement is to have URIs (globally unique identifiers) of users and messages everywhere, where now ”local" IDs are used. I see local ids usage as a major deficiency of current API. Which breaks federation (from a client point of view) and provides a small window - one "instance" of the network, via which the whole communication oc… -
AndStatus (andstatus)'s status on Thursday, 08-Dec-2016 11:00:55 EST
AndStatus
@deavmi Please read on duplicated posts here: https://github.com/andstatus/andstatus/issues/83 -
AndStatus (andstatus)'s status on Thursday, 08-Dec-2016 05:12:25 EST
AndStatus
@kevie
There is some problem in secure connection to the server. If cannot figure out the real cause, you can swith AndStatus to insecure SSL connection with this Social Network (goto Settings - > Accounts -> Manage Social Networks - > select this network and change "SSL Mode and security" setting...)
See for similar cases https://github.com/andstatus/andstatus/issues/208
@maiyannah
All Hacker Poesy content and data are available under the 
