@aldobelus I know about problems with #notifications, please read my reply to you 5 days ago about my own investigation of possible causes, including about "there is nothing new". Unfortunately, due to the Twitter-like approach in a server to client communication taken by GNU Social many years ago and even by Mastodon recently, notes and activities that look the same for a human eye, are represented as different by each server. This is the main cause of users' confusions seeing notifications about the same activities. Hoping that the networks will eventually implement #ActivityPub "client to server layer" spec that resolves this deficiency, I plan to improve Notifications in #AndStatus even in the presence of such unavoidable duplicates... And another note: Looking for Notifications improvements, please make sure that you have AndStatus v.43.02 installed, see https://github.com/andstatus/andstatus/issues/456
@autogestion A month or two ago I visited the https://test.activitypub.rocks site and at last found out, which exactly features are REQUIRED for a client app to formally declare its support of #ActivityPub. I've added "Client discovers the URL of a user's outbox from their profile" already, working on other features. What's most important is that internal data model of #AndStatus is already compatible with #ActivityPub, I hope :-) The only hard part to implement is compatible OAUTH (AndStatus supports two variants of OAuth, but it looks like I will need the third for ActivityPub...) After completion of the REQUIRED features I will create the new "ActivityPub" Social Network Type (in addition to the three existing) and will start actual testing... Unfortunately, I don't see any working _real_ (not a toy) server with Client to Server layer support, where I could register as a user and test my client app ;-( ?!