Auto-Embed Links (formerly TikTok Plugin) [2024.03.06]

[jagerbomber]

Which older version specifically?

[bigballofyarn]

Nov 13, 2024 5:02:47 GMT -8 jagerbomber said:

Which older version specifically?

I'm using 0.0.5 and not the new 0.2.1.

[jagerbomber]

any modifications/changes or additions you did in the settings?

[bigballofyarn]

jagerbomber ,

I added some sites that weren't in the list. I made sure "Get List of Providers" was checked. There's not much that's editable.

[Chris]

Nov 13, 2024 4:22:19 GMT -8 bigballofyarn said:

Nov 13, 2024 1:27:08 GMT -8 Chris said:

We've already established that v0.2.1 is broken when it attempts to download a new provider list. The browser's security heuristics, in an abundance of caution, deny the download because the "content-type" of what was requested does not match the type that was actually sent. The plugin's coding expects a "success" or a "failure" but not a "successfully failed" and therefore crashes hard.

ETA3: v0.2.2 (changes below applied )()

ETA2: This should allow v0.2.1 to continue parsing after the download gets rejected instead of aborting.

1. Click the Build Plugin button to enter build mode

2. Go to the components tab and then scroll down to line 25 in the 2nd javascript component and you should see this

   if(localStorage['oEmbed_providers'] && (+new Date - +new Date(Number(localStorage['oEmbed_providers_time']))) <  parseInt(settings.update_on,10) ){
settings.providers = JSON.parse(localStorage['oEmbed_providers']);
console.info(`Grabbed provider list from localStorage with ${settings.providers.length} entries (static list has ${p.length} entries)`)
}else{

   
   
   edit it to add try/catch so it can recover from any possible network errors returning HTTP errors in HTML instead of JSON
   
   

   if(localStorage['oEmbed_providers'] && (+new Date - +new Date(Number(localStorage['oEmbed_providers_time']))) <  parseInt(settings.update_on,10) ){
try{ //start try/catch
settings.providers = JSON.parse(localStorage['oEmbed_providers']);
console.info(`Grabbed provider list from localStorage with ${settings.providers.length} entries (static list has ${p.length} entries)`)
}catch(k){} //end try/catch
}else{

3. Go to the components tab and then scroll down to line 42 in the 2nd javascript component and you should see this

   if(providers.length){ console.log(Array.from(content.headers.entries())); //debugger;

settings.providers = providers;
localStorage['oEmbed_providers']= JSON.stringify(providers);
localStorage['oEmbed_providers_time']= +new Date;
console.info(`Successfully downloaded provider list from ${provider.url} with ${settings.providers.length} entries, older (default) list had ${p.length} entries`)
}

   
   
   edit it to add try/catch so it can recover from any possible network errors returning HTTP errors in HTML instead of JSON
   
   

   if(providers.length){ console.log(Array.from(content.headers.entries())); //debugger;
try{ //start try/catch
localStorage['oEmbed_providers']= JSON.stringify(providers);
localStorage['oEmbed_providers_time']= +new Date;
settings.providers = providers;
console.info(`Successfully downloaded provider list from ${provider.url} with ${settings.providers.length} entries, older (default) list had ${p.length} entries`)
}catch(k){} //end try/catch
}

4. You'll need to manually add newer additions to the provider list if the plugin cannot download the list

ETA: instructions on how to create a free and private Cloudflare proxy
(this proxy removes the content-type in the response, preventing the browser from suspecting it as an attempt at an exploit)

All is good. This is fine for me. I'm never putting you to work. The objective was only to offer you help if what you wanted to do was test/code/whatever. I'm keeping the older one installed for now and may play around with Cloudflare when I have more time later. I expect that my forum would reach 100,000 hits entirely too quickly though. With that, I might just keep the older version of the plugin and not even bother with Cloudflare. Your coding, help, and generosity never go unnoticed. 

Thanks, bigballofyarn . I do appreciate your encouragements

The proxies are coded to automatically failsafe to the next in line; the more the merrier 😉 (all that could not happen, of course, if the code aborted)

Once a CF proxy hits the limit, it starts refusing connections and returns an error, which would bring the next batter up. You can, of course, have multiple CF workers set up as proxies...

[bigballofyarn]

I installed v0.2.2. I've asked my posse to report any positive feedback or issues.