| Thanks for the kind words! > If I'm not wrong, quickly reading your beautiful synthetic python code, you store music in your server (as a MongoDB blob). ins't it ? Nope, the bot only stores track title, performer and id. Actual media is stored on Telegram servers. > Just an idea, maybe always interesting for sort of "auto-deleting" sahring, as secret messages (but could be wrong). Yes, I'm thinking about it. > I noted that search functionality could be developed to understand better what user are looking for, but this is not a criticism of your excellent work, just a feature for a future implementation! Sure, I'm open for any suggestions and criticism :) I'm thinking about how to improve it. |
good idea ;-) BTW, do you have any recent news about Telegram decisions about uploaded files persistence on their server ? https://core.telegram.org/bots/faq#can-i-count-on-file-ids-t...
> For the moment, file_ids for your bot's outgoing files may be recycled after several thousand files have been sent. This may be changed in the future. Inbound file_ids can be treated as persistent.
About searching on MusicBot (using web interface: https://web.telegram.org/#/im?p=@MusicCatalogBot)
I noted that:
1. inserting an author name, by example:
Alice Coltrane
?! :-)
I got all tracks related to any "Alice", by example
Moby - Alice some other Cocteau Twins track, etc.
no track related really to "Alice Coltrane", that's probably because you just do an OR on your query, ok, clear.
2. in the web client, in result track list, song names appear truncated... by example I'm not able to read the Cocteau Twin complete title track, in the above example.