Add metrics for rate limits

Correctly identify CLOSED messages and rate limit on them too

Shared rate limiter for multiple conns

Rate limit from notice warnings

More validations and check it before push to queue

Increase timeout

Handle closed messages

Add more comments

Add flake for local development

Add deployment to readme

Reduce memory usage by not storing unnecessary data and rename things to
make them easier to und...

Also don't die when there is an error updating tasks.

Most of the time there will be nothing to do anyway.

Due to previous incorrect design assumptions we were running individual
public key queries per r...

It obviously belongs there and we shouldn't get any funny ideas about
databases in its viccinity.

It is pointless to wait more than a couple of seconds if something is
wrong.

The endpoint is:

/public-keys/{hex-public-key}

The response looks like this:

{
"follo...

Signature verification is expensive and we get disconnected from relays
a lot.

We can have entries in public_keys but not contacts_events if the public
key is a followee not a...

They will be rejected anyway, our previous error-based method of
detecting this was flawed and s...

Some events contain malformed p tags and we do our best to try to scan
them and accept them.

The events have type `6666` and the payload looks like this:

{
"relays": [
...

The idea is to make it work like https://purplepag.es/what.

The idea is to make metrics more readable.

This probably doesn't matter but it is pointless to try to connect to
those.

Add more metrics

Download all events for specified public keys and their contacts.