app

This is a follow up to #11277.

Problem

Currently each individual share entries has the CSS class of .share-item:

However one of a widely used filter (https://secure.fanboy.co.nz/fanboy-annoyance.txt) ended up catching this as a false positive and hides all t

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

Version: v0.10.0
To reproduce, go to settings and add more than categories at the same time below any category.
When you assign the name for one of the new, the other get the same name.
If you go to the second and try to change the name, the first one gets the second name.
I hope this helps.
Thanks.

[aw-qt_2021-03-26T00-09-49.log](https://github.com/ActivityWatch/activitywatch/files/621747

When we install net-istio (and potentially other plugins) multiple validating webhooks are registered.

Unfortunately the webhooks are configured with just namespace selectors that are identical. Thus when config-istio is updated the serving webhook is invoked (which is a noop) and vice-versa for any serving config maps.

To avoid this we should use objectSelectors and distinctly label the

At the moment fences, walls, hedges etc. are rendered as a very thin dotted line which is barely visible on the map, though its an important information for pedestrians and hikers.

Let's make rendering more prominent and perhaps different for walls and fences (and m