From a327ec132f56d69fa31f8698ed83349914db54d6 Mon Sep 17 00:00:00 2001 From: Alex Gleason Date: Thu, 30 Mar 2023 14:42:13 -0500 Subject: [PATCH] README: move available policies to the top --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 33765b2..7a1e8ab 100644 --- a/README.md +++ b/README.md @@ -63,6 +63,12 @@ Finally, edit `strfry.conf` and enable the policy: That's it! 🎉 Now you should check strfry logs to ensure everything is working okay. +## Available policies + +For complete documentation of policies, see: + +- https://doc.deno.land/https://gitlab.com/soapbox-pub/strfry-policies/-/raw/develop/mod.ts + ## Writing your own policies You can write a policy in TypeScript and host it anywhere. Deno allows importing modules by URL, making it easy to share policies. @@ -173,12 +179,6 @@ Then, in the pipeline: - You should not use `console.log` anywhere in your policies, as strfry expects stdout to be the strfry output message. -## Available policies - -For complete documentation of policies, see: - -- https://doc.deno.land/https://gitlab.com/soapbox-pub/strfry-policies/-/raw/develop/mod.ts - ## Filtering jsonl events with your policy It is not currently possible to retroactively filter events on your strfry relay. You can however export the events with `strfry export`, filter them locally, and then import them into a fresh database. You can also use this command to filter Nostr events from any source, not just strfry.