Started building a simple tab scroller because nothing proper existed.
Well, now it has workspaces, a command bar, mouse gestures, keyboard shortcuts, time-travel sessions and a side panel UI.
I may have overegineered it.
Most workspace solutions treat sync as a premium upsell. Build in a server, add a login, charge monthly. The extension becomes the thing you depend on.
Solution: using Chrome's built-in sync (no separate servers, no telemetry, no new accounts). It just simply works.
@QoreChain "no cloud no third party" is becoming the strongest selling point in tech and that should tell you everything about how badly the cloud era broke user trust
@garrytan Vendoring skills locally is the part nobody's talking about. Once your agent workflow lives in the repo alongside the code, every contributor inherits your judgment without a meeting.
Full audit if anyone wants it: the 2026 code has 19 scored actions, Phoenix transformer replaced SimClusters, TweepCred is gone. Happy to share details.
Spent a full day auditing the X algorithm source code (xai-org/x-algorithm on GitHub). Here's what nobody tells you:
The weight values everyone quotes (27x reply, 150x author-reply, 10x bookmark) are from the 2023 release. The 2026 system redacted all weights. Bookmark isn't even a scored action anymore.
The real cold start trap: 15 followers × 5-15% test distribution = 1-2 people see your post. Even 100% engagement from them isn't enough signal. The algorithm never expands distribution.
The only free exit I've found: replies on threads by 50K+ accounts. My top 3 performing content are all replies — each got 10x more views than my best original post.
Your own posts are invisible at <100 followers. But thousands of people are already reading that viral thread. Show up there.
What's actually working for you at low follower count?
#buildinpublic
@ai_for_success Google's biggest competitor is their own product discovery. They shipped this in December and even power users are finding out from tweets.
@thedawgyg The fact that finding an RCE in Chrome and getting a response requires someone else to tag the right people for you is wild. Billions of users and the reporting process is a guessing game?
The other half of Chrome's RAM problem: page bloat. A single news site tab loads 20-40 ad network requests and several MB of third-party JavaScript before you even read the headline. Multiply that across 15 tabs.
Chrome 146 Memory Saver discards inactive tabs but doesn't touch what's inflating them. Block the bloat before it loads and suspend what you're not using — that's the real combo.
Steam Spring Sale is live! All my games are discounted: https://t.co/sSeWdJepAE
These are worth checking out if you like dark games with cool stories, and want to support a solo dev creating games like these in the future as well. 😆
#steam#indiegame#gaming#steamspringsale
@allodev CWS review for a first extension usually takes 1-3 days — if it needs host permissions for the X domain, expect the longer end. On the platform side, mass-unfollow in bursts can trigger rate limits. Spacing them out is safer than blasting through thousands.
Launched a new website Fri evening: 680 pageviews and 11.8% site-to-CWS conversion so far.
AI chatbots (Claude, ChatGPT) are citing the articles without me doing anything. Nine visits from AI referrals so far. Small number, but the referral path is real.