v0.3.0

Major overhaul - to websocket lib, db management, etc. Performance should far exceed prior versions.

If you deploy this version without migrating, you'll start with new empty databases (nn.db and nn-kv.db); your prior data will reside in n.db.

To migrate your data: Before running this new version, update your relay jar but don't start the relay. Instead, run:

java -cp target/me.untethr.nostr-relay-0.3.0.jar clojure.main --main me.untethr.nostr.common.store-migrate

You should also update your conf/logback.xml and conf/spy.properties to the ones included in this release.

There are new optional config options in conf/relay.yaml that you may want to copy into your config for future tweaking, but this is not necessary.

After successful, you can start your relay and backup or discard the old db.

v0.2.2

• Implemented database pooling and database metrics

Just update your relay. No need to change config or anything.

v0.2.1

• nip22 support — now you can add max-created-at-delta: 2700, for example, to your server's relay.yaml file to prevent far-future events from being published

v0.2.0

• nip-16 implemented
• optional max-content-length added to relay.yml config
• readme and added doc/deploy.md with more deploy notes
• all sqlite writes go through singleton event thread
• synchronous fulfillment when limit = 1 for low-latency "lookup" requests
• misc fixes

What do do:

• use this release jar
• update your server conf/nip11.json "supported-nips" and "version" properties to use replaceable runtime variables (see conf/nip11.json in repo for exactly how to do this)
• update your server conf/relay.yml with new optional properties:

# This is optional. If not specified, the relay will store events of any numeric
# kind. Otherwise, the relay will (quietly) not store events not whitelisted
# here.
supported-kinds: ["0-5", "7", "40-49", "10000-19999", "20000-29999"]

# Optional. If not specified, then content of any length is accepted.
max-content-length: 1048576