nikolay

You announce the launch in advance so that people can prepare. Otherwise, you're discriminating people by time zones giving an unfair advantage to people who were awake when you announced it or weren't at work or didn't want to do personal stuff while at work. This is exactly how Facebook did it years ago - they didn't have usernames in the beginning, but announced at what date and time they will open it up to the world. But you didn't have to invest a new identity - you could've used Goodreads or X.com or another one common among your customers. Also, you reserve usernames in high demand and you create some automated granting process - the more social media accounts with that username you link, the higher weight in the claiming process you get, and so on.

But the best approach is not to launch a service with usernames - you gain NOTHING. In fact, you can only piss people off! You launch the service, you allow users to link other social identities and you then decide what to do.

I am canceling my Readwise as you didn't get me an advance notice for username grabs and I couldn't get mine, so, I have no incentive to promote username I don't associate myself with. You guys need to understand the meaning and value of identity - you can't play games of rolling dice! Learn from how Meta did it with WhatsApp usernames - they did it right, and you screwed up!

What's the context?

Anecdotal evidence: many monks end up having prostate cancer, including famous saints of Eastern Orthodoxy.

But didn't Tim Ferris in his bod say that the more often you ejaculate, the shorter you live? His rationale (based on talking to doctors, scientists, etc.) was that semen production is prioritized for the allocation of many nutrients. So if you do expend them too often, but don't get enough from your diet, you deplete your body of them.

Yeah, I've tried this as well, but via Antigravity - it was very effective. I wish to have some smart router that monitors the trends of your usage and has skills-based routing to the best model for the job.

By usage trend I mean something considering Codex almost predictable resets, your usage, and maybe even plan ahead using your backlog to know what you will need sooner.

For example, if you want to ship a lot of UI/UX this week, save Claude for it, and use other models to do the coding.

In fact, I completely revamped the way I do testing and even GitHub Actions, because I started to get hit with a lot of GitHub Actions costs. So, what I did was a smart test actions, which verify if the code has test attestations for local runs, so, they just skip burning GitHub Actions redundantly - the code has already been tested successfully locally.

Another huge burn from Actions came from squashed PRs - my attestations didn't work as the commit hash changes, so, I needed to put that into consideration as well.

In general, I'm completely revamping my release cycle, not allowing PRs to age, and main no longer represents Production. Agents keep merging as soon as possible and then another process assesses if there's a good enough release candidate having enough features that pass more extensive tests. There's no point to always test and always fix piece by piece if you're not going to release.

So, the RC candidate also generate a changelog, blog posts with the features, and so on.

Yes, it's about the same time when I noticed degradation in the quality, too.

It is dumb. None of my threads were closed with shipped features. It keeps going into endless review cycles essentially burning all my quota within a couple of days. And I'm not talking about complex a features an OpenAPI-based integration and some enhancement of pytest traces building maps of touched files. Both these are in their second week of token burn!

Agreed. Yet, it munches tokens like there's not tomorrow. I don't get anything done with Claude in the past 2-3 weeks - just eating up its weekly quota within a day.

I use both for grocery delivery. The grocery platform of Instacart is better, so, I hope we can get the best of both worlds with having the better DoorDash promos with the better platform.

No M6, really? Anyway, I've never used touch on Windows, never going to is it on macOS either.

Running in parallel and the new "thread coordination" is even worse! I "love" the cryptic messages threads share, and the endless loops of "main has changed, so, all tests done got invalidated". Maybe I have the wrong workflow, but I doubt. Mostly it's harness regular updates.

A domain names web storefront with negotiations system, complex payment shapes, quite a few integrations with registrars and services, a Telegram bot for back office with mini apps, etc. A CLI, a TUI, an MCP, a WebMCP, text messaging. Built mostly on Cloudflare and with Ansible and OpenTofu. Runs also a local DuckDB database as I don't feel comfortable putting registry keys somewhere in the cloud, and so on. It is a scope creep, no doubt, but the idea is a to be fully autonomous, to ship features after I just pitch an idea to it. It writes blog posts, produces podcasts (not using Gemini Notebook!), advertises on social media, etc. Lots of work I could never do without coding agents, and I try to perfect it from all angles - following standards, and being as modern as possible. It's overkill, no doubt, but hey, why not. I'm trying to build a foundation for future projects, and get back into real development, and the last 10-15 I spent mostly with Infrastructure as Code. The maintenance of the entire system is probably less than $50/mo, which includes token costs for LLMs, ElevenLabs, etc.

I constantly get into endless review cycles of 50+ rounds. Claude Code simply cannot get many things right regardless of the effort.

I am talking about functional flaws, not cosmetic ones. For example, in web apps, where a11y is mandated, Claude Code kept violating accessibility (regardless of the installed skills), and even the lackluster GitHub Copilot with some outdated models always finds serious violations. Codex constantly finds race conditions and other timing flaws for distributed services written by Claude Code. But I have to admit that Codex sucks at web design compared to Claude Code!

Opus 5.5 burns tokens like there's no tomorrow! Meanwhile, GPT 6.1 Sol on Extra High feels unlimited! Opus (on Max 20x) munches my weekly quota in a day, or two at best. Meanwhile, working with Codex and reviewing with a $50/mo Muse Code Wonder Full seems like it can go own forever (on the same codebase, the same skills, etc.) I am highly disappointed by the overly glorified Opus and Claude Code in general - there's no commit in which Codex or Muse Code or GitHub Pilot don't find critical flaws! I have long sessions of Claude Code having over 100 review cycles of Codex and still not addressing all the valid issues that Codex finds in Claude Code's work! Claude Code keeps injecting British English into prose and identifiers with nothing being able to stop it! Of course, there are almost never resets for Claude Code either - they would rather me focus on Codex being my primary and Claude Code being the reviewer (it works much better than in reverse). Anyway, enver trust a single model! Always review with another frontier one!

It's not the AI, it's the legal side of things - some third party pretending to be you. Not to mention the possible attacked of talking to an agent that has access to your Gmail, and lots, and lots of other accounts.

If I hack a server, the first thing I'm gonna do is lock everybody else out, including the owner. At least in this particular case. In normal breaches, you need to keep being stealth for as long as possible, of course.

The AI is so obvious. Give it a few months and support reps will start declining such calls.

This is a form of a canary token I've been using already. The thing is that it only makes sense if the server breach is cheaper than the money into the wallet. Of course, after you fully monetize your hack, the last step would be to get the bitcoins, too, but how is this helping the owner? The good thing about the existing canary token is that they are all over the place hidden among legitimate similar records and could be harder for the hackers to tell from the rest.

I personally prefer "tripwire" than "canary token", but that's another topic.

Nice! I signed up! I hope more class action lawsuit are brought up about the greedy registrars who are abusing their monopolies! And, finally, a class action lawsuit against ICANN, which legitimizes these monopolies, and, I won't be surprised, its decision makers get payments under the table for the vastly profitable redemption, and "deleted" domains aftermarket!

Imagine you fail to pay your cellphone bill, which is much higher per year than a domain renewal, and then your operator puts your number on auction and your competitors buys it and start taking your clients' calls.

Namecheap is the worst! Our CTO left and our account was tied to his phone. Our CEO didn't want to talk to him, so, over chat, I made them remove the phone 2FA. They didn't authenticate me in any way - only gave them a good story and our username. I know people trash talk GoDaddy, but I've been the most happiest with them - they have support, if you have lots of domains, they assign to your an account exec that can do stuff for you. I've dealt with literally all registrars as I own thousands of domains. Nobody else comes close to GoDaddy - they have APIs, they have support, they listen. Plus, they are big and you can sue them - try suing company abroad if they mess up!

As far as I recall, Namecheap was based in Eastern Europe - as an Eastern European, I can tell you that I would never put anything important in an Eastern European company! Their new Spaceship offshoot is lipstick on a pig, literally.

Cloudflare is also not a good choice - you have no support! Porkbun may seem cool, but I'm not impressed as they lack some basic features such as profiles, let's say.

Launch video [0] and source code [1].

[0]: https://www.youtube.com/watch?v=FbKXvab-0yQ

[1]: https://github.com/davidondrej/cloudroom-core

In 2026, we still don't have a major OS that sandboxes everything.

It didn't ban me, but it did warn me and quote their acceptable use policy or something.

Whatever Ukraine does to Russia, Russia does back to Ukraine severalfold. Which of the two sides can sustain more damage? I think the answer is clear!

To me, English punctuation seems chaotic compared to Bulgarian, which could be hard but logical. English spelling is better than, let's say, Greek or French.

As a developer, I'm surprised people write either "Hello world!" or "Hello, world!" In Bulgarian, as in Russian, the addressee is always set off by commas.

English is so much easier than, let's say, Greek, Russian, or French (at least these I know firsthand). Even Bulgarian, my native language, which is simpler than Russian, is much harder than English, with a lot more things to memorize. Two things in English take time: punctuation and vocabulary (with all the nuances of words). Everything else is easy-peasy!