Slack archive

cofacts

Month: 2022-06

2022-06-01

mrorz 15:16:15
我在撈 chatbot 過去收到的圖片的時候

撈到這張，覺得很有趣 w
https://github.com/cofacts/media-manager/blob/6528c7929a2d7d0ee81c7f74483b4b68e42aa726/test/fixtures/animated.gif
話說對手出界這樣有算得分嗎

2022-06-02

cai 15:35:46
https://cofacts.tw/article/3u75jn29hsvv7
https://www.tiktok.com/@leader_10011010/video/7098623431654100251 下方留言有寫課文為林宜澐〈午後〉
可能要去圖書館挖才找得到小說全文

TikTok

抱歉原諒我的笑聲 #國文老師 #罵髒話

@leader_10011010 抱歉原諒我的笑聲 #國文老師 #罵髒話 ♬ 原聲 - 牛奶領袖 - 領袖

https://culture.hccc.gov.tw/zh-tw/archives/detail/character-2505
> 林宜澐的創作類型包含小說以及散文，題材大多以故鄉花蓮為出發點，擅長以喜、鬧劇的方式書寫小說，內容充滿對於政治時事的嘲諷批判，展現出個人的寫作魅力與洞察力
感覺適合影劇改編(錯棚)
學生感覺很興奮wwwwww
但是那小說反映的是市井小民生活
左下角 logo 是高立圖書公司
大學的教科書
對耶這不是國中小的那些出版社
而高立官網也說是做大專院校中英文教科書出版
大一國文 或者 通識教小說寫作吧
應該是呢
「政府並無制定大專院校的課綱，大學課程為各校系自行安排，這點有讀過大學的都知道」這樣回會不會太嗆（欸
好想要私訊問原作者確認是否為大一國文或通識喔
但我不知道 tiktok 是不是有私訊功能
畢竟我連帳號都沒有 lol
你如果要問，可以寫信去問那位老師XD 有公務信箱
大感謝 m(_ _)m
原來這個 meet URL 可以找得到課綱
是說「四應外一」
是應用外語系一年級的課程的意思嗎（也就是大一國文）
那那個「四」是什麼
四技吧?
感謝 @iacmai
先用簡單的資料寫一版回應了
我沒想到用meet網址去找，我是直接用作品名稱+國文 去找到的
變形？fb還沒查到，不能確認是否同影片
https://cofacts.tw/article/36fs79offnukx
https://cofacts.tw/article/wzk2owsprd8b

原始tiktok 的影片變成私密帳號
見鬼，wayback machine 存檔也失效了
cai 15:35:46
https://cofacts.tw/article/3u75jn29hsvv7
https://www.tiktok.com/@leader_10011010/video/7098623431654100251 下方留言有寫課文為林宜澐〈午後〉
可能要去圖書館挖才找得到小說全文
https://culture.hccc.gov.tw/zh-tw/archives/detail/character-2505
> 林宜澐的創作類型包含小說以及散文，題材大多以故鄉花蓮為出發點，擅長以喜、鬧劇的方式書寫小說，內容充滿對於政治時事的嘲諷批判，展現出個人的寫作魅力與洞察力
感覺適合影劇改編(錯棚)
學生感覺很興奮wwwwww
但是那小說反映的是市井小民生活
左下角 logo 是高立圖書公司
大學的教科書
對耶這不是國中小的那些出版社
而高立官網也說是做大專院校中英文教科書出版
大一國文 或者 通識教小說寫作吧
應該是呢
「政府並無制定大專院校的課綱，大學課程為各校系自行安排，這點有讀過大學的都知道」這樣回會不會太嗆（欸
好想要私訊問原作者確認是否為大一國文或通識喔
但我不知道 tiktok 是不是有私訊功能
畢竟我連帳號都沒有 lol
你如果要問，可以寫信去問那位老師XD 有公務信箱
大感謝 m(_ _)m
原來這個 meet URL 可以找得到課綱
是說「四應外一」
是應用外語系一年級的課程的意思嗎（也就是大一國文）
那那個「四」是什麼
四技吧?
感謝 @iacmai
先用簡單的資料寫一版回應了
我沒想到用meet網址去找，我是直接用作品名稱+國文 去找到的
變形？fb還沒查到，不能確認是否同影片
https://cofacts.tw/article/36fs79offnukx
https://cofacts.tw/article/wzk2owsprd8b

原始tiktok 的影片變成私密帳號
見鬼，wayback machine 存檔也失效了

2022-06-04

2022-06-05

2022-06-06

2022-06-07

9heich 01:30:03
@9heich has joined the channel

2022-06-08

cai 13:06:18
https://cofacts.tw/article/lkfysmlqry8 2021年的勸世三姊妹又被拿出來講了
感謝回報，拿出了舊回應擋著
www.facebook.com/page/175344503895/search/?q=勸世三姊妹 有後續啦
去年底正式演出的版本不知道改成怎樣了，地址應該有改掉，只是網路流傳的應該還是舊版本
好像還是讀劇音樂會形式 XD
cai 13:06:18
https://cofacts.tw/article/lkfysmlqry8 2021年的勸世三姊妹又被拿出來講了
感謝回報，拿出了舊回應擋著
www.facebook.com/page/175344503895/search/?q=勸世三姊妹 有後續啦
去年底正式演出的版本不知道改成怎樣了，地址應該有改掉，只是網路流傳的應該還是舊版本
好像還是讀劇音樂會形式 XD
cai 13:43:29
最近的惡作劇連結有傑夫殺手，會強制全螢幕+聲光，點連結前要注意
cai 13:43:29
最近的惡作劇連結有傑夫殺手，會強制全螢幕+聲光，點連結前要注意
👽 2

2022-06-11

2022-06-13

github2 14:44:45

<https://github.com/cofacts/media-manager/pull/3|#3 Publish to npm>

不知怎的，這個 Github action 好像一定要進 main branch 之後才偵測得到 https://github.community/t/workflow-dispatch-workflow-not-showing-in-actions-tab/130088/39

這樣一來就要 merge 才能測了呢 >“<
如果大家沒問題的話我下午就 merge media-manager 的 PR 們唷
我先用 CLI 發布一個版本來讓 rumors-api 可以測過
所以還可以 review 一下 media-manager~
https://www.npmjs.com/package/@cofacts/media-manager
github2 14:44:45

<https://github.com/cofacts/media-manager/pull/3|#3 Publish to npm>

不知怎的，這個 Github action 好像一定要進 main branch 之後才偵測得到 https://github.community/t/workflow-dispatch-workflow-not-showing-in-actions-tab/130088/39

這樣一來就要 merge 才能測了呢 >“<
如果大家沒問題的話我下午就 merge media-manager 的 PR 們唷
我先用 CLI 發布一個版本來讓 rumors-api 可以測過
所以還可以 review 一下 media-manager~
https://www.npmjs.com/package/@cofacts/media-manager
mrorz 14:49:59
不知怎的，這個 Github action 好像一定要進 main branch 之後才偵測得到 https://github.community/t/workflow-dispatch-workflow-not-showing-in-actions-tab/130088/39

這樣一來就要 merge 才能測了呢 >“<
如果大家沒問題的話我下午就 merge media-manager 的 PR 們唷

GitHub Community

Workflow_dispatch workflow not showing in actions tab

As of today if you create a workflow file manually on your machine or through GitHub interface it doesn’t matter. If you want to use the workflow_dispatch trigger it will only work on the main branch if you commit it to a separate branch (any non default branch) it will not show.

2022-06-14

github2 04:05:17

<https://github.com/cofacts/rumors-api/pull/284#issuecomment-1154376799|Comment on #284 Apply media manager>

<https://coveralls.io/builds/49975159|Coverage Status> Coverage decreased (-0.1%) to 87.355% when pulling *<https://github.com/cofacts/rumors-api/commit/8dae1a06381ac702897c5f0d814c6c57c8facf11|8dae1a0> on apply-media-manager* into *<https://github.com/cofacts/rumors-api/commit/319b9d3cef5efa151c82f1d9c73f1e35903cef22|319b9d3> on master*.

github2 04:05:17

<https://github.com/cofacts/rumors-api/pull/284#issuecomment-1154376799|Comment on #284 Apply media manager>

<https://coveralls.io/builds/49975159|Coverage Status> Coverage decreased (-0.1%) to 87.355% when pulling *<https://github.com/cofacts/rumors-api/commit/8dae1a06381ac702897c5f0d814c6c57c8facf11|8dae1a0> on apply-media-manager* into *<https://github.com/cofacts/rumors-api/commit/319b9d3cef5efa151c82f1d9c73f1e35903cef22|319b9d3> on master*.

mrorz 16:38:41
有人檢舉這裡的網友回報補充
https://cofacts.tw/article/31zo1t3qdbgzz

我查了一下，發現這個網友是在編輯回應之前就填寫這個補充的，然後其他使用上看起來是個一般的 LINE 使用者。也就是說，使用者在 LINE bot 上傳了這則訊息，Cofacts chatbot 回應「有待好心人來查證、先不要相信唷」之後，使用者暴怒 (?) 然後按「提供更多情報」寫了這個。

之前也有人來信說 comment 應該要有 time display，不過這個其實也已經有票 https://github.com/cofacts/rumors-site/issues/425
好像可以開個 good first issue？
我可以來在 github comment 提及 email 與使用者的檢舉來 escalate ＋ 標 good first issue
mrorz 16:38:41
有人檢舉這裡的網友回報補充
https://cofacts.tw/article/31zo1t3qdbgzz

我查了一下，發現這個網友是在編輯回應之前就填寫這個補充的，然後其他使用上看起來是個一般的 LINE 使用者。也就是說，使用者在 LINE bot 上傳了這則訊息，Cofacts chatbot 回應「有待好心人來查證、先不要相信唷」之後，使用者暴怒 (?) 然後按「提供更多情報」寫了這個。

之前也有人來信說 comment 應該要有 time display，不過這個其實也已經有票 https://github.com/cofacts/rumors-site/issues/425
好像可以標個 good first issue？

cofacts.github.io

Community Builder

Web site created using create-react-app

<https://github.com/cofacts/rumors-site/issues/425|#425 Show author of reply requests (article comments)>

We should show author of reply requests, as depicted in <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=681%3A0|figma>. *Mobile* <https://user-images.githubusercontent.com/108608/113914992-c4961180-9810-11eb-89cf-31b78f363609.png|image> *Desktop* <https://user-images.githubusercontent.com/108608/113914962-bba54000-9810-11eb-9568-4c47bab8117d.png|image>

我可以來在 github comment 提及 email 與使用者的檢舉來 escalate ＋ 標 good first issue

2022-06-15

mrorz 09:06:36
今天的例行會議移到禮拜五唷～
mrorz 09:06:36
今天的例行會議移到禮拜五唷～

2022-06-16

2022-06-17

cai 19:25:44
怪異
為什麼都會出現 `對 Cofacts 真的假的的建言` ?
https://cofacts.tw/article/225j78w0z449z
https://cofacts.tw/article/h094j93pmsgy
cai 19:25:44
怪異
為什麼都會出現 `對 Cofacts 真的假的的建言` ?
https://cofacts.tw/article/225j78w0z449z
https://cofacts.tw/article/h094j93pmsgy

2022-06-18

Recca Chao 17:04:47
@flamerecca711 has joined the channel
Recca Chao 17:04:59
👏
🙌 2 1
Recca Chao 17:04:59
👏

2022-06-19

cai 22:42:46
https://cofacts.tw/article/24olhlxr18iat
https://www.instagram.com/epidemic_taiwan/ 在IG限時動態內的連結，這要怎麼寫在佐證阿 😅
會被人懷疑蠻合理的，表單要人填學校跟姓名，IG上又找不到什麼資訊
cai 22:42:46
https://cofacts.tw/article/24olhlxr18iat
https://www.instagram.com/epidemic_taiwan/ 在IG限時動態內的連結，這要怎麼寫在佐證阿 😅
會被人懷疑蠻合理的，表單要人填學校跟姓名，IG上又找不到什麼資訊
cai 23:03:17
檢舉違規內容 (回覆) 公告有錯字：「即便乳此」
感謝回報
cai 23:03:17
檢舉違規內容 (回覆) 公告有錯字：「即便乳此」
感謝回報

2022-06-20

mrorz 03:28:02
https://cofacts.tw/article/225j78w0z449z
幫這個詐騙說話的滿可能都是詐騙同夥
值得查一下 CIB
mrorz 03:28:02
https://cofacts.tw/article/225j78w0z449z
幫這個詐騙說話的滿可能都是詐騙同夥
值得查一下 CIB
🧐 2
carey011677 05:23:47
@carey011677 has joined the channel
Teemo 08:42:18
開源社雞排跟開源有關嗎？

2022-06-22

mrorz 12:32:15
提醒一下
本週會議是週四唷
mrorz 12:32:15
提醒一下
本週會議是週四唷
github2 13:06:01

<https://github.com/cofacts/rumors-line-bot/issues/310|#310 Feedback is sent to wrong articleId / replyId>

When user scrolls back and gives feedback, the feedback will be given to the latest article / reply. For instance, in the conversation below, when user clicks "yes" circled in red, the feedback will be sent to the circled out reply further below: <https://user-images.githubusercontent.com/108608/174947370-44cf2a68-07e8-422a-8c8d-0eeadead2b9b.png|image> If the second selected article have multiple replies, the `selectedReplyId` will stay in the previous selection, while the `selectedArticleId` in context being updated. This will create an article-reply-feedback to wrong combination of `articleId` and `replyId`, and chatbot will return "Cannot record your feedback" error. We now have hundreds of such feedback in the database. Since the buttons comes from the same search session, the old buttons are not blocked. *Suggested fix* In <https://github.com/cofacts/rumors-line-bot/issues/176|#176> we have addressed that this is an issue. But instead of using JWT (which we want to deprecate), passing `articleId` and `replyId` right inside the LIFF URL should be enough. We should also remove the need to use `sendMessage` in feedback LIFFs, similar to what we have done in comment LIFFs (<https://g0v.hackmd.io/dOAOGDNzTGCWEsXW8weIgg#%E9%80%81%E5%87%BA%E8%A8%8A%E6%81%AF-state-diagram|discussion>)

我在自己機器試跑 https://github.com/cofacts/rumors-api/pull/285 的 migration script 時，發現百餘份 feedback 的 `articleId` 跟 `replyid` 根本對不起來。追蹤了一下才發現，是因為 chatbot context 錯亂導致的。只要使用者往回捲，按了前一個回應的是否有用，那個 feedback 就會被送到最下面的 reply 上。

這個有點嚴重，不知道多少個 feedback 是因為這樣給錯的，我想要立即處理 QQ
我在想會不會有些莫名其妙的 feedback 就是這樣來，因為使用者可能會有這樣的流程：

• 查了一則訊息，cofacts 吐出數則待選訊息
• 選了一則訊息，chatbot 給了一個回應，使用者不滿意
• 使用者捲回去選另一則訊息，chatbot 給了另一個回應，使用者覺得有用，所以給了好評
• 使用者想要捲回去給前面看到的回應負評，但此時因為此 bug 的原因，這個負評會給到下面的回應，還會把原本的好評取消掉
看起來這個 bug 應該是 2017 年， https://github.com/cofacts/rumors-line-bot/issues/49 做完之後就存在的囧
根據 2018 年的統計，「chatbot 使用者捲回去點前面的按鈕」這件事，每天大概會有兩百次
https://github.com/cofacts/rumors-line-bot/issues/49#issuecomment-439603502
當然這不代表說每次使用者點舊按鈕都是為了打分數啦，可能是回頭選 article 或回頭選 reply
但這也告訴我們，chatbot 使用者是很常會往回捲的，只要按鈕不會再對話紀錄中消失，就要非常注意其設計，最好每顆按鈕都不該 depend on context，或是該動作的所有參數都已經放在 action 上
github2 13:06:01

<https://github.com/cofacts/rumors-line-bot/issues/310|#310 Feedback is sent to wrong articleId / replyId>

When user scrolls back and gives feedback, the feedback will be given to the latest article / reply. For instance, in the conversation below, when user clicks "yes" circled in red, the feedback will be sent to the circled out reply further below: <https://user-images.githubusercontent.com/108608/174947370-44cf2a68-07e8-422a-8c8d-0eeadead2b9b.png|image> If the second selected article have multiple replies, the `selectedReplyId` will stay in the previous selection, while the `selectedArticleId` in context being updated. This will create an article-reply-feedback to wrong combination of `articleId` and `replyId`, and chatbot will return "Cannot record your feedback" error. We now have hundreds of such feedback in the database. Since the buttons comes from the same search session, the old buttons are not blocked. *Suggested fix* In <https://github.com/cofacts/rumors-line-bot/issues/176|#176> we have addressed that this is an issue. But instead of using JWT (which we want to deprecate), passing `articleId` and `replyId` right inside the LIFF URL should be enough. We should also remove the need to use `sendMessage` in feedback LIFFs, similar to what we have done in comment LIFFs (<https://g0v.hackmd.io/dOAOGDNzTGCWEsXW8weIgg#%E9%80%81%E5%87%BA%E8%A8%8A%E6%81%AF-state-diagram|discussion>)

我在自己機器試跑 https://github.com/cofacts/rumors-api/pull/285 的 migration script 時，發現百餘份 feedback 的 `articleId` 跟 `replyid` 根本對不起來。追蹤了一下才發現，是因為 chatbot context 錯亂導致的。只要使用者往回捲，按了前一個回應的是否有用，那個 feedback 就會被送到最下面的 reply 上。

這個有點嚴重，不知道多少個 feedback 是因為這樣給錯的，我想要立即處理 QQ
我在想會不會有些莫名其妙的 feedback 就是這樣來，因為使用者可能會有這樣的流程：

• 查了一則訊息，cofacts 吐出數則待選訊息
• 選了一則訊息，chatbot 給了一個回應，使用者不滿意
• 使用者捲回去選另一則訊息，chatbot 給了另一個回應，使用者覺得有用，所以給了好評
• 使用者想要捲回去給前面看到的回應負評，但此時因為此 bug 的原因，這個負評會給到下面的回應，還會把原本的好評取消掉
看起來這個 bug 應該是 2017 年， https://github.com/cofacts/rumors-line-bot/issues/49 做完之後就存在的囧
根據 2018 年的統計，「chatbot 使用者捲回去點前面的按鈕」這件事，每天大概會有兩百次
https://github.com/cofacts/rumors-line-bot/issues/49#issuecomment-439603502
當然這不代表說每次使用者點舊按鈕都是為了打分數啦，可能是回頭選 article 或回頭選 reply
但這也告訴我們，chatbot 使用者是很常會往回捲的，只要按鈕不會再對話紀錄中消失，就要非常注意其設計，最好每顆按鈕都不該 depend on context，或是該動作的所有參數都已經放在 action 上
mrorz 13:09:03
我在自己機器試跑 https://github.com/cofacts/rumors-api/pull/285 的 migration script 時，發現百餘份 feedback 的 `articleId` 跟 `replyid` 根本對不起來。追蹤了一下才發現，是因為 chatbot context 錯亂導致的。只要使用者往回捲，按了前一個回應的是否有用，那個 feedback 就會被送到最下面的 reply 上。

這個有點嚴重，不知道多少個 feedback 是因為這樣給錯的，我想要立即處理 QQ
cai 15:16:44
為什麼最近都是假冒凱基阿？
cai 15:16:44
為什麼最近都是假冒凱基阿？

2022-06-23

github2 09:49:25

<https://github.com/cofacts/rumors-line-bot/pull/311|#311 Implement line content proxy>

usage `/getcontent?token={jwt}` • use a 5min-expired jwt to avoid others accessing it

github2 09:49:25

<https://github.com/cofacts/rumors-line-bot/pull/311|#311 Implement line content proxy>

usage `/getcontent?token={jwt}` • use a 5min-expired jwt to avoid others accessing it

:white_check_mark: No checks have passed

github2 13:35:08

Review on #311 Implement line content proxy

Using signed JWT to avoid arbitrary access is elegant! It ensures that only rumors-line-bot can generate valid URLs for the endpoint, and the URL it gives out has limited access in time. <https://user-images.githubusercontent.com/108608/175222413-ba8a878f-ac53-4372-9d88-9751590baed2.png|image>

github2 13:35:08

Review on #311 Implement line content proxy

Using signed JWT to avoid arbitrary access is elegant! It ensures that only rumors-line-bot can generate valid URLs for the endpoint, and the URL it gives out has limited access in time. <https://user-images.githubusercontent.com/108608/175222413-ba8a878f-ac53-4372-9d88-9751590baed2.png|image>

github2 13:35:09

<https://github.com/cofacts/rumors-line-bot/pull/311#discussion_r904531058|Comment on #311 Implement line content proxy>

This will download the whole file from LINE to chatbot before sending to response. Could we directly pipe body to response instead? In this way the file will not fill up the memory of chatbot. Also, it would be great if this proxy can forward `Content-Type` and `Content-Length` from LINE `getContent` endpoint, as media-manager would rely on these two headers to determine file type and process files.

github2 13:35:09

<https://github.com/cofacts/rumors-line-bot/pull/311#discussion_r904531058|Comment on #311 Implement line content proxy>

This will download the whole file from LINE to chatbot before sending to response. Could we directly pipe body to response instead? In this way the file will not fill up the memory of chatbot. Also, it would be great if this proxy can forward `Content-Type` and `Content-Length` from LINE `getContent` endpoint, as media-manager would rely on these two headers to determine file type and process files.

2022-06-24

cai 12:50:58
cofacts.g0v.tw 的憑證已於 2022/6/24 過期
image.png
感謝反應
nginx reload 又爛了囧
咦這次 nginx reload 是對的
似乎是 certbot 出事
是有多衰 lol
手動重跑就過了
憑證已更新
🙇 1
github2 16:38:38

<https://github.com/cofacts/rumors-line-bot/pull/314|#314 Upgrade npm to 8.13.1 (8.5+) and regenerate package-lock.json>

so that its version resolution matches the new npm behavior used on Github action. *Before* <https://github.com/cofacts/rumors-line-bot/runs/7038118527?check_suite_focus=true|https://github.com/cofacts/rumors-line-bot/runs/7038118527?check_suite_focus=true> (on master branch) <https://user-images.githubusercontent.com/108608/175497728-9ddd2ee1-6907-4c82-9d9a-a865a68930c2.png|image> *After* <https://github.com/cofacts/rumors-line-bot/actions/runs/2554485738|https://github.com/cofacts/rumors-line-bot/actions/runs/2554485738> (on this branch) <https://user-images.githubusercontent.com/108608/175497790-501281a7-b26c-4cd9-852d-923ac41b338b.png|image>

@acerxp511 這個 PR 會修好我們的 github action~~
我把我自己的 npm 更新到最新版（ https://docs.npmjs.com/try-the-latest-stable-version-of-npm#upgrading-on-nix-osx-linux-etc ）之後 `npm i`，lockfile 就更新了

這個 PR 就是放那個更新後的 lockfile
github2 16:38:38

<https://github.com/cofacts/rumors-line-bot/pull/314|#314 Upgrade npm to 8.13.1 (8.5+) and regenerate package-lock.json>

so that its version resolution matches the new npm behavior used on Github action. Reference: <https://github.com/npm/cli/issues/4684|npm/cli#4684> *Before* <https://github.com/cofacts/rumors-line-bot/runs/7038118527?check_suite_focus=true|https://github.com/cofacts/rumors-line-bot/runs/7038118527?check_suite_focus=true> (on master branch) <https://user-images.githubusercontent.com/108608/175497728-9ddd2ee1-6907-4c82-9d9a-a865a68930c2.png|image> *After* <https://github.com/cofacts/rumors-line-bot/actions/runs/2554485738|https://github.com/cofacts/rumors-line-bot/actions/runs/2554485738> (on this branch) <https://user-images.githubusercontent.com/108608/175497790-501281a7-b26c-4cd9-852d-923ac41b338b.png|image>

:white_check_mark: All checks have passed

@acerxp511 這個 PR 會修好我們的 github action~~
我把我自己的 npm 更新到最新版（ https://docs.npmjs.com/try-the-latest-stable-version-of-npm#upgrading-on-nix-osx-linux-etc ）之後 `npm i`，lockfile 就更新了

這個 PR 就是放那個更新後的 lockfile
github2 16:43:12

<https://github.com/cofacts/rumors-line-bot/pull/314#issuecomment-1165346511|Comment on #314 Upgrade npm to 8.13.1 (8.5+) and regenerate package-lock.json>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50328003|Build 2554559934>* • *0* of *0* changed or added relevant lines in *0* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *86.946%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:43:12

<https://github.com/cofacts/rumors-line-bot/pull/314#issuecomment-1165346511|Comment on #314 Upgrade npm to 8.13.1 (8.5+) and regenerate package-lock.json>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50328003|Build 2554559934>* • *0* of *0* changed or added relevant lines in *0* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *86.946%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

cai 20:41:12
https://tfc-taiwan.org.tw/articles/7737
https://www.mygopen.com/2022/06/feed-antibiotic.html
兩篇對於東港那題的回應，兩家針對點不同，答案不一樣XDD
這樣不是很好嗎，由不同角度切入 XD
cai 20:41:12
https://tfc-taiwan.org.tw/articles/7737
https://www.mygopen.com/2022/06/feed-antibiotic.html
兩篇對於東港那題的回應，兩家針對點不同，答案不一樣XDD
這樣不是很好嗎，由不同角度切入 XD

2022-06-25

github2 02:35:11

<https://github.com/cofacts/rumors-fb-bot/pull/36|#36 Bump node-fetch from 2.2.0 to 2.6.7>

Bumps <https://github.com/node-fetch/node-fetch|node-fetch> from 2.2.0 to 2.6.7. Release notes _Sourced from <https://github.com/node-fetch/node-fetch/releases|node-fetch's releases>._ &gt; *v2.6.7* &gt; *Security patch release* &gt; &gt; Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred &gt; &gt; *What's Changed* &gt; &gt; • fix: don't forward secure headers to 3th party by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1453|node-fetch/node-fetch#1453> &gt; &gt; *Full Changelog*: <https://github.com/node-fetch/node-fetch/compare/v2.6.6...v2.6.7|node-fetch/node-fetch@v2.6.6...v2.6.7> &gt; &gt; *v2.6.6* &gt; *What's Changed* &gt; &gt; • fix(URL): prefer built in URL version when available and fallback to whatwg by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1352|node-fetch/node-fetch#1352> &gt; &gt; *Full Changelog*: <https://github.com/node-fetch/node-fetch/compare/v2.6.5...v2.6.6|node-fetch/node-fetch@v2.6.5...v2.6.6> &gt; &gt; *v2.6.2* &gt; &gt; fixed main path in package.json &gt; &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; See <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261|CHANGELOG> for details. &gt; &gt; *v2.6.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.6.0/CHANGELOG.md#v260|CHANGELOG>. &gt; &gt; *v2.5.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.5.0/CHANGELOG.md#v250|CHANGELOG>. &gt; &gt; *v2.4.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.1/CHANGELOG.md#v241|CHANGELOG>. &gt; &gt; *v2.4.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.0/CHANGELOG.md#v240|CHANGELOG>. &gt; &gt; *v2.3.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.3.0/CHANGELOG.md#v230|CHANGELOG>. &gt; &gt; *v2.2.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.2.1/CHANGELOG.md#v221|CHANGELOG>. Commits • <https://github.com/node-fetch/node-fetch/commit/1ef4b560a17e644a02a3bfdea7631ffeee578b35|`1ef4b56`> backport of <https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1449|#1449> (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1453|#1453>) • <https://github.com/node-fetch/node-fetch/commit/8fe5c4ea66b9b8187600e6d5ec9b1b6781f44009|`8fe5c4e`> 2.x: Specify encoding as an optional peer dependency in package.json (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1310|#1310>) • <https://github.com/node-fetch/node-fetch/commit/f56b0c66d3dd2ef185436de1f2fd40f66bfea8f4|`f56b0c6`> fix(URL): prefer built in URL version when available and fallback to whatwg (... • <https://github.com/node-fetch/node-fetch/commit/b5417aea6a3275932283a200214522e6ab53f1ea|`b5417ae`> fix: import whatwg-url in a way compatible with ESM Node (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1303|#1303>) • <https://github.com/node-fetch/node-fetch/commit/18193c5922c64046b922e18faf41821290535f06|`18193c5`> fix v2.6.3 that did not sending query params (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1301|#1301>) • <https://github.com/node-fetch/node-fetch/commit/ace7536c955556be742d9910566738630cc3c2a6|`ace7536`> fix: properly encode url with unicode characters (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1291|#1291>) • <https://github.com/node-fetch/node-fetch/commit/152214ca2f6e2a5a17d71e4638114625d3be30c6|`152214c`> Fix(package.json): Corrected main file path in package.json (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1274|#1274>) • <https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab|`b5e2e41`> update version number • <https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334|`2358a6c`> Honor the `size` option after following a redirect and revert data uri support • <https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4|`8c197f8`> docs: Fix typos and grammatical errors in README.md (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/686|#686>) • Additional commits viewable in <https://github.com/node-fetch/node-fetch/compare/v2.2.0...v2.6.7|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~endless|endless>, a new releaser for node-fetch since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-fb-bot/network/alerts|Security Alerts page>.

github2 02:35:11

<https://github.com/cofacts/rumors-fb-bot/pull/36|#36 Bump node-fetch from 2.2.0 to 2.6.7>

Bumps <https://github.com/node-fetch/node-fetch|node-fetch> from 2.2.0 to 2.6.7. Release notes _Sourced from <https://github.com/node-fetch/node-fetch/releases|node-fetch's releases>._ &gt; *v2.6.7* &gt; *Security patch release* &gt; &gt; Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred &gt; &gt; *What's Changed* &gt; &gt; • fix: don't forward secure headers to 3th party by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1453|node-fetch/node-fetch#1453> &gt; &gt; *Full Changelog*: <https://github.com/node-fetch/node-fetch/compare/v2.6.6...v2.6.7|node-fetch/node-fetch@v2.6.6...v2.6.7> &gt; &gt; *v2.6.6* &gt; *What's Changed* &gt; &gt; • fix(URL): prefer built in URL version when available and fallback to whatwg by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1352|node-fetch/node-fetch#1352> &gt; &gt; *Full Changelog*: <https://github.com/node-fetch/node-fetch/compare/v2.6.5...v2.6.6|node-fetch/node-fetch@v2.6.5...v2.6.6> &gt; &gt; *v2.6.2* &gt; &gt; fixed main path in package.json &gt; &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; See <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261|CHANGELOG> for details. &gt; &gt; *v2.6.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.6.0/CHANGELOG.md#v260|CHANGELOG>. &gt; &gt; *v2.5.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.5.0/CHANGELOG.md#v250|CHANGELOG>. &gt; &gt; *v2.4.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.1/CHANGELOG.md#v241|CHANGELOG>. &gt; &gt; *v2.4.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.0/CHANGELOG.md#v240|CHANGELOG>. &gt; &gt; *v2.3.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.3.0/CHANGELOG.md#v230|CHANGELOG>. &gt; &gt; *v2.2.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.2.1/CHANGELOG.md#v221|CHANGELOG>. Commits • <https://github.com/node-fetch/node-fetch/commit/1ef4b560a17e644a02a3bfdea7631ffeee578b35|`1ef4b56`> backport of <https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1449|#1449> (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1453|#1453>) • <https://github.com/node-fetch/node-fetch/commit/8fe5c4ea66b9b8187600e6d5ec9b1b6781f44009|`8fe5c4e`> 2.x: Specify encoding as an optional peer dependency in package.json (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1310|#1310>) • <https://github.com/node-fetch/node-fetch/commit/f56b0c66d3dd2ef185436de1f2fd40f66bfea8f4|`f56b0c6`> fix(URL): prefer built in URL version when available and fallback to whatwg (... • <https://github.com/node-fetch/node-fetch/commit/b5417aea6a3275932283a200214522e6ab53f1ea|`b5417ae`> fix: import whatwg-url in a way compatible with ESM Node (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1303|#1303>) • <https://github.com/node-fetch/node-fetch/commit/18193c5922c64046b922e18faf41821290535f06|`18193c5`> fix v2.6.3 that did not sending query params (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1301|#1301>) • <https://github.com/node-fetch/node-fetch/commit/ace7536c955556be742d9910566738630cc3c2a6|`ace7536`> fix: properly encode url with unicode characters (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1291|#1291>) • <https://github.com/node-fetch/node-fetch/commit/152214ca2f6e2a5a17d71e4638114625d3be30c6|`152214c`> Fix(package.json): Corrected main file path in package.json (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1274|#1274>) • <https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab|`b5e2e41`> update version number • <https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334|`2358a6c`> Honor the `size` option after following a redirect and revert data uri support • <https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4|`8c197f8`> docs: Fix typos and grammatical errors in README.md (<https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/686|#686>) • Additional commits viewable in <https://github.com/node-fetch/node-fetch/compare/v2.2.0...v2.6.7|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~endless|endless>, a new releaser for node-fetch since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-fb-bot/network/alerts|Security Alerts page>.

Teemo 04:28:58
https://thediplomat.com/2022/06/ukraine-disinformation-fight-sounds-warning-bells-for-taiwan/

thediplomat.com

Ukraine Disinformation Fight Sounds Warning Bells for Taiwan

Short of a drastic overhaul, Tsai Ing-wen’s administration must gain a firmer understanding of vulnerabilities in the domestic information environment.

👍 1
github2 11:08:32

<https://github.com/cofacts/takedowns/pull/77|#77 Create 0625-ads-and-scam.md>

前一張表有點久以前，所以開一張新的表來放二次詐騙

github2 11:08:32

<https://github.com/cofacts/takedowns/pull/77|#77 Create 0625-ads-and-scam.md>

前一張表有點久以前，所以開一張新的表來放二次詐騙

cai 12:51:27
https://www.appledaily.com.tw/politics/20220624/7C041D815EABDAE716D712950F
cofacts被蘋果日報截圖了

AppleDaily

網傳內閣改組名單　總統府澄清：沒有改組打算｜蘋果新聞網｜蘋果日報

關於網路流傳一份名單，其中訛稱鄭文燦接任總統府秘書長、林佳龍任行政院副院長與林右昌接任交通部長，對此總統府今日（24日）回應，總統對於秘書長沒有異動的打算，也沒有內閣改組的打算，期盼各界勿以訛傳訛。

🙌 2
github2 15:08:57

<https://github.com/cofacts/rumors-line-bot/pull/315|#315 Cleanup feedback related state, old LIFF page and token mechanism>

• Remove `feedback/yes` and `feedback/no` LIFF pages • Remove LINE bot GraphQL endpoints related to above pages - `context` query and `voteReply` mutation • Remove LIFF &lt;&gt; LINE bot graphql's bearer token mechanism • It <https://g0v.hackmd.io/860RnxUGTi6z2Kca6ojAbg#LIFF-ltgt-Chatbot-server-communication|was introduced> in LIFF as `token` URL param. LIFF forwards the token back in LINE bot GraphQL, so that LINE bot graphql can authenticate user when determining GraphQL context. • However, this whole mechanism is replaced by LIFF v2's ID token (or possibly access token if we remove ID token permission) • The last place we use such token was in `PositiveFeedback` and `NegativeFeedback` LIFF pages. • The mechanism can be removed after the aforementioned LIFF pages are removed • Remove `askingReplyFeedback` state handler and its related prefix logic

:white_check_mark: All checks have passed

github2 15:08:57

<https://github.com/cofacts/rumors-line-bot/pull/315|#315 Cleanup feedback related state, old LIFF page and token mechanism>

• Remove `feedback/yes` and `feedback/no` LIFF pages • Remove LINE bot GraphQL endpoints related to above pages - `context` query and `voteReply` mutation • Remove LIFF &lt;&gt; LINE bot graphql's bearer token mechanism • It was introduced in LIFF as `token` URL param. LIFF forwards the token back in LINE bot GraphQL, so that LINE bot graphql can authenticate user when determining GraphQL context. • However, this whole mechanism is replaced by LIFF v2's ID token (or possibly access token if we remove ID token permission) • The last place we use such token was in `PositiveFeedback` and `NegativeFeedback` LIFF pages. • The mechanism can be removed after the aforementioned LIFF pages are removed • Remove `askingReplyFeedback` state handler and its related prefix logic

github2 15:11:22

<https://github.com/cofacts/rumors-line-bot/pull/315#issuecomment-1166210742|Comment on #315 Cleanup feedback related state, old LIFF page and token mechanism>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50354874|Build 2559819518>* • *2* of *2* *(100.0%)* changed or added relevant lines in *1* file are covered. • *1* unchanged line in *1* file lost coverage. • Overall coverage decreased (*-1.3%*) to *85.648%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 15:11:22

<https://github.com/cofacts/rumors-line-bot/pull/315#issuecomment-1166210742|Comment on #315 Cleanup feedback related state, old LIFF page and token mechanism>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50354874|Build 2559819518>* • *2* of *2* *(100.0%)* changed or added relevant lines in *1* file are covered. • *1* unchanged line in *1* file lost coverage. • Overall coverage decreased (*-1.3%*) to *85.648%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:50:57

<https://github.com/cofacts/rumors-line-bot/pull/315#issuecomment-1166231358|Comment on #315 Cleanup feedback related state, old LIFF page and token mechanism>

This branch has been deployed to <https://line.me/R/ti/p/%40nkq3195z|staging LINE bot>; everyone can give it a try.

github2 16:50:57

<https://github.com/cofacts/rumors-line-bot/pull/315#issuecomment-1166231358|Comment on #315 Cleanup feedback related state, old LIFF page and token mechanism>

This branch has been deployed to <https://line.me/R/ti/p/%40nkq3195z|staging LINE bot>; everyone can give it a try.

github2 17:19:16

<https://github.com/cofacts/rumors-api/pull/286|#286 fix ArticleType's attachmentUrl when attachmentHash does not exist>

The bug was introduced in <https://github.com/cofacts/rumors-api/pull/284|#284> . Querying `ArticleType`'s `attachmentUrl` will trigger `Cannot read properties of undefined (reading 'split')` error. <https://user-images.githubusercontent.com/108608/175766904-0971cfe6-7706-4fcf-abab-98c124af4248.png|圖片> The root cause is that for non-image articles, `attachmentHash` is null. However, we send `null` to `MediaManager` to generate URL for `attachmentUrl` field. This PR: • Returns null for `attachmentUrl` if `attachmentHash` is null • Introduces a test case that will fail if this PR is not implemented

github2 17:19:16

<https://github.com/cofacts/rumors-api/pull/286|#286 fix ArticleType's attachmentUrl when attachmentHash does not exist>

The bug was introduced in <https://github.com/cofacts/rumors-api/pull/284|#284> . Querying `ArticleType`'s `attachmentUrl` will trigger `Cannot read properties of undefined (reading 'split')` error. <https://user-images.githubusercontent.com/108608/175766904-0971cfe6-7706-4fcf-abab-98c124af4248.png|圖片> The root cause is that for non-image articles, `attachmentHash` is null. However, we send `null` to `MediaManager` to generate URL for `attachmentUrl` field. This PR: • Returns null for `attachmentUrl` if `attachmentHash` is null • Introduces a test case that will fail if this PR is not implemented

:white_check_mark: All checks have passed

github2 17:21:33

<https://github.com/cofacts/rumors-api/pull/286#issuecomment-1166238794|Comment on #286 fix ArticleType's attachmentUrl when attachmentHash does not exist>

<https://coveralls.io/builds/50355484|Coverage Status> Coverage increased (+0.02%) to 87.549% when pulling *<https://github.com/cofacts/rumors-api/commit/e4fc699c8ed2c6c9421af6b95069e58ab0adcbea|e4fc699> on fix-url-resolver* into *<https://github.com/cofacts/rumors-api/commit/6540c6cbb03e0166a125820344a6e8da5e744d61|6540c6c> on master*.

github2 17:21:33

<https://github.com/cofacts/rumors-api/pull/286#issuecomment-1166238794|Comment on #286 fix ArticleType's attachmentUrl when attachmentHash does not exist>

<https://coveralls.io/builds/50355484|Coverage Status> Coverage increased (+0.02%) to 87.549% when pulling *<https://github.com/cofacts/rumors-api/commit/e4fc699c8ed2c6c9421af6b95069e58ab0adcbea|e4fc699> on fix-url-resolver* into *<https://github.com/cofacts/rumors-api/commit/6540c6cbb03e0166a125820344a6e8da5e744d61|6540c6c> on master*.

2022-06-26

cai 15:11:39
分類tag 是新戰場嗎 😆
大家有空幫忙按個分類的投票
把任何東西都標成「中國政治宣傳」
是把這個分類標籤弄爛的最簡單做法
他以為他在幫忙，實際是在幫倒忙
哎
（按一堆「反對」ing）
cai 15:11:39
分類tag 是新戰場嗎 😆
大家有空幫忙按個分類的投票
把任何東西都標成「中國政治宣傳」
是把這個分類標籤弄爛的最簡單做法
他以為他在幫忙，實際是在幫倒忙
哎
（按一堆「反對」ing）
github2 18:54:13

<https://github.com/cofacts/community-builder/pull/12|#12 Add columns and filters in editor works tables>

This PR depends on API being released to production <https://github.com/cofacts/rumors-api/pull/286|cofacts/rumors-api#286> and feedback user IDs being <https://github.com/cofacts/rumors-api/pull/285#issuecomment-1159399583|fully migrated>. *Add category column in feedback table* Lists the article's category for each feedback. Fixes <https://github.com/cofacts/community-builder/issues/11|#11> <https://user-images.githubusercontent.com/108608/175810778-0344ac0f-c7df-4a31-95a1-d355a6cee866.png|圖片> *Show feedbacks for a specific article-reply creator* Introduces `articleReplyUserId` URL param that specifies the author of article replies. Fixes <https://github.com/cofacts/community-builder/issues/10|#10> <https://user-images.githubusercontent.com/108608/175810802-ee011c98-2b4a-489f-b45a-e4c51557fe54.png|圖片> *Add article text for reply request* This helps when we determine if a user-reported spamming reply request is replying to something relevant. Also it provides link to article so that we can click into it to see if there is other spamming comments. <https://user-images.githubusercontent.com/108608/175810744-26db3e31-a030-4466-aec4-d1f1865b7fae.png|圖片>

github2 18:54:13

<https://github.com/cofacts/community-builder/pull/12|#12 Add columns and filters in editor works tables>

This PR depends on API being released to production <https://github.com/cofacts/rumors-api/pull/286|cofacts/rumors-api#286> and feedback user IDs being <https://github.com/cofacts/rumors-api/pull/285#issuecomment-1159399583|fully migrated>. *Add category column in feedback table* Lists the article's category for each feedback. Fixes <https://github.com/cofacts/community-builder/issues/11|#11> <https://user-images.githubusercontent.com/108608/175810778-0344ac0f-c7df-4a31-95a1-d355a6cee866.png|圖片> *Show feedbacks for a specific article-reply creator* Introduces `articleReplyUserId` URL param that specifies the author of article replies. Fixes <https://github.com/cofacts/community-builder/issues/10|#10> <https://user-images.githubusercontent.com/108608/175810802-ee011c98-2b4a-489f-b45a-e4c51557fe54.png|圖片> *Add article text for reply request* This helps when we determine if a user-reported spamming reply request is replying to something relevant. Also it provides link to article so that we can click into it to see if there is other spamming comments. <https://user-images.githubusercontent.com/108608/175810744-26db3e31-a030-4466-aec4-d1f1865b7fae.png|圖片>

:white_check_mark: All checks have passed

2022-06-27

mrorz 16:56:55
把任何東西都標成「中國政治宣傳」
是把這個分類標籤弄爛的最簡單做法
他以為他在幫忙，實際是在幫倒忙
哎
（按一堆「反對」ing）
mrorz 16:58:39
6/25 我從 staging 把 production 的資料庫備份拉下來
結果拉一次要花快 4 美金 XD
image.png
😮 2

2022-06-28

mrorz 10:39:26
昨天在 Media manager 開了新的 draft PR，用來開發 file variant
就是傳一個 URL 給 media manager，media manager 除了把原圖傳上 GCS 之外，還會即時壓縮成縮圖，影片截圖之類的，一起傳上 GCS。
因為原本一個 file ID 對應到單一檔案，現在是一個 file ID 對應到一組 variant，所以改了不少地方，需要 review。
https://github.com/cofacts/media-manager/pull/4/files
mrorz 10:39:26
昨天在 Media manager 開了新的 draft PR，用來開發 file variant
就是傳一個 URL 給 media manager，media manager 除了把原圖傳上 GCS 之外，還會即時壓縮成縮圖，影片截圖之類的，一起傳上 GCS。
因為原本一個 file ID 對應到單一檔案，現在是一個 file ID 對應到很多 variant file，所以改了不少地方，需要 review。
https://github.com/cofacts/media-manager/pull/4/files
kelvinho84 16:25:01
e
kelvinho84 16:25:04
e
cai 20:15:56
https://getdr.com/大量民眾收到xxx科學研究所的提告通知，原因竟是/
cofacts 又被截圖當範例了XDD
喔喔喔喔有專文了讚讚讚
之後可以直接用這篇回～
165 每次都把案例 generalize 到沒人認得出來的狀況
受騙的人把對話記錄拿來 google 的話
根本不可能找到 165 的這些宣導
也就不會知道整個台灣其實有一大堆人跟自己一樣正在受騙
刑事局的新聞稿也是，詳細版的可能還要翻各家媒體、CIB局長室
cai 20:15:56
https://getdr.com/大量民眾收到xxx科學研究所的提告通知，原因竟是/
cofacts 又被截圖當範例了XDD
喔喔喔喔有專文了讚讚讚
之後可以直接用這篇回～
165 每次都把案例 generalize 到沒人認得出來的狀況
受騙的人把對話記錄拿來 google 的話
根本不可能找到 165 的這些宣導
也就不會知道整個台灣其實有一大堆人跟自己一樣正在受騙
刑事局的新聞稿也是，詳細版的可能還要翻各家媒體、CIB局長室

2022-06-29

github2 14:03:45

<https://github.com/cofacts/rumors-api/issues/287|#287 Connect Cofacts API to Media Manager file variants>

Modify attachment field and `CreateMediaArticle` for MediaManager v0.2.0 (PR: <https://github.com/cofacts/media-manager/pull/4|cofacts/media-manager#4> )

github2 14:07:17

<https://github.com/cofacts/media-manager/issues/5|#5 Media Manager documentation>

Add its usage to README • 把 <https://github.com/cofacts/media-manager/|https://github.com/cofacts/media-manager/> 的 README 補上一些圖說 • Use <https://typedoc.org/|typedoc> (or <https://www.reddit.com/r/typescript/comments/q3ylku/i_created_a_documentation_generator_for/|other alternatives?>) to generate document and publish on github pages? Introduce its methodology in a open place (hackmd / google doc / Github wiki / etc) Ref: • <https://docs.google.com/document/d/1QeMLpwE1HeBqo8Aa-QJ3uzNtCxRPlUECC-xWTU-rdQU/edit|https://docs.google.com/document/d/1QeMLpwE1HeBqo8Aa-QJ3uzNtCxRPlUECC-xWTU-rdQU/edit> • <https://docs.google.com/document/d/146yZjgmuJvvWjcmniRyjyMLu85815L30-H7j90kYBtE/edit#heading=h.qiy6ovn65cn7|https://docs.google.com/document/d/146yZjgmuJvvWjcmniRyjyMLu85815L30-H7j90kYBtE/edit#heading=h.qiy6ovn65cn7> • <https://docs.google.com/document/d/1YcXSU5UdZfJHkZoUetMH4L-j16aIpHkl-oghDEFaSJU/edit#|https://docs.google.com/document/d/1YcXSU5UdZfJHkZoUetMH4L-j16aIpHkl-oghDEFaSJU/edit#>

mrorz 14:36:56
今晚議程
滿多會在過 6 月底即將要上 production 的東西唷
https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ

g0v.hackmd.io

20220629 會議記錄 - HackMD

真的假的
真的唷 @yhsiang 今晚 8pm 來 gather 呀
https://gather.town/app/z3x18KQFgZCX8MeZ/cofacts
mrorz 14:36:56
今晚議程
滿多會在過 6 月底即將要上 production 的東西唷
https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ
真的假的
真的唷 @yhsiang 今晚 8pm 來 gather 呀
https://gather.town/app/z3x18KQFgZCX8MeZ/cofacts
github2 22:01:53

<https://github.com/cofacts/rumors-site/issues/492|#492 Filter in profile page>

From <https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE1|https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ#未竟項目1> <https://user-images.githubusercontent.com/108608/176455781-8f405b9a-b953-4a00-93b0-35a69048d0c6.png|圖片> • 「一個月內」filter 不是 for 這個使用者的 article reply 而是文章的最新 reply，導致 filter 不準確 • tab 裡的計數應該要跟 filter 連動，比較有用；tab 裡目前的數字跟最上面重複。 • filter 可能要移到 tab 上面，比較能呈現 filter 會影響 tab 這件事

github2 22:01:53

<https://github.com/cofacts/rumors-site/issues/492|#492 Filter in profile page>

From <https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE1|https://g0v.hackmd.io/UP6DRljfTciCSv_mUtB7wQ#未竟項目1> <https://user-images.githubusercontent.com/108608/176455781-8f405b9a-b953-4a00-93b0-35a69048d0c6.png|圖片> • 「一個月內」filter 不是 for 這個使用者的 article reply 而是文章的最新 reply，導致 filter 不準確 • tab 裡的計數應該要跟 filter 連動，比較有用；tab 裡目前的數字跟最上面重複。 • filter 可能要移到 tab 上面，比較能呈現 filter 會影響 tab 這件事

2022-06-30

mrorz 23:32:53
我要來 merge code 囉
mrorz 23:32:53
我要來 merge code 囉
github2 23:39:39

<https://github.com/cofacts/rumors-db/issues/46#issuecomment-1171374736|Comment on #46 Reply reference field should use cjk_url_email analyzer>

Already delivered in replies index v1.1.0 <https://github.com/cofacts/rumors-db/commit/5db5a2f14ee547ea0f063b454807484d693a4aa6|5db5a2f>

github2 23:39:39

<https://github.com/cofacts/rumors-db/issues/46#issuecomment-1171374736|Comment on #46 Reply reference field should use cjk_url_email analyzer>

Already delivered in replies index v1.1.0 <https://github.com/cofacts/rumors-db/commit/5db5a2f14ee547ea0f063b454807484d693a4aa6|5db5a2f>

mrorz 23:47:52
2022/7/1 1:00 ~ 1:15（1 個多小時後）Cofacts 會短暫下線
mrorz 23:47:52
2022/7/1 1:00 ~ 1:15（1 個多小時後）Cofacts 會短暫下線進行 DB reindex 唷