Day: September 9, 2026

September 9, 2026

4GoodHosting, Domain Related, Hosting Related, VPS Hosting, Web Hosting, WordPress, WordPress Hosting

Reading Time: 43 minutes

Most advice on building a retail brand is about how things look and feel. Colour palette, typography, store layout, shelf presence, packaging, the tone of the signage, the workshop where everybody agrees on three adjectives. It is a large and well-developed body of work, and for a physical shop it is largely correct — when the customer is standing in your space, the space is the brand. Then the customer is not standing in your space. They are on a phone, on a bus, at 9:40 on a Tuesday night, with your site half-loaded and a payment method you do not accept. Nothing about your colour palette is relevant to what happens next. This article is about that second situation, which is now where most of a retail brand's damage occurs. Not because design does not matter — it does — but because design is the part everyone already works on, and the failures that actually destroy trust are almost entirely invisible to the business until a customer tells them, or does not. Written for Canadian retail businesses running a website alongside, or instead of, a physical location. It covers what breaks, in rough order of how badly it damages you, and what the infrastructure underneath has to do to stop it. What ‘brand’ becomes once the store is a website The useful starting point is to be precise about what transfers from physical retail and what does not, because a great deal of retail branding advice is written as though the online version is the same exercise on a smaller screen. It is not, for one structural reason. In a shop, staff absorb the failures. Online, nothing does When something goes wrong in a physical store — an item is out of stock, the card terminal is slow, the queue is long, the price on the shelf does not match the till — a person intervenes. They apologise, they check the back, they offer an alternative, they honour the shelf price. The failure still happened, but it was absorbed, and the customer's memory of it is mediated by someone who was visibly trying. Online there is no one on...

September 9, 2026

4GoodHosting, Domain Related, Proxy Servers

Reading Time: 48 minutes

A proxy server is a computer that makes requests on behalf of something else. That is the whole idea, and everything else is detail. The reason proxies confuse people is not that the concept is difficult. It is that one word has been stretched to cover several genuinely different technologies that happen to share that one behaviour. The software filtering web traffic on an office network, the service sitting in front of a busy website distributing traffic across servers, the thing someone buys to scrape product prices, and the layer terminating encryption at the edge of a content network are all called proxies. They do not do similar jobs. Most explanations of proxy servers make this worse rather than better. They list types without explaining what distinguishes them, they repeat the claim that a proxy encrypts your traffic (which is usually false), and they treat proxies and VPNs as near-synonyms (which they are not). By the end you know more words and no more mechanics. This guide takes the opposite approach. It explains what a proxy actually does at the level of the request, distinguishes the two fundamental directions a proxy can face, works through the types properly, is specific about what happens to encrypted traffic, and is honest about what proxies can and cannot protect. It also covers the parts that matter for a Canadian business in particular, including where a proxy sits relative to your data and what that means for the privacy commitments you may have made to your clients. The definition, and the request path A proxy server is an intermediary that receives a network request, forwards it to its destination on the requester's behalf, receives the response, and passes that response back. The two endpoints communicate through it rather than directly with each other. Walk through what happens without one first. You type an address into your browser. Your device resolves the hostname to an IP address, opens a connection to that address, sends an HTTP request, and receives a response. The web server sees your IP address, because your device is the thing talking to it. Now insert a proxy. Your browser is configured...

September 9, 2026

Domain Related

Reading Time: 35 minutes

If you have spent an evening comparing website builders, you have probably noticed that almost everything written about them is published by a company that sells one. That does not make the advice wrong. It does mean one question rarely gets a straight answer: what happens to your website if you decide to leave? This article covers what a website builder is and how one actually works, which is the easy part. It also covers the parts that get skipped — what you own at the end of it, what a builder does to your search visibility, where your site physically lives, and the specific circumstances in which a builder is the wrong tool. Some of those answers argue against using one. What is a website builder? A website builder is software that lets you create and publish a website through a visual editor, instead of writing the code yourself. You start from a template, add your own text and images, arrange the layout by pointing and clicking, and publish. The builder generates the underlying HTML, CSS and JavaScript on your behalf. That is the whole concept. Everything else — templates, drag-and-drop, AI page generation, built-in stores — is a variation on it. It helps to be precise about what a builder replaces, because the term gets used loosely. A website builder replaces the act of writing front-end code. It does not replace design judgement, copywriting, product photography, or the decision about what your website is for. Those remain yours, and they are the parts that determine whether the site works. One more distinction worth making early, because it causes real confusion later: a website builder is a tool for making a site. Hosting is the service that keeps the site available on the internet. Some builders bundle the two so tightly that they look like one product. Others keep them separate. That difference turns out to matter a great deal, and it is the subject of the next two sections. How does a website builder work? A drag-and-drop website builder sits between you and the code, and it works in four stages. 1. The template establishes the structure You...