shadowfacts
/
Tusker
2
10
Fork 2
Code Issues 62 Pull Requests Releases Wiki Activity

mentions don't get marked as read on the server. #357

New Issue
Closed
opened 2023-02-14 16:04:17 +00:00 by jondthompson · 5 comments
jondthompson commented 2023-02-14 16:04:17 +00:00
Copy Link

When I read a mention or a reply on Tusker, I expect that it will not be unread on the server. However, that is not the case.

When I read a mention or a reply on Tusker, I expect that it will not be unread on the server. However, that is not the case.
shadowfacts commented 2023-02-14 19:36:55 +00:00
Owner
Copy Link

What do you mean by unread? I don't know where in the web UI that information is surfaced.

What do you mean by unread? I don't know where in the web UI that information is surfaced.
jondthompson commented 2023-02-15 15:39:46 +00:00
Author
Copy Link

It's on the right, directly under Home.

It's on the right, directly under Home.
Screenshot 2023-02-15 at 9.38.01 AM.png
23 KiB
Screenshot 2023-02-15 at 9.38.01 AM.png
shadowfacts commented 2023-02-15 21:13:48 +00:00
Owner
Copy Link

Gotcha, I'll look into that.

Note to self: this might use the marker api? not sure what else it could be

Gotcha, I'll look into that. Note to self: this might use the marker api? not sure what else it could be
shadowfacts added the
enhancement
 label 2023-02-15 21:13:51 +00:00
jondthompson commented 2023-02-16 00:00:46 +00:00
Author
Copy Link

I know its ticket creep, but any thought about integrating with the iOS notification system so unreads send push notifications? if you need another issue i can do so

I know its ticket creep, but any thought about integrating with the iOS notification system so unreads send push notifications? if you need another issue i can do so
shadowfacts commented 2023-02-16 00:34:46 +00:00
Owner
Copy Link

Push notifications are already planned for a future update.

Push notifications are already planned for a future update.
shadowfacts added this to the 2024.x milestone 2023-07-02 19:02:26 +00:00
shadowfacts modified the milestone from 2024.x to 2024.1 2023-12-22 16:03:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
develop
public-beta
release
calckey
async
simple-swift-promises
pixelfed
2024.2-122
2024.2-121
2024.2-120
2024.1-119
2024.1-118
2024.1-117
2024.1-116
2024.1-115
2024.1-113
2024.1-112
2024.1-111
2023.8-110
2023.8-109
2023.8-107
2023.8-106
2023.8-105
2023.8-104
2023.7-103
2023.6-100
2023.5-98
2023.5-97
2023.5-96
2023.5-94
2023.5-91
2023.5-89
2023.5-84
2023.5-83
2023.5-81
2023.5-80
2023.5-77
2023.4-76
2023.4-75
2023.4-74
2023.4-73
2023.4-72
2023.4-71
2023.4-70
2023.3-69
2023.2-68
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
external

Issue depends on changes to external projects.

  
help wanted

Need some help

  
invalid

Something is wrong

  
investigate

An unconfirmed issue

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
external
help wanted
invalid
investigate
question
wontfix
Milestone
Clear milestone
No items
No Milestone
2024.1
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: shadowfacts/Tusker#357
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?