I have a friend who believes in the moon landing conspiracy - you know, one of those people who think the Americans never actually went to the Moon.

He's convinced the whole thing was staged, masterfully filmed by movie directors. Arguing with him is almost pointless - he says every photo is fake. The fact that even Soviet scientists never questioned the authenticity of the American Moon landing doesn't matter to him.

But there's one argument that made him stop and think. No, I didn't manage to change his mind, but at least I got him to shut up for a while - confused him, so to speak.

The argument went like this: "So what, they faked all their Moon landings?"
Funny thing is, he didn't even know that the Americans went to the Moon not once, but several times.

Here's the list of all Moon missions:
Apollo 11 - July 16, 1969
Apollo 12 - November 14, 1969
Apollo 14 - January 31, 1971
Apollo 15 - July 26, 1971
Apollo 16 - April 16, 1972
Apollo 17 - December 7, 1972

So according to the "logic" of Moon landing deniers, the Americans didn't fake it just once - they supposedly faked it six times, along with all the photos, videos, and even the Moon rocks they brought back.

Humans have been flying to space since 1961 - that's over 60 years now. These days, we even have tourist spaceflights. In sci-fi movies, people travel between planets, stars, and even galaxies.

But what is space from the perspective of aviation and astronautics? Technically, it starts somewhere between 100 and 122 kilometers above Earth's surface. The range exists because different organizations define the boundary of space slightly differently.

Is 120 kilometers really that high? The average diameter of our planet is 12,742 kilometers - quite a lot. Below, I drew a simple picture to show what a spaceflight looks like to scale:

See that tiny red dot? That’s our trip to "outer space". Not exactly impressive, right? For comparison, the International Space Station orbits at an altitude of about 418.2 km - on this scale, its point would only be a couple of pixels higher.

Human technology is still in its infancy. Legally, we can say we fly to space - but in reality, it looks more like what you see above. As for interplanetary travel, so far, only our robots have made the journey.

Fixed a bug with displaying the number of unread comments.

Improved error display when mobile internet connection is lost.

Added a sticky loader when saving a comment.

Improved aria-attributes for screen readers.

Added Open Graph support for some pages.

When publishing a post, a like is automatically added to the published post.

In open posts, a button icon was added to quickly jump to comments.

Separate language-specific home pages were created on sub-URLs like /es, /de, etc.

The site header is now fixed at the top on most pages.

You can now insert previously uploaded images and videos into posts and comments by selecting them from a list.

If, while editing a post, a user accidentally deletes a content block, it can now be restored using a button in the notification in the corner of the screen.

New types of complaints have been added: content created by a AI and copyright infringement.

The project rules have been updated.

A small profanity check is now performed when saving a post or comment.

A man has five children - all girls. He dreams of a son, an heir! Now his wife is pregnant again. Let's skip the psychology behind all this and focus on the probabilities.

Emotionally, it feels like after five girls in a row, a boy is due. Surely, the odds of finally having a son are much higher now.

But this is a textbook example of the gambler's fallacy - the false belief that if something happens repeatedly, the opposite is bound to happen soon. That's not how probability works.

According to math, the chance of having exactly five girls in a row followed by another girl is 1 in 64, or about 1.6%. But those five girls are already here. The only thing that matters now is the next birth.

And the odds of having a boy? Still 50/50. Every birth is an independent event (assuming randomness), so the previous outcomes don't change the next one.

So yes, there's still a 50% chance they'll have another girl.

If you try to use Quill Editor with Nuxt 3 when rendering a page in SSR you will get this error:
That means NodeJS doesn't have the global variable 'document'. Because SSR rendering is executed in
a NodeJS environment, not a browser.

The sad fact: <client-only> won't help with this problem. The problem with quill's code is that during import, it assumes it's being executed in the browser. I hope you remember that the code imported from the module is not just imported, but executed, i.e. the authors of Quill wrote it so that the 'document' object is immediately accessed there. Very bad.

One solution is to disable SSR, but its an awful solution. But the second solution is to use dynamic JS imports.

My <script lang="ts" setup> in QuillEditor.vue in Nuxt 3 project:

import 'quill/dist/quill.core.css';
import 'quill/dist/quill.snow.css';
// import Quill from 'quill'; // SSR problem with 'document', need to use dynamic import
import type Quill from 'quill';

const elemForQuillEditor = ref<HTMLDivElement|null>(null);

let editor: null|Quill = null; // Do not store in ref() - it causes bugs!

// ...

async function createQuillAndSetListeners() {
  const Quill = (await import('quill')).default; // This is most important thing - usage of JS dynamic import

  if (!elemForQuillEditor.value) return;
  editor = new Quill(elemForQuillEditor.value, {
    theme: 'snow',
    modules: {
      history: {
        delay: 2000,
        maxStack: 500,
        userOnly: true,
      },
      toolbar: {
        container: [
          ['bold', 'italic', 'underline', 'strike'],
          ['link'],
          [{ list: 'ordered' }, { list: 'bullet' }],
          [{ script: 'sub' }, { script: 'super' }],
          [{ header: [1, 2, 3, 4, 5, 6, false] }],
          [{ color: [] }, { background: [] }],
          ['clean'],
          ['undo', 'redo'],
        ],
        handlers: {
          undo() {
            editor?.history.undo();
          },
          redo() {
            editor?.history.redo();
          },
        },
      },
    },
    placeholder: props.placeholder,
  });
  
  editor.on('text-change', () => {
    if (!editor) return;
    // ... my other code
  });
}

// ...

onMounted(createQuillAndSetListeners);

Now your Quill editor will work in Nuxt 3 even during SSR!

Write language name after triple backticks (```) and content of preformatted text will be highlighted.
This is example:

 ``` ts
 let projectName: string|null = null;
 projectName = 'Famabara';
 ```

Of course, you shouldn't start backticks-line with a space.

Golang syntax highlight example:

package main

import "fmt"

func main() {
	fmt.Println("Hello, from Go!")
}

Javascript syntax highlight example:

console.log(2**2**3); // 256
console.log(2**(2**3)); // 256
console.log((2**2)**3); // 65

SQL example:

SELECT p.id, p.title FROM posts p LIMIT 10;

For C++ write "cpp", not "c++".
For C# write "csharp", not "c#"

Famabara uses highlight.js for syntax highlight.

Several useful changes have been added to the site over the past few days.

First, search was added to Famabara. All posts are indexed automatically.

Secondly, users can now subscribe to tags.

Of course, many minor changes have been made to improve the interaction with the site.

Famabara now supports quotes in posts and comments. Write ">" character in the beginning of a new line and this line will become a quote.

Example:

No, don't do it!

That's a good idea!

The text I wrote:

> I want to eat 3 pizzas.
No, don't do it!

> I want to eat an apple.
> And a peach.
That's a good idea!

Stay with Famabara!