-
Notifications
You must be signed in to change notification settings - Fork 113
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
Herramienta / Comando para impedir intercambios entre usuario A y B #438
Comments
Ya tenemos los comandos Proposal in EnglishAs in any p2p platform there are always misunderstandings, lack of seriousness, etc., by some users so it is always necessary some tool or way to block or prevent a user with whom you have already had a bad experience, to take an order. Currently the only way to do this is to cancel the trade by both parties, so the ill-intentioned user can ignore and leave your funds frozen until the bot expires the trade. Due to the lack of blocking option the malicious user can perform the freeze over and over again indefinitely. Possible Solution: Which should avoid exchanges between user A and B, the bot should keep the telegram id to prevent Second command `/unblock @username In case of error or solution to the misunderstanding and be able to continue doing exchanges with the user. Third command The bot should ignore the |
or |
perfecto |
Hi!, I would want to get this one, could you assign it to me? |
Hi @jgosmus already assigned it to you |
Hi @jgosmus are you still working on this issue? let me know if you have any blocker, we can help you |
Hi @grunch! I will let you know if I get blocked, thanks for the help :) |
Hi, I'm working on the issue and there are some points that I would like to confirm.
I'm going to guess this is correct and it's not possible to hide offers so when you pick an offer from an user that is blocked the bot won't give you the option to accept the offer and it will tell you why. Guessing this I have two doubts:
|
that's correct, orders can't be hidden
IMO the message should be different if you are the blocked user or if you are the user who blocked the other user. Maybe messages like this:
I don't think it should be revealed who the maker is, to take care of their privacy, because maybe if someone knows who the creator of an order is, they can tell other users and that's not good But let's see if there are more opinions on this. |
Agreed on this |
I want to let you know that I am still working on this feature, I expect to have it ready for next week |
Hola @jgosmus cómo vas con este issue? |
Buenas @Catrya ! Por como tengo los commits creo que dividir la feature en varias PR puede ser un poco complejo, este finde puedo intentar hacer el apaño o si veis bien que lo haga en una PR lo subo directamente, como me digáis |
Perfecto, no hay problema. Era solo para saber si lo continuarías para si no dejarlo libre para que alguien más lo tomara. Gracias por responder. Gran trabajo! |
Como en toda plataforma p2p siempre hay malos entendidos, falta de seriedad, etc, por parte de algunos usuarios por lo cual siempre es necesaria alguna herramienta o forma de bloquear o impedir que un usuario con el que ya se ha tenido una mala experiencia
pueda tomar una orden, actualmente la unica forma de hacerlo es cancelar el intercambio por ambas partes, por lo cual el usuario mal intencionado puede ignorar y dejar tus fondos congelados hasta que el bot expire el intercambio. Debido a la falta de opcion de bloqueo el usuario mal intencionado puede realizar el congelamiento una y otra vez indefinidamente.
Solucion:
comando /block @username
el cual debera bloquear intercambios entre usuario A y B, el bot debera conservar el id de telegram para prevenir cambios del @username.
comando /unblock @username
En caso de error o solucion al mal entendido y poder seguir haciendo intercambios con el usuario.
comando /blocklist
Mostrara el listado de @username's en la lista de bloqueo.
El bot debera ignorar el comando /block @username en caso de tener algun intercambio activo entre ambos usuarios para evitar mal uso del comando.
The text was updated successfully, but these errors were encountered: