I think that’s you, #[2]​ πŸΆπŸΎπŸ˜‚πŸ˜‚πŸ˜‚πŸ«‘

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

nostdress | DBG Error publishing to relay wss://relay.mostr.pub: msg: rate-limited: too many requests

Reply to this note

Please Login to reply.

Discussion

It is understandable though πŸΆπŸΎπŸ˜‚πŸ˜‚πŸ˜‚

Indeed! I think that current implementation handles zaps much faster! Need more people to use it! 🐢🐾🫑

I will also test it today, I will let you know how it goes. 🐢🐾

Thanks. Please file an issue if you find bugs! Eager to see how it works in other environments! 🐢🐾🫑