WEBVTT 00:00:00.000 --> 00:00:05.920 Namegarage Weekly uses AI voices, with a script based on our published posts and reviewed before 00:00:06.000 --> 00:00:07.040 publication. 00:00:07.040 --> 00:00:13.360 Welcome back to Namegarage Weekly. Our first episode gave you the tour. This week, we're asking a more 00:00:13.440 --> 00:00:19.840 practical question: how do you get from “I've got an idea” to a shortlist you can actually use? 00:00:19.840 --> 00:00:24.240 Preferably without opening forty tabs and forgetting why the first one was interesting. 00:00:24.240 --> 00:00:30.507 A respectable ambition. We're covering October eighteenth through twenty-fourth: finding names by describing a 00:00:30.560 --> 00:00:36.480 project, keeping track of the ones you like, and a surprisingly useful investigation into blurry 00:00:36.560 --> 00:00:37.360 artwork. 00:00:37.360 --> 00:00:43.120 Those sound like separate stories. But they both come down to what reaches the person using the product. A 00:00:43.240 --> 00:00:47.840 search result needs to help you choose. A sharp image needs to arrive sharp. 00:00:47.840 --> 00:00:53.760 We'll also look at four of the current Platinum and Gold offers, then catch up with the Dutch auctions. Let's 00:00:53.840 --> 00:00:57.600 start before the shortlist, when you don't yet know what to type. 00:00:58.050 --> 00:01:04.130 A conventional domain search assumes you already have part of the answer. Type “bakery,” and you're looking for 00:01:04.170 --> 00:01:07.010 a name with bakery in it, or something close. 00:01:07.010 --> 00:01:13.490 Which is useful if that's what you want. But maybe you want a warm, friendly name for a neighborhood bakery, and 00:01:13.530 --> 00:01:16.050 the right name doesn't contain the word at all. 00:01:16.050 --> 00:01:22.410 That's the gap the new search is trying to close. You can describe a project, an audience, or a tone. 00:01:22.450 --> 00:01:28.330 Namegarage compares that description with the descriptions and possible uses published for its domains. 00:01:28.330 --> 00:01:34.530 So the question can be “What fits this idea?” rather than “Which names contain these letters?” 00:01:34.530 --> 00:01:40.370 Yes, although I'd keep both questions. If I know the name I'm looking for, I don't want the search to become 00:01:40.450 --> 00:01:42.010 philosophical about it. 00:01:42.010 --> 00:01:46.610 “You asked for a spelling. Have you considered your deeper aspirations?” 00:01:46.610 --> 00:01:52.930 Exactly the conversation I don't need from a search box. The ordinary name search still works as you type. The 00:01:53.010 --> 00:01:55.450 search by meaning adds another way in. 00:01:55.450 --> 00:02:01.570 And if that extra search is busy, the ordinary results stay available. That seems like a sensible engineering 00:02:01.930 --> 00:02:05.610 choice: an extra capability shouldn't take away the basic one. 00:02:05.610 --> 00:02:11.410 It also helps you judge the suggestions. The result shows the use case it matched. You can ask whether that 00:02:11.490 --> 00:02:15.703 connection makes sense instead of taking a mysterious ranking on trust. 00:02:15.703 --> 00:02:22.370 I'd still try several descriptions. “A bakery,” “a gift business,” and “a cozy neighborhood brand” might 00:02:22.450 --> 00:02:28.490 lead me to different possibilities. That difference could help me work out what I actually want the name to say. 00:02:28.490 --> 00:02:33.890 That's a useful way to use it. A search result can prompt a better question. It doesn't settle the naming 00:02:34.090 --> 00:02:35.197 decision for you. 00:02:35.197 --> 00:02:40.610 You can also start searching from other pages now. The shared header gets you back to the catalog with your 00:02:40.770 --> 00:02:46.130 search carried over. So reading about a name doesn't mean losing your route back to the rest. 00:02:46.250 --> 00:02:51.770 And there's another route for people already working with an AI assistant. A new connection lets a compatible 00:02:51.850 --> 00:02:56.250 assistant search the public catalog and check an individual name's current price. 00:02:56.250 --> 00:03:02.730 I like the idea of staying with the brief you've already been discussing. But I'd want a clear stopping point. 00:03:03.210 --> 00:03:08.010 Looking at names is one thing. Having software negotiate on my behalf is another. 00:03:08.010 --> 00:03:14.410 The connection stops at reading. It can't buy, reserve a domain, make an offer, or send a message. 00:03:14.810 --> 00:03:17.850 It brings back information and a link for you to review. 00:03:17.850 --> 00:03:24.090 That makes the handoff quite clear. Let the assistant help gather options; keep the decision with the person 00:03:24.170 --> 00:03:25.290 spending the money. 00:03:25.290 --> 00:03:30.810 And check the listing when you're ready. A name in a conversation isn't a reservation, and a price quoted 00:03:30.890 --> 00:03:32.410 earlier can change. 00:03:32.860 --> 00:03:39.420 Once a name makes the shortlist, the next problem is remembering to check it. Or checking it far too 00:03:39.500 --> 00:03:40.300 often. 00:03:40.300 --> 00:03:46.460 The individual Price alerts button now opens a short form on the domain page itself. You can follow that name 00:03:46.620 --> 00:03:52.300 without leaving it. For a broader weekly selection, you can choose price ranges as well as interests. 00:03:52.300 --> 00:03:58.940 That distinction matters. If I want one particular name, a general newsletter isn't quite the same thing. 00:03:59.340 --> 00:04:03.460 If I'm still exploring, following one name might be too narrow. 00:04:03.460 --> 00:04:09.700 And budget is part of the brief. A list can be full of attractive names and still be useless if none is in the 00:04:09.740 --> 00:04:11.140 range you're considering. 00:04:11.140 --> 00:04:17.260 There's a confirmation before the emails start, and a way to stop them in each alert. I wouldn't call that an 00:04:17.340 --> 00:04:20.940 exciting feature, but I would notice if it were missing. 00:04:20.940 --> 00:04:27.260 A lot of this week's work is like that. The contact page now asks why you're writing. A payment problem and a 00:04:27.340 --> 00:04:30.940 naming question should arrive with enough context to tell them apart. 00:04:30.940 --> 00:04:37.340 Without turning a simple message into an application form. The phone number is optional, and asking for help 00:04:37.580 --> 00:04:40.140 doesn't mean agreeing to marketing messages. 00:04:40.140 --> 00:04:45.820 The email and text choices are separate and optional. Leaving them unticked doesn't change the answer to your 00:04:45.900 --> 00:04:46.780 question. 00:04:46.780 --> 00:04:52.780 That fits with the change to blog discussion, too. You now sign in with Google, GitHub, or Apple to 00:04:52.860 --> 00:04:59.140 comment, but you can still read posts, read approved comments, and listen without signing in. 00:04:59.140 --> 00:05:05.900 There's a trade-off there. Signing in adds a step. In return, a comment has some account context instead of only 00:05:05.940 --> 00:05:07.420 a name someone typed. 00:05:07.420 --> 00:05:12.060 I wouldn't want that to become “we've verified everything this person says.” 00:05:12.060 --> 00:05:17.860 Nor should it. It shows control of an account, not someone's legal identity or the truth of an argument. 00:05:18.060 --> 00:05:21.740 Comments still go through moderation, and the email address stays private. 00:05:21.860 --> 00:05:28.420 For agencies choosing a name with a client, the new partner program adds another kind of context. There are 00:05:28.540 --> 00:05:34.340 shareable shortlists, reviewed introductions, and separate arrangements for agencies and brokers. 00:05:34.340 --> 00:05:40.020 I think the distinction between a shortlist and an introduction is useful. A shortlist says, “Here are some 00:05:40.100 --> 00:05:45.860 options.” An introduction says, “There's a particular buyer interested in a particular domain.” 00:05:45.860 --> 00:05:52.420 Passing around a link shouldn't quietly register a client, disclose their details, or reserve a name. 00:05:52.420 --> 00:05:58.580 The published program keeps those steps separate. It also keeps the seller responsible for accepting offers. The 00:05:58.660 --> 00:06:04.740 commission pilot concerns verified cash sales; it isn't a promise of automatic commissions on every type of 00:06:04.820 --> 00:06:05.780 transaction. 00:06:05.780 --> 00:06:12.100 We'll leave the percentages and agreement details in the notes. If you're an agency or broker, the program page 00:06:12.180 --> 00:06:15.220 is the place to check the current application position. 00:06:15.220 --> 00:06:21.380 And after a purchase, the same need for context continues. The lease portal covered in our launch episode brings 00:06:21.460 --> 00:06:27.540 the payment position and supported domain management together. That post falls inside this week's dates too, so 00:06:27.580 --> 00:06:29.540 we won't give you the whole tour twice. 00:06:29.540 --> 00:06:36.340 The common question is simple: “Where do I go next?” A useful product keeps answering it after the interesting 00:06:36.500 --> 00:06:37.380 first click. 00:06:37.830 --> 00:06:44.390 It has to answer without relying only on what you can see. Another update keeps progress messages in place for 00:06:44.550 --> 00:06:51.030 assistive technology. A catalog refresh or a message being sent should be understandable without moving you away 00:06:51.110 --> 00:06:52.630 from the field you're using. 00:06:52.630 --> 00:06:59.030 There's also a public, machine-readable declaration of the browser privacy signal Namegarage already 00:06:59.110 --> 00:07:05.350 honors. That's documentation of an existing choice, rather than a new request to track you. 00:07:05.350 --> 00:07:11.430 And if the site itself won't load, there's a separate public status page. It's hosted away from the main website 00:07:11.510 --> 00:07:14.390 and checks a few important pages independently. 00:07:14.390 --> 00:07:21.190 Useful, with a limit: a healthy homepage isn't proof that every payment or email is working. If something 00:07:21.270 --> 00:07:24.950 goes wrong, the page and what happened still matter. 00:07:24.950 --> 00:07:31.110 That limit connects neatly to the artwork investigation. An upload being accepted isn't proof that visitors are 00:07:31.190 --> 00:07:33.030 seeing the file you uploaded. 00:07:33.030 --> 00:07:39.110 This one started with an ordinary frustration: a logo looks sharp in the original file, then soft on a 00:07:39.630 --> 00:07:43.430 platform. The standard suggestion is to make a bigger image. 00:07:43.430 --> 00:07:50.190 Sometimes that's the answer. But here the investigation asked what size the platform was actually delivering. 00:07:50.230 --> 00:07:55.750 If it keeps sending a small version, making your original bigger doesn't necessarily fix the view. 00:07:55.750 --> 00:08:02.390 The Spotify example is especially easy to picture. The show cover was three thousand pixels square. In the 00:08:02.510 --> 00:08:08.430 observed enlarged artwork view, the selected image was only six hundred and forty pixels square. 00:08:08.430 --> 00:08:13.990 And that enlarged view needed more detail on the high-density display used for the capture. The smaller 00:08:14.190 --> 00:08:19.430 thumbnail is a different case: the selected image had enough pixels for the size of that box. 00:08:19.430 --> 00:08:26.190 So “Spotify sends a smaller image” isn't the whole finding. Smaller can be fine for a small thumbnail. 00:08:26.230 --> 00:08:29.910 It's the enlarged view that exposes the problem in that example. 00:08:30.030 --> 00:08:36.830 Right. The WhatsApp capture showed a related problem: a relatively small delivered cover stretched across a 00:08:36.950 --> 00:08:42.910 much wider area. The post preserves the files and compares matching parts of the lettering, so readers can 00:08:43.110 --> 00:08:44.350 inspect the evidence. 00:08:44.350 --> 00:08:50.750 And LinkedIn complicates the story in a useful way. The later capture supplied a larger image than the 00:08:50.830 --> 00:08:56.910 earlier one. It deserves credit for the better observed result, even though there isn't a confirmed explanation 00:08:56.950 --> 00:08:58.230 for the change. 00:08:58.230 --> 00:09:03.950 That's where I'd resist the temptation to turn a comparison into a verdict on entire platforms. These are 00:09:04.110 --> 00:09:10.670 particular desktop views at particular times. They don't tell us how every device or app behaves. 00:09:10.670 --> 00:09:17.230 Fair. But they do give a creator a better next step than exporting the same banner for the seventh time. 00:09:17.230 --> 00:09:23.470 Keep the original. Find out what file the page selects. Compare the same part of the artwork at the same display 00:09:23.550 --> 00:09:28.590 size. Then ask a question about delivery, not just upload requirements. 00:09:28.590 --> 00:09:35.203 The post also proposes letting platforms retain a vector master and generate the right image sizes from it. 00:09:35.257 --> 00:09:39.070 That's a proposal, not a feature we're announcing from those platforms. 00:09:39.070 --> 00:09:44.990 And it wouldn't conjure detail out of a tiny photograph. It would help when the master really contains scalable 00:09:45.110 --> 00:09:46.470 lettering and shapes. 00:09:46.470 --> 00:09:52.990 There's a broader lesson here for builders. Success at one step can be real and still fall short of the result 00:09:53.030 --> 00:09:59.310 the customer cares about. “File accepted” and “logo looks clear” are two different checks. 00:09:59.310 --> 00:10:05.310 Much like “search returned results” and “I found a name worth considering.” You have to look at the experience 00:10:05.350 --> 00:10:06.670 at the other end. 00:10:06.670 --> 00:10:13.310 You can share the investigation, or any blog post or podcast episode, with the new sharing buttons. They 00:10:13.390 --> 00:10:19.470 point to the public page and leave out playback positions and extra query details. There aren't social widgets 00:10:19.550 --> 00:10:21.350 loading behind those buttons. 00:10:21.350 --> 00:10:26.470 And the article carries the source files and measurements if you want to go deeper. Here, we'll spare you a 00:10:26.510 --> 00:10:27.790 spoken spreadsheet. 00:10:28.240 --> 00:10:34.160 Speaking of spreadsheets, the complete premium offer list is in the notes. We checked the current deals and 00:10:34.280 --> 00:10:40.160 these individual listings early on Sunday, October twenty-fifth. Current listings govern prices and 00:10:40.240 --> 00:10:46.560 availability. This selection's offers close Saturday, October thirty-first, at six p.m. Pacific. 00:10:46.560 --> 00:10:53.280 Two Platinum names first. AppJam dot com is nineteen thousand six hundred ninety dollars at that check. 00:10:53.360 --> 00:10:57.840 As a naming idea, I can hear a development studio or an app-building event in it. 00:10:57.840 --> 00:11:04.480 It sounds active. I like the sense of making something together, though a serious enterprise product might want 00:11:04.560 --> 00:11:09.520 a quieter tone. That's a choice about personality, not a score the name wins. 00:11:09.520 --> 00:11:16.240 The other Platinum pick, Advizy dot com, is thirteen thousand eight hundred eighty dollars. It suggests advice 00:11:16.400 --> 00:11:18.640 without spelling out a particular profession. 00:11:18.640 --> 00:11:25.120 More room for a business to define it, then. But I'd say it aloud and ask someone to spell it back. A coined 00:11:25.200 --> 00:11:29.400 name gives you flexibility; you still have to make it easy to remember. 00:11:29.400 --> 00:11:35.760 For Gold, AirNotify dot com is ten thousand one hundred thirty dollars. My first associations are flight 00:11:35.840 --> 00:11:41.680 updates or air-quality alerts. Those are possible uses, not businesses included with the domain. 00:11:41.680 --> 00:11:47.680 The name tells you more straight away. That can be helpful if the brief is specific. It could feel restrictive 00:11:47.760 --> 00:11:51.680 if the product later moves well beyond those associations. 00:11:51.680 --> 00:11:57.520 Abstractify dot com goes in another direction, at seven thousand six hundred ninety dollars. I can imagine a 00:11:57.600 --> 00:12:02.040 summarizing tool or a design product that simplifies complicated material. 00:12:02.040 --> 00:12:08.480 I prefer that one when the product can demonstrate the idea quickly. The name promises a process: take something 00:12:08.560 --> 00:12:13.760 complicated and make it simpler. I'd want the first screen to show me what that means. 00:12:13.760 --> 00:12:19.560 Four different tests for a shortlist, then: tone, spelling, clarity, and room to grow. 00:12:19.560 --> 00:12:26.080 The notes have regular prices, savings, the other eligible offers, and direct links. You don't have to choose 00:12:26.160 --> 00:12:28.160 from only the four we talked about. 00:12:28.610 --> 00:12:34.850 Now a quick return to three names from the launch episode. These are Dutch auctions, where the scheduled price 00:12:34.930 --> 00:12:37.650 steps down while a name remains available. 00:12:37.650 --> 00:12:43.810 Elastic-Fabric dot com is now five hundred ninety-five dollars, compared with seven hundred forty-five at our 00:12:43.850 --> 00:12:48.370 pilot's check. Its next scheduled price is four hundred ninety-five. 00:12:48.370 --> 00:12:54.130 VerifySignature dot com is one thousand one hundred ninety-five now, down from one thousand four hundred 00:12:54.210 --> 00:12:58.930 ninety-five at that earlier check. The next step is nine hundred ninety-five. 00:12:58.930 --> 00:13:05.570 And Komposable, with a K, dot com is two thousand ninety-five, compared with two thousand six hundred 00:13:05.650 --> 00:13:11.170 ninety-five in the pilot. The next listed step is one thousand five hundred ninety-five. 00:13:11.170 --> 00:13:17.250 For these three, that next step is also the published minimum. It's scheduled for October thirty-first at six 00:13:17.410 --> 00:13:23.410 p.m. Pacific. The collection ends November seventh, at five p.m. Pacific, after the clock change. 00:13:23.410 --> 00:13:29.730 Waiting might save you money. It also leaves time for someone else to buy the name. The minimum is a possible 00:13:29.810 --> 00:13:32.810 later price, not a booking with your name on it. 00:13:32.810 --> 00:13:37.890 If you're interested, the notes link to the schedules and listings. Check the current position rather than 00:13:37.970 --> 00:13:40.770 relying on a number you heard earlier in the week. 00:13:41.220 --> 00:13:48.020 This week's changes give you more ways to begin, and clearer ways to continue: describe the idea, keep 00:13:48.060 --> 00:13:53.620 a useful shortlist, follow a name, and bring the right context when you ask for help. 00:13:53.620 --> 00:13:59.460 And when the result looks wrong, check what actually reached the person using it. Sometimes the most useful 00:13:59.700 --> 00:14:02.980 engineering question is simply, “What did they receive?” 00:14:02.980 --> 00:14:09.540 You'll find the sources, dated offers, Dutch auction watch, and transcript with this episode's notes. 00:14:09.700 --> 00:14:14.420 This is Namegarage Weekly. Thanks for listening, and we'll see what the next week brings.