Ichiro

Chapter 1 - A calm world for the ungrateful

Sat, 27 Jun 2026 00:00:00 GMT

22 bullets.

He picked up a broken gun from the ground, turning and twisting it. Still loaded. Released the magazine, took out the remaining bullets.

32 bullets.

Instead of keeping the gun, he threw it over the edge, down into what used to be a forest. Now it was just a barren valley, filled with all the rubble they had thrown down there, together with anything else that was broken. Some would call it a dumpster, but it wasn’t that bad. If there were still children living around here, they would probably use it as a playground. There were huge rocks which you could climb upon, jump to the next one, take a broken gun and play soldier.

But there were no children here. So it was just a valley, which used to be a forest.

Nothing more, nothing less.

Today’s invasion had been harder. Lots of soldiers were being dropped upon them via helicopters and airplanes and since they didn’t have the ammunition to deal with aircrafts, they were limited to killing the soldiers on ground. It wasn’t always easy, but they managed to survive this battle like all the others.

Casualties were now a part of their lives, but he had been so lucky to not lose any of his closer friends. Yet.

He looked around for more bodies of enemy soldiers, but he had already looted all of them. Another team would come and bury the remains, so his job was done for today. He could return home.

Or what else he could call it.

Turning around, he started to ascend the hill, carrying his rifle over his shoulder and making sure not to trip. Most of the grass and earth was burnt, making it hard for him to find purchase, but he somehow made it. He had to.

He took a shortcut through the remains of the third building, which he had known pretty well. Some time ago, he used to study here, visiting this area five times a week, 30 hours a week. One never realizes how much one can get used to something, until it is gone.

The FH 3, the building that used to stand here, had been reduced to mere rubbles. Even the modern structure hadn’t been able to withstand the power of a nuke or two. The computers, the chairs, the tables, everything had been burned and reduced to ash. Now there were only sorry remains of a once tall and beautiful building.

He stopped for a second and took a breath, when he reached some kind of wall made out of rubble and metal. He lifted his hand and waved to a person standing inside of the building, where the wall had been broken, thus allowing the person to jump down if he pleased. The person acknowledged his action and gave him a thumbs up, thus allowing him to proceed further. Climbing over the wall, he was greeted by the only building that had somehow survived the bombs.

Just as he was stepping under the building inside the shade, he was greeted by yet another person going towards him, calling his name.

“Stephan!”

He knew the approaching person well. It was kind of calming to see a familiar face every now and then.

“Oliver,” he acknowledged the smaller man. The glasses, the brownish hair and the beard were something one could never ignore. Especially the mismatching colours…

“Back from the battlefield? And, found any top-secret plans? Maybe their self-programmed version of a DOM parser? I could use some frustration trying to decode their code”, the man jokingly said. He definitely wasn’t serious, but how could one stay serious all the time in this kind of situation?

“Some bullets and a really fancy hat, but no USB with a DOM parser. Sorry, Oliver,” he calmly replied and cracked his neck. “I would really prefer a good cup of coffee right now,” he mumbled to himself, thinking back to a time when he still had the material and the time for that. But those days were gone… just like someone he knew.

“Figured. Well, if you need a good laugh, look at the proposed plans of the ‘Chief’. Honestly, who put him in charge?” Oliver sighed and pointed to the double doors, which used to be glass doors, but due to the explosions, all of it had been shattered. Now they were patched up with some wooden planks. Notes were usually being hammered onto them whenever a new decision had been made.

Stephan approached the doors, looking for a new sheet of paper he hadn’t seen. There were actually a lot of others: Information regarding meetings, a memorial for the lost people, which people belong to which group, some kind of menu for the week, and some kind of Impediment Backlog for any problems.

The new paper was hanging on the top left, a pretty bad place to hang something, since short people had a hard time reading that. He didn’t have that problem, but he knew someone who would.

There were plans for leaving the town and sending people to scavenge in the other cities. Most towns had been evacuated after the first bombs hit, so the only people living around these parts were them and some who refused to leave.

The only reason why soldiers were being sent here was that they kept refusing to bow to the invaders. Seemed pretty cliché. Well, it wasn’t so cliché that Austria was being bombarded and attacked all the time, while the rest of the European union didn’t do a thing to help them. It was true that they were also being attacked, but not as bad as Austria. The whole situation was messy and confusing, and even they didn’t know what was happening or who was attacking.

The only things they knew were the following: Some nation dropped bombs on Austria and was now sending soldiers to destroy and occupy them, but there was also war happening in the other European countries. Radio and television were no longer running, just like the internet – so it was basically impossible to find out what really was happening. Even electricity was scarce nowadays. This whole situation wasn’t that much different from any 08/15 dystopian war novel.

They had spent the last few months just trying to build a base here, since it was extremely dangerous to roam outside the cities. Most of the forests had been destroyed by bombs and fires, thus making it hard to hide from enemy scouts.

However, there was one thing that allowed them to defend the base from following bombs that the enemies were dropping on them.

It was one certain thing, that was triggered inside of them during the first attack. One thing he himself was able to do, but not many others.

Shortly after the first bombs had fallen, he was patrolling nearby, when three enemy soldiers ambushed him. He was able to flee behind some rubble, but still got hit in the shoulder by a shot. The pain made his sight blurry and his aim shaky. He wasn’t able to hit anything in this condition, and the enemies knew. They were approaching him, only a few metres between them, when the final thought of dying hit him.

He was about to die. Probably a slow death, as they would take their time with him.

The thought of dying like this triggered it.

The first soldier finally jumped over the rubble, aiming at him with a grin, only for his head to implode into tiny bits.

Milliseconds passed, in which the second and third soldiers only had begun to realize that their companion had been killed, before it happened again.

It wasn’t their heads that were exploding. It was a bullet with an unimageable force that was destroying them, shot by a shaking rifle, but never missing its target.

He had the ability to hit any target with his bullets, no matter the condition.

The first time it happened, he said it was luck. The second time, it was per pure chance. The third time, he began to wonder how he had been able to hit the sniper hidden between rubble through a tiny crack.

And with the fourth time, he realized that some of his friends had their own abilities as well.

Whatever had happened that day when the first bomb had fallen – something had changed inside of them, giving them powers beyond imagination.

And sometimes, when he was about to fall asleep, a tiny, lost memory would appear before his eyes, the memory of a person surrounded by burning corpses, wielding some kind of power like all of them, but long before they had encountered it.

Slowly, he came back to reality, shaking his head and forfeiting the trail of memories he had been following. There was no time to get lost in the past.

Again, he looked at the announcement. The Chief had already chosen some groups which were to explore the area and find out what had triggered all of this tragedy.

He slowly looked at the short list of groups. Only four had been chosen, each having been assigned to one cardinal point.

West – Group 2, the Drunken Heroes.

East – Group 9, the Lost Memory Drive.

North – Group 11, the Stack Overflow.

He was still grimacing over those bad group names, when he reached the group assigned to the South. Group 7.

The Bible Study Group.

HELP ME

Thu, 25 Jun 2026 00:00:00 GMT

MAH

Chapter 0 - The white noise, suppressing your memories

Wed, 24 Jun 2026 00:00:00 GMT

Agonizing, unbearable pain. Aching bones, the feeling of being crushed alive. A thousand needles constantly being pinched inside your head, over and over again. Hot, burning blood, colouring your world completely red. How did this happen?

White noise filled his head, while he was still trying to keep his mind focused. He tried lifting his body, but slowly realized that his lower part had been crushed by rubble. His consciousness was barely there, which was why he couldn’t feel the pain. It was some kind of luck.

As he slowly looked around him, he started to recognize familiar faces, some of which were nearly unrecognizable.

Crushed under a pillar lay one of his colleagues, his ginger beard not being the only thing that was coloured in a tone of red. He was still breathing, but not awake. The first explosion had been near him, probably knocking him through the glass of the building next to him. Shards were still around him, but also sticking out of various regions of his body.

The pain was probably unimaginable.

Not far to the left of his first colleague lay another one. Tall, but skinny, with brown hair, which was darker than usual, due to the amount of blood that was still leaking from his head. He could see him twitch and try to lift himself up, but the huge glass shards inside his legs were probably keeping him from doing that. But he was still alive.

The white noise was slowly fading away, only for him to hear the agonized pants of a familiar voice to his far left.

The woman laying there was trying her best to just breath and not lose consciousness. Part of her body had been burned severely when the first bomb detonated next to them. She had been one of the many people who weren’t able to hide behind a pillar or a wall. Now she was probably the only one who had survived this ordeal – at least now. Her glasses were gone, probably part of all the shards and sharp pieces laying all around them. Her brown hair was now short, as part of it had been burned with the first detonation.

His own sight started to become blurry again. His crushed body started to overwhelm him with pain, coming from every muscle and every bone he had – and there was also the hot blood that was still flowing out of his injury on his head, covering half his face. Breathing became harder, shorter, more uncoordinated. He wanted to scream and cry, but his voice was gone. All he could do was to endure the pain, slowly losing consciousness.

Amidst the rubble and the bodies, he could see one person stand upright, hurt like everyone else, but so different.

The person turned around, returning his gaze.

A cracked smile and a crushed soul were the last things he saw. Then darkness came and put him to sleep.

The ordeal had begun.

Test

Mon, 22 Jun 2026 00:00:00 GMT

This is an attempt at testing

Some test or something what do I know?

---
title: Test
published: 2026-6-22
tags: [Markdown, Blogging, Demo]
category: Examples
draft: false
---

Markdown Extended Features

Wed, 01 May 2024 00:00:00 GMT

GitHub Repository Cards

You can add dynamic cards that link to GitHub repositories, on page load, the repository information is pulled from the GitHub API.

::github{repo="Fabrizz/MMM-OnSpotify"}

Create a GitHub repository card with the code ::github{repo="<owner>/<repo>"}.

::github{repo="saicaca/fuwari"}

Admonitions

Following types of admonitions are supported: note tip important warning caution

:::note Highlights information that users should take into account, even when skimming. :::

:::tip Optional information to help a user be more successful. :::

:::important Crucial information necessary for users to succeed. :::

:::warning Critical content demanding immediate user attention due to potential risks. :::

:::caution Negative potential consequences of an action. :::

Basic Syntax

:::note
Highlights information that users should take into account, even when skimming.
:::

:::tip
Optional information to help a user be more successful.
:::

Custom Titles

The title of the admonition can be customized.

:::note[MY CUSTOM TITLE] This is a note with a custom title. :::

:::note[MY CUSTOM TITLE]
This is a note with a custom title.
:::

GitHub Syntax

[!TIP] The GitHub syntax is also supported.

> [!NOTE]
> The GitHub syntax is also supported.

> [!TIP]
> The GitHub syntax is also supported.

Spoiler

You can add spoilers to your text. The text also supports Markdown syntax.

The content :spoiler[is hidden ayyy]!

The content :spoiler[is hidden **ayyy**]!

Expressive Code Example

Wed, 10 Apr 2024 00:00:00 GMT

Here, we'll explore how code blocks look using Expressive Code. The provided examples are based on the official documentation, which you can refer to for further details.

Expressive Code

Syntax Highlighting

Regular syntax highlighting

console.log('This code is syntax highlighted!')

Rendering ANSI escape sequences

ANSI colors:
- Regular: [31mRed[0m [32mGreen[0m [33mYellow[0m [34mBlue[0m [35mMagenta[0m [36mCyan[0m
- Bold:    [1;31mRed[0m [1;32mGreen[0m [1;33mYellow[0m [1;34mBlue[0m [1;35mMagenta[0m [1;36mCyan[0m
- Dimmed:  [2;31mRed[0m [2;32mGreen[0m [2;33mYellow[0m [2;34mBlue[0m [2;35mMagenta[0m [2;36mCyan[0m

256 colors (showing colors 160-177):
[38;5;160m160 [38;5;161m161 [38;5;162m162 [38;5;163m163 [38;5;164m164 [38;5;165m165[0m
[38;5;166m166 [38;5;167m167 [38;5;168m168 [38;5;169m169 [38;5;170m170 [38;5;171m171[0m
[38;5;172m172 [38;5;173m173 [38;5;174m174 [38;5;175m175 [38;5;176m176 [38;5;177m177[0m

Full RGB colors:
[38;2;34;139;34mForestGreen - RGB(34, 139, 34)[0m

Text formatting: [1mBold[0m [2mDimmed[0m [3mItalic[0m [4mUnderline[0m

Editor & Terminal Frames

Code editor frames

console.log('Title attribute example')

<!-- src/content/index.html -->
<div>File name comment example</div>

Terminal frames

echo "This terminal frame has no title"

Write-Output "This one has a title!"

Overriding frame types

echo "Look ma, no frame!"

# Without overriding, this would be a terminal frame
function Watch-Tail { Get-Content -Tail 20 -Wait $args }
New-Alias tail Watch-Tail

Text & Line Markers

Marking full lines & line ranges

// Line 1 - targeted by line number
// Line 2
// Line 3
// Line 4 - targeted by line number
// Line 5
// Line 6
// Line 7 - targeted by range "7-8"
// Line 8 - targeted by range "7-8"

Selecting line marker types (mark, ins, del)

function demo() {
  console.log('this line is marked as deleted')
  // This line and the next one are marked as inserted
  console.log('this is the second inserted line')

  return 'this line uses the neutral default marker type'
}

Adding labels to line markers

// labeled-line-markers.jsx
<button
  role="button"
  {...props}
  value={value}
  className={buttonClassName}
  disabled={disabled}
  active={active}
>
  {children &&
    !active &&
    (typeof children === 'string' ? <span>{children}</span> : children)}
</button>

Adding long labels on their own lines

// labeled-line-markers.jsx
<button
  role="button"
  {...props}

  value={value}
  className={buttonClassName}

  disabled={disabled}
  active={active}
>

  {children &&
    !active &&
    (typeof children === 'string' ? <span>{children}</span> : children)}
</button>

Using diff-like syntax

+this line will be marked as inserted
-this line will be marked as deleted
this is a regular line

--- a/README.md
+++ b/README.md
@@ -1,3 +1,4 @@
+this is an actual diff file
-all contents will remain unmodified
 no whitespace will be removed either

Combining syntax highlighting with diff-like syntax

  function thisIsJavaScript() {
    // This entire block gets highlighted as JavaScript,
    // and we can still add diff markers to it!
-   console.log('Old code to be removed')
+   console.log('New and shiny code!')
  }

Marking individual text inside lines

function demo() {
  // Mark any given text inside lines
  return 'Multiple matches of the given text are supported';
}

Regular expressions

console.log('The words yes and yep will be marked.')

Escaping forward slashes

echo "Test" > /home/test.txt

Selecting inline marker types (mark, ins, del)

function demo() {
  console.log('These are inserted and deleted marker types');
  // The return statement uses the default marker type
  return true;
}

Word Wrap

Configuring word wrap per block

// Example with wrap
function getLongString() {
  return 'This is a very long string that will most probably not fit into the available space unless the container is extremely wide'
}

// Example with wrap=false
function getLongString() {
  return 'This is a very long string that will most probably not fit into the available space unless the container is extremely wide'
}

Configuring indentation of wrapped lines

// Example with preserveIndent (enabled by default)
function getLongString() {
  return 'This is a very long string that will most probably not fit into the available space unless the container is extremely wide'
}

// Example with preserveIndent=false
function getLongString() {
  return 'This is a very long string that will most probably not fit into the available space unless the container is extremely wide'
}

Collapsible Sections

// All this boilerplate setup code will be collapsed
import { someBoilerplateEngine } from '@example/some-boilerplate'
import { evenMoreBoilerplate } from '@example/even-more-boilerplate'

const engine = someBoilerplateEngine(evenMoreBoilerplate())

// This part of the code will be visible by default
engine.doSomething(1, 2, 3, calcFn)

function calcFn() {
  // You can have multiple collapsed sections
  const a = 1
  const b = 2
  const c = a + b

  // This will remain visible
  console.log(`Calculation result: ${a} + ${b} = ${c}`)
  return c
}

// All this code until the end of the block will be collapsed again
engine.closeConnection()
engine.freeMemory()
engine.shutdown({ reason: 'End of example boilerplate code' })

Line Numbers

Displaying line numbers per block

// This code block will show line numbers
console.log('Greetings from line 2!')
console.log('I am on line 3')

// Line numbers are disabled for this block
console.log('Hello?')
console.log('Sorry, do you know what line I am on?')

Changing the starting line number

console.log('Greetings from line 5!')
console.log('I am on line 6')

Simple Guides for Fuwari

Mon, 01 Apr 2024 00:00:00 GMT

Cover image source: Source

This blog template is built with Astro. For the things that are not mentioned in this guide, you may find the answers in the Astro Docs.

Front-matter of Posts

---
title: My First Blog Post
published: 2023-09-09
description: This is the first post of my new Astro blog.
image: ./cover.jpg
tags: [Foo, Bar]
category: Front-end
draft: false
---

Attribute	Description
`title`	The title of the post.
`published`	The date the post was published.
`description`	A short description of the post. Displayed on index page.
`image`	The cover image path of the post.<br/>1. Start with `http://` or `https://`: Use web image<br/>2. Start with `/`: For image in `public` dir<br/>3. With none of the prefixes: Relative to the markdown file
`tags`	The tags of the post.
`category`	The category of the post.
`draft`	If this post is still a draft, which won't be displayed.

Where to Place the Post Files

Your post files should be placed in src/content/posts/ directory. You can also create sub-directories to better organize your posts and assets.

src/content/posts/
├── post-1.md
└── post-2/
    ├── cover.png
    └── index.md

Markdown Example

Sun, 01 Oct 2023 00:00:00 GMT

An h1 header

Paragraphs are separated by a blank line.

2nd paragraph. Italic, bold, and monospace. Itemized lists look like:

this one
that one
the other one

Note that --- not considering the asterisk --- the actual text content starts at 4-columns in.

Block quotes are written like so.

They can span multiple paragraphs, if you like.

Use 3 dashes for an em-dash. Use 2 dashes for ranges (ex., "it's all in chapters 12--14"). Three dots ... will be converted to an ellipsis. Unicode is supported. ☺

An h2 header

Here's a numbered list:

first item
second item
third item

Note again how the actual text starts at 4 columns in (4 characters from the left side). Here's a code sample:

# Let me re-iterate ...
for i in 1 .. 10 { do-something(i) }

As you probably guessed, indented 4 spaces. By the way, instead of indenting the block, you can use delimited blocks, if you like:

define foobar() {
    print "Welcome to flavor country!";
}

(which makes copying & pasting easier). You can optionally mark the delimited block for Pandoc to syntax highlight it:

import time
# Quick, count to ten!
for i in range(10):
    # (but not *too* quick)
    time.sleep(0.5)
    print i

An h3 header

Now a nested list:

First, get these ingredients:
- carrots
- celery
- lentils
Boil some water.

Dump everything in the pot and follow this algorithm:

 find wooden spoon
 uncover pot
 stir
 cover pot
 balance wooden spoon precariously on pot handle
 wait 10 minutes
 goto first step (or shut off burner when done)

Do not bump wooden spoon or it will fall.

Notice again how text always lines up on 4-space indents (including that last line which continues item 3 above).

Here's a link to a website, to a local doc, and to a section heading in the current doc. Here's a footnote [^1].

[^1]: Footnote text goes here.

Tables can look like this:

size material color

9 leather brown 10 hemp canvas natural 11 glass transparent

Table: Shoes, their sizes, and what they're made of

(The above is the caption for the table.) Pandoc also supports multi-line tables:

keyword text

red Sunsets, apples, and other red or reddish things.

green Leaves, grass, frogs and other things it's not easy being.

A horizontal rule follows.

Here's a definition list:

apples : Good for making applesauce. oranges : Citrus! tomatoes : There's no "e" in tomatoe.

Again, text is indented 4 spaces. (Put a blank line between each term/definition pair to spread things out more.)

Here's a "line block":

| Line one | Line too | Line tree

and images can be specified like so:

Inline math equations go in like so: $\omega = d\phi / dt$. Display math should get its own line and be put in in double-dollarsigns:

$$I = \int \rho R^{2} dV$$

$$ \begin{equation*} \pi =3.1415926535 ;8979323846;2643383279;5028841971;6939937510;5820974944 ;5923078164;0628620899;8628034825;3421170679;\ldots \end{equation*} $$

And note that you can backslash-escape any punctuation characters which you wish to be displayed literally, ex.: `foo`, *bar*, etc.

Include Video in the Posts

Tue, 01 Aug 2023 00:00:00 GMT

Just copy the embed code from YouTube or other platforms, and paste it in the markdown file.

---
title: Include Video in the Post
published: 2023-10-19
// ...
---

<iframe width="100%" height="468" src="https://www.youtube.com/embed/5gIf0_xpFPI?si=N1WTorLKL0uwLsU_" title="YouTube video player" frameborder="0" allowfullscreen></iframe>

YouTube

Bilibili

Draft Example

Fri, 01 Jul 2022 00:00:00 GMT

This Article is a Draft

This article is currently in a draft state and is not published. Therefore, it will not be visible to the general audience. The content is still a work in progress and may require further editing and review.

When the article is ready for publication, you can update the "draft" field to "false" in the Frontmatter:

---
title: Draft Example
published: 2024-01-11T04:40:26.381Z
tags: [Markdown, Blogging, Demo]
category: Examples
draft: false
---