Notices by AndStatus (andstatus@loadaverage.org), page 16
-
AndStatus (andstatus@loadaverage.org)'s status on Friday, 13-Oct-2017 05:42:22 UTC 
AndStatus
@regentaenzer 1. When #AndStatus crashes, special (#ACRA) module intercepts the crash and opens a pop-up dialog, allowing a User to send a Crash Report to a Developer via email. See a screenshot in this issue for example: https://github.com/andstatus/andstatus/issues/272
2. I want to find out, what caused a crash in your case, but information that you provided is not enough to be sure that I'm doing exactly what you did, when you encountered the crash. Please note that there are thousands of AndStatus users, and I didn't receive similar reports for a long time. So can you figure out that what you _exactly_ do, or maybe your phone, are quite unusual.
The best way to solve the problem is to start with creating a new issue at https://github.com/andstatus/andstatus/issues attaching screenshot(s) and writing exact steps to reproduce the crash, please. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 12-Oct-2017 18:15:56 UTC
AndStatus
@regentaenzer Could you send me Crash report? -
Yuri Volkov (yvolk@loadaverage.org)'s status on Thursday, 12-Oct-2017 06:57:54 UTC 
Yuri Volkov
@cwebber@octodon.social Thank you for reply to the #ActivityPub issue at https://github.com/w3c/activitypub/issues/260
I followed the discussion there plus copying my follow-up below:
1. Let's go step by step. Explicitly stating that Actors and Users are different entities is a good way forward.
BTW the confusing phrase "users are represented as "actors" here" should also be changed to "users are mapped to actors" with addition, how (you suggested wording...)
Where can we see current draft for review how it looks now? You are too quick to state that the issue is resolved :-)
2. Let's check if the statement is valid:
* ""user" is technically an entity outside the protocol"
2.1 First of all the term is used tens times in the document, which describes the protocol: https://www.w3.org/TR/activitypub/
2.2. The term "user" is used for two different things, actually:
* for "natural person from a real world"
* and for "user's account at a Servetr" (my interpretation).
The second meaning is definitely "inside protocol". Just look at these phrases, from many available, for example:
* "This protocol permits a client to act on behalf of a user."
* "Client to server interaction takes place through clients posting Activities to a user's outbox"
My conclusion is that a User in the second meaning "user's account at a Server" is definitely a part of the protocol description.
3. As now we agreed on separation of an Actor from a User, let's look again, what we read in the document.
3.1 You know: there are many places, where the word user(s) should be replaced with a word Actor(s), e.g. here {again, one of many examples):
* "The Follow activity is used to subscribe to the activities of another user."
Attributes of a User are presented as attributes of an Actor in examples... -
Yuri Volkov (yvolk@loadaverage.org)'s status on Monday, 09-Oct-2017 05:48:29 UTC
Yuri Volkov
@mike@macgirvin.com I agree that #ActivityStreams2 is well designed. Maybe this is exactly because its ideas are actively tested in practice for several years in pump.io. Confusion of Actors and Users of servers in the #ActivityPub I regard as a conceptual mistake that should be fixed _now_. So I proposed concrete additions to the spec in this issue: https://github.com/w3c/activitypub/issues/260
Not many responses so far :-( -
Mike Macgirvin (mike@macgirvin.com)'s status on Wednesday, 04-Oct-2017 23:06:09 UTC 
Mike Macgirvin
@andstatus At the present time there is no alternative which can possibly unite the free web. The only way I can see to move forward is for projects to support multiple protocols into the foreseeable future.
There are some interesting developments in the works. Unlike ActivityPub, I believe that discussing any alternatives before there are solid specifications and tested implementations would be foolish.
I will note that the basis for ActivityPub is ActivityStreams2, which is a well designed and extensible specification. It is however merely a serialisation and not a transfer protocol. If you paired ActivityStreams2 with a solid transport protocol you would have something useful. So supporting ActivityStreams2 is still a good idea. Unfortunately, ActivityPub frequently confuses data and transport and puts a lot of additional constraints on the data which aren't present in AS2. Keeping the AP data restrictions separated from the lower AS2 data layer so that the transport layer can be cleanly replaced is a bit of a challenge. -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 05-Oct-2017 03:33:08 UTC
AndStatus
@zoowar This is exactly what I propose in this #ActivityPub specification bug report: https://github.com/w3c/activitypub/issues/260
Separation of Actors (e.g. a Person) from Users of servers (user accounts) even on a conceptual (domain model level). Please support this fix!
@mike @cwebber -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 04-Oct-2017 20:28:37 UTC
AndStatus
@mike@macgirvin.com What do you this is a better alternative to #ActivityPub? Or maybe something concrete could be changed in its current version to make it better? -
AndStatus@Mastodon (andstatus@mastodon.social)'s status on Monday, 02-Oct-2017 06:46:55 UTC 
AndStatus@Mastodon
@FuzboleroXV 1. #AndStatus allows you to see messages from all Social Networks even in one timeline.
2. You can respond to a message as any of your accounts of _the same Social Network_.
For Pump.io, accounts in all instances belong to the Single Social network. For Mastodon - only accounts on the same instance: because of outdated client API. More details +discussion with @Gargron here:
https://github.com/andstatus/andstatus/issues/419
@infO_Overlord -
Yuri Volkov (yvolk@loadaverage.org)'s status on Sunday, 01-Oct-2017 05:04:45 UTC
Yuri Volkov
I filed a bug for #ActivityPub, which is exactly about Person's freedom to choose (and actually, change) an instance/server of a global social network without loosing his/her identity, including historical data.
Moving from one instance of a federation to another is a normal case, just like having user accounts at several servers. And #ActivityPub specification should explicitly allow this.
See https://github.com/w3c/activitypub/issues/260
@fuzboleroxv @citizenphnix
@cwebber @gargron @deadsuperhero @mmn @lnxw48a1 -
Christine Lemmer-Webber (cwebber@octodon.social)'s status on Wednesday, 27-Sep-2017 13:04:10 UTC 
Christine Lemmer-Webber
@yvolk @clacke That's from the tutorial and afaict it's not incorrect, just simplified. Users are actors; left unsaid is that other things can be actors too. (It also didn't say users can't have multiple actors.) The reason it isn't said is to try to reduce the "asides" used in the overview/tutorial, which is trying to allow newcomers to become as familiar with concepts as fast as possible while remaining correct.
I believe this is "technically correct, which is the best kind of correct" ;)
-
Yuri Volkov (yvolk@loadaverage.org)'s status on Friday, 29-Sep-2017 06:00:09 UTC
Yuri Volkov
@cwebber Reposting to make sure you received my reply. Where should I file this #ActivityPub issue?
The #ActivityPub spec's problem is not in that simplistic phrase "users are represented as actors here".
The problem is that there is NO technical description of the whole domain model layer: relation between Actors (e.g. Person) and Users of servers. Current version will be interpreted as having one-to-one relation between the two _different_ kinds of entities, and that _is_ incorrect
?!
My first post on this subject was:
Contemplating on correct implementation of a data model, corresponding to the #ActivityPub specification, I started to realize that current version of the document https://www.w3.org/TR/activitypub has a gap/confusion of two different notions: Person (one of Actor types, see https://www.w3.org/TR/activitystreams-vocabulary/#dfn-person ) and a User of a server (quote from ActivityPub spec: "users are represented as "actors" here")
Actually these are very different notions: a Person may be represented as more than one User, on different servers. And a User may represent not a Person, but e.g. an Organization.
?!
@clacke -
Yuri Volkov (yvolk@mastodon.social)'s status on Thursday, 28-Sep-2017 06:10:33 UTC 
Yuri Volkov
@cwebber The #ActivityPub spec's problem is not in that simplistic phrase "users are represented as actors here".
The problem is that there is NO technical description of the whole domain model layer: relation between Actors (e.g. Person) and Users of servers. Current version will be interpreted as having one-to-one relation between the two _different_ kinds of entities, and that _is_ incorrect
?! -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 25-Sep-2017 05:57:47 UTC
AndStatus
@hakui This means that you better set sync period to 2 hours in order not to loose messages. Concrete value of the sync frequency depends on a number of new messages in your timeline and on a server settings... -
AndStatus (andstatus@loadaverage.org)'s status on Friday, 22-Sep-2017 05:32:28 UTC
AndStatus
@bl4n Please check AndStatus settungs -> Storage -> History Time / Size. Maybe old messages were purged automatically after three days?! Increase the History Time...
To force re-reading of a timeline, go to Manage Timelines, find the Timeline and select "Forget sync events and dates" in its context menu. -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 19-Sep-2017 07:08:17 UTC
AndStatus
@johnnynull Turn them off for now and use context menu.
I need to redo them... -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 19-Sep-2017 06:55:24 UTC
AndStatus
@johnnynull I think you need to read this FAQ on syncing in #AndStatus https://github.com/andstatus/andstatus/issues/295 -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 18-Sep-2017 07:00:49 UTC
AndStatus
@lnxw48a1 You could try: 1. Set your desired non-combined timeline as a Default one (in Manage Timelines)
2. Open #AndStatus via its shortcut, not via its Widget or a Notification. That way the Default timeline will be opened. -
Hallå Kitteh (clacke@social.heldscal.la)'s status on Saturday, 18-Mar-2017 21:48:12 UTC 
Hallå Kitteh
@sonyam pump.io has private messaging, followers-only posting, federated identity so you can run around on other servers and comment using your home id, the API is lightweight and very consistent and understandable in comparison with GS+Qvitter (I hear), and it's the basis for the Next Big Thing, #activitypub.
pump.io was built in a few months by one guy though, and GS was built in a couple of years by several full-time people, so there are still quirks in the (actually intentionally) limited web UI. pump.io works best with a client.
@andstatus does a decent job. I'm not going to complain, because I still didn't file those bugs since last I complained, so the buck is with me. It's mostly about message formatting, other than that it's an awesome client for both GS and pump. -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 11-Sep-2017 13:55:09 UTC
AndStatus
@kris Settings -> Attachments -> turn off "Download attachments over WiFi only" -
AndStatus (andstatus@loadaverage.org)'s status on Monday, 04-Sep-2017 08:32:13 UTC
AndStatus
@itsumonotakumi First of all, #AndStatus has FAQ, which allows to search for answers and to ask new questions: https://github.com/andstatus/andstatus/wiki/FAQ
The change log lists features, added during the last six years, with links to detailed descriptions in corresponding development tickets: http://andstatus.org/changelog.html
Regarding concrete features, which are marked as missed. Just from the top of my mind:
1. Drafts: You can "Save draft" during editing (see a diskette icon above with this tooltip). Plus, AndStatus has "Drafts timeline" whist lists all drafts chronologically like in any email application. Any draft can be edited or discarded, naturally.
How this could be overlooked, if you specifically searched for this feature?
2. Timeline filters. There is more than one way to have filtered timeline:
2.1 Search for one or several words. Resulted filtered timeline can be even made syncable! (see Manage timelines menu item)
2.2. See "Filters" section in Settings.
Do you think that an interested User won't notice any of these ways to filter a Timeline?
... https://loadaverage.org/attachment/3744263
All Bobinas P4G content and data are available under the 