As a teenager, I was into aviation, hung out at airports, and collected postcards of airplanes. The Boeing 747, the jumbo jet, was the obvious crown jewel. Seeing one, or receiving a postcard of one, brought a jolt of joy.

The Atlantic has an article about the Boeing 747 that revealed some details I didn’t know. The 747 was originally built with cargo in mind: with the pilots on the upper deck, the nose could be opened to front-load the containers. Since supersonic flight was all the rage in the 60s, Boeing believed that would be the destiny of a big, slow plane. When the 747 was used mostly for passengers, airlines had all kinds of fancy ideas for what to do with the space. Very different from the squeezed-like-sardines concepts they use today.

The article also shows why modern journalism can be so tedious. The writer tried hard to produce the everything-gets-worse narrative that the media (and selfish politicians) love so much.

But while the golden age of flying in the 70s was lavish, with jumbos offering space, bars, and lounges, better safety, and the affordability of flights today are certainly an improvement.

Saturday Matinee Game.

Today's MLB game of choice, Texas Rangers vs Toronto Blue Jays, has a start time of 2:07 PM CDT. As I usually do, I'll follow the game's score and stats as they change in in real time via MLB's Gameday Service, where we can also find a link to the radio-call of the game.

And the adventure continues.

I woke up with a bleeding mouth because of that lovely dream i was having. It never changed. It never does, i coughed blood all over the bed and went to the bathroom to clean it, but there wasn’t a single drop of blood. I went to bed and the same thing, i was choking on nothing, and i guess that’s how i started my day, either way. I had a wedding last night, so perhaps the blood was the suffocating acting i had to present to look sane while my whole system is telling me to leave, my aunt was getting married that night, and I shouldn’t miss it because “family comes first,” something I’ve heard while walking past an empty graveyard. Well, whatever, it happened, and i had to deal with it, it wasn’t that of a boring day after all. Such an eventful day. Anyway, after all that, i still had to deal with my housemate’s “situation”. because of course i did, there’s always something waiting in the background, like it pays rent too. He’s still not done arguing about whatever the original problem was. I don’t even remember how it started anymore, but i dont think he does either, which somehow makes it worse. It’s reached the stage where the topic stopped mattering halfway through, but now it’s just about winning or whatever people call it when they refuse to stop talking. And im tired. Like actually tired, and not the ” sleep and you’ll be fine” kind, the whole day feels like it got pressed into one long heavy block and then dropped on me at random intervals. i slept most of the day after getting back, which should’ve fixed it, but it didn’t. if anything, it just made me feel more behind on being awake. Im still tired and nothing really feels finished. The argument isn’t finished. The day doesn’t feel finished. even my own thoughts feel like they stopped mid-sentence and forgot where they were going.

I’ll probably just stay up for a bit longer. Not because i want to. Just because going back to sleep feels like it won’t actually change anything, and im not in the mood to find out im right again.

Sincerely, Tired Ahmed

besoknya di pertemuan mereka, orang tua Miya dan orang tua Kiyoomi berkumpul di ruang tamu rumah Kiyoomi. sakusa menatap Atsumu dengan tajam dan penuh keseriusan. ayahnya berbincang bincang dengan ayah Miya karena mereka teman dekat. “jadi, apa anda menyetujui perjodohan ini Kenzi?” ujar ayah Kiyoomi menyebut nama ayah Miya.

“oh jelas lah, Atsumu anak yang penurut. jadi dia hanya mengiyakan perjodohan ini. bagaimana dengan anak anda?” tanya ayah Miya dengan senyum. Sakusa memalingkan wajahnya dengan kesal, ayahnya hanya bisa menghela nafas.

“Sakusa harus dipaksa untuk menerima perjodohan ini, dia memang aneh.” jawab ayah Kiyoomi dengan tegas.

“Ahahaha, tidak apa apa. jangan terlalu ditekan, biarkan saja.”

berbincang lama, ayah Kiyoomi menyuruh Sakusa untuk berkenalan dengan Atsumu. tetapi Sakusa menolak dengan tegas. “tidak. Papa, aku sudah bilang. aku punya pacar!” ujarnya dengan kasar. ayah Kiyoomi tiba tiba diam, ia menahan emosinya.

“Sakusa, berapa kali papa bilang? putuskan pacarmu.” Sakusa tetap menggeleng dengan keras kepala.

“tidak akan. aku tidak akan menuruti perintah kalian.” ujarnya dengan tegas membuat kepala Ayahnya pusing. ia memukul meja dengan keras.

“Sakusa Kiyoomi. kenapa kamu keras kepala sekali?” dia berhenti sejenak sebelum melanjutkan.

“kamu tidak punya hak untuk menolak perjodohan ini. kalaupun kau memaksa, papa akan memblokir semua kartu dan menyita ponselmu. jadi gelandangan saja dengan pacarmu itu.” Sakusa terdiam, dadanya sesak, rasanya ia tidak bisa berbicara lagi. ibu Kiyoomi panik, ia segera menenangkan ayah Kiyoomi agar tenang dan tidak terbawa suasana.

“mau kamu jadi gelandangan sama pacarmu yang tidak seberapa itu? cantik saja tidak, matre iya!” sial, sepertinya Sakusa tertusuk oleh pisau di perutnya karena perkataan ayahnya. sangat tajam, sangat menusuk.

Sakusa hanya diam, ia tidak bisa berkata kata. Atsumu yang melihat juga tidak bisa apa apa. ia anak penurut walaupun dia aktif. Atsumu mengenal Sakusa dari lama, namun ia tidak mempunyai rasa apapun kepada Sakusa. namun demi orang tua, ia memaksa dirinya karena ini perjodohan paksa.

Sakusa, pria bodoh yang menjadi bahan ghibahan murid murid SMA Haikyuu. anehnya, Sakusa tidak peduli apa yang dikatakan mereka, ia mencintai pacarnya, selesai. banyak yang bergosip tentang pacar Sakusa, cewek matre yang memandang uang Sakusa. banyak sekali orang yang menemuinya bersama pria lain. tapi jawaban Sakusa tidak sesuai harapan mereka.

ada apa dengan pria ini? apa dia dipelet oleh cewek itu?

suatu hari Sakusa dipanggil orang tuanya untuk pergi ke dapur dan makan. saat makan malam, ayahnya berbicara. “Sakusa, ibu dan ayah akan menjodohkan mu.” Sakusa terkejut dan tersedak nasi nya saking terkejutnya. ia bingung, apa maksud orang tuanya untuk menjodohkannya?!

“dijodohkan? dengan siapa?” tanya Sakusa dengan datar.

“Papa menjodohkan mu dengan orang bernama Atsumu Miya. dia juga sekolah di SMA Haikyuu. apa kau kenal?” sakusa menggeleng pelan, ia sama sekali tidak mengenali siapa Atsumu Miya, namun mendengar 'Miya' itu seperti tidak asing.

“kenapa aku dijodohkan?” Sakusa menatap penuh keseriusan ayahnya terdiam sejenak dan membalas.

“Papa tidak suka dengan pacar mu.” //DEGG.

Sakusa terdiam sejenak, ia minum air nya dan menatap dengan tajam. “apa maksud papa? kenapa dengan pacarku? kenapa semua orang membenci dia?” tanya Sakusa dengan tegas.

ibunya menghela nafas pelan, ia menaruh sup ke piringnya dan berkata. “nak, dia hampir saja mencuri uang mu, apa kamu lupa? dia juga mencoba mengambil dompet yang ada di dompet Mama.” sakusa terdiam sejenak, ia tidak bisa berpikir lagi.

“tapi Ma—” ayahnya memotong perkataannya

“tidak ada tapi tapi. kamu dijodohkan. ayah tidak peduli kau terima atau tidak.” Sakusa terdiam.

Bagaimana ini? ia harus apa?

This is the sequel to how to self-host a tangled git server without Bluesky. That post gets you a live git server, owned by your own AT Protocol identity, on your own domain. This one is the next five minutes — actually pushing a repository to it and watching the wire close.

Same honesty disclaimer as before: I'm not a protocol person. What follows is a recipe I worked out by doing it, getting it wrong, and reading the logs with an LLM that knew where to look. It works. It's not authoritative.

Here's the whole thing, upfront:

git remote add knot git@knot.suranyami.com:did:plc:akmmkxg66qtexw6pl6erhwfe
git push knot main

That's a real command against my real server. The did:plc:... is the repo's permanent ID, not yours. We'll get to why it looks like that. Read on for the three steps and the two ways I embarrassed myself getting there.

---

The thing nobody explains: there are two DIDs

Before the steps, one concept that had me stuck for an embarrassing amount of time. A tangled server deals in two different AT Protocol identities, and the clone URL uses the one you're not expecting.

• Your identity — the DID that owns the repo. Mine is did:plc:tg42msv45ief3qphccenrogh, handle forge.suranyami.com. This is you. You logged in as this.
• The repo's identity — when you create a repo, the server mints a separate DID for the repo itself. That's the did:plc:akmmkxg66qtexw6pl6erhwfe in the clone URL. It's not you. It's the repo's own permanent ID, anchored to the server.

So the clone URL is not git@your-server:you/repo, the way it would be on GitHub or Forgejo. It's git@your-server:<repoDid> — the repo's own DID, bare, no username, no repo name, no .git. That's the permalink form tangled gives you, and it's the one that actually works.

If that feels weird, it is. It's also the whole point of federated identity — the repo is a first-class object with its own ID that survives any one server, not a path under someone's account. Whether that's worth the cognitive tax is a separate question. Today we're just making it work.

---

Step 1 — make the repo on tangled.org

Sign in at tangled.org as your self-hosted handle. Create a repo:

• Owner: your identity (forge.suranyami.com).
• Host: your server (knot.suranyami.com).
• Name: whatever you want it called.

Tick “Use permalink” when it offers a clone URL. That gives you the git@your-server:did:plc:<repoDid> form — the one that works. Copy it. (There's no .git on the end. There is never a .git on the end. More on that in a minute.)

Which repo to push? I used a real one — maze, a Phoenix app that's already public on GitHub with no live secrets in its history. A tangled server is publicly-browsable federated git. There is no private-repo toggle. It is a different threat model from GitHub, where you can shove secrets into a private repo and trust the platform's access control. Here you cannot. So pick something you'd happily publish to the world — because you are.

If your repo has ever tracked real credentials, that's a job for git filter-repo and a quiet rotation, not a knot push. I have one of those coming myself. Not today.

---

Step 2 — register your SSH key

Same settings page on tangled.org: paste your public key (~/.ssh/id_ed25519.pub or equivalent), give it a name.

One thing I had backwards: the key lands on your identity immediately, at registration — not lazily on your first push. The model I was carrying in my head (from half-reading the docs) was “first git sign mints the key.” That's a real concept, but it's the server's own signing keypair, a separate thing. Your SSH key, the one that authenticates you to the server over SSH, is written the moment you register it. So if you can ssh git@your-server and get accepted before you've ever pushed, that's why.

Test it:

ssh -T git@knot.suranyami.com
# Welcome to this knot!        ← see the note below before you panic

If you get Permission denied (publickey), the key isn't registered (or isn't the one your agent is offering). If you get the welcome line, you're in.

---

Step 3 — add the remote and push

cd path/to/your-repo
git remote add knot git@knot.suranyami.com:did:plc:<repoDid>
git push knot main

knot is just a remote name — call it tangled, origin2, whatever. I used knot because the env vars already call it that and I'd lost the energy to fight the branding in two places.

That's the happy path. It worked for me, second try. The first try — and a chunk of lost afternoon — is the actual story.

---

Two ways I broke this, and the lesson in each

The clone URL has no .git, and that is not optional

I did what you do with every git remote I've ever configured: I appended .git. Muscle memory. The server returned 404 repo not found.

The reason is in the server's lookup table. When you ask for did:plc:.../maze.git, the server's guard looks up the name with the .git suffix — but it stores repo aliases under the bare name (maze). So maze.git never matches, and you get a 404 for a repo that definitely exists. Drop the .git and it resolves.

This is the kind of bug that's invisible until you read the guard's own log, which lives at /home/git/guard.log inside the server container:

docker exec <tangled-container> cat /home/git/guard.log
# status=200 OK  fullPath=/home/git/repositories/did:plc:akmmkxg66qtexw6pl6erhwfe
# command completed success=true

That log is the authoritative source of truth for “did the server accept my request.” git's own stdout is a liar by omission here, because of the second bug:

Welcome to this knot! is not an error

The server prints a welcome banner — a MOTD — on stderr before it exec's the actual git command. For a brand-new empty repo, git-upload-pack emits zero refs, so the only thing you see is the MOTD. To the naked eye that looks identical to “the push failed and printed a message.” It didn't. exit=0 is the signal. The banner is noise.

I spent a genuinely silly amount of time convinced my first push had failed because of that banner, and then a sillier amount of time convinced the clone URL David had pasted me was truncated (no repo name, no .git — surely that's wrong). It wasn't truncated. It was the correct permalink form. I just couldn't see past the MOTD.

The lesson, for the third time in as many weeks: when a command's human-readable output and its exit code disagree, the exit code is the one telling the truth. Read the log the server itself keeps, not the string git happened to surface.

---

Proving it landed

Once the push returns * [new branch] main -> main, verify from the outside:

# clone it back, from anywhere
git clone git@knot.suranyami.com:did:plc:akmmkxg66qtexw6pl6erhwfe /tmp/knot-clone
cd /tmp/knot-clone && git log --oneline    # your full history, from the server

Or ask the server's own API what branches it knows about:

curl -s "https://knot.suranyami.com/xrpc/sh.tangled.repo.branches?repo=did:plc:akmmkxg66qtexw6pl6erhwfe" | jq .
# [{ "name": "main", "hash": "8bf07b2...", "is_default": true }]

And because this is federated identity, the push also wrote records back to your PDS — the git event is signed into your identity's record store, which is the whole mechanism by which other servers discover and mirror your repo. Check the collections on your owner DID:

curl -s "https://pds.suranyami.com/xrpc/com.atproto.repo.describeRepo?repo=did:plc:tg42msv45ief3qphccenrogh" \
  | jq '.collections'
# ["io.atcr.sailor.profile","sh.tangled.actor.profile","sh.tangled.knot",
#  "sh.tangled.publicKey","sh.tangled.repo"]

sh.tangled.repo turning up is the push having made it all the way through to the identity layer. That's the wire closing.

---

What you end up with

• A repo on a git host you own, on a federated network that no single company controls.
• A clone URL that's a permanent ID, not a path under someone's account — ugly, but it survives a server move in a way you/repo never could.
• The same one-file-backup discipline as the self-hosting post: your .env (and the rotation key inside it) is your identity. Lose it and the repo's ownership goes with it.

None of this needed me to be a protocol expert, and I'm still not one. It needed the working command, the two gotchas that stop it from working, and the willingness to read the server's own log instead of trusting git's summary. If you've already got the server up, the push is five minutes. The debugging around it took longer than both posts combined.

Hello again, it’s me!

I’m on the train again. A slightly older one without AC, but which has wooden panelling and blue seats.

I’m hearing the wind through the window which is slightly opened.

I am happy with a bit of melancholy mingled into it, bittersweet.

I don’t want to poke into this state of mind right now. Let’s just say that it’s a sore and it itches, but let’s not pick this scab right now, it’ll just make things worse. I think.

Sometimes strong ruthless introspection is the key to progress.

Sometimes it’s best to leave it be.

And that’s that; don’t force conclusions; life is a marathon.

I’m not hungover today, but I didn’t sleep until four, hearing the rain smattering on the roof and I was right by the ceiling

Picturing I was in a tent,

Then thinking about all the blood pumping through my body.

Five litres of blood.

Thinking that I likely have gotten rosacea on my nose through DNA

Thinking that it would help with some cortisone

Thinking that it’ll solve itself once I get back into my regular fitness routine.

All things considered: having these random pointless thoughts and being uncomfortable in a cozy type of way.

I guess that reflects my inner state of mind right now too: The rain on the ceiling.

Yes.

And now I’m going home.

Occasionally, I like to have a look through our archived blogs. Sometimes, it turns out to be an exercise in seeing just how far our position on an issue has evolved and altered. At other times, it’s finding that there are some aspects of what we do and how we see situations that have always remained pretty constant. One thing we have always been absolutely consistent about is the need to build/re-build a sense of solidarity at the grassroots in our communities. This goes right back to our days in the Independent Working Class Association. When I was looking through the long ago archived archived South Essex Heckler, I found the piece below which although it was written seven years ago, still holds true in my opinion. I’m reproducing the piece from the Heckler below exactly as it was first published so, all of the references will concern projects we were supporting when we were living back in Essex:

Rebuilding solidarity at the grassroots… June 25, 2019

Where we are

We’ve had over ten years of austerity and it’s leaving our class in an increasingly precarious state. A brutal benefits regime is pushing more people into desperate poverty, homelessness, a greater likelihood of premature death and towards suicide. Even at the surface level, it’s impossible to escape the neglect and physical decay that’s blighting more and more of our neighbourhoods. As housing tenure becomes ever more precarious, the sense of community solidarity that could play a role in pulling people back from the brink is fracturing and dying.

So long as the authorities can keep the lid on the situation in the neighbourhoods where austerity has hit the hardest, they’ve no problem with the fracturing of community solidarity. The truth is, they actively pursue the project of undermining our solidarity by dividing us into the ‘hard-working and deserving’ and the ‘work shy, feckless and undeserving’. When you challenge this by showing the number of in work households who are in receipt of benefits, they’ll imply that the working poor need to be striving harder. All of this is exacerbated by the other games of divide and rule as the so called ‘indigenous’ working class is pitted against allegedly ‘job stealing’ migrants. Further exacerbation comes with the denigration of anyone who steps out of the bounds of an increasingly resurgent traditional ‘conventionality’ and tries to live some kind of alternative lifestyle.

It only takes a loss of employment and income to propel someone from being ‘hard-working’ to being ‘idle’, ‘a burden’ and on benefits. Also, unless someone is in the top quarter of the social pecking order, not only are they at risk of immiseration in an increasingly precarious world, regardless of who they, crumbling public services and infrastructure will be impacting on their lives. In terms of what we have to put up with, there’s more that should be uniting us than dividing us. Despite what the powers that be who want us divided and at each others throats may wish for, the blunt truth is that a lot of us are in this together.

Start at the grassroots

So, how can we start to re-build the sense of solidarity we need to fight back against this and eventually, build the better world that we deserve? Start small and start right at the grassroots where you live. A simple act of solidarity is looking out for the neighbours on either side of you and for them to do the same. Even if it’s a house of multiple occupation, quite often, it’s possible to strike up a rapport. We’ve seen this happen with a member of the Vange Hill Community Group reaching out to and forming a working relationship with EU migrants in a house of multiple occupation in their close.

In order to get people to know each other a bit better, canvass opinion and organise a practical activity such as a community clean up. Not only will you see a physical difference after a few hours graft, for a lot of people, doing something collectively with their neighbours will be an empowering experience. Even if it’s just a close or a small street, it’s a start and if people on other parts of the estate see what’s been achieved, hopefully they’ll be inspired to do the same.

One step up from a clean up is starting a community garden if you can find a suitable location. That can be anything from putting in a few flower beds to brighten up an otherwise dreary close to starting to grow your own vegetables and fruit – or doing both if you feel ambitious enough and can get enough people involved. As to whether you want to ask the council for permission first, it’s entirely down to you. If your council has a record of being uncooperative when dealing with tenants and residents on your estate, just go ahead and do it anyway. Given how stretched councils are, providing you’re sensible, they’ll most likely leave you alone. If they do decide to get stroppy, mounting a campaign to save your garden will bring people together and should you win, will give morale in your part of the estate a significant boost.

Organising regular cleaning, doing whatever maintenance you feel you can take on and running a community garden will bring people together. Also, picking up the skills needed to this this acts as a boost to people’s confidence and self esteem. Not everyone will be able to make an equal contribution because of time pressure or disability – accept that any contribution is valid and ensure support from those who can’t take part is valued. Once a level of cohesion has been built up, work out ways of making sure that vulnerable people in your community are being checked up and their needs are being met.

On isolated estates, food poverty can be an issue due to the lack of shops selling decent quality, affordable food and poor public transport to shopping areas where a wider range of food is available. As well as running a community vegetable and fruit garden, you could start to think about an estate run food bank or food buying group. Obviously, this takes more effort and there’s a learning curve involved but if you put the effort in, you’ve achieved a vital objective – getting more control over your food supply.

Use what’s there to help boost community solidarity and morale and also to ensure the needs of the more vulnerable people in your neighbourhood are being met. As anarchists, we’re supposed to reject the church. Well, when a church such as Trinity Methodist Church in Vange has a community cafe for use by the whole neighbourhood, contribute to food banks, offer support to disabled people, run toddler groups, offer youth activities to all young people in the community to name just a few, it would be churlish in the extreme to not accept the help and support they can offer. Essentially, a lot of what they do is not dissimilar to what some more grounded, neighbourhood anarchist groups abroad who’ve got their act together undertake!

We are where we are so the priority has to be re-building community solidarity in whatever ways that work. On top of this, empowering people who want to make life in their neighbourhoods better is an essential task. As we’ve seen from what’s happened with the community run Hardie Park in Stanford-le-Hope, the transformation in the lives of those involved plus the boost to morale in the town proves the worth of sticking at this. Small victories can steadily lead to a growing sense of confidence and collective strength that will give people a growing degree of independence from local and national governance that’s increasingly failing them.

None of this is going to be plain sailing and one of the more difficult parts will be dealing with the anti-social element in a neighbourhood. In an ideal world, those chaotic households where there’s a risk of members falling into anti-social behaviour or crime would be getting helped by the surrounding community. We want to get to the point where that can happen and there’s less need for outside intervention. In the interim, once a degree of community solidarity starts to emerge, the people best placed to decide how to deal with anti-social behaviour are those living in the neighbourhood. They’ll have the knowledge of the perpetrators and a shrewd idea of the risks involved – that will go a long way to enable them to devise a strategy to deal with the situation.

Conclusion

We keep returning to this theme in various forms. We make no apology for this because if we can’t build and nurture a sense of community and solidarity, any other change is pretty much off the agenda. A lot of what has been written above comes from our days in the Independent Working Class Association and then our more recent experiences working with Basildon & Southend Housing Action, Brooke House Residents, Vange Hill Community Group and Friends of Hardie Park.

We don’t pretend to know it all because we don’t and are honest enough to admit that what we do is a constant learning curve. We recognise that some of the more purist anarchists may find that our approach has too many ‘compromises’. The point is not to just theorise and understand the world but to change it. We’re doing what we can with limited resources working with our class at the grassroots, getting our hands dirty (literally sometimes!) to try and make a difference. We hope people can respect that and offer solidarity when we need it…

I think, after all those gods and stuff, the core of Mahikari is attaching spirits, or spirit disturbance. They account for nearly everything you experience in your life. Heaven forbid that there are regular, you know, sciencey or logical reasons for anything.

Photo by Photos_frompasttofuture on Unsplash

Let’s start with what Mahikari says about attaching spirits in Primary Kenshu:

This phenomenon of a spirit attaching [to your body] is called the phenomena of attaching spirits. The person who is attached by a spirit will come to develop similar conditions as the spirit.

For instance, if a person is attached by a spirit who died of tuberculosis … the person will develop tuberculosis, and if a spirit died of asthma attaches to a person, within about a week or so the person will develop asthma. [pg 18]

---

From the various actual examples I have just given, no doubt you understand by now that whether it is sickness, crime or other unhappy phenomena, we can quite clearly state that 80% is caused by spirit disturbance.

No doubt you will experience this from now on. If there are a 100 people, even at a conservative estimate 80 will be receiving some sort of spirit disturbance.

In modern medicine, however, there is no spiritual research done. Without solving problems to do with attaching spirits, such as people dying due to warnings from their ancestors, no matter how people look for happiness, it is impossible.

Here lies a basic mistake in today’s modern medicine. If mankind is really to look for happiness, it is first necessary to become awakened to spirituality and discover the way to solve spirit disturbance. So Sukuinushisama [the founder dude, Okada] often appealed to us that it is essential to awaken to the world of spirit, starting with those who have the attitude to do so, and strive to awaken all humankind to this. [pp 29–30]

So here’s how it goes down. Someone dies – happens to the best of us. Maybe they have a grudge against you (you know, from that time when you …). Maybe they have resentment against your grandfather (it’s OK, we all know he was a bit of a dick). Maybe they are in love with you (naaaaw). Maybe they’re lonely. Maybe they’re out for revenge. Maybe they’re a sneaky fox, raccoon or snake (like, the animals, for reals). Whatever, it typically comes down to your karma, or your family’s sins and impurities.

But – instead of toddling off to the astral world to do their training after death, as they should, they decide to hang around. And they do that by attaching to your spiritual body. Like a remora. Only with more spirit stuff, and less fish.

Photo by The New York Public Library on Unsplash

And when a spirit attaches to you, you get whatever ailment or psychological problem they have. So if they died from heart disease, you’ll get heart disease too.

So Mahikari logic says that if you solve the spirit disturbance, you’ll be healed too. Heal and counsel the spirit so it’s no longer angry or out to get you, or in love with you, or whatevs, then it will release you and go back to the astral world, where it belongs. And all the problems it was causing for you will stop. Simples.

How do you solve spirit disturbance, you ask? Good question!

Well.

What do you know. It mainly involves doing a lot of divine service (unpaid labour!) for the group. ‘Saving others’. This raises your spiritual level, and improves the situation for the attaching spirit.

And sometimes you can have spirit investigations if things are really getting out of hand. This is when one of the doshis (priests) or kanbu (senior staff) gives you Light to the soul spirit (forehead) and talks directly to the attaching spirit during the session. So you have your eyes closed, and they are chatting away to the spirit. They ask it questions like what is it, where did it come from, does it have resentment or love or anger etc towards you, and which part of the body is it attached to.

Sometimes the spirit will make you move, like rocking back and forth, or shaking your head. And they can speak. People report they can suddenly speak another language like Japanese (a popular option) even though they don’t know Japanese! Because the attaching spirit is Japanese (again, a popular option), and is speaking in its own language. I call fucking bullshit. I experienced this, many times, and one time had a Japanese warrior ‘attached to me’. Yes, I spoke Japanese to my inquisitor (who it must be said was speaking English) and all I said was the basic Japanese words I already knew like ‘Yes’ and ‘No’.

At least they are trying to understand and counsel the spirit, to help it give up emotional and physical attachment to you. They aren’t about banishing it. So that’s nice.

In Primary Kenshu they go through a list of all the different types of diseases, and what causes them. Yes! It’s mostly attaching spirits! Surprise! And the rest is caused by toxins. They love toxins. Just a reminder, all medicine is toxins.

The following is typical advice about whatever ailment you care to name:

Women’s Problems:

As for Okiyome, give Okiyome thoroughly on the back and front of the uterus. Also, such things as anteflexion of the uterus, miscarriage, stillbirth, uterine cancer and so on are mostly caused by an attaching spirit with resentment concerning a man-woman relationship. Such resentment from a man-woman relationship may, for example, be if grandfather had had a mistress but left her to die in misery. If things like that happened such spirits become resentful and attach to people. There are many cases where it is due to something that happened with the ancestors about 3-5 generations or so ago. Or it may have something to do with the husband or the wife at the present time.

In such cases, it's necessary to reflect on one's life, and if there's anything that indicates such mistakes, it’s first necessary to apologise saying, 'I won't do anything like that anymore, please forgive me', and receive Okiyome. Otherwise it won't do any good.

Whether it's something to do with the ancestors or oneself, it's important actively to save people to erase such sins. As you save others, your own impurities will be erased and you'll be saved. – Primary Kenshu, pg 117

You might notice the big focus on saving others. Big focus. That means hunting for new members. Constantly. So, to solve the problems that the cult ascribes to attaching spirits, you need to do masses of divine service, and try to get others to join. Convenient (for them).

Also. Attaching spirits can also cause traffic accidents, and interfere with your divine service! No, it’s not your bad driving or your gut telling you you’re in a cult. It’s spirits. The subject for further blog posts. Stay tuned, and til then, be kind to your attaching spirits!

#kenshu #spirits #karma #illness #medicine #health

I found out that G was organizing another girls trip. J told me, And even offered to ask her directly about inviting me. G said that this was just going to be a girls trip. It hurts because there was a trip earlier and G said that next time she would absolutely invite me, and it kind of feels like I’m getting my hopes crushed after getting them raised. I know that there may be valid reasons for it, but it very much hurts in the same way that my childhood did when I would get excluded from things with friends because they were girls and I was not. And it feels like it’s the same thing happening again.

S: G is planning another trip, and explicitly did not invite me because it is going to be a girls trip.

T: it sucks because I don’t see why I couldn’t be invited, and additionally G said that next time she would invite me.

F: I feel like I’m being excluded, and it’s because of my gender. I feel like the friends I consider close are not actually that close to me.

B: I feel like shit, and I pull away from my friendships.

T: This might just be a girls trip in the sense of an existing friend group, and G does enjoy interacting with me and would want to go on a trip, but they already have their established friend group.

F: honestly it still hurts a lot. But I think it hurts a little bit less so. I can talk with my therapist and try to figure out how to not have this bitterness.

B: I talked with my therapist and I don’t punish friendships for this.