Does anyone use #Andstatus? how do I get to recognize my instance?

is actively developed. Recent changes were driven by support. And this helped finding bugs, which affected all Social networks.
The latest production version is 33.08

@auracaletec #AndStatus allows to move to "External storage" its data, including downloaded messages.
AndStatus Settings -> Storage -> External storage
For some reason I wasn't alerted for this thread. Even after I refreshed the mentions timeline. #AndStatus error maybe? Anyway, hello there, doggie! Welcome to the !fediverse.

The reason I followed you back immediately here is because I have it set up to follow back anyone that follows me, like a bot, because I don't check this account very often. Matter of fact, I post here mainly when I want to longpost or describe in detail something that @kzimmermann can't do in just 140c.

Actually, not many accounts will behave this way, though, as it's not the default, and there's even an option *not* to be followed at all (probably to avoid problems with stalking, I guess?) So do not worry, most people will probably not be autofollowing you back if you find that annoying.

Hope that clears it up!
@deadsuperhero Inspiring news! Glad that I noticed them at least now :-)
I didn't think #ActivityPub adoption campaign could be so active :-)
Just this weekend I started to refactor internal data model of #AndStatus from "messages"/"users" with some "favorited", "followed" etc. attributes to "activities" with actors and actions... I'm trying to use terminology of ActivityPub/ActivityStreams as much as possible in order to make application's code more transparent...
@maiyannah @cwebber @bob
#AndStatus v.33.08 is available for beta testing at
1. First of all: simplified creation of a new Social Network for #Mastodon and #GNUSocial users.
2. "Favorites" timeline is now syncable for all types of social networks. It's set to be synced automatically by default for new installations. If you upgraded existing installation, you will need to go to the "Manage Timelines" menu item in the Timeline action bar and set "Sync" flag for "Favorites" timelines of all accounts.
3. Fixed syncing and showing of "Friends" and "Followers" timelines. Please try them!
4. Accuracy of the "Relative time" (... ago) increased. Now you will see "... minutes ago" up to 2 hours, then  "... hours ago" up to 2 days, then "... days ago" up to three months and then - any number of "months ago". So no more "more than a year ago" for all old messages.
5. The first fix for: Occasionally message context menu doesn't work.

And here is how that old discussion on term looks like now in
(I like the dark theme although light theme is a default one now...)

@maloki It's interesting that a couple of years ago we discussed a generic term for our networks (including and ), and that time I came to conclusion that "Social network" is far better term than "Microblogging". Interesting discussion:
Tip: application can store messages for years, this is why I easily found that conversation ;-)

@KARiley40 Try
Maybe it's not as pretty looking as others, but it will allow you to try other Social networks also, and it works offline...
You can even use it as a tool to explore Social networks, joining Search query results from all networks in a single view....

@dragnucs Yes, we even discussed with them format of that tags in order to simplify the automated #f-droid process. And it works somehow, as you see. But for some reason it takes several days for F-droid to produce new build after the tag creation.
E.g #AndStatus v.33.04 was added to F-Droid repository on May 15 - four days after creation of corresponding tag 33.04-release.
I think this is because their automated build process failed and needed some manual fix after some changes in the source code (e.g. after Gradle plugin update...)
@nestort @megver83

@ilpianista v.33.07 has far better support of and it includes important fix for sending attachments in and

@andstatus did have the same issue again. And sorry but I forgot to enable logs so my logs directory was empty.

This time I configured #andstatus to work only by Wifi, and yesterday did noted a high battery usage so I checked data use by wifi and Andstatus did waste almost 1Gb while usually it's a bunch of Mb daily.

The problem seems to be caused because my node was not responding and I believe that last time I have the same problem was down again.
@colegota Please set logging level to VERBOSE.
What I cannot understand is: what data is being transferred? I mean if a server is down, it doesn't respond. By default, in #AndStatus failed commands are repeated not more than 10 times, and not less than after several minutes after previous attempt...
@musicman I also noticed that sometimes older messages are being downloaded after newer. Maybe I observe this, because I use several accounts so sometimes I receive the same messages via different channels in different times. As you may have noticed, #AndStatus collapses duplicated posts in one, so sometimes "new" messages are even not shown, they only add "+1" to an existing message's footer...

Does any user like application?
I understand that its interface is not "for millions" :-) (e.g. no "Wizard" to add not preconfigured Mastodon instance) but it really has its values?!

@punk That GNU Social client's protocol is usually called "Twitter compatible" (old Twitter REST API v.1.0) ?!
But I'm pleased that #AndStatus becomes a common noun :-)
@hector Thank you very much for the report! It's really a please to receive reports about real bugs :-)
I will look at this in 12 hours, so you have time to find some more bugs to be fixed today :-)
Please note that the latest production version of #AndStatus is 33.07.
Yesterday I was implementing #Mastodon API in #AndStatus. Comparing AndStatus with #Tusky client at some point I noticed that Tusky shows me a new post, which mentions myself. But I couldn't find the same post in any timeline that AndStatus feeds from the Mastodon server.
It appeared that in addition to Twitter/GNU Social-like timelines Mastodon has something conceptually similar to an "Activity stream" that is called "Notifications" here and, as other parts of the API, is "hand made" :-)
Actually, this is a good sign, showing that ideas of #ActivityStreams (currently represented by the #ActivityPub standard ) are growing in the heads of the Mastodon developers. I would go one step further and formulate all timelines and actions as activities and activity streams...
It's interesting that these ideas are growing in _my_ head also :-) - I decided that internal AndStatus model of notifications will be based on ActivityStreams too. I.e. each individual notification will have an Actor, an Action and an Object/Content e.g. "Peter posted 'I met a friend'". Having notifications in such a structure, we will be able to show them to a User in any needed form: in the Android Notification bar or as a timeline.
Currently AndStatus shows mostly "mentions" only in its "Mentions" timeline...