Added an additional document about the quota-related errors and linked to it in the #screenshotone API quota-related errors.

When there are no more credits (#screenshotone), I decided to make it obvious and render the quota in the red color.

Changed the color theme of the code examples for #screenshotone to a darker one.

Fix the #screenshotone API validation to catch a case like:

Catch networking errors and DNS issues when rendering websites for #screenshotone.

Refilled proxies balance for #screenshotone (it allows customers rendering screenshots from different locations).

Helped a #screenshotone customer to write a selector to screenshot a specific part of a website.

Checked website rendering for a few customers and closed the first support tickets of the day for #screenshotone.

Just sent the first email to dive deeper into the customer churn reasons for #screenshotone.

Shared my build in public report for #screenshotone on Twitter and LinkedIn.

Improved utilization of the #screenshotone GPU server by using Vulkan API with NVIDIA GPUs. It has improved rendering performance by 1000% in some cases.

Back from my vacation! And immediately fixed a website rendering issue for #screenshotone 💪

Fixed quota notifications for #screenshotone users. It might help to convert more users once they get the notification.

Closed a few more support tickets for #screenshotone. Fixed rendering issues for a few websites.

Closed the first support issue of the day for the #screenshotone customers.

Improve error handling for the #screenshotone TypeScript SDK.

Canceled subscription for and refunded a customer because #screenshotone didn't fit them well 🤷🏻‍♂️

Added an ability to use proxies with the #screenshotone Zapier integration.

Added custom error properties to the #screenshotone Python SDK for better error handling.

Improved a few heuristics for the full-page screenshot rendering (#screenshotone) for websites which use viewport units and have glitches.