free-software

We badly started implementing some props mutation.
There are usually two cases:

1. The props are injected via root component propsData
2. The props are used inside a vue app

Solution 1

Migrate the propsData (usually initial-states) to the root .vue file away from the .js entry point

Solution 2

Use a sync modifier and change the data flow according to vue documentations

There's a potential for privacy-related incidents such as hitting "Enter" when opening flameshot from the toolbar. This action captures the screen but subsequently uploads it to imgur, even if it was not the user's intention.

There should be a confirmation required from the user before any upload takes place. For some reason, the upload stemming from this action (flameshot toolbar icon ->

https://github.com/ornicar/lila/blob/92d6fc6b466594d0a4c8c492b298e4804124704f/ui/%40types/lichess/index.d.ts#L256

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

Is there any interest in maybe supporting an https://github.com/ArchiveBox/ArchiveBox integration in some way? It's a good solution for keeping archived copies of links. Maybe new bookmark entries could be added to an archivebox instance if configured?

This is an Easy Hack.

Detailed description and rationale

We have documentation in loleaflet/loleaflet-api.html it would be great to transfer those bits directly to source code via comments in front of declarations for self documenting purposes. Please start small, picking one option at the time per PR

Example

1. Pick