The vTual Project: Build Alpha v.0.1 Report, Part 4
It's been roughly three weeks since the last update about Part 3 of vTual Build Alpha v.0.1 Report was written. This blog post will summarize what has happened.
Major Change
The scope of major changes encompasses aspects that have a significant impact on the system and UI/UX, directly influencing their functionality and user experience.
Quota Optimization
Most major public services, such as YouTube or Twitch, typically offer data exchange that can be accessed by the public through their official APIs. To run vTual services, we heavily relied on official APIs to get this public datas.
However, please note that the quota limits set for these APIs are often quite restrictive, making them insufficient for applications that require a significantly larger and more frequent data exchange such as public aggregator like vTual.
Given the constraints, there are a couple of options to consider when attempting to operate a project with limited quotas.
Firstly, one could propose an increase in the limit, which would provide more room for maneuver or even research for new possible feature.
Alternatively, optimizing the API integration to make the most of the existing limited quotas is also a viable solution. By streamlining the integration process, it's possible to achieve greater efficiency and make the most of the available resources, ultimately allowing the project to move forward despite the initial limitations. We have implemented both of these options in this three-week period.
When it comes to quota optimization, the progress has been remarkably effective.
You see, initially a single check could consume the entire quota allowance because we are still implementing "one API request for one item" -- which means if there are 100 items to check, then it will use up 100 quotas.
However, the documentation states that one API request can actually serve multiple item. After rewritting entire backend for Youtube and Twitch integration, now the usage has been significantly reduced to a relatively small amount compared to before.
By leveraging this optimization, we were able to significantly enhance our efficiency and reduce the overall quota consumption. This improvement not only enhances efficiency but also allows for more extensive operations within the same limits. As a result, the project can now function more smoothly, making better use of the available resources while minimizing waste API request.
Technically speaking, for example; One Youtube API request can accommodate up to 50 items for certain request, such as /videos endpoint. This means that if there are 100 videos that need to be checked, now the quota used is only 2, instead of 100.
Quota Increase Possibility
As mentioned earlier, we have also explored the possibility of increasing the quota limit for our vTual project.
Although there is a possibility that requests may be denied, as experienced by other developers, I am uncertain about the specific approaches they took when submitting their requests. Like do they really explain their intentions and goals clearly?
I remain optimistic about collaborating with the YouTube team to clearly articulate the intent, objectives, and implementation of the vTual integration with their API.
And I believe that by fostering open communication and providing a comprehensive understanding of our project, we can build a strong case for our request and demonstrate the value it brings. This proactive approach not only reflects our commitment to the partnership but also enhances the likelihood of a positive outcome.
So on October 20, 2024 I submitted a request for YouTube quota increase.
By leveraging the optimization of API requests and the potential for increased quotas, I am hopeful that vTual can operate even more effectively, ultimately providing greater benefits to the content creators involved.
Last Edit for following extra paragraph: November 8, 2024.
As per what I wrote above, Since October 20, 2024, I have submitted a request for quota increase. Throughout this process, there have been no significant changes on either the frontend or backend, if it is not necessary.
This approach was taken to ensure that all aspects meet the requirements for the quota increase as stipulated by the YouTube team. A small error in any changes could potentially result in previously approved points being rejected once again, which could ultimately prolong the quota increase process.
Therefore, during this process, we have also taken the initiative to take a brief pause from the development of vTual and other Silverspoon services.
This decision comes in light of the fact that the development of vTual has consumed a significant amount of time over the past year.
By stepping back for a moment, we aim to recharge and reassess our strategies, ensuring that when we resume, we can bring fresh perspectives and renewed energy to our projects.
Let us hope that this process can be completed soon and successfully realized, allowing vTual to be launched to the public. The anticipation surrounding this release is palpable, and we are eager to share our hard work and innovation with everyone.
Best regards,
"Kurokuma Wakaba"