Brian

> I think I get your point on possibly filtering of changes with larger % being filtered off. I do suppose it is a trade-off atm of spam vs potential...

> > > I think I get your point on possibly filtering of changes with larger % being filtered off. I do suppose it is a trade-off atm of spam...

 alertSkipThreshold appears to have its own limitations as well, does not seem to filter spam v well on slightly larger intervals. (15s for this case) Possible solutions 1. Use...

Previously mentioned threads regarding volume implementation, https://github.com/brianleect/binance-pump-alerts/issues/24 https://github.com/brianleect/binance-pump-alerts/issues/10 https://github.com/brianleect/binance-pump-alerts/issues/12 Volume is definitely a good indicator of big moves in crypto. However, there are some limitations regarding the current way the...

> I see your point and totally agree with the limitations. Thanks for your detailed explanation. > > When sticking the rest API (which currently uses no API Keys), there...

Possibly implement customizable triggers E.g. 2 consecutive 1s triggers -> Buy 2 consecutive 15s trigger within _ timeframe -> Buy Different level of purchase could be set, small / med...

> Hey, same here somehow. Alerts getting double send for some weird reason. > >  > > Is there a way for a quick 'n dirty fix? Don't think...

 Link: https://binance-docs.github.io/apidocs/spot/en/#24hr-ticker-price-change-statistics @Juanjacinto123 If I'm not mistaken, this would be the endpoint to get the 24h volume info. However, the currently used endpoint is different due to different requirements...

> Hi @brianleect, any update on this? Thanks I have an idea of how this could still be implemented on the current program structure. I could have an option to...

> > > Hi @brianleect, any update on this? Thanks > > > > > > I have an idea of how this could still be implemented on the current...