「接触確認アプリ「COCOA」、Android版は昨年9月から事実上機能せず 政府謝罪」

"The Android version of COCOA, an app for confirming contact with patients with new coronas, has been effectively disabled since last September, and the government has apologized"

Andoroidスマホを持っている人は激怒していいし、政府は床に頭を擦りつけて謝るべきだ ―― それでいいし、そうでなくてはならない。

People with Android phones should be outraged, and the government should apologize for scraping its head on the floor. That's fine, and that should be.


It is outrageous that the system has not been functioning since the end of September 2020.


I also think that people who have Android phones can file a lawsuit under the State Compensation Act against the government on the grounds that they have been put at risk


(I think this is equivalent to "gross negligence" under Article 1, Section 2, but I know it is difficult to determine the damages.)



That's why, as an engineer, I'm the only one who's willing to say it.

―― Andoroidのスマホって、そういうこと、結構、あるよね

"Android phones do that a lot, don't they?"




I have always thought that it would be a good idea to distribute dummy software that simulates an infected terminal.


I think that the distribution of the simulated software can be limited to only IT experts (i.e. me) who can handle at least public key cryptosystems.


I think it would be preferable for COCOA to display one or two messages a day that say, "Your phone has confirmed a reaction to the test terminal, but it is not contact with an infected person.


「私を助けてくれるのは、過去の私だ」 ―― を実感しています。

I'm realizing that 'The only person who can help me is the past me'.


For a few years now, I've been trying to leave every bit of lousy code, every dirty script, every unsightly SQL statement on my homepage.


Of course, the description is only about "technology", so you know what I do, but you don't know what kind of work I do.

というか、意図的にそういう風に記載しています ―― 必要なら、各種の偽装情報も放り込んでいます。

Or rather, it's intentionally written that way -- with all sorts of disguised information thrown in if necessary.


Because I have a duty of confidentiality regarding my work.



All I have in my notes are the results of using the notes (public information) left by my predecessors and running them by myself.


This is basically a "memorandum transfer to future me", but at the same time, it is intended as a "small contribution to the contributions of my predecessors".

で、こんな「個人的な落書きのようなメモ」が、他の人に役に立っているのか ―― とも思えるのですが、これが結構、役に立っているみたいなんですよ。

So, I'm not sure if these "personal scribbled notes" are useful to other people, but they seem to be quite useful.


It's pretty amazing, but the page that generates the most PV on my wp.kobore.net site is


"A lot of trouble to get a single "tree" into MSYS2 (PGP key unknown)"



「"dial tcp: lookup db on no such host exit" に苦しめられる日々の終焉」

"Day by day of suffering from "dial tcp: lookup db on no such host exit"



Can you believe it?


I even wondered who was using MSYS2.



However, when I looked at the access log, it seems that there are accesses from all over the world.


People are using search engines to find this Far Eastern engineer's page.


And even if they can't read Japanese, they can probably guess what it is from the script that is written.


Whenever I have a technical problem, I try everything I can find, whether the content is in Chinese, Russian, or Arabic.


A cornered engineer will do anything.


「技術メモを世界に公開しておく」というだけのことが、世界中のエンジニアにに貢献している、ということは ―― 決して大袈裟な話ではないようです。

It's not an exaggeration to say that "making technical memos available to the world" is contributing to engineers around the world.


And this is just my personal opinion,


'Lousy code, dirty scripts, and unsightly SQL statements are useful'



Because that would be so much more helpful to me.


To be frank, a clean and concise code is of no use to me.


―― 強いリーダーシップを持っている政治家が求められている

"Politicians with strong leadership skills are in demand"


I don't know if this is true or false, but at least I'm not 'asking for it'.


Anyone who has studied modern history will immediately understand what kind of disasters such a man has brought about.


Rudolf Hitler, Joseph Stalin, Mao Zedong, Pol Pot, Nicolae Ceauescu


Some people may say, "Dictatorship is not the same as strong leadership.


I also believe that it is desirable for leaders to be strong in neighborhood associations, student councils, and private businesses.


However, a "politician" is an entity that can exercise power by being entrusted by the people or by being supported by a violent apparatus.


The combination of "strong leadership" and "politicians" is not the same as normal leadership.



The "economic measures" for the new corona disaster are difficult, but the "infection control measures" have become much clearer.


I think this is being proven by the results of the second emergency declaration.

人と「出会うな」「しゃべるな」「飯食うな」 ―― これまで、ずっと言われてきたことが、やはり正しかった。

Don't talk to people, don't meet people, don't eat with people - all the things they've been told were right.


They were right, so we'll do the right thing.


Go to a restaurant and save Japan's restaurant industry. However, go alone. And eat in silence.


If you eat while looking at your phone, the meal is enjoyable in its own way.


My diary is the best place in the world to learn about "eating alone". Please refer to it.

さて ―― この程度のことに、「強いリーダーシップ」がいるのか? 私たちは、そこまで愚かか?

Now -- do we really need "strong leadership" for something like this? Are we really so stupid?


(There are politicians and bureaucrats who are that stupid. I'm forgetful, so I'll make a list and publish it later. I'll keep updating and publishing it as new fools appear)



What is required of the government is ultra-precise control of the two handles, "economic measures" and "infection control.


This kind of ultra-precise control is based on the principle of "on-the-spot" and "prediction".

制御とは、 ―― 古典制御であれ、現代制御であれ、PIDであれ、ファジィであれ、ニューロであれ、

Control is -- whether classical control, modern control, PID, fuzzy, neuro, etc.


- "On-the-spot" to information as it is obtained from the environment.



- 'Predictions' derived from current controls




Based on the premise that the new coronas will never be completely eradicated, we will have to live in a world of coexistence with the virus.


The means to do this are "on-the-spot" and "predicting.


Of course, it has to be highly mathematical and statistical, logical, and highly targeted.

はっきりと言えることは「これをやれば完璧」 ―― そんな魔法のパラメータは存在しない、ということです。

What is clear is that there is no magic parameter of 'Do this and make it perfec'


The government will continue to declare a state of emergency and the people will immediately respond to it.

結果が出たら、緊急事態宣言を解除する ―― これを、これから何度でも繰り返すのです。

Once the results are in, the state of emergency will be lifted -- and this will be repeated as many times as necessary.


That is the work of government, and the behavioral change that is required of us.



There is no need for "strong leadership.


What is needed is "a leader who can mobilize the full power of government to perform advanced calculations and forecasts and deliver the results.



(1)"gintoyo_postgres_1 docker-entrypoint.sh Up>5432/tcp" というDockerコンンポーネントが動作中であるとする。

(2)docker exec -it gintoyo_postgres_1 psql -U postgres -d ca_sim という方法で、"ca_sim"というDBに直接アクセスできるものとする。

(3)docker exec -it gintoyo_postgres_1 bash → psql -d ca_sim -p 8910 -U postgres という方法でも"ca_sim"というDBにアクセスできるものとする


ca_sim というDBと全く同じものを、ca_sim9という名前で作る

3. 手順

(Step.1) Dockerで直接DBには入らないで、シェルでログインする
C:\Users\ebata\20210203\gintoyo>docker exec -it gintoyo_postgres_1 bash

(Step.2) シェルからDBを作成する(ここでは"ca_sim9")
root@8240d01caea2:/# createdb -U postgres ca_sim9
(Step.3) シェルからDBをコピーする(ここでは"ca_sim"→"ca_sim9") 。"-U postgres"を入れないと、"rootじゃない"等の文句を言われる
root@8240d01caea2:/# pg_dump -U postgres -Ft ca_sim | pg_restore -U postgres -d ca_sim9
■ シェルからpsqlアクセスしようとすると失敗する
root@8240d01caea2:/# psql -d ca_sim -p 8910 -U postgres
psql: error: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.8910"?
# psql -d ca_sim -U postgres
# psql -d ca_sim -p 5432 -U postgres
(Step.4) シェルから出る
root@8240d01caea2:/# exit
(Step.5) Docker exec でアクセスする
C:\Users\ebata\20210203\gintoyo>docker exec -it gintoyo_postgres_1 psql -U postgres
psql (13.1 (Debian 13.1-1.pgdg100+1))
Type "help" for help.
(Step.6) "ca_sim9"が存在するか調べる
postgres=# \l
                                  List of databases
   Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges
 ca_sim    | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 ca_sim9   | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres
 template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres
(5 rows)
(Step.7) "ca_sim9"の中身を調べる
postgres=# \c ca_sim9
You are now connected to database "ca_sim9" as user "postgres".
ca_sim9=# \dt
                 List of relations
 Schema |          Name          | Type  |  Owner
 public | aggregate_result       | table | postgres
 public | area_definition        | table | postgres
 public | ways                   | table | postgres
 public | ways_vertices_pgr      | table | postgres
(21 rows)
ca_sim9=# \dv
               List of relations
 Schema |        Name        | Type |  Owner
 public | bus_position_view  | view | postgres
 public | user_position_view | view | postgres
(5 rows)
=======  ここまで =========