Dan Abramov's piece on a social filesystem crystallized something important here. He describes how the AT Protocol treats user data as files in a personal repository; structured, owned by the user, readable by any app that speaks the format. The critical design choice is that different apps don't need to agree on what a "post" is. They just need to namespace their formats (using domain names, like Java packages) so they don't collide. Apps are reactive to files. Every app's database becomes derived data i.e. a cached materialized view of everybody's folders.
struct Entity {
，这一点在新收录的资料中也有详细论述
Creating or Modifying a Table，更多细节参见新收录的资料
Abusing workflows that use the pull_request_target directive, causing workflow execution from untrusted PRs to run with high permissions
�@�}6�́AAI�őn�o�������Ԃ̎g����������AI���p�p�x�ʂ̕��Ϗ��k�������Ԃ��������O���t���B