-
Notifications
You must be signed in to change notification settings - Fork 164
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
POW #2
Comments
@hermanskledar I'm working on this on my fork cf #212 Do you know how many bits of PoW are typical of other clients at the moment? I will make a "add PoW" button when sending a note, wondering what the default options should be for number of bits to add (in addition to a custom amount). |
No I don't but I know that with nostrid you can adjust your difficulty for
sending and the requirement for others to show on your feed
…On Sat, Mar 11, 2023, 07:57 maxmoney21m ***@***.***> wrote:
@hermanskledar <https://github.com/hermanskledar> I'm working on this on
my fork cf #212 <#212>
Do you know how many bits of PoW are typical of other clients at the
moment? I will make a "add PoW" button when sending a note, wondering what
the default options should be for number of bits to add (in addition to a
custom amount).
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMTXMP5XSB4EZK3ZY4JUIWLW3QO6LANCNFSM6AAAAAAUA43WCY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
vitorpamplona
pushed a commit
that referenced
this issue
Jul 10, 2024
As spam is becaming issue more and more I think this may be now important. Also there are already clients using it: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First of all, great app. Very fast I enjoy using it for my nostr consumption therefore I would kindly ask for an awesome feature,
I would love being able to see POW on messages and filter on this aswell as do some POW on my own device like nostrid does.
The text was updated successfully, but these errors were encountered: