You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to self host recitations. This would have the following benefits:
Load on the main CDN would be reduced.
It would be easier for people to add new recitations, as they don't have to bother the quran.com team everytime (Maybe also reduces work for the team?)
It can give rise to a "forge" ecosystem (Tilawah Hub?) where many different people can upload their recitations. It would also reduce the load on the main CDN.
The above forges could have many other types of integrations - for example, automatic timings generation using quran-align or something similar. Maybe something for Tarteel AI to look into?
In terms of how to proceed with doing this, here is what I've been able to come up with:
The Qurʾān API would need to be decoupled into two - data and audio. Audio is a separate section in the API documentation right now, however, for example, endpoints like /verses have an optional field of audio which would need to be changed (Or be made reciter agnostic) .
The audio API would need an introspection endpoint that returns the reciters available on that instance.
Frontends would need to have a field to pick an audio instance root URL (can have default presets).
This is of course a massive task, but I think it would be an extremely useful feature.
The text was updated successfully, but these errors were encountered:
It would be great to be able to self host recitations. This would have the following benefits:
In terms of how to proceed with doing this, here is what I've been able to come up with:
data
andaudio
.Audio
is a separate section in the API documentation right now, however, for example, endpoints like/verses
have an optional field ofaudio
which would need to be changed (Or be made reciter agnostic) .This is of course a massive task, but I think it would be an extremely useful feature.
The text was updated successfully, but these errors were encountered: