@deviant That is another story: for connection to Mastodon #AndStatus uses java.net implementation from Android firmware and _that_ implementation is outdated in Android before v.5.1, as I found out. This is why AndStatus cannot connect to some Mastodon instances on devices with Android v. before v.5...
So upgrade to at least Android 5.1 could help.
@ZeniorXV In order not to reinvent a wheel I suggest to use text reader's notions like "continuous", "one page/message/toot...", " one conversation" etc. reading modes and a way to navigate in that modes:
- in continuous mode we scroll vertically only (as we do now in a timeline);
- in a paged mode we scroll vertically one page (or one conversation...) only and move between pages using horizontal swipe gestures.
@Vavassor @Tusky #Mastodon #UX
@cristomc Actually current design of Pump.io does allow to see in one client instance of #AndStatus information from several accounts on different pump.io hosts as information of ONE federated social network. Basically because pumpio instances provide GUIDs of all objects (users, posts...) to a client application.
Unfortunately neither #GNUSocial nor #Mastodon (developed almost yesterday...) allow this :-(
In server-to-client communication instance-local identifies are used...
@cristomc FYI #AndStatus supports #PumpIo, so it already can communicate using Activities. I expect minor changes to adapt that implementation to what currently #ActivityPub is...
The most interesting part will be communication from a single client application with different ActivityPub implementations as with a single Global Social Network...
@cristomc Please let me know, when your #ActivityPub server instance will be available for testing: my #AndStatus client should be easily adapted for this new protocol. Moreover, it could be used as a server testing tool as it can log json messages to separate files (in addition to normal text logs)
@ZeniorXV I see, thank you for the idea. Currently this can be done in #AndStatus in a generic way: any "(hashtag) Search Timeline" can be made easy visible for selection (in a "context" or globally) , and such timelines can be made syncable automatically, what is equivalent to subscription to hashtags. Currently only ”Account” is considered as a "context" for timelines' filtering. But maybe "Timeline type" (e.g. "Favorites") could also be added as a filtering criterion...
@AndStatus - ah, not exactly, but interesting to know the AndStatus options anyway, thanks.
What I had in mind was simply to be able to go to a hashtag column/view, and mark that "search result" or "hashtag view" as a favorite, so that I get a convenient set of links in my favorites, each to separate hashtag views.
I even forget interesting hashtags if I do not "bookmark" them like this. And I would like to manage such a "bookmarks" list of interesting hashtags right inside the favorites area
@AndStatus Well I started my project in 2011 (but I had to stop public development in 2015), now I'm rebuilding and updating my project for release a new version, using ActivityPub instead my old design.
Now, my project will focused also in offering services as a layer. (ex: my research on mobility on 2014 as a service goo.gl/k5Mggh). I think that federation is a step ahead in social nets and services. That's the reason why I didn't choose joining another project :)