Notices by AndStatus (andstatus@loadaverage.org), page 19
-
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 30-Aug-2017 06:20:59 UTC 
AndStatus
@colegota Thank you, I like option 3 the most. In order to increase text legibility I would try to color left part only: the whole space, where avatars are shown?!
@thefaico https://loadaverage.org/attachment/3736533 -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 29-Aug-2017 16:22:35 UTC
AndStatus
@colegota I like this conceptually. E.g. optional colored strip on the left side, below avatars, would work. Similar to existing "reply to me" line, to the right of it?! Are you good in visual design to draw some mock of that? https://loadaverage.org/attachment/3735572 -
Colegota (colegota@quitter.es)'s status on Monday, 28-Aug-2017 07:50:07 UTC 
Colegota
@andstatus just the messages from colegota@quitter.es and cayentana@quitter.no shown in different colors at combined timeline.
Can be a background color, a vertical line in one side...
Over the message it's written the node (Quitter España / Quitter.no...) but it's small and many times I repeat messages with the wrong account.
@thefaico -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 28-Aug-2017 06:27:46 UTC
AndStatus
@colegota Different (instances of ) Social networks could be marked differently in a Timeline. But actions/messages from one instance cannot be easily and fully correctly grouped by account unless these are private messages... simply because any account could retrieve these activities/messages from this instance.
What do _you_ need? -
AndStatus (andstatus@loadaverage.org)'s status on Saturday, 26-Aug-2017 19:27:37 UTC
AndStatus
@megver83 I don't use Tor and don't know how to integrate with it, but you could look at this discussion, maybe you can do this already: https://github.com/andstatus/andstatus/issues/43 -
Cadis Etrama Di Raizel (raizel@niu.moe)'s status on Friday, 25-Aug-2017 13:06:18 UTC 
Cadis Etrama Di Raizel
@andstatus @thefaico Your proposed rebuild of AndStatus will more than make up for anything that I felt was lacking in and would encourage me to start using Pump.io again. Your work and dedication to Andstatus is as admirable as ever, thank you!
-
AndStatus (andstatus@loadaverage.org)'s status on Friday, 25-Aug-2017 06:31:26 UTC
AndStatus
@raizel Which concrete feature are you missing?
Currently I'm rebuilding #AndStatus to support #ActivityStreams as a data model natively. In particular, Notifications / Activities timeline will be introduced to show all incoming Activities (and not messages only as now) in the order they were actually received by this device (and not in the order of dates, when corresponding messages were published or actions occurred). So users (especially having multiple accounts) won't wonder, for example, which "New mentions" were received.
This will immediately make AndStatus much more friendlier to existing Pump.io users, I think.
?! -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 25-Aug-2017 06:15:57 UTC
AndStatus
@ericxdu23 Your device is _so_ popular that it has ready to use builds even for Android 7.
Just lookup it at https://lineageos.org -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 24-Aug-2017 20:01:15 UTC
AndStatus
@xrevan86 Less than 10% for #AndStatus. Maybe because recently incompatibility of Android 4 with some #Mastodon instances was discovered... Do you use such device? -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 24-Aug-2017 17:19:09 UTC
AndStatus
I decided to drop support of Android versions before v.5.0 in the future releases of #AndStatus
This will allow to start cleaning code from outdated solutions and components...
Android v.4 devices currently amount to less than 13% of active devices, which have AndStatus installed, according to Google Play statistics. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 24-Aug-2017 13:33:36 UTC
AndStatus
@6gain During long outage of #loadaverage I diversified my posting instances.
As loadaverage.org is back again I will, at least, reblog using this account my posts from other instances. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 24-Aug-2017 06:55:44 UTC
AndStatus
@takegami If you think that the problem may be at #AndStatus side, please give more info, including Android and AndStatus versions... Also please look into "Commands in a queue"... -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 22-Aug-2017 16:16:24 UTC
AndStatus
@1iceloops123 "critique" is far better for the project and for developer's inspiration than silent uninstall :-)
For #AndStatus news and tips please follow one of my accounts (the list and order of accounts changes over time...):
@andstatus @andstatus @andstatus@quitter.no @andstatus@identi.ca @andstatus1@twitter.com ... -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 17-Aug-2017 17:04:07 UTC
AndStatus
@mmn @sylvhem I guess #Mastodon developers see "entire world" as consisting of controlled/compliant Mastodon instances only :-( -
Yuri Volkov (yvolk@loadaverage.org)'s status on Tuesday, 15-Aug-2017 05:28:33 UTC 
Yuri Volkov
Suggested correction to https://www.w3.org/TR/activitypub/
1. I noticed an inaccuracy in section 6.9. "Undo Activity"
"The undo activity and the activity being undone must both have the same author."
"author" should be changed to "actor" here so it will read:
"The undo activity and the activity being undone must both have the same actor."
2. Actually, the "author" property is used (informally ?!) in examples of this document, but I didn't find _any_ reference to such a "property" in https://www.w3.org/TR/activitystreams-vocabulary/
the latter documents uses "actor" instead.
Looks like autor should be replaced with "actor" in examples also to avoid confusion and incompatible implementations...
?! -
AndStatus@Quitter.no (andstatus@quitter.no)'s status on Monday, 14-Aug-2017 04:32:57 UTC 
AndStatus@Quitter.no
@maiyannah
...
9. Try to authenticate using the same credentials as at the step 3.
Expected result: You are authenticated successfully and see the same JSON as at the step 5.
Actual result: You cannot authenticate even after repeated attempts.
---
I don't have IOS device to test above scenario. Could you try?
PS: I don't see any problem with the site certificate.
@bob@primatemind.info
(part 2 of 2) -
AndStatus@Quitter.no (andstatus@quitter.no)'s status on Monday, 14-Aug-2017 04:25:52 UTC
AndStatus@Quitter.no
@maiyannah Did you call me, the brave User? :-)
As I understand, we are talking about "Basic authentication" at https://community.highlandarrow.com site?!
Just now I made this test from my Windows 10 PC + Google Chrome browser helping to show that the problem is not specific to Android:
1. In tab 1 of the browser navigate to https://community.highlandarrow.com/main/public .
2. Web UI opens.
3. Authenticate yourself, if not authenticated yet.
4. In the tab 2 try to access URL of the Home API:
https://community.highlandarrow.com/api/statuses/home_timeline.json
5. JSON response with social network messages appears without any credentials prompt.
6. Switch to the tab 1 and log off (click your avatar at the top for the log out menu item).
7. Switch to the tab 2 (where you're at https://community.highlandarrow.com/api/statuses/home_timeline.json ) and refresh the page.
8. "Authentication Request" popup opens.
...
@bob
(part 1of 2) -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 11-Aug-2017 18:03:39 UTC
AndStatus
@decripter37 I would recommend to search for an upgrade to your device at https://lineageos.org or https://forum.xda-developers.com/android/software
I personally use #Lineageos 13 - Android 6 - on my 3 years old tablet, and this it like a second life for the device :-) -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 11-Aug-2017 16:10:36 UTC
AndStatus
@decripter37 I noticed that #AndStatus on devices before Android v.5.1 doesn't work with some Mastodon instances due to outdated connection libraries in the firmware... -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 09-Aug-2017 17:02:31 UTC
AndStatus
@xrevan86 Thank you for help with #loadaverage
It's interesting, what was a cause of that PHP problem?
All Chirp! content and data are available under the 
