🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg

It would be nice to use shortcuts for common functions, like:

• s to trigger screen sharing (start/stop)
• someKey to switch between available streams
• f to trigger full screen
• c to copy the room url

https://material.io/resources/color/#!/?view.left=1&view.right=0 readability needs to be possible almost universally ideally. This means avoiding all caps strings in titles as screen readers read every letter and other nonsense like this however the first and foremost concern is just simply that we ship with a default that is visible for our sighted users who may have issues with color blindness

Add environment variables to make it possible to disable the following features:

• Face Recognition: PHOTOVIEW_DISABLE_FACE_RECOGNITION=1
  completely disable face recognition and hide the icon from the side menu

• Video encoding: PHOTOVIEW_DISABLE_VIDEO_ENCODING=1
  disable ffmpeg encoding, but still allow web compatiable videos that doesn't need encoding.

• **RAW processing:

Hi there, i couldn't find a matching issue about this, and since it is affecting multiple areas/apps of Nextcloud, i went with this repo.

In apps that use tags or other elements with selectable colors, i always find myself annoyed by the bad contrast due to late switching of the foreground color.
For example when moving from Google Calendar to Nextcloud, the default blue and red colors would

lowdefy/lowdefy#540 (comment)

As mentioned in discord I would recommend adding the following to your k3s deployment. I see multiple pages about the k3s deployment and each are missing the following which will make sure the nodes stay alive even if you over provision pods.

INSTALL_K3S_EXEC= ........ --kubelet-arg system-reserved=cpu=100m,memory=100Mi --kubelet-arg kube-reserved=cpu=200m,memory=400Mi

If we can't open port, then lets do something like:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Addr

Currently we are using an emoji, this causes inconsistencies across browsers and systems.