Suguru Hirahara @ctonysem@mastodon.technology

Recently I published a co-authored book in Japanese: https://www.kawade.co.jp/np/isbn/9784309249896/

In this book I wrote a relationship between phenomenology and sociology. Its main object is to clarify how it would be possible to set an essential and universal principle of civil society.

https://mbasic.facebook.com/story.php?story_fbid=10164577253060023&id=615100022

On my Twitter account I have made it public that I prefer this mastodon account over it. Sometimes I am going to toot in my native language too.

My twitter account: https://twitter.com/phguides

ツイッターに代えて今はマストドンを主に使用しております。

Wow, does this mean #element was removed because Google did not understand correctly how #matrix works?

Hi @matrix, later please publish this incident as a whole for reference for other startups. Your experience should help them to understand what kind of risk they confront actually. Thanks!

I have never seen Google acts so recklessly like today.

I have completed #degoogle already since one year, so actually not a big deal for me, but I feel very sorry for those who live on its ecosystem.

In Google's ecosystem, you can exists as long as allowed, which is the very logic in authoritarian countries.

For #matrix network, you can find a lot of other choices than #element here: https://matrix.org/clients/

Ditto Chat, Nio, Pattle, FluffyChat, etc.

You see, removing one program arbitrarily does not change the situation.

#google

I wrote how to install #diaspora manually on Debian 10.

https://blog.progressiv.dev/suguru/how-to-install-diaspora-decentralized-social-network-on-debian-10

You should be able to install it by following the steps on the article. I also explained why you should not wait for automated installation tool.

Now setting up #writefreely (write.as) to create another blog.

Wait, does it support federation too?

https://writefreely.org/docs/latest/writer/federation

Wow, you do not need a third party plug-in like Disqus anymore to accept comments from readers, right?

I finally figured out how to install #diaspora. The answer: avoid bitnami's installer at all.

There is a lot of reports about the installer on the diaspora's official forum, and it is discouraged officially.

See: https://discourse.diasporafoundation.org/t/noob-using-bitnami-ports-and-security-help/3202/2

Followed this guide (https://www.howtoforge.com/how-to-install-diaspora-decentralized-social-media-on-debian-10/) and I got a diaspora instance running.

Trust me, when it comes to diaspora, manual installation is a faster way than other automation tools.

I started feeling that on fediverse it is as important as on centralized cloud services to be careful where you are going to host your data.

Unless #E2EE is implemented you would still have to trust someone, and there could be malicious actors too.

If you are going to use public instances, please be careful. You should conduct due diligence by yourself; who manages the server, how they are financed etc...

On the official installation guide I would like to see how to set up a webserver with Let's Encrypt support, for example.

> You most likely have already a webserver running on port 80 (http) and 443 (https).

... how did you think it was most likely to have a webserver with HTTPS support already? I guess some would try on a VPS with fresh install, without a webserver.

On the official forum of diaspora there is a lot of comments from the team that you should not avoid Bitnami installer in the first place. This, to be honest, does not look to be a friendly advice, and it sounds like "I told you so", which is actually right.

I set up my own #diaspora pod on the VPS I rental with the application Bitnami provides.

https://bitnami.com/stack/diaspora/installer

Still I am struggling to make my account discoverable from other instances. I can find myself on my own instance, but I cannot find that account from another instance where I have had an account. I think I set it up not right...

Any idea how to troubleshoot??