Add P.A.R.A. methodology documentation and restructure Personal folder
- Created Methodology.md to outline the P.A.R.A. system and its components. - Added Outline.md for a structured overview of P.A.R.A. content. - Documented PKM content organization decisions in PKM-Consolidation-Decision.md. - Introduced Workflows.md to explain practical applications of P.A.R.A. in work scenarios. - Moved sensitive information to security-sensitive folder and restructured the Personal folder to align with P.A.R.A. principles. - Archived backup files including Matrix Me.md and TTG Cookies.md. - Implemented a comprehensive refactor of the Personal folder to improve organization and security.
This commit is contained in:
windyboy
@@ -1,289 +0,0 @@
|
||||
1. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://www.dogsheep.cn/transform/Q08CyX81GI](https://www.dogsheep.cn/transform/Q08CyX81GI)
|
||||
|
||||
2. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$5jBx4l29mfPuLYTif430IG1fm7qCHlLmbq5yxw5UkJM?via=matrix.chans.xyz)
|
||||
|
||||
[https://live.qq.com/10014465](https://live.qq.com/10014465)
|
||||
|
||||
3. [](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$vH6DXdfFU4FChoo94TBxmcgRXWIDtzV8D0yJ_G55cho?via=matrix.chans.xyz)
|
||||
|
||||
[https://www.lanjing.live/live/1016753](https://www.lanjing.live/live/1016753)
|
||||
|
||||
4. ---
|
||||
|
||||
## Wed, Aug 3 2022
|
||||
|
||||
---
|
||||
|
||||
5. 糖醋小排
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22](https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22)
|
||||
|
||||
7. ---
|
||||
|
||||
## Sun, Oct 9 2022
|
||||
|
||||
---
|
||||
|
||||
8. 糖醋小排
|
||||
|
||||
[](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$B-jSeeAKV5uxOhso9vY2vAEzlKKyahMpQb45YwSAiYw?via=matrix.chans.xyz)
|
||||
|
||||
adb shell pm grant com.dp.logcatapp [android.permission.READ](http://android.permission.read/)_LOGS
|
||||
|
||||
|
||||
|
||||
|
||||
15. 糖醋小排
|
||||
|
||||
|
||||
[https://gzshb.gzonline.gov.cn/index.html](https://gzshb.gzonline.gov.cn/index.html)
|
||||
|
||||
16. ---
|
||||
|
||||
## Wed, Nov 2 2022
|
||||
|
||||
---
|
||||
|
||||
17. 糖醋小排
|
||||
|
||||
|
||||
[gzzn.ipowersoft.net:8092](http://gzzn.ipowersoft.net:8092/)
|
||||
opsuser
|
||||
opsuser@Gzzn
|
||||
|
||||
18. ---
|
||||
|
||||
## Thu, Nov 10 2022
|
||||
|
||||
---
|
||||
|
||||
19. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://docs.qq.com/sheet/DTEhJSmNiYm53clBk](https://docs.qq.com/sheet/DTEhJSmNiYm53clBk)
|
||||
|
||||
20. ---
|
||||
|
||||
## Thu, Nov 17 2022
|
||||
|
||||
---
|
||||
|
||||
21. 糖醋小排
|
||||
|
||||
|
||||
|
||||
6258 1017 4403 4127
|
||||
|
||||
22. ---
|
||||
|
||||
## Wed, Feb 15 2023
|
||||
|
||||
---
|
||||
|
||||
23. 糖醋小排
|
||||
|
||||
|
||||
[https://decentralizedcreator.com/reverse-prompt-lookup-image-to-prompt/](https://decentralizedcreator.com/reverse-prompt-lookup-image-to-prompt/)
|
||||
|
||||
24. 糖醋小排
|
||||
|
||||
|
||||
[https://marketplace.visualstudio.com/items?itemName=vaibhavacharya.code-gpt-va](https://marketplace.visualstudio.com/items?itemName=vaibhavacharya.code-gpt-va)
|
||||
|
||||
25. ---
|
||||
|
||||
## Thu, Feb 16 2023
|
||||
|
||||
---
|
||||
|
||||
26. 糖醋小排
|
||||
|
||||
|
||||
[gzzn.ipowersoft.net:8092](http://gzzn.ipowersoft.net:8092/)
|
||||
opsuser
|
||||
opsuser@Gzzn
|
||||
|
||||
27. ---
|
||||
|
||||
## Sat, Mar 11 2023
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
29. ---
|
||||
|
||||
## Mon, Mar 13 2023
|
||||
|
||||
---
|
||||
|
||||
30. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22](https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22)
|
||||
|
||||
31. 糖醋小排
|
||||
|
||||
|
||||
|
||||
1. 在 Telegram 添加机器人账号 @ure_best_bot
|
||||
2. 发送命令 /start 5CKxFIeYNHvLuV5X (点击复制) 给机器人
|
||||
|
||||
32. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://sub.cutecloud.link/link/rCvnzdf6GsYxO0TT?clash=1](https://sub.cutecloud.link/link/rCvnzdf6GsYxO0TT?clash=1)
|
||||
|
||||
33. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://subapi1.gardenparty.one/link/7662I1Snxww7zkgq?sub=2&client=clash](https://subapi1.gardenparty.one/link/7662I1Snxww7zkgq?sub=2&client=clash)
|
||||
|
||||
34. ---
|
||||
|
||||
## Wed, Mar 15 2023
|
||||
|
||||
---
|
||||
|
||||
35. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://18.laomao1.xyz/api/v1/client/subscribe?token=daddf8de9b1e002478b6fc59a6760e85](https://18.laomao1.xyz/api/v1/client/subscribe?token=daddf8de9b1e002478b6fc59a6760e85)
|
||||
|
||||
36. ---
|
||||
|
||||
## Mon, Mar 20 2023
|
||||
|
||||
---
|
||||
|
||||
37. 糖醋小排
|
||||
|
||||
|
||||
|
||||
天河区天河南二路19号宏发大厦
|
||||
|
||||
38. [](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$KG5CYE4CBEYvbXxIrqIcwdJsrRYfWPEDK5Hu7GnInm8?via=matrix.chans.xyz)
|
||||
|
||||
联想移动客户服务中心（广州天河南二路店） 天河区天河南二路19号宏发大厦5楼541室（地铁三号线石牌桥a出口往东前行20米进楼巴候车室北门坐电梯5楼） 联系电话：020-85239885 营业时间：9:00-18:00
|
||||
|
||||
39. ---
|
||||
|
||||
## Wed, Mar 22 2023
|
||||
|
||||
---
|
||||
|
||||
40. 糖醋小排
|
||||
|
||||
|
||||
5楼541号
|
||||
|
||||
41. [](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$1efo6uPbdud2DuUKAZ-qcwQr4U2e7iJrmDuNAXxNGqs?via=matrix.chans.xyz)
|
||||
|
||||
[
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
](blob:https://app.element.io/f01ed754-55a6-4fa1-9288-c7beebacf35c)
|
||||
|
||||
42. [](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$W2YW0yafatgKihSSe-AhI_TTgF-BEYl44ODjJ8vkMwQ?via=matrix.chans.xyz)
|
||||
|
||||
[
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
](blob:https://app.element.io/2f909ed3-b52f-4bf6-a580-3b64218901fa)
|
||||
|
||||
43. ---
|
||||
|
||||
## Thu, Mar 23 2023
|
||||
|
||||
---
|
||||
|
||||
44. 糖醋小排
|
||||
|
||||
|
||||
|
||||
Hi, here’s your giffgaff password reset request for bb668161. Click here to continue: [https://giffgaff.com/auth/reset/new-password?token=cf6b4bd286076012b66d74c282d60f7a02324fd3&username=bb668161](https://giffgaff.com/auth/reset/new-password?token=cf6b4bd286076012b66d74c282d60f7a02324fd3&username=bb668161)
|
||||
|
||||
45. ---
|
||||
|
||||
## Mon, Mar 27 2023
|
||||
|
||||
---
|
||||
|
||||
46. 糖醋小排
|
||||
|
||||
|
||||
|
||||
A3-XJVFVNV-SPM4EW-5G4SL-MNQNL-44ZRW-76Z8D
|
||||
|
||||
47. ---
|
||||
|
||||
## Tue, Mar 28 2023
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
49. ---
|
||||
|
||||
## Wed, Mar 29 2023
|
||||
|
||||
---
|
||||
|
||||
50. 糖醋小排
|
||||
|
||||
糖
|
||||
|
||||
[](https://matrix.to/#/!PvmBDNIGRbaczLicYT:matrix.chans.xyz/$cqKGzacU35kiDcZ2zvMepvfHlydbVKJ7FWTCzuzszvY?via=matrix.chans.xyz)
|
||||
|
||||
onepassword://team-account/add?email=genjuro00%[40gmail.com](http://40gmail.com/)&key=A3-XJWVNV-SPM4EW-5G4SL-MNQNL-44ZRW-76Z8D&server=https%3A%2F%[2Fmy.1password.com](http://2fmy.1password.com/)%2F
|
||||
|
||||
51. 糖醋小排
|
||||
|
||||
|
||||
|
||||
[https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22](https://api.inforun.work/v1/service/10004950?hmac=51EA681FE0EF28CB8766BA258D2555D8C0CBF849E1DCA1183C6C4C59585C1607&lang=&templateId=22)
|
||||
|
||||
52. 糖醋小排
|
||||
|
||||
|
||||
|
||||
53. ---
|
||||
|
||||
## Thursday
|
||||
|
||||
---
|
||||
|
||||
54. 糖醋小排
|
||||
|
||||
|
||||
|
||||
TF2YuWSNj8dJgNMe4CGakDswK8kkTQMSLu
|
||||
|
||||
55. 糖醋小排
|
||||
|
||||
|
||||
|
||||
歐易 備份 Q6BA2WMCCXGGKPRD
|
||||
@@ -1,56 +0,0 @@
|
||||
```
|
||||
[
|
||||
{
|
||||
"domain": "totheglory.im",
|
||||
"expirationDate": 1768864598.827946,
|
||||
"hostOnly": true,
|
||||
"httpOnly": true,
|
||||
"name": "pass",
|
||||
"path": "/",
|
||||
"sameSite": null,
|
||||
"secure": true,
|
||||
"session": false,
|
||||
"storeId": null,
|
||||
"value": "3d0fca9b34a18a2bc0e2074b9a3b13e0"
|
||||
},
|
||||
{
|
||||
"domain": "totheglory.im",
|
||||
"expirationDate": 1768864598.82797,
|
||||
"hostOnly": true,
|
||||
"httpOnly": false,
|
||||
"name": "laccess",
|
||||
"path": "/",
|
||||
"sameSite": null,
|
||||
"secure": true,
|
||||
"session": false,
|
||||
"storeId": null,
|
||||
"value": "1753096598"
|
||||
},
|
||||
{
|
||||
"domain": "totheglory.im",
|
||||
"expirationDate": 1768864598.827846,
|
||||
"hostOnly": true,
|
||||
"httpOnly": true,
|
||||
"name": "uid",
|
||||
"path": "/",
|
||||
"sameSite": null,
|
||||
"secure": true,
|
||||
"session": false,
|
||||
"storeId": null,
|
||||
"value": "17052"
|
||||
},
|
||||
{
|
||||
"domain": "totheglory.im",
|
||||
"expirationDate": 1787656599.24496,
|
||||
"hostOnly": true,
|
||||
"httpOnly": false,
|
||||
"name": "user_info_hash",
|
||||
"path": "/",
|
||||
"sameSite": null,
|
||||
"secure": true,
|
||||
"session": false,
|
||||
"storeId": null,
|
||||
"value": "e0de221dfdaee86bbbf4d69b451f5941"
|
||||
}
|
||||
]
|
||||
```
|
||||
@@ -1,3 +0,0 @@
|
||||
|
||||
|
||||
变量隐藏 [[Scope and Shadowing - Rust By Example]]
|
||||
@@ -1,16 +0,0 @@
|
||||
|
||||
|
||||
access token:
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
access token zed:
|
||||
```
|
||||
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
|
||||
```
|
||||
|
||||
release token:
|
||||
```
|
||||
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
|
||||
```
|
||||
@@ -1,38 +0,0 @@
|
||||
|
||||
Hi Amin,
|
||||
|
||||
Thanks for posting in the community. We are happy to help you.
|
||||
|
||||
According to your description, the situation on your end is likely caused by your organization's settings/policies (e.g. conditional access policy).
|
||||
|
||||
You can try the following steps, and then check if it still happens or not.
|
||||
|
||||
1. Please sign out your accounts from Office applications, then close all Office applications.
|
||||
|
||||
2. Open File Explorer, paste the following path, and delete all files and folders.
|
||||
|
||||
%localappdata%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
|
||||
|
||||
3. In the Windows search bar, search for "Access Work or School".
|
||||
|
||||
4. Check if you can see your business account in "Access Work or School".
|
||||
|
||||
- If you don't see it, please select Connect and add your business account.
|
||||
|
||||
|
||||
- If you can see it, please select it and select Disconnect. After that, please click "Connect" and log into your account again to register the device.
|
||||
|
||||
|
||||
5. Run one Office application, such as Word, sign into your account, and check again.
|
||||
|
||||
If the error message still appears after trying the above steps, I recommend you report the situation to your organization admin or IT department.
|
||||
|
||||
We look forward to your response. Thanks for your cooperation.
|
||||
|
||||
Sincerely,
|
||||
|
||||
George | Microsoft Community Moderator
|
||||
|
||||
[Updated by George Jiang MSFT 04:33 AM 08/10 2024 UTC + 8]
|
||||
|
||||
• Beware of Scammers posting fake Support Numbers here.
|
||||
@@ -1,5 +0,0 @@
|
||||
亲，以下是您购买的商品信息。
|
||||
MobaXterm Professional 便携版
|
||||
下载地址https://wwxs.lanzoum.com/ieYNw0s21tab
|
||||
备用地址https://www.987123.xyz/oss/lovemei9/MobaXterm/MobaXterm_Portable_v23.1.zip
|
||||
说明：复制以上地址进行下载，软件包中已经集成授权文件，下载后解压即用。
|
||||
@@ -1,3 +0,0 @@
|
||||
|
||||
api:
|
||||
secret_WggiGblW3PayQXirTeOCrS9FTsQ5EWGWHjInmNcvJdv
|
||||
@@ -1,86 +0,0 @@
|
||||
|
||||
Here is the **definitive, consolidated guide** for setting up Playwright on **Arch Linux (WSL)**.
|
||||
|
||||
This summary skips the trial-and-error we just went through and provides the "Happy Path" to get everything working in one go.
|
||||
|
||||
---
|
||||
|
||||
### 📋 Prerequisites
|
||||
* **WSL 2** (Recommended).
|
||||
* **Proxy (Optional):** If you are behind a proxy, remember to use `sudo -E` to preserve environment variables.
|
||||
|
||||
---
|
||||
|
||||
### 🚀 Step 1: System Prep & Node.js
|
||||
First, ensure your package database is fresh (fixes 404 errors) and install Node.js.
|
||||
|
||||
```bash
|
||||
# Update system and install Node.js/npm
|
||||
# Use -E if you have https_proxy set in your shell
|
||||
sudo -E pacman -Syu nodejs npm
|
||||
```
|
||||
|
||||
### 📦 Step 2: Install System Dependencies (The Critical Step)
|
||||
**Do not** use `npx playwright install-deps` (it fails on Arch). Instead, install these packages manually. This list includes all the X11, Graphics, and Network libraries required by Chromium, Firefox, and WebKit.
|
||||
|
||||
```bash
|
||||
sudo -E pacman -S --needed \
|
||||
git \
|
||||
nss \
|
||||
nspr \
|
||||
libdrm \
|
||||
alsa-lib \
|
||||
mesa \
|
||||
gtk3 \
|
||||
at-spi2-core \
|
||||
pango \
|
||||
cairo \
|
||||
gdk-pixbuf2 \
|
||||
libx11 \
|
||||
libxcomposite \
|
||||
libxdamage \
|
||||
libxext \
|
||||
libxfixes \
|
||||
libxrandr \
|
||||
libxcursor \
|
||||
libxi \
|
||||
libxrender \
|
||||
libxcb \
|
||||
freetype2 \
|
||||
fontconfig \
|
||||
ffmpeg
|
||||
```
|
||||
|
||||
### 🛠️ Step 3: Initialize Playwright
|
||||
Set up your project and download the browser binaries (these are separate from the system libs above).
|
||||
|
||||
```bash
|
||||
# Create project directory
|
||||
mkdir my-tests && cd my-tests
|
||||
|
||||
# Initialize (Select TypeScript/JavaScript as preferred)
|
||||
npm init playwright@latest
|
||||
|
||||
# If prompted to "Install Playwright browsers", select True.
|
||||
# If you need to install them manually later:
|
||||
npx playwright install
|
||||
```
|
||||
|
||||
### ✅ Step 4: Run Tests
|
||||
You are now ready to run.
|
||||
|
||||
```bash
|
||||
npx playwright test
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### 💡 Troubleshooting Cheat Sheet
|
||||
|
||||
| Issue | Solution |
|
||||
| :------------------------ | :-------------------------------------------------------------------------------- |
|
||||
| **`install-deps` fails** | **Ignore it.** It only supports Ubuntu. Use the `pacman` command in Step 2. |
|
||||
| **`libxxx.so not found`** | You are missing a package. Use `pkgfile libxxx.so` to find the Arch package name. |
|
||||
| **404 Errors (Pacman)** | Your mirrors are out of sync. Run `sudo pacman -Syu` to refresh. |
|
||||
| **Browser won't launch** | Ensure `nspr` and `nss` are installed (included in Step 2). |
|
||||
| **GUI/Headless issues** | If visual mode fails, try `xvfb-run npx playwright test`. |
|
||||
@@ -1,173 +0,0 @@
|
||||
|
||||
To set up **Oh My Posh** with **Zsh** on **Debian 12**, follow these steps to install the necessary components and configure your terminal prompt.
|
||||
|
||||
## Installation Steps
|
||||
|
||||
### 1. Download the Oh My Posh Binary
|
||||
First, you need to download the Oh My Posh binary suitable for Linux. Open your terminal and run the following command:
|
||||
|
||||
```bash
|
||||
sudo wget https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/posh-linux-amd64 -O /usr/local/bin/oh-my-posh
|
||||
```
|
||||
|
||||
### 2. Set Executable Permissions
|
||||
Make the downloaded binary executable:
|
||||
|
||||
```bash
|
||||
sudo chmod +x /usr/local/bin/oh-my-posh
|
||||
```
|
||||
|
||||
### 3. Create a Directory for Themes
|
||||
You need a directory to store your themes. Create it using:
|
||||
|
||||
```bash
|
||||
mkdir -p ~/.poshthemes
|
||||
```
|
||||
|
||||
### 4. Download Themes
|
||||
You can download predefined themes from the Oh My Posh repository. For example, to download the latest themes, run:
|
||||
|
||||
```bash
|
||||
wget https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/themes.zip -O ~/.poshthemes/themes.zip
|
||||
```
|
||||
|
||||
Unzip the downloaded file:
|
||||
|
||||
```bash
|
||||
unzip ~/.poshthemes/themes.zip -d ~/.poshthemes
|
||||
```
|
||||
|
||||
Then, clean up by removing the zip file:
|
||||
|
||||
```bash
|
||||
rm ~/.poshthemes/themes.zip
|
||||
```
|
||||
|
||||
### 5. Update Your Zsh Configuration
|
||||
Now, you need to configure your Zsh shell to use Oh My Posh. Open your `.zshrc` file in a text editor:
|
||||
|
||||
```bash
|
||||
nano ~/.zshrc
|
||||
```
|
||||
|
||||
Add the following line at the end of the file to initialize Oh My Posh with a specific theme (replace `alien` with your preferred theme name):
|
||||
|
||||
```bash
|
||||
eval "$(oh-my-posh --init --shell zsh --config ~/.poshthemes/alien.omp.json)"
|
||||
```
|
||||
|
||||
### 6. Apply Changes
|
||||
After saving and closing the `.zshrc` file, apply the changes by running:
|
||||
|
||||
```bash
|
||||
source ~/.zshrc
|
||||
```
|
||||
|
||||
## Additional Configuration
|
||||
|
||||
### Install a Nerd Font (Optional)
|
||||
For better aesthetics, install a Nerd Font that supports icons used by Oh My Posh. You can download fonts like **Meslo** or **Fira Code** from their respective repositories and install them on your system.
|
||||
|
||||
### Set Terminal Font
|
||||
Finally, ensure that your terminal emulator is configured to use the newly installed Nerd Font for optimal display of icons and symbols.
|
||||
|
||||
By following these steps, you will have successfully set up Oh My Posh with Zsh on Debian 12, enhancing your terminal's appearance and functionality.
|
||||
|
||||
Citations:
|
||||
[1] https://dev.to/karleeov/wsl-arch-setup-for-oh-my-posh-51pa
|
||||
[2] https://www.reddit.com/r/NixOS/comments/1ge1gwn/how_to_set_ohmyposh_settings/
|
||||
[3] https://ohmyposh.dev/docs/installation/linux
|
||||
[4] https://www.librebyte.net/en/cli-en/oh-my-posh-a-beatifull-prompt-for-your-shell/
|
||||
[5] https://www.youtube.com/watch?v=nGHgyPLi7UM
|
||||
[6] https://calebschoepp.com/blog/2021/how-to-setup-oh-my-posh-on-ubuntu/
|
||||
[7] https://www.linux.org/threads/need-help-finalizing-oh-my-posh-bash-terminal.52617/
|
||||
|
||||
|
||||
|
||||
.zshrc
|
||||
```
|
||||
#go lang
|
||||
export GOROOT=/usr/local/go
|
||||
export GOPATH=/home/windy/go-lang
|
||||
export PATH=$PATH:$GOROOT/bin:$GOPATH/bin
|
||||
|
||||
eval "$(oh-my-posh --init --shell zsh --config ~/.poshthemes/powerlevel10k_modern.omp.json)"
|
||||
|
||||
|
||||
[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh
|
||||
|
||||
|
||||
# Zinit setup and plugin management
|
||||
ZINIT_HOME="${XDG_DATA_HOME:-${HOME}/.local/share}/zinit/zinit.git"
|
||||
[ ! -d $ZINIT_HOME ] && mkdir -p "$(dirname $ZINIT_HOME)"
|
||||
[ ! -d $ZINIT_HOME/.git ] && git clone https://github.com/zdharma-continuum/zinit.git "$ZINIT_HOME"
|
||||
source "${ZINIT_HOME}/zinit.zsh"
|
||||
|
||||
# Load essential annexes (non-turbo mode for annex functionality)
|
||||
zinit light-mode for \
|
||||
zdharma-continuum/zinit-annex-as-monitor \
|
||||
zdharma-continuum/zinit-annex-bin-gem-node \
|
||||
zdharma-continuum/zinit-annex-patch-dl \
|
||||
zdharma-continuum/zinit-annex-rust
|
||||
|
||||
# Load Zeno plugin with keybindings
|
||||
zinit ice lucid depth"1" blockf
|
||||
zinit light yuki-yano/zeno.zsh
|
||||
|
||||
if [[ -n $ZENO_LOADED ]]; then
|
||||
bindkey ' ' zeno-auto-snippet
|
||||
bindkey '^m' accept-line
|
||||
bindkey '^i' zeno-completion
|
||||
bindkey '^g' zeno-ghq-cd
|
||||
bindkey '^r' zeno-history-selection
|
||||
bindkey '^x' zeno-insert-snippet
|
||||
fi
|
||||
|
||||
# Load additional Zsh plugins
|
||||
zinit ice wait"0"; zinit light zsh-users/zsh-completions
|
||||
autoload -Uz compinit && compinit
|
||||
zstyle ':completion:*' matcher-list 'm:{a-z}={A-Z}'
|
||||
zstyle ':completion:*:default' menu select=1
|
||||
|
||||
zinit light zsh-users/zsh-syntax-highlighting
|
||||
zinit light zsh-users/zsh-autosuggestions
|
||||
zinit light Aloxaf/fzf-tab
|
||||
|
||||
# FZF configuration
|
||||
zi ice from"gh-r" as"program"
|
||||
zi light junegunn/fzf
|
||||
|
||||
# Auto-suggestions styling
|
||||
ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="fg=244"
|
||||
|
||||
# History settings
|
||||
HISTFILE=~/.zsh-history
|
||||
HISTSIZE=100000
|
||||
SAVEHIST=1000000
|
||||
HISTDUP=erase
|
||||
setopt appendhistory sharehistory hist_ignore_space hist_ignore_all_dups
|
||||
setopt hist_save_no_dups hist_ignore_dups hist_find_no_dups
|
||||
setopt inc_append_history share_history
|
||||
|
||||
# Zsh options for usability
|
||||
setopt AUTO_CD
|
||||
setopt AUTO_PARAM_KEYS
|
||||
|
||||
# Completion and FZF styling
|
||||
zstyle ':completion:*' matcher-list 'm:{a-z}={A-Za-z}'
|
||||
zstyle ':completion:*' list-colors "${(s.:.)LS_COLORS}"
|
||||
zstyle ':completion:*' menu no
|
||||
zstyle ':fzf-tab:complete:cd:*' fzf-preview 'ls --color $realpath'
|
||||
|
||||
# Load additional plugins with default keys
|
||||
zinit pack"default+keys" for fzf
|
||||
|
||||
# Ensure Zinit autocompletion
|
||||
autoload -Uz _zinit
|
||||
(( ${+_comps} )) && _comps[zinit]=_zinit
|
||||
|
||||
# Consolidate PATH with deduplication
|
||||
export PATH=$(echo "/run/current-system/sw/bin:/usr/local/bin:/usr/local/sbin:$PATH" | tr ':' '\n' | awk '!seen[$0]++' | tr '\n' ':' | sed 's/:$//')
|
||||
|
||||
|
||||
```
|
||||
@@ -1,9 +0,0 @@
|
||||
|
||||
## 2023.4.18 尝试
|
||||
小黄瓜原料： 1044克
|
||||
盐： 21.7克
|
||||
糖： 11.7克
|
||||
蒜末
|
||||
姜末
|
||||
蒜苔切碎
|
||||
芝麻
|
||||
@@ -1,9 +0,0 @@
|
||||
|
||||
文明7标准：
|
||||
```
|
||||
7I0EZ-N5HWF-JYIGF
|
||||
```
|
||||
激活码2：
|
||||
```
|
||||
EIFGE-K032P-RQ8BH
|
||||
```
|
||||
@@ -1,6 +0,0 @@
|
||||
|
||||
## lock
|
||||
### 静脉解锁
|
||||
|
||||
|
||||
## door
|
||||
@@ -1,18 +0,0 @@
|
||||
|
||||
|
||||
床边衣柜
|
||||
|
||||
高 38
|
||||
宽 35
|
||||
深 39
|
||||
|
||||
床角衣柜
|
||||
上柜下层：
|
||||
|
||||
宽：69
|
||||
深：56
|
||||
高：27.5
|
||||
隔板深：39.5
|
||||
|
||||
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
|
||||
厨房清洁剂储物盒子
|
||||
```
|
||||
24*24*40
|
||||
```
|
||||
File diff suppressed because it is too large
Load Diff
@@ -1,170 +0,0 @@
|
||||
---
|
||||
title: "在非原生ESIM设备上申请Giffgaff ESIM"
|
||||
source: "https://simonmy.com/posts/giffgaff-esim-apply-without-official-app.html#1-%E7%94%A8%E9%82%AE%E7%AE%B1%E6%B3%A8%E5%86%8C%E4%B8%80%E4%B8%AAgiffgaff%E8%B4%A6%E5%8F%B7"
|
||||
author:
|
||||
- "[[Simon (Yu Ma)]]"
|
||||
published: 2024-10-22
|
||||
created: 2025-09-25
|
||||
description: "Progress is the activity of today and the assurance of tomorrow."
|
||||
tags:
|
||||
- "clippings"
|
||||
---
|
||||
## 背景
|
||||
|
||||
Giffgaff是英国的一家虚拟运营商，其Giffgaff卡适合长期保号使用。Giffgaff原先只提供实体SIM卡，随后开始支持将实体SIM卡转换为esim或者直接购买新的esim。Giffgaff并不提供ESIM的二维码，而是通过Giffgaff APP直接将ESIM配置文件下载到手机中。Giffgaff在申请或更换ESIM时都会检测当前手机是否能够支持ESIM功能，由于国内设备或早期发行的设备不支持ESIM功能，客户端将无法进行申请。本文介绍如何使用抓包请求的方式，直接申请Giffgaff ESIM卡，并获取二维码进行绑定。ESTK/5ber/9esim等均可采用此方案。
|
||||
|
||||
## 操作步骤
|
||||
|
||||
### 1\. 用邮箱注册一个Giffgaff账号
|
||||
|
||||
打开官网注册链接([https://www.giffgaff.com/auth/register](https://www.giffgaff.com/auth/register))，进行常规注册。特别需要注意的地方我截图放在下面，没有提到的步骤就按照常规进行填写。
|
||||
|
||||
安全提醒
|
||||
|
||||
注意！这一步的邮箱是安全邮箱，一定要自己可信的邮箱来注册，后续经常要用来做验证，不要使用临时邮箱或不安全的邮箱。
|
||||
|
||||
1. 填写安全邮箱
|
||||
2. 邮箱收到验证码后，填写进行下一步
|
||||
3. 密码符合要求填写就好，一定要记住，后续要频繁使用
|
||||
4. 选择 `No Thanks` ，生日可不写
|
||||
5. 当你看到 `Welcome` 的时候，说明已经注册成功，点击按钮回到 `我的Giffgaff`
|
||||
6. 不要关闭这个窗口，后续要用！
|
||||
|
||||
[](https://image.simonmy.com/file/1729607150231_image.png) [](https://image.simonmy.com/file/1729607245363_image.png) [](https://image.simonmy.com/file/1729607267059_image.png)
|
||||
|
||||
特别提醒
|
||||
|
||||
后续登录都是使用 `我的Giffgaff` 中显示的用户名登录，不会使用邮箱。 邮箱是用来收验证码
|
||||
|
||||
### 2\. 下载Postman客户端
|
||||
|
||||
通过官方网站下载Postman客户端，首次运行会提示并注册并登录Postman，如果你自己有账号可直接登录。切记，这里一定要注册登录，因为后续要依赖Postman的高级功能，不登录无法使用。
|
||||
|
||||
特别提醒
|
||||
|
||||
如果你仅希望临时注册一个账号并不暴露自己的邮箱，可以使用下面的网站快速获得临时邮箱，完成接验证码或确认邮件。 [https://fakemail.ink/](https://fakemail.ink/) 和 [https://fakemail.chat/](https://fakemail.chat/)
|
||||
|
||||
下载地址：https://www.postman.com/downloads/
|
||||
|
||||
[](https://image.simonmy.com/file/1729606034895_image.png) [](https://image.simonmy.com/file/1729606121802_image.png) [](https://image.simonmy.com/file/1729606169022_image.png)
|
||||
|
||||
跳回软件后的部分，自己随便填写就好，没有什么要特别注意的了。
|
||||
|
||||
### 3\. 导入Postman脚本
|
||||
|
||||
打开软件后，直接点击Import按键，粘贴脚本地址到图示位置即可。
|
||||
|
||||
脚本地址：
|
||||
|
||||
```
|
||||
https://assets.simonmy.com/2025-02-25/pNpfad.json
|
||||
```
|
||||
|
||||
备用脚本地址：
|
||||
|
||||
```
|
||||
https://image.simonmy.com/file/1740496037998_Giffgaff-swap-esim_20250225a.json
|
||||
```
|
||||
|
||||
[](https://image.simonmy.com/file/1729606423680_image.png) [](https://image.simonmy.com/file/1729606546311_image.png)
|
||||
|
||||
### 4\. Postman登录账号获取Token
|
||||
|
||||
提示：这个步骤后续还要重复操作，下文中提到重新执行 `Postman登录账号`, 具体过程执行以下步骤即可
|
||||
|
||||
要通过HTTP请求的方式直接与Giffgaff服务器通讯，首先需要获取一个Access Token。向服务器发送的请求中需要包含这个Token来验证用户身份。 具体步骤如下：
|
||||
|
||||
1. 选中这一组脚本后，依次点击 `Authorization` - `滚动条划到最后` - `Clear cookies` - `Get New Access Token`
|
||||
2. 弹窗后输入用户名和密码，注意这里的用户名是 `我的Giffgaff` 中的用户名，并不是邮箱
|
||||
3. 邮箱接收验证码，提交登录
|
||||
4. 稍等一会，Postman有一个弹框，点击按钮 `Use Token`
|
||||
|
||||
[](https://image.simonmy.com/file/1729608044731_image.png) [](https://image.simonmy.com/file/1729608249229_image.png) [](https://image.simonmy.com/file/1729608325194_image.png)
|
||||
|
||||
### 5\. 执行脚本 - 邮箱二次确认，获取签名
|
||||
|
||||
脚本中的前三步骤我合并在一起描述，本步骤是为了二次验证，获取签名。 具体步骤如下：
|
||||
|
||||
1. 点击 `發送認證郵件 Send Email Verification` ，并发送请求
|
||||
2. 安全邮箱收到验证码后，填写到 `檢查郵件認證碼 Verify Email code` 的 `Body` ，并且发送请求
|
||||
3. 点击 `取得會員資訊 Get Member` ，并发送请求
|
||||
|
||||
[](https://image.simonmy.com/file/1729609371482_image.png) [](https://image.simonmy.com/file/1729609494858_image.png) [](https://image.simonmy.com/file/1729609604305_image.png)
|
||||
|
||||
### 6\. 执行脚本 - 申请ESIM卡
|
||||
|
||||
1. 点击 `申請 SIM卡 Reserve SIM` 发送请求
|
||||
2. 注意返回体里面的 `esim` 部分，这一块要复制保存下来
|
||||
[](https://image.simonmy.com/file/1729615482105_image.png)
|
||||
|
||||
### 7\. 通过官方APP - 激活ESIM卡并完成充值
|
||||
|
||||
1. 通过 `Play商店` 或 `App Store` 下载 Giffgaff
|
||||
2. 使用用户名(注意不是邮箱)和密码 登录官方App，同样邮箱会收到验证码，正常验证即可
|
||||
3. 登录后选择选择 `SIM Card` 下的 `Activate your SIM card`
|
||||
4. 输入上一步获取的 `activationCode` 6位激活码，提交激活
|
||||
5. 页面拉到最下面，选择 `I don't want a plan` 付费方案
|
||||
|
||||
[](https://image.simonmy.com/file/1734447150223_image.png) [](https://image.simonmy.com/file/1734447173642_image.png) [](https://image.simonmy.com/file/1734447218968_image.png)
|
||||
|
||||
1. 选择最小充值金额 €10， 再次提交继续。
|
||||
2. 新增一个付款方式，并选择 `Add Card`, 这里可以使用国内发行的Visa和Master Card。 并填写账单信息，用地址生成器弄一个英国的地址。或者你写中国自己的地址也可以，并没有非常强的要求。
|
||||
3. 勾选协议授权，并提交。
|
||||
4. 稍等片刻你应该就可以看到自己的手机号码了
|
||||
|
||||
[](https://image.simonmy.com/file/1734447264041_image.png) [](https://image.simonmy.com/file/1734447318908_image.png) [](https://image.simonmy.com/file/1734447381690_image.png)
|
||||
|
||||
注意：此时此刻你是无法进行安装ESIM的，回到电脑端Postman窗口
|
||||
|
||||
### 8\. 下载ESIM，生成二维码
|
||||
|
||||
由于我的卡是之前操作过的，所以就没有办法继续演示截图。后续就是顺序执行剩下的脚本，我把步骤列在这里。
|
||||
|
||||
特别提醒
|
||||
|
||||
不要去执行 `申請交換eSIM Swap SIM` ，这个步骤一定要跳过！！！
|
||||
|
||||
1. 执行脚本 `取得eSIM Get ESIMs` ， 获取当前可以下载的ESIM信息
|
||||
2. 执行脚本 `取得eSIM下載碼 Get ESIM Token` ， 获取ESIM LPA信息。如果你知道LPA怎么用，下面扫码的步骤可不执行。
|
||||
3. 执行脚本 `產生QRCode Get ESIM QRCode`
|
||||
|
||||
[](https://image.simonmy.com/file/1729611969794_image.png) [](https://image.simonmy.com/file/1729612014146_image.png) [](https://image.simonmy.com/file/1729612038215_image.png)
|
||||
|
||||
### 9\. 导入ESIM, 等待服务器激活
|
||||
|
||||
使用支持eSIM的手机、EasyUICC或者其他第三方的eSIM管理工具扫描这个二维码，即可下载并安装eSIM配置文件
|
||||
|
||||
### 10\. 更换ESIM卡(SIM换ESIM同理)
|
||||
|
||||
特别提醒
|
||||
|
||||
首次申请不需要关注这个过程，此过程是帮助有换卡需求的小伙伴
|
||||
|
||||
近期Giffgaff API更新，很多小伙伴在使用脚本时都出现了 `Required header 'X-GG-MFA-REF' is not present.`异常。 如果你也遇到了这个问题，请按照下面的步骤解决。
|
||||
|
||||
1. 执行上述步骤的 `1-6` ，你会在Postman中获得一个状态为 `RESERVED` 的ESIM卡， 请如图，暂时保存这个卡的所有信息，尤其是 `activationCode` 和 `ssn` ，Postman不要关闭，后续有用！！！
|
||||
2. 登录并打开官网个人信息页([https://www.giffgaff.com/profile/details](https://www.giffgaff.com/profile/details))
|
||||
3. 找到SIM Card - Replace my SIM 这个Tab， 点击Open - Activate your SIM, 如图
|
||||
4. 进入激活页面后，填写你上述的 `activationCode` ，点击 `Active`
|
||||
5. 点击下面的确认按钮，跳转页面后再次点击确认，网页会跳转到首页并提示成功。
|
||||
6. 回到Postman, 执行上述第8步
|
||||
|
||||
> 执行脚本 `取得eSIM Get ESIMs` ， 获取当前可以下载的ESIM信息
|
||||
> 执行脚本 `取得eSIM下載碼 Get ESIM Token` ， 获取ESIM LPA信息。如果你知道LPA怎么用，下面扫码的步骤可不执行。
|
||||
> 执行脚本 `產生QRCode Get ESIM QRCode`
|
||||
|
||||
[](https://image.simonmy.com/file/1753876221141_GvRPUJ.png) [](https://image.simonmy.com/file/1753876440224_J0BMEg.png) [](https://image.simonmy.com/file/1753876538880_vs8rh3.png) [](https://image.simonmy.com/file/1753876624730_gQ0myu.png)
|
||||
|
||||
### 11\. 其他
|
||||
|
||||
如果你在过程中遇到了问题，可以在下方留言或通过 [https://t.me/Charpati](https://t.me/Charpati) 寻求帮助
|
||||
寻求帮助前，请一定准备好下面材料和设备：
|
||||
|
||||
1. 一个可用的安全邮箱
|
||||
2. 一个可支付的银行卡
|
||||
3. 一个支持ESIM的设备(可以是estk、5ber、9esim等)
|
||||
4. 当前遇到的问题
|
||||
|
||||
## 参考文章
|
||||
|
||||
1. [如何将GiffGaff sim卡转换为esim](https://azhu.site/posts/1015/)
|
||||
@@ -1,9 +0,0 @@
|
||||
|
||||
|
||||
【联想服务】尊敬的moto用户，您好：
|
||||
感谢致电400热线，Moto手机双清的方法如下：
|
||||
1、在关机状态下，同时按住开机键和音量减键3S左右，屏幕出现机器人倒地界面后松开，
|
||||
2、按音量减键直到右上角显示RECOVERY MODE，
|
||||
3、按电源键确认进入recovery，此时手机会出现moto开机logo，耐心等待一会，手机屏幕会显示机器人倒地界面，显示No command（无命令），此时按住电源键，然后短按一下音量加键，即可显示recovery菜单，
|
||||
4、在recovery菜单界面按音量减键移动到光标到wipe data/factory reset，按电源键确认，然后按音量减键选择Factory data reset，再按电源键确认即可开始清除，
|
||||
5、清除完毕后屏幕上再次显示recovery菜单，左下角显示data wipe complete，到此已经完成双清的操作，手机中包括设置的锁屏密码、个人资料、内部存储设备存储的照片音乐文档等数据均已被清除，选择reboot system now选项后按电源键确认即可重启手机。
|
||||
@@ -1,4 +0,0 @@
|
||||
List:
|
||||
- New application features and menu
|
||||
- Focus mode for the current line
|
||||
- Focus UI for writing
|
||||
@@ -1,365 +0,0 @@
|
||||
/* Special Font */
|
||||
body, p {
|
||||
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
|
||||
}
|
||||
|
||||
.cm-s-obsidian {
|
||||
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
.editor {
|
||||
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
.markdown-preview-view code {
|
||||
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
.preview {
|
||||
font-family: "Dank Mono",'Inter', -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Microsoft YaHei Light", sans-serif;
|
||||
font-size: 16px;
|
||||
}
|
||||
|
||||
/* Scrollbar */
|
||||
::-webkit-scrollbar {
|
||||
background-color: transparent;
|
||||
}
|
||||
|
||||
/**/
|
||||
/* Editor Section */
|
||||
/**/
|
||||
/* Line size */
|
||||
.cm-s-obsidian pre.HyperMD-header {
|
||||
line-height: 1!important;
|
||||
}
|
||||
|
||||
/* Selection */
|
||||
.theme-light {
|
||||
--text-selection: rgba(112, 93, 207, 0.5);
|
||||
}
|
||||
|
||||
.theme-dark {
|
||||
--text-selection: rgba(112, 93, 207, 0.5);
|
||||
}
|
||||
|
||||
::selection {
|
||||
background-color: #705dcf;
|
||||
color: white;
|
||||
}
|
||||
|
||||
/* Title */
|
||||
/* Current main pane */
|
||||
.view-header-title {
|
||||
color: #705dcf;
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
.workspace-leaf.mod-active .view-header {
|
||||
text-align: center;
|
||||
}
|
||||
/* Other pane */
|
||||
.workspace-leaf-header-title-container {
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
/* Headers */
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-1.cm-header.cm-header-1 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-2.cm-header.cm-header-2 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-3.cm-header.cm-header-3 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-4.cm-header.cm-header-4 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-5.cm-header.cm-header-5 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
span.cm-formatting.cm-formatting-header.cm-formatting-header-6.cm-header.cm-header-6 {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
/* Header folder icon */
|
||||
.CodeMirror-foldgutter-open, .CodeMirror-foldgutter-folded {
|
||||
color: #3e3471;
|
||||
}
|
||||
|
||||
.CodeMirror-foldgutter-open, .CodeMirror-foldgutter-folded {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
/* Cursor */
|
||||
.cm-fat-cursor .CodeMirror-cursor {
|
||||
background: #3e3471;
|
||||
}
|
||||
|
||||
.cm-animate-fat-cursor {
|
||||
background-color: #3e3471;
|
||||
}
|
||||
|
||||
/* Selection in popup ([[]] autocomplete)*/
|
||||
.suggestion-item.is-selected {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-light .suggestion-shortcut {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
/* Inner and Outer links */
|
||||
.cm-url {
|
||||
color: lightblue!important;
|
||||
}
|
||||
|
||||
.markdown-highlighting .internal-link .cl-underlined-text {
|
||||
color: var(--text-accent)!important;
|
||||
}
|
||||
|
||||
.markdown-highlighting .link .cl-underlined-text {
|
||||
color: lightblue!important;
|
||||
}
|
||||
|
||||
/* Blockquote */
|
||||
.preview blockquote {
|
||||
background-color: var(--background-modifier-border);
|
||||
border: 1px solid var(--text-muted);
|
||||
}
|
||||
|
||||
/* Highlights and Bold */
|
||||
strong {
|
||||
font-size: larger;
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
mark {
|
||||
background-color: darkgoldenrod;
|
||||
}
|
||||
|
||||
.markdown-highlighting .tag {
|
||||
color: var(--text-accent)!important;
|
||||
}
|
||||
|
||||
/* Tables */
|
||||
.markdown-preview-view th {
|
||||
background-color: #3e3471;
|
||||
color: white
|
||||
}
|
||||
|
||||
.cm-s-obsidian pre.HyperMD-table-row span.cm-hmd-table-sep {
|
||||
color: unset;
|
||||
}
|
||||
|
||||
.cm-s-obsidian pre.HyperMD-table-row-1 > span {
|
||||
color: unset;
|
||||
}
|
||||
|
||||
/* Status bar */
|
||||
.theme-dark .status-bar-item {
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-light .status-bar-item {
|
||||
color: black;
|
||||
}
|
||||
|
||||
/**/
|
||||
/* Preview section */
|
||||
/**/
|
||||
/* Centered preview */
|
||||
.markdown-preview-view
|
||||
{
|
||||
padding-left: 10% !important;
|
||||
padding-right: 10% !important;
|
||||
}
|
||||
|
||||
.markdown-embed-title {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
.markdown-preview-view .markdown-embed {
|
||||
background-color: var(--background-primary-alt);
|
||||
margin-top: 0.5rem;
|
||||
margin-bottom: 0.5rem;
|
||||
}
|
||||
|
||||
.markdown-preview-view .internal-link {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
.markdown-preview-view a {
|
||||
color: lightblue;
|
||||
}
|
||||
|
||||
/**/
|
||||
/* Side panel section */
|
||||
/**/
|
||||
/* Plugin Title and Description */
|
||||
.plugin-name {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
.plugin-description {
|
||||
color: var(--text-normal)
|
||||
}
|
||||
|
||||
/* Files title and Buttons */
|
||||
.nav-file-title-content, .nav-folder-title-content {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
.nav-action-button {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
/* File explorer navigation selection */
|
||||
.nav-file.is-active > .nav-file-title, .nav-file.is-active > .nav-folder-title, .nav-file.is-active > .nav-folder-collapse-indicator, .nav-folder.is-active > .nav-file-title, .nav-folder.is-active > .nav-folder-title, .nav-folder.is-active > .nav-folder-collapse-indicator {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
body:not(.is-grabbing) .nav-file-title:hover, body:not(.is-grabbing) .nav-folder-title:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.nav-file-title-content, .nav-folder-title-content {
|
||||
color:unset;
|
||||
}
|
||||
|
||||
.nav-folder.mod-root > .nav-file-title:hover, .nav-folder.mod-root > .nav-folder-title:hover {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
body:not(.is-grabbing) .nav-file-title:hover .nav-folder-collapse-indicator, body:not(.is-grabbing) .nav-folder-title:hover .nav-folder-collapse-indicator {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.nav-file-title, .nav-folder-title, .nav-folder-collapse-indicator {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
/* File explorer menu*/
|
||||
.menu-item:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
/* Backlinks Color and Text */
|
||||
.search-result-file-matched-text {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.search-result-file-title {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
.search-result-file-matches {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
.search-result-file-title:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.search-result-file-match:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
/* Folder arrow */
|
||||
.nav-folder.is-collapsed .nav-folder-collapse-indicator {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
.nav-folder-collapse-indicator {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
/* Tag Selection */
|
||||
.tag-pane-tag:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-light .tag-pane-tag-count {
|
||||
color: var(--text-normal)
|
||||
}
|
||||
|
||||
/* Title */
|
||||
.side-dock-title {
|
||||
color: #705dcf;
|
||||
}
|
||||
|
||||
/* Ribon */
|
||||
.side-dock-ribbon {
|
||||
background-color: #3e3471!important;
|
||||
color: var(--text-muted)
|
||||
}
|
||||
|
||||
.side-dock-ribbon-tab, .side-dock-ribbon-action {
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-dark .side-dock-ribbon-tab.is-active {
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-dark .side-dock-ribbon-tab.is-before-active {
|
||||
color: white;
|
||||
}
|
||||
|
||||
.theme-light .side-dock-ribbon-tab.is-active {
|
||||
color: var(--text-normal);
|
||||
}
|
||||
|
||||
.theme-light .side-dock-ribbon-tab.is-before-active {
|
||||
color: white;
|
||||
}
|
||||
|
||||
.side-dock-ribbon-tab-inner {
|
||||
color: unset;
|
||||
}
|
||||
|
||||
.side-dock-ribbon-before.is-before-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-after.is-after-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-tab.is-before-active .side-dock-ribbon-tab-inner, .side-dock-ribbon-tab.is-after-active .side-dock-ribbon-tab-inner {
|
||||
background-color: #3e3471;
|
||||
}
|
||||
|
||||
.side-dock-ribbon-tab, .side-dock-ribbon-before, .side-dock-ribbon-after, .side-dock-ribbon-tab-inner {
|
||||
transition: none;
|
||||
}
|
||||
|
||||
/**/
|
||||
/* Settings panel Section */
|
||||
/**/
|
||||
.vertical-tab-nav-item.is-active {
|
||||
background-color: #3e3471;
|
||||
color:white;
|
||||
}
|
||||
|
||||
.horizontal-tab-nav-item:hover, .vertical-tab-nav-item:hover {
|
||||
background-color: #3e3471;
|
||||
color: white;
|
||||
}
|
||||
|
||||
.vertical-tab-nav-item.is-active {
|
||||
background-color: #3e3471;
|
||||
}
|
||||
|
||||
.vertical-tab-nav-item.is-active {
|
||||
border-left-color: #3e3471;
|
||||
}
|
||||
@@ -1,41 +0,0 @@
|
||||
# The Methodology
|
||||
The P.A.R.A system is surprisingly simple at first glance but very powerful when applied. At its core, it's just a four folder wide hierarchy with four-layer deeps, starting with those four root folders:
|
||||
|
||||
1. Projects
|
||||
2. Areas
|
||||
3. Resources
|
||||
4. Archive
|
||||
|
||||
From there, each of the roots is allowed one sub-folder level and then notes. That's how the four levels deep work: App (1) -> `1. Projects` (2) -> P.A.R.A. Demo Vault (3) -> Methodology (4). The reason for this is to keep it manageable and easy to remember and navigate. That restriction was initially because of Evernote limitation, but it turns out to have some serendipity potential. By putting all your notes from similar "zone" and actionability together, you end up with many serendipitous findings of new related notes and ideas.
|
||||
|
||||
Just those root folders and their children, the system can contain everything most people needs for their notes and files. This taxonomy works because you don't split things based on categories but actionability and areas of your life. So now, let's define those roots to help see how it works.
|
||||
|
||||
## Definition
|
||||
1. Projects: *Every current project that is actionable with its notes, files, artifacts*
|
||||
- If you have a project that requires notes or files, it should have a folder in 1. Projects.
|
||||
- Since this folder is for projects you are working on _right now_, it's the most actionable and probably where you will spend most of your time.
|
||||
2. Areas: *Zone of responsibility with standard to uphold over long periods*, parent, animals, management, coding, house.
|
||||
- Areas are **the personal** bucket of your life for important things that don't have an end date. You won't ever "stop" working on your health; for example, it's a constant ongoing thing.
|
||||
- While areas can (and often do) generate projects, they are not linked since it's already intuitive which areas a project comes from, so there's no need to create an explicit link between, for example, the "Server maintenance" project and the "Sysadmin" area.
|
||||
- Finally, because they are personal, areas contain information you wrote for _yourself only_ about those areas in your life. Which is opposite to 3. Resources.
|
||||
3. Resources: *Zone of interest for various topics that don't require standard/responsibility*, game, cooking, productivity, technology.
|
||||
- Resources are **generally helpful for others**, not just you. For example, if someone was to ask you for information about cooking, you could zip that folder and send it to them.
|
||||
- The folders in there will very often reflect your various interests, what you're curious about and want to learn more about.
|
||||
- They are not necessarily actual "resources" as in PDF, Pictures, etc. they can also be notes about those subjects
|
||||
4. Archives: *Where stuff from all the other category become unused*, finished project, change of responsibility, etc.
|
||||
- This folder will be where you put things you won't need for a while, as the name suggests. For the most part, something in there won't be seen for a time, and that's why it has the lowest actionability, but sometimes a new project could use things in there, or a change of areas might mean you need to get stuff out of there.
|
||||
- For example, you have lots of notes on living with a pet in a small apartment, and then you move to a new bigger one. You could move all those to the archive if one day you have to go back to a small apartment again take them out.
|
||||
|
||||
## Setup
|
||||
The setup for it is pretty simple, create root folders for each category, like in this sandbox. From there, move all of your current notes into `4. Archives` as is with the same existing hierarchy (remember it's not deleted 😉). Then create one folder for each of your current projects you're working on in `1. Projects` (remember only one sub-folder to stay four levels deep). For `2. Areas`, if you already know some of them, you can create the folders already, but try not to have too many empty folders. Finally, `3. Resources`, you want to stay empty for now unless you already captured things that could go in it. The idea is that each time you go into `4. Archives` to take one of the "old" notes or files, you then move it to the right spot in the new taxonomy. Doing it this way will highlight the most used notes, and what's left behind can stay in Archive until it's finally used (or not).
|
||||
|
||||
Once you have the folder hierarchy done, you want to copy it across all your other systems; that is where P.A.R.A. starts to shine. You want to have the same hierarchy for your local files on your computer, in your notes, in your Dropbox/Google Drive/iCloud, and everywhere else you have to keep information. Doing that will make it very quick and easy to find things you might need for work or something in the same zone across all your apps. For this reason, the more system you integrate the taxonomy into, the easier finding things will be.
|
||||
|
||||
### Setup tips:
|
||||
- If a note (or a file) can go into two different folders, you put it in the folder where you will **_most likely need it next_** since folders are based on actionability, and it will get moved anyway in the flow of things.
|
||||
- You can also have the "same" folder in 2 different roots. For example, `2. Areas/Health` and `3. Resources/Health` the first one is **_your_** health notes and the other **general** health-related notes.
|
||||
- Remember, you do **_not_** want to sort all your current notes and files and put them in the new folder, put them all in the Archive as is, and then move them out as you use them.
|
||||
- You do **_not_** have to do every single folder for your local files and cloud service; create the sub-folders are you need them, **_but_** you need to have one complete setup, most likely in your notes, to act as the primary reference for the others.
|
||||
|
||||
|
||||
# Next stop [[Workflows]]
|
||||
@@ -1,16 +0,0 @@
|
||||
## Start here
|
||||
- General how-this-work
|
||||
- What to expect
|
||||
- How to start
|
||||
## Definition
|
||||
- ![[PARA Notes#Definitions]]
|
||||
## Methodology
|
||||
- Actionnability
|
||||
- Fluidity
|
||||
- Project based
|
||||
- Constraint
|
||||
## Workflow
|
||||
- ![[PARA Notes#Workflow]]
|
||||
## Next steps
|
||||
- Tiago's blog
|
||||
- Discord
|
||||
@@ -1,39 +0,0 @@
|
||||
# PKM Content Organization - Decision Note
|
||||
|
||||
## Analysis (2025-12-29)
|
||||
|
||||
After reviewing both locations containing PARA methodology content:
|
||||
- **[300-resources/Personal Knowledge Management](300-resources/Personal Knowledge Management)** - 8 files (course notes, references, essays)
|
||||
- **[100-project/Personal/PKM/PARA](100-project/Personal/PKM/PARA)** - 3 files (implementation guide)
|
||||
|
||||
## Decision: Keep Current Structure
|
||||
|
||||
**Rationale:**
|
||||
1. **Different purposes, complementary content:**
|
||||
- `300-resources/PKM/` contains **source material** from BASB courses, external essays, and learning references
|
||||
- `100-project/PKM/PARA/` contains **implementation documentation** specific to this vault's setup
|
||||
|
||||
2. **PARA principle alignment:**
|
||||
- Resources = generally useful reference material (course notes, methodology explanations)
|
||||
- Projects = active work on implementing/customizing the system
|
||||
|
||||
3. **Content breakdown:**
|
||||
- **300-resources/PKM/** (Reference material):
|
||||
- BASB Class 7 & 8 notes (course content)
|
||||
- PARA Notes.md & PARA Notes from class.md (methodology reference)
|
||||
- Gregory Gundersen essay (writing philosophy)
|
||||
- Dickens deep work (anecdote)
|
||||
- Images.md (visual references)
|
||||
|
||||
- **100-project/PKM/PARA/** (Implementation):
|
||||
- Methodology.md (how to apply in Obsidian)
|
||||
- Workflows.md (practical examples for this vault)
|
||||
- Outline.md (project plan)
|
||||
|
||||
## Cleanup Actions Taken
|
||||
|
||||
✅ Moved arc42 from `300-resources/PKM/` to `300-resources/Development/Architecture/` (was misplaced)
|
||||
|
||||
## Recommendation
|
||||
|
||||
No merge needed. The two locations serve distinct purposes and should remain separate. If PKM project becomes inactive, move implementation docs to `200-area/Personal Development/` (ongoing learning responsibility) and keep course references in `300-resources/`.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user