Documenting code, one commit at a time.
The devlog-ist/landing project focuses on creating a compelling landing experience. Recent work centered on improving SEO and ensuring proper sitemap discovery.
The Cloudflare CDN was overriding the application's robots.txt, which prevented search engines from discovering the sitemap. This negatively impacted SEO performance.
To bypass the CDN override, a
Working on the devlog-ist/landing project, we're refining the authentication flow. The goal is to streamline user registration and login, particularly for non-developers who might be contributing recommendations. We've adjusted the available OAuth providers to match user roles.
Previously, both GitHub and LinkedIn were presented as default options on the login and registration pages.
OAuth provides a streamlined approach to user authentication, but it's crucial to implement security measures that protect user data and prevent unauthorized access. A common scenario involves social login, where users authenticate via third-party providers like GitHub or LinkedIn.
A potential vulnerability arises when users not yet
Maintaining a consistent URL structure is crucial for search engine optimization (SEO). Duplicate content, even with slight variations in the URL (like the presence or absence of "www"), can confuse search engines and dilute your website's ranking potential.
Search engines like Google treat example.com and `www.example.
This article discusses a common issue in applications using GitHub OAuth for authentication: inadvertently overwriting a user's existing token with one that has fewer permissions. We'll explore how to ensure the application preserves the user's original, broader-scoped token when requesting narrower scopes during subsequent logins.
Many applications use GitHub
When dealing with multi-tenant applications, handling tenant removal gracefully is crucial for user experience and data integrity. This post discusses a strategy for tenant dissolution with a focus on minimizing disruption and providing users with options.
In a multi-tenant system, deleting a tenant can have significant implications for its users.
Managing resource quotas across multiple tenants can be challenging, especially when the need for manual overrides arises. This post explores how we refactored our token usage service to implement a tenant-centric quota system with support for manual adjustments.
Previously, our token quota management was user-based. This created inefficiencies when the context already provided
Maintaining data consistency across distributed systems and applications often requires careful management of caches. Stale data in caches can lead to unexpected behavior and inconsistencies. We recently implemented several enhancements to our application's caching strategy, focusing on proactive invalidation to ensure data accuracy and prevent outdated information from impacting
During a recent update, we encountered an issue where partial failures during data synchronization could lead to data loss. This post details the problem and the solution implemented to ensure data integrity.
Our application relies on synchronizing data from an external source. The synchronization process involves fetching and updating various data points.
We've recently refactored and optimized our AI token usage tracking to improve performance and maintainability. This involved extracting duplicated queries and enhancing user filtering.
The primary focus was on improving the efficiency of retrieving daily and monthly tenant AI usage data. This was achieved through two key changes:
