@baloouriza What do you think #AndStatus forgot to do? I don't see the beginning of this conversation, so I'm curious :-) BTW I'm implementing "sensitive" note/toot property now in AndStatus. @madestmadness
What's new: 1. Added "Home Timeline" notification type that allows to be notified on any note received via the Home Timeline (Inbox). It's turned on by default. Can be turned off in Settings -> Notifications https://github.com/andstatus/andstatus/issues/508 2. Improved identification of the same Actors (users) in posts that cross instances and types of Social networks (ActivityPub / Mastodon / GNU Social). 3. Fixed posting via ActivityPub Client to Server protocol. https://github.com/andstatus/andstatus/issues/499
@baloouriza #AndStatus has an option to show latest notes first in the Conversation view. Regarding timelines: how do you "Pull to refresh" at the bottom of the list? I didn't see any such Android app yet... @gdorn
@lohang I use #Twitter so rarely these days that I don't use anything except the web site. I believe #AndStatus (for Android) was able to connect to Twitter. I do not know whether that is currently true. Same for #Choqok (KDE desktop client). #TTYtter (command line client) has a successor, but I've never tried the new one.
@dwaltiz I fixed probable cause of the "lost draft" problem, that you encountered, in #AndStatus v.47.11 (released yesterday). A draft could be lost (unsent and invisible in a timeline) in a case there was another draft saved earlier by the same account. Now different drafts don't interfere with each other.
@dwaltiz Funny proposal :-) I think it's much easier to fix the problem that you encountered (I suspect it's about UI/#UX) yet even _you_ didn't find time to file the issue properly, trying to reproduce it, describing steps to reproduce the issue and attaching screenshots. Just this post that doesn't help to make the app better, unfortunately :-( Yes, there may be "steps back" (developers call them "regressions") but they occur exactly because I'm rewriting #AndStatus and rely on community members, who take their time to explain, what went wrong... So, when you are ready to help, please file the bug here and we will substantially discuss it: https://github.com/andstatus/andstatus/issues?q=is%3Aissue+sort%3Aupdated-desc Maybe at that stage somebody will join us with concrete help...
What's new: 1. When some Actor follows (or stops following) me, show detailed info about that Actor, not about my Actor. 2. If an attached video has a preview image, that image will be shown (currently available for Mastodon only). View image / View media context menu item for remotely accessed media files. Show a text link to a media file, for which even preview image couldn't be downloaded (instead of no attachment at all as before). #502 3. Don't download attached Video by default. May be changed in Settings -> Attachments -> Download attached video 4. Actor's avatar in their profile is shown with maximum resolution. 5. Fixed: Cannot delete a Note's Title (Name) after it was first saved (even in a draft). 6. Fixed: Default notification sound was heard even if set to Silent in Settings. This was caused by changed rules after starting to target Android 9. Any Android notification (including Vibration and Sound) should show an icon in Notification Area (Android 9 restriction). https://loadaverage.org/attachment/5061991
@emacsen #AndStatus Android client allows you to setup as many user accounts as you wish in several types of Social networks (#ActivityPub is in testing now). And it recognizes the same your Actor in different instaces, showing a combine view of one Actor via several networks, or a view of all your Actors...
I made the simplest implementation of #ActivityPub C2S protocol in #AndStatus, allowing me to log into pleroma.site, read home timeline and get other user's info (i.e. read the Actor's profile based on his "id"). But I've got an error response from pleroma.site server on an attempt to send a Note, so I created another bug report in pleroma issues tracker: https://git.pleroma.social/pleroma/pleroma/issues/650
Discussion of the #ActivityPub Note's "name" property usage and it's processing by Pleroma. Main attention is on the Client to Server interactions that are being implemented in #AndStatus.
I feel that we mixing two different use cases here:
1. An ActivityPub property, to which a Note's Subject/Title is placed, when entered via Pleroma web UI. I understood about this point.
2. Delivery / sending to other servers a Note, which came from a client application or from another server and which has the "name" property. I assume that if incoming Note has the "name" property, Pleroma doesn't delete that property, but sends it to recipients with the same value. ?!
@tom79 "statuses/mentions.json" endpoint is the primary source of Notifications in the GNU Social "type of a Social network" and in Twitter. But as I wrote, an activity / note from ANY timeline may be put into "(Unread) Notifications" timelines, if #AndStatus app decides that a User needs to be notified about it. Even from "Search" timelines, which can be made syncable. @up201705417@loadaverage.org
@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
@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.
#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...