v1.4 now include the decoding as suggested by CrazyCat Thanks for the point in the right direction CrazyCat wouldn't have thought of that so cheers
Cheers
v1.3 might solve some of the probs you had (I couldn't replicate them all )
The 301 redirection handling was quite new for me at least but good to poke into. It's definitely not finished but it might be less broken than it was before
Cheers
I gave this a go here https://m00nie.com/eggdrop-url-title-grabbing-script/ although it's not part of the YouTube script just yet. I might mangle it together with the YouTube and Twitter scripts though in the future if this one seems to work ok in the next while
Cheers
I think you might need to check your bot is compiled with UTF-8 support or what the default encoding is on your OS. I had to recompile some of my older hosted bots to get UTF-8 working properly
Cheers
Hi Caesar ☺️ Thanks for the spot on the date being red incorrectly.ive updated the script to sort this along with your suggestion of the string maps (which I've never used before now so nice to learn something cleaner 😁) The change that broke the script though is the API now randomly(?) seems to app...
There are some hopefully commented to be clear variables near the top of the script to control the throttle timers. Just change those to what suits you
Updating with new news migjt be more than a little noisy but I'll have a look and see how that might work
Cheers
Hi Caesar Thanks for the suggestion I'll have a look into it and see if that would help (just a different way than I've done it before so something to learn/try for me) 😁 m4s the default is one request per user ever 30s, one per channel every 10s and the same search term or link spammed in 5 mins an...
v2.2 adds the option to set a default location and will use that if no per user location is saved (just comment out the setnews line to stop people doing that )
Realised i didn't share a link for anyone else but https://www.m00nie.com/news-script-for-eggdrop-bot/
Hopefully all fixed in v2.1 ....V2 was.... not great (I think the technical term is utter [censored] I didn't test fully or at all for some cases).... I hadn't actually realised that the V2 API is more geographically based than specific news source. V2.1 reflects that and now reports latest stories ...
New update (2.0) moved to the new API and 'sorted' the TLS errors I hope due to the move to cloudflare and need for SNI plus my TLS config seems a bit old/rubbish for more modern Https
Hopefully all good now
Cheers
(I added the ytsearch flag to switch on/off the searching functions only: .chanset #channel +ytsearch) Hi m4s 😁 Thanks for the good idea. I've added that to the script and posted an update, cheers for the suggestion. @AlbozZz sorry I'm not familiar with that help site but it looks like it's missed ...
I saw this and updated the script to include it as a configurable option for a per user and per channel limit. Newest version has the variables at the top
Hope it helps a little
Cheers