Inconsistent TICKER implementations

[L1nkus]

TICKER sometimes means 'bookTicker' (real-time best bid and ask updates), but sometimes 'ticker' (slow, usualy ever second updates with a bunch of extra info like volume in last 24h).

E.g. on binance it correponds to 'bookTicker':

    websocket_channels = {
    L2_BOOK: 'depth',
    TRADES: 'aggTrade',
    TICKER: 'bookTicker',
    CANDLES: 'kline_',
    BALANCES: BALANCES,
    ORDER_INFO: ORDER_INFO
}

But on gateio to 'ticker', despite that the 'bookTicker' endpoint is also available on gateio:

websocket_channels = {
     L2_BOOK: 'spot.order_book_update',
     TRADES: 'spot.trades',
     TICKER: 'spot.tickers',
     CANDLES: 'spot.candlesticks'
}

Are there plans to make TICKER, or to maybe have L1_BOOK correspond to 'bookTicker', while TICKER to 'ticker' endpoints?

[bmoscon]

probably will just remove ticker - the value it gives seems marginal and too many inconsistencies like these

[L1nkus]

Thank for the response.
Though hmmm, idk if I'd call it marginal. For example on Binance it's the only way to get real-time updates along trades, but through just trades you can't obtain quantities on best levels