API Updated Needed?

[vincentlarkin]

Hello brothers, @Llewellynvdm @sermonindex-dev @sherebiahtishbi

It has been a while, I have recently had time to look at this and it seems to me (correct me if I am wrong) the API needs to be updated, as in put in line with what the website currently offers.

Some links on sermonindex.net do not lead to any audio files (https://www.sermonindex.net/modules/mydownloads/viewcat.php?cid=1450) , and now a lot lead to archive.org links. I have updated my personal sermondownlloader codebase to be able to download from these archive links, but this still leads to the problem of dead links.

If pages do not have valid audio files, their entry in the API should probably be removed, or the link fixed. Is there an easy way to do this via server-side? I am not familiar with this API.

Thank you.

[Llewellynvdm]

Greetings Brothers,

Yes the collapse of Archive.org has significant result, but it should not effect this API, just the website. I have diversify my online hosting of audio sermons to make use of one main stable "yet not free" hosting solutions that I would suggest as an alternative to the current Dropbox and Archive solutions.

New solution is wasabi.com

They can host up-to 5 TB for only $5 usd per month, and then adding it behind a cloudflare CDN is super easy and a powerful dependable access point that will be most long lasting, with high volume. Here is a few links to look at:

https://wasabi.com/resource/solution-brief/cloudflare/
https://www.cloudflare.com/en-gb/partners/technology-partners/wasabi/
https://wasabi-support.zendesk.com/hc/en-us/articles/360018526192-How-do-I-use-Cloudflare-with-Wasabi-

I have just finished a complete container driven API solution for the Wasabi API, that I will integrate with Sermon Distributor, and we can convert this simply for use with SI, if needed as it supports the whole CRUD, and listing in a simple small set of classes.

What happened with Dropbox?

I am moving away from Dropbox, as they are more and more showing signs that they will block and even delete our sermons simple because it is not agreeable to their own objectives.

So yes, Dropbox is the current linked audio files in this API, I think what is happening is we are pushing up against their limitations of a free account and then they block further downloads. I can try and resolve that but reactivating that account, but I am moving all our own audio files for https://www.loudvoice.org/ and https://truechristian.church/ to Wasabi in the next few days.

How does the API work now?

In short we have a "custom themed" YOURLS instance: https://api.sermonindex.net/admin/

So that each link in the API for example: https://api.sermonindex.net/SID4076-download opens/redirects to https://www.dropbox.com/s/j36il881uzhtfp8/SID4077.mp3?dl=0

These redirecting links are managed by the YOURLS system database, and is easy to update. So if you all agree that I can move the audio files into the Wasabi system (as part of my account, so I will sponsor this for as long as I can), and then update the links we should get this resolved fairly quickly for all the existing links. Any donations towards this hosting will be helpful, but at-least you can know we've got this for the next few years.

@sermonindex-dev I would need access to the YOURLS system database do do this, and it probably be a good time to just update everything again.

To update the API

Here Greg just need to give me a new dump of the database as we did in the beginning and I will generate the new API update of all the needed new data into this repository.

Next steps?

Well I am going to move all the files anyway from dropbox to wasabi as a backup... and I would like to update the API links anyway to insure we stop getting slammed by the Dropbox limitations, as this as massively effected our websites as well. So its really up to Greg how quickly we incorporate these changes into Sermon Index.

[sermonindex-dev]

brother Llewellyn, Thank you so much for serving and getting drop box working for all these years. Imagine all the messages that have been downloaded and listened to! It's staggering. Towards going forward, I believe the most seamless and easy would be to just link to archive.org for all the content. It has been working well for many years and it seems this would be the best option as its also free and SermonIndex has a special partnership with them. Could all the API links be changed to point to the archive.org links? As referred to they are static and can be hotlinked to as the link structure will not change ie for one example: http://ia800309.us.archive.org/18/items/SERMONINDEX_SID4025/SID4025.mp3

…

On Sun, 21 May 2023 at 18:20, <<eWɘ>>yn ***@***.***> wrote: Greetings Brothers, Yes the collapse of Archive.org has significant result, but it should not effect this API, just the website. I have diversify my online hosting of audio sermons to make use of one main stable "yet not free" hosting solutions that I would suggest as an alternative to the current Dropbox and Archive solutions. New solution is wasabi.com They can host up-to 5 TB for only $5 usd per month, and then adding it behind a cloudflare CDN is super easy and a powerful dependable access point that will be most long lasting, with high volume. Here is a few links to look at: https://wasabi.com/resource/solution-brief/cloudflare/ https://www.cloudflare.com/en-gb/partners/technology-partners/wasabi/ https://wasabi-support.zendesk.com/hc/en-us/articles/360018526192-How-do-I-use-Cloudflare-with-Wasabi- I have just finished a complete container driven API <https://git.vdm.dev/joomla/wasabi> solution for the Wasabi API, that I will integrate with Sermon Distributor <https://git.vdm.dev/christian/Joomla-Sermon-Distributor>, and we can convert this simply for use with SI, if needed as it supports the whole CRUD, and listing in a simple small set of classes. What happened with Dropbox? I am moving away from Dropbox, as they are more and more showing signs that they will block and even delete our sermons simple because it is not agreeable to their own objectives. So yes, Dropbox is the current linked audio files in this API, I think what is happening is we are pushing up against their limitations of a free account and then they block further downloads. I can try and resolve that but reactivating that account, but I am moving all our own audio files for https://www.loudvoice.org/ and https://truechristian.church/ to Wasabi in the next few days. How does the API work now? In short we have a "custom themed" *YOURLS* instance: https://api.sermonindex.net/admin/ So that each link in the API for example: https://api.sermonindex.net/SID4076-download opens/redirects to https://www.dropbox.com/s/j36il881uzhtfp8/SID4077.mp3?dl=0 These redirecting links are managed by the *YOURLS* system database, and is easy to update. So if you all agree that I can move the audio files into the Wasabi system (*as part of my account, so I will sponsor this for as long as I can*), and then update the links we should get this resolved fairly quickly for all the existing links. Any donations towards this hosting will be helpful, but at-least you can know we've got this for the next few years. @sermonindex-dev <https://github.com/sermonindex-dev> I would need access to the *YOURLS* system database do do this, and it probably be a good time to just update everything again. To update the API Here Greg just need to give me a new dump of the database as we did in the beginning and I will generate the new API update of all the needed new data into this repository. Next steps? We I am going to move all the files anyway from dropbox to wasabi as a backup... and I would like to update the API links anyway to insure we stop getting slammed by the Dropbox limitations, as this as massively effected our websites as well. So its really up to Greg how quickly we incorporate these changes into Sermon Index. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD4ZU5MCIKFG6KQB4A3XHKBJ7ANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon*

[Llewellynvdm]

Okay, seems like the info I had about archive.org huge lawsuit must may have been a false alarm, not to sure who is speaking the truth these days. But I know the powers that be are going after it and are trying to end it in a huge way, be aware of that.

But sure we can link all to archive,org if you want that. We can completely decouple it from the YOURLS system and hard link it into the API.

I would need a few more examples to get the whole format setup and we can with the same step to update of the API (with the new data), also update the links at the same time.

decentralized hosting (remains the future)

I have been working hard on this and think I have resolved many key issues... we can explore this in more details some day.

side note of interest

Note, that since I need lots of data on my account at Wasabi, I will still move the files from Dropbox there. You see the way it works, is the more data you have the more free downloads you have, I currently have about 3,5TB of data already with them... and so another 300GB will not make that big of a difference, further more seeing that they have an easy to plugin CDN I am going that direction with all my static content.

The tool that we are using more and more with Wasabi is Restic a very powerful and easy backup tool. Here you can see how easy it is to setup the integration with wasabi+restic The most affordable, stable, and simple backup solution I have found to date, What is more is since we are working with S3 storage it is easy to adapt towards any other S3 profiler like MEGA.io and of course Amazon them selves.

But yes you need root access to a server to make use of these freedoms... I actually have a whole documented wiki that gives you step by step guidance how to most securely set this up for your own servers.

[sermonindex-dev]

brother Llewellyn, Yes I fully agree that decentralization is the big way forward. I would love to use your Wasabi as an additional hosting server if you uploaded all the sermons there. Does it give a straight forward folder system that is easy to link to, or does it give random urls like dropbox did? Towards archive.org here are some other examples of links: http://ia600501.us.archive.org/2/items/SERMONINDEX_SID0290/SID0290.mp3 http://ia600503.us.archive.org/32/items/SERMONINDEX_SID0219/SID0219.mp3 http://ia800504.us.archive.org/6/items/SERMONINDEX_SID19659/SID19659.mp3 would you have to know all the links or with this could you script something?

…

On Sun, 21 May 2023 at 22:42, <<eWɘ>>yn ***@***.***> wrote: Okay, seems like the info I had about archive.org huge lawsuit must may have been a false alarm, not to sure who is speaking the truth these days. But I know the powers that be are going after it and are trying to end it in a huge way, be aware of that. But sure we can link all to archive,org if you want that. We can completely decouple it from the *YOURLS* system and hard link it into the API. I would need a few more examples to get the whole format setup and we can with the same step to update of the API (with the new data), also update the links at the same time. decentralized hosting (remains the future) I have been working hard on this and think I have resolved many key issues... we can explore this in more details some day. side note of interest Note, that since I need lots of data on my account at Wasabi, I will still move the files from Dropbox there. You see the way it works, is the more data you have the more free downloads you have, I currently have about 3,5TB of data already with them... and so another 300GB will not make that big of a difference, further more seeing that they have an easy to plugin CDN I am going that direction with all my static content. The tool that we are using more and more with Wasabi is Restic <https://restic.net/> a very powerful and easy backup tool. Here you can see how easy it is to setup the integration with wasabi+restic <https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#wasabi> The most affordable, stable, and simple backup solution I have found to date, What is more is since we are working with S3 storage it is easy to adapt towards any other S3 profiler like MEGA.io <https://mega.io/objectstorage> and of course Amazon them selves. But yes you need root access to a server to make use of these freedoms... I actually have a whole documented wiki that gives you step by step guidance how to most securely set this up for your own servers. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD7A7ICR63LZDOURBVDXHLABBANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon*

[Llewellynvdm]

With regards to the archive.org its seems like the first part the [ia600501] part is unknown, how will I know what that will be? Is it based on the location of the folder so that all number two folder items are having the same "ia600501" sub-domain?

I can see the second number [/2/] is the folder number if I am correct, and the rest is generic and based of the file name, which we have. So if we can understand the way the first value is found we should be good to auto generate all links.

As for Wasabi, it will be direct links, that follow the folder and file names directly... I did start moving the files and here is one of the first links that will work:

https://wasabi.sermonindex.info/0/SID0001.mp3

To make that url be:

https://wasabi.sermonindex.net/0/SID0001.mp3

You simply need to add the following DNS update (On cloudflare, must be DNS on cloudflare):

And I need to rename the bucket in my wasabi account from wasabi.sermonindex.info to wasabi.sermonindex.net and then the links will be .net its that simple.

[sermonindex-dev]

brother, I added these records. When trying to add the "www" record I could not because we are already using this. Once this is done and working with this parameter: https://wasabi.sermonindex.info/0/SID0001.mp3 then do we just update to use this for the codebase for the app @Sherebiah Tishbi ***@***.***> ?

…

On Mon, 22 May 2023 at 21:38, <<eWɘ>>yn ***@***.***> wrote: With regards to the archive.org its seems like the first part the [ *ia600501*] part is unknown, how will I know what that will be? Is it based on the location of the folder so that all number two folder items are having the same "ia600501" sub-domain? I can see the second number [*/2/*] is the folder number if I am correct, and the rest is generic and based of the file name, which we have. So if we can understand the way the first value is found we should be good to auto generate all links. As for Wasabi, it will be direct links, that follow the folder and file names directly... I did a start moving the files and here is one of the first links that will work: https://wasabi.sermonindex.info/0/SID0001.mp3 To make that url be: https://wasabi.sermonindex.net/0/SID0001.mp3 You simply need to add the following DNS update (On cloudflare, must be DNS on cloudflare): [image: image] <https://user-images.githubusercontent.com/5607939/240081272-8cbc8657-1640-4009-8a05-ad7104553146.png> And I need to rename the bucket in my wasabi account from wasabi.sermonindex.info to wasabi.sermonindex.net and then the links will be .net its that simple. — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD6OMU4KXTEHURD7ANDXHQBIBANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon*

[Llewellynvdm]

AT the moment all links are in the API, and point to: http://api.sermonindex.net/SID0001-download so theoretically if the system is based on the API, we just need to update the API that is the whole point of an API. So we have two values:

{
    "title": "Sanctification - Part 1 (reading)",
    "url": "http:\/\/api.sermonindex.net\/SID13470",
    "size": "0",
    "format": "mp3",
    "scripture": "",
    "topic": "Audio Books",
    "description": "Alpheus Paget Wilkes (19 January 1871 \u2013 5 October 1934) was an English evangelical Christian missionary to Japan who was one of the founders of the Japan Evangelistic Band in 1903. In addition to extensive mission work in Japan, and touring South East Asia, he wrote a number of penetrating expositions of Christian scriptures.",
    "download": "http:\/\/api.sermonindex.net\/SID13470-download",
    "speaker_name": "A. Paget Wilkes",
    "_scripture": []
}

The first url is to open the then Dropbox hosted file on Dropbox, and be able to play it there. The other link download starts a direct download which is ideal for feeding the link into a player. We will update these two values in the API, or we can just keep the YOURLS system and just update the redirect there. Since both those links are redirected by the YOURLS system currently.

But if there where other work-around features build in to the app it will need to be updated for sure.

[Llewellynvdm]

Brother, about the DNS, you need only the one record.. not the www, as this is just how I have the .info setup to redirect to the main site. the only record we need is the sub-domain that would stream the audio from wasabi, so this means any sub-domain will work. Did you not read the documentation I shared at the outset of this conversation?

[Llewellynvdm]

So I mounted Dropbox to a AWS server (waited for all the file to download), and then with the following command:

aws s3 sync /home/ubuntu/Dropbox/Apps/sermonindex/sermons s3://wasabi.sermonindex.info --endpoint-url https://s3.wasabisys.com

Sync all the sermons from Dropbox to Wasabi, and it is nearly finished...

[Llewellynvdm]

Side note I only have up to folder 28 and the upload is now complete, I could generate a list of all the files that I have in this repository so we can compare it with the actual list...

[sermonindex-dev]

brother @vincent Larkin ***@***.***> are you ok to update with the wasabi links or are you fine to just continue with the archive links? could you maybe share here with @Llewellynvdm <https://github.com/Llewellynvdm> how you accomplished them? Llewellyn, if we do not use wasabi links in some of the apps I could utilize it was a backup server to host out the content, is there any charge for this or is it just still $5 ?

…

On Tue, 23 May 2023 at 13:59, <<eWɘ>>yn ***@***.***> wrote: Side note I only have up to folder *28* and the upload is now complete, I could generate a list of all the files that I have in this repository so we can compare it with the actual list... — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD47F5Z6Y3RK66RE3LTXHTUGHANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon*

[vincentlarkin]

Either site is fine in my opinion, both will work with the app 🙂. Thank you Outlook for iOS<https://aka.ms/o0ukef> を入手

…

________________________________ 差出人: sermonindex-dev ***@***.***> 送信日時: Tuesday, May 23, 2023 12:38:47 PM 宛先: sermonindex/audio_api ***@***.***> CC: Vincent L ***@***.***>; Author ***@***.***> 件名: Re: [sermonindex/audio_api] API Updated Needed? (Issue #10) brother @vincent Larkin ***@***.***> are you ok to update with the wasabi links or are you fine to just continue with the archive links? could you maybe share here with @Llewellynvdm <https://github.com/Llewellynvdm> how you accomplished them? Llewellyn, if we do not use wasabi links in some of the apps I could utilize it was a backup server to host out the content, is there any charge for this or is it just still $5 ?

On Tue, 23 May 2023 at 13:59, <<eWɘ>>yn ***@***.***> wrote: Side note I only have up to folder *28* and the upload is now complete, I could generate a list of all the files that I have in this repository so we can compare it with the actual list... — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD47F5Z6Y3RK66RE3LTXHTUGHANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon* — Reply to this email directly, view it on GitHub<#10 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AED7JL6LHNYJZO5FF26X7VTXHTY2PANCNFSM6AAAAAAYJSFOSQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Llewellynvdm]

I am not sure I fully understand what your asking @sermonindex-dev

Here is a breakdown of the Wasabi cost, with a nice slider: https://wasabi.com/cloud-storage-pricing/#three-info

The wasabi free egress policy explains that the best way to use Wasabi is when you have like 3TB of data and only 300GB of that is being downloaded regularly. If you have more downloads than the amount of data you have with them, like you have 3TB and the downloads is 4TB you will get a warring and they could close your account if it continues to happen. So the solution is huge amount of data, of which only a small amount is linked to active downloads. Which means it suites me very good if your not using the sermons that I have in my Wasabi instance, as it gives me more "valid" data which we can be use in emergencies, and its easy to do that because of the straightforward linking. So I would say lets move the whole API over to you archive links, and see how that works out.

In which case you would still need to answer my question that I raised in this comment.

[sermonindex-dev]

@vincent Larkin ***@***.***> could you share with @Llewellynvdm <https://github.com/Llewellynvdm> how you were able to figure out to hard code the archive.org links? I think we all agree now the best is to code all media to those links, correct?

…

On Wed, 24 May 2023 at 10:32, <<eWɘ>>yn ***@***.***> wrote: I am not sure I fully understand what your asking @sermonindex-dev <https://github.com/sermonindex-dev> Here is a breakdown of the Wasabi cost, with a nice slider: https://wasabi.com/cloud-storage-pricing/#three-info The wasabi free egress policy <https://wasabi.com/paygo-pricing-faq/#free-egress-policy> explains that the best way to use Wasabi is when you have like 3TB of data and only 300GB of that is being downloaded regularly. If you have more downloads than the amount of data you have with them, like you have 3TB and the downloads is 4TB you will get a warring and they could close your account if it continues to happen. So the solution is huge amount of data, of which only a small amount is linked to active downloads. *Which means it suites me very good if your not using the sermons that I have in my Wasabi instance*, as it gives me more "*valid*" data which we can be use in *emergencies*, and its easy to do that because of the straightforward linking. So I would say lets move the whole API over to you archive links, and see how that works out. In which case you would still need to answer my question that I raised in this comment <#10 (comment)> . — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALBHJD44KLRY52GXHQGGOR3XHYEYDANCNFSM6AAAAAAYJSFOSQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Greg Gordon* *Website: https://www.sermonindex.net <https://www.sermonindex.net>* *Twitter: https://www.twitter.com/sermonindex <https://www.twitter.com/sermonindex>* *Instagram: https://www.instagram.com/sermonindexnet <https://www.instagram.com/sermonindexnet>* *Youtube: https://www.youtube.com/sermonindex <https://www.youtube.com/sermonindex>* "Brethren, be encouraged; *a latter rain is yet possible. Seek it.*" *- C.H. Spurgeon*

[vincentlarkin]

@vincent Larkin @.> could you share with @Llewellynvdm https://github.com/Llewellynvdm how you were able to figure out to hard code the archive.org links? I think we all agree now the best is to code all media to those links, correct?
…
On Wed, 24 May 2023 at 10:32, <<eWɘ>>yn @.> wrote: I am not sure I fully understand what your asking @sermonindex-dev https://github.com/sermonindex-dev Here is a breakdown of the Wasabi cost, with a nice slider: https://wasabi.com/cloud-storage-pricing/#three-info The wasabi free egress policy https://wasabi.com/paygo-pricing-faq/#free-egress-policy explains that the best way to use Wasabi is when you have like 3TB of data and only 300GB of that is being downloaded regularly. If you have more downloads than the amount of data you have with them, like you have 3TB and the downloads is 4TB you will get a warring and they could close your account if it continues to happen. So the solution is huge amount of data, of which only a small amount is linked to active downloads. Which means it suites me very good if your not using the sermons that I have in my Wasabi instance, as it gives me more "valid" data which we can be use in emergencies, and its easy to do that because of the straightforward linking. So I would say lets move the whole API over to you archive links, and see how that works out. In which case you would still need to answer my question that I raised in this comment <#10 (comment)> . — Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALBHJD44KLRY52GXHQGGOR3XHYEYDANCNFSM6AAAAAAYJSFOSQ . You are receiving this because you were mentioned.Message ID: @.***>
-- Greg Gordon Website: https://www.sermonindex.net https://www.sermonindex.net Twitter: https://www.twitter.com/sermonindex https://www.twitter.com/sermonindex Instagram: https://www.instagram.com/sermonindexnet https://www.instagram.com/sermonindexnet Youtube: https://www.youtube.com/sermonindex https://www.youtube.com/sermonindex "Brethren, be encouraged; a latter rain is yet possible. Seek it." - C.H. Spurgeon

This is the code that seeks out the archive.org url:

``
logger.info(Url=${url});
console.log(nodeUrl.parse(url));

// 5/21/23: Updated to fetch from archive.org due to Dropbox disabling downloads which the sermonindex api downloadurl redirects to
// We have to parse the old Url for the Sermon id and then we can just download it from archive.org

let urlMetadata = nodeUrl.parse(url)
let sermonId = urlMetadata.path.substring(1)
let downloadUrl = `https://archive.org/download/SERMONINDEX_${ sermonId }/${ sermonId }.mp3`

logger.info(`Attempting to download sermon! Url=${ downloadUrl }, SermonId=${ sermonId}, Path=${ folderpath }`)

download(downloadUrl, folderpath, options)

``

Weather we use archive or wasabi, we can make the application work.