From 4e3a1e2d39856954f771ab555ae24e386ef8168b Mon Sep 17 00:00:00 2001
From: forgejo-actions
Date: Mon, 16 Mar 2026 01:00:55 +0000
Subject: chore: update webmentions
---
data/webmentions.json | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 88 insertions(+)
(limited to 'data')
diff --git a/data/webmentions.json b/data/webmentions.json
index 6497e284..0cc6bce2 100644
--- a/data/webmentions.json
+++ b/data/webmentions.json
@@ -12813,5 +12813,93 @@
]
}
}
+ },
+ {
+ "webmention": {
+ "source": "https://brid.gy/comment/mastodon/@eltrac@akk.eltr.ac/B4HpVNxVYRytNGP2Bs/B4IYaTbmTO3IHV2eq8",
+ "target": "https://www.geedea.pro/weekly/72/",
+ "modified": 1773622772915
+ },
+ "microformats": {
+ "type": [
+ "h-entry"
+ ],
+ "properties": {
+ "uid": [
+ "https://myce.li/notes/ajw0ljv0plk0005f"
+ ],
+ "in-reply-to": [
+ "https://akk.eltr.ac/web/statuses/B4HpVNxVYRytNGP2Bs",
+ "https://www.geedea.pro/weekly/72/",
+ "tag:akk.eltr.ac,2013:B4HpVNxVYRytNGP2Bs"
+ ],
+ "author": [
+ {
+ "type": [
+ "h-card"
+ ],
+ "value": "Chlorine chlorine",
+ "properties": {
+ "uid": [
+ "tag:myce.li,2013:chlorine"
+ ],
+ "numeric-id": [
+ "B2SrMYpnmub1YtehAu"
+ ],
+ "name": [
+ "Chlorine"
+ ],
+ "nickname": [
+ "chlorine"
+ ],
+ "photo": [
+ "https://assets.myce.li/media/3ccc1ee7-febc-4f3e-9211-f9604326e403.webp"
+ ],
+ "url": [
+ "https://myce.li/@chlorine",
+ "https://chlo.is/",
+ "https://src.chlo.is/chlorine",
+ "https://codeberg.org/chlorine",
+ "https://akk.eltr.ac/@chlorine"
+ ]
+ }
+ }
+ ],
+ "name": [
+ "@eltrac 你们是怎么忍受 #+BEGIN_SRC #+END_SRC 这种写法的? 实不相瞒,我也觉得这种写法有些繁琐。所以一般直接用 @eltrac
\n\n 你们是怎么忍受 #+BEGIN_SRC #+END_SRC 这种写法的?
\n
\n实不相瞒,我也觉得这种写法有些繁琐。所以一般直接用 <s 或者两个反引号作为 trigger 展开。
\n\n 标准化是好事,但拓展性差也是问题。
\n
\n我没试着扩展过 Org mode 语法,但我想是完全可以扩展的,虽然我目前只试过扩展块语法(就是那个 ^#\\+BEGIN_([A-Z]+)$。另外……实不相瞒,我不太理解高亮标记在何时是必不可缺的。
",
+ "text": "@eltrac 你们是怎么忍受 #+BEGIN_SRC #+END_SRC 这种写法的? 实不相瞒,我也觉得这种写法有些繁琐。所以一般直接用