This is because some "minor" changes have a significant impact, that leading to updates in various aspects and code revisions, here and there.

Background​

There are several underlying issues that have driven the development towards version v.0.1.2, including the following:

Email Failover​

There are several actions that require approval and must be communicated via email, such as password reset requests.

Therefore, we have designed a failover configuration for our emails to ensure that the messages we send consistently land in your inbox rather than being marked as spam.

To maintain system stability, emails will now be sent periodically rather than instantly. Therefore, please be patient and wait to receive the email for the action you need.

The sender's email address has also been updated to use the vTual domain. Previously, it utilized an email address associated with the entire Silverspoon project, but now the sender's email reflects vTual's branding.

Storage Server​

Even before vTual exist, our "legacy" infrastructure is primarily already located in Europe, including its storage servers.

This storage server is based on our own research conducted for the operational service that came before vTual, which was a file hosting service.

Since file hosting operations require storage servers with large capacities and high bandwidth, we sought a service that could balance these needs while remaining relatively affordable.

After careful consideration, we somehow found a storage server provider that meets all of our criteria.

After we discontinued our file hosting service, the infrastructure and configuration of this storage server remained in our possession. Subsequently, it was repurposed for internal storage for all Silverspoon projects, including vTual.

However, several challenges arose afterward, particularly concerning performance and latency after the vTual infrastructure was fully relocated From Europe to Asia.

Durability and accessibility also posed unique challenges, considering that this storage server lacks duplication and caching features.

The solution: We spun up another storage server that addresses all the existing issues. This new server is located in Asia to cut down the latency, it's offers physical duplication and have built-in caching features.

• Old implementation: Local object (image, video, etc) in Europe > Caching in CDN (Object in Asia for Asian visitor, etc).
• New implementation: Local object (image, video, etc) in Asia > Cached physicaly at the nearest duplicate location to the visitor (Object duplication in Europe for European visitor, etc) > Caching in CDN (Object in Europe for European visitor, etc).

As a result, the storage server issues have been successfully resolved after making various adjustments. Performance and durability is expected to also improve significantly, as caching will be implemented on both the physical side and the CDN.

The links from the new storage server have also been simplified and are now more closely associated with vTual. Previously, the links were for the entire Silverspoon project, but now both public and private objects utilize vTual's branding.

Sitemap​

A sitemap is a component that facilitates search engines, such as Google, in navigating the content of our website. Recognizing the importance of a sitemap, I ultimately decided to implement this feature.

What I needed was a sitemap implementation that could organize content by day, while the official documentation and its related tutorials only provided examples for creating a sitemap for all existing content.

Although this method is simpler, it requires the database to work much harder, and I am not fond of this approach to implementation. So I chose to "freestyle" my code, as I was unable to find a solution for my specific idea.

After successfully experimenting, I discovered that Google does not accept sitemaps stored at external addresses other than the same site address registered as a property.

You know, this issue arose because I had saved the sitemap on the aforementioned storage server. As a result, the implementation of daily sitemap storage and indexing has been redone, with the data now being stored on the main server of vTual.

Let us hope that in the future, vTual's content can be effectively indexed by search engines.

Internal Touch Up​

I feel that I have been too focused on optimizing the integration of external services, which has led to several internal aspects being written in a less than optimal manner.

As a result, I have decided to make some adjustments to the internal repository in order to optimize the running code.

Verdict​

At the very least, the four points mentioned above represent significant developments rather than mere minor changes.

Therefore, I am categorizing this update as one that elevates the application version to v.0.1.1 and I hope that this will further enhance the functionality and usability of vTual.

This January marks a significant milestone, as version 0.1 of vTual has been finalized and is now generaly available for public launch.

Write More Insight!​

Aight. As noted in the vTual changelog, the project has been in development since early 2024, specifically around March. This period coincided with my decision to resign from my previous job for various reasons.

This transition marked the beginning of an exciting once-in-a-lifetime journey for me, which allowing me to dedicate my time and energy to bringing this passion project called vTual come into life. However, the journey was not without its challenges.

You know, a significant number of shortcomings arose. Particularly due to a lack of thorough planning, which led to several complete overhauls of the codebase.

Additionally, I discovered that my experience was not quite sufficient to manage a project of this scale effectively. While the concept may appear straightforward at first glance, translating it into a functional, optimized and user-friendly platform has proven to be a multifaceted challenge.

As a result, the development process took nearly a year to complete, far exceeding the initial estimate of just 3 to 6 months.

But the storm has passed, as the development of vTual version 0.1 has been successfully completed and is now available for general public use. At least that's the plan.

What Does it Mean?​

Okay don't be angry. On the surface, the vTual project is already fully operational and can be accessed and utilized through its official website without any obstacles. However, the information regarding this launch has not yet been publicly announced.

So only those who are already aware of the project can take advantage of its features at this time. YTTA.

Why Do That?​

During the brainstorming process for the initial ideas and concepts, it was concluded that vTual will adopt two unique types of approaches regarding user management.

The first approach allows users to register and manage their own accounts independently, giving them control over their experience.

And the second approach enables administrators to manage accounts on behalf of the creators, acting as temporary representative for them. When the said content creator wants to manage their own profile, they just have to submit a claim.

But due to our very limited marketing budget, our current focus will be on adding profiles of various content creators to the platform, since a barren battlefield is not beautiful.

And once we have a substantial number of profiles, I will consider fully sharing the message to the world that vTual is not just a mere dream, but a tangible reality.

Also for the convenience of its users, I need to finalize the documentation related to this project. Since comprehensive documentation is crucial for helping users understand all aspects of vTual, including its features and functionalities.

By ensuring that this information is clear and accessible, I aim to enhance the user experience and empower individuals to make the most of the platform.

"So please try us when we are ready."

Is Everything Good?​

Depending on the context, I can explain it as follows:

About the Codebase​

Currently, vTual is at version 0.1, which means that the codebase is still in a stage where it functions adequately but is not yet optimized to meet all needs.

It's akin to trying to sleep comfortably in a room cluttered with trash; While its possible to get by, the environment is far from ideal.

However, I have previously worked with a codebase that was far worse than a decaying radioactive septic tank from Chernobyl. Afaik this particular "codebase" was even rented out for almost whooping $40,000 a year to numerous unfortunate clients, many of whom ended up suffering significant losses as a result of using it.

So in light of that comparison, I believe the vTual codebase is in relatively good shape.

About the OpEx and CapEx​

Recognizing that a project like vTual requires a robust and complex server infrastructure and configuration, I have allocated OpEx amounting to at least few hundreds of dollars just for the first quarter of operational.

While this amount may not seem substantial to some, it is quite significant for me personally, especially considering that this is just a small hobby project. At that time my justification was that "This investment is crucial to ensure that the platform can handle user demands and function smoothly from the outset."

However, I later conducted a reality check to reassess whether such an investment was truly necessary at this stage. Like you know, can someone guarantee the success of this project?

The answer is, of course, was a hard big no. Then it became clear that while the initial allocation was well-intentioned, it might not be essential just yet.

This realization prompted me to reevaluate my priorities and focus on more immediate needs for the project. So I decided to cancel all plans regarding various plans and configurations about the whole server infrastructure design.

Such plans like setting up a high availability environment for a centralized storage servers, series of distributed database server or any other functions that theoretically could operate in a serverless environment; It is all gone now, so no more overcomplexity and overspending.

Goodbye to you annoying but loved portainer, haproxy, patroni, citrus and the rest of another little devil. You all somehow forced me to be an overnight DevSecOps.

Before revealing my own server benchmark, for comparison, I conducted a benchmark using YABS against servers from Hetzner Cloud with significantly higher specifications:

• CPX41 series, which features 8 cores of Epyc 7002, 16 GB of RAM, and 240 GB of SSD storage, priced at €24.70 per month, per server.
• CPX51 series, which features 16 core of Epyc 7002, 32 GB of RAM and 360 GB of SSD storage, priced at €54.40 per month, per server.

And that's the final benchmark of the server available on Hetzner Cloud.

So, what about the server I am using? Its specifications are likely something along these lines:

• 4 cores of Epyc 9554, 16 GB of RAM, and 200 GB of NVMe storage.
• 4 cores of Epyc 7443, 16 GB of RAM, and 200 GB of NVMe storage.

And that's the final benchmark among the many servers that I could, should, and truly regretted having to cancel. These two bad beautiful bitches is just born wild.

I won't mention the price or the provider, but I certainly had an overshadowing goal in mind when including this comparison.

And just as a fun fact, the server mentioned above was purchased during Black Friday, which means the price was significantly "more" reasonable.

In addition to the main server mentioned above, there are several other microservers that I cannot cancel because they have already been purchased for the upcoming year.

At first, the initial purpose of these microservers was to serve as part of a series of servers dedicated to database-related needs.

And lastly, as for the CapEx, I think that there is nothing important I can share since this project does not have fixed assets that require payment, such as buildings or other significant expenses.

About the Server That Will be Used​

Sorry, I may have cut that point quite absurdly.

In a previous changelog, I shared an update regarding the plan to relocate the server infrastructure from Asia to Europe, which is apparently Germany, due to the relatively lower costs but with higher specification.

While it is true that I subsequently purchased a considerable number of servers in Europe, this does not mean that the servers located in Asia have become inactive. You know why? This is because the servers in Asia were also purchased on an annual basis. sobs.

Initially, these Asian servers were intended for specific system needs, such as handling email-related services and managing SSL certificates provision and renewal.

But since the servers in Asia were purchased on an annual basis, It is safe to say that, as a result, I do not need to spend a lot of money on operational costs at least for the next year.

Yep absolutely as you think. All operational needs of vTual, including the website, database, websocket and more, will rely on these two significantly inferior servers located in Asia, when compared to what used to be in Europe.

Several other functions and operations, such as the need for sending notification emails or load balancing for storage servers, will be managed by appropriate serverless services that specialize in these special tasks.

At least until vTual demonstrates clear signs that it requires higher server resources, then upgrading the server will be prioritized once again.

About the Remaining OpEx Budget​

I once said that "I have allocated OpEx amounting to at least few hundreds of dollars just for the first quarter of operational" so, what will happen to the budget after concluding that we will utilize the previously available servers in Asia?

First and foremost, I plan to use the funds to subscribe to Twitter Blue as part of the promotional strategy for vTual, particularly targeting the vTuber community.

Promoting the platform while engaging with potential users seems to be an effective approach I intend to take.

By leveraging Twitter's features, I can enhance visibility, connect with potential users, and foster a sense of community around vTual.

Secondly, the budget may find its way back into my personal savings, which seems to be growing colder after being left with fewer occupants for quite some time.

About the Future Update​

vTual will continue to be actively and regularly maintained, although major updates may no longer be the top priority.

For example, processes such as bug fixing and routine maintenance will remain ongoing to ensure the platform runs smoothly.

As a case in point, there was a significant overlap between two schedulers yesterday, which led to the server becoming overloaded by clogged tasks.

This unexpected situation also caused a dramatic spike in YouTube API usage, skyrocketing from the usual 1,500 requests per day to an astonishing 212,000 requests between January 14th - 15th.

But by midday on January 15th, the issue was resolved, allowing YouTube API usage to return to normal levels. As a result, from January 16th onward, the API requests seems stabilized.

This situation arose because testing in the staging environment was conducted using a relatively small dataset, around 2,000 to 5,000 data.

However, once the system transitioned to the production phase, the volume of data increased significantly up to 30,000 just in a matter of days, thus leading to unforeseen challenges.

Therefore, once again, vTual will continue to be actively and regularly maintained due to the presence of numerous potential risk scenarios that could threaten the system's operations. So don't worry because I'm still active maintaining, even though the addition of new major features may be slightly deprioritized.

But as a result, major ideas such as rewriting the better version of the codebase, localizing the language, adding new authentication methods, and implementing several other features may take quite a while to come to fruition.

However, one of the major update plans that may be implemented in the near future is the addition of a TikTok tracker, which I hope can be realized smoothly.

Update on TikTok implementation: After conducting research on the official documentation of the TikTok API, it can be concluded that TikTok API does not offer any public information for developers. ALL DATA related to an individual can only be accessed by the person themselves.

This means that ALL DATA accessible through the TikTok API, including general information such as names, bios, and video content, can only be accessed by the individuals themselves. Thus, vTual is unable to manage any information regarding TikTok profile of a user.

Fyi, services that have previously been integrated such as Twitch and YouTube also impose restrictions and limitations on certain information. But these restrictions and limitations only apply to data that is considered private, such as membership lists that CAN ONLY be accessed by the person themselves.

Tldr: Twitch and YouTube allow access only to public information, while all data on TikTok is categorized as private.

There are several options available for implementing TikTok API as "public information" however most of these options are unofficial, paid, and/or expensive.

We will not force implementation by taking this option, so that the TikTok integration was officially canceled.

Where Are You Going?​

At this point, this posts may seem like a rather melancholic farewell letter. However, the reality is that I am not going anywhere. In fact, this marks a new beginning, albeit one that doesn't align with the original vision I have envisioned.

As I mentioned at the beginning, vTual is a project I have been working on during my job search after resigning. After all, radioactive nuclear is toxic, you know?

Unfortunately, job opportunities did not come my way in 2024, possibly because I lacked an active portfolio to showcase my skills and experience. You know what's funny? This simple project could even be completed while I'm looking for a new job since early 2024. Lmao.

However, now that vTual is active and has taken on its own form, I intend to use it as a portfolio for potential future employers who didn't employ me in Chernobyl-like environment. This is why I will continue to maintain vTual actively, since vTual is still far from mature as a product.

However, if vTual has the potential to become a primary choice in my career, I believe I could dedicate the best version of myself to making it an outstanding platform. Well, who knows?

Verdict​

In conclusion, I hope that vTual can have a positive impact on all of us, aligning with the core essence of everything: Silverspoon.

My wish is for everyone connected to Silverspoon, you and me, to experience goodness and prosperity. May this initiative bring about beneficial outcomes for all involved, fostering a sense of community and shared success.

But despite the hurdles, this journey has led me to the realization of something quite rewarding and fulfilling.

What Is Going On?​

I am so thrilled to announce that the vTual Project, a simple pilot concept that I have envisioned since 2022, finally come to fruition: It is almost ready for public launch!

The term "almost" is used because there are still a few minor adjustments needed before the project can be fully released to the public, as these adjustments primarily involve the implementation of certain development ideas and infrastructure improvements.

Development​

In terms of feature implementation and system optimization, I can confidently say that vTual v.0.1 is essentially complete and aligns well with the initial targets we set. Like external needs, such as the request for an increase in API quota from the YouTube team, have also been successfully approved. Quota optimization for both Youtube and Twitch API is also done.

However, there are a few minor additional internal features, such as a fanbox, that I would like to incorporate into vTual.

If these enhancements do not disrupt our schedule, I plan to integrate them into v.0.1. However, if it appears that adding these features could potentially delay the release, I will prioritize them for inclusion in the roadmap for v.0.2 instead.

This approach ensures that we maintain our timeline while still considering valuable improvements for future versions.

Infrastructure​

We all know that vTual, as a project, will need to store and process a significant amount of data. The volume of data involved may well exceed anything I have handled throughout my career as a programmer so far.

Furthermore, vTual will also play a crucial role as my portfolio as a programmer, showcasing my skills and real-life expertise in a tangible way.

And most importantly, I have a deep personal affection for vTual, embracing both its strengths and its shortcomings.

With countless reasons highlighting the importance of vTual to me personally, there is no justification that could deter me from splurging investing in its infrastructure.

The next paragraph will be particularly fascinating if you are a nerd intrigued by the foundational infrastructure utilized by vTual.

After conducting several experiments and carefully considering the operational costs, we can conclude that the current details of the infrastructure lineup are as follows:

Server for Web Server​

To operate vTual effectively, the current server infrastructure designated for web server purposes has the following specifications: Powered by 4 cores of EPYC 9554 Genoa, equipped with 16 GB of RAM, NVMe storage and a premium network port of 2 Gbps. Premium DDoS protection is also included in the hundreds of Gbps figure.

The server operates on a high-availability cloud hosting model, which means that all components are designed to perform auto-healing in the event of a failure in any part of the system.

These specifications have been carefully selected to ensure optimal performance and reliability, allowing us to meet the demands of our users while providing a seamless experience.

Server for Database Server​

To operate vTual more effectively, I have allocated specific server for database-management purpose that has the following specifications: Powered by 4 cores of EPYC 7443P Milan, equipped with 16 GB of RAM, NVMe storage and a premium network port of 2 Gbps. Premium DDoS protection is also included in the hundreds of Gbps figure.

The server provider and it's location is the same as that used for web server purposes that i mentioned above; however, the node are different to ensure redundancy in case of a failure in one of the nodes.

Data processing will also require intensive read performance for the database, which is why I have added two slaves servers with following specifications: Each of these slaves are equipped with 2 cores of EPYC 7401P Naples, 4 GB of RAM, NVMe storage and a network port of 1 Gbps.

This slave server comes from a different provider and does not offer significant performance or robust features compared to the main server. However, considering that it is intended solely as a supplementary server, I believe it is more than adequate for our current needs.

Unused Server​

I have written before about the reasons for the changes in infrastructure used by vTual.

At present, there are approximately two unused servers that have been purchased for the long term. These idle servers are located in the Southeast Asian (SEA) region, specifically in Indonesia and Singapore.

The main reason for opting for a long-term purchase was the opportunity to benefit from discounted prices when acquired on an annual basis.

But tldr; The server market offered by Europe presents more "strength" with relatively stable pricing that is easier on the budget. As a result, the operational infrastructure has been relocated to Europe!

Nevertheless, these servers will still be utilized for other beneficial purposes that contribute to the advancement of vTual. One of the ideas currently being developed is to prepare them for use as game servers.

This initiative not only allows us to maximize the potential of our existing resources but also opens up new opportunities for engaging with our audience in the gaming community.

By repurposing these servers, we aim to enhance our offerings and create a more dynamic environment for users, ultimately driving growth and innovation within the vTual platform.

Absolutely Stupid​

So far I must admit that the development of vTual has been quite an intense journey.

Beyond the fact that vTual is built on an open-source project (under Laravel, Composer and it's environment), I have undertaken all the research and development on my own, starting from the ground up as a newbie programmer. The process has been both challenging and rewarding, as it has required me to dive deep into various aspects and concept of software development.

I must also acknowledge that the expenses associated with running the infrastructure are neither cheap nor easy to manage. The development of vTual has indeed taken a toll on me, both physically and mentally, as well as financially.

Do you want to hear the craziest part? After all the effort, hard work, and investment I've put into this project; I have yet to even consider issues related to promotion and monetization strategies to ensure that the entire infrastructure can eventually be financially sustainable.

In short, the series of events surrounding vTual has been reckless and stupidly stupid. However, despite all the chaos, I truly love the journey it has taken me on.

Every effort I make is aimed at ensuring that vTual operates smoothly and meets the necessary requirements, so one or hundreds of trials seem necessary to face in order to achieve maturity for vTual as a product.

Public ETA​

November will conclude with the organization of our infrastructure, and December is likely to be dedicated to testing sessions.

Given this timeline, the earliest estimated time of arrival (ETA) I can provide for public access is early 2025.

Memento​

From overthinking...

...to countless brainstorming that won't fit the image...

...VNS, the foundation of vTual was born.

Fucking big thanks to these two distinguished middlelight resident.

This blog post will be the final report from the development side of vTual version 0.1 before its release.

Ongoing Progress​

There are numerous developments currently underway on the operational side of things.

One of the key focuses is the optimization of the backend, particularly concerning the implementation of external APIs, such as those from YouTube and Twitch.

The goal is to maximize the usage of these APIs without exhausting the quota before the reset period occurs.

The external APIs from YouTube and Twitch are crucial, serving as the backbone of vTual's operations in delivering up-to-date information about your favorite content creators activities.

When the API quota is depleted, data retrieval becomes impossible, which can significantly hinder or even stop the service's ability to provide timely updates.

While the Twitch API does not seem to offer the option for quota increases, YouTube appears to provide an opportunity for such requests. vTual submitted a quota increase application on October 20, and the process is still ongoing as stated on last report.

This procedure can be quite lengthy as evaluations are typically conducted on a weekly basis, and there are numerous factors that the YouTube team must assess to determine whether vTual meets the criteria for a quota increase. These factors include both the user interface and user experience, as well as the technical implementation.

vTual is planned for release once this process is completed. In the meantime, it will remain in a closed sandbox environment, where continuous optimizations will be carried out to enhance its performance and functionality.

This careful approach ensures that vTual will be well-prepared for its eventual launch, compared to a hasty decision.

Future Progress​

As a programmer, skill development is essential, especially in a field where technological advancements occur at a rapid pace. A moment of complacency can lead to the emergence of new technologies within minutes.

This dynamic is also reflected in my relationship with vTual; whenever a new feature idea arises, I find myself needing to learn various new concepts to bring that idea to fruition.

During its development from early February to November 2024, I have absorbed a wealth of new knowledge while also striving to enhance my existing skills for greater optimization.

Throughout the development of vTual, particularly in version 0.1, I feel a sense of satisfaction and pride in the final product, as it aligns with the vision I have held since 2019-2020, the year when the idea for vTual was born.

However, as a programmer, I recognize that the codebase of version 0.1 is overly complex, suboptimal, and redundant.

Long-term maintenance will be challenging if we continue to rely on this codebase. While optimization is one potential solution to address these issues, I do not believe that a complete overhaul of the 0.1 codebase is a straightforward option.

The core problem lies within the very foundation of the codebase itself. Initially, vTual was developed with a "just make it work" philosophy, resulting in many modules being written without proper standardization. This includes arbitrary variable names, inefficient loops, and repetitive function definitions, among other issues.

It wasn't until around mid-August that the development of vTual began to implement the DRY ("Don't Repeat Yourself") principle, which ultimately led to wrapping each action into reusable modules and standardizing variable names, among other improvements. In short, the vTual 0.1 codebase is a blend of order and disorder.

While optimization on this scale is still feasible, it requires extra effort that may be equivalent to starting from scratch.

Given that the range of features offered by vTual is still relatively limited, I believe that a "rewrite" would be a much easier and more efficient option.

Not only would this approach allow for a more structured development process, but it would also enable the incorporation of many new elements that could enhance the latest version compared to the current 0.1 codebase.

That said, the decision to rewrite remains a topic of discussion. I have yet to determine the right time to embark on this journey—whether it will be realized in version 0.2 or triggered by specific case, such as the release of Laravel 12.

While there is no definitive timeline for this decision, I remain ambitious about fully optimizing vTual and adding new features in the future.

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"

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.

Revamped Front Page​

As a programmer, I must admit that I'm more comfortable with backend development than frontend design. That's why I relied heavily on Bootstrap for these 5 years, which provides a range of preset classes to simplify the design process. Despite this, I still struggle to fully grasp the principles of good UI/UX design.

Throughout my journey, I've come to realize that the initial design of vTual's interface was stiff and uninviting. It's ironic and dangerous, considering that a well-designed interface is essential for capturing users' attention and interest.

From the design above, you can probably tell how uninviting the layout I created was. It's a far cry from the modern, sleek designs that we've grown accustomed to, and I can only imagine how off-putting it must have been for users who encountered it.

After careful consideration, I finally decided to "invest" in vTual's main interface by conducting market research on designs that could potentially meet the platform's needs in a marketplace.

I spent a significant amount of time weighing my options, carefully evaluating and filtering through various designs. Ultimately, I found a template that I believed would be a great fit for vTual, and I decided to purchase it. This decision marked a significant turning point in the platform's development, as it allowed me to revamp the user interface and create a more modern, visually appealing, and user-friendly experience.

By leveraging a pre-designed template, I was able to tap into the expertise of professional designers and bring a level of polish to vTual that I wouldn't have been able to achieve on my own. Despite this, the new template presented a fresh experience and challenge.

You see, I was accustomed to using Bootstrap's "UI kit" which is essentially a pre-built, plug-and-play solution. While it's convenient, it also means that the design may end up looking uniform or similar to many other websites.

In contrast, the template I purchased is built using Tailwind, a "utility-first" framework that takes a DIY approach. This means that I have the flexibility to create a unique design, but it requires extra customization effort.

It's a trade-off, seriously. I have to invest more time and energy into tailoring the design to my needs, but the payoff is a more distinctive and personalized look for vTual. It's a departure from my comfort zone, but I'm excited to learn and grow from this experience.

So far, the design of vTual is still largely based on the default presets provided by the template, with only minor modifications to suit our specific needs.

This is because I haven't had the luxury of dedicating sufficient time to fully learn and master Tailwind. As a result, I've had to rely on the template's built-in features and configurations, rather than fully customizing the design to my vision.

But after seeing the preview of the new design, I'd say that it's definitely a step in the right direction, as the new look is somewhat more refreshing compared to the original design, right?

Infrastructure Changes​

Since the vTuber culture originated from Japan, the vTuber market and fanbase is quite large in the Southeast Asian (SEA) region. Also since I'm based in Indonesia, I initially felt that having the infrastructure in SEA would be ideal.

Not only would it be closer to our target market, but as a developer, I would also find it easier to maintain and manage the infrastructure. As proximity would allow for faster response times, easier troubleshooting, and more efficient maintenance, which would ultimately benefit our users.

Additionally, being in the same region as our target market would enable us to better understand their needs and preferences, allowing us to tailor our services to meet their expectations more effectively.

With this in mind, I choose a multiple provider that virtually or physically located in Singapore to host server for website, server for database, server for email, server for storage, CDN, and also serverless infrastructure.

By having a localized presence, technically we're able to reduce latency and improve overall performance for potential users in SEA, as we could providing a faster and more reliable experience. This strategic decision was made to cater to the growing demand for digital services in the region, and to ensure that vTual is well-positioned to meet the needs of its users in SEA.

But sadly, the issue is that infrastructure in Singapore (or SEA as a whole) is a luxury commodity. Even during the testing period, where all variables can still be controlled, the costs are already draining my pockets.

I worry that if this continues, it will be extremely challenging when we reach the launch stage, not to mention when it comes to expansion.

The high costs of infrastructure in the region could become a significant obstacle to vTual's growth and scalability, making it difficult to sustain and expand our operations. This is a critical concern that I need to address in order to ensure the long-term viability of vTual.

However, decisions must be made, no matter how difficult or heavy they may be. After careful consideration and taking into account vTual's financial capabilities, I finally made the decision to relocate our entire infrastructure to Europe, where most providers can offer same or even better quality infrastructure at a lower cost.

This was not an easy decision, as it meant abandoning our initial plan to seamlessly operate in the SEA region. However, the financial realities and the need to ensure the long-term sustainability of vTual made it a necessary choice.

By making this move, I hope to be able to reduce costs, improve performance, and create a more stable foundation for vTual's growth and expansion. It's a calculated risk, but one that I believe is necessary for the future success of vTual.

Worry not as our infrastructure in Europe is still equipped with much more powerful hardware and networks compared to what we had in Singapore.

This significant upgrade will ensure that our services are delivered with even greater speed, reliability, and performance, despite being located in a different region.

Minor Challenge​

The scope of minor challenge encompasses aspects that have a significant impact on the system development, directly influencing the development progression.

Almost Land on Juicy Project​

I guess about two week ago, I received an intriguing offer to develop an application for one of the travel companies. What caught my attention, of course, was the total price tag of the application, which was substantial due to its complexity.

The project proposal outlined a comprehensive and feature-rich application that would require a significant amount of development time and resources. While I was initially hesitant to take on such a large project, the potential reward was too great to ignore.

So I decided to carefully consider the proposal and weigh the pros and cons of accepting the offer. Because if I were to accept this offer, I would have to put the development of vTual on hold for several months to come.

However, since I feel that vTual is still lacking in terms of financial resources, I decided to accept the offer as a means to boost our financial capabilities and support the future development of vTual. By taking on this project, I hope to generate a significant amount of revenue that can be reinvested into vTual, allowing us to accelerate our development roadmap and achieve our goals more quickly.

I think that it's a strategic decision that will require some short-term sacrifices, but I believe it will ultimately benefit vTual in the long run.

However, since the potential client missed the negotiation deadline by a week without giving a single word, I got the feeling that this project wouldn't run smoothly even if it can be forced, so I didn't have the intention to do any follow up on it.

You know that I was prepared to put vTual on hold to pursue this opportunity, but their lack of responsiveness has given me a convenient reason to exit.

I can now refocus my attention on vTual without any distractions, and I'm relieved that I don't have to compromise on our development timeline. It's a welcome turn of events, and I'm excited to dive back into vTual's development with renewed energy and focus.

I will explain that this doesn't mean I'm easily dismissive of projects with significant value and prospect. However, if a project lacks mutual respect, then personally i think it's not worth continuing, especially considering how chaotic and undervalued the developer community is in Indonesia.

Conclusion​

So, it seems that vTual's development is safe for now and thank you for being a part of this exciting journey!

Last Edit for following extra paragraph: October 11, 2024.

After experimenting with customization on Tailwind for the past few days, I was surprised to find that a significant number of default classes were unavailable for use. As a result, I ultimately decided to purchase an alternative template built on Bootstrap, which I'm more familiar with, to accelerate the development of the visual interface.

This decision was largely driven by the need for efficiency, as I've had prior experience working with Bootstrap, and I'm confident that it will enable me to work more quickly and effectively.

By leveraging a framework I'm already comfortable with, I can focus on refining the design rather than spending excessive time figuring out the intricacies of Tailwind.

The irony, however, lies in the fact that despite the template's visually appealing design which perfectly aligns with vTual's needs: The template developer behind it seems to have made a rather questionable decision.

They decided to combine the entire javascript library into one file called main.min.js and then minified it. In fact they don't even provide the unminified javascript, making it very difficult to categorize which javascript is needed and which is not.

This left me with a staggering 14 MB of main.min.js and i wonder why they still deeming it suitable for use in a production-ready product.

This raises some eyebrows, as such a large file size can significantly impact page load times and overall user experience. It's puzzling that the developer didn't consider the potential performance implications of including such a massive file, especially in today's fast-paced digital landscape where speed and efficiency are necessary.

Let's say this is a skill issue from my side, but please... It would be better if such paid product made it easier for the buyer.

And you might be wondering why I still went ahead and purchased the template despite knowing about the hefty javascript file. Well, let me explain!

As a developer and content creator, I'm fortunate to have a relatively fast internet connection with speeds of around 100 Mbps. When I first previewed the template before buying, the 14 MB javascript file didn't seem like a significant issue, likely due to my robust internet connection.

The file loaded quickly, the visuals are appealing and I didn't experience any noticeable lag or performance issues: heck it's perfect. Everything is theoretically applied when accessed 100 Mbps internet speed.

It wasn't until I was about to upload all the static assets after completing the UI development that I stumbled upon this issue.

I was taken aback when I saw that the total file size was nearing 50 MB, despite having a relatively small number of files.

My initial reaction was, "How is this possible? What's causing the bulk of the file size?" - and that's when I discovered that the 14 MB javascript file was the main culprit, courtesy of the template's main main.min.js javascript file.

It was a bit of a shock, to say the least, and I couldn't help but wonder how this oversight had slipped through the cracks.

I mean I don't really care if the total size reaches hundreds of MB or even GB, after all disk space or bandwidth is not really a problem for us. But a single 14 MB javascript file is a big blow.

You see, when we purchase a template legally we're entitled to a special privilege; Direct access to dedicated support, where we can reach out for assistance with the template issue. In this case, I could have done just that, but I knew it would significantly slow down the already delayed development process of vTual.

I would have to wait for the support team to respond, troubleshoot, and potentially provide a fix, which would only add to the project's timeline.

But as a developer, I'm acutely aware of the importance of meeting deadlines, and I didn't want to risk further delays that could impact the overall project's release.

Also as a developer, I'm a strong proponent of the DRY (Don't Repeat Yourself) principle, which emphasizes the importance of reusable code.

To achieve this, I always apply the concept of Components to all the UI elements I develop. This approach allows me to break down the user interface into smaller, modular pieces that can be easily reused throughout the application.

Once the initial UI development is complete, I take it a step further by refactoring these components into even smaller, more granular pieces.

This process enables me to create a library of reusable components that can be easily assembled and reassembled to build new features and interfaces, reducing code duplication and making maintenance a breeze. By doing so, I can ensure that my codebase remains efficient, scalable, and easy to maintain.

I don't really want to go back and forth in uncertainty regarding UI matters and separating component really is tiring. So... With issues cropping up left and right on the UI front, and the launch deadline rapidly approaching, I ultimately decided to stick with the original vTual design for the beta launch.

I figured it would be more practical to focus on getting the application up and running first, and then revisit the UI development once the beta version was live.

This approach would allow me to prioritize the core functionality and ensure a smoother launch, rather than risking further delays by trying to perfect the UI at this stage.

Throughout the UI development process, I hadn't even touched the backend, which still required far more critical optimization. In fact, I had deliberately put the backend on the backburner, knowing that it needed a significant overhaul to ensure the application's performance and scalability.

By doing so, I could buy myself some breathing room to refine the design and address any remaining issues in a more iterative and incremental manner, rather than trying to tackle everything at once.

I'll conclude this lengthy writing with a statement: As a developer, I always strive to use a license that aligns with its intended purpose, regardless of whether the product resulting from that license meets my specific needs or not.

I may not have the financial means, but I still have a moral compass that prevents me from engaging in piracy. Despite the temptation to cut corners and save a buck, I believe that intellectual property rights must be respected, and creators should be compensated for their hard work and innovation.

This is proof of purchase of a Tailwind-based template.

And this is proof of purchase of a Bootstrap-based template.

Though all of these bad decisions cost me a staggering $48 (Rp. 751.632) that could theoretically be used for extending the infrastructure. Fuck man, that's so damn expensive.

Welp. Someone please refund me lmao.

During that two-month period, we made several update, progress and changes about the developments that we can share to the public. Here's what we can say so far.

Ready Features​

Here are the features that are ready to be launched in the v.0.1 alpha version, according to the report part 2.

YouTube Tracker​

It has been said from previous reports that the YouTube tracker is fully functional and performing flawlessly as intended.

This feature allows users to monitor and track their YouTube channels, videos, and related metrics without any issues. Although there may be slight changes in its implementation, but still it’s a significant milestone for the vTual Project, and we can’t wait for you to experience its capabilities.

Account Manager​

It is has been stated from previous reports that the account manager is partially functional at this stage. As it would handles basic user information such as gender, language, external link and many more.

While this feature is fully operational, but still expect some changes and enhancements in future releases as we continue to refine and improve its functionality.

Some said partially functional is the "Affiliation manager" which requires additional planning and handling, as it deals with many security issues if not managed properly.

Twitch Tracker​

It has been said from previous reports that the Twitch tracker is currently in early development but is expected to be included in alpha build v.0.1. Worry not as this plan has been successfully implemented and will be carried out to be included in alpha build v.0.1.

This feature aims to provide tracking capabilities for Twitch streams and channels, expanding the reach and utility of the vTual Project.

However, since Twitch does not enforce persistent VODs on past archives like YouTube, we will not enforce an initial check on past VODs. Because of course those VODs will expire and obsolete anyways.

User-Relation Function​

This feature supposed to be released on alpha build v.0.2, but I feel that this was the main point of the vTual as a whole project. So I'm racing against time and capability constraints so that this feature can be released on alpha build v.0.1.

This feature is intended to create a timeline-like experience for users to follow and interact with their favorite creators. It’s fully functional and performing flawlessly as intended to add a social dimension to the vTual Project that will enhance user engagement and connection.

Even so, the data about "who follows who" and "who is followed by who" will still be treated as private data and kept convidental.

To be exactly clear; As with any other social media platforms, users can customize their own timeline by only following creators they like, or even opt to unfollow their following creator. What needs to be underlined is that currently, the creator will not know who is following and unfollowing them.

Please note that our product is still a beta product and we don't want to disencouraging the creators for their "numbers" of "growth" on our small platform. As this could happen because our product is a new product that known by not so many people, so we don't want to add any more burden to the "numbers" you gained due to our mistake.

As we feel the product is more mature, these statistics will then periodically be made publicly available.

Planned Features​

There are currently no additional features planned, as currently our focus is aimed on improving existing features.

Infrastructure stability and security is also something we are working on improving, as we all hate anything that is slow, unreliable and unsafe.

Collaboration in improving backend performance is also currently under discussion with several related parties.

Simplifying navigation and improving user experience are also top priorities that we will pursue for alpha build v.0.1.

Conclusion​

The development is still ongoing and is still on the right track. Although there were a few hiccups here and there, the majority of which were probably due to my health problems, but we can probably expect that this ambitious project called "vTual" can release it's very first build, the "v.0.1" by the end of 2024.

Thank you for being a part of this exciting journey!

Ready Features​

Here are the features that are ready to be launched in the v.0.1 alpha version.

YouTube Tracker​

We are thrilled to announce that the YouTube tracker is fully functional and performing flawlessly. This feature allows users to monitor and track YouTube channels, videos, and related metrics without any issues. It’s a significant milestone for the vTual Project, and we can’t wait for you to experience its capabilities.

Account Manager​

The account manager is partially functional at this stage. It handles basic user information such as gender, language, external link and many more. While this feature is operational, expect some changes and enhancements in future releases as we continue to refine and improve its functionality.

In-Development Features​

Here are the features that are still in development but ready to be launched in the v.0.1 alpha version.

Twitch Tracker​

The Twitch tracker is currently in early development but is expected to be included in alpha build v.0.1. This feature aims to provide similar tracking capabilities for Twitch streams and channels, expanding the reach and utility of the vTual Project.

Planned Features​

Here are the features that are still in development but scheduled to be shipped in the next v.0.2 alpha version.

User-Relation Function​

Looking ahead to alpha build v.0.2, we are working on a user-relation function. This feature is intended to create a timeline-like experience for users to follow and interact with their favorite creators. It’s still in the early stages of development, but it promises to add a social dimension to the vTual Project that will enhance user engagement and connection.

Conclusion​

The development and testing of the vTual Project are progressing steadily, with several key features already functional and others on the way. We appreciate the patience and support of our early users and are committed to delivering a robust and innovative platform. Stay tuned for more updates as we continue to develop and refine the vTual Project.

Thank you for being a part of this exciting journey!

What to Expect​

Though this page is just the beginning, we have big plans for this space. Here’s what you can look forward to:

• Project Updates: Detailed information on the progress and milestones of our ongoing projects.
• Product Announcements: Be the first to know about new products, features, and improvements.
• Insights and Stories: Behind-the-scenes looks at our development process, team interviews, and user experiences.
• Tips and Tutorials: Practical advice and guides on how to make the most of our products.

Our Vision​

The Silverspoon Project is committed to innovation and excellence. Our blog will reflect these values by providing transparent and engaging content that keeps you informed and connected to our work.

Stay Tuned​

We’re excited about the future and can’t wait to share our journey with you. Stay tuned for the launch of our full blog, where you’ll find a wealth of information and stories about the Silverspoon Project. In the meantime, feel free to explore our website and learn more about what we do.

Thank you for your interest in the Silverspoon Project. We appreciate your patience and look forward to bringing you valuable content soon!