cofacts

Month: 2022-09

2022-09-03

mrorz 17:31:20
Stable Diffusion 最近好像很紅
所以找了個熱門謠言用 google translate 翻成英文之後丟進去讓他跑跑看
是不是可以拿來變成圖

好像有點有趣
image.png
chihao 18:44:48
Cofacts 10 月會有編輯小聚嗎?是不是可以聯合 10 週年各種活動一起宣傳?請大家一起來闢謠!
bil ++ 不知道編輯小聚的時間地點通常會在什麼時候決定呢?我在蒐集 10 月間各項活動的資訊,想要在 9 月中一起來宣傳宣傳 😛
咦小聚不是 9 月嗎
那要不要因應 10 週年移師(?)10 月?XD
啊對耶,我以為現在還是八月。小聚會在九月,但可以配合十月活動
那 10 月會是編輯小聚,還是其他活動呢?
10月很樂意參與活動,但考量到10月第三週,可能會是小規模的工作坊
哦哦哦!確認一下 bil 的意思是:10 月第 3 週 cofacts 會揪一次小型工作坊 ← 這樣嗎?
對,因為十週年在第三週
收到!如果有共筆的話歡迎編輯這個 book https://g0v.hackmd.io/@chihao/g10v-book/
這樣第 3 週超熱鬧!
不過也還是有 10/15 的活動 XD
也能移到第二週的
隨坑主意願!
或是感謝感謝
chihao 18:44:48
Cofacts 10 月會有編輯小聚嗎?是不是可以聯合 10 週年各種活動一起宣傳?請大家一起來闢謠!
bil ++ 不知道編輯小聚的時間地點通常會在什麼時候決定呢?我在蒐集 10 月間各項活動的資訊,想要在 9 月中一起來宣傳宣傳 😛
咦小聚不是 9 月嗎
那要不要因應 10 週年移師(?)10 月?XD
啊對耶,我以為現在還是八月。小聚會在九月,但可以配合十月活動
那 10 月會是編輯小聚,還是其他活動呢?
10月很樂意參與活動,但考量到10月第三週,可能會是小規模的工作坊
哦哦哦!確認一下 bil 的意思是:10 月第 3 週 cofacts 會揪一次小型工作坊 ← 這樣嗎?
對,因為十週年在第三週
收到!如果有共筆的話歡迎編輯這個 book https://g0v.hackmd.io/@chihao/g10v-book/
這樣第 3 週超熱鬧!
不過也還是有 10/15 的活動 XD
也能移到第二週的
隨坑主意願!
或是感謝感謝
🎉 2

2022-09-04

a038038456123 09:38:09
@a038038456123 has joined the channel

2022-09-05

cai 14:00:30
https://cofacts.tw/article/K4oYCIMBv5it-Cx_3on_
「阿嬤年邁體弱禁不起暴打」文字出自於 2022/8/30 CTWANT新聞
其他家報導沒有提到
https://www.setn.com/News.aspx?NewsID=1169563
https://udn.com/news/story/7320/6574396
https://www.cna.com.tw/news/asoc/202208300041.aspx
https://news.ltn.com.tw/news/ChiayiCounty/breakingnews/4041629
https://news.tvbs.com.tw/local/1891689

相關的應該是 2022/8/26 111偵005722 111偵009009
好怪
UDN 是說檢方請求重刑
網傳圖片卻說檢方認定
喔喔喔我看懂了
是網傳圖片抓住檢方不用殺人罪起訴的部分
嘉義地檢署有澄清
https://www.cyc.moj.gov.tw/media/293283/1110907%E5%98%89%E6%AA%A2%E5%B0%8D%E6%96%BC%E7[…]%BE%84%E6%B8%85%E6%96%B0%E8%81%9E%E7%A8%BF.pdf?mediaDL=true
> 本署起訴書並無網友所 言認定「阿嬤年邁體弱禁不起暴打」等內容。
嘉義地檢署有澄清
https://www.cyc.moj.gov.tw/media/293283/1110907%E5%98%89%E6%AA%A2%E5%B0%8D%E6%96%BC%E7[…]%BE%84%E6%B8%85%E6%96%B0%E8%81%9E%E7%A8%BF.pdf?mediaDL=true
> 本署起訴書並無網友所 言認定「阿嬤年邁體弱禁不起暴打」等內容。
起訴書是不是通常不公開呀
起訴書有給媒體
結論:CWANT亂下標題 + 只看標題不求證的民眾
這案例是不是可以給 #disinfo 當教材XD
cai 14:00:30
https://cofacts.tw/article/K4oYCIMBv5it-Cx_3on_
「阿嬤年邁體弱禁不起暴打」文字出自於 2022/8/30 CTWANT新聞
其他家報導沒有提到
https://www.setn.com/News.aspx?NewsID=1169563
https://udn.com/news/story/7320/6574396
https://www.cna.com.tw/news/asoc/202208300041.aspx
https://news.ltn.com.tw/news/ChiayiCounty/breakingnews/4041629
https://news.tvbs.com.tw/local/1891689

相關的應該是 2022/8/26 111偵005722 111偵009009
好怪
UDN 是說檢方請求重刑
網傳圖片卻說檢方認定
喔喔喔我看懂了
是網傳圖片抓住檢方不用殺人罪起訴的部分
嘉義地檢署有澄清
https://www.cyc.moj.gov.tw/media/293283/1110907%E5%98%89%E6%AA%A2%E5%B0%8D%E6%96%BC%E7[…]%BE%84%E6%B8%85%E6%96%B0%E8%81%9E%E7%A8%BF.pdf?mediaDL=true
> 本署起訴書並無網友所 言認定「阿嬤年邁體弱禁不起暴打」等內容。
嘉義地檢署有澄清
https://www.cyc.moj.gov.tw/media/293283/1110907%E5%98%89%E6%AA%A2%E5%B0%8D%E6%96%BC%E7[…]%BE%84%E6%B8%85%E6%96%B0%E8%81%9E%E7%A8%BF.pdf?mediaDL=true
> 本署起訴書並無網友所 言認定「阿嬤年邁體弱禁不起暴打」等內容。
起訴書是不是通常不公開呀
起訴書有給媒體
結論:CWANT亂下標題 + 只看標題不求證的民眾
這案例是不是可以給 #disinfo 當教材XD
👍 1
cai 21:46:47
https://cofacts.tw/article/29nb1wecl206h
七大line假好友跟數位發展部合併謠言了 😆
毆嘴螳螂⋯
> 七大Line假好友網軍側翼組織分別是:
> 1.趨勢科技防詐達人
> 2.Mygopen
> 3.美的好朋友
> 4.Cofacts真的假的
> 5.美玉姨
> 6.美麗姨
> 7.台灣事實查核中心
那個 6 是什麼呀⋯⋯
我也好想知道啊啊啊
😂 1
cai 21:46:47
https://cofacts.tw/article/29nb1wecl206h
七大line假好友跟數位發展部合併謠言了 😆
毆嘴螳螂⋯
> 七大Line假好友網軍側翼組織分別是:
> 1.趨勢科技防詐達人
> 2.Mygopen
> 3.美的好朋友
> 4.Cofacts真的假的
> 5.美玉姨
> 6.美麗姨
> 7.台灣事實查核中心
那個 6 是什麼呀⋯⋯
我也好想知道啊啊啊
cai 22:19:12
https://cofacts.tw/article/3uwbrxcufi6b6
這篇我不知道如何吐槽起
飯店電視頻道沒有TVBS怪政府
居然有 7 人在傳
變成 9 次詢問了
是 viral message 耶
直接問飯店 ++ \o/
飯店的 MOD 不等於 中華電信的 MOD ,飯店有自己的頻道商
那跟NCC還有中華電信還有關係嗎?
原始訊息是溪頭的飯店的回應
不過看起來飯店確實是不會使用中華電信 MOD
這樣目前回應好像就會有問題
但看起來也是有飯店確實是用中華電信 MOD
https://booking.taiwantravelmap.com/user/order.aspx?m=799&r=5164&lg=ch
商業市場機制,NCC無權介入 XDD
不過 NCC 能把整個台下架 XD
宜蘭蘇澳 綺麗商旅
cai 22:19:12
https://cofacts.tw/article/3uwbrxcufi6b6
這篇我不知道如何吐槽起
飯店電視頻道沒有TVBS怪政府
居然有 7 人在傳
變成 9 次詢問了
是 viral message 耶
直接問飯店 ++ \o/
飯店的 MOD 不等於 中華電信的 MOD ,飯店有自己的頻道商
那跟NCC還有中華電信還有關係嗎?
原始訊息是溪頭的飯店的回應
不過看起來飯店確實是不會使用中華電信 MOD
這樣目前回應好像就會有問題
但看起來也是有飯店確實是用中華電信 MOD
https://booking.taiwantravelmap.com/user/order.aspx?m=799&r=5164&lg=ch
商業市場機制,NCC無權介入 XDD
不過 NCC 能把整個台下架 XD
宜蘭蘇澳 綺麗商旅
mrorz 22:19:48
看來二次詐騙現在會直接盜別人文章搞 SEO 然後宣傳自己的二次詐騙帳號
https://cofacts.tw/article/1c6jl5fq7plsw
這網址一直洗板

在我清掉之後
就 0 人回報了
所以是發文後自回那種
共有以下十五篇
2zeg7nknvppyd
1c6jl5fq7plsw
20j7tov2pwi6u
yjhr09b8h0mo
3q1zucbbrobxa
2f7ujanyqo1vr
312jz2odp1xwd
2o1ycthbdatar
n6cr2rlwndvz
3ps8oul9x114a
1pe9fq93m6oez
2dlvj7t517ogr
zfykyif3b2sq
l1k7sptlglo3
2mqe16ahhtrg
mrorz 22:19:48
看來二次詐騙現在會直接盜別人文章搞 SEO 然後宣傳自己的二次詐騙帳號
https://cofacts.tw/article/1c6jl5fq7plsw
這網址一直洗板

在我清掉之後
就 0 人回報了
所以是發文後自回那種
共有以下十五篇
2zeg7nknvppyd
1c6jl5fq7plsw
20j7tov2pwi6u
yjhr09b8h0mo
3q1zucbbrobxa
2f7ujanyqo1vr
312jz2odp1xwd
2o1ycthbdatar
n6cr2rlwndvz
3ps8oul9x114a
1pe9fq93m6oez
2dlvj7t517ogr
zfykyif3b2sq
l1k7sptlglo3
2mqe16ahhtrg

2022-09-06

cai 17:31:00
https://cofacts.tw/article/cz62km3xvyd5
假gov網站換成健保卡失效
看網站應該是這種的變形

2022-09-07

github2 18:58:41

<https://github.com/cofacts/rumors-line-bot/pull/321|#321 Fix image search on chatbot>

We observed that duplicate images are being submitted to Cofacts. According to the analysis in <https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#%E4%B8%8A%E7%B7%9A%E5%BE%8C%E8%BF%BD%E8%B9%A4%EF%BC%9A%E9%87%8D%E8%A4%87%E5%9C%96%E7%89%87|https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#%E4%B8%8A%E7%B7%9A%E5%BE%8C%E8%BF%BD%E8%B9%A4%EF%BC%9A%E9%87%8D%E8%A4%87%E5%9C%96%E7%89%87> , the root cause is • Production server does not have `MEDIA_ARTICLE_SUPPORT` turned on • Chatbot does not specify `articleTypes` so that only text is returned by default • Therefore, when chatbot user sends a very similar image, API always returns empty image search response This PR fixes the duplicate image submission problem by specifying all article types so that no matter what API's `MEDIA_ARTICLE_SUPPORT` is, chatbot can get all media results.

:white_check_mark: All checks have passed

github2 18:58:41

<https://github.com/cofacts/rumors-line-bot/pull/321|#321 [processImage] >

We observed that duplicate images are being submitted to Cofacts. According to the analysis in <https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#%E4%B8%8A%E7%B7%9A%E5%BE%8C%E8%BF%BD%E8%B9%A4%EF%BC%9A%E9%87%8D%E8%A4%87%E5%9C%96%E7%89%87|https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#%E4%B8%8A%E7%B7%9A%E5%BE%8C%E8%BF%BD%E8%B9%A4%EF%BC%9A%E9%87%8D%E8%A4%87%E5%9C%96%E7%89%87> , the root cause is • Production server does not have `MEDIA_ARTICLE_SUPPORT` turned on • Chatbot does not specify `articleTypes` so that only text is returned by default This PR fixes the duplicate image submission problem by specifying all article types so that no matter what API's `MEDIA_ARTICLE_SUPPORT` is, chatbot can get all media results.

github2 19:00:47

<https://github.com/cofacts/rumors-line-bot/pull/321#issuecomment-1239238970|Comment on #321 Fix image search on chatbot>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52272513|Build 3007073645>* • *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 *91.52%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 19:00:47

<https://github.com/cofacts/rumors-line-bot/pull/321#issuecomment-1239238970|Comment on #321 Fix image search on chatbot>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52272513|Build 3007073645>* • *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 *91.52%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

Steward 21:58:46
@steward has joined the channel

2022-09-08

mrorz 15:52:51
昨天會議中檢討的重複圖片的問題 + bugfix 已經在主站上線囉

• 隨著修復 chatbot 的圖片搜尋功能,未來 LINE 使用者可以正常看到相似圖片,在圖片相同的時候也會阻擋使用者創建新 article
• 針對已經在網站上的相似圖片,網站的「相似可疑訊息」也會列出 search hash 相同的圖片,方便共用回應與標記分類
現在 chatbot 可以正常查詢圖片並且回覆查核回應囉~

g0v.hackmd.io

20220907 會議記錄 - HackMD

🌸 1
cai 16:59:57
嘉義地檢署有澄清
https://www.cyc.moj.gov.tw/media/293283/1110907%E5%98%89%E6%AA%A2%E5%B0%8D%E6%96%BC%E7[…]%BE%84%E6%B8%85%E6%96%B0%E8%81%9E%E7%A8%BF.pdf?mediaDL=true
> 本署起訴書並無網友所 言認定「阿嬤年邁體弱禁不起暴打」等內容。
2
mrorz 19:12:40
ID hash 一樣,但 search hash 不一樣的特例
https://cofacts.tw/article/XYpMCIMBv5it-Cx_CYnd
https://cofacts.tw/article/v4oJHIMBv5it-Cx_Ops9
image.png
Mar Marín 21:25:26
@mar has joined the channel

2022-09-09

github2 14:24:56

<https://github.com/cofacts/rumors-line-bot/issues/322|#322 Handle duplicate image messaages>

In <https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#Case-%E7%99%BD%E8%9D%99%E8%9D%A0|20220907 meeting> we discussed several cases when users may submit images that is highly similar to existing images in the database. We will use this ticket to track the issue and see if we should mitigate this issue further (such as using image hash as article hash; don't change article ID if we change hashing algorithm)

github2 14:24:56

<https://github.com/cofacts/rumors-line-bot/issues/322|#322 Handle duplicate image messaages>

In <https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg#Case-%E7%99%BD%E8%9D%99%E8%9D%A0|20220907 meeting> we discussed several cases when users may submit images that is highly similar to existing images in the database. We will use this ticket to track the issue and see if we should mitigate this issue further (such as using image hash as article hash; don't change article ID if we change hashing algorithm)

2022-09-10

mrorz 19:37:27
9/8 release 過後 error rate 上升了
主要是 `could_not_connect`
原因不明
image.png
image.png

2022-09-11

2022-09-12

2022-09-14

chihao 11:15:49
Cofacts 的大家好!IORG(台灣資訊環境研究中心 https://iorg.tw )今年針對 2018-2022 資訊操弄對台灣選舉及公共討論的影響做了文獻回顧及訪談,最近完成研究成果及政策建議的初稿,接下來希望用焦點團體訪談徵求各界意見。最近一場焦點訪談安排在 9/23 下週五 1330,地點在台北車站附近,不知道有沒有 cofacts 的貢獻者想來參加?根據我長期在這裡潛水的經驗⋯不知道 @iacmai 會不會有時間來參加?XD 因為我並不認識太多人,有興趣參加的 cofacts 貢獻者都請務必跟我聯絡!
謝謝邀約,我有事不會去~
@iacmai 感謝回覆!如果你可以幫忙的話,歡迎推坑其他人!XD
🙌 1
chihao 11:15:49
Cofacts 的大家好!IORG(台灣資訊環境研究中心 https://iorg.tw )今年針對 2018-2022 資訊操弄對台灣選舉及公共討論的影響做了文獻回顧及訪談,最近完成研究成果及政策建議的初稿,接下來希望用焦點團體訪談徵求各界意見。最近一場焦點訪談安排在 9/23 下週五 1330,地點在台北車站附近,不知道有沒有 cofacts 的貢獻者想來參加?根據我長期在這裡潛水的經驗⋯不知道 @iacmai 會不會有時間來參加?XD 因為我並不認識太多人,有興趣參加的 cofacts 貢獻者都請務必跟我聯絡!
謝謝邀約,我有事不會去~
@iacmai 感謝回覆!如果你可以幫忙的話,歡迎推坑其他人!XD
mrorz 13:32:21
我要來把 staging 資料庫
洗成週日 production 的 backup 的樣子囉
Staging 上面現在是 2022/9/11 production snapshot,加上過往 8900 篇圖片訊息的傳送數據唷

今晚會測試~
mrorz 13:32:21
我要來把 staging 資料庫
洗成週日 production 的 backup 的樣子囉
Staging 上面現在是 2022/9/11 production snapshot,加上過往 8900 篇圖片訊息的傳送數據唷

今晚會測試~
mrorz 14:51:01
Staging 上面現在是 2022/9/11 production snapshot,加上過往 8900 篇圖片訊息的傳送數據唷

今晚會測試~
github2 20:00:25

<https://github.com/cofacts/rumors-site/pull/504#issuecomment-1246659778|Comment on #504 [LandingPage] update dead link of news>

<https://coveralls.io/builds/52461612|Coverage Status> Coverage remained the same at 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/1ae4bb1fb0c588bd7647795f0285791aae37d6ac|1ae4bb1> on update-news* into *<https://github.com/cofacts/rumors-site/commit/caa63930809eb36795f878acd355ab9846a48823|caa6393> on master*.

github2 20:00:25

<https://github.com/cofacts/rumors-site/pull/504#issuecomment-1246659778|Comment on #504 [LandingPage] update dead link of news>

<https://coveralls.io/builds/52461612|Coverage Status> Coverage remained the same at 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/1ae4bb1fb0c588bd7647795f0285791aae37d6ac|1ae4bb1> on update-news* into *<https://github.com/cofacts/rumors-site/commit/caa63930809eb36795f878acd355ab9846a48823|caa6393> on master*.

2022-09-15

github2 02:07:21

<https://github.com/cofacts/rumors-line-bot/issues/323|#323 Button of choosing reply always expires>

*Steps to reproduce* 1. Send the following text: &gt; 蔡英文的堂弟 蔡世能 :在桃園成立大日本帝國,希望“重建日本政府” &gt; &gt; 若是沒有蔡英文的認同與支持,他敢這樣幹!? 2. See the reply list, choose any reply *Expected* User should be able to read reply after choosing reply *Actual* "Button has been expired" error is shown after choosing reply <https://user-images.githubusercontent.com/108608/190229739-b75c64ae-f0e5-4ce0-b881-fa3ce36a4124.png|image>

github2 02:07:21

<https://github.com/cofacts/rumors-line-bot/issues/323|#323 Button of choosing reply always expires>

*Steps to reproduce* • Send the following text: &gt; 蔡英文的堂弟 蔡世能 :在桃園成立大日本帝國,希望“重建日本政府” &gt; &gt; 若是沒有蔡英文的認同與支持,他敢這樣幹!? • See the reply list *Expected* User should be able to read reply when choosing reply *Actual* "Button has been expired" error is shown <https://user-images.githubusercontent.com/108608/190229739-b75c64ae-f0e5-4ce0-b881-fa3ce36a4124.png|image>

github2 13:37:28

<https://github.com/cofacts/rumors-line-bot/issues/323#issuecomment-1247605461|Comment on #323 Button of choosing reply always expires>

Seems that context is empty after providing text that has 100% match. <https://user-images.githubusercontent.com/108608/190322130-3ffe80ec-704f-43aa-a2c6-6f927bd86df1.png|image> It is supposed to have at least a `data` attribute and a new `sessionId`. No `data` in context will trigger <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/index.js#L158-L170|this logic>, responding that the button is expired. Note that the action buttons do have `sessionId` in its postback data, so `data` is passed to `choosingArticle` handler correctly. Then what happens <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/choosingArticle.js#L365|when `choosingArticle` returns its `data`>? Still needs further investigation.

github2 13:37:28

<https://github.com/cofacts/rumors-line-bot/issues/323#issuecomment-1247605461|Comment on #323 Button of choosing reply always expires>

Seems that context is empty after providing text that has 100% match. <https://user-images.githubusercontent.com/108608/190322130-3ffe80ec-704f-43aa-a2c6-6f927bd86df1.png|image> It is supposed to have at least a `data` attribute and a new `sessionId`. No `data` in context will trigger <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/index.js#L158-L170|this logic>, responding that the button is expired. Note that the action buttons do have `sessionId` in its postback data, so `data` is passed to `choosingArticle` handler correctly. Then what happens <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/choosingArticle.js#L365|when `choosingArticle` returns its `data`>? Still needs further investigation.

github2 13:42:25

<https://github.com/cofacts/rumors-line-bot/issues/323#issuecomment-1247608171|Comment on #323 Button of choosing reply always expires>

Root cause: `handlePostback`, a function that returns `{context: data}`, is used in handlers that should return `{data}`.

我想到 root cause 了 @acerxp511
請看看 proposed solution 是否合理
滿 tricky 的,只有在「只有一個高相似度訊息」或「選中的訊息只有一則回應」時,會踩到這個 bug
我們在測試的時候不一定會選中這種訊息來測
github2 13:42:25

<https://github.com/cofacts/rumors-line-bot/issues/323#issuecomment-1247608171|Comment on #323 Button of choosing reply always expires>

*Root cause* `handlePostback`, a function that returns `{context: data}`, is used in handlers that should return `{data}`. 1. `handleInput`, `handlePostback` and `processImage` are top-level functions that returns `{context, replies}` for `singleUserHandler` to set redis context and submit replies. 2. These functions calls handlers such as `initState` and `choosingArticle`, who returns data in `{data, replies, ...}` format. 3. However, in `initState` and `choosingArticle`, in some scenarios we may return results from `handlePostback`. • The caller of `initState` expects a result in the form `{data, replies, ...}` but in this case it returns `{context, replies}` • The caller tries to grab `data` (which is `undefined` in this case) and put in `context`, thus the context is dropped. 4. After context is dropped, any postback action will trigger <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/index.js#L158-L170|this logic>, rendering the "button is expired" error. 5. In the unit test, we mock the return result of `handlePostback` all together, so that we cannot spot this issue. *Suggested fix* 1. In the context of handlers such as `initState` and `choosingArticle`, instead of calling `handlePostback({data}, NEXT_ACTION)`, we should call the handler for the `NEXT_ACTION` and return its result. This ensures that the signature stays the same. 2. We do not mock the called handler in unit test so that we can inspect the response of the called handler. Although the snapshot may overlap and changes to the called handler may incur multiple snapshot changes, we can at least see if the full response is as expected. *Impact* • `handlePostback({ data }, 'CHOOSING_ARTICLE', event, userId)` In `initState` under condition `edgesSortedWithSimilarity.length === 1 &amp;&amp; hasIdenticalDocs` • --&gt; If there is only 1 identical text, the resulting buttons have no context and always yields "button is expired" error • Example: the example in the ticket description • `handlePostback({ data }, 'CHOOSING_REPLY', event, userId)` in `choosingArticle` under condition `articleReplies.length === 1` • --&gt; if there is only 1 reply, the "current context" will be dropped. If user chooses another article in the same search session, the LINE bot will respond with "expired button" error • Example: <https://user-images.githubusercontent.com/108608/190326939-478883ab-12f7-4f86-9a5d-68b70e7ec28b.png|image>

我想到 root cause 了 @acerxp511
請看看 proposed solution 是否合理
滿 tricky 的,只有在「只有一個高相似度訊息」或「選中的訊息只有一則回應」時,會踩到這個 bug
我們在測試的時候不一定會選中這種訊息來測

2022-09-16

cai 00:02:09
https://cofacts.tw/article/cknhykse9szv 租金補貼這電話查了前面幾碼028995是行政院新莊聯合辦公大樓,營建署在這邊是下水道工程處欸
對呀看起來就好可疑
cai 00:02:09
https://cofacts.tw/article/cknhykse9szv
https://cofacts.tw/article/2gpce9z9j6jg9
租金補貼這電話查了前面幾碼028995是行政院新莊聯合辦公大樓,營建署在這邊是下水道工程處欸
為什麼不是給總機再加分機這種好查的,給直撥電話難怪被懷疑
對呀看起來就好可疑
👍 1
cai 15:09:05
https://cofacts.tw/article/A4riQ4MBv5it-Cx_Q8Cx 八卦板也有這張,配色很像舊版疾管署的簡報配色(最近的配色看行政院記者會有改)
早上的新聞 說是草案 ,剛剛記者會也有提到,沒聽清楚
https://heho.com.tw/archives/240907
cai 15:09:05
https://cofacts.tw/article/A4riQ4MBv5it-Cx_Q8Cx 八卦板也有這張,配色很像舊版疾管署的簡報配色(最近的配色看行政院記者會有改)
早上的新聞 說是草案 ,剛剛記者會也有提到,沒聽清楚
https://heho.com.tw/archives/240907
cai 15:28:24
https://cofacts.tw/article/1rnb57l4c8r3n
這篇查了FB得到tiktok影片 https://www.tiktok.com/@sukhoic/video/7137148751164050715
備份1 備份2
留言有說是在桃園八德廣興國小前 https://goo.gl/maps/uYRhdkbMPQktovMYA
是偵測車速的「車速微笑偵測提醒系統」,桃園限定
全台首創車速微笑偵測提醒系統,以人性化的方式降低超速比率
之前有回過 https://cofacts.tw/reply/AqjPxHUB9w1KR1IkQSeX
資訊不知道有沒有更新
好問題,當時應該沒有後面的攝影裝置 lol
看來即使有加裝了攝影機,也還沒跟罰單連動唷
https://tfc-taiwan.org.tw/articles/8232
cai 15:28:24
https://cofacts.tw/article/1rnb57l4c8r3n
這篇查了FB得到tiktok影片 https://www.tiktok.com/@sukhoic/video/7137148751164050715
備份1 備份2
留言有說是在桃園八德廣興國小前 https://goo.gl/maps/uYRhdkbMPQktovMYA
是偵測車速的「車速微笑偵測提醒系統」,桃園限定
全台首創車速微笑偵測提醒系統,以人性化的方式降低超速比率
之前有回過 https://cofacts.tw/reply/AqjPxHUB9w1KR1IkQSeX
資訊不知道有沒有更新
好問題,當時應該沒有後面的攝影裝置 lol
看來即使有加裝了攝影機,也還沒跟罰單連動唷
https://tfc-taiwan.org.tw/articles/8232

2022-09-18

cai 22:41:36
地震系列文再次浮起
cai 22:41:36
地震系列文再次浮起

2022-09-19

mrorz 14:36:39
地震陰謀論
https://cofacts.tw/article/36js3s1r5gtbr
感謝提供,已經更新
這篇是講核爆的,剛好與謠言提到「軍事技術引起的人工地震,則不會產生P波」相反www
只是原文提到的軍事技術不知道是否指的是核爆了
😢 2
mrorz 14:36:39
地震陰謀論
https://cofacts.tw/article/36js3s1r5gtbr
感謝提供,已經更新
這篇是講核爆的,剛好與謠言提到「軍事技術引起的人工地震,則不會產生P波」相反www
只是原文提到的軍事技術不知道是否指的是核爆了

2022-09-20

cai 13:57:56
cofacts 又被提到了
https://new7.storm.mg/article/4516733
https://new7.storm.mg/article/4516558

new7.storm.mg

假訊息.自救》不實謠言滲透台灣社會!該如何分辨假消息?事實查核團體3招教你破解-新新聞

假訊息從文字、圖片變型成影音、語音,甚至還有難以辨識的深偽變造(deepfake),除了靠政府查緝、開罰,以及事實查核機構連日研究提供報告,面對日常生活中的假訊息,我們有什麼方法可以應對?就在2022年九合一大選的參選人登記當周,法務部調查局舉辦「選舉查察工作」誓

new7.storm.mg

假訊息.現象》遭假訊息侵擾台灣蟬聯九年世界冠軍!三類謠言在選戰中發酵 中國在台資訊操弄主軸全揭露-新新聞

台灣自2018年以來的選舉受到假訊息影響深遠,距離年底九合一大選還有70天,從過去4年多次投票的經驗當中,假訊息經常以哪些形式出現,又怎麼影響我們的思考與判斷?中秋假期除了早有4年前就傳出的「柚子和優酪乳一起吃會中毒」的謠言廣傳,健康、疫情、國防類假訊息也在臉書社

感謝提供,記錄在 aJC_yNdpSLKmstvfJgUAsA
1
cai 21:59:19
https://cofacts.tw/article/1yogxocp9blpe
https://cofacts.tw/article/jymc4z41fe9m
去查了0917的氣象局記者會直播 主任講的是規模5,沒有7級8級
不太可能是0918吧?
> 「中央山脈斷層」昨日被關山地震啟動
這個好像也沒出現在主任的說詞
這個斷層似乎還有一些分歧
https://e-info.org.tw/node/235013
> 中央氣象局地震預報主任
> 中央氣象局地震預報
這也是錯的,那是「中央氣象局地震測報中心」不是預報 XDD
把文字直接丟網路搜尋也只有得到cofacts的網頁,FB查不到
cai 21:59:19
https://cofacts.tw/article/1yogxocp9blpe
https://cofacts.tw/article/jymc4z41fe9m
去查了0917的氣象局記者會直播 主任講的是規模5,沒有7級8級
不太可能是0918吧?
> 「中央山脈斷層」昨日被關山地震啟動
這個好像也沒出現在主任的說詞
這個斷層似乎還有一些分歧
https://e-info.org.tw/node/235013
> 中央氣象局地震預報主任
> 中央氣象局地震預報
這也是錯的,那是「中央氣象局地震測報中心」不是預報 XDD
把文字直接丟網路搜尋也只有得到cofacts的網頁,FB查不到
👍 1

2022-09-21

mrorz 12:23:17
今日議程
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FIqCOZMZLRe-JPMSJIV3yRQ

HackMD

Cofacts 會議記錄 - HackMD

# Cofacts 會議記錄 ## 2022 - [20220921 會議記錄](/IqCOZMZLRe-JPMSJIV3yRQ) - [20220914 會議記錄](/vl_7BJq1RsGb

github2 13:35:54

<https://github.com/cofacts/rumors-line-bot/pull/324#issuecomment-1253227687|Comment on #324 Fix issue choosing reply button expire>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52637636|Build 3095429439>* • *5* of *5* *(100.0%)* changed or added relevant lines in *4* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.02%*) to *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 13:35:54

<https://github.com/cofacts/rumors-line-bot/pull/324#issuecomment-1253227687|Comment on #324 Fix issue choosing reply button expire>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52637636|Build 3095429439>* • *5* of *5* *(100.0%)* changed or added relevant lines in *4* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.02%*) to *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

cai 13:59:19
https://cofacts.tw/article/3abh8widcmel5
好多人問,這影片複合好多健康類謠言,這要怎麼拆 😥
標題跟開頭講神尾哲男,後面講的番茄、綠茶、紅薯(地瓜)、紅辣椒 、西蘭花(綠花椰菜) 、玉米 、海帶抗癌,又講茄子跟茄子料理
神尾哲男的書籍介紹,影片後面提到的蔬果跟書所提的內容無關
😢 2
cai 13:59:19
https://cofacts.tw/article/3abh8widcmel5
好多人問,這影片複合好多健康類謠言,這要怎麼拆 😥
標題跟開頭講神尾哲男,後面講的番茄、綠茶、紅薯(地瓜)、紅辣椒 、西蘭花(綠花椰菜) 、玉米 、海帶抗癌,又講茄子跟茄子料理
神尾哲男的書籍介紹,影片後面提到的蔬果跟書所提的內容無關
github2 14:14:41

Review on #324 Fix issue choosing reply button expire

LGTM! Thanks for the fix :pray:

github2 14:14:41

Review on #324 Fix issue choosing reply button expire

LGTM! Thanks for the fix :pray:

2022-09-22

mrorz 00:15:08
🚧 Cofacts 工作小組將會在今日(2022/9/22)凌晨 1:30 am~2:30 am 間執行資料遷移作業,屆時 Cofacts 真的假的網站與 LINE bot 將會在這區間的恰當時機下線 15 分鐘,造成不便敬請見諒。

g0v.hackmd.io

20220914 會議記錄 - HackMD

data migration 完成,8000 份舊圖已經在 Cofacts 主站上囉(須指定 `articleTypes` 才看得到)
https://cofacts.tw/articles?articleTypes=IMAGE&orderBy=replyRequestCount
mrorz 00:15:08
🚧 Cofacts 工作小組將會在今日(2022/9/22)凌晨 1:30 am~2:30 am 間執行資料遷移作業,屆時 Cofacts 真的假的網站與 LINE bot 將會在這區間的恰當時機下線 15 分鐘,造成不便敬請見諒。
data migration 完成,8000 份舊圖已經在 Cofacts 主站上囉(須指定 `articleTypes` 才看得到)
https://cofacts.tw/articles?articleTypes=IMAGE&orderBy=replyRequestCount
cai 18:06:38
memo 有氣象局圖示的圖卡找法
氣象相關圖卡→報天氣 FB
地震相關圖卡→報地震 FB
cai 18:06:38
memo 有氣象局圖示的圖卡找法
氣象相關圖卡→報天氣 FB
地震相關圖卡→報地震 FB
1

2022-09-23

github2 13:12:17

<https://github.com/cofacts/rumors-line-bot/pull/325|#325 Remove mongo client closing logic>

because it is done in setup-jest instead in <https://github.com/cofacts/rumors-line-bot/commit/71b69a7575b67b5994e03a34600751b4a7340091|71b69a7>

:white_check_mark: All checks have passed

github2 13:14:18

<https://github.com/cofacts/rumors-line-bot/pull/325#issuecomment-1255808567|Comment on #325 Remove mongo client closing logic>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52703891|Build 3110520753>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 13:14:18

<https://github.com/cofacts/rumors-line-bot/pull/325#issuecomment-1255808567|Comment on #325 Remove mongo client closing logic>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52703891|Build 3110520753>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 13:24:32

<https://github.com/cofacts/rumors-line-bot/issues/326|#326 Cannot choose "no such message" when searching for images>

<https://user-images.githubusercontent.com/108608/191896120-79b7d4f9-a313-44ee-8434-50ba1eeb8ff5.png|image> *Root cause* In <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/choosingArticle.js#L50-L74|`POSTBACK_NO_ARTICLE_FOUND` logic> of `choosingArticle` handler, we currently do not handle images properly. *TODO* • Copy the <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/processImage.js#L252-L265|current not-found reply> ("I am sorry you cannot find...") in `processImage` to `choosingArticle` • Update the <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/processImage.js#L259-L261|wording of not-found reply in `processImage`> to something like "Unfortunately, I currently don’t recognize..." in <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/initState.js#L311|initState>. • The current wording in `processImage` is actually the 'not found' reply for text when choosing article.

github2 13:24:32

<https://github.com/cofacts/rumors-line-bot/issues/326|#326 Cannot choose "no such message" when searching for images>

As found in <https://g0v.hackmd.io/IqCOZMZLRe-JPMSJIV3yRQ#%E6%B2%92%E6%9C%89%E5%AF%A6%E4%BD%9C%E3%80%8C%E6%89%BE%E4%B8%8D%E5%88%B0%E6%88%91%E6%83%B3%E6%9F%A5%E7%9A%84%E8%A8%8A%E6%81%AF%E3%80%8D|20220921 meeting>, the following button does not work: <https://user-images.githubusercontent.com/108608/191896120-79b7d4f9-a313-44ee-8434-50ba1eeb8ff5.png|image> *Root cause* In <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/choosingArticle.js#L50-L74|`POSTBACK_NO_ARTICLE_FOUND` logic> of `choosingArticle` handler, we currently do not handle images properly. *Proposed solution* Should do both of the following: • Copy the <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/processImage.js#L252-L265|current not-found reply> ("I am sorry you cannot find...") from `processImage` to `choosingArticle` • separate image handling logic from text handling logic within `choosingArticle` • Update the <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/processImage.js#L259-L261|wording of not-found reply in `processImage`> to something like "Unfortunately, I currently don’t recognize..." in <https://github.com/cofacts/rumors-line-bot/blob/master/src/webhook/handlers/initState.js#L311|initState>. • The current wording in `processImage` is actually the 'not found' reply for text when choosing article.

github2 13:33:37

<https://github.com/cofacts/rumors-line-bot/issues/327|#327 Cannot record feedback in certain state>

From <https://g0v.hackmd.io/IqCOZMZLRe-JPMSJIV3yRQ#Feedback-%E7%84%A1%E6%B3%95%E7%B4%80%E9%8C%84|20220921 meeting> *Steps to reproduce* 1. 給一圖,觸發兩則圖 A, B 2. 先選一個有多個回應的圖 A,但不選回應 3. 捲回去選單一回應的圖 B,觸發回應 4. 捲回去挑一個 A 的回應顯示 5. 對該回應按「有用」或「沒用」 6. 按關閉,會出現「無法紀錄您的評價」 <https://user-images.githubusercontent.com/108608/191897488-87dae2c5-2531-4c8a-a8b0-d01a5aba7b71.png|image> <https://user-images.githubusercontent.com/108608/191897504-9496c8a1-bc17-4e64-b861-61e4c2098d89.png|image> <https://user-images.githubusercontent.com/108608/191897512-7783dac7-cf69-4b17-bcd1-5005984e5c40.png|image>

github2 13:33:37

<https://github.com/cofacts/rumors-line-bot/issues/327|#327 Cannot record feedback in certain state>

From <https://g0v.hackmd.io/IqCOZMZLRe-JPMSJIV3yRQ#Feedback-%E7%84%A1%E6%B3%95%E7%B4%80%E9%8C%84|20220921 meeting> *Steps to reproduce* 1. 給一圖,觸發兩則圖 A, B 2. 先選一個有多個回應的圖 A,但不選回應 3. 捲回去選單一回應的圖 B,觸發回應 4. 捲回去挑一個 A 的回應顯示 5. 對該回應按「有用」或「沒用」 6. 按關閉,會出現「無法紀錄您的評價」 <https://user-images.githubusercontent.com/108608/191897488-87dae2c5-2531-4c8a-a8b0-d01a5aba7b71.png|image> <https://user-images.githubusercontent.com/108608/191897504-9496c8a1-bc17-4e64-b861-61e4c2098d89.png|image> <https://user-images.githubusercontent.com/108608/191897512-7783dac7-cf69-4b17-bcd1-5005984e5c40.png|image>

github2 15:13:22

<https://github.com/cofacts/rumors-line-bot/pull/328|#328 docs: fix hyperlink>

The `LINE official tutorial` link at `README.md` isn't valid anymore.

github2 15:13:22

<https://github.com/cofacts/rumors-line-bot/pull/328|#328 docs: fix hyperlink>

The `LINE official tutorial` link at `README.md` isn't valid anymore.

github2 15:52:28

Review on #328 docs: fix hyperlink

Thanks for updating the link! :muscle:

github2 15:52:28

Review on #328 docs: fix hyperlink

Thanks for updating the link! :muscle:

github2 15:55:03

<https://github.com/cofacts/rumors-line-bot/pull/328#issuecomment-1255902275|Comment on #328 docs: fix hyperlink>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52705988|Build 3110979112>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 15:55:03

<https://github.com/cofacts/rumors-line-bot/pull/328#issuecomment-1255902275|Comment on #328 docs: fix hyperlink>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52705988|Build 3110979112>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:25:52

<https://github.com/cofacts/rumors-line-bot/pull/329|#329 fix: incorrect thank-you message>

Closes <https://github.com/cofacts/rumors-line-bot/issues/320|#320>.

github2 16:25:52

<https://github.com/cofacts/rumors-line-bot/pull/329|#329 fix: incorrect thank-you message>

Closes <https://github.com/cofacts/rumors-line-bot/issues/320|#320>.

:white_check_mark: All checks have passed

github2 16:27:57

<https://github.com/cofacts/rumors-line-bot/pull/329#issuecomment-1255932478|Comment on #329 fix: incorrect thank-you message>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52706596|Build 3111362375>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:27:57

<https://github.com/cofacts/rumors-line-bot/pull/329#issuecomment-1255932478|Comment on #329 fix: incorrect thank-you message>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52706596|Build 3111362375>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:48:37

<https://github.com/cofacts/rumors-line-bot/pull/330|#330 docs: fix hyperlink>

Fix broken LINE developer links.

:white_check_mark: All checks have passed

github2 16:50:37

<https://github.com/cofacts/rumors-line-bot/pull/330#issuecomment-1255952358|Comment on #330 docs: fix hyperlink>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52707084|Build 3111485211>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 16:50:37

<https://github.com/cofacts/rumors-line-bot/pull/330#issuecomment-1255952358|Comment on #330 docs: fix hyperlink>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52707084|Build 3111485211>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 18:06:59

<https://github.com/cofacts/rumors-line-bot/pull/331|#331 fix: `COFACTS_API_URL` is unnecessary>

We should replace `COFACTS_API_URL` with `/graphql`, otherwise `getArticlesFromCofacts` will be blocked by CORS.

:white_check_mark: All checks have passed

github2 18:06:59

<https://github.com/cofacts/rumors-line-bot/pull/331|#331 fix: `COFACTS_API_URL` is unnecessary>

We should replace `COFACTS_API_URL` with `/graphql`, otherwise the local development will fail.

github2 18:08:49

<https://github.com/cofacts/rumors-line-bot/pull/331#issuecomment-1256025507|Comment on #331 fix: `COFACTS_API_URL` is unnecessary>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52708680|Build 3111950811>* • *1* of *1* *(100.0%)* changed or added relevant line in *1* file are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 18:08:49

<https://github.com/cofacts/rumors-line-bot/pull/331#issuecomment-1256025507|Comment on #331 fix: `COFACTS_API_URL` is unnecessary>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52708747|Build 3111962803>* • *1* of *1* *(100.0%)* changed or added relevant line in *1* file are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

2022-09-24

cai 11:15:22
https://cofacts.tw/article/3oqzghsaf3ywu
https://cofacts.tw/article/34upakgymhnci 這篇又說新聞都沒報了w
FB搜尋
其中一個影片來源: https://www.tiktok.com/@aa666363/video/7145972751235304731

TikTok

@aa666363 &#9836; &#19968;&#29983;&#20804;&#24351;&#22823;&#36807;&#22825; - &#26472;&#20811;&#24847;

新聞有影片的是中時跟中天
真妙
剛才回掉了,看之後反應 XD
這系列可以跟之前920退警團體遊行系列一起觀察,共同點是中天有影片
以前看到媒體都沒報會覺得是假的,但是920退警遊行這個很怪,9/19很多家報導,9/20當天的反而少,跟以前不太同,是因為零衝突、沒候選人所以沒什麼記者想衝現場嗎?
這系列可以跟之前920退警團體遊行系列一起觀察,共同點是中天有影片
以前看到媒體都沒報會覺得是假的,但是920退警遊行這個很怪,9/19很多家報導,9/20當天的反而少,跟以前不太同,是因為零衝突、沒候選人所以沒什麼記者想衝現場嗎?
那個時候大家都在衝地震消息吧
就活動慘遭蓋台
如果我是新聞室主管
當然會想跑地震
注意力也都放在地震測報中心說未來有沒有餘震之類
的確那幾天新聞都是地震相關的
還有什麼中央山脈斷層的
不只發生一次了
是看準周一上班才有人澄清吧w
cai 11:15:22
https://cofacts.tw/article/3oqzghsaf3ywu
https://www.facebook.com/search/top/?q=%E5%91%82%E7%A7%80%E8%93%AE%E5%B8%B6%E9%A0%AD%E5%8F%8D%E8%8F%9C%E7%9A%84%E5%A4%A7%E9%81%8A%E8%A1%8C
其中一個影片來源: https://www.tiktok.com/@aa666363/video/7145972751235304731
新聞有影片的是中時跟中天
真妙
剛才回掉了,看之後反應 XD
這系列可以跟之前920退警團體遊行系列一起觀察,共同點是中天有影片
以前看到媒體都沒報會覺得是假的,但是920退警遊行這個很怪,9/19很多家報導,9/20當天的反而少,跟以前不太同,是因為零衝突、沒候選人所以沒什麼記者想衝現場嗎?
這系列可以跟之前920退警團體遊行系列一起觀察,共同點是中天有影片
以前看到媒體都沒報會覺得是假的,但是920退警遊行這個很怪,9/19很多家報導,9/20當天的反而少,跟以前不太同,是因為零衝突、沒候選人所以沒什麼記者想衝現場嗎?
那個時候大家都在衝地震消息吧
就活動慘遭蓋台
如果我是新聞室主管
當然會想跑地震
注意力也都放在地震測報中心說未來有沒有餘震之類
的確那幾天新聞都是地震相關的
還有什麼中央山脈斷層的
不只發生一次了
是看準周一上班才有人澄清吧w
cai 14:45:31
這系列可以跟之前920退警團體遊行系列一起觀察,共同點是中天有影片
以前看到媒體都沒報會覺得是假的,但是920退警遊行這個很怪,9/19很多家報導,9/20當天的反而少,跟以前不太同,是因為零衝突、沒候選人所以沒什麼記者想衝現場嗎?
github2 15:16:26

<https://github.com/cofacts/community-builder/pull/13|#13 [BigNum] add comment count>

• Add comment count panel • Apply `website` filter to feedbacks and reply-requests so that numbers only show website user contributions • Better match the contributor on site • Adjust order to feedback &gt; comment &gt; reply so that it corresponds to meetup's introductionary order <https://user-images.githubusercontent.com/108608/192085333-b0bc0938-ee0e-4b49-a27b-2cec3b6396ae.png|image> <https://user-images.githubusercontent.com/108608/192085307-c549a74a-3db9-48a1-88ca-06301a65df77.png|image>

:white_check_mark: All checks have passed

github2 15:16:26

<https://github.com/cofacts/community-builder/pull/13|#13 [BigNum] add comment count>

• Add comment count panel • Apply `website` filter to feedbacks and reply-requests so that numbers only show website user contributions • Better match the contributor on site • Adjust order to feedback &gt; comment &gt; reply so that it corresponds to meetup's introductionary order <https://user-images.githubusercontent.com/108608/192085333-b0bc0938-ee0e-4b49-a27b-2cec3b6396ae.png|image> <https://user-images.githubusercontent.com/108608/192085307-c549a74a-3db9-48a1-88ca-06301a65df77.png|image>

github2 16:00:21

Review on #331 fix: `COFACTS_API_URL` is unnecessary

Thanks for the refactor! The constant `COFACTS_API_URL` was introduced before we stitch chatbot GraphQL and cofacts-api GraphQL together. Personally I did not spot such CORS issue because we setup our staging API to allow domains such as localhost:5001 and my personal ngrok URL. Since we have made Cofacts API available via chatbot GraphQL server, It is great to move forward without the constant. One thing to note is that we can probably drop `APP_ID` env and `x-app-id` header as well. Query used in `getArticlesFromCofacts()` does not require authentication, and Chatbot GraphQL does not forward `x-app-id` header either.

github2 16:00:21

Review on #331 fix: `COFACTS_API_URL` is unnecessary

Thanks for the refactor! The constant `COFACTS_API_URL` was introduced before we stitch chatbot GraphQL and cofacts-api GraphQL together. Personally I did not spot such CORS issue because we setup our staging API to allow domains such as localhost:5001 and my personal ngrok URL. Since we have made Cofacts API available via chatbot GraphQL server, It is great to move forward without such constant. One thing to note is that we can probably drop `APP_ID` env and `x-app-id` header as well. Query used in `getArticlesFromCofacts()` does not require authentication, and Chatbot GraphQL does not forward `x-app-id` header either.

isabelhou 16:12:08
@bil da0在討論要用哪些協作工具?想問一下cofacts的經驗?https://g0v.hackmd.io/HZRP0xVjTj60z4npVSsMtg
我打不開耶、要說說什麼方向呢
@bil 忘記調模式了。我有先放揪松的工具,就簡單列工具就可以。
• Hackmd 作為討論紀錄 work journal、technical design doc 的 knowledge base,以 hackmd book mode 彙整在一起
• 對外使用 hackfoldr (因為當時 hackmd 還沒有 bookmode 或是 bookmode 還不能自訂 URL)
• 確定要開發的 item 會在對應的 github repo 開票
• 帶狀的專案,在 breakdown 成 github 票之後,還會在
太感謝了。
isabelhou 16:12:08
@bil da0在討論要用哪些協作工具?想問一下cofacts的經驗?https://g0v.hackmd.io/HZRP0xVjTj60z4npVSsMtg
我打不開耶、要說說什麼方向呢
@bil 忘記調模式了。我有先放揪松的工具,就簡單列工具就可以。
• Hackmd 作為討論紀錄 work journal、technical design doc 的 knowledge base,以 hackmd book mode 彙整在一起
• 對外使用 hackfoldr (因為當時 hackmd 還沒有 bookmode 或是 bookmode 還不能自訂 URL)
• 確定要開發的 item 會在對應的 github repo 開票
• 帶狀的專案,在 breakdown 成 github 票之後,還會在
太感謝了。

2022-09-25

PARALELL 17:12:25
@zx754615 has joined the channel
Hao Nien 21:25:05
@kennith8 has joined the channel
Hao Nien 21:25:26
hello
Hao Nien 21:25:26
hello
Hao Nien 21:26:19
I just joined gathering this afternoon
🙌 1
Hao Nien 21:26:19
I just joined gathering this afternoon

2022-09-26

github2 02:03:00

<https://github.com/cofacts/rumors-line-bot/pull/332|#332 Fix articles page pagination when there is no articles>

Currently empty articles page will trigger error due to 0 elements in `edges`. After this PR, empty edges will not trigger error. `&lt;Pagination /&gt;` should render nothing in this case. <https://user-images.githubusercontent.com/108608/192158253-f31581dd-9cd8-4d7e-9e60-91e17cac14d7.png|image>

:white_check_mark: All checks have passed

github2 02:03:00

<https://github.com/cofacts/rumors-line-bot/pull/332|#332 Fix articles page pagination when there is no articles>

Currently empty articles page will trigger error due to 0 elements in `edges`. After this PR, empty edges will not trigger error. <https://user-images.githubusercontent.com/108608/192158253-f31581dd-9cd8-4d7e-9e60-91e17cac14d7.png|image>

github2 02:05:01

<https://github.com/cofacts/rumors-line-bot/pull/332#issuecomment-1257246651|Comment on #332 Fix articles page pagination when there is no articles>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52737857|Build 3123134267>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 02:05:01

<https://github.com/cofacts/rumors-line-bot/pull/332#issuecomment-1257246651|Comment on #332 Fix articles page pagination when there is no articles>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52737857|Build 3123134267>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

cai 12:53:20
不只發生一次了
是看準周一上班才有人澄清吧w
1
mrorz 14:00:17
稍微把之前寫過的開發用文件整理成 hackmd book mode + 放到主要的 hackfoldr 裡
其實還滿多的
https://g0v.hackmd.io/@mrorz/cofacts-rd/
mrorz 14:00:17
稍微把之前寫過的開發用文件整理成 hackmd book mode + 放到主要的 hackfoldr 裡
其實還滿多的
https://g0v.hackmd.io/@mrorz/cofacts-rd/

HackMD

Cofacts reasearch &amp; design docs - HackMD

# Cofacts reasearch &amp; design docs :::info - Design docs: Implementation documents with requiremen

1

2022-09-27

github2 03:59:19

<https://github.com/cofacts/rumors-site/pull/505|#505 Bump degenerator and pm2>

Bumps <https://github.com/TooTallNate/node-degenerator|degenerator> to 3.0.2 and updates ancestor dependency <https://github.com/Unitech/pm2|pm2>. These dependencies need to be updated together. Updates `degenerator` from 2.2.0 to 3.0.2 Release notes _Sourced from <https://github.com/TooTallNate/node-degenerator/releases|degenerator's releases>._ &gt; *3.0.2* &gt; *Patches* &gt; &gt; • Update `vm2` to v3.9.8: f690e194041f9dacba5341d5a98bbd1a65996048 &gt; &gt; *3.0.1* &gt; *Patches* &gt; &gt; • Fix return `undefined`: ccc3445354135398b6eb1a04c7d27c13b833f2d5 &gt; • Fix `filename` option: 9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e &gt; &gt; *3.0.0* &gt; *Major Changes* &gt; &gt; • Remove "generator" output mode: <https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/12|#12> &gt; • Use `vm2` module to prevent privilege escalation of untrusted code: <https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/11|#11> &gt; &gt; *Minor Changes* &gt; &gt; • Add `any` default return type to `compile()`: e0b9fc83faabb101944b63bc73b710be7787f15b Commits • <https://github.com/TooTallNate/node-degenerator/commit/3b609557e46aca742bb2fcfc5ad8254cd599d633|`3b60955`> 3.0.2 • <https://github.com/TooTallNate/node-degenerator/commit/f690e194041f9dacba5341d5a98bbd1a65996048|`f690e19`> Update `vm2` to v3.9.8 • <https://github.com/TooTallNate/node-degenerator/commit/5cf4ab2eeacfa593e95ae84e4cc433592156088f|`5cf4ab2`> 3.0.1 • <https://github.com/TooTallNate/node-degenerator/commit/9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e|`9d25bb6`> Fix `filename` option • <https://github.com/TooTallNate/node-degenerator/commit/ccc3445354135398b6eb1a04c7d27c13b833f2d5|`ccc3445`> Fix return `undefined` • <https://github.com/TooTallNate/node-degenerator/commit/dc10ee9daa270157c19a16f7168fc42210f3355c|`dc10ee9`> 3.0.0 • <https://github.com/TooTallNate/node-degenerator/commit/e0b9fc83faabb101944b63bc73b710be7787f15b|`e0b9fc8`> Add `any` default return type to `compile()` • <https://github.com/TooTallNate/node-degenerator/commit/852043f9621f098ccf3a577a1d9a2ed0de20f402|`852043f`> Use `vm2` module to prevent privilege escalation of untrusted code (<https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/11|#11>) • <https://github.com/TooTallNate/node-degenerator/commit/7ad1041853551e393439003a10da56c605115652|`7ad1041`> Remove "generator" output mode (<https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/12|#12>) • See full diff in <https://github.com/TooTallNate/node-degenerator/compare/2.2.0...3.0.2|compare view> Updates `pm2` from 4.5.6 to 5.2.0 Release notes _Sourced from <https://github.com/Unitech/pm2/releases|pm2's releases>._ &gt; *5.2.0* &gt; &gt; • replace node-cron by croner (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5183|#5183> <https://github-redirect.dependabot.com/Unitech/pm2/issues/5035|#5035>) &gt; • upgrade mocha deps &gt; • fix pm2 report when daemon not running &gt; • remove semver check for legacy node.js versions &gt; • update node version in setup.deb.sh by using lts (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5201|#5201>) + openrc &gt; • replace legacy util._extend by Object.assign (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5239|#5239>) &gt; • add missing start options types (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5242|#5242>) &gt; • recursive detection of package.json (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5267|#5267>) &gt; • make tarball module uninstall cross-platform (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5269|#5269>) &gt; • Fix unnecessary "ENOENT" console.error when serving a spa (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5272|#5272>) &gt; • fix: used env variable instead of hardcode datetime format (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5277|#5277>) &gt; • copyright update (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5278|#5278>) &gt; • fix: remove constants import from VersionCheck (not needed) (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5279|#5279>) &gt; • Reduce async import (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5280|#5280>) &gt; &gt; *5.1.2* &gt; &gt; • cron-restart improvements &gt; &gt; *5.1.1* &gt; &gt; • add back Node 10.x support &gt; • make pm2-sysmonit module optional &gt; • remove fast-printf and replace with sprintfjs &gt; &gt; *5.0.3* &gt; &gt; • fixes for system monitoring &gt; &gt; *5.0.0* &gt; *System Monitoring* &gt; &gt; A new local system monitoring feature has been added, allowing to monitor numerous vital server metrics. &gt; &gt; Most important metrics will be displayed when doing a pm2 ls: &gt; &gt; ``` &gt; ┌─────┬─────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐ &gt; │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ &gt; ├─────┼─────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤ &gt; │ 4 │ app │ default │ 1.0.0 │ fork │ 164618 │ 2s │ 1670 │ online │ 0% │ 41.8mb │ unitech │ disabled │ &gt; └─────┴─────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘ &gt; host metrics | cpu: 1.6% 42.9º | mem free: 52.0% | wlp0s20f3: ⇓ 0mb/s ⇑ 0mb/s | disk: ⇓ 0.199mb/s ⇑ 0mb/s /dev/nvme0n1p3 88.25% | &gt; ``` &gt; &gt; All server metrics will be available to <http://pm2.io|pm2.io>: &gt; &gt; ``` &gt; ┌─────────────────────────────┬──────────────────────────────────┐ &gt; │ PM2 CPU Usage │ 0.0 % │ &gt; │ PM2 Memory Usage │ 67.4 mb │ &gt; │ PM2 Agent CPU Usage │ 0 % │ &gt; &lt;/tr&gt;&lt;/table&gt; &gt; ``` ... (truncated) Changelog _Sourced from <https://github.com/Unitech/pm2/blob/master/CHANGELOG.md|pm2's changelog>._ &gt; *5.2.0* &gt; &gt; • replace node-cron by croner (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5183|#5183> <https://github-redirect.dependabot.com/Unitech/pm2/issues/5035|#5035>) &gt; • upgrade mocha deps &gt; • fix pm2 report when daemon not running &gt; • remove semver check for legacy node.js versions &gt; • update node version in setup.deb.sh by using lts (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5201|#5201>) + openrc &gt; • replace legacy util._extend by Object.assign (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5239|#5239>) &gt; • add missing start options types (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5242|#5242>) &gt; • recursive detection of package.json (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5267|#5267>) &gt; • make tarball module uninstall cross-platform (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5269|#5269>) &gt; • Fix unnecessary "ENOENT" console.error when serving a spa (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5272|#5272>) &gt; • fix: used env variable instead of hardcode datetime format (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5277|#5277>) &gt; • copyright update (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5278|#5278>) &gt; • fix: remove constants import from VersionCheck (not needed) (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5279|#5279>) &gt; • Reduce async import (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5280|#5280>) &gt; &gt; *5.1.2* &gt; &gt; • easily disable cron-restart strategy via `$ pm2 restart --cron-restart 0` &gt; • allow to update cron-restart on restart &gt; &gt; *5.1.1* &gt; &gt; • remove fast-printf and replace w…

:white_check_mark: All checks have passed

github2 03:59:19

<https://github.com/cofacts/rumors-site/pull/505|#505 Bump degenerator and pm2>

Bumps <https://github.com/TooTallNate/node-degenerator|degenerator> to 3.0.2 and updates ancestor dependency <https://github.com/Unitech/pm2|pm2>. These dependencies need to be updated together. Updates `degenerator` from 2.2.0 to 3.0.2 Release notes _Sourced from <https://github.com/TooTallNate/node-degenerator/releases|degenerator's releases>._ &gt; *3.0.2* &gt; *Patches* &gt; &gt; • Update `vm2` to v3.9.8: f690e194041f9dacba5341d5a98bbd1a65996048 &gt; &gt; *3.0.1* &gt; *Patches* &gt; &gt; • Fix return `undefined`: ccc3445354135398b6eb1a04c7d27c13b833f2d5 &gt; • Fix `filename` option: 9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e &gt; &gt; *3.0.0* &gt; *Major Changes* &gt; &gt; • Remove "generator" output mode: <https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/12|#12> &gt; • Use `vm2` module to prevent privilege escalation of untrusted code: <https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/11|#11> &gt; &gt; *Minor Changes* &gt; &gt; • Add `any` default return type to `compile()`: e0b9fc83faabb101944b63bc73b710be7787f15b Commits • <https://github.com/TooTallNate/node-degenerator/commit/3b609557e46aca742bb2fcfc5ad8254cd599d633|`3b60955`> 3.0.2 • <https://github.com/TooTallNate/node-degenerator/commit/f690e194041f9dacba5341d5a98bbd1a65996048|`f690e19`> Update `vm2` to v3.9.8 • <https://github.com/TooTallNate/node-degenerator/commit/5cf4ab2eeacfa593e95ae84e4cc433592156088f|`5cf4ab2`> 3.0.1 • <https://github.com/TooTallNate/node-degenerator/commit/9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e|`9d25bb6`> Fix `filename` option • <https://github.com/TooTallNate/node-degenerator/commit/ccc3445354135398b6eb1a04c7d27c13b833f2d5|`ccc3445`> Fix return `undefined` • <https://github.com/TooTallNate/node-degenerator/commit/dc10ee9daa270157c19a16f7168fc42210f3355c|`dc10ee9`> 3.0.0 • <https://github.com/TooTallNate/node-degenerator/commit/e0b9fc83faabb101944b63bc73b710be7787f15b|`e0b9fc8`> Add `any` default return type to `compile()` • <https://github.com/TooTallNate/node-degenerator/commit/852043f9621f098ccf3a577a1d9a2ed0de20f402|`852043f`> Use `vm2` module to prevent privilege escalation of untrusted code (<https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/11|#11>) • <https://github.com/TooTallNate/node-degenerator/commit/7ad1041853551e393439003a10da56c605115652|`7ad1041`> Remove "generator" output mode (<https://github-redirect.dependabot.com/TooTallNate/node-degenerator/issues/12|#12>) • See full diff in <https://github.com/TooTallNate/node-degenerator/compare/2.2.0...3.0.2|compare view> Updates `pm2` from 4.5.6 to 5.2.0 Release notes _Sourced from <https://github.com/Unitech/pm2/releases|pm2's releases>._ &gt; *5.2.0* &gt; &gt; • replace node-cron by croner (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5183|#5183> <https://github-redirect.dependabot.com/Unitech/pm2/issues/5035|#5035>) &gt; • upgrade mocha deps &gt; • fix pm2 report when daemon not running &gt; • remove semver check for legacy node.js versions &gt; • update node version in setup.deb.sh by using lts (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5201|#5201>) + openrc &gt; • replace legacy util._extend by Object.assign (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5239|#5239>) &gt; • add missing start options types (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5242|#5242>) &gt; • recursive detection of package.json (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5267|#5267>) &gt; • make tarball module uninstall cross-platform (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5269|#5269>) &gt; • Fix unnecessary "ENOENT" console.error when serving a spa (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5272|#5272>) &gt; • fix: used env variable instead of hardcode datetime format (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5277|#5277>) &gt; • copyright update (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5278|#5278>) &gt; • fix: remove constants import from VersionCheck (not needed) (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5279|#5279>) &gt; • Reduce async import (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5280|#5280>) &gt; &gt; *5.1.2* &gt; &gt; • cron-restart improvements &gt; &gt; *5.1.1* &gt; &gt; • add back Node 10.x support &gt; • make pm2-sysmonit module optional &gt; • remove fast-printf and replace with sprintfjs &gt; &gt; *5.0.3* &gt; &gt; • fixes for system monitoring &gt; &gt; *5.0.0* &gt; *System Monitoring* &gt; &gt; A new local system monitoring feature has been added, allowing to monitor numerous vital server metrics. &gt; &gt; Most important metrics will be displayed when doing a pm2 ls: &gt; &gt; ``` &gt; ┌─────┬─────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐ &gt; │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │ &gt; ├─────┼─────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤ &gt; │ 4 │ app │ default │ 1.0.0 │ fork │ 164618 │ 2s │ 1670 │ online │ 0% │ 41.8mb │ unitech │ disabled │ &gt; └─────┴─────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘ &gt; host metrics | cpu: 1.6% 42.9º | mem free: 52.0% | wlp0s20f3: ⇓ 0mb/s ⇑ 0mb/s | disk: ⇓ 0.199mb/s ⇑ 0mb/s /dev/nvme0n1p3 88.25% | &gt; ``` &gt; &gt; All server metrics will be available to <http://pm2.io|pm2.io>: &gt; &gt; ``` &gt; ┌─────────────────────────────┬──────────────────────────────────┐ &gt; │ PM2 CPU Usage │ 0.0 % │ &gt; │ PM2 Memory Usage │ 67.4 mb │ &gt; │ PM2 Agent CPU Usage │ 0 % │ &gt; &lt;/tr&gt;&lt;/table&gt; &gt; ``` ... (truncated) Changelog _Sourced from <https://github.com/Unitech/pm2/blob/master/CHANGELOG.md|pm2's changelog>._ &gt; *5.2.0* &gt; &gt; • replace node-cron by croner (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5183|#5183> <https://github-redirect.dependabot.com/Unitech/pm2/issues/5035|#5035>) &gt; • upgrade mocha deps &gt; • fix pm2 report when daemon not running &gt; • remove semver check for legacy node.js versions &gt; • update node version in setup.deb.sh by using lts (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5201|#5201>) + openrc &gt; • replace legacy util._extend by Object.assign (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5239|#5239>) &gt; • add missing start options types (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5242|#5242>) &gt; • recursive detection of package.json (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5267|#5267>) &gt; • make tarball module uninstall cross-platform (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5269|#5269>) &gt; • Fix unnecessary "ENOENT" console.error when serving a spa (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5272|#5272>) &gt; • fix: used env variable instead of hardcode datetime format (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5277|#5277>) &gt; • copyright update (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5278|#5278>) &gt; • fix: remove constants import from VersionCheck (not needed) (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5279|#5279>) &gt; • Reduce async import (<https://github-redirect.dependabot.com/Unitech/pm2/issues/5280|#5280>) &gt; &gt; *5.1.2* &gt; &gt; • easily disable cron-restart strategy via `$ pm2 restart --cron-restart 0` &gt; • allow to update cron-restart on restart &gt; &gt; *5.1.1* &gt; &gt; • remove fast-printf and replace w…

github2 04:01:04

<https://github.com/cofacts/rumors-site/pull/505#issuecomment-1258551143|Comment on #505 Bump degenerator and pm2>

<https://coveralls.io/builds/52770004|Coverage Status> Coverage remained the same at 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/67fd5e2adec8c8f70e38895c9f8cafebf7817e72|67fd5e2> on dependabot/npm_and_yarn/degenerator-and-pm2-3.0.2* into *<https://github.com/cofacts/rumors-site/commit/7429b0698c89b448675b62d97f63ab302e5f01c2|7429b06> on master*.

github2 04:01:04

<https://github.com/cofacts/rumors-site/pull/505#issuecomment-1258551143|Comment on #505 Bump degenerator and pm2>

<https://coveralls.io/builds/52770004|Coverage Status> Coverage remained the same at 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/67fd5e2adec8c8f70e38895c9f8cafebf7817e72|67fd5e2> on dependabot/npm_and_yarn/degenerator-and-pm2-3.0.2* into *<https://github.com/cofacts/rumors-site/commit/7429b0698c89b448675b62d97f63ab302e5f01c2|7429b06> on master*.

2022-09-28

mrorz 18:02:10
https://cofacts.tw/article/148h07xc7p4xm 這到底是搭配什麼圖
mrorz 18:02:10
https://cofacts.tw/article/148h07xc7p4xm 這到底是搭配什麼圖還影片
cai 23:23:53
https://youtu.be/LHcoY39udoY 真的是放住家信箱

2022-09-29

github2 08:44:26

<https://github.com/cofacts/rumors-line-bot/pull/333|#333 Fix comment LIFF thanks message>

Fix bug found in <https://g0v.hackmd.io/ysACleHDTBmVMbH_4mi8uQ#%E2%9B%94%EF%B8%8F-Release-Blockers|20220928 meeting> (Related to <https://github.com/cofacts/rumors-line-bot/pull/329|#329> ) *1 reply request (no other)* <https://user-images.githubusercontent.com/108608/192913275-892f2cff-a581-4134-a495-816396ca2635.png|image> *2 reply requests (1 other)* <https://user-images.githubusercontent.com/108608/192913138-f20c59a8-91d6-4bea-82cb-235317d1221d.png|image> *5 reply requests* <https://user-images.githubusercontent.com/108608/192912897-b95b63ca-1f38-4966-a456-59f1405232c2.png|image>

:white_check_mark: All checks have passed

github2 08:44:26

<https://github.com/cofacts/rumors-line-bot/pull/333|#333 Fix comment LIFF thanks message>

Fix the release blocker found in <https://g0v.hackmd.io/ysACleHDTBmVMbH_4mi8uQ#%E2%9B%94%EF%B8%8F-Release-Blockers|20220928 meeting> (Related to <https://github.com/cofacts/rumors-line-bot/pull/329|#329> ). Also change the mandarin translation "共有 N 人" to "另有 N 人" so that it makes sense for both the case N = 1 and N &gt; 1. *1 reply request (no other)* <https://user-images.githubusercontent.com/108608/192913275-892f2cff-a581-4134-a495-816396ca2635.png|image> *2 reply requests (1 other)* <https://user-images.githubusercontent.com/108608/192913783-defd37eb-7aca-4602-bad5-d5042b3fb142.png|image> *5 reply requests (4 other)* <https://user-images.githubusercontent.com/108608/192913852-fef42e29-83ed-4123-8020-c51bd387ac31.png|image>

:white_check_mark: All checks have passed

github2 08:46:52

<https://github.com/cofacts/rumors-line-bot/pull/333#issuecomment-1261612223|Comment on #333 Fix comment LIFF thanks message>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52853496|Build 3147862573>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 08:46:52

<https://github.com/cofacts/rumors-line-bot/pull/333#issuecomment-1261612223|Comment on #333 Fix comment LIFF thanks message>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/52853538|Build 3147870075>* • *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 *91.543%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

Scott Shih 11:42:31
@scott.shih has joined the channel
mrorz 14:06:23
https://cofacts.tw/article/1ahrngs1nb7zc 好端端的投書,在 LINE 傳的時候被斷行成正元體
這樣有比較好讀嗎 lol
mrorz 14:06:23
https://cofacts.tw/article/1ahrngs1nb7zc 好端端的投書被斷行成正元體
這樣有比較好讀嗎 lol
github2 14:20:30

<https://github.com/cofacts/rumors-line-bot/pull/333|#333 Fix comment LIFF thanks message>

再請大家測測看, staging line bot 上還有沒有昨晚發現的 release blocker 的問題唷
沒有的話凌晨就會推新版
github2 14:20:30

<https://github.com/cofacts/rumors-line-bot/pull/333|#333 Fix comment LIFF thanks message>

再請大家測測看, staging line bot 上還有沒有昨晚發現的 release blocker 的問題唷
沒有的話凌晨就會推新版
mrorz 17:53:00
再請大家測測看, staging line bot 上還有沒有昨晚發現的 release blocker 的問題唷
沒有的話凌晨就會推新版

2022-09-30

github2 07:35:45

<https://github.com/cofacts/rumors-site/pull/506|#506 Bump d3-color and d3>

Bumps <https://github.com/d3/d3-color|d3-color> to 3.1.0 and updates ancestor dependency <https://github.com/d3/d3|d3>. These dependencies need to be updated together. Updates `d3-color` from 1.4.1 to 3.1.0 Release notes _Sourced from <https://github.com/d3/d3-color/releases|d3-color's releases>._ &gt; *v3.1.0* &gt; &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#rgb_clamp|_rgb_.clamp> and <https://github.com/d3/d3-color/blob/main/README.md#hsl_clamp|_hsl_.clamp>. <https://github-redirect.dependabot.com/d3/d3-color/issues/102|#102> &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#color_formatHex8|_color_.formatHex8>. <https://github-redirect.dependabot.com/d3/d3-color/issues/103|#103> &gt; • Fix <https://github.com/d3/d3-color/blob/main/README.md#color_formatHsl|_color_.formatHsl> to clamp values to the expected range. <https://github-redirect.dependabot.com/d3/d3-color/issues/83|#83> &gt; • Fix catastrophic backtracking when parsing colors. <https://github-redirect.dependabot.com/d3/d3-color/issues/89|#89> <https://github-redirect.dependabot.com/d3/d3-color/issues/97|#97> <https://github-redirect.dependabot.com/d3/d3-color/issues/99|#99> <https://github-redirect.dependabot.com/d3/d3-color/issues/100|#100> <https://security.snyk.io/vuln/SNYK-JS-D3COLOR-1076592|SNYK-JS-D3COLOR-1076592> &gt; &gt; *v3.0.1* &gt; &gt; • Make build reproducible. &gt; &gt; *v3.0.0* &gt; &gt; • Adopt type: module. &gt; &gt; This package now requires Node.js 12 or higher. For more, please read <https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c|Sindre Sorhus’s FAQ>. &gt; &gt; *v2.0.0* &gt; &gt; This release adopts ES2015 language features such as <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of|for-of> and drops support for older browsers, including IE. If you need to support pre-ES2015 environments, you should stick with d3-color 1.x or use a transpiler. Commits • <https://github.com/d3/d3-color/commit/7a1573ed260de4fd97d061975244841132adde92|`7a1573e`> 3.1.0 • <https://github.com/d3/d3-color/commit/75c19c40c246e4b3fbcfdeeba29249c51ccf6524|`75c19c4`> update LICENSE • <https://github.com/d3/d3-color/commit/ef94e0125cce176e2df2f877c70741f4e2856073|`ef94e01`> update dependencies • <https://github.com/d3/d3-color/commit/5e9f7579dd32a74664f5000ee99aa87e3e463c2b|`5e9f757`> method shorthand • <https://github.com/d3/d3-color/commit/e4bc34e46cba08c4b7209f2bea74ef570c000b86|`e4bc34e`> formatHex8 (<https://github-redirect.dependabot.com/d3/d3-color/issues/103|#103>) • <https://github.com/d3/d3-color/commit/ac660c6b6bd60a2f1cd255fe04ead7d1b053861d|`ac660c6`> {rgb,hsl}.clamp() (<https://github-redirect.dependabot.com/d3/d3-color/issues/102|#102>) • <https://github.com/d3/d3-color/commit/70e3a041f1890e63855fad693891652b36f48195|`70e3a04`> clamp HSL format (<https://github-redirect.dependabot.com/d3/d3-color/issues/101|#101>) • <https://github.com/d3/d3-color/commit/994d8fd95181484a5a27c5edc919aa625781432d|`994d8fd`> avoid backtracking (<https://github-redirect.dependabot.com/d3/d3-color/issues/100|#100>) • <https://github.com/d3/d3-color/commit/7d61bbe6e426a7f3d3f4520a8b31cfc92dc69ee7|`7d61bbe`> 3.0.1 • <https://github.com/d3/d3-color/commit/93bc4ff5423ecbefb6607724384bf6ca788d13b6|`93bc4ff`> related <https://github-redirect.dependabot.com/d3/d3/issues/3|d3/d33>; extract copyrights from LICENSE • Additional commits viewable in <https://github.com/d3/d3-color/compare/v1.4.1...v3.1.0|compare view> Updates `d3` from 5.16.0 to 7.6.1 Release notes _Sourced from <https://github.com/d3/d3/releases|d3's releases>._ &gt; *v7.6.1* &gt; &gt; • <https://github.com/d3/d3-contour/blob/main/README.md#density_bandwidth|_density_.bandwidth> now supports fractional (non-integer) values. &gt; &gt; *v7.6.0* &gt; &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blur|d3.blur>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blur2|d3.blur2>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blurImage|d3.blurImage>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#medianIndex|d3.medianIndex>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#quantileIndex|d3.quantileIndex>. &gt; &gt; *v7.5.0* &gt; &gt; • Add <https://github.com/d3/d3-contour/blob/main/README.md#density_contours|_density_.contours>. &gt; &gt; *v7.4.5* &gt; &gt; • Fix the interpretation of an array of numbers passed to <https://github.com/d3/d3-contour/blob/main/README.md#density_thresholds|_density_.thresholds>. &gt; &gt; *v7.4.4* &gt; &gt; • Fix incorrect behavior of d3.bisector when given an asymmetric comparator. &gt; &gt; *v7.4.3* &gt; &gt; • Fix crash in d3.bin. Thanks, <https://github.com/weiglemc|`@​weiglemc`>! &gt; &gt; *v7.4.2* &gt; &gt; • Fix off-by-one bin assignment due to rounding error in d3.bin. &gt; &gt; *v7.4.1* &gt; &gt; • Significantly improve the performance of d3.bin. &gt; • Fix the implementation of d3.thresholdScott. &gt; • d3.pack and d3.packEnclose are now fully deterministic. &gt; • d3.pack and d3.packEnclose now handle certain floating point errors better. &gt; &gt; *v7.4.0* &gt; &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#rgb_clamp|_rgb_.clamp> and <https://github.com/d3/d3-color/blob/main/README.md#hsl_clamp|_hsl_.clamp>. &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#color_formatHex8|_color_.formatHex8>. &gt; • Fix <https://github.com/d3/d3-color/blob/main/README.md#color_formatHsl|_color_.formatHsl> to clamp values to the expected range. &gt; • Fix catastrophic backtracking when parsing colors. <https://security.snyk.io/vuln/SNYK-JS-D3COLOR-1076592|SNYK-JS-D3COLOR-1076592> &gt; &gt; *v7.3.0* &gt; &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolsStroke|d3.symbolsStroke>. Thanks, <https://github.com/hemanrobinson|`@​hemanrobinson`>! &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolsFill|d3.symbolsFill>, replacing (deprecating) d3.symbols. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolAsterisk|d3.symbolAsterisk>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolDiamond2|d3.symbolDiamond2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolPlus|d3.symbolPlus>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolSquare2|d3.symbolSquare2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolTriangle2|d3.symbolTriangle2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolX|d3.symbolX>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#link|d3.link>. &gt; &gt; *v7.2.1* &gt; &gt; • Fix _stratify_.path when the top-level directory is only a single character. ... (truncated) Commits • <https://github.com/d3/d3/commit/19302a5055658907743b46a8428ba1ee39927b0f|`19302a5`> 7.6.1 • <https://github.com/d3/d3/commit/c1c2c0b8ca8d9058d8d07a9b8f89d6c8ec28d16e|`c1c2c0b`> d3-contour 4.0.0 • <https://github.com/d3/d3/commit/795f2030a4b727b3a14526ed9974d4e41c006a92|`795f203`> 7.6.0 • <https://github.com/d3/d3/commit/22f1dc734b8078ef7eaabff42d9aa479599559db|`22f1dc7`> d3-array 3.2.0 • <https://github.com/d3/d3/commit/d61883547c058d9e19fa04269fec48e2f4f8d494|`d618835`> 7.5.0 • <https://github.com/d3/d3/commit/d9f58e148dee005d8fa948d9e6b7dd154b18ca63|`d9f58e1`> d3-contour 3.1.0 • <https://github.com/d3/d3/commit/6d7057148dd18fc8240d51a2183d3f03ac42480c|`6d70571`> 7.4.5 • <https://github.com/d3/d3/commit/7e9eba396c80095f9b786af24cb4e8abbc03ed18|`7e9eba3`> d3-contour 3.0.2 • <https://github.com/d3/d3/commit/2f256d997879aef15d0a8f7e94a242dbc57d0106|`2f256d9`> 7.4.4 • <https://github.com/d3/d3/commit/8ff8c81b46bb43934f3cbc386298846702b99f79|`8ff8c81`> d3-array 3.1.6 • Additional commits viewable in <https://github.com/d3/d3/compare/v5.16.0...v7.6.1|compare view> Dependabot will resolve any conflicts with this PR as long as you don't alter it yo…

github2 07:35:45

<https://github.com/cofacts/rumors-site/pull/506|#506 Bump d3-color and d3>

Bumps <https://github.com/d3/d3-color|d3-color> to 3.1.0 and updates ancestor dependency <https://github.com/d3/d3|d3>. These dependencies need to be updated together. Updates `d3-color` from 1.4.1 to 3.1.0 Release notes _Sourced from <https://github.com/d3/d3-color/releases|d3-color's releases>._ &gt; *v3.1.0* &gt; &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#rgb_clamp|_rgb_.clamp> and <https://github.com/d3/d3-color/blob/main/README.md#hsl_clamp|_hsl_.clamp>. <https://github-redirect.dependabot.com/d3/d3-color/issues/102|#102> &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#color_formatHex8|_color_.formatHex8>. <https://github-redirect.dependabot.com/d3/d3-color/issues/103|#103> &gt; • Fix <https://github.com/d3/d3-color/blob/main/README.md#color_formatHsl|_color_.formatHsl> to clamp values to the expected range. <https://github-redirect.dependabot.com/d3/d3-color/issues/83|#83> &gt; • Fix catastrophic backtracking when parsing colors. <https://github-redirect.dependabot.com/d3/d3-color/issues/89|#89> <https://github-redirect.dependabot.com/d3/d3-color/issues/97|#97> <https://github-redirect.dependabot.com/d3/d3-color/issues/99|#99> <https://github-redirect.dependabot.com/d3/d3-color/issues/100|#100> <https://security.snyk.io/vuln/SNYK-JS-D3COLOR-1076592|SNYK-JS-D3COLOR-1076592> &gt; &gt; *v3.0.1* &gt; &gt; • Make build reproducible. &gt; &gt; *v3.0.0* &gt; &gt; • Adopt type: module. &gt; &gt; This package now requires Node.js 12 or higher. For more, please read <https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c|Sindre Sorhus’s FAQ>. &gt; &gt; *v2.0.0* &gt; &gt; This release adopts ES2015 language features such as <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of|for-of> and drops support for older browsers, including IE. If you need to support pre-ES2015 environments, you should stick with d3-color 1.x or use a transpiler. Commits • <https://github.com/d3/d3-color/commit/7a1573ed260de4fd97d061975244841132adde92|`7a1573e`> 3.1.0 • <https://github.com/d3/d3-color/commit/75c19c40c246e4b3fbcfdeeba29249c51ccf6524|`75c19c4`> update LICENSE • <https://github.com/d3/d3-color/commit/ef94e0125cce176e2df2f877c70741f4e2856073|`ef94e01`> update dependencies • <https://github.com/d3/d3-color/commit/5e9f7579dd32a74664f5000ee99aa87e3e463c2b|`5e9f757`> method shorthand • <https://github.com/d3/d3-color/commit/e4bc34e46cba08c4b7209f2bea74ef570c000b86|`e4bc34e`> formatHex8 (<https://github-redirect.dependabot.com/d3/d3-color/issues/103|#103>) • <https://github.com/d3/d3-color/commit/ac660c6b6bd60a2f1cd255fe04ead7d1b053861d|`ac660c6`> {rgb,hsl}.clamp() (<https://github-redirect.dependabot.com/d3/d3-color/issues/102|#102>) • <https://github.com/d3/d3-color/commit/70e3a041f1890e63855fad693891652b36f48195|`70e3a04`> clamp HSL format (<https://github-redirect.dependabot.com/d3/d3-color/issues/101|#101>) • <https://github.com/d3/d3-color/commit/994d8fd95181484a5a27c5edc919aa625781432d|`994d8fd`> avoid backtracking (<https://github-redirect.dependabot.com/d3/d3-color/issues/100|#100>) • <https://github.com/d3/d3-color/commit/7d61bbe6e426a7f3d3f4520a8b31cfc92dc69ee7|`7d61bbe`> 3.0.1 • <https://github.com/d3/d3-color/commit/93bc4ff5423ecbefb6607724384bf6ca788d13b6|`93bc4ff`> related <https://github-redirect.dependabot.com/d3/d3/issues/3|d3/d33>; extract copyrights from LICENSE • Additional commits viewable in <https://github.com/d3/d3-color/compare/v1.4.1...v3.1.0|compare view> Updates `d3` from 5.16.0 to 7.6.1 Release notes _Sourced from <https://github.com/d3/d3/releases|d3's releases>._ &gt; *v7.6.1* &gt; &gt; • <https://github.com/d3/d3-contour/blob/main/README.md#density_bandwidth|_density_.bandwidth> now supports fractional (non-integer) values. &gt; &gt; *v7.6.0* &gt; &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blur|d3.blur>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blur2|d3.blur2>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#blurImage|d3.blurImage>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#medianIndex|d3.medianIndex>. &gt; • Add <https://github.com/d3/d3-array/blob/main/README.md#quantileIndex|d3.quantileIndex>. &gt; &gt; *v7.5.0* &gt; &gt; • Add <https://github.com/d3/d3-contour/blob/main/README.md#density_contours|_density_.contours>. &gt; &gt; *v7.4.5* &gt; &gt; • Fix the interpretation of an array of numbers passed to <https://github.com/d3/d3-contour/blob/main/README.md#density_thresholds|_density_.thresholds>. &gt; &gt; *v7.4.4* &gt; &gt; • Fix incorrect behavior of d3.bisector when given an asymmetric comparator. &gt; &gt; *v7.4.3* &gt; &gt; • Fix crash in d3.bin. Thanks, <https://github.com/weiglemc|`@​weiglemc`>! &gt; &gt; *v7.4.2* &gt; &gt; • Fix off-by-one bin assignment due to rounding error in d3.bin. &gt; &gt; *v7.4.1* &gt; &gt; • Significantly improve the performance of d3.bin. &gt; • Fix the implementation of d3.thresholdScott. &gt; • d3.pack and d3.packEnclose are now fully deterministic. &gt; • d3.pack and d3.packEnclose now handle certain floating point errors better. &gt; &gt; *v7.4.0* &gt; &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#rgb_clamp|_rgb_.clamp> and <https://github.com/d3/d3-color/blob/main/README.md#hsl_clamp|_hsl_.clamp>. &gt; • Add <https://github.com/d3/d3-color/blob/main/README.md#color_formatHex8|_color_.formatHex8>. &gt; • Fix <https://github.com/d3/d3-color/blob/main/README.md#color_formatHsl|_color_.formatHsl> to clamp values to the expected range. &gt; • Fix catastrophic backtracking when parsing colors. <https://security.snyk.io/vuln/SNYK-JS-D3COLOR-1076592|SNYK-JS-D3COLOR-1076592> &gt; &gt; *v7.3.0* &gt; &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolsStroke|d3.symbolsStroke>. Thanks, <https://github.com/hemanrobinson|`@​hemanrobinson`>! &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolsFill|d3.symbolsFill>, replacing (deprecating) d3.symbols. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolAsterisk|d3.symbolAsterisk>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolDiamond2|d3.symbolDiamond2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolPlus|d3.symbolPlus>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolSquare2|d3.symbolSquare2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolTriangle2|d3.symbolTriangle2>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#symbolX|d3.symbolX>. &gt; • Add <https://github.com/d3/d3-shape/blob/main/README.md#link|d3.link>. &gt; &gt; *v7.2.1* &gt; &gt; • Fix _stratify_.path when the top-level directory is only a single character. ... (truncated) Commits • <https://github.com/d3/d3/commit/19302a5055658907743b46a8428ba1ee39927b0f|`19302a5`> 7.6.1 • <https://github.com/d3/d3/commit/c1c2c0b8ca8d9058d8d07a9b8f89d6c8ec28d16e|`c1c2c0b`> d3-contour 4.0.0 • <https://github.com/d3/d3/commit/795f2030a4b727b3a14526ed9974d4e41c006a92|`795f203`> 7.6.0 • <https://github.com/d3/d3/commit/22f1dc734b8078ef7eaabff42d9aa479599559db|`22f1dc7`> d3-array 3.2.0 • <https://github.com/d3/d3/commit/d61883547c058d9e19fa04269fec48e2f4f8d494|`d618835`> 7.5.0 • <https://github.com/d3/d3/commit/d9f58e148dee005d8fa948d9e6b7dd154b18ca63|`d9f58e1`> d3-contour 3.1.0 • <https://github.com/d3/d3/commit/6d7057148dd18fc8240d51a2183d3f03ac42480c|`6d70571`> 7.4.5 • <https://github.com/d3/d3/commit/7e9eba396c80095f9b786af24cb4e8abbc03ed18|`7e9eba3`> d3-contour 3.0.2 • <https://github.com/d3/d3/commit/2f256d997879aef15d0a8f7e94a242dbc57d0106|`2f256d9`> 7.4.4 • <https://github.com/d3/d3/commit/8ff8c81b46bb43934f3cbc386298846702b99f79|`8ff8c81`> d3-array 3.1.6 • Additional commits viewable in <https://github.com/d3/d3/compare/v5.16.0...v7.6.1|compare view> Dependabot will resolve any conflicts with this PR as long as you don't alter it yo…

:white_check_mark: No checks have passed

mrorz 19:34:58
看來即使有加裝了攝影機,也還沒跟罰單連動唷
https://tfc-taiwan.org.tw/articles/8232

台灣事實查核中心

【錯誤】網傳「很多人沒見過的新型測速攝影…為了你們辛苦賺來的錢,不要讓政府把你當提款機,務必小心,不要超速!」?

【報告將隨時更新 2022/9/30版】 一、網傳影片拍攝地點為桃園市。 桃園市交通局表示,網傳影片的設施為「車輛速度偵測提醒系統」,僅用於偵測車輛速度,並會以「綠色笑臉」、「紅色哭臉」圖樣來提醒駕駛人不要超速,並不具備照相舉發功能,也沒有與警局的測速照相系統連動。 二、目前桃園市共設置11支車輛速度偵測桿,交通局觀察到提醒效果卓著,行經車輛均明顯降速,今年底前還會再新增四處共8支,希望提醒駕駛人安全駕駛勿超速。 傳言呼籲駕駛人不要超速是正確觀念,但網傳影片中的「車輛速度偵測提醒系統」僅用於提醒,並不具備照相舉發功能。因此,傳言為「錯誤」訊息。

👀 1