Conversation
Notices
-
Diogo Cordeiro (diogo@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:03:11 JST Diogo Cordeiro 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 repeated this.
-
Diogo Cordeiro (diogo@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:15:08 JST Diogo Cordeiro @tom79 https://loadaverage.org/attachment/4987291 AndStatus repeated this. -
Fedilab (tom79@mastodon.social)'s status on Sunday, 03-Feb-2019 22:15:55 JST Fedilab @diogo yes but what about previous ones?
AndStatus repeated this. -
Diogo Cordeiro (diogo@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:19:08 JST Diogo Cordeiro @tom79 here they are https://loadaverage.org/attachment/4987300 AndStatus repeated this. -
Diogo Cordeiro (diogo@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:38:23 JST Diogo Cordeiro Ah, I think I know what is going on...? :thinking:
IIRC, GNU social handles notifications in a very specific way that I haven't studied in detail yet (but intend to this summer). I think you have to go through your timeline so that AndStatus can collected previous notifications, or just accept that only newer marked as read notifications will show up there. Try to trigger a notification and then mark it as read, it should then be added there.
@AndStatus@GnuSocial.no Can you confirm this to be expected behaviour?
@mmn Can you add some inside on how notifications are handled? -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:40:23 JST AndStatus @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 @colegota https://loadaverage.org/attachment/4987331Diogo Cordeiro likes this. -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Feb-2019 22:45:19 JST AndStatus @up201705417@loadaverage.org "Unread notifications" are just notifications, which weren't explicitly marked as "read" by a user (using "Mark all as read" button on an "Unread notifications" timeline).
@tom79 @lnxw48a1@nu.federati.net @colegotaDiogo Cordeiro likes this. -
AndStatus (andstatus@loadaverage.org)'s status on Sunday, 03-Feb-2019 23:09:32 JST AndStatus @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.orgDiogo Cordeiro likes this.