Notifications still arrive for filtered posts #545
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: shadowfacts/Tusker#545
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've been getting a lot of the same spam as other Mastodon users. I got tired with dealing with it so I set up a filter at my mastodon profile page to ignore posts with that content. Works well! They don't show up in Tusker.
However, Tusker still sends me notifications about the filtered posts.
Note to self: this requires this entitlement which is by request only
I'm interested in the flow of information.
Are the sources of information different for what is displayed in the app compared to what ends up as a notification? Or not? Where does the filtering happen?
The source of information is essentially the same, but filtering is implemented on the client side. The notifications tab has had filtering for ages and I skipped it initially for push notifications because I hadn't requested that entitlement. The special entitlement is required because, otherwise, a malicious app developer could send hidden/silent push notifications, waking up the app in the background w/o informing the user. In Tusker's case, push notification filtering can't be done on my server because the notification content is encrypted by the originating instance and only decrypted on your device.