FaSTTUBe/ftracker
60
1
Fork 0
Code Issues 2 Pull Requests Releases 1 Wiki Activity

Reminders #9

New Issue
Closed
opened 2020-11-24 22:37:04 +01:00 by o.winkels · 5 comments
o.winkels commented 2020-11-24 22:37:04 +01:00
Owner
Copy Link

Notify person if they didn't sign out befrore midnight or something like that

  • EMail?
  • MS Teams?
  • Discord?
  • TG?
  • Web Push Notification <-- Current Favorite
Notify person if they didn't sign out befrore midnight or something like that - EMail? - MS Teams? - Discord? - TG? - **Web Push Notification** <-- Current Favorite
o.winkels added this to the RC2 (Bonus features) milestone 2020-11-24 22:37:04 +01:00
o.winkels added the
Backend
 label 2020-11-24 22:44:06 +01:00
o.winkels added the
System
 label 2020-11-24 22:45:33 +01:00
o.winkels added the
enhancement
 label 2020-11-24 22:46:50 +01:00
o.winkels changed title from Email reminders to Reminders 2020-12-06 11:26:19 +01:00
o.winkels commented 2020-12-07 18:29:28 +01:00
Author
Owner
Copy Link

Currently not planned due to time constraints, i'll revisit when i have time or there is demand.

Currently not planned due to time constraints, i'll revisit when i have time or there is demand.
o.winkels modified the milestone from RC2 (Bonus features) to basic depth estimation 2020-12-16 00:05:49 +01:00
o.winkels added this to the Soon™ milestone 2021-05-18 14:37:10 +02:00
o.winkels started working 2021-05-27 16:30:57 +02:00
o.winkels worked for 5h 52min 34s 2021-05-27 22:23:31 +02:00
o.winkels commented 2021-05-27 22:31:22 +02:00
Author
Owner
Copy Link

It turns out M$ Teams' API for this stuff is pretty shit. The options are:

  • A Bot. Looks like they can only be reactive, i.e. only send a message if they received one before.
  • A "daemon" API client. Unfortunately these have no permissisons available to find/create chats and send messages
  • An "app" API client. Requires some sort of OAuth flow to authenticate that is overly complicated. Use cases would be:
    • Users sign into ftracker using their M$ account, which sounds neat until you realize users can't send messages to themselves
    • 1 user (Dummy/Admin) Authenticates like this and then sends the messages. Can most likely work but seems like a complicated mess.
  • Use "daemon" client to send messages to public team channels. Bad because privacy and "shaming".
  • Back to E-Mail? Nobody reads those soon enough though.
It turns out M$ Teams' API for this stuff is pretty shit. The options are: - A Bot. Looks like they can only be reactive, i.e. only send a message if they received one before. - A "daemon" API client. Unfortunately these have no permissisons available to find/create chats and send messages - An "app" API client. Requires some sort of OAuth flow to authenticate that is overly complicated. Use cases would be: - Users sign into `ftracker` using their M$ account, which sounds neat until you realize users can't send messages to themselves - 1 user (Dummy/Admin) Authenticates like this and then sends the messages. Can most likely work but seems like a complicated mess. - Use "daemon" client to send messages to public team channels. Bad because privacy and "shaming". - Back to E-Mail? Nobody reads those soon enough though.
o.winkels commented 2021-06-07 15:56:09 +02:00
Author
Owner
Copy Link

A new option just came to mind: Why not try out those newfangled web-push-notifications? That will require messing with service workers and stuff, but is probably still easier than M$' shitty APIs.

A new option just came to mind: Why not try out those newfangled web-push-notifications? That will require messing with service workers and stuff, but is probably still easier than M$' shitty APIs.
o.winkels started working 2021-06-07 15:56:19 +02:00
o.winkels worked for 15min 2s 2021-06-07 16:11:22 +02:00
o.winkels started working 2021-06-07 17:41:29 +02:00
o.winkels worked for 3h 43min 54s 2021-06-07 21:25:23 +02:00
o.winkels started working 2021-06-08 00:04:49 +02:00
o.winkels worked for 14min 50s 2021-06-08 00:19:39 +02:00
o.winkels self-assigned this 2021-06-08 00:58:22 +02:00
o.winkels commented 2021-06-08 01:00:43 +02:00
Author
Owner
Copy Link

Made good progress today (see branch push-notifications). Seems very promising. I hope device support is okay, no idea about safari for example.

Things left to do:

  • Send notifications on timer
  • Restrict notificatioin test endpoint
  • Polish some of the code
  • Add to Dockerfile
  • Document
  • Test, test, test
Made good progress today (see branch [`push-notifications`](https://git.fasttube.de/FaSTTUBe/ftracker/compare/master...push-notifications)). Seems very promising. I hope device support is okay, no idea about safari for example. Things left to do: - [x] Send notifications on timer - [x] Restrict notificatioin test endpoint - [x] Polish some of the code - [x] Add to Dockerfile - [x] Document - [x] Test, test, test
o.winkels started working 2021-06-10 22:25:11 +02:00
o.winkels commented 2021-06-11 02:03:59 +02:00
Author
Owner
Copy Link

Shit's production ready i think!

Shit's production ready i think!
o.winkels worked for 3h 42min 41s 2021-06-11 02:07:52 +02:00
Sign in to join this conversation.
push-notifications
Branches Tags
Labels
Clear labels
Backend
controller issue
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
Frontend
Web UI Issue
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
Storage
Storage system issue
System
System config level issue
wontfix
This won't be fixed
No Label
Backend
enhancement
System
Milestone
No items
No Milestone Soon™
Assignees
Clear assignees
No Assignees o.winkels
1 Participants
Notifications
Total Time Spent: 13 hours 49 minutes
o.winkels
13 hours 49 minutes
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FaSTTUBe/ftracker#9
No description provided.
Delete Branch "%!s()"

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?