🚨 only for reckless testers, this is not a release!

help me find a reasonable proof of work limit by testing out this build of bitchat with proof of work for spam prevention (the same way bitcoin prevents spam btw).

https://limewire.com/d/2ZYzQ#sZPuofd9nr

- download and install

- go into a geohash chat

- write something, see semicolon guy

- turn on proof of work, notice the difficulty slider

- write a few messages

- increase difficulty, write a few messages

📝 report: device, max difficulty

at what difficulty does it take your phone more than a few seconds to send a message? which device are you using? which operating system?

comment below so I can gather some data. appreciate you 🫡

nostr:nevent1qvzqqqqqqypzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzemhxue69uhks6tnwshxummnw3ezumrpdejz7qpqnwvnkhtgsc9y9eqscrxs433kzkd5htg5pr3qa8fd3qyrt8dcf47stuzj97

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqs0fk6jwz7ejxchh6s7d5p473w7uwffr8pfga9m4sgrgtfz836wp5qv6d7rz link fixed! thank you

For me it already works perfectly without semicolon spam.

Android 14 on Motorola Edge 30

I personally think that that pow slider would be perfect as permanently on the top of the screen

Long live "reckless testers"

What's the <@spam-tester> making an appearance?

8 bits seems to cool the semicolons on Pixel 7pro, android V16

How to go into geohash region? Can't write in there more than 'ge'

Pixel 8 pro

Up to 15 bits is very fast. 16 gives a slight delay. 17 up is a noticeable delay.

can you sample some more data? my pixel 9 seems slower

Does the length of message affect the time taken?

I occasionally get longer times at 15, but it's usually pretty quick. 16 or above is always a noticeable wait. 14 seems to always be quick.

Limewire is still a thing 😮

Not seeing the pow option in 1.2.2 from that link graphene pixe6a

Install again

S25 15bits=1.5 sec

Android v15 arrows we2

Semicolons became invisible in pow1.

On my device, posting with pow20 or higher takes several dozen seconds.

The end goal is to have relays verify the POW too, right?

I would say it is working great

Haven't seen ;;;; guy yet, but I feel like the maximum for a manageable time to send for UX was around 15-16 bits.

Pixel 8 on calyx (soon to be graphene🤝)

TIL Limewire still exists.

I was looking for this comment.

16 is treshold I would say too. 13 works very well

Hell yes nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccppemhxue69uhhjctzw5hx6ef0qyt8wumn8ghj76rfwd6zumn0wd68ytnvv9hxgtc2mtflh

PoW will always be the way to combat spam 🤘🏼

nostr:nevent1qqszd0ef9r2nz4utznspq29npvfhjjhwq2dqd0aerj803v8ht8xnp5sppamhxue69uhkummnw3ezumt0d5dl9lh4

12 feels easy and cozy, not much differet than the ui state changes you'd expect from a 'sending' action. 15 takes a couple seconds but i don't mind if i've chosen it and i know why.

pixel 7, grapheneOS

Cubot KingKong ES, difficult 13 almost instant, 14 normal, in 16 the time it's a lot for conversations

Geohash appears grayed out. What am I doing wrong??

Maybe Location permissions

Hmmm. It acts like they are enabled. There is a green teleport button but it doesn't do anything

What geo are you trying?

Thanks. I just didn't know what I was going. No one even in my region right now so it was a bit confusing

Okay I still wasn't getting it at all. I see now that the teleport button only works if you type in a new geohash. I was totally misunderstanding

Consensus seems to be 13 bits

Samsung S24 (SM-S921B/DS) Android 15, 16 bits = 5-7 seconds. 15 bits = 2-4 seconds. 14 bits 0-5 seconds.

Just sent messages, not seeing semicolon guys atm.

On limewire? Bruhh back in the day, every download on limewire came with a free viruses

I saw that and was like...nah bruhhh

It's a signed apk 🤘

Similar results on message length sending time to other S25 reports. However, I'm not getting human responses on 9q anymore and it occasionally displays an old section of chat out of chronological order.

Yeah I think the big question is. What delay when sending a message is acceptable for UX. I don’t have an Android so I can’t test it on bitchat, but will work on implementing this in coolr. My guess is that a second or so would be fine. Especially if there some animated visual that indicates something is happening. It’s also worth people to understand yoyll probably only see others messages that are using the same threshold or lower since I assume the client is blocking any messages that are not meeting your set threshold.

I can't see anyone's messages and online users on graphene. Chatting with myself 😁

Okay, found the issue: I overwrote the obttanum version. Now after uninstalling it worked

On the reckless apk the active user count isn't fatching and the app is asking to turn on Bluetooth every other minute. 16 bits seems like is Gucci to go with

I wonder if nostr:nprofile1qqsg73x9vycmxcnx3v8qr05vwxey0pje3wmglwgfeltcl2lmqkxapuqprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj7qgmwaehxw309ankcetpwdhkuct5daezuer9wchhyetvv9usz9thwden5te0wfjkccte9ejxzmt4wvhxjme0g9vq0e has any suggestions, getwired.app had this feature

This has been tried so many times and never works. Your phone won't be able to compete with a desktop computer so there's no real way to do PoW prevention. Bitcoin works because of reusable PoW, where you can delegate it to specialized people, not make it something everyone does.

I know my dude

thank you nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7ut7uqx and all the reckless testers 🫶🏽

nostr:nevent1qqszd0ef9r2nz4utznspq29npvfhjjhwq2dqd0aerj803v8ht8xnp5sppamhxue69uhkummnw3ezumt0d5dl9lh4

When I send a message it takes a long time to compute the first time and then if I send the same message in another geogash it’s almost instant.

Also longer messages seem to take way longer to compute. And semicolons, the symbol and the word spelled out take forever to compute 😂

all that was chance, try again!

I just tested v.1.2.2 with Google Pixel 8a, GrapheneOS and found that with difficulty: 15 bits, the letter "p" (as a message) takes between 2 and 19 seconds. 🤷

Pixel 8, 15b cca 3s. 16b cca 10s

12 is quick, 13 starts to push it taking a few seconds, 14 is too much at 5 plus seconds each message

oh and I'm on a Samsung s10

Phone caught fire at 15

ahhh nice!!!

love style of text box, writing & font! unique design!

Hello everyone, can someone explain how the Proof of Work principle works in this context?

Thks a lot 🖖

Did you managed to handle that

Bro dropped a limewire link 😂 you guys are having too much fun lol.

Limewire & IRC

It’s my childhood 🥹

Ayo check it out Mr bitchat

nostr:note1ltvky54rsdppk8anq6upxvjftm8nkkj6gmvw45lk2lvjglek6v5qw66k88

Pixel 9a, GrapheneOS, Bitchat running in a private space. Any difficulty adjustment seems never-ending, even 1 bit.

https://blossom.primal.net/f7a7446039ed764fc4d88bb97078cba219786a8df22b14ae1f39158df28e7198.mp4