Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
The AsyncAPY.defaultclient module is, well, awful. I made it in like one hour or so to test my server and never really updated it, for a default implementation I'd expect something more robust and optionally async, too.

Describe alternatives you've considered
Rewrite the enti

The bot should:

• Kick or restrict writing a user who sends too many messages per second/minute (configurable).
• Notify the group when it takes some action (eg. the user has been restricted/banned).
• The feature should be opt-in per group, being off by default.

Nice to have:

• Warn a user before reaching a limit (eg. when a user has written 80-90% of allowed messages per m

The sever and core raise here (and maybe in other methods as well, not checked yet) a wrong exc. when the entry wasn't found.

https://github.com/viur-framework/viur-core/blob/06a47b18658aa1b801251cbbca60d153b927b346/prototypes/list.py#L203-L204

(Creating this issue was faster than a PR. Tbd...)