-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whitelist / Blacklist pubkeys #15
Comments
Currently there is not, but there should be, and I am working on it! I will update this ticket ASAP when this is ready. |
I want to build a paid damus relay and I would like to use strfry. would love if this was a thing! and a way to dynamically add users so I can create a payment interface. |
Nice! We're working on plugin system that will allow this. It's currently in the Here are the docs for plugins including an example of a whitelist: |
Thanks @hoytech let’s say I’m running strfry via docker-compose. Should bind mounting that plugin to the same path (/etc) as strfry.conf work? |
Hmm good question. I think that should probably work, as long as the container has all the dependencies it needs to execute the plugin script. For example, if your plugin is in node, you'll need the |
I’ll probably re-write it in python. Since the Dockerfile in this repo looks to be stock ubuntu, I assume it will have python3. Maybe I’ll put the plugin in /app instead of having an executable sitting in /etc which is kinda bad form. |
Makes sense. Yep I assume it will have a system python available so it should "just work". Let me know if not though! |
@hoytech in fact, not. I guess the I have a lightly tested and seemingly working python adaptation of your |
Now running the beta [decc3ae] live as my semi-private relay with just a few hand-picked pubkeys allowed to post. The whitelist is rejecting lots of spam. So far, so good. |
Glad to hear it's working -- thanks for letting us know. A gist of instructions we can link to would be great! |
@hoytech Took me a while to work out all the kinks, but here’s my repo that implements a docker-based personal relay server with strfry using the write policy plugin I developed. This may currently be the fastest, easiest way to get a nostr relay up and running. |
Is this issue up to date? docs/plugins.md is on master and https://gitlab.com/soapbox-pub/strfry-policies/ makes good use of it. With the latter, black- and white lists are easy to do. |
Is there, or could there be, a way to configure strfry for whitelisting or blacklisting pubkeys allowing or disallowing posting to the instance?
The text was updated successfully, but these errors were encountered: