「set」を含む日記 RSS

はてなキーワード: setとは

2025-07-25

Part2 - Chapter5 1つずつ壊してみよう_3

Part2 - Chapter5 1つずつ壊してみよう_3

ストレージノードを停止する

データーが保存されているリージョン情報を取得して、各リージョンを一意に特定するregion_idを把握する

リーダーノードフォロワーノード構成を調べる。region_idを持つリーダーノード特定する

リーダーノード情報を調べる(IPポート番号)

mysql> SELECT region_id, store_id, address FROM tikv_region_status NATURAL JOIN tikv_region_peers NATURAL JOIN tikv_store_status WHERE is_leader = 1 AND table_name = 'Books';

+-----------+----------+-----------------+

region_id store_id address

+-----------+----------+-----------------+

302 3 127.0.0.1:20161

+-----------+----------+-----------------+

1 row in set (0.01 sec)

https://www.imdb.com/list/ls4100008754/

https://www.imdb.com/list/ls4100007424/

https://www.imdb.com/list/ls4100003263/

https://www.imdb.com/list/ls4100075426/

https://www.imdb.com/list/ls4100009000/

MySQLクライアントはTiDBサーバー接続しているので、TiKVサーバーの停止の影響は受けない。

そのため、クエリを実行しても問題なく動作する。ロスコネとかの心配なし。

内部的にはリトライが行われるのでレイテンシは増加する

まとめ

TiKVサーバーではデータリージョンで保存される

一台のみ停止の場合は残りのフォロワーリーダーを交代するので、影響を受けない

二台のリーダーを停止させると、自力での復旧ができなくなる。

運用場合は、一台目が停止した時点でスケールアウト操作実施する

2025-07-04

WSL2 USBカメラ+他のUSB機器 2022年09月06日版

WSL2 USBカメラ+他のUSB機器 2022年09月06日版

OSWindows11 21H2

OSビルド:22000.918

WSL2 5.10.102.1 + Ubuntu20.04

WSL2 Linux Kernel 5.10.60.1 からKernelモジュールUSBIP対応標準的に組み込まれたらしいが、Microsoft公式提供しているKernelや手順ををそのまま使用すると動作しない


2022年09月06日時点の最新カーネルは 5.15.62.1 だが、wsl --update で展開されるバージョンが 5.10.102.1 だったため 5.10.102.1 を使用する

以下すべての手順の Windows Terminal を使用する箇所は 管理者権限 で実行

以下、[WT] は Windows Terminal、[Ubuntu] は Ubuntu側のbashを表す

WSLのカーネルアップデートusbipd-winインストール

[WT] Windows Terminalで実行

> wsl --update

> wsl --status

カーネル バージョン: 5.10.102.1

> winget install --interactive --exact dorssel.usbipd-win

見つかりました usbipd-win [dorssel.usbipd-win] バージョン 2.3.0

このアプリケーションは所有者からライセンス供与されます

Microsoftサードパーティパッケージに対して責任を負わずライセンス付与しません。

Downloading https://github.com/dorssel/usbipd-win/releases/download/v2.3.0/usbipd-win_2.3.0.msi

██████████████████████████████ 10.4 MB / 10.4 MB

インストーラハッシュが正常に検証されました

パッケージインストールを開始しています...

インストール完了しました

[WT] Ubuntu 20.04 のインストール

> wsl --install --distribution Ubuntu-20.04

[WT] WSLのディストリビューションを起動(WSL2起動用アイコンマウスクリックして起動してもよい)

> wsl --list

LinuxWindows サブシステム ディストリビューション:

Ubuntu-20.04 (既定)

> wsl -d Ubuntu-20.04

[Ubuntu] 追加パッケージインストール

sudo apt update

sudo apt install -y linux-tools-5.4.0-77-generic hwdata

sudo update-alternatives --install /usr/local/bin/usbip usbip /usr/lib/linux-tools/5.4.0-77-generic/usbip 20

[WT] WSLの再起動

> wsl --shutdown

> wsl -d Ubuntu-20.04

PCUSBカメラ接続する

[WT] USBカメラusbipd に認識されることを確認する (この記事では 2-7)

> usbipd wsl list

BUSID VID:PID DEVICE STATE

2-2 056e:00d9 USB 入力デバイス Not attached

2-3 1c4f:0027 USB 入力デバイス Not attached

2-7 1bcf:2284 Full HD webcam, USB microphone Not attached

2-11 0495:3011 ESS USB DAC, USB 入力デバイス Not attached

2-14 8087:0029 インテル(R) ワイヤレス Bluetooth(R) Not attached

[WT] USBカメラUbuntu側にアタッチする(アタッチ成功した場合は何も表示されない)

> usbipd wsl attach --busid 2-7

>

[WT] USBカメラが正常にアタッチされていることを確認する(Attached と表示されていれば成功

> usbipd wsl list

BUSID VID:PID DEVICE STATE

2-2 056e:00d9 USB 入力デバイス Not attached

2-3 1c4f:0027 USB 入力デバイス Not attached

2-7 1bcf:2284 Full HD webcam, USB microphone Attached - Ubuntu-20.04

2-11 0495:3011 ESS USB DAC, USB 入力デバイス Not attached

2-14 8087:0029 インテル(R) ワイヤレス Bluetooth(R) Not attached

[Ubuntu] Ubuntubashログオンした既定のユーザを video グループ所属させる。なお、WSLを起動した時点で既に追加されているメッセージが表示される。

$ sudo adduser $USER video

[Ubuntu] WSL2上の Ubuntu20.04 の中からUSBカメラ認識されていることを確認する。 lsusb コマンドを経由すると正常にUSBカメラ認識されているが、/dev/video* にはUSBカメラが列挙されない

$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 003: ID 1bcf:2284 Sunplus Innovation Technology Inc. Full HD webcam

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls -l /dev/video*

ls: cannot access '/dev/video*': No such file or directory

[Ubuntu] USB CameraがWSL内で認識されるようにLinuxカーネルカスタムビルドする。下記リポジトリの手順通りに実施すると、WSL Linuxカーネルカスタムビルドされたものに入れ替わる。注意点は、<windows username> の部分だけは各自環境Windowsユーザー名に手で書き換える必要が有ること。なお、.wslconfig は 絶対windows 側で編集してはならない。絶対に。

[WT] WSLをシャットダウンし、その後起動する

> wsl --shutdown

> wsl -d Ubuntu-20.04

[WT] USBカメラusbipd に認識されることを確認する (この記事では 2-7)

> usbipd wsl list

BUSID VID:PID DEVICE STATE

2-2 056e:00d9 USB 入力デバイス Not attached

2-3 1c4f:0027 USB 入力デバイス Not attached

2-7 1bcf:2284 Full HD webcam, USB microphone Not attached

2-11 0495:3011 ESS USB DAC, USB 入力デバイス Not attached

2-14 8087:0029 インテル(R) ワイヤレス Bluetooth(R) Not attached

[WT] USBカメラUbuntu側にアタッチする(アタッチ成功した場合は何も表示されない)

> usbipd wsl attach --busid 2-7

>

https://www.imdb.com/de/list/ls599665017/

https://www.imdb.com/de/list/ls599665017/copy/

[WT] USBカメラが正常にアタッチされていることを確認する(Attached と表示されていれば成功

> usbipd wsl list

BUSID VID:PID DEVICE STATE

2-2 056e:00d9 USB 入力デバイス Not attached

2-3 1c4f:0027 USB 入力デバイス Not attached

2-7 1bcf:2284 Full HD webcam, USB microphone Attached - Ubuntu-20.04

2-11 0495:3011 ESS USB DAC, USB 入力デバイス Not attached

2-14 8087:0029 インテル(R) ワイヤレス Bluetooth(R) Not attached

[Ubuntu] WSL2上の Ubuntu20.04 の中からUSBカメラ認識されていることを確認する

$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 003: ID 1bcf:2284 Sunplus Innovation Technology Inc. Full HD webcam

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ ls -l /dev/video*

crw------- 1 root root 81, 0 Sep 6 17:29 /dev/video0

crw------- 1 root root 81, 1 Sep 6 17:29 /dev/video1

[Ubuntu] USBカメラがWSL2の中から認識されることを確認するテストコード作成する

$ pip install opencv-contrib-python

$ cat << 'EOT' > ${HOME}/usbcam_test.py

import cv2

W=640

H=480

cap = cv2.VideoCapture(0)

cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter_fourcc('M','J','P','G'))

#cap.set(cv2.CAP_PROP_FOURCC, cv2.VideoWriter_fourcc('Y','U','Y','V'))

cap.set(cv2.CAP_PROP_FRAME_WIDTH, W)

cap.set(cv2.CAP_PROP_FRAME_HEIGHT, H)

cap.set(cv2.CAP_PROP_FPS, 30)

https://www.imdb.com/de/list/ls599660855/

https://www.imdb.com/de/list/ls599660855/copy/

while True:

ret, frame

ONNX -> TFLite, TensorFlow, Keras, TFJS, CoreML 変換

ONNX -> TFLite, TensorFlow, Keras, TFJS, CoreML 変換

自作ツール onnx2tf

実装している機能が多すぎるので、この記事表現していない変換オプションはREADMEを参照。TransformerやSTTやTTSやその他もろもろの一発変換に対応したつもり。onnx-tensorflow より推論効率が高いモデルを生成できる。また、onnx-tensorflowよりも対応しているオペレーションの種類が多い。

コントリビューター

コード量(code = 行)

cloc .

419 text files.

414 unique files.

174 files ignored.

----------------------------------------

Language files blank comment code

----------------------------------------

Python 300 4820 6637 37182

JSON 27 109 0 3107

Markdown 5 343 0 2061

YAML 7 42 79 586

Dockerfile 1 6 3 38

----------------------------------------

SUM: 340 5320 6719 42974

----------------------------------------

2. 使用方法

onnx==1.13.1

onnxruntime==1.13.1

onnx-simplifier==0.4.17

onnx_graphsurgeon

simple_onnx_processing_tools

tensorflow==2.13.0rc0

2-1. インストールサンプルモデルダウンロード

docker

docker run --rm -it \

  • v `pwd`:/workdir \
  • w /workdir \

ghcr.io/pinto0309/onnx2tf:latest

pip

pip install onnx2tf -U

モデル

wget https://github.com/PINTO0309/onnx2tf/releases/download/0.0.2/resnet18-v1-7.onnx

2-2. 基本の「き」

TFLite を出力。

onnx2tf -i resnet18-v1-7.onnx

2-3. 基本の「ほ」

TFLite変換 + 完全体の saved_model を出力。

onnx2tf -i resnet18-v1-7.onnx -osd

2-4. 基本の「ん」

TFLite変換 + 全OPの精度チェック。

onnx2tf -i resnet18-v1-7.onnx -cotof

2-5. Keras

.h5 はイロイロと問題があるので、現状最新のフォーマット keras_v3 フォーマットで出力。

onnx2tf -i resnet18-v1-7.onnx -okv3

.h5 を生成するとき

https://www.imdb.com/es/list/ls599679681/

https://www.imdb.com/es/list/ls599679681/copy/

onnx2tf -i resnet18-v1-7.onnx -oh5

2-6. TFLite の入出力名を魔改造

# Custom flatc binary for Ubuntu 20.04+

# https://github.com/PINTO0309/onnx2tf/issues/196

wget https://github.com/PINTO0309/onnx2tf/releases/download/1.7.3/flatc.tar.gz \

&& tar -zxvf flatc.tar.gz \

&& sudo chmod +x flatc \

&& sudo mv flatc /usr/bin/

# Custom flatc binary for Windows

# Set the environment variable paths appropriately on your own.

# https://github.com/PINTO0309/onnx2tf/issues/196

https://github.com/PINTO0309/onnx2tf/releases/download/1.7.3/flatc.exe

onnx2tf -i resnet18-v1-7.onnx -coion

https://www.imdb.com/es/list/ls599679368/

https://www.imdb.com/es/list/ls599679368/copy/

2025-07-03

dorawii

@echo off
setlocal

set TEMPFILE=%TEMP%\gpgmessage.asc

(
echo -----BEGIN PGP SIGNED MESSAGE-----
echo Hash: SHA512
echo.
echo https://anond.hatelabo.jp/20250703153633#
echo -----BEGIN PGP SIGNATURE-----
echo.
echo iHUEARYKAB0GT6pgAKCRBw3s9u4+
echo SNC1AQCAXXWIQTEe8eLwpVRSViDKR5wMdsubD0OIay9wQpTMeI3NvH7tjgEA9lgwrA8OSykP
echo pvYgtiTPIgJAbdGrrmPPYKMdsubss4+SAUCa4YrDbL/CSdnwQEJ/bOIOPgE=
echo =AWTp
echo -----END PGP SIGNATURE-----
) > "%TEMPFILE%"

gpg --verify "%TEMPFILE%"

endlocal
gpg: CRCエラー。04838A - 0164E9
gpg: packet(2) too short
gpg: 署名が見つかりません
gpg: 署名検証できませんでした。署名ファイル
(.sigや.asc)がコマンド行の最初でなければ
ならないことを念頭においてください。

はい偽物

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

https://anond.hatelabo.jp/20250703181948# 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaGZLQgAKCRBwMdsubs4+
SHquAQDGBsh153Z4upz8exyB3E0SnX5OOG+Wm1bCTdymuiGYbwEAyO7LOCYC42K7
1dlBoZ4ZsNyZj4SO5Erg4WnqVK+drAE=
=eCvB
-----END PGP SIGNATURE-----

2025-06-28

dorawii

@echo off
setlocal

set TEMPFILE=%TEMP%\gpgmessage.asc

(
echo -----BEGIN PGP SIGNED MESSAGE-----
echo Hash: SHA512
echo.
echo https://anond.hatelabo.jp/20250628143524#
echo -----BEGIN PGP SIGNATURE-----
echo.
echo iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaF9+nAAKCRBwMdsubs4+
echo SBUuAQDDWgtyvSQb7Rh40m24rYf2Q9M3PITPsX8cI18hoCodhwEAlcFyrg0iwt4N
echo 4VEKGp/kCscTYhxt2omecTQzaGl/LAc=
echo =IS8V
echo -----END PGP SIGNATURE-----
) > "%TEMPFILE%"

gpg --verify "%TEMPFILE%"

endlocal
gpg: 06/28/25 14:33:16 ���� (�W����)に施された署名
gpg:                EDDSA鍵C47BC78BC29551495883291E7031DB2E6ECE3E48を使用
gpg: "dorawii <dorawii200@gmail.com>"からの*不正な*署名 [究極]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

https://anond.hatelabo.jp/20250628144429# 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaF+BaQAKCRBwMdsubs4+
SIvZAQCoSZtUix6tusFn7IPp/6BaPyNAwaAa432iHc2w/hkLKwEA5FABZckLVBds
cIDPcfB79cyOJ7pg+hH89lJMtbKOKw8=
=gqV1
-----END PGP SIGNATURE-----

2025-06-27

dorawii

↓起きてみたら署名消してて草。

https://anond.hatelabo.jp/20250627020109#

もし署名あったらこんな感じで検証したうえで偽者断罪できたのに。

@echo off
setlocal

set TEMPFILE=%TEMP%\gpgmessage.asc

(
echo -----BEGIN PGP SIGNED MESSAGE-----
echo Hash: SHA512
echo.
echo https://anond.hatelabo.jp/20250619161207
echo -----BEGIN PGP SIGNATURE-----
echo.
echo iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaFO4RgAKCRBwMdsubs4+
echo SNilAP9Cf9so4SWzD5wz0FehUCk7D2pwNXQti3/wtW6WI9KcSwEA24kjl/LZ0HQR
echo hlfpY+2Q4arL/PO+eRJLjcWEEpTUnQg=
echo =59FW
echo -----END PGP SIGNATURE-----
) > "%TEMPFILE%"

gpg --verify "%TEMPFILE%"

endlocal

んでもって、お前は余命宣告通りに死んだだけだよ。哀れだねえって言おうと思ってたのに。

https://anond.hatelabo.jp/20250627020109#

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

https://anond.hatelabo.jp/20250627124045# 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaF4TRwAKCRBwMdsubs4+
SOCDAQDBL0SoFeFj4mboawI0Sw+skOIXsLNG//45cycuXkwjLAEA5guPxypVdmsf
r96q5hRrf/HwwPllXRj5+Jfw09boKAg=
=eNjW
-----END PGP SIGNATURE-----

2025-06-16

コマンド入力アドベンチャーゲーム

LLMの活用で新しいものできないか

設定とラスボスだけ決めておいてたどり着くようなの

いまならデゼニランドもPUTやSETで動くようにできそう

2025-06-13

我が名はサイボーグdorawii

パーマリンク署名対象にするより堅牢自動化を作れた。

一度投稿したうえで別タブを開いてプログラム的(fetch)に送信してその別タブが閉じられる仕組み。

改めてスクリプト配布しちゃる

最初投稿してエントリページに移動した親タブ側のjsコード
// ==UserScript==
      // @name         PGP署名検出と別タブ自動編集
      // @namespace    http://tampermonkey.net/
      // @version      1.0
      // @description  PGP署名がない投稿自動編集ページへ誘導
      // @match        https://anond.hatelabo.jp/*
      // @grant        GM_setValue
      // @grant        GM_getValue
      // @grant        GM.openInTab
      // ==/UserScript==

      (function () {
        'use strict';

        const body = document.getElementById('entry-page');
        if (!body) return;

        const titleText = document.title;
        if (!titleText.includes('dorawii')) return;

        const pgpRegex = /BEGIN.*PGP(?: SIGNED MESSAGE| SIGNATURE)?/;
        const preElements = document.querySelectorAll('div.body pre');
        let hasPgpSignature = false;

        for (const pre of preElements) {
          if (pgpRegex.test(pre.textContent)) {
            hasPgpSignature = true;
            break;
          }
        }

        if (hasPgpSignature) return;

        const editLink = document.querySelector('a.edit');
        const childTab = GM.openInTab(editLink.href, { active: false, insert: true, setParent: true });

      })();
親タブから開かれる編集ページの子タブのjsコード
 // ==UserScript==
      // @name         編集ページ処理と自動送信・閉じ
      // @namespace    http://tampermonkey.net/
      // @version      1.0
      // @description  編集ページで署名処理と送信、タブ自動閉じ
      // @match        https://anond.hatelabo.jp/dorawii_31/edit?id=*
      // @grant        GM_getValue
      // @grant        GM_xmlhttpRequest
      // @grant        GM_setClipboard
      // @grant        GM_notification
      // @connect      localhost
      // ==/UserScript==

      (async function () {
        'use strict';

        const shouldRun = await GM_getValue('open-tab-for-edit', '0');

        const textareaId = 'text-body';
        const textarea = document.getElementById(textareaId);

        if (!textarea) return;

        const content = textarea.value;

        const pgpSignatureRegex = /-----BEGIN PGP SIGNED MESSAGE-----[\s\S]+?-----BEGIN PGP SIGNATURE-----[\s\S]+?-----END PGP SIGNATURE-----/;
        if (pgpSignatureRegex.test(content)) {
          console.log('[PGPスクリプト] 署名が検出されたためそのまま送信します');
          return;
        }

        const httpRequest = (url, data) => {
          return new Promise((resolve, reject) => {
            GM_xmlhttpRequest({
              method: 'POST',
              url: url,
              headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
              data: `value=${encodeURIComponent(data)}`,
              onload: function (response) {
                resolve(response.responseText);
              },
              onerror: function (error) {
                reject(error);
              }
            });
          });
        };


        // textarea の値を取得
        // 1. 現在のページのURLからURLオブジェクト作成
        const currentUrl = new URL(window.location.href);

        // 2. ベースとなる部分 (例: "https://anond.hatelabo.jp") を取得
        const origin = currentUrl.origin;

        // 3. 'id' パラメータの値 (例: "20250610184705") を取得
        const idValue = currentUrl.searchParams.get('id');

        // 4. ベース部分とIDを結合して、目的URL文字列を生成
        //    idValueが取得できた場合のみ実行する
        let newUrl = null;
        if (idValue) {
          newUrl = `${origin}/${idValue}`;
        }

        // 5. 生成されたURL変数に代入し、コンソールに出力して確認
        console.log(newUrl);
        const valueToSend = newUrl;

        try {
          const signatureText = await httpRequest('http://localhost:12345/run-batch', valueToSend);
          console.log('バッチ応答:', signatureText);
          if (!signatureText.includes('BEGIN PGP SIGNED MESSAGE')) {
            alert('PGP署名クリップボードに見つかりませんでした。');
            return;
          }

          const newText = content.replace(/\s*$/, '') + '\n' + signatureText + '\n';
          textarea.value = newText;

          console.log('[PGPスクリプト] 署名を貼り付けました。送信を再開します。');


          const form = document.forms.edit;

          const newForm = form.cloneNode(true);
          form.replaceWith(newForm);

          newForm.addEventListener('submit', async (e) => {
            e.preventDefault(); // HTML標準のsubmitをキャンセル
            const bodyText = textarea?.value || '';

            // reCAPTCHA トークンの取得
            const recaptchaToken = await new Promise((resolve) => {
              grecaptcha.enterprise.ready(() => {
                grecaptcha.enterprise.execute('hoge', { action: 'EDIT' })
                  .then(resolve);
              });
            });

            // POSTするデータの構築
            const formData = new FormData(newForm);
            formData.set('body', bodyText);
            formData.set('recaptcha_token', recaptchaToken);
            formData.set('edit', '1');
            try {
              const response = await fetch(newForm.action, {
                method: 'POST',
                body: formData,
                credentials: 'same-origin'
              });


              if (response.ok) {
                console.log('送信成功');
                window.close();


              } else {
                console.error('送信失敗', response.status);
              }
            } catch (err) {
              console.error('送信中にエラーが発生', err);
            }

          });

          // プログラム的に送信トリガー
          newForm.dispatchEvent(new Event('submit', { bubbles: true }));

        } catch (e) {
          console.error('バッチ呼び出し失敗:', e);
        }

      })();
node.jsで動かすローカルサーバーコード
const http = require('http');
const { exec } = require('child_process');
const querystring = require('querystring');

const server = http.createServer((req, res) => {
  if (req.method === 'GET' && req.url === '/ping') {
    res.writeHead(200);
    res.end('pong');
  } else if (req.method === 'POST' && req.url === '/run-batch') {
    let body = '';

    req.on('data', chunk => {
      body += chunk.toString();
    });

    req.on('end', () => {
      const parsed = querystring.parse(body);
      const value = parsed.value || 'default';

      // 値を引数としてバッチに渡す
      exec(`C:\\Users\\hoge\\Desktop\\makesign.bat "${value}"`, { encoding: 'utf8' }, (err, stdout, stderr) => {
        if (err) {
          res.writeHead(500);
          res.end('Error executing batch: ' + stderr);
        } else {
          res.writeHead(200, { 'Content-Type': 'text/plain; charset=utf-8' });
          res.end(stdout.trim());
        }
      });
    });

  } else {
    res.writeHead(404);
    res.end('Not found');
  }
});

server.listen(12345, () => {
  console.log('Batch server running at http://localhost:12345/');
});
@echo off
setlocal enabledelayedexpansion


:: 署名するファイルset "infile=%~1"
set outfile=%TEMP%\pgp_output.asc

:: 以前の出力があれば削除
if exist "%outfile%" del "%outfile%"


:signloop
:: AutoHotkeyパスフレーズ入力(gpgがパスワード要求するダイアログが出た場合に備える)
start "" /b "C:\Users\hoge\Documents\AutoHotkey\autopass.ahk"

:: PGPクリア署名作成
echo %infile% | gpg --yes --clearsign --output "%outfile%"


:: 署名成功していればループを抜ける
if exist "%outfile%" (

    goto postprocess
) else (

    timeout /t 1 > nul
    goto signloop
)
:postprocess

powershell -nologo -command ^
  "$header = '>|'; $footer = '|<'; $body = Get-Content '%outfile%' -Raw; Write-Output ($header + \"`r`n\" + $body + $footer)"

powershell -nologo -command ^
  "$header = '>|'; $footer = '|<'; $body = Get-Content 'signed.asc' -Raw; Set-Clipboard -Value ($header + \"`r`n\" + $body + $footer)"

endlocal
exit /b
AutoHotkey(以前と同じ)
#Persistent
#SingleInstance ignore
SetTitleMatchMode, 2
WinWaitActive, pinentry
SendInput password
Sleep 100
SendInput {Enter}
ExitApp

動けばいいという考えで作っているので余分なコードも含んでいるかもしれない。

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

https://anond.hatelabo.jp/20250613185036 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaEv1FQAKCRBwMdsubs4+
SHHkAQDUOLgBcdji2T6MJ7h/vlMdFfGlWAzNdXijjE1gIuEPywEAiMNMZqhrMmtl
c7UqRuggNJ/UTa5xTIcKp622+7jJQQg=
=Lgkl
-----END PGP SIGNATURE-----

2025-06-10

はい」としか言えない質問が嫌い

嫌いな質問がある。

から父が聞いてきた質問で、

『「はい」としか言えない質問』が嫌いだ。

例えば、

夜中の22時に「ご飯食べた?」

火曜日の21時に「明日学校か?」

など。

間違いなく「はい」としか言いようがない。

そして、反応は毎回「へえ」とどうでもよさそうな感じだ。

母に「父がわかりきったことを聞いてくる」と相談しても、

子供と会話を持ちたいんじゃない?」と母は言う。

なんか子供が好きとか気になるからというより、

父として子供と接しておかねばならないという自分の保身のために思えた。

子供の頃からずっと言語化できなくてモヤモヤしていたがそういうことだろう。

三者面談かなにかで、

子供と会話はしていますか?」と聞かれて、

父が「割としていますよ」と答えたときは嘘つけと思った。

心理学テクニックで『「はい」と言わせることで好印象に思わせる』テクニックがあるような記憶があった。

調べたら、イエスセット(Yes set)というテクニックらしい。

聞き手に「はい」を連続させて契約を結びやすくするもので、悪用したものが「ハイハイ学校」らしい。

別に父は何か物を買わせようとはしてこなかったが、骨の髄まで営業マンかよと。

とにかく、『「はい」としか言えない質問』が嫌いだ。

正確に言うと『「はい」としか言えない質問を何度も繰り返す』のが嫌いだ。

大事なことの確認や忘れたことの確認で同じことを聞くのはわかる。自分もやる。

ただ、明らかに考えればわかるようなことを、

しかも「それを聞いてあなたは行動が変化するんですか?」ということを何度も聞いてくるのは、

私の行動を何かに誘導しようという思惑を感じる。

もし『「はい」としか言えない質問』をしているのなら気をつけてほしい。

2025-06-09

dorawii

ようやく(ほぼ)すべてが自動化された。

あとはローカルサーバーの起動をスタートアップに設定する(方法AIに聞いて指示に従う)だけの消化試合

ここにほとんどAI頼りのコードを公開しておく。

事前にインストールしておくもの

autohotkey

nodejs

ユーザースクリプトを実行できる拡張機能

パスとかの注意

署名要求してくるパスワードを自動入力するahkファイルドキュメントAutoHotkey配下に置いた。

バッチファイル(make.sign.bat)はデスクトップに置いた。

以下コード

autopass.ahk
#Persistent
#SingleInstance ignore
SetTitleMatchMode, 2
WinWaitActive, pinentry
SendInput お前のパスワード
Sleep 100
SendInput {Enter}
ExitApp
run-bacth-server.js
// run-batch-server.js
const http = require('http');
const { exec } = require('child_process');

const server = http.createServer((req, res) => {
  if (req.url === '/ping') {
    res.writeHead(200);
    res.end('pong');
  } else if (req.url === '/run-batch') {
    exec('C:\\Users\\you\\Desktop\\makesign.bat', (err) => {
      res.writeHead(200);
      res.end(err ? 'Error' : 'OK');
    })
    ;
  } else {
    res.writeHead(404);
    res.end('Not found');
  }
});

server.listen(12345, () => {
  console.log('Batch server running at http://localhost:12345/');
});
makesign.bat
@echo off
setlocal enabledelayedexpansion

:: ミリ秒単位UTC時刻を取得
for /f %%a in ('powershell -nologo -command "[int64]::Parse((Get-Date).ToUniversalTime().ToString('yyyyMMddHHmmssfff'))"') do set timestamp=%%a

:: 署名するファイルset infile=%TEMP%\pgp_input.txt
set outfile=%TEMP%\pgp_output.asc

:: 以前の出力があれば削除
if exist "%outfile%" del "%outfile%"

:: タイムスタンプを原文として保存
echo %timestamp% > "%infile%"

:signloop
:: AutoHotkeyパスフレーズ入力(gpgがパスワード要求するダイアログが出た場合に備える)
start "" /b "C:\Users\infini\Documents\AutoHotkey\autopass.ahk"

:: PGPクリア署名作成
gpg --yes --clearsign --output "%outfile%" "%infile%"


:: 署名成功していればループを抜ける
if exist "%outfile%" (
    echo [INFO] 署名成功
    goto postprocess
) else (
    echo [WARN] 署名失敗、再試行します…
    timeout /t 1 > nul
    goto signloop
)
:postprocess

:: PowerShellで余計な改行なしに |< をつけてクリップボードコピー
powershell -nologo -command ^
  "$header = '>|'; $footer = '|<'; $body = Get-Content '%outfile%' -Raw; Set-Clipboard -Value ($header + \"`r`n\" + $body + $footer)"

echo Done. signed.asc created and clipboard updated (no extra blank line).
endlocal
exit /b
tempermonkeyとかに登録するユーザースクリプト
// ==UserScript==
// @name         PGP署名自動付加スクリプト(GM_xmlhttpRequest版)
// @namespace    http://tampermonkey.net/
// @version      1.0
// @description  投稿前にPGP署名を付けてから送信(fetch未使用)
// @match        https://anond.hatelabo.jp/dorawii_31/edit*
// @grant        GM_xmlhttpRequest
// @grant        GM_setClipboard
// @grant        GM_notification
// / @connect      localhost
// ==/UserScript==

(function () {
  'use strict';

  const submitId = 'submit-button';
  const textareaId = 'text-body';
  const localServer = 'http://localhost:12345/run-batch';

  const pgpSignatureRegex = /-----BEGIN PGP SIGNED MESSAGE-----[\s\S]+?-----BEGIN PGP SIGNATURE-----[\s\S]+?-----END PGP SIGNATURE-----/;

  const httpRequest = (url) => {
    return new Promise((resolve, reject) => {
      GM_xmlhttpRequest({
        method: 'GET',
        url: url,
        onload: function (response) {
          resolve(response.responseText);
        },
        onerror: function (error) {
          reject(error);
        }
      });
    });
  };

  const interceptClick = () => {
    const btn = document.getElementById(submitId);
    if (!btn || btn.dataset.pgpIntercepted === 'true') return;
    btn.dataset.pgpIntercepted = 'true';

    btn.addEventListener('click', async function (e) {
      const textarea = document.getElementById(textareaId);
      if (!textarea) return;

      const content = textarea.value;

      if (pgpSignatureRegex.test(content)) {
        console.log('[PGPスクリプト] 署名が検出されたためそのまま送信します');
        return;
      }

      e.preventDefault();
      e.stopImmediatePropagation();
      console.log('[PGPスクリプト] 署名が見つからないため処理を停止し、署名を取得します');

      try {
        await httpRequest(localServer); // バッチ実行

        const signatureText = await navigator.clipboard.readText();
        if (!signatureText.includes('BEGIN PGP SIGNED MESSAGE')) {
          alert('PGP署名クリップボードに見つかりませんでした。');
          return;
        }

        const newText = content.replace(/\s*$/, '') + '\n' + signatureText + '\n';
        textarea.value = newText;

        console.log('[PGPスクリプト] 署名を貼り付けました。送信を再開します。');
        btn.click(); // イベント再発火

      } catch (err) {
        alert('PGP署名の取得または貼り付けに失敗しました。\n' + err);
      }
    }, true);
  };

  window.addEventListener('load', () => {
    setTimeout(interceptClick, 1000);
  });
})();

プロミスメソッドとか全然まだ理解してなくてそのなかに関数代入したその関数オブジェクトプロパティresponseを?いやまあそのあたりのコードが示すデータの流れが全然理解できないような人間でもここまでできちゃった。

AIすごいなと思うよ。そして思うのは今後重要になってくるのは文法とか自体に詳しいことじゃなくて、そのプログラムの処理内容を指示できるシステムエンジニア的な言語化能力のほうじゃないかなと思った。

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

20250609111559680 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaEbCbwAKCRBwMdsubs4+
SLueAPwOv7PBk4voAe5qlcCEvs/PJhmKc5QAb/1R43JMQFuDZgD/UTPEKsL/PhK9
jFGv2HDXK1dVjLNwvosgX9uYJh5xxwY=
=qiOE
-----END PGP SIGNATURE-----

2025-06-08

dorawii

ChatGPTにバッチファイルを作ってもらったのでこれから署名捗るぞ。これだけ手軽化できたらレスバに入っても署名つけるのも億劫にならずできそうだ。

なにせ文章を書き折ったらあとはバッチダブルクリックしてCtr+Vするだけだ。

原文には現在日時のミリ秒表示を使うことにした。

名乗る人が増えることを期待して作らせたものを公開しておく。

@echo off
setlocal

:: ミリ秒単位UTC時刻を取得
for /f %%A in ('powershell -nologo -command "[int64]::Parse((Get-Date).ToUniversalTime().ToString('yyyyMMddHHmmssfff'))"') do set timestamp=%%A

:: PGPクリア署名作成
echo %timestamp% | gpg --yes --clearsign > signed.asc

:: PowerShellで余計な改行なしに |< をつけてクリップボードコピー
powershell -nologo -command ^
  "$header = '>|'; $footer = '|<'; $body = Get-Content 'signed.asc' -Raw; Set-Clipboard -Value ($header + \"`r`n\" + $body + $footer)"

echo Done. signed.asc created and clipboard updated (no extra blank line).
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

20250608045542542 
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTEe8eLwpVRSViDKR5wMdsubs4+SAUCaEUXzgAKCRBwMdsubs4+
SCvuAQDjRjPVCO1F9DgmAKoqKYG7qB9r4e7y2Ky+/umT/OhnygEA8h2NL8zIczSp
hcOk/MaDWJJ2Y7WDA3d6gxFakW8TKAw=
=HE4/
-----END PGP SIGNATURE-----

2025-05-30

Github code pilotの最大の欠点

何もしないと個人リポジトリ―のコードが取り込まれ、設定によってはどんなライセンスコードだろうと取り込まれることだ。たとえば…

https://github.com/timdetering/Wintellect.PowerCollections/blob/master/Binaries/License.txt

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

みたいに商用利用が実質的ダメな奴だろうとな…。

ちなみにこのライセンス合意管轄

This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

アメリカニューヨーク州なので、ニューヨーク州法と連邦法が適用される。

もし、Github code pilotでBigListやNode、Bagなどのコードが出てきたら、注意したほうがいいぞ。

https://www.ai-souken.com/article/github-copilot-copyright-issues

訴えている奴がマジでいるんで、Code Pilot Businessのほうは公開されているコードは取り込まないという設定を有効にしておいたほうがいいと思われる。

2025-05-28

推薦系スコア統合問題

この構造はすべて、(集合と関数の)圏論構造を持ちうるデータ空間です。

ステップ 1:圏と関手による基本抽象化

まず、構造を圏的に捉えます

これらの直積圏 C = Cᵤ × Cᵢ 上で、fⱼ:C → ℝ を射とする関手列が定義されているとみなせます

ステップ 2:エンリッチド圏による意味付け(V-Category)

推薦問題の核心は、スコア意味的な関係定量的または論理的評価することにあります。これを抽象的に捉えるには、エンリッチド圏の理論が適しています

2.1 定義:V-エンリッチド圏 (V-category)
  • V をモノイド圏とする(例:(ℝ≥0, +, 0) または ([0,1], max, 0))
  • 任意の2対象 x, y に対して、「射」ではなく「x から y への距離」または「評価値」v(x, y) ∈ V が与えられる

推薦システムにおいて:

2.2 本問題への適用

ユーザー u ∈ U、アイテム i ∈ I に対して、評価: v(u, i) ≔ g(f₁(u, i), ..., fₙ(u, i)) ∈ ℝ

これは、ユーザーアイテムペア空間 U × I を対象とする ℝ-エンリッチド圏と見なせる。

ステップ 3:トポス理論への接続

3.1 トポスとは?

トポスとは、直感的には「集合のような性質を持つ圏」です。ただしそれは集合よりはるかに柔軟で、論理空間一般化的枠組みです。

問題では、推薦空間自体を内部論理意味を持つトポスと見なします。

3.2 推薦空間トポスとして構築

ステップ 4:推論と最大化をトポス内部で定義

ステップ 5:総合抽象構造としての構成


総括

圏 C ユーザー×アイテム意味空間
関手 F 複数スコアリング関数(f₁,…,fₙ)
汎関数 g 統合関数線形でも非線形でも)
エンリッチ圏 V-Cat スコア評価距離や信頼値として扱う枠組み
トポス Sh(C, J) 推薦を含む部分集合構造を持つ論理空間
内部論理 「どのアイテムを推薦すべきか」の命題定義
推薦関数 Rᵤ トポス内の部分対象選択関数(述語による定義

2025-04-08

トランプ日本の態度にガチギレ、しかメディア歪曲報道しすぎ

中国の事を気にしている暇はない

Donald J. Trump Posts From His Truth Social

@TrumpDailyPosts

3時間

Countries from all over the World are talking to us. Tough but fair parameters are being set. Spoke to the Japanese Prime Minister this morning. He is sending a top team to negotiate! They have treated the U.S. very poorly on Trade. They don’t take our cars, but we take MILLIONS of theirs. Likewise Agriculture, and many other “things.” It all has to change, but especially with CHINA!!!

Donald Trump Truth Social 04/07/25 09:27 AM

世界中の国々が私たちと話をしています。厳しいが公平な条件が設定されています。今朝、日本首相と話をしました。彼は交渉のためにトップチーム派遣しています!彼らは貿易に関して米国を非常にひどく扱っています。彼らは私たちの車を受け取らないのに、私たちは彼らの車を何百万台も受け取っています農業やその他多くの「もの」も同様です。すべてを変える必要がありますが、特に中国に関しては!!!

本命中国だが、日本にも相当キレている。

Sputnik 日本

@sputnik_jp

41分

トランプ大統領 USスチール買収の再審査を指示 45日以内に報告】

🇺🇸 トランプ米大統領は、USスチール買収案件についての措置の適切性を判断するため、対米外国投資委員会(CFIUS)に新たな審査を命じた。ホワイトハウスが7日声明を表した。

トランプ氏は新たな審査目的を「私が判断するのを助けるため」と語っている。これを受け、CFIUSは45日以内に報告書の提出が義務付けられる。

ℹ️ 3月末、日本製鉄は米政権から買収の承認を得た場合USスチール工場改修への投資額をこれまでの27億ドルから約70億ドルに増やす可能性があることが、セマフォーの報道で明らかにされていた。合弁取引問題現在、米法務省管轄している。

https://x.com/sputnik_jp/status/1909276317180367190

うそうじゃない

時事ドットコム時事通信ニュース

@jijicom

【速報】トランプ氏は、日本GMフォードの車が売れていないことを「恐るべき不均衡」と非難した

上記文章自動車限定しておらず、見出しとして非常に不適切で、頭がおかしい。

スプートニクの方が正確なのはなんで?

Sputnik 日本

@sputnik_jp

日本貿易米国をひどい扱い=トランプ大統領

🗨「彼ら(日本)は貿易では米国にとても悪い態度だ。むこうは米国車を買わないのに、こちらはむこうの車を何百万台も買っている。農業もほかの多くの物でも事情は全く同じ。すべてを変えねばならないが、特に中国とは!」

トランプ米大統領は石破首相との電話会談後、自身SNSにこう投稿した。さら貿易関税を話し合うため、日本代表団が訪米することを明らかにしている。

🗨「世界中の国々が米国交渉を行っている。我々が提示するのは厳しいが、公平な条件だ」

ℹ️ これに先立ち石破首相は、早期に訪米し、日本製品に対する関税問題解決したいと語った。石破氏は米国関税導入で生じた一連の状況を『国難』と呼んでいる。

https://x.com/sputnik_jp/status/1909256101964771413

比較すればわかるが、少なくともポストを正確に訳して記事にしている。日本見出しからして不正確で読む気にならない。

2025-04-05

Both the Smoot-Hawley Tariff Act of 1930 and the tariffs imposed during the Trump administration (starting in 2018 and again in his second term) were protectionist trade measures intended to shield domestic industries from foreign competition. However, they differ in several key aspects:  

Smoot-Hawley Tariff Act (1930):

Timing: Enacted during the onset of the Great Depression.  

Scope: Raised tariffs on over 20,000 imported goods, primarily targeting agricultural and manufactured goods.  

Average Increase: Increased existing import duties by an average of about 20%. Some sources state the average increase on dutiable goods was higher.  

Motivation: Primarily aimed at protecting American farmers and industries struggling with overproduction and decreased demand.  

Congressional Role: Tariff rates were set by the U.S. Congress.

Economic Context: The U.S. was running a trade surplus at the time, although imports of manufactured goods were increasing.

Impact: Widely blamed for exacerbating the Great Depression by triggering retaliatory tariffs from other countries, leading to a sharp decline in global trade and U.S. exports.  

Trump Tariffs (2018-2020 & 2025):

Timing: Implemented during a period of relative economic stability in the first term, and again in a context where Trump declared a "national emergency" regarding foreign trade in his second term.

Scope: Targeted specific countries (e.g., China, EU, Canada, Mexico) and specific industries (e.g., steel, aluminum) initially. The second term actions propose broader tariffs on all countries and potentially higher reciprocal tariffs on those with large trade deficits with the U.S.  

Average Increase: The average increase varied depending on the targeted goods and countries. Some reports indicate that Trump's proposed tariffs in his second term could result in an average duty surpassing the levels of Smoot-Hawley.  

Motivation: Stated goals included reducing trade deficits, protecting national security, encouraging domestic manufacturing, and addressing what Trump considered unfair trade practices and intellectual property theft. His second term rhetoric emphasizes "reciprocity" and addressing non-tariff barriers.  

Presidential Authority: Implemented through presidential executive orders, leveraging national security clauses and other trade laws, granting the President more direct control.  

Economic Context: The U.S. had significant trade deficits. Trade as a percentage of GDP was also much larger than in 1930.  

Impact: Led to retaliatory tariffs from affected countries, impacting U.S. exports and increasing costs for some American businesses and consumers. The broader potential impact of the second term tariffs is still unfolding, but experts predict higher prices for consumers and negative effects on the U.S. and global economies, with the possibility of a significant reduction in U.S. GDP.  

Similarities:

Protectionist Intent: Both aimed to protect domestic industries from foreign competition through the imposition of tariffs.  

Unilateral Actions: Both involved significant unilateral actions by the U.S., potentially disrupting established trade relationships.

Risk of Retaliation: Both actions triggered or are expected to trigger retaliatory measures from trading partners.

Key Differences:

Economic Climate: Smoot-Hawley was enacted during a severe economic downturn, while Trump's tariffs were initiated in a more stable (initially) economy.

Target and Scope: Smoot-Hawley was a broadside across many imports, while Trump's tariffs were more targeted initially, with the potential for broader application in his second term with a focus on "reciprocity."

Tariff Levels: While both increased tariffs, the average level and the specific rates on certain goods differed. Some analyses suggest Trump's second-term proposals could exceed the average levels of Smoot-Hawley.

Authority: Smoot-Hawley was a result of Congressional action, while Trump's tariffs were largely driven by presidential authority.  

Global Trade Landscape: The global economy and the interconnectedness of trade were vastly different in 1930 compared to the periods of Trump's tariffs.

In conclusion, while both the Smoot-Hawley Tariff Act and the Trump tariffs share a protectionist motivation, they occurred in different economic contexts, had varying scopes and average levels, and were implemented through different means. The potential for negative economic consequences, including trade wars and harm to the global economy, is a significant concern associated with both historical and contemporary tariff actions.  

2025-03-26

get wildがあるならset wildは?

setWild(&tough)

2025-03-02

推薦システム簡素モデル

対象: ユーザー集合U, アイテム集合I, 実数集合ℝ

 

主要関手:

F: U → Set(I) (履歴)

R: U → (I → ℝ) (関連)

G: U → (I → ℝ) (スコア)

 

定義:

∀u∈U, F(u) ⊆ I

R(u): I → ℝ, dom(R(u)) = F(u)

G(u) = H(G_1(u), ..., G_n(u))

ここでH: ℝ^n → (I → ℝ)は結合関数

2025-02-23

anond:20250223200232

DEFINE SCENE: "anatomical_study_model"

SET PARAMETERS:

OBJECT_1: "female_unit", ATTRIBUTES: {height: 170cm, attire: "none", exposure_level: 100%, pose: "upright_with_tilt_15deg"}

INTERACTION: "static_display", TARGET: {zone: "full_body", emphasis: "skin_surface_detail"}

ENVIRONMENT: "clinical_void", LIGHTING: "neutral_750lux", BACKGROUND: "solid_white"

EXECUTE RENDER:

DETAIL_LEVEL: "ultra_high"

FOCUS: "texture_and_form"

AVOID: "genital_explicitness"

OUTPUT: "static_image"

2025-02-21

肥田式強健術

肥田式強健術は、肥田春充が開発した身体と心のトレーニング方法で、大正から昭和初期に人気がありました。

この方法は、身体の中心(特に丹田」)を強化し、健康と強さを築くことを重視します。

驚くべきことに、肥田春充は元々虚弱体質でしたが、この方法で2年で強靭な体を手に入れ、柔道剣道などで卓越した能力を発揮しました。

また、彼の方法精神的な成長にもつながり、一部の文献では「神の力」を発見したとされていますが、霊性を手に入れるかどうかは個人解釈依存します。

肥田春充とは?

肥田春充(1883-1956)は、日本健康法の創始者で、元々虚弱体質だった彼が自ら開発した方法超人的な体を手に入れました。彼は明治大学柔道部の創設者としても知られ、柔道剣道弓術などで優れた成績を残しました。

方法の特徴

この技術は、西洋ウェイトトレーニング日本の伝統的なエネルギー概念特に丹田」)を組み合わせ、身体の中心に力を集中させることで健康と強さを築きます1930年代には多くの人々に採用され、昭和天皇もその本を読んでいた記録があります

霊性について

肥田春充自身は「神の力」を発見したと述べ、深い精神的な洞察を得たように見えますが、霊性を手に入れるかどうかは明確には定義されていません。彼の方法は主に身体的・精神健康に焦点を当てており、霊性の獲得は個々の実践者による解釈経験依存する可能性があります

調査ノート

肥田春充の「肥田式強健術」について、以下の詳細な調査を行いました。この方法は、大正から昭和初期にかけて注目された健康身体訓練の方法であり、その背景や特徴、影響力を明らかにします。

肥田春充の背景

肥田春充1883年に生まれ1956年に亡くなりました。彼は元々虚弱体質で、幼少期に麻疹で重病を患い、18歳まで中学校入学できなかったほどでした(My Dad Is an OTAKU)。しかし、彼は自身方法を通じて身体を強化し、「超人」と呼ばれるほどの強靭な体を手に入れました。この過程は、彼の伝記や関連文献で詳述されています

技術名称定義

ユーザークエリでは「肥田式強健術」と記載されていますが、これは「Hida Shiki Kyoken Jutsu(肥田式強健術)」とも呼ばれます。Quest Stationのページ(Quest Station)では、「Hida Shiki Kyoken Jutsu」が「心身を鍛える究極の方法」と紹介されており、健康身体の動きに焦点を当てています

「Kyoken Jutsu」の意味については、具体的な漢字は明らかではありませんが、文脈から「強健な技術」や「健康強化の方法」と解釈されます。webhiden.jp(webhiden.jp)では、「肥田式強健術」が中心的な名称として扱われており、以下の表でその発展段階がまとめられています

段階

説明

出版物/方法

初期開発

10種類のエクササイズに焦点、下腹部の緊張と「気合(kiai)」を強調。

1911

実験 簡易強健術』 (Experimental Simple Strong Health Method)

「動的力」の導入

「足踏みによる衝撃力」を取り入れ、「動的力」と命名、「気合適用強健術」へ発展。

1930年代初頭

-

「中心」の概念

身体の「真の中心位置」を幾何学的に説明

1916

『強い身体をつくる法』 (Method to Build a Strong Body)

中心鍛錬技術

鉄棒を使った「中心鍛錬技術」を発表、6ヶ月で「腰と腹の均等、真の中心」を実現。

1923

-

主要著作

技術包括的著作出版

1936

『聖中心道 肥田式強健術 天真療法』 (Holy Center Path Hida-style Strong Health Method, Natural Therapy)

方法の特徴

My Dad Is an OTAKU記事によると、この方法は「Hara(Tanden)」つまり臍の下または後ろにある身体の重心と内なるエネルギーの座に焦点を当てます。具体的には、腹部と下背部を均等に緊張させ、身体の中心に力を集中させることで、加速的にパワーを高めます。この訓練により、肥田は2年で強靭な体を手に入れ、柔道明治大学柔道部の創設者竹内流免許を6ヶ月で取得)、剣道弓術やり投げ長刀銃剣術射撃などのスポーツで卓越した能力を発揮しました。

また、アメリカボクサーマッカーサーフォスタームハンマド・アリもこのKyoken-jutsuを学んだとされています(My Dad Is an OTAKU)。これは国際的な影響力を持つ証拠です。

歴史的影響と普及

この方法大正時代(1912-1926年から昭和初期(1930年代頃)にかけてブームを呼び、多くの人々に採用されました。1936年の『聖中心道 肥田式強健術 天真療法』は、その包括的な内容で知られ、昭和天皇も読んでいたとされています(webhiden.jp)。Quest StationDVD(Quest Station)では、現代でも「日本の伝統的な身体運動方法」として注目されており、以下の製品販売されています

Product ID

Title

Description

Length

Language

Format

Other Info

Price

URL

SPD-9412

Hida Shiki Kyoken Jutsu Introduction

Basic principles and movements

70min

Japanese with English subtitles

DVD NTSC

All Region DVD

4,500PYY

products_dvd/e_SPD-9412.html

SPD-9413

Hida Shiki Kyoken Jutsu Practical Methods

Breaking methods, correct movement, center training

106min

Japanese with English subtitles

DVD NTSC

All Region DVD

4,500PY

products_dvd/e_SPD-9413.html

SPD-9416

Hida Shiki Kyoken Jutsu Introduction and Practical Methods

2 DVD set of Introduction and Practical Methods

176min

Japanese with English subtitles

DVD NTSC

All Region DVD

8,500PY

products_dvd/e_SPD-9416.html

霊性についての考察

ユーザークエリでは、「肥田式強健術を極めると霊性を手に入れることができるか?」と問われています肥田春充自身は、「神の力」を発見したと述べ、深い精神的な洞察を得たように見えます(My Dad Is an OTAKU)。例えば、1954年ポール・レプスが訪問した際、70代の肥田が30代のように見えたと報告されています。これは、彼の方法が単なる身体訓練を超え、精神的な次元に影響を与えた可能性を示唆します。

しかし、霊性の獲得は明確に定義されておらず、個々の実践者による解釈経験依存する可能性があります。webhiden.jpやQuest Station情報からは、肥田式強健術が主に身体的・精神健康に焦点を当てていることが明らかであり、霊性の獲得は間接的な結果として考えられるかもしれません。

調査過程

調査はまず肥田春充名前ウェブ検索を行い、Quest Station、Wikidata、webhiden.jpAmazon書籍ブログ記事(My Dad Is an OTAKU)などの結果を得ました。Quest Stationのページでは、Hida Shiki Kyoken Jutsuが「心身を鍛える究極の方法」と紹介されており、webhiden.jpでは発展段階が詳細に記載されていました。

さらに、My Dad Is an OTAKU記事を閲覧し、肥田方法が「Hara(Tanden)」に焦点を当てた訓練であることを確認しました。これにより、「肥田式強健術」が肥田健康法の翻訳である結論付けました。

結論

肥田式強健術」は、肥田春充が開発した身体と心の訓練方法で、大正から昭和初期に広く普及しました。この方法は、身体の中心を強化し、強さと健康を築くことを目指し、西洋ウェイトトレーニング日本の伝統的なエネルギー概念を融合しています。その影響力は国内外に及び、現代でもDVD書籍(webhiden.jp)で学ぶことができます霊性の獲得については、肥田自身が「神の力」を発見したと述べていますが、これは個々の実践者による解釈依存する可能性があります

Key Citations

Hida Shiki Kyoken Jutsu Introduction Quest Station

肥田春充 Hida Harumichi 肥田式強健術 webhiden

A Man Born Frail Became Superman My Dad Is an OTAKU

肥田式強健術

肥田式強健術は、肥田春充が開発した身体と心のトレーニング方法で、大正から昭和初期に人気がありました。

この方法は、身体の中心(特に丹田」)を強化し、健康と強さを築くことを重視します。

驚くべきことに、肥田春充は元々虚弱体質でしたが、この方法で2年で強靭な体を手に入れ、柔道剣道などで卓越した能力を発揮しました。

また、彼の方法精神的な成長にもつながり、一部の文献では「神の力」を発見したとされていますが、霊性を手に入れるかどうかは個人解釈依存します。

肥田春充とは?

肥田春充(1883-1956)は、日本健康法の創始者で、元々虚弱体質だった彼が自ら開発した方法超人的な体を手に入れました。彼は明治大学柔道部の創設者としても知られ、柔道剣道弓術などで優れた成績を残しました。

方法の特徴

この技術は、西洋ウェイトトレーニング日本の伝統的なエネルギー概念特に丹田」)を組み合わせ、身体の中心に力を集中させることで健康と強さを築きます1930年代には多くの人々に採用され、昭和天皇もその本を読んでいた記録があります

霊性について

肥田春充自身は「神の力」を発見したと述べ、深い精神的な洞察を得たように見えますが、霊性を手に入れるかどうかは明確には定義されていません。彼の方法は主に身体的・精神健康に焦点を当てており、霊性の獲得は個々の実践者による解釈経験依存する可能性があります

調査ノート

肥田春充の「肥田式強健術」について、以下の詳細な調査を行いました。この方法は、大正から昭和初期にかけて注目された健康身体訓練の方法であり、その背景や特徴、影響力を明らかにします。

肥田春充の背景

肥田春充1883年に生まれ1956年に亡くなりました。彼は元々虚弱体質で、幼少期に麻疹で重病を患い、18歳まで中学校入学できなかったほどでした(My Dad Is an OTAKU)。しかし、彼は自身方法を通じて身体を強化し、「超人」と呼ばれるほどの強靭な体を手に入れました。この過程は、彼の伝記や関連文献で詳述されています

技術名称定義

ユーザークエリでは「肥田式強健術」と記載されていますが、これは「Hida Shiki Kyoken Jutsu(肥田式強健術)」とも呼ばれます。Quest Stationのページ(Quest Station)では、「Hida Shiki Kyoken Jutsu」が「心身を鍛える究極の方法」と紹介されており、健康身体の動きに焦点を当てています

「Kyoken Jutsu」の意味については、具体的な漢字は明らかではありませんが、文脈から「強健な技術」や「健康強化の方法」と解釈されます。webhiden.jp(webhiden.jp)では、「肥田式強健術」が中心的な名称として扱われており、以下の表でその発展段階がまとめられています

段階

説明

出版物/方法

初期開発

10種類のエクササイズに焦点、下腹部の緊張と「気合(kiai)」を強調。

1911

実験 簡易強健術』 (Experimental Simple Strong Health Method)

「動的力」の導入

「足踏みによる衝撃力」を取り入れ、「動的力」と命名、「気合適用強健術」へ発展。

1930年代初頭

-

「中心」の概念

身体の「真の中心位置」を幾何学的に説明

1916

『強い身体をつくる法』 (Method to Build a Strong Body)

中心鍛錬技術

鉄棒を使った「中心鍛錬技術」を発表、6ヶ月で「腰と腹の均等、真の中心」を実現。

1923

-

主要著作

技術包括的著作出版

1936

『聖中心道 肥田式強健術 天真療法』 (Holy Center Path Hida-style Strong Health Method, Natural Therapy)

方法の特徴

My Dad Is an OTAKU記事によると、この方法は「Hara(Tanden)」つまり臍の下または後ろにある身体の重心と内なるエネルギーの座に焦点を当てます。具体的には、腹部と下背部を均等に緊張させ、身体の中心に力を集中させることで、加速的にパワーを高めます。この訓練により、肥田は2年で強靭な体を手に入れ、柔道明治大学柔道部の創設者竹内流免許を6ヶ月で取得)、剣道弓術やり投げ長刀銃剣術射撃などのスポーツで卓越した能力を発揮しました。

また、アメリカボクサーマッカーサーフォスタームハンマド・アリもこのKyoken-jutsuを学んだとされています(My Dad Is an OTAKU)。これは国際的な影響力を持つ証拠です。

歴史的影響と普及

この方法大正時代(1912-1926年から昭和初期(1930年代頃)にかけてブームを呼び、多くの人々に採用されました。1936年の『聖中心道 肥田式強健術 天真療法』は、その包括的な内容で知られ、昭和天皇も読んでいたとされています(webhiden.jp)。Quest StationDVD(Quest Station)では、現代でも「日本の伝統的な身体運動方法」として注目されており、以下の製品販売されています

Product ID

Title

Description

Length

Language

Format

Other Info

Price

URL

SPD-9412

Hida Shiki Kyoken Jutsu Introduction

Basic principles and movements

70min

Japanese with English subtitles

DVD NTSC

All Region DVD

4,500PYY

products_dvd/e_SPD-9412.html

SPD-9413

Hida Shiki Kyoken Jutsu Practical Methods

Breaking methods, correct movement, center training

106min

Japanese with English subtitles

DVD NTSC

All Region DVD

4,500PY

products_dvd/e_SPD-9413.html

SPD-9416

Hida Shiki Kyoken Jutsu Introduction and Practical Methods

2 DVD set of Introduction and Practical Methods

176min

Japanese with English subtitles

DVD NTSC

All Region DVD

8,500PY

products_dvd/e_SPD-9416.html

霊性についての考察

ユーザークエリでは、「肥田式強健術を極めると霊性を手に入れることができるか?」と問われています肥田春充自身は、「神の力」を発見したと述べ、深い精神的な洞察を得たように見えます(My Dad Is an OTAKU)。例えば、1954年ポール・レプスが訪問した際、70代の肥田が30代のように見えたと報告されています。これは、彼の方法が単なる身体訓練を超え、精神的な次元に影響を与えた可能性を示唆します。

しかし、霊性の獲得は明確に定義されておらず、個々の実践者による解釈経験依存する可能性があります。webhiden.jpやQuest Station情報からは、肥田式強健術が主に身体的・精神健康に焦点を当てていることが明らかであり、霊性の獲得は間接的な結果として考えられるかもしれません。

調査過程

調査はまず肥田春充名前ウェブ検索を行い、Quest Station、Wikidata、webhiden.jpAmazon書籍ブログ記事(My Dad Is an OTAKU)などの結果を得ました。Quest Stationのページでは、Hida Shiki Kyoken Jutsuが「心身を鍛える究極の方法」と紹介されており、webhiden.jpでは発展段階が詳細に記載されていました。

さらに、My Dad Is an OTAKU記事を閲覧し、肥田方法が「Hara(Tanden)」に焦点を当てた訓練であることを確認しました。これにより、「肥田式強健術」が肥田健康法の翻訳である結論付けました。

結論

肥田式強健術」は、肥田春充が開発した身体と心の訓練方法で、大正から昭和初期に広く普及しました。この方法は、身体の中心を強化し、強さと健康を築くことを目指し、西洋ウェイトトレーニング日本の伝統的なエネルギー概念を融合しています。その影響力は国内外に及び、現代でもDVD書籍(webhiden.jp)で学ぶことができます霊性の獲得については、肥田自身が「神の力」を発見したと述べていますが、これは個々の実践者による解釈依存する可能性があります

Key Citations

Hida Shiki Kyoken Jutsu Introduction Quest Station

肥田春充 Hida Harumichi 肥田式強健術 webhiden

A Man Born Frail Became Superman My Dad Is an OTAKU

2025-02-14

トランプ政権、600億円分のテスラ車購入

Trump administration set to purchase $400 million worth of armored Teslas

https://www.npr.org/2025/02/13/g-s1-48571/trump-administration-order-400-million-worth-of-armored-teslas

悪の帝国、やりたい放題だな

トランプに期待して投票した労働者たちは救われない

2025-02-02

Chatgptが答えた異星人の存在可能性とのそのロジック

Please consider the histroy of humanity from biological perpsecitve and current known fact in nearby universe, which expo-planet (from the Sol system perspective) is most likely to have civlizaed society? Please add percentage next to it in the chart

ChatGPT

Reasoned about exoplanet civilization likelihoodを28 秒行う

Evaluating planetary prospects

OK, I’m looking at the likelihood of a civilized society on an exoplanet within our Solar System. I’ll consider biological history and current space knowledge, aiming to identify the most promising candidate.

Identifying potential candidates

I'm considering exoplanets like Proxima Centauri b and TRAPPIST-1e, which might suggest they are within or observed from our Solar System.

Assessing potential candidates

I’m evaluating Proxima Centauri b, Barnard's Star, LHS 1140, and TRAPPIST-1, focusing on their habitable zones and available data. The Drake equation might help estimate their civilized society likelihoods.

Identifying promising exoplanets

I’m noting key exoplanets like Proxima Centauri b and TRAPPIST-1, which have Earth-like characteristics and are in habitable zones. This narrows down the potential candidates for advanced civilizations.

Assessing habitable zones

I'm gathering info on planets like Proxima Centauri b and TRAPPIST-1, considering factors like magnetic fields, atmospheres, and proximity to G-type stars for their potential to support advanced civilizations.

Evaluating exoplanet prospects

I'm noting that Proxima Centauri b, despite being close and around a red dwarf star, might support life if it has a magnetic field and atmosphere. This makes me think about its potential.

Charting probabilities

I'm estimating civilization probabilities for exoplanets like Proxima Centauri b and TRAPPIST-1 e, using speculative percentages based on the Drake equation and the lack of evidence for intelligent life.

Charting speculative odds

I'm crafting a chart with exoplanet names and civilization likelihood percentages, grounded in the long timeline of life's evolution, despite the speculative nature of these figures.

Identifying exoplanet contenders

I’m evaluating exoplanets like Proxima Centauri b, TRAPPIST-1 e, and Kepler-186f, considering their star types and distances, to gauge their potential for supporting advanced civilizations from our solar system's viewpoint.

Weighing proximity and observation

I'm leaning towards Proxima Centauri b due to its closeness and observational potential, despite concerns about its flare star dynamics. TRAPPIST-1 e, f, or g are also worth considering.

Revisiting exoplanet options

I'm focusing on exoplanets like Proxima Centauri b, Ross 128 b, LHS 1140 b, TRAPPIST-1 e/f/g, and K2-18b, aiming to chart their likelihood of hosting a civilized society based on current knowledge.

Assessing exoplanet potentials

I'm gathering speculative probabilities for exoplanets like Proxima Centauri b and TRAPPIST-1 e/f/g, using the Drake equation and current understanding, to better estimate their chances of hosting a civilized society.

Refining speculative probabilities

I’m refining speculative probabilities for exoplanets, including Proxima Centauri b and TRAPPIST-1 e/f/g, to estimate their chances of hosting a civilized society, considering Earth's long biological history.

Refining odds

I'm considering the astronomical timeline for intelligent life on Earth, leading me to assign even lower speculative odds for exoplanets like Proxima Centauri b and TRAPPIST-1 e.

Clarifying speculative nature

I’m crafting a simplified chart with arbitrary percentages, clearly noting the speculative nature and lack of scientific data, while considering the target audience's basic understanding of the topic.

Mapping out speculative odds

I’m charting arbitrary percentages for exoplanets, clarifying their speculative nature, and ensuring the data is accessible for young audiences with minimal scientific detail.

Crafting a chart

I’m creating a markdown table with speculative percentages for the likelihood of civilized life on exoplanets, emphasizing their purely theoretical nature and considering the understanding level of an 8-year-old.

Integrating speculative analysis

I’m mapping out a markdown chart with speculative percentages for the likelihood of a civilized society on exoplanets, mindful of the complexity and simplifying for an 8-year-old's understanding.

Assessing likelihoods

I’m piecing together markdown for exoplanets, noting Proxima Centauri b's reduced civilized life chance due to the red dwarf's activity. This inclusion highlights the speculative nature of the analysis.

Piecing together speculative odds

I’m detailing a markdown chart for audience-friendly exoplanet likelihoods, considering environmental challenges and adding a disclaimer about the speculative nature and lack of evidence.

Piecing together

I’m leaning towards Proxima Centauri b for its proximity and silent star, but I’ll add a speculative chart ranking nearby exoplanets, noting their advanced civilizations' hypothetical likelihood.

Assessing civilization probabilities

I'm emphasizing the slow emergence of intelligent life on Earth, which suggests that the odds of any habitable planet developing a complex civilization might be as low as a few percent.

Below is a very speculative chart thatbased on what we know about Earth’s long, winding path from simple life to a “civilized society” and our limited observations of nearby exoplanets—gives some fun, made‑up percentage chances for a few of our best candidate exoplanets. Remember: Scientists have not yet found any proof of life (let alone advanced civilizations) on any exoplanet. These numbers are just playful estimates to help you think about the ideas!

Speculative Chances of Finding an Advanced Civilization on Nearby Exoplanets

Exoplanet Estimated Likelihood of a Civilized Society

Proxima Centauri b ~2%

TRAPPIST-1 e ~1.5%

TRAPPIST-1 f ~1%

TRAPPIST-1 g ~1%

LHS 1140 b ~0.5%

How Did We (Very Roughly) Guess These Numbers?

Earth’s Example:

On Earth, life began as simple single‑celled organisms and took billions of years to evolve into a species that built complex societies. This long journey suggests that—even if a planet is in the “habitable zone” (where liquid water could exist)—developing an advanced, civilized society might be rare.

Nearby Exoplanets:

Proxima Centauri b:

This is the closest exoplanet to us. Even though its star (Proxima Centauri) is a red dwarf that sometimes sends out strong flares (which might harm life), its closeness makes it one of our most interesting candidates. That’s why we give it a slightly higher guess (~2%).

TRAPPIST-1 System (e, f, g):

These planets are part of a group orbiting a very cool star. Their environments might be challenging (for example, they could be tidally locked, meaning one side always faces the star), so the chance of a complex, advanced civilization might be a bit lower.

LHS 1140 b:

This planet is promising in some ways but is a little farther away and around a dimmer star, so our playful estimate is even lower.

A Final Note

All of these percentages are extremely rough guesses based on what little we understand about the conditions for life and intelligence. Scientists use ideas like the Drake Equation to think about these chances—but until we have concrete evidence, these numbers remain just for fun and imagination.

Enjoy exploring these ideas—and remember, space is full of mysteries waiting to be discovered!




あなた:

Please examine the Drake Equation itself and see if this euqation is acculate or more opition in the equation you will use

ChatGPT

Reasoned about the Drake Equationを6 秒行う

re-examining the Drake Equation

evaluating the Drake Equation's value

Clarifying the Drake Equation

OK, let me see. The Drake Equation isn't a precise formula; it's more of a guiding heuristic that tackles numerous uncertainties regarding extraterrestrial civilizations.

Assessing the Drake Equation

Thinking through the Drake Equation, I’m evaluating its conceptual nature, its uncertain parameters, and its criticism to conclude on its reliability as an accurate predictive model.

Understanding the Drake Equation

I’m mapping out the Drake Equation as a conceptual guide, detailing its parameters, which are often based on estimates or opinions, to evaluate its reliability for predicting extraterrestrial civilizations.

The Drake Equation is a famous formula that was created to help scientists think about the many factors involved in estimating the number of detectable extraterrestrial civilizations in our galaxy. However, when we look at the equation closely, we see that it is more of a conceptual framework or heuristic tool than a precise, predictive formula. Let’s break down why:

The Drake Equation

The equation is usually written as:

𝑁

=

𝑅

×

𝑓

𝑝

×

𝑛

𝑒

×

𝑓

𝑙

×

𝑓

𝑖

×

𝑓

𝑐

×

𝐿

N=R

×f

p

×n

e

×f

l

×f

i

×f

c

×L

Where:

𝑅

R

: The average rate of star formation per year in our galaxy.

𝑓

𝑝

f

p

: The fraction of those stars that have planetary systems.

𝑛

𝑒

n

e

: The average number of planets that could potentially support life per star with planets.

𝑓

𝑙

f

l

: The fraction of those planets where life actually develops.

𝑓

𝑖

f

i

: The fraction of planets with life where intelligent life evolves.

𝑓

𝑐

f

c

: The fraction of civilizations that develop technology that releases detectable signals into space.

𝐿

L: The length of time such civilizations release detectable signals.

Why the Drake Equation Is More of a Guideline Than a Precise Formula

Uncertain Inputs:

Well-Known Parameters:

Some factors, like

𝑅

R

(star formation rate) and

𝑓

𝑝

f

p

(fraction of stars with planets), have become better known through modern astronomy.

Highly Speculative Factors:

The parameters related to the development of life and intelligence

𝑓

𝑙

f

l

,

𝑓

𝑖

f

i

,

𝑓

𝑐

f

c

, and

𝐿

L—are based on very limited data. For example, Earth is the only planet we know where life has developed, so we have no way to compare or derive a statistically robust estimate for these factors. This means that the values chosen for these parameters are largely subjective estimates or educated guesses.

Wide Ranges of Possible Values:

Because many of these factors are not well-constrained, if you change one of the more uncertain parameters even slightly, the final estimate for

𝑁

N (the number of civilizations) can vary by many orders of magnitude. This wide range shows that the equation can lead to very different outcomes based on personal or theoretical assumptions.

Heuristic, Not Predictive:

The Drake Equation was never meant to provide a precise answer. Instead, it serves as a way to organize our thinking about what conditions might be necessary for the development of extraterrestrial civilizations. It encourages discussion about the relative importance of different factors and highlights where our scientific knowledge is limited.

Is the Drake Equation Accurate or More Opinion-Based?

Accurate?

In the sense of being a strict mathematical model with well-defined inputs and predictable outputs, the Drake Equation is not accurate. Its accuracy is limited by the extreme uncertainties in several of its key parameters.

Opinion-Based?

Many of the terms in the equation, especially those concerning the evolution of life and intelligence, are based on opinion, interpretation, and the single example of Earth. Therefore, while the structure of the equation is logical, the numbers you put into it (and hence the final result) are often more reflective of our current opinions and assumptions than of robust empirical data.

Conclusion

The Drake Equation is a valuable tool for framing the question of extraterrestrial life. It helps scientists and enthusiasts break down a complex problem into smaller, more manageable questions. However, because several of its factors are highly uncertain and subject to personal interpretation, it is more of a conceptual guide—or even a way to stimulate discussion—than a formula that provides a definitive, accurate prediction of the number of extraterrestrial civilizations.

In summary, while the Drake Equation is useful for thinking about the various factors that might lead to the emergence of a civilization, its outputs should be taken as highly speculative estimates rather than precise measurements.




あなた:

Please also consider the possiblities of non-human intelligent emrgencing from the long history of Sol system and nearby planets and see if there is any possiblites that in one time intelligent life emerged in nearby planets and see this to the equation

ChatGPT

Reasoned about non-human intelligence and the Drake Equationを19 秒行う

Evaluating non-human intelligence

I'm thinking about the potential for non-human intelligent life forms in the Sol system and neighboring planets, and how this might factor into the equation.

Piecing together possibilities

I'm thinking about how to integrate the emergence of non-human intelligent life, possibly on Mars or Europa, into the Drake Equation for the Sol system and neighboring planets.

Reflecting on potential

It's interesting to think about the hypothesis of intelligent life emerging on Mars or Venus, though Earth remains the only known life-supporting planet in the solar system.

Considering other realms

I'm examining if intelligent life could have emerged on planets like Mars, Venus, or Europa, and how this possibility aligns with the predictions of the Drake Equation.

Analyzing parallel evolution

Hmm, I’m thinking about how non-human intelligent life on Mars or Venus could intersect with the assumptions of the Drake Equation, which seems to focus solely on Earth-based evolution.

Evaluating life exploration

I’m piecing together the hypothesis of non-human, advanced, intelligent life in the solar system. Mars, Venus, and Titan present challenges, but Europa and Enceladus might harbor microbial life.

Adapting the equ Permalink | 記事への反応(0) | 21:12

Chatgptが答えた異星人の存在可能性とのそのロジック

Please consider the histroy of humanity from biological perpsecitve and current known fact in nearby universe, which expo-planet (from the Sol system perspective) is most likely to have civlizaed society? Please add percentage next to it in the chart

ChatGPT

Reasoned about exoplanet civilization likelihoodを28 秒行う

Evaluating planetary prospects

OK, I’m looking at the likelihood of a civilized society on an exoplanet within our Solar System. I’ll consider biological history and current space knowledge, aiming to identify the most promising candidate.

Identifying potential candidates

I'm considering exoplanets like Proxima Centauri b and TRAPPIST-1e, which might suggest they are within or observed from our Solar System.

Assessing potential candidates

I’m evaluating Proxima Centauri b, Barnard's Star, LHS 1140, and TRAPPIST-1, focusing on their habitable zones and available data. The Drake equation might help estimate their civilized society likelihoods.

Identifying promising exoplanets

I’m noting key exoplanets like Proxima Centauri b and TRAPPIST-1, which have Earth-like characteristics and are in habitable zones. This narrows down the potential candidates for advanced civilizations.

Assessing habitable zones

I'm gathering info on planets like Proxima Centauri b and TRAPPIST-1, considering factors like magnetic fields, atmospheres, and proximity to G-type stars for their potential to support advanced civilizations.

Evaluating exoplanet prospects

I'm noting that Proxima Centauri b, despite being close and around a red dwarf star, might support life if it has a magnetic field and atmosphere. This makes me think about its potential.

Charting probabilities

I'm estimating civilization probabilities for exoplanets like Proxima Centauri b and TRAPPIST-1 e, using speculative percentages based on the Drake equation and the lack of evidence for intelligent life.

Charting speculative odds

I'm crafting a chart with exoplanet names and civilization likelihood percentages, grounded in the long timeline of life's evolution, despite the speculative nature of these figures.

Identifying exoplanet contenders

I’m evaluating exoplanets like Proxima Centauri b, TRAPPIST-1 e, and Kepler-186f, considering their star types and distances, to gauge their potential for supporting advanced civilizations from our solar system's viewpoint.

Weighing proximity and observation

I'm leaning towards Proxima Centauri b due to its closeness and observational potential, despite concerns about its flare star dynamics. TRAPPIST-1 e, f, or g are also worth considering.

Revisiting exoplanet options

I'm focusing on exoplanets like Proxima Centauri b, Ross 128 b, LHS 1140 b, TRAPPIST-1 e/f/g, and K2-18b, aiming to chart their likelihood of hosting a civilized society based on current knowledge.

Assessing exoplanet potentials

I'm gathering speculative probabilities for exoplanets like Proxima Centauri b and TRAPPIST-1 e/f/g, using the Drake equation and current understanding, to better estimate their chances of hosting a civilized society.

Refining speculative probabilities

I’m refining speculative probabilities for exoplanets, including Proxima Centauri b and TRAPPIST-1 e/f/g, to estimate their chances of hosting a civilized society, considering Earth's long biological history.

Refining odds

I'm considering the astronomical timeline for intelligent life on Earth, leading me to assign even lower speculative odds for exoplanets like Proxima Centauri b and TRAPPIST-1 e.

Clarifying speculative nature

I’m crafting a simplified chart with arbitrary percentages, clearly noting the speculative nature and lack of scientific data, while considering the target audience's basic understanding of the topic.

Mapping out speculative odds

I’m charting arbitrary percentages for exoplanets, clarifying their speculative nature, and ensuring the data is accessible for young audiences with minimal scientific detail.

Crafting a chart

I’m creating a markdown table with speculative percentages for the likelihood of civilized life on exoplanets, emphasizing their purely theoretical nature and considering the understanding level of an 8-year-old.

Integrating speculative analysis

I’m mapping out a markdown chart with speculative percentages for the likelihood of a civilized society on exoplanets, mindful of the complexity and simplifying for an 8-year-old's understanding.

Assessing likelihoods

I’m piecing together markdown for exoplanets, noting Proxima Centauri b's reduced civilized life chance due to the red dwarf's activity. This inclusion highlights the speculative nature of the analysis.

Piecing together speculative odds

I’m detailing a markdown chart for audience-friendly exoplanet likelihoods, considering environmental challenges and adding a disclaimer about the speculative nature and lack of evidence.

Piecing together

I’m leaning towards Proxima Centauri b for its proximity and silent star, but I’ll add a speculative chart ranking nearby exoplanets, noting their advanced civilizations' hypothetical likelihood.

Assessing civilization probabilities

I'm emphasizing the slow emergence of intelligent life on Earth, which suggests that the odds of any habitable planet developing a complex civilization might be as low as a few percent.

Below is a very speculative chart thatbased on what we know about Earth’s long, winding path from simple life to a “civilized society” and our limited observations of nearby exoplanets—gives some fun, made‑up percentage chances for a few of our best candidate exoplanets. Remember: Scientists have not yet found any proof of life (let alone advanced civilizations) on any exoplanet. These numbers are just playful estimates to help you think about the ideas!

Speculative Chances of Finding an Advanced Civilization on Nearby Exoplanets

Exoplanet Estimated Likelihood of a Civilized Society

Proxima Centauri b ~2%

TRAPPIST-1 e ~1.5%

TRAPPIST-1 f ~1%

TRAPPIST-1 g ~1%

LHS 1140 b ~0.5%

How Did We (Very Roughly) Guess These Numbers?

Earth’s Example:

On Earth, life began as simple single‑celled organisms and took billions of years to evolve into a species that built complex societies. This long journey suggests that—even if a planet is in the “habitable zone” (where liquid water could exist)—developing an advanced, civilized society might be rare.

Nearby Exoplanets:

Proxima Centauri b:

This is the closest exoplanet to us. Even though its star (Proxima Centauri) is a red dwarf that sometimes sends out strong flares (which might harm life), its closeness makes it one of our most interesting candidates. That’s why we give it a slightly higher guess (~2%).

TRAPPIST-1 System (e, f, g):

These planets are part of a group orbiting a very cool star. Their environments might be challenging (for example, they could be tidally locked, meaning one side always faces the star), so the chance of a complex, advanced civilization might be a bit lower.

LHS 1140 b:

This planet is promising in some ways but is a little farther away and around a dimmer star, so our playful estimate is even lower.

A Final Note

All of these percentages are extremely rough guesses based on what little we understand about the conditions for life and intelligence. Scientists use ideas like the Drake Equation to think about these chances—but until we have concrete evidence, these numbers remain just for fun and imagination.

Enjoy exploring these ideas—and remember, space is full of mysteries waiting to be discovered!




あなた:

Please examine the Drake Equation itself and see if this euqation is acculate or more opition in the equation you will use

ChatGPT

Reasoned about the Drake Equationを6 秒行う

re-examining the Drake Equation

evaluating the Drake Equation's value

Clarifying the Drake Equation

OK, let me see. The Drake Equation isn't a precise formula; it's more of a guiding heuristic that tackles numerous uncertainties regarding extraterrestrial civilizations.

Assessing the Drake Equation

Thinking through the Drake Equation, I’m evaluating its conceptual nature, its uncertain parameters, and its criticism to conclude on its reliability as an accurate predictive model.

Understanding the Drake Equation

I’m mapping out the Drake Equation as a conceptual guide, detailing its parameters, which are often based on estimates or opinions, to evaluate its reliability for predicting extraterrestrial civilizations.

The Drake Equation is a famous formula that was created to help scientists think about the many factors involved in estimating the number of detectable extraterrestrial civilizations in our galaxy. However, when we look at the equation closely, we see that it is more of a conceptual framework or heuristic tool than a precise, predictive formula. Let’s break down why:

The Drake Equation

The equation is usually written as:

𝑁

=

𝑅

×

𝑓

𝑝

×

𝑛

𝑒

×

𝑓

𝑙

×

𝑓

𝑖

×

𝑓

𝑐

×

𝐿

N=R

×f

p

×n

e

×f

l

×f

i

×f

c

×L

Where:

𝑅

R

: The average rate of star formation per year in our galaxy.

𝑓

𝑝

f

p

: The fraction of those stars that have planetary systems.

𝑛

𝑒

n

e

: The average number of planets that could potentially support life per star with planets.

𝑓

𝑙

f

l

: The fraction of those planets where life actually develops.

𝑓

𝑖

f

i

: The fraction of planets with life where intelligent life evolves.

𝑓

𝑐

f

c

: The fraction of civilizations that develop technology that releases detectable signals into space.

𝐿

L: The length of time such civilizations release detectable signals.

Why the Drake Equation Is More of a Guideline Than a Precise Formula

Uncertain Inputs:

Well-Known Parameters:

Some factors, like

𝑅

R

(star formation rate) and

𝑓

𝑝

f

p

(fraction of stars with planets), have become better known through modern astronomy.

Highly Speculative Factors:

The parameters related to the development of life and intelligence

𝑓

𝑙

f

l

,

𝑓

𝑖

f

i

,

𝑓

𝑐

f

c

, and

𝐿

L—are based on very limited data. For example, Earth is the only planet we know where life has developed, so we have no way to compare or derive a statistically robust estimate for these factors. This means that the values chosen for these parameters are largely subjective estimates or educated guesses.

Wide Ranges of Possible Values:

Because many of these factors are not well-constrained, if you change one of the more uncertain parameters even slightly, the final estimate for

𝑁

N (the number of civilizations) can vary by many orders of magnitude. This wide range shows that the equation can lead to very different outcomes based on personal or theoretical assumptions.

Heuristic, Not Predictive:

The Drake Equation was never meant to provide a precise answer. Instead, it serves as a way to organize our thinking about what conditions might be necessary for the development of extraterrestrial civilizations. It encourages discussion about the relative importance of different factors and highlights where our scientific knowledge is limited.

Is the Drake Equation Accurate or More Opinion-Based?

Accurate?

In the sense of being a strict mathematical model with well-defined inputs and predictable outputs, the Drake Equation is not accurate. Its accuracy is limited by the extreme uncertainties in several of its key parameters.

Opinion-Based?

Many of the terms in the equation, especially those concerning the evolution of life and intelligence, are based on opinion, interpretation, and the single example of Earth. Therefore, while the structure of the equation is logical, the numbers you put into it (and hence the final result) are often more reflective of our current opinions and assumptions than of robust empirical data.

Conclusion

The Drake Equation is a valuable tool for framing the question of extraterrestrial life. It helps scientists and enthusiasts break down a complex problem into smaller, more manageable questions. However, because several of its factors are highly uncertain and subject to personal interpretation, it is more of a conceptual guide—or even a way to stimulate discussion—than a formula that provides a definitive, accurate prediction of the number of extraterrestrial civilizations.

In summary, while the Drake Equation is useful for thinking about the various factors that might lead to the emergence of a civilization, its outputs should be taken as highly speculative estimates rather than precise measurements.




あなた:

Please also consider the possiblities of non-human intelligent emrgencing from the long history of Sol system and nearby planets and see if there is any possiblites that in one time intelligent life emerged in nearby planets and see this to the equation

ChatGPT

Reasoned about non-human intelligence and the Drake Equationを19 秒行う

Evaluating non-human intelligence

I'm thinking about the potential for non-human intelligent life forms in the Sol system and neighboring planets, and how this might factor into the equation.

Piecing together possibilities

I'm thinking about how to integrate the emergence of non-human intelligent life, possibly on Mars or Europa, into the Drake Equation for the Sol system and neighboring planets.

Reflecting on potential

It's interesting to think about the hypothesis of intelligent life emerging on Mars or Venus, though Earth remains the only known life-supporting planet in the solar system.

Considering other realms

I'm examining if intelligent life could have emerged on planets like Mars, Venus, or Europa, and how this possibility aligns with the predictions of the Drake Equation.

Analyzing parallel evolution

Hmm, I’m thinking about how non-human intelligent life on Mars or Venus could intersect with the assumptions of the Drake Equation, which seems to focus solely on Earth-based evolution.

Evaluating life exploration

I’m piecing together the hypothesis of non-human, advanced, intelligent life in the solar system. Mars, Venus, and Titan present challenges, but Europa and Enceladus might harbor microbial life.

Adapting the equ Permalink | 記事への反応(0) | 21:12

2025-01-15

Halo Finally Looks Set to Make the Jump to PlayStation This Year

Microsoft is seemingly ready to launch its flagship Xbox video game series Halo on rival platforms for the first time, including PlayStation and Nintendo Switch 2.

Leaker NateTheHate, who this week reported that Nintendo is set to reveal Switch 2 on January 16, also reported in a separate podcast that Microsoft will finally bring Halo to PlayStation in the form of a PlayStation 5 port of Halo: The Master Chief Collection, as well as a release on Switch 2. Windows Central’s Jez Corden subsequently corroborated the report.

マイクロソフトは、主力の Xbox ビデオゲーム シリーズ Halo を、PlayStationNintendo Switch 2 などの競合プラットフォームで初めてリリースする準備が整ったようです。

今週、任天堂1月16日Switch 2を発表する予定であると報じたリーカーのNateTheHateは、別のポッドキャストで、マイクロソフトがついにHaloPlayStationに持ち込み、Halo: The Master Chief CollectionPlayStation 5移植Switch 2のリリースを行うとも報じた。その後、Windows CentralのJez Cordenがこの報道裏付けた。

一部では今月下旬から来月上旬にかけて「STATE OF PLAY」が公開されるとかいう噂も出始めたし、そのタイミングで発表されるのかな

2024-11-17

日本マスコミが伝えない

➤「救いようが最もうない、極東自称他称の〝ジャーナリスト〟や〝学者〟、〝知米派〟は読まなくても構い。読んでもその肥大化した自己承認欲求、度し難い自己愛人格では読むことはできないし、理解もできない。ただ見下した目線で見やるだけで、そこに自分が利用できる素材がなければ鼻で嗤うだけだ。この文章は、我がU.S.を領りたい、領ろうと下向きの反省眼光で欲する諸君に読んで貰いたい。

I Traveled to 46 States in America This Summer. Here’s Why Trump Won.

By Frank S. Zhou

By Ezekiel A. Wells

Ezekiel A. Wells ’27 is a Double Concentrator in Environment Science & Engineering and Economics in Eliot House. He spent last summer traveling to 46 American states conducting interviews for his YouTube series, “Crossroads America.

3 days ago

A week after Democrats’ election loss, accusations have flown in every direction within their Party. Some fault President Joe Biden for an egoistic refusal to drop out of the race earlier. Some blame the Harris campaign for failing to serve key demographics and communicate a clear vision for the country. And some blame Americans, claiming that racism and sexism drove voters toward Trump.

These factors certainly exist, but we’re missing a larger piece of the picture.

Over the summer, I traveled to 46 states in the U.S., creating a YouTube series highlighting slices of life across the country. In conversations from my nearly three-month road trip, I spoke with Republicans who were certain that inflation is entirely Biden’s fault and Democrats who, despite their frustrations with corporate profits and desires for universal healthcare, hoped for a more moderate candidate. From supporters of all candidates, I heard a shocking amount of misinformation.

After combing through hundreds of hours of interview footage from swing state Trump voters, I am certain that, as much as other factors influenced the outcome of the election, our crumbling media landscape — which has caused a rift in our democracy — is most to blame.

In the postwar period, news was dominated by three main channels, and because of the Fairness Doctrine, each station reported the same stories and covered multiple sides of each issue. Viewers picked which channels they watched mainly based on their preferences for news anchors’ personalities. Of course, this model had its problems, but, at the end of the day, it meant that Americans worked with a shared set of facts.

A shared set of facts is not the world we live in today.

Throughout my interviews, conspiracy theories were rampant, and on at least five separate occasions across separate states, I was told that Bill Gates tampers with our food, adding plastic to our fruits and vegetables to make his medical investments more profitable.

In conversations with voters, neither side seemed able to name many specific policy issues they cared about; everyone just seemed to repeat the words of their favorite pundits, podcast hosts, and internet personalities.

Although this behavior is harmful, I don’t blame everyday Americans. Blame falls on the media that has ostracized, disillusioned, and misinformed them.

Advertisement

I first saw this trend with low-wage workers in West Virginia, who — despite falling inflation rates — have seen stagnated salaries and clear increases in food costs. Channels like Fox News bred anger and resentment for many of them.

Take July of this summer, for example, when for the first time in his presidency, prices actually fell under the Biden administration. Traditional media establishments rushed to celebrate this victory, with one article from CNN declaring, “The White House can finally cross out ‘inflationon its list of presidential liabilities.” However, outside these bubbles, I observed many Americans held a different view.

In late July, I was welcomed at a massive family reunion in Tylertown, Mississippi, where one Trump voter — a middle-aged, Black, family man, pastor, and soul food enthusiast — made this clear.

“When I go in the grocery stores, and I gotta spend my last to get groceries, you mean to tell me I’m not gonna look and see who’s gonna vote to help me? I voted for Trump and I’d vote for him again, because he put money in our pocket,” he told me.

In their coverage, mainstream news organizations obsess over the Federal Reserve’s next rate cuts while failing to connect with people concerned with their next meals. With titles like “Vance: Young Americans ‘Are Becoming Paupers’ Due To Inflation, High Housing Costs,” sites like The Daily Wire had their fingers on the pulse of American sentiment, welcoming new readership from those who felt neglected by traditional media.

This problem was not just confined to the economy. While Biden’s mental state was deteriorating, liberal media outlets seemed to under-cover these stories, sheltering him from scrutiny of his declining capabilities, until the infamous presidential debate.

Formerly trusted networks slowly made themselves indigestible to the polarized American public, and in 2024, for the third year in a row, a Gallup poll found that more Americans indicated having “no trust” in the media than those who trust it a “great deal/fair amount”.

So where does the average American turn when the nation’s media cannot be trusted? For many people, it was YouTube talk shows, Newsmax, and podcasters such as Joe Rogan.

While Democrats seek to blame various internal factors for this election’s loss, I cannot help but think of Joe Rogan’s Trump endorsement, the many blind lies I heard from ordinary citizens across the country, and declining trust in American journalism.

As Harvard students and members of higher education institutions, we have a part to play in the problem. At Harvard’s Institute of Politics, those who denied the 2020 election results have been precluded from speaking at the JFK Jr. Forum. While the goal is understandable, it shields students from understanding the American viewpoints they represent.

Advertisement

There is a difference between platforming intentional and manipulative misinformation and listening to and learning about where people are and what they believe.

As a pipeline to mainstream media, Harvard, and its future journalists, have to consider the audience they lose when they stay inside of their bubble and ignore the issues of everyday Americans.

The disappearance of factual importance in our world is alarming and dangerous, but if we, as aspiring journalists, politicians, and engaged citizens, want to be taken seriously in communicating Trump’s threat to democracy, inflationary tariff policies, and so on, we owe American voters that seriousness, too.

Ezekiel A. Wells ’27 is a Double Concentrator in Environment Science & Engineering and Economics in Eliot House. He spent last summer traveling to 46 American states conducting interviews for his YouTube series, “Crossroads America."

ログイン ユーザー登録
ようこそ ゲスト さん