@silverwizard Different "Types of Social Networks" in #AndStatus correspond to different client APIs. Friendica's client API was adapted to be compatible with #GNUSocial specifically to be able to use client applications, which work with GNU Social.
@silverwizard wrote: "AndStatus is an Android app for OStatus clients" This is wrong. #OStatus is a server-to-server protocol, #AndStatus connects to servers using server-to-client protocols. This is why AndStatus doesn't know and doesn't depend on OStatus protocol. Moreover, #Mastodon 's client-to-server protocol is still based on outdated Twitter like API, not on #ActivityPub, unfortunately. @jackyalcine
@jark Reviewing and improving #ActivityPub specification is not about coding/programming. It's about analysis and modeling. But my experience shows that it's hard to notice problems and mistakes in such documents, until you don't try to start actually using it in practise, in this case - starting to implement some application using this specification OR starting to adapt this specification, as an Analyst, for some concrete application. This way you will read every phrase, some of them - many times... @mike @verius @clacke @cwebber
@regentaenzer Yes, please test again. By the way, you can create a backup of #AndStatus data, including accounts (but without images) in Settings -> Storage, then reinstall AndStatus and do any tests, and after all your tests reinstall again and Restore that backup on the first launch of AndStatus. This is why I personally still use the same AndStatus's database that I created several years ago: I restore the last backup in a case of problems...
@regentaenzer I added "quit.im" Social network to #AndStatus by typing just "quit.im" and pressing Add button. Then I tried to add an account to that Social network not han having correct credentials: I got "401 Unathorized" error message, as expected. Then I registered at quit.im and tried to add this new account: it was successfully added, no freezing or restarts. So I couldn't reproduce the problem, unfortunately. https://loadaverage.org/attachment/3821325
@regentaenzer Could you send to me: Social network type + exact URL, which caused the crash. Screenshot will be ideal (URL sent via servers as a text string can be altered...)
@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.
@cwebber@octodon.social The same for me: Only implementing now domain model of #ActivityPub /#ActivityStreams in my #AndStatus application I became deep enough aware of the specs' advantages and shortcomings... so I initiated another round of the spec fixes. Sorry that not months ago... @bea @teascade @neon
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...
@sonyampump.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.
@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
@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
@itsumonotakumi This comparison could be interesting if it was more accurate. I cannot tell about other apps, but seeing lots of incorrect values for AndStatus I cannot trust the whole table :-( Suggestion for the author: please put "?" instead of "Y" or "N" if you are unsure...
@fuzboleroxv I think that Pump.io solved the problem with non-synchronized remote User's info/messages the best: instead of loading network with synchronization of questionable importance, its API allows client application to go directly to the User's instance and grab any interesting (publicly available) data from the "golden source". This approach guarantees that you will see all User's public posts etc. Pump.io clients, including #AndStatus, can do this for years, because this is natural and simple ;-) @vavassor @gargron