Remote notifications protocol and settings pane

[nothingneko]

Problem

We are not notable enough for press organizations to pick up on information our users need, some users don’t have discord, and others may not check our website, so we must issue the data to every user ourselves to ensure security and user happiness.

Proposal

I propose a way for us to send notifications to every Tau system.

Fyra Labs would be able to issue alerts to all systems. Alerts at the standard level will appear in a feed in settings, the pane title is tbd. Alerts at the urgent level will send a notification and appear in the feed in settings. All alerts will need approval from myself or the CEO to avoid sending superfluous information

Prior Implementations (Optional)

No response

[lleyton]

Mockups?

[nothingneko]

I’ll get to it hon

[nothingneko]

Thanks to Lains for the design

[lleyton]

Where would this be? Can you show some more detailed examples of notifications? How about when in the shell? Emergency alerts?

[nothingneko]

Notifications would only be delivered when the version you're running reaches EOL. All other notices appear in this pane. Emergency alerts will be handled differently, let's see if PBS Warn has an API.

Urgent Notification Example

End of Life

This version has reached End of Life and no longer receives security updates. Check System Notices in Settings for more information.

[kinoko87]

I think the observer pattern could be a interesting implementation

I think there could be two ways of working with it

1. All machines listen to a port that receives notifications and dispatches any event listeners set to get notifications
2. A user account system, all machines that are logged in with the same account/or are added in some other way. So when one system has some issue, it will dispatch any event listeners on other machines that acknowledge it.

[nothingneko]

I think the observer pattern could be a interesting implementation

I think there could be two ways of working with it

1. All machines listen to a port that receives notifications and dispatches any event listeners set to get notifications

Having a consistently open port is a security hazard, and we'd have to secure it appropriately

2. A user account system, all machines that are logged in with the same account/or are added in some other way. So when one system has some issue, it will dispatch any event listeners on other machines that acknowledge it.

That's not what we're looking for, this is more intended for us (Fyra) to send users information

[kinoko87]

I think the observer pattern could be a interesting implementation
I think there could be two ways of working with it

1. All machines listen to a port that receives notifications and dispatches any event listeners set to get notifications

Having a consistently open port is a security hazard, and we'd have to secure it appropriately

2. A user account system, all machines that are logged in with the same account/or are added in some other way. So when one system has some issue, it will dispatch any event listeners on other machines that acknowledge it.

That's not what we're looking for, this is more intended for us (Fyra) to send users information

Ohh okay, my bad.