@megver83 Before v.35 #AndStatus used #Android provided search tools, which decided themselves, what to search and for how long.
In order to make search interface more flexible and powerful, starting from v.35 (in Beta now https://github.com/andstatus/andstatus/issues/456 ) AndStatus stores Message search history in Timelines only. Go to Manage Timelines and remove all unneeded Search timelines.
Users search queries are stored for current Application run, i.e. in device memory only.
#AndStatus v.35.03 brings User autocompletion during message composing and Users search. Local search works for all social networks, Users search in the Internet is supported for #Mastodon and #Twitter
Currenly in Beta https://github.com/andstatus/andstatus/issues/456 https://gnusocial.no/attachment/581244
@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.
My phone only reacts to jabber, SMS and phone calls. Each new service, even once as nifty as #Mastodon, straddles that line between useful and annoying. ^_^
@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...