/tmp/bucket

將分為兩部分討論：

1. 真
2. 解釋性

什麼是真知識

認知的局限性

我們無法否認我們的思想、身體限制了我們對於世界的認知。身體上，我們的眼睛能看到的光的波段是有限的；思想上，我們的語言所能描述的範圍，就是我們能理解的範圍。

所以我們可以初步把知識分為：可理解的、不可理解的。

能驗證的就是真？

既然認知範圍外的我們碰不到、也確認不了，那我們就不管啦！關注我們能認知的就好(？)
只要在我們能理解的範圍內，驗證為真的知識就是真知識！

問題是，我們如何驗證呢？

例如，我們如何驗證天氣播報說：「今天是晴天」呢？

「很簡單啊，打開窗戶往外看不就知道了？」

「問題是我們怎麼驗證自己的感官器官運作正常呢？」

「那我們相信氣象數據總不會錯吧？」

「一樣的問題，我們怎麼驗證做氣象儀器的人、和解讀數據的人說的是真的呢？」

相信他人相信他人的相信

最後我們會發現，要理性的去驗證每件事成本太高，不可能做到去親證每件事。
所以我們選擇採信他人的說法，既然大家都說那是對的，那他是對的機率應該夠高足以讓我們相信。

但他人何嘗不是如此？

解釋性

「解釋性」高的知識是指更好解釋當前現象的知識。

豐收之神

讓稻作生長的是陽光、水？還是豐收之神？

平心而論，其實兩者都說得通，都具備解釋性。

我們今天之所以會傾向前者，只是因為前者更符合我們知道的其他物理「知識」。想像一下，如果我們是中世紀的普通人，擁有的是中世紀普通人的「知識體系」，那後者的解釋性可能的就強，因為他跟我們的其他知識擺在一起不矛盾！

我們可以發現，我們相信的其實是那與我們「知識體係」不矛盾、前後邏輯一致的知識，而整件事又受我們「經驗」限制。

小結

• 理解之外無法觸及，理解之內的無法逐一驗證，所以我們不得不人云亦云
• 現在普遍被認為是真的，也可能只是暫時的真，所以我們必須時時謹慎。

但只有我們如此意識到認知上的諸多限制，才能有機會更靠近那個真實。

Reference

• 呵，人類妳對【知識】一無所知 | 當代哲學知識論亂談

Error

I got this error when I run hexo server. The site still works but it made feel unsatisfied…

1
2
3
4
5
6
7

(node:87224) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:87224) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:87224) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
(node:87224) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(node:87224) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:87224) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency

My dependencies:

• node: v16.8.0
• hexo: 6.1.0
• hexo-cli: 4.3.0

Solution

Append below code to package.json then run yarn install or npm install. The error should be fixed.

1
2
3

"resolutions": {
  "stylus": "^0.54.8"
}

Reference

• https://www.haoyizebo.com/posts/710984d0/

最近看中國視頻學到的新詞。

什麼是「內卷」

簡單定義：低級的循環往復

從農場、工廠、互聯網創作，都是產出供給，而供給需要被有效的消費掉

在需求不變的情況下，新生產力(新工人)投入，可能導致以下兩種情況：

• 削價競爭，也就是「內卷」
• 淘汰多餘的生產力(工人)

中國內卷化的原因

出口需求飽和，但國內消費又不足夠填補

國內消費需求低的可能原因：

• 繳了各種貸款(房貸、車貸)沒錢消費
• 勞工普遍低薪
• 再分配(稅收)沒分到一般大眾

Reference

工资太低？什么都难做？究竟是什么导致中国这些年的”突然内卷化”？【Eng Sub】What caused China’s Involution/Neijuanhua? Rich Poor Gap?

About burn

When

• burn as gas fee (BEP-95)
• burn by quarter
• burn by price (Auto-Burn)
• some smart contracts also burn BNB in some conditions

Why

To make deflation

How

Send tokens to an address without a private key, which means no one can access the tokens anymore.

BEP-95

Why

To fasten the burn efficiency.

How

Since the solution is to burn partial of validators’ reward, the more users use BSC (which means more blocks need to be validated by validators), the more BNB would be burned.

Auto-Burn

Rule

The more the price of BNB decreases, the more BNB will be burned.

When the total supply is lower than 1B, the burn process stops (BEP-95 still works).

Formula

1

B = N * 1000 / (P + K)

• B: how many BNB to burn
• N: new BNB amount of this quarter
• P: average price
• K: constant value, 1000

More detail about Auto-Burn

Intro

I got a mission to clone an existing service, which has its database separately from the original.

Here is my to-do list:

1. create tables
2. sync data

This article will focus on how to sync data. To read how to create tables from the old database check out here

Laravel Database Sync

I found this great tool to do this task: https://github.com/waelwalid/laravel-database-sync

Please follow the instructions to install the tool.

Adjustments

I run my app in a php-fpm-alpine docker container so some adjustments need to do or the tool won’t work.

1. Make the container can run the shell scripts
2. Install mysql-client
3. Disable LOCK TABLE if you are NOT a root user in the synced database when executing mysqldump

1. Make the container can run the shell scripts

The sync-tool is implemented by shell scripts, and with the header, #!/bin/bash, so only bash can run it.

And since I used an alpine image, which doesn’t have the Bash installed by default so I had two options:

1. Change the header to #!/bin/sh
2. Install Bash or just use an Ubuntu image for convenience

1
2

# add this to the Dockerfile
RUN apk add --no-cache --upgrade bash

2. Install mysql-client

Still, by default, the alpine image doesn’t come with mysql-client, which is used in the shell script so we need to install it.

1

apk add --no-cache mysql-client

3. Disable LOCK TABLE if you are NOT a root user in the synced database

Since I sync the data using a user who ONLY has SELECT privilege, I need to disable LOCK TABLE, and PROCESS when dumping the data.

Open vendor/waelwalid/laravel-database-sync/database-update.sh.

Add --single-transaction=TRUE --no-tablespaces after mysqldump command.

Like this:

1
2
3
4

mysqldump -v --single-transaction=TRUE --no-tablespaces \
-h $REMOTE_DATABASE_HOST -u $REMOTE_DATABASE_USER \
-p $REMOTE_DATABASE_PASS $REMOTE_DATABASE_NAME \
> $CONFIG/dumps/remote-database-$CURRENT_TIME.sql

If you use login as root, or other users with LOCK TABLE, and PROCESS privileges, you can skip this step.

Quote from the document:

mysqldump requires at least the SELECT privilege for dumped tables, SHOW VIEW for dumped views, TRIGGER for dumped triggers, LOCK TABLES if the –single-transaction option is not used, and (as of MySQL 8.0.21) PROCESS if the –no-tablespaces option is not used. Certain options might require other privileges as noted in the option descriptions.

Check out for more details about mysqldump

After all

Now you can run composer database-update to sync the data, or just execute .vendor/waelwalid/laravel-database-sync/database-update.sh which is the same, cheers :)

Intro

I got a mission to clone an existing service, which has its database separately from the original.

Here is my to-do list:

1. create tables
2. sync data

This article will only record the first step. the next step will be written in the second episode.

How to create tables from the existing database

Since this project is a Laravel app, but without migration files so I came out with 2 solutions:

1. Create migrations from the existing database, then run php artisan migrate to create the same tables to my new database
2. Create create-table-SQLs from the existing database, then somehow run these SQLs

Migration Generator

I thought the first one is more ideal since it is easier for other developers to maintain so I googled “laravel create migration …” then google returned me a bunch of packages to do these tasks, nice!

here is a couple of choices:

• composer package:
  • https://github.com/Xethron/migrations-generator
  • https://github.com/barryvdh/laravel-migration-generator
  • https://github.com/adamkearsley/laravel-convert-migrations
• online convertor
  • https://laravelarticle.com/laravel-migration-generator-online

So I generated all the migrations in seconds, lovely!
Then I run php artisan migrate!

CRASH!

Checked out the migrations, found that the generator didn’t generate the codes properly. It missed some details, like lacking index, so I needed to go through each file to debug… which was not my purpose to use a tool so I tried the second solution, create tables by pure SQL

How to Execute SQL Files in Laravel

It is easier than I thought

1
2
3

use Illuminate\Support\Facades\DB;

DB::unprepared(file_get_contents('path/to/sql.sql'));

I test a table and it worked properly, created exactly same table as the original without error

Implement

So I exported the table structure in SQL from phpMyAdmin manually (the total number of tables is still acceptable for me to do this).

Instead of creating a command to do this task, I still generated migrations matched to the tables since I would like to have the ROLLBACK feature in Laravel migration. Remember? We can create migrations in seconds by using one of the mentioned packages. Don’t forget to edit .env to switch to the original database, And after generating, switch back to the NEW database.

Here is my migration code. I put all the SQL in database/sql_migrations but you can put them anywhere you like.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;

class CreateNewTable extends Migration {

    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        $sqlpath = 'database/sql_migrations/'.basename(__FILE__, ".php").'.sql';
            Illuminate\Support\Facades\DB::unprepared(file_get_contents($sqlpath));
    }


    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop('new');
    }

}

After all files are set, we can easily run php artisan migrate to create tables, and php artisan migrate:rollback to rollback.

Laravel | Sync Data From an Existing Database

Use this API

1

<img src="https://render.githubusercontent.com/render/math?math=O(n^2)">

Result:

Reference

https://gist.github.com/a-rodin/fef3f543412d6e1ec5b6cf55bf197d7b