@tom79 Notifications in #AndStatus may actually originate from any downloaded note, from any timeline. The application then decides if any given note is deserved to be notified about (according to user's settings...) I think that the key difference here between AndStatus and #Mastalab is that AndStatus downloads and analyses _all_ timelines in a background beforehand. All timelines are ready for reading even without Internet connection. Mastalab downloads only a small portion thus having less data to think about. And it requires Internet connection when you click on a notification: you will see nothing without Internet. @up201705417@loadaverage.org I like your words "competent in notifying me", thank you :-) @lnxw48a1 @colegotahttps://loadaverage.org/attachment/4987331
Okay, just read about what Mastalab is and you definitely shouldn't be using qvitter API given that some instances (like the one I'm using) don't have that plugin installed.
About getting notifications, I've been using @andstatus and it is very competent in notifying me, so I guess maybe that app developer might be able to provide you with the required guidance. Or you can just look for the bit of code handling that on AndStatus, it is FLOSS :)
@AndStatus Thanks for the confirmation. I was surprised, but now it's work well. I will keep working on #GNUSocial I notice that there are a lot of features that I will have to disable. For endpoints, they all respect same parameters described in Twitter api?
@tom79 Yes, you can use Basic authentication with #GNUSocial (username + password). Several years ago I tried to find any working example of OAuth with GNU Social and didn't find any. Since that time #AndStatus supports Basic Authentication only with GNU Social.
@kaniini I see that you already have everything to add "/whoami" endpoint: - authentication works, so you know an Actor, who makes a request. - you should only return the Actor's "object", not a timeline. I already see that you do have that object inside a timeline... Will wait, thank you. @thefaico
@rysiek Maybe it's the right time to start building (or completing implementation of) #ActivityPub compatible client to server API and not waste time on improvements of Mastodon's custom API ?! @dfeyer @kaniini @maryjane
@kaniini Thank you, after several attempts I figured out the correct full URL for the "whoami" API endpoint: https://pleroma.site/users/AndStatus/inbox - and I got JSON response. Will parse it and return to You to move further, if you don't mind :-)
However, this URL, looking like an actor's inbox, is conceptually incorrect for the "whoami" call as even #ActivityPub spec says: "The inbox is discovered through the inbox property of an actor's profile". This is why the "whoami" call should be the same for every user, and not the "inbox" of a concrete user/actor. I think :-)
This is "whoami" call where the authenticated Actor receives his/her profile information, including URLs of endpoints!
#AndStatus Android client is ready for integration/developer's testing of the "client to server" #ActivityPub protocol. I created an alpha build of AndStatus for server developer, which allows to use AndStatus as a manual Server API testing tool. In order to move forward, past authorisation step, I need an account on a server that successfully authenticates/authorises a User. Servers that I'm aware of, didn't automate/implement the Client registration/User authorisation steps yet...
@amish If you care about stored data, I would recommend to make a backup before reinstall in #AndStatus Settings -> Storage. If not, uninstall - Reboot- Install is the most reliable way to avoid possible installation problems.