CommunityGlows Blog
Under the hood
How CommunityGlows works: webviews, memory, platform rules and the technical choices behind them.
Sub-topics
- Memory and webviews
Why several open networks use memory, and what page sleeping would change.
- Platform rules
Blocked sign-ins, captchas, quotas and automation policies, and what isolation can and cannot change.
- Behind the scenes
The technical choices behind CommunityGlows, from browser extension to desktop app.
Articles on this topic
- Behind the Scenes of CommunityGlows: From a Browser Extension to a Desktop App
The story behind CommunityGlows and its technical choices: why Tauri, how sessions stay apart per profile and network, and why open networks use memory.
- What CommunityGlows Can and Cannot Do About Platform Rules
Blocked sign-ins, captchas, API quotas, and automation policies: understand the limits social platforms impose on CommunityGlows and its users.
- Why Do Multiple Open Networks Use So Much Memory?
WebViews, processes, active pages, and warm sessions: understand the cost of a multi-network cockpit and the tradeoffs of future page sleeping.