cofacts

Month: 2022-08

2022-08-03

cai 22:37:54
https://cofacts.tw/article/2742uwo9vu2q
看裡面的網址原本以為去詐騙,丟去 expand url 發現還真的是連結到google表單
瑪家鄉公所的FB宣傳文也是用這個縮網址
為什麼會想用xyz結尾的網址啦 😅
image.png
😂 2

2022-08-04

cai 22:10:29
本日熱門:9400萬系列文
https://cofacts.tw/article/3b220f4vuifrz
https://cofacts.tw/article/3u4h4j1wr1ars
https://cofacts.tw/article/3iu7rmxas4div

這不確定是否同系列,連結的影片好像沒提到500萬?
https://cofacts.tw/article/1biwny9qa3fk4
https://cofacts.tw/article/uz7dnscjkcfk

外交部澄清稿後的
https://cofacts.tw/article/44nel0vjz9ma
https://cofacts.tw/article/3nx4mdh1jb7yf
https://cofacts.tw/article/z9mkno4x6phm
原來後續政論節目有接手呀
想到可以查得方向應該有
1. 我國該筆預算過去編列到現在的狀況是否有所增減,尤其是橫跨不同執政黨時期
2. 該筆資料據說出自美國開放資料。那跟其他國家(ex: 以色列)相比,我國花在遊說的前有特別多嗎?
或是看美國台灣觀測站或其他粉專
之前是不是有寫過政治遊說科普文
今天又有一篇新的,然後又被發現是盜帳的
6月的也有相關話題,針對聯合報的
https://www.mofa.gov.tw/News_Content.aspx?n=99&s=98019
> 我國駐美代表處聘用公關公司協助推動強化台美關係,是我國政府長年的一貫作法,跨越不同政黨的政府皆同,並非單一政黨所獨創或獨有的運作。公關公司在美國為我國進行遊說工作,一向嚴格遵守相關法律,其預算也由我國立法院進行完整、合法、公開透明的監督。近年來相關預算的支出規模大致持平,外交部也會依據實際需要進行微調。
https://www.upmedia.mg/news_info.php?Type=2&SerialNo=147468
https://www.ly.gov.tw/Pages/Detail.aspx?nodeid=6590&pid=215457
中天的政論節目是8/2,八卦板那篇是8/4
咦?原來是政論節目先,八卦版後?
外交部澄清稿第二篇
https://www.mofa.gov.tw/News_Content.aspx?n=1163&s=98258
> 網傳公關公司文件資料是假造圖片,包括表格內容及負責人的簽名均是偽造。
事實查核中心的檔案列表是 FARA 的 filing system 列表

如果是想要看 by foreign principal 的統計,其實可以直接看 FARA Reports to Congress
https://www.justice.gov/nsd-fara/fara-reports-congress

每半年有一個報告,我正在把 20202H2 挑幾個國家出來打成表
https://docs.google.com/spreadsheets/d/1QE9x2VME12YWqYNayfRxERyjVZHnbYxpEnaEvrORGaU/edit
cai 22:10:29
本日熱門:9400萬系列文
https://cofacts.tw/article/3b220f4vuifrz
https://cofacts.tw/article/3u4h4j1wr1ars
https://cofacts.tw/article/3iu7rmxas4div

這不確定是否同系列,連結的影片好像沒提到500萬?
https://cofacts.tw/article/1biwny9qa3fk4
https://cofacts.tw/article/uz7dnscjkcfk

外交部澄清稿後的
https://cofacts.tw/article/44nel0vjz9ma
https://cofacts.tw/article/3nx4mdh1jb7yf
https://cofacts.tw/article/z9mkno4x6phm
原來後續政論節目有接手呀
想到可以查得方向應該有
1. 我國該筆預算過去編列到現在的狀況是否有所增減,尤其是橫跨不同執政黨時期
2. 該筆資料據說出自美國開放資料。那跟其他國家(ex: 以色列)相比,我國花在遊說的前有特別多嗎?
或是看美國台灣觀測站或其他粉專
之前是不是有寫過政治遊說科普文
今天又有一篇新的,然後又被發現是盜帳的
6月的也有相關話題,針對聯合報的
https://www.mofa.gov.tw/News_Content.aspx?n=99&s=98019
> 我國駐美代表處聘用公關公司協助推動強化台美關係,是我國政府長年的一貫作法,跨越不同政黨的政府皆同,並非單一政黨所獨創或獨有的運作。公關公司在美國為我國進行遊說工作,一向嚴格遵守相關法律,其預算也由我國立法院進行完整、合法、公開透明的監督。近年來相關預算的支出規模大致持平,外交部也會依據實際需要進行微調。
https://www.upmedia.mg/news_info.php?Type=2&SerialNo=147468
https://www.ly.gov.tw/Pages/Detail.aspx?nodeid=6590&pid=215457
中天的政論節目是8/2,八卦板那篇是8/4
咦?原來是政論節目先,八卦版後?
外交部澄清稿第二篇
https://www.mofa.gov.tw/News_Content.aspx?n=1163&s=98258
> 網傳公關公司文件資料是假造圖片,包括表格內容及負責人的簽名均是偽造。
事實查核中心的檔案列表是 FARA 的 filing system 列表

如果是想要看 by foreign principal 的統計,其實可以直接看 FARA Reports to Congress
https://www.justice.gov/nsd-fara/fara-reports-congress

每半年有一個報告,我正在把 20202H2 挑幾個國家出來打成表
https://docs.google.com/spreadsheets/d/1QE9x2VME12YWqYNayfRxERyjVZHnbYxpEnaEvrORGaU/edit

2022-08-05

github2 01:57:56

<https://github.com/cofacts/rumors-site/pull/499#issuecomment-1205590513|Comment on #499 Include LIFF stats in article page>

Updated according to <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F6gLsmuTUQia3sjyYPPcFvQ|meeting discussion> <https://user-images.githubusercontent.com/108608/182918507-60654179-2925-4a2b-b327-51f9f4a83a91.png|image> <https://user-images.githubusercontent.com/108608/182918534-4dfccae9-45fd-49f3-a5fa-752f2883a845.png|image> <https://user-images.githubusercontent.com/108608/182918681-8a863e10-3541-4ca3-8c50-dc446618eadb.png|image> <https://user-images.githubusercontent.com/108608/182918712-7a231ec1-b654-4871-b803-4f3f312171e6.png|image>

github2 01:57:56

<https://github.com/cofacts/rumors-site/pull/499#issuecomment-1205590513|Comment on #499 Include LIFF stats in article page>

Updated according to <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F6gLsmuTUQia3sjyYPPcFvQ|meeting discussion> <https://user-images.githubusercontent.com/108608/182918507-60654179-2925-4a2b-b327-51f9f4a83a91.png|image> <https://user-images.githubusercontent.com/108608/182918534-4dfccae9-45fd-49f3-a5fa-752f2883a845.png|image> <https://user-images.githubusercontent.com/108608/182918681-8a863e10-3541-4ca3-8c50-dc446618eadb.png|image> <https://user-images.githubusercontent.com/108608/182918712-7a231ec1-b654-4871-b803-4f3f312171e6.png|image>

mrorz 16:49:44
在「張景明」之後
現在一直洗的換成「呂尚傑」
https://cofacts.github.io/community-builder/#/editorworks?showAll=1&day=365&userId=aFQPbYIBZ4FY5vnA-lMv

cofacts.github.io

Community Builder

Web site created using create-react-app

mrorz 17:06:26
中研院在 KDD 有篇 paper 是關於用 AI 生成 counterfactual explanations for fake claims
https://arxiv.org/abs/2206.04869
https://github.com/yilihsu/AsktoKnowMore

arXiv.org

Ask to Know More: Generating Counterfactual Explanations for Fake Claims

Automated fact checking systems have been proposed that quickly provide veracity prediction at scale to mitigate the negative influence of fake news on people and on public opinion. However, most...

yilihsu/AsktoKnowMore

Ask to Know More: Counterfactual Explanations for Fake Claims source code

mrorz 17:06:26
中研院在 KDD 有篇 paper 是關於用 AI 生成 counterfactual explanations for fake claims
https://arxiv.org/abs/2206.04869
https://github.com/yilihsu/AsktoKnowMore
mrorz 23:42:41
事實查核中心的檔案列表是 FARA 的 filing system 列表

如果是想要看 by foreign principal 的統計,其實可以直接看 FARA Reports to Congress
https://www.justice.gov/nsd-fara/fara-reports-congress

每半年有一個報告,我正在把 20202H2 挑幾個國家出來打成表
https://docs.google.com/spreadsheets/d/1QE9x2VME12YWqYNayfRxERyjVZHnbYxpEnaEvrORGaU/edit
😮 2

2022-08-07

github2 14:57:43

<https://github.com/cofacts/rumors-line-bot/pull/316|#316 Feature/image search>

1. Implement processImage 2. Remove old image related code: tesseract-ocr, GDrive 3. Extract postback event function as a standalone handler 4. Remove isSkipUser paramater by directly calling `handlePostback`

github2 14:57:43

<https://github.com/cofacts/rumors-line-bot/pull/316|#316 Feature/image search>

*Changes* 1. Implement processImage, fixes <https://github.com/cofacts/rumors-line-bot/issues/304|#304> 2. Remove old image related code: tesseract-ocr, GDrive 3. Extract postback event function as a standalone handler • Input(text) -&gt; `handleInput` -&gt; return buttons that will trigger `handlePostback` • Input(image) -&gt; `processImage` -&gt; return buttons that will trigger `handlePostback` • Input(postback) -&gt; `handlePostback` 4. Remove isSkipUser (only used in `initState`) parameter by directly calling `handlePostback` *Snapshots* <https://user-images.githubusercontent.com/6376572/183279240-d72dce87-c366-4050-b989-c3927a7bb100.png|https://user-images.githubusercontent.com/6376572/183279240-d72dce87-c366-4050-b989-c3927a7bb100.png> <https://user-images.githubusercontent.com/6376572/183279242-7a99b590-d773-4e0d-b764-479262af57ca.png|https://user-images.githubusercontent.com/6376572/183279242-7a99b590-d773-4e0d-b764-479262af57ca.png> <https://user-images.githubusercontent.com/6376572/183279246-e642c1ce-a2bd-4d5d-b29b-730bf6f41ea2.png|https://user-images.githubusercontent.com/6376572/183279246-e642c1ce-a2bd-4d5d-b29b-730bf6f41ea2.png>

:white_check_mark: All checks have passed

github2 15:00:35

<https://github.com/cofacts/rumors-line-bot/pull/316#issuecomment-1207344621|Comment on #316 Feature/image search>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/51470788|Build 2811714669>* • *83* of *106* *(78.3%)* changed or added relevant lines in *11* files are covered. • *4* unchanged lines in *2* files lost coverage. • Overall coverage increased (+*5.8%*) to *91.292%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 15:00:35

<https://github.com/cofacts/rumors-line-bot/pull/316#issuecomment-1207344621|Comment on #316 Feature/image search>

*Pull Request Test Coverage Report for <https://coveralls.io/builds/51470788|Build 2811714669>* • *83* of *106* *(78.3%)* changed or added relevant lines in *11* files are covered. • *4* unchanged lines in *2* files lost coverage. • Overall coverage increased (+*5.8%*) to *91.292%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 18:04:07

<https://github.com/cofacts/rumors-api/pull/290|#290 fetchStatsFromGA script now warns about sampled data>

When back filling old analytics data, we found that the fetched LIFF stats are inconsistent with the numbers on Google Analytics. We can reproduce this on local machine, and found that the inaccuracy only happens when the data is sampled: <https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling|https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling> If we specify a shorter date range when running the script, the inconsistency will be gone. This PR adds a warning message when sampled data is detected from the Google Analytics Reporting API response. <https://user-images.githubusercontent.com/108608/183285758-e32e57a5-6533-48d3-96ad-c0e4e5b6bfbf.png|圖片>

github2 18:04:07

<https://github.com/cofacts/rumors-api/pull/290|#290 fetchStatsFromGA script now warns about sampled data>

When back filling old analytics data, we found that the fetched LIFF stats are inconsistent with the numbers on Google Analytics. We can reproduce this on local machine, and found that the inaccuracy only happens when the data is sampled: <https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling|https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling> If we specify a shorter date range when running the script, the inconsistency will be gone. This PR adds a warning message when sampled data is detected from the Google Analytics Reporting API response. <https://user-images.githubusercontent.com/108608/183285758-e32e57a5-6533-48d3-96ad-c0e4e5b6bfbf.png|圖片> Sampling should only happens when we manually back-fill the data. The hourly cron job should not have that much of data that triggers Google Analytics samplng.

:white_check_mark: All checks have passed

github2 18:06:18

<https://github.com/cofacts/rumors-api/pull/290#issuecomment-1207373115|Comment on #290 fetchStatsFromGA script now warns about sampled data>

<https://coveralls.io/builds/51471855|Coverage Status> Coverage increased (+0.01%) to 87.768% when pulling *<https://github.com/cofacts/rumors-api/commit/4aac44c901ef46b5e512909c22b5a492b74bca76|4aac44c> on warn-about-sampled* into *<https://github.com/cofacts/rumors-api/commit/985911c62e94f6d15e330f61d9bc1d05d9263480|985911c> on master*.

github2 18:06:18

<https://github.com/cofacts/rumors-api/pull/290#issuecomment-1207373115|Comment on #290 fetchStatsFromGA script now warns about sampled data>

<https://coveralls.io/builds/51471855|Coverage Status> Coverage increased (+0.01%) to 87.768% when pulling *<https://github.com/cofacts/rumors-api/commit/4aac44c901ef46b5e512909c22b5a492b74bca76|4aac44c> on warn-about-sampled* into *<https://github.com/cofacts/rumors-api/commit/985911c62e94f6d15e330f61d9bc1d05d9263480|985911c> on master*.

2022-08-08

github2 16:58:53

Review on #7 Documentation

:+1::+1::+1:

github2 16:58:53

Review on #7 Documentation

:+1::+1::+1:

2022-08-09

cai 12:39:17
登入後不是會自動切換 `cofacts.tw` 嗎
這幾天發生的情況,如果在 firefox 登入後網址再切到 `cofacts.g0v.tw` 會等於沒有登入,但是切回到 `cofacts.tw` 就還是有登入的狀態,chrome 沒有這種情況。
cai 12:39:17
登入後不是會自動切換 `cofacts.tw` 嗎
這幾天發生的情況,如果在 firefox 登入後網址再切到 `cofacts.g0v.tw` 會等於沒有登入,但是切回到 `cofacts.tw` 就還是有登入的狀態,chrome 沒有這種情況。
mrorz 13:52:56
印象中不會切換
mrorz 13:52:56
印象中不會切換
mrorz 13:53:14
登入 cookie 應該都是在 cofacts.tw @@
mrorz 13:53:14
登入 cookie 應該都是在 cofacts.tw @@
mrorz 13:54:00
我可以再查一下
mrorz 13:54:00
可以再查一下

2022-08-10

github2 00:43:54

<https://github.com/cofacts/takedowns/pull/84|#84 Create 0810-love-scam.md>

這個有很多故事 www

今晚有人檢舉此篇訊息下某 LINE 使用者補充交友詐騙的訊息

點進去看之後我覺得被檢舉的人沒違規,反而訊息下有一排人非常可疑,一查就發現通通都是今天晚上 9 點註冊 + 回應的,直接一波帶走。

不過其中一個人特別有趣,他除了推自家的詐騙網之外,還同時在另一個網站的訊息下補充:「詐騙集團 女生就是客服」
https://cofacts.github.io/community-builder/#/editorworks?type=2&day=365&userId=41SxgoIBZ4FY5vnAwnUM&showAll=1

⋯⋯檢舉 LINE 使用者的補充的,就是你吧 wwwwww
不過我覺得同業互踩「詐騙集團 女生就是客服」這件事情
是不是就代表,其實交友詐騙的型態就是這種
一個人分飾多角,用這個方式來吸金的作法 w
github2 00:43:54

<https://github.com/cofacts/takedowns/pull/84|#84 Create 0810-love-scam.md>

這個有很多故事 www

今晚有人檢舉此篇訊息下某 LINE 使用者補充交友詐騙的訊息

點進去看之後我覺得被檢舉的人沒違規,反而訊息下有一排人非常可疑,一查就發現通通都是今天晚上 9 點註冊 + 回應的,直接一波帶走。

不過其中一個人特別有趣,他除了推自家的詐騙網之外,還同時在另一個網站的訊息下補充:「詐騙集團 女生就是客服」
https://cofacts.github.io/community-builder/#/editorworks?type=2&day=365&userId=41SxgoIBZ4FY5vnAwnUM&showAll=1

⋯⋯檢舉 LINE 使用者的補充的,就是你吧 wwwwww
不過我覺得同業互踩「詐騙集團 女生就是客服」這件事情
是不是就代表,其實交友詐騙的型態就是這種
一個人分飾多角,用這個方式來吸金的作法 w
mrorz 10:47:26
今日議程
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FuZ3gouRWRamtrCFzKFrgnw

HackMD

Cofacts 會議記錄 - HackMD

# Cofacts 會議記錄 ## 2022 - [20220810 會議記錄](/uZ3gouRWRamtrCFzKFrgnw) - [20220803 會議記錄](/6gLsmuTUQia3

github2 18:06:01

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942268386|Comment on #316 Feature/image search>

Q: seems that we should delete these text related search from `processImage` test ?

github2 18:06:01

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942268386|Comment on #316 Feature/image search>

Q: seems that we should delete these text related search from `processImage` test ?

github2 18:53:29

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942291753|Comment on #316 Feature/image search>

I think we should not show "None of these messages matches mine" if there is a 100% match. Because if the user chooses this option and tries to submit the image, `MediaManager` will find that the uploaded file has 100% match and does not perform upload anyway.

github2 18:53:29

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942291753|Comment on #316 Feature/image search>

I think we should not show "None of these messages matches mine" if there is a 100% match. Because if the user chooses this option and tries to submit the image, `MediaManager` will find that the uploaded file has 100% match and does not perform upload anyway.

github2 18:53:29

Review on #316 Feature/image search

Thanks for the contribution! Although the PR is big, it's still understandable. The PR description and the weekly sync helped a lot :+1: Please find my comments below.

github2 18:53:29

Review on #316 Feature/image search

Thanks for the contribution! Although the PR is big, it's still understandable. The PR description and the weekly sync helped a lot :+1: Please find my comments below.

github2 18:53:29

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942298351|Comment on #316 Feature/image search>

The height of thumbnail image always does not exceed 240px (set <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/mutations/CreateMediaArticle.js#L67|in rumors-api>). Can we set the <https://developers.line.biz/en/docs/messaging-api/flex-message-layout/#box-max-height|maxHeight> of hero so that images don't get blurry?

github2 18:53:29

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942298351|Comment on #316 Feature/image search>

The height of thumbnail image always does not exceed 240px (set <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/mutations/CreateMediaArticle.js#L67|in rumors-api>). Can we set the <https://developers.line.biz/en/docs/messaging-api/flex-message-layout/#box-max-height|maxHeight> of hero so that images don't get blurry?

github2 19:05:25

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942318872|Comment on #316 Feature/image search>

Outdated comment. Hope we can fix the comment along with this PR XD Suggested change

github2 19:05:25

<https://github.com/cofacts/rumors-line-bot/pull/316#discussion_r942318872|Comment on #316 Feature/image search>

Outdated comment. Hope we can fix the comment along with this PR XD Suggested change

2022-08-11

cai 15:07:17
https://cofacts.tw/article/lz3lrtk1r2y6
提到大立光跟台積電,這能直接跟那些公司講了吧
github2 16:57:06

Review on #317 docs: fix hyperlink

Thanks for the update!

github2 16:57:06

Review on #317 docs: fix hyperlink

Thanks for the update!

github2 16:58:00

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

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

github2 16:58:00

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

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

cai 18:43:37
自從那個假紓困詐騙,現在看到補貼相關的舊文浮上來都會感覺不妙
這兩天看到的紓困詐騙是寫要48小時內送出,是因為防詐達人判定寫要48小時後再傳一次嗎
https://cofacts.g0v.tw/article/2s000nj9u1uhw

難怪兒童補助那篇又浮上來
咦,我以為只是想要用限時來降低人的判斷力
跟限時特價一樣
cai 18:43:37
自從那個假紓困詐騙,現在看到補貼相關的舊文浮上來都會感覺不妙
這兩天看到的紓困詐騙是寫要48小時內送出,是因為防詐達人判定寫要48小時後再傳一次嗎
https://cofacts.g0v.tw/article/2s000nj9u1uhw

難怪兒童補助那篇又浮上來
咦,我以為只是想要用限時來降低人的判斷力
跟限時特價一樣
😢 2
cai 21:13:05
這兩天看到的紓困詐騙是寫要48小時內送出,是因為防詐達人判定寫要48小時後再傳一次嗎
https://cofacts.g0v.tw/article/2s000nj9u1uhw

難怪兒童補助那篇又浮上來

2022-08-12

2022-08-15

2022-08-17

github2 13:49:46

<https://github.com/cofacts/rumors-line-bot/issues/319|#319 Articles list and article LIFF should show image>

From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> LIFF article list (articles) and article page should support displaying images

github2 13:49:46

<https://github.com/cofacts/rumors-line-bot/issues/319|#319 Articles list and article LIFF should show image>

From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> LIFF article list (articles) and article page should support displaying images

github2 13:58:31

<https://github.com/cofacts/rumors-line-bot/issues/320|#320 Incorrect thank-you message when editing reply request (comments)>

From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> *As-is* <https://user-images.githubusercontent.com/108608/185045067-dfd5fdb5-4f7c-47d8-baad-3037bb1fe2d4.png|image> *To-be* If there is no other people submitting reply request / comments, we should not show the second sentence. Just use the first sentence (thank the user).

github2 13:58:31

<https://github.com/cofacts/rumors-line-bot/issues/320|#320 Incorrect thank-you message when editing reply request (comments)>

From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> *As-is* <https://user-images.githubusercontent.com/108608/185045067-dfd5fdb5-4f7c-47d8-baad-3037bb1fe2d4.png|image> *To-be* If there is no other people submitting reply request / comments, we should not show the second sentence. Just use the first sentence (thank the user).

2022-08-18

github2 13:17:44

<https://github.com/cofacts/rumors-line-bot/pull/318#discussion_r948644150|Comment on #318 Feature/image submit>

Q: is this expected that `processImage()` returns a context with `messageId` being `undefined`? Seems that the mock event in the test case is `{message: {id: '...'}}` but in `processImage` we store `event.messageId` in context. Which one is correct?

github2 13:17:44

<https://github.com/cofacts/rumors-line-bot/pull/318#discussion_r948644150|Comment on #318 Feature/image submit>

Q: is this expected that `processImage()` returns a context with `messageId` being `undefined`? Seems that the mock event in the test case is `{message: {id: '...'}}` but in `processImage` we store `event.messageId` in context. Which one is correct?

github2 13:17:44

Review on #318 Feature/image submit

Thanks for the PR! Wordings look good to me, will deploy to staging and test. Please find my comments below.

github2 13:17:44

Review on #318 Feature/image submit

Thanks for the PR! Wordings look good to me, will deploy to staging and test. Please find my comments below.

github2 13:49:21

<https://github.com/cofacts/rumors-line-bot/pull/318#discussion_r948673004|Comment on #318 Feature/image submit>

Oh! My test input is incorrect, it should have a `messageId` in the test input. I will update it! In `webhook/index.js`, I assign a `messageId` to `event`: `event = { messageId: otherFields.message.id, type, ...otherFields };`.

github2 13:49:21

<https://github.com/cofacts/rumors-line-bot/pull/318#discussion_r948673004|Comment on #318 Feature/image submit>

Oh! My test input is incorrect, it should have a `messageId` in the test input. I will update it! In `webhook/index.js`, I assign a `messageId` to `event`: `event = { messageId: otherFields.message.id, type, ...otherFields };`.

2022-08-19

Mason 21:48:52
@ohmygodmason has joined the channel

2022-08-20

cai 16:18:48
這篇其實蠻有趣的,附圖故意不露出收件人,然後勞保局又有分 勞保/勞退/國民年金 繳費單 www
https://cofacts.g0v.tw/article/2bipfvp7oap6o
https://cofacts.g0v.tw/article/2vvg5rbnt0m8b
截圖來源下方的留言都沒人提出質疑欸
https://i.imgur.com/C9vMdGm.png

facebook.com

Log in or sign up to view

See posts, photos and more on Facebook.

最基本的解決是超商代繳是要向超商業者申請的,詐騙過不了
這個,我是有朋友真的發生過,收到的繳費單超商可以繳
繳完之後仍然被催收、以及有滯納金
單位說他繳的繳費單不是他們的,該單位不負責~

自此之後他都不相信勞健保寄來的繳費單@@"

但詳細狀況不清楚是勞保或勞退,或者這兩個搞混,或者是真的有假的繳費單或其他狀況等...
繳費單去超商繳會有感熱紙的收據(小白單),上面會寫繳哪種費用,之後要理論也是憑這張去問 https://www.hcct.gov.tw/ch/home.jsp?id=248&parentpath=&mcustomize=faq_view.jsp&dataserno=201704270001&t=FAQ&mserno=201511220004
開串那張勞保跟勞退提撥那種繳費單,其實是投保單位才要擔心的問題
勞保局竟然在假日澄清了
https://www.bli.gov.tw/0107260.html
> 近日民眾於臉書反映收到勞保局所寄發繳款單係詐騙乙事,經查證並詳加瞭解,勞保局澄清,該二封繳款單確係是本局所寄發無誤,一是保險費繳款單(含勞保、職保、就保);另一是勞工退休金繳款單(含雇主提繳費及勞工個人提繳費),請民眾安心。
😢 1 😮 1
cai 16:18:48
這篇其實蠻有趣的,附圖故意不露出姓名跟地址,然後勞保局又有分 勞保/勞退/國民年金 繳費單 www
https://cofacts.g0v.tw/article/2bipfvp7oap6o
截圖來源下方的留言都沒人提出質疑欸
https://i.imgur.com/C9vMdGm.png
最基本的解決是超商代繳是要向超商業者申請的,詐騙過不了
這個,我是有朋友真的發生過,收到的繳費單超商可以繳
繳完之後仍然被催收、以及有滯納金
單位說他繳的繳費單不是他們的,該單位不負責~

自此之後他都不相信勞健保寄來的繳費單@@"

但詳細狀況不清楚是勞保或勞退,或者這兩個搞混,或者是真的有假的繳費單或其他狀況等...
繳費單去超商繳會有感熱紙的收據(小白單),上面會寫繳哪種費用,之後要理論也是憑這張去問 https://www.hcct.gov.tw/ch/home.jsp?id=248&parentpath=&mcustomize=faq_view.jsp&dataserno=201704270001&t=FAQ&mserno=201511220004
開串那張勞保跟勞退提撥那種繳費單,其實是投保單位才要擔心的問題
勞保局竟然在假日澄清了
https://www.bli.gov.tw/0107260.html
> 近日民眾於臉書反映收到勞保局所寄發繳款單係詐騙乙事,經查證並詳加瞭解,勞保局澄清,該二封繳款單確係是本局所寄發無誤,一是保險費繳款單(含勞保、職保、就保);另一是勞工退休金繳款單(含雇主提繳費及勞工個人提繳費),請民眾安心。

2022-08-21

cai 13:17:28
這種政策向的謠言很常出現在週末 政府單位沒上班的時候
等到上班日澄清時已經不知道傳到哪邊去了
😢 1
cai 13:17:28
這種政策向的謠言很常出現在週末 政府單位沒上班的時候
等到上班日澄清時已經不知道傳到哪邊去了
iriversland 14:08:39
@iriversland has joined the channel
cai 14:59:46
勞保局竟然在假日澄清了
https://www.bli.gov.tw/0107260.html
> 近日民眾於臉書反映收到勞保局所寄發繳款單係詐騙乙事,經查證並詳加瞭解,勞保局澄清,該二封繳款單確係是本局所寄發無誤,一是保險費繳款單(含勞保、職保、就保);另一是勞工退休金繳款單(含雇主提繳費及勞工個人提繳費),請民眾安心。
1

2022-08-22

cai 00:22:06
https://cofacts.tw/article/2c0dc33pgrled
https://cofacts.tw/article/kdjbe6qh4nci
這篇有影片,台88快速道路是對的
綠色車子跟2017年這部影片很像,不過後面載的東西長不一樣
Ohhh 感謝提供警察護送影片
昨天寫的時候想作為「警察不只會護送燃料棒,其他東西也會」但沒找到
更新回應了
再加上一篇
https://cofacts.tw/article/3dbbag6p54ogq
cai 00:22:06
https://cofacts.tw/article/2c0dc33pgrled
https://cofacts.tw/article/kdjbe6qh4nci
這篇有影片,台88快速道路是對的
綠色車子跟2017年這部影片很像,不過後面載的東西長不一樣
Ohhh 感謝提供警察護送影片
昨天寫的時候想作為「警察不只會護送燃料棒,其他東西也會」但沒找到
更新回應了
再加上一篇
https://cofacts.tw/article/3dbbag6p54ogq
mrorz 23:17:50
這個我覺得太荒謬了,刪文前先來存個檔 XDDDD
https://web.archive.org/web/20220822151702/https://cofacts.tw/article/3azeqffkjbbjt
他們有開youtube跟社團喔~~~
網址還故意仿原版的網址,演超像的
ㄏㄏ
幸好寫回應的時候有把它做存檔,wayback machine 還留存著舊圖
mrorz 23:17:50
這個我覺得太荒謬了,刪文前先來存個檔 XDDDD
https://web.archive.org/web/20220822151702/https://cofacts.tw/article/3azeqffkjbbjt
他們有開youtube跟社團喔~~~
網址還故意仿原版的網址,演超像的
ㄏㄏ
幸好寫回應的時候有把它做存檔,wayback machine 還留存著舊圖
😆 1 😮 1
cai 23:54:47
http://info.csa.org.tw/ 證券商公會的反詐騙專區竟然還在http 😥
我用 Google chrome 捲軸卷不太動
cai 23:54:47
http://info.csa.org.tw/ 證券商公會的反詐騙專區竟然還在http 😥
我用 Google chrome 捲軸卷不太動

2022-08-23

github2 12:32:49

<https://github.com/cofacts/rumors-line-bot/pull/318|#318 Feature/image submit>

送出新圖片在 staging chatbot 上線囉,大家可以測測看~

之後預計會把 staging 再次洗成 production 資料
github2 12:32:49

<https://github.com/cofacts/rumors-line-bot/pull/318|#318 Feature/image submit>

送出新圖片在 staging chatbot 上線囉,大家可以測測看~

之後預計會把 staging 再次洗成 production 資料
github2 12:32:49

<https://github.com/cofacts/rumors-line-bot/issues/306|#306 [Image-M2] LINE bot can submit new images>

送出新圖片在 staging chatbot 上線囉,大家可以測測看~

之後預計會把 staging 再次洗成 production 資料
github2 12:32:49

<https://github.com/cofacts/rumors-line-bot/issues/306|#306 [Image-M2] LINE bot can submit new images>

送出新圖片在 staging chatbot 上線囉,大家可以測測看~

之後預計會把 staging 再次洗成 production 資料
mrorz 13:16:15
送出新圖片在 staging chatbot 上線囉,大家可以測測看~

之後預計會把 staging 再次洗成 production 資料
🙌 1

2022-08-24

github2 13:32:33

<https://github.com/cofacts/rumors-site/pull/501|#501 Add articleTypes URL param without UI>

This PR adds a URL param, `articleTypes`, to rumors-site article list. • Currently we do not officially launch image support, so the UI of this filter is not implemented yet. • Users must *manually specify `articleTypes` in URL*, it is not accessible from UI. • `articleTypes` should be a comma separated list of `ArticleTypeEnum` (`TEXT`, `IMAGE`, `VIDEO`, `AUDIO`). • When not given, `articleTypes` is not specified in `ListArticles`. • If given, `articleTypes` is specified and thus would <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/queries/ListArticles.js#L513-L525|override `MEDIA_ARTICLE_SUPPORT` flag in rumors-api>. *Screenshot* *Only images* <https://user-images.githubusercontent.com/108608/186336655-06eccc25-366b-4ef7-84bc-2ba151bad949.png|image> *Only text* <https://user-images.githubusercontent.com/108608/186336735-0c53f560-6b84-440f-9633-800b66d20c6b.png|image> *Not specified* The result depends on if the API has turned on `MEDIA_ARTICLE_SUPPORT` flag. On staging it is turned on, so it does not limit the article type to just text. <https://user-images.githubusercontent.com/108608/186336888-e4f02d18-1fb3-49d0-9431-f656d851678b.png|image>

:white_check_mark: All checks have passed

github2 13:32:33

<https://github.com/cofacts/rumors-site/pull/501|#501 Add articleTypes URL param without UI>

This PR adds a URL param, `articleTypes`, to rumors-site article list. • Currently we do not officially launch image support, so the UI of this filter is not implemented yet. • Users must *manually specify `articleTypes` in URL*, it is not accessible from UI. • `articleTypes` should be a comma separated list of `ArticleTypeEnum` (`TEXT`, `IMAGE`, `VIDEO`, `AUDIO`). • When not given, `articleTypes` is not specified in `ListArticles`. • If given, `articleTypes` is specified and thus would <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/queries/ListArticles.js#L513-L525|override `MEDIA_ARTICLE_SUPPORT` flag in rumors-api>. *Screenshot* *Only images* <https://user-images.githubusercontent.com/108608/186336655-06eccc25-366b-4ef7-84bc-2ba151bad949.png|image> *Only text* <https://user-images.githubusercontent.com/108608/186336735-0c53f560-6b84-440f-9633-800b66d20c6b.png|image> *Not specified* The result depends on if the API has turned on `MEDIA_ARTICLE_SUPPORT` flag. On staging it is turned on, so it does not limit the article type to just text. <https://user-images.githubusercontent.com/108608/186336888-e4f02d18-1fb3-49d0-9431-f656d851678b.png|image>

:white_check_mark: All checks have passed

github2 13:34:23

<https://github.com/cofacts/rumors-site/pull/501#issuecomment-1225218247|Comment on #501 Add articleTypes URL param without UI>

<https://coveralls.io/builds/51897634|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/e0130121d06d74d2a5bf7c4bcc9667fad9048c93|e013012> on article-type* into *<https://github.com/cofacts/rumors-site/commit/1808d09f411c313454f4214748a9c2dba0627225|1808d09> on master*.

github2 13:34:23

<https://github.com/cofacts/rumors-site/pull/501#issuecomment-1225218247|Comment on #501 Add articleTypes URL param without UI>

<https://coveralls.io/builds/51897634|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/e0130121d06d74d2a5bf7c4bcc9667fad9048c93|e013012> on article-type* into *<https://github.com/cofacts/rumors-site/commit/1808d09f411c313454f4214748a9c2dba0627225|1808d09> on master*.

cai 19:56:50
蠻完整的假投資詐騙流程新聞
https://www.ettoday.net/news/20220824/2323325.htm
議員的FB 比較多截圖

ETtoday新聞雲

Kevin老師有急事找你!台中男誤信證券簡訊 遭吸乾1400萬 | ETtoday社會新聞 | ETtoday新聞雲

近期許多民眾都收炒股、投資等詐騙簡訊,對方假冒證券商、銀行等名義寄簡訊騷擾,還會裝熟抱怨民眾消失很久沒聯絡,或稱有急事要求人加通訊軟體。台中就有一名張先生收到一封簡訊,自稱Kevin老師能介紹飆股,結果誤信加入群組及對方設立的App操作股票,前後宛如鬼遮眼般匯出1400萬元,隨即被踢出群組及封鎖帳號,張先生怒向議員檢舉,也希望提醒其他人不要受害。

facebook.com

Log in or sign up to view

See posts, photos and more on Facebook.

關鍵字:`晚上8點開直播`宣稱會告知如何購入股票穩賺不賠
cai 19:56:50
蠻完整的假投資詐騙流程新聞
https://www.ettoday.net/news/20220824/2323325.htm
議員的FB 比較多截圖
關鍵字:`晚上8點開直播`宣稱會告知如何購入股票穩賺不賠

2022-08-25

mrorz 02:04:54
今天測試的 LINE bot 傳圖片的部分上線囉
目前還沒有正式上線,所以要看圖的話必須用下面的 URL (需要指定 articleTypes URL param)
https://cofacts.tw/articles?articleTypes=IMAGE

目前是可以針對這些圖片撰寫回應的,也會計算有幾個人回報,基本上應該跟一般訊息都一樣。

要請大家幫忙注意的是:
1. 這幾天網友傳圖的樣態,是否有重複或者是不適合的圖片、不適合的比例有多高。
2. 網站、LINE 機器人最近是否穩定。圖片處理會佔據部分資源,想要釐清目前的主機是否可以承受。
雖然沒有公開說可以傳圖片,但其實無時無刻都有人傳圖片給 LINE 機器人,所以即使沒有公開宣傳,還是可以收得到圖片的。

(btw https://cofacts.tw/article/-ooD0YIBv5it-Cx_DlFT 這個是我測試用的。放了有點後悔,因為這樣這張的送出時間就會是今天,而不是這張圖真正在傳的時候 QQ
我們還是不要隨便在 production 傳圖測試比較好)
關於把之前蒐集到的圖片放上去,我在想要不要直接 deploy 到 production 耶

畢竟現在 production 上已經有人在傳圖了,有些圖其實是直接有重複的。

直接 deploy 上去就可以省去從 staging --> production 的圖片們 merge 的這一步 merge 的部分,如果有人上傳舊圖,也會直接使用舊圖。
然後我們直接在 production 透過 https://cofacts.tw/articles?articleTypes=IMAGE 檢視說有沒有 inappropriate image 需要下架
我發現最近大概一天都會有 100 張圖進帳
(dedup 前)
mrorz 02:04:54
今天測試的 LINE bot 傳圖片的部分上線囉
目前還沒有正式上線,所以要看圖的話必須用下面的 URL (需要指定 articleTypes URL param)
https://cofacts.tw/articles?articleTypes=IMAGE

目前是可以針對這些圖片撰寫回應的,也會計算有幾個人回報,基本上應該跟一般訊息都一樣。

要請大家幫忙注意的是:
1. 這幾天網友傳圖的樣態,是否有重複或者是不適合的圖片、不適合的比例有多高
2. 網站、LINE 機器人最近是否穩定
雖然沒有公開說可以傳圖片,但其實無時無刻都有人傳圖片給 LINE 機器人,所以即使沒有公開宣傳,還是可以收得到圖片的。

(btw https://cofacts.tw/article/-ooD0YIBv5it-Cx_DlFT 這個是我測試用的。放了有點後悔,因為這樣這張的送出時間就會是今天,而不是這張圖真正在傳的時候 QQ)
關於把之前蒐集到的圖片放上去,我在想要不要直接 deploy 到 production 耶

畢竟現在 production 上已經有人在傳圖了,有些圖其實是直接有重複的。

直接 deploy 上去就可以省去從 staging --> production 的圖片們 merge 的這一步 merge 的部分,如果有人上傳舊圖,也會直接使用舊圖。
然後我們直接在 production 透過 https://cofacts.tw/articles?articleTypes=IMAGE 檢視說有沒有 inappropriate image 需要下架
我發現最近大概一天都會有 100 張圖進帳
(dedup 前)
mrorz 02:06:30
大家覺得我應該在 FB group 這裡也跟大家說圖片正在測試中、請大家注意網站穩定度嗎
mrorz 02:06:30
大家覺得我應該在 FB group 這裡也跟大家說圖片正在測試中、請大家注意網站穩定度嗎
Peter 11:32:27
大家好!我10/21-22會以g0v 社群參與者的身分去青發署舉辦的2022國際青年趨勢論壇現場擺攤介紹g0v,想問問 cofacts 最近有沒有需要幫忙介紹或讓大家來參與的內容,我們可以幫忙介紹!
我們有折疊傳單~~我覺得可以發起來 XD
@bil 覺得如何
啊但傳單是中文 QQ
一個解套是可以用QR 碼放英文的內容,貼在傳單上
我有英文傳單,我找一找
好的!
所以現場與會者都是外國人嗎
不是喔,都有
Peter 11:32:27
大家好!我10/21-22會以g0v 社群參與者的身分去青發署舉辦的2022國際青年趨勢論壇現場擺攤介紹g0v,想問問 cofacts 最近有沒有需要幫忙介紹或讓大家來參與的內容,我們可以幫忙介紹!
我們有折疊傳單~~我覺得可以發起來 XD
@bil 覺得如何
啊但傳單是中文 QQ
一個解套是可以用QR 碼放英文的內容,貼在傳單上
我有英文傳單,我找一找
好的!
所以現場與會者都是外國人嗎
不是喔,都有
mrorz 12:30:50
關於把之前蒐集到的圖片放上去,我在想要不要直接 deploy 到 production 耶

畢竟現在 production 上已經有人在傳圖了,有些圖其實是直接有重複的。

直接 deploy 上去就可以省去從 staging --> production 的圖片們 merge 的這一步 merge 的部分,如果有人上傳舊圖,也會直接使用舊圖。
cai 19:37:17
65歲免費領一份5劑快篩這圖片有重複
https://cofacts.tw/article/o4pH1IIBv5it-Cx_fFUp
https://cofacts.tw/article/pYpI1IIBv5it-Cx_hFVE
https://cofacts.tw/article/PIq81IIBv5it-Cx_HVbc
https://cofacts.tw/article/gIow1IIBv5it-Cx_x1UF
我們現在用來比對圖片的演算法,雖然可以找到相似圖,但沒有很厲害,剛好這幾張比對不到QQ

好奇的話可以用這個網站比對每一則原圖
(登入 Cofacts 後,在文章頁面點圖片就可以看到原圖)
https://online-image-comparison.com/
蝙蝠的 3 張
https://cofacts.tw/article/q4oK1YIBv5it-Cx_b1ZI
是同時間送出的,間隔不到一秒
是送出按鈕直接按三次嗎
我調一下 chatbot log 好了
實在滿奇怪
昨天會議中檢討的重複圖片的問題 + bugfix 已經在主站上線囉

• 隨著修復 chatbot 的圖片搜尋功能,未來 LINE 使用者可以正常看到相似圖片,在圖片相同的時候也會阻擋使用者創建新 article
• 針對已經在網站上的相似圖片,網站的「相似可疑訊息」也會列出 search hash 相同的圖片,方便共用回應與標記分類
現在 chatbot 可以正常查詢圖片並且回覆查核回應囉~
cai 19:37:17
65歲免費領一份5劑快篩這圖片有重複
https://cofacts.tw/article/o4pH1IIBv5it-Cx_fFUp
https://cofacts.tw/article/pYpI1IIBv5it-Cx_hFVE
https://cofacts.tw/article/PIq81IIBv5it-Cx_HVbc
https://cofacts.tw/article/gIow1IIBv5it-Cx_x1UF
我們現在用來比對圖片的演算法,雖然可以找到相似圖,但沒有很厲害,剛好這幾張比對不到QQ

好奇的話可以用這個網站比對每一則原圖
(登入 Cofacts 後,在文章頁面點圖片就可以看到原圖)
https://online-image-comparison.com/
蝙蝠的 3 張
https://cofacts.tw/article/q4oK1YIBv5it-Cx_b1ZI
是同時間送出的,間隔不到一秒
是送出按鈕直接按三次嗎
我調一下 chatbot log 好了
實在滿奇怪
昨天會議中檢討的重複圖片的問題 + bugfix 已經在主站上線囉

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

2022-08-26

mrorz 14:32:03
目前正在 colab 上算每張之前收到的 LINE 網傳圖片的 image hash,有 12 萬張圖的 hash 要算。

~算 hash 什麼的聽起來像在挖礦~
calculate-hash.gif
3

2022-08-27

cai 14:32:20
https://cofacts.tw/article/3e6dywrq7k682 防疫補助詐騙的網址出現從gov 變成 g0v 😆
居然 wwwwww
cai 14:32:20
https://cofacts.tw/article/3e6dywrq7k682 防疫補助詐騙的網址出現從gov 變成 g0v 😆
居然 wwwwww
😆 1
cai 20:32:07
https://www.cma.edu.tw/news_detail-1227.html 這是要角度要對多準才會變這篇啊 https://cofacts.tw/article/rIps3YIBv5it-Cx_ql6D
找不到青年日報原圖
Oh 原來青年日報有做 youtube
https://www.youtube.com/channel/UC-g1gwSLD0PsbecHcPI8QyA/videos
格式還不錯
2018的
最下面是環球網,直接是官媒
cai 20:32:07
這是要角度要對多準才會變這篇啊
陸軍官校版本 https://www.cma.edu.tw/news_detail-1227.html
謠言版 https://cofacts.tw/article/rIps3YIBv5it-Cx_ql6D
找不到青年日報原圖
Oh 原來青年日報有做 youtube
https://www.youtube.com/channel/UC-g1gwSLD0PsbecHcPI8QyA/videos
格式還不錯
2018的
最下面是環球網,直接是官媒
😂 1

2022-08-28

mrorz 15:11:49
Google drive 的圖片的 hash 全部算完了
• Drive 裡的圖共有 126,535 張
• hash 相同出現超過兩次的有 8910 張
• 超過 3, 4, 5, 6 次的分別為 4276, 2855, 2262, 1858
有興趣的可以到 media_entries spreadsheet 的 Preview sheet 瀏覽 (需 request access)
可以手動輸入 page 換頁,或者是調高出現次數門檻
image.png
image.png
我是覺得可以考慮超過 3 次的圖(4,276 張)就好
畢竟 2 次的有些圖也好久了
或者是最新 2022 年還有再傳的,有 2 次就納入
其他的舊圖, 3 次才納入
接續「讓編輯可以共編圖上的文字」的話題
我寫了共編圖中文字 / 文字辨識 / 逐字稿的 design doc
https://g0v.hackmd.io/OhGIQzoxR5eF6audQuS_FQ

裡面包含:
UI design Figma
UX flow 試玩(建議用手機玩玩看,看建立逐字稿流程是否直覺)
◦ 有考慮到「在儲存逐字稿時,如果有人搶先儲存逐字稿,那要怎麼處理衝突」的流程!
• 資料庫欄位
• API 設計
請大家看看~~提出一些需要討論的點
• 共編「圖上文字」英文這裡用 transcript,中文目前有「圖中文字」、「文字辨識」、「逐字稿」等命名,可以想一個好名字
• 之後支援影片跟聲音的時候,如何支援很長的影片與聲音共編逐字稿(hackmd 裡面有塊紅色背景的區塊在討論此議題)
上面的 design doc 忘記設計說
如果有 similar article (一樣是圖,hash 相近) 已經有 transcript
那是不是能有簡單的套用另一張圖 transcript 的功能
Figma 上補了「similar article (一樣是圖,hash 相近) 已經有 transcript」的狀況
正在把 8,900 張出現過兩次或以上的圖上傳到 google cloud storage 中
1
mrorz 16:37:35
現在桌面版 Google Chrome 也支援 Lens 了
image.png
cai 21:12:52
https://cofacts.tw/article/1fc2tqyqya8y8
廢死這篇的文字 用google搜尋可找到兩個時間點
2015/6/2
這篇說在新聞留言看到的,原新聞已失連 https://www.mobile01.com/topicdetail.php?f=638&t=4406082
FB的留言區 https://www.facebook.com/tsaiingwen/photos/a.10151242056081065/10152722158506065/?comment_id=10152726822781065
2016/3/28(小燈泡事件) ,這次有KMT台中分部發文
https://www.facebook.com/story.php?story_fbid=976048009175162&id=256015127845124
2015/6/2 的我猜可能跟 6/1 苗博雅去三立54新觀點講廢死議題有關,名單還要查
感謝,我來看看
👍 1
cai 21:12:52
https://cofacts.tw/article/1fc2tqyqya8y8
廢死這篇的文字 用google搜尋可找到兩個時間點
2015/6/2
這篇說在新聞留言看到的,原新聞已失連 https://www.mobile01.com/topicdetail.php?f=638&t=4406082
FB的留言區 https://www.facebook.com/tsaiingwen/photos/a.10151242056081065/10152722158506065/?comment_id=10152726822781065
2016/3/28(小燈泡事件) ,這次有KMT台中分部發文
https://www.facebook.com/story.php?story_fbid=976048009175162&id=256015127845124
2015/6/2 的我猜可能跟 6/1 苗博雅去三立54新觀點講廢死議題有關,名單還要查
感謝,我來看看

2022-08-29

github2 00:25:27

<https://github.com/cofacts/media-manager/pull/9|#9 Allow query by ID>

This PR adds functionality to search similar media entries by media entry ID. ``` mediaManager.query({ id: mediaEntryId }); ``` Note that it is prohibited that `id` and `url` are used together.

github2 00:25:27

<https://github.com/cofacts/media-manager/pull/9|#9 Allow query by ID>

This PR adds functionality to search similar media entries by media entry ID. ``` mediaManager.query({ id: mediaEntryId }); ``` Note that it is prohibited that `id` and `url` are used together.

mrorz 00:30:17
我要來把 staging 洗成 production 資料庫囉
同時也會把 staging 接到 production 的 google cloud storage 所以圖檔會同步
mrorz 00:30:17
我要來把 staging 洗成 production 資料庫囉
同時也會把 staging 接到 production 的 google cloud storage 所以圖檔會同步
github2 02:38:20

<https://github.com/cofacts/rumors-site/pull/502|#502 Support showing similar images in side section>

Support image articles be displayed in the similar article section in article detail page. Depends on API <https://github.com/cofacts/rumors-api/pull/291|cofacts/rumors-api#291> *Storybook* Mobile <https://user-images.githubusercontent.com/108608/187089547-c315e151-9659-4629-b12f-7e3072ad91f7.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089552-1614b89c-2425-4b4f-a1ff-63d1cc73608d.png|image> *Real example* Mobile <https://user-images.githubusercontent.com/108608/187089493-baac15b3-a4fe-467d-ad3e-9fce860a9d9c.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089466-29347cc9-0ecc-4b81-a73a-c63f98e722ac.png|image>

:white_check_mark: All checks have passed

github2 02:38:20

<https://github.com/cofacts/rumors-site/pull/502|#502 Support showing similar images in side section>

Support image articles be displayed in the similar article section in article detail page. Depends on API <https://github.com/cofacts/rumors-api/pull/291|cofacts/rumors-api#291> *Storybook* Mobile <https://user-images.githubusercontent.com/108608/187089547-c315e151-9659-4629-b12f-7e3072ad91f7.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089552-1614b89c-2425-4b4f-a1ff-63d1cc73608d.png|image> *Real example* Mobile <https://user-images.githubusercontent.com/108608/187089493-baac15b3-a4fe-467d-ad3e-9fce860a9d9c.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089466-29347cc9-0ecc-4b81-a73a-c63f98e722ac.png|image>

:white_check_mark: All checks have passed

github2 02:40:14

<https://github.com/cofacts/rumors-site/pull/502#issuecomment-1229528190|Comment on #502 Support showing similar images in side section>

<https://coveralls.io/builds/52007988|Coverage Status> Coverage increased (+0.03%) to 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/217fde412537e6c0e5fae4b82144d347ee862239|217fde4> on related-media-articles* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.

github2 02:40:14

<https://github.com/cofacts/rumors-site/pull/502#issuecomment-1229528190|Comment on #502 Support showing similar images in side section>

<https://coveralls.io/builds/52007988|Coverage Status> Coverage increased (+0.03%) to 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/217fde412537e6c0e5fae4b82144d347ee862239|217fde4> on related-media-articles* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.

cai 14:15:06
台南 加油站 迷藥 傳單 系列
附的是`語音檔`,沒詳細內容難比對
https://cofacts.tw/article/3pi6xr6i5ad0k
https://cofacts.tw/article/1ymfzql25c6zz
https://cofacts.tw/article/31g3rxkua4bd3
https://cofacts.tw/article/1e888y26b8pol

與以前流傳過的謠言類似點
• 女性
• 加油站
• 名片→傳單
• 迷藥
• 去民宅求助
https://tfc-taiwan.org.tw/articles/748
https://news.ltn.com.tw/news/society/breakingnews/1630802
https://udn.com/news/story/7315/6573135
看樣子地點會亂改,這版本是恆春的
新聞寫的語音內容
> 在社群軟體LINE群組聽到一段女性錄音,有一名叫「玉婷」的親戚在加油站拿到傳單,之後開始暈眩且被跟蹤,趕緊停在別人家門口且報警才未受害,該傳單經警方化驗有迷藥成分,因此呼籲大家別拿傳單。
這個語音查核中心回了
https://tfc-taiwan.org.tw/articles/8082
cai 14:15:06
台南 加油站 迷藥 傳單 系列
附的是`語音檔`,沒詳細內容難比對
https://cofacts.tw/article/3pi6xr6i5ad0k
https://cofacts.tw/article/1ymfzql25c6zz
https://cofacts.tw/article/31g3rxkua4bd3
https://cofacts.tw/article/1e888y26b8pol

與以前流傳過的謠言類似點
• 女性
• 加油站
• 名片→傳單
• 迷藥
• 去民宅求助
https://tfc-taiwan.org.tw/articles/748
https://news.ltn.com.tw/news/society/breakingnews/1630802
https://udn.com/news/story/7315/6573135
看樣子地點會亂改,這版本是恆春的
新聞寫的語音內容
> 在社群軟體LINE群組聽到一段女性錄音,有一名叫「玉婷」的親戚在加油站拿到傳單,之後開始暈眩且被跟蹤,趕緊停在別人家門口且報警才未受害,該傳單經警方化驗有迷藥成分,因此呼籲大家別拿傳單。
這個語音查核中心回了
https://tfc-taiwan.org.tw/articles/8082
😮 1
mrorz 21:41:19
接續「讓編輯可以共編圖上的文字」的話題
我寫了共編圖中文字 / 文字辨識 / 逐字稿的 design doc
https://g0v.hackmd.io/OhGIQzoxR5eF6audQuS_FQ

裡面包含:
UI design Figma
UX flow 試玩(建議用手機玩玩看,看建立逐字稿流程是否直覺)
◦ 有考慮到「在儲存逐字稿時,如果有人搶先儲存逐字稿,那要怎麼處理衝突」的流程!
• 資料庫欄位
• API 設計
請大家看看~~提出一些需要討論的點
• 共編「圖上文字」英文這裡用 transcript,中文目前有「圖中文字」、「文字辨識」、「逐字稿」等命名,可以想一個好名字
• 之後支援影片跟聲音的時候,如何支援很長的影片與聲音共編逐字稿(hackmd 裡面有塊紅色背景的區塊在討論此議題)

g0v.hackmd.io

Cofacts crowd-sourced transcript design doc - HackMD

2022-08-30

mrorz 20:12:52
這個語音查核中心回了
https://tfc-taiwan.org.tw/articles/8082
mrorz 21:36:18
這篇的網友補充被檢舉了
https://cofacts.tw/article/r9mm7ix480uc
附註貼了刑法誹謗罪的法條

我調查了一下,看起來是這樣:
• 好像有個叫做子楓Aaron 的 LINE 灰盾牌帳號在騙人 https://www.dcard.tw/f/talk/p/239246678
• Cofacts 上另一篇可能是罐頭回覆的,被送進來,然後網友補充裡面有 https://cofacts.tw/article/2zq2sp8f1frzq
• 我在想是不是冒名頂替,所以想找「許子楓」的 IG 或 FB。IG 這裡有:https://www.youtube.com/watch?v=PZY_TxjmelE 但點進去已經關閉。因此找不到澄清文。
• 從該 Youtube 「智趣娛樂」名字找不到其他資訊,Dcard 有人說是直播代操粉絲工作室
我的想法是,因為無法查證(沒有公開帳號發布澄清文) + 確實有人用這個名字在詐騙,因此想要判定為 NOOP (不做事情),若真的是被冒名,就請對方來信這樣。
大家覺得如何

Dcard

許子楓是詐騙嗎? - 閒聊板 | Dcard

一開始,某人加了我賴,然後語音問我是不是在哪裡要找他買衣服的,我因為滿頭問號加上不認識,所以沒有理他,過了一段時間他又打字問了一次,最後說是個誤會,然後他就很直接的自我介紹、自己平常會做的事,說他當過 - 生活

mrorz 21:36:18
這篇的網友補充被檢舉了
https://cofacts.tw/article/r9mm7ix480uc
附註貼了刑法誹謗罪的法條

我調查了一下,看起來是這樣:
• 好像有個叫做子楓Aaron 的 LINE 灰盾牌帳號在騙人 https://www.dcard.tw/f/talk/p/239246678
• Cofacts 上另一篇可能是罐頭回覆的,被送進來,然後網友補充裡面有 https://cofacts.tw/article/2zq2sp8f1frzq
• 我在想是不是冒名頂替,所以想找「許子楓」的 IG 或 FB。IG 這裡有:https://www.youtube.com/watch?v=PZY_TxjmelE 但點進去已經關閉。因此找不到澄清文。
• 從該 Youtube 「智趣娛樂」名字找不到其他資訊,Dcard 有人說是直播代操粉絲工作室
我的想法是,因為無法查證(沒有公開帳號發布澄清文) + 確實有人用這個名字在詐騙,因此想要判定為 NOOP (不做事情),若真的是被冒名,就請對方來信這樣。
大家覺得如何
mrorz 21:43:58
上面的 design doc 忘記設計說
如果有 similar article (一樣是圖,hash 相近) 已經有 transcript
那是不是能有簡單的套用另一張圖 transcript 的功能
canadian_aaron 22:42:17
i am certain i am not 子枫Aaron 😉
canadian_aaron 22:42:17
i am certain i am not 子枫Aaron 😉
😂 2

2022-08-31

github2 05:43:31

<https://github.com/cofacts/rumors-fb-bot/pull/39|#39 Bump moment-timezone from 0.5.21 to 0.5.37>

Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.21 to 0.5.37. Release notes _Sourced from <https://github.com/moment/moment-timezone/releases|moment-timezone's releases>._ &gt; *0.5.34* &gt; &gt; • Updated data to IANA TZDB `2021e` &gt; &gt; *Release 0.5.33* &gt; &gt; • Updated data to IANA TZDB `2021a` &gt; &gt; *Release 0.5.32* &gt; &gt; • Updated data to IANA TZDB `2020d` &gt; &gt; *Release 0.5.31* &gt; &gt; Fixed Travis builds for Node.js 4 and 6 &gt; &gt; *Release 0.5.28* &gt; *`0.5.29` _2020-02-21_* &gt; &gt; Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@​adgrace`>: &gt; &gt; • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country &gt; • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone &gt; • Added a method `moment.tz.countries()` to get all country codes &gt; • And as you know `moment.tz.names()` already exists &gt; &gt; *Release 0.5.27* &gt; *`0.5.27` _2019-10-14_* &gt; &gt; • Updated data to IANA TZDB `2019c &gt; &gt; *Release 0.5.26* &gt; &gt; • Updated data to IANA TZDB `2019b` &gt; • Fix: stabilize Array.sort <https://github-redirect.dependabot.com/moment/moment-timezone/pull/762|#762> &gt; &gt; *Release 0.5.25* &gt; &gt; • Fix `moment.tz.dataVersion` to return `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/742|#742> &gt; • Update path in bower.json &gt; &gt; *Release 0.5.24* &gt; &gt; • Updated data to IANA TZDB `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/737|#737> &gt; • Start shipping both a 1970-1930 file and a rolling 10-year file <https://github-redirect.dependabot.com/moment/moment-timezone/issues/614|#614> <https://github-redirect.dependabot.com/moment/moment-timezone/issues/697|#697> &gt; • Fixed bug where `_z` time zone name was not cleared with `.local()` or `.utcOffset(offset)` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/738|#738> &gt; &gt; *Release 0.5.23* &gt; &gt; • Fix minor issue with tz guessing in Russia <https://github-redirect.dependabot.com/moment/moment-timezone/issues/691|#691> &gt; &gt; *Release 0.5.22* &gt; &gt; • Updated data to IANA TZDB 2018g <https://github-redirect.dependabot.com/moment/moment-timezone/issues/689|#689> &gt; • Fix issue with missing LMT entries for some zones, and fix data builds on Linux and Windows <https://github-redirect.dependabot.com/moment/moment-timezone/issues/308|#308> Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ &gt; *`0.5.37` _2022.08-25_* &gt; &gt; • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> &gt; &gt; *`0.5.36` _2022.08-25_* &gt; &gt; • IANA TZDB 2022c &gt; • improvements/fixes to data pipeline &gt; &gt; *`0.5.35` _2022-08-23_* &gt; &gt; • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> &gt; • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> &gt; &gt; Thanks to the OpenSSF Alpha-Omega project for reporting these! &gt; &gt; *`0.5.34` _2020-11-10_* &gt; &gt; • Updated data to IANA TZDB `2021e` &gt; &gt; *`0.5.33` _2020-11-15_* &gt; &gt; • Updated data to IANA TZDB `2021a` &gt; &gt; *`0.5.32` _2020-11-14_* &gt; &gt; • Updated data to IANA TZDB `2020d` &gt; &gt; *`0.5.31` _2020-05-16_* &gt; &gt; • Fixed Travis builds for Node.js 4 and 6 &gt; &gt; *`0.5.30` _2020-05-16_* &gt; &gt; • Updated data to IANA TZDB `2020a` &gt; • Fixed typescript definitions &gt; &gt; NOTE: You might need to un-install `@​types/moment-timezone`. Check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/858|moment/moment-timezone#858> for more info &gt; &gt; *`0.5.29` _2020-05-16_* &gt; &gt; • Merged fix of es6 module loading issue <https://github.com/moment/moment-timezone/commit/1fd42349189b24e15c60f162dc8c40b42db79dfe|moment/moment-timezone@1fd4234> &gt; • Merged PR with typescript declarations <https://github.com/moment/moment-timezone/commit/ed529ea6fbcc70315c0c3f6d7c7cb70eadf56b03|moment/moment-timezone@ed529ea> &gt; • Merged fixes to changelog <https://github.com/moment/moment-timezone/commit/adb7d7b43c7328d814311ac1355bfeef88eab6e8|moment/moment-timezone@adb7d7b> &gt; &gt; *`0.5.28` _2020-02-21_* &gt; &gt; Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@​adgrace`>: &gt; &gt; • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country &gt; • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone &gt; • Added a method `moment.tz.countries()` to get all country codes &gt; • And as you know `moment.tz.zones()` already exists &gt; &gt; *`0.5.27` _2019-10-14_* &gt; &gt; • Updated data to IANA TZDB `2019c` &gt; &gt; *`0.5.26` _2019-06-06_* &gt; &gt; • Updated data to IANA TZDB `2019b` ... (truncated) Commits • See full diff in <https://github.com/moment/moment-timezone/commits/0.5.37|compare view> <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 05:43:31

<https://github.com/cofacts/rumors-fb-bot/pull/39|#39 Bump moment-timezone from 0.5.21 to 0.5.37>

Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.21 to 0.5.37. Release notes _Sourced from <https://github.com/moment/moment-timezone/releases|moment-timezone's releases>._ &gt; *0.5.34* &gt; &gt; • Updated data to IANA TZDB `2021e` &gt; &gt; *Release 0.5.33* &gt; &gt; • Updated data to IANA TZDB `2021a` &gt; &gt; *Release 0.5.32* &gt; &gt; • Updated data to IANA TZDB `2020d` &gt; &gt; *Release 0.5.31* &gt; &gt; Fixed Travis builds for Node.js 4 and 6 &gt; &gt; *Release 0.5.28* &gt; *`0.5.29` _2020-02-21_* &gt; &gt; Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@​adgrace`>: &gt; &gt; • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country &gt; • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone &gt; • Added a method `moment.tz.countries()` to get all country codes &gt; • And as you know `moment.tz.names()` already exists &gt; &gt; *Release 0.5.27* &gt; *`0.5.27` _2019-10-14_* &gt; &gt; • Updated data to IANA TZDB `2019c &gt; &gt; *Release 0.5.26* &gt; &gt; • Updated data to IANA TZDB `2019b` &gt; • Fix: stabilize Array.sort <https://github-redirect.dependabot.com/moment/moment-timezone/pull/762|#762> &gt; &gt; *Release 0.5.25* &gt; &gt; • Fix `moment.tz.dataVersion` to return `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/742|#742> &gt; • Update path in bower.json &gt; &gt; *Release 0.5.24* &gt; &gt; • Updated data to IANA TZDB `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/737|#737> &gt; • Start shipping both a 1970-1930 file and a rolling 10-year file <https://github-redirect.dependabot.com/moment/moment-timezone/issues/614|#614> <https://github-redirect.dependabot.com/moment/moment-timezone/issues/697|#697> &gt; • Fixed bug where `_z` time zone name was not cleared with `.local()` or `.utcOffset(offset)` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/738|#738> &gt; &gt; *Release 0.5.23* &gt; &gt; • Fix minor issue with tz guessing in Russia <https://github-redirect.dependabot.com/moment/moment-timezone/issues/691|#691> &gt; &gt; *Release 0.5.22* &gt; &gt; • Updated data to IANA TZDB 2018g <https://github-redirect.dependabot.com/moment/moment-timezone/issues/689|#689> &gt; • Fix issue with missing LMT entries for some zones, and fix data builds on Linux and Windows <https://github-redirect.dependabot.com/moment/moment-timezone/issues/308|#308> Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ &gt; *`0.5.37` _2022.08-25_* &gt; &gt; • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> &gt; &gt; *`0.5.36` _2022.08-25_* &gt; &gt; • IANA TZDB 2022c &gt; • improvements/fixes to data pipeline &gt; &gt; *`0.5.35` _2022-08-23_* &gt; &gt; • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> &gt; • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> &gt; &gt; Thanks to the OpenSSF Alpha-Omega project for reporting these! &gt; &gt; *`0.5.34` _2020-11-10_* &gt; &gt; • Updated data to IANA TZDB `2021e` &gt; &gt; *`0.5.33` _2020-11-15_* &gt; &gt; • Updated data to IANA TZDB `2021a` &gt; &gt; *`0.5.32` _2020-11-14_* &gt; &gt; • Updated data to IANA TZDB `2020d` &gt; &gt; *`0.5.31` _2020-05-16_* &gt; &gt; • Fixed Travis builds for Node.js 4 and 6 &gt; &gt; *`0.5.30` _2020-05-16_* &gt; &gt; • Updated data to IANA TZDB `2020a` &gt; • Fixed typescript definitions &gt; &gt; NOTE: You might need to un-install `@​types/moment-timezone`. Check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/858|moment/moment-timezone#858> for more info &gt; &gt; *`0.5.29` _2020-05-16_* &gt; &gt; • Merged fix of es6 module loading issue <https://github.com/moment/moment-timezone/commit/1fd42349189b24e15c60f162dc8c40b42db79dfe|moment/moment-timezone@1fd4234> &gt; • Merged PR with typescript declarations <https://github.com/moment/moment-timezone/commit/ed529ea6fbcc70315c0c3f6d7c7cb70eadf56b03|moment/moment-timezone@ed529ea> &gt; • Merged fixes to changelog <https://github.com/moment/moment-timezone/commit/adb7d7b43c7328d814311ac1355bfeef88eab6e8|moment/moment-timezone@adb7d7b> &gt; &gt; *`0.5.28` _2020-02-21_* &gt; &gt; Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@​adgrace`>: &gt; &gt; • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country &gt; • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone &gt; • Added a method `moment.tz.countries()` to get all country codes &gt; • And as you know `moment.tz.zones()` already exists &gt; &gt; *`0.5.27` _2019-10-14_* &gt; &gt; • Updated data to IANA TZDB `2019c` &gt; &gt; *`0.5.26` _2019-06-06_* &gt; &gt; • Updated data to IANA TZDB `2019b` ... (truncated) Commits • See full diff in <https://github.com/moment/moment-timezone/commits/0.5.37|compare view> <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>.

Lucien Hsu 09:49:34
@meteor831 has joined the channel
github2 14:18:53

<https://github.com/cofacts/rumors-site/pull/503|#503 Bump moment-timezone from 0.5.34 to 0.5.37>

Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.34 to 0.5.37. Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ &gt; *`0.5.37` _2022.08-25_* &gt; &gt; • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> &gt; &gt; *`0.5.36` _2022.08-25_* &gt; &gt; • IANA TZDB 2022c &gt; • improvements/fixes to data pipeline &gt; &gt; *`0.5.35` _2022-08-23_* &gt; &gt; • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> &gt; • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> &gt; &gt; Thanks to the OpenSSF Alpha-Omega project for reporting these! Commits • <https://github.com/moment/moment-timezone/commit/ffe6f340a6bdae6be1cbc1cbef4a4f2b87e2c63c|`ffe6f34`> Add changelog for 0.5.37 • <https://github.com/moment/moment-timezone/commit/450ca6304ba62baf27817ed7840828eee4e3b0c5|`450ca63`> Bump version to 0.5.37 • <https://github.com/moment/moment-timezone/commit/95f1a9b5cd3a15b8c75bd36029152ff1b43a5136|`95f1a9b`> Build moment-timezone 0.5.36 • <https://github.com/moment/moment-timezone/commit/abba28c7b0e1faf7df8592806007fcb2753b3078|`abba28c`> Add changelog for 0.5.36 • <https://github.com/moment/moment-timezone/commit/ac6de03cf34610068185961613d719bc050c7d2b|`ac6de03`> Bump version to 0.5.36 • <https://github.com/moment/moment-timezone/commit/7a5cadf9cbece0a9c7b9da0ee244c21375eb33a6|`7a5cadf`> tests: Fix country tests for 2022c • <https://github.com/moment/moment-timezone/commit/6754c75f5be4fbb16e90e336c9decbad6b506388|`6754c75`> data: generate 2022c data+tests • <https://github.com/moment/moment-timezone/commit/f74a364b1aac2c96cedd0a8cf5c7188268b9bcde|`f74a364`> bugfix: Wipe tests/zones before generation • <https://github.com/moment/moment-timezone/commit/e850f9fa6d3b440c51ae0cda7d9d573627839167|`e850f9f`> grunt: do not bundle zone and contry tests • <https://github.com/moment/moment-timezone/commit/f13e22b069f9115eddad5294a4c0f5335c61590a|`f13e22b`> data: automatically create data/*/VERSION.json for latest • Additional commits viewable in <https://github.com/moment/moment-timezone/compare/0.5.34...0.5.37|compare view> <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-site/network/alerts|Security Alerts page>.

:white_check_mark: All checks have passed

github2 14:18:53

<https://github.com/cofacts/rumors-site/pull/503|#503 Bump moment-timezone from 0.5.34 to 0.5.37>

Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.34 to 0.5.37. Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ &gt; *`0.5.37` _2022.08-25_* &gt; &gt; • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> &gt; &gt; *`0.5.36` _2022.08-25_* &gt; &gt; • IANA TZDB 2022c &gt; • improvements/fixes to data pipeline &gt; &gt; *`0.5.35` _2022-08-23_* &gt; &gt; • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> &gt; • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> &gt; &gt; Thanks to the OpenSSF Alpha-Omega project for reporting these! Commits • <https://github.com/moment/moment-timezone/commit/ffe6f340a6bdae6be1cbc1cbef4a4f2b87e2c63c|`ffe6f34`> Add changelog for 0.5.37 • <https://github.com/moment/moment-timezone/commit/450ca6304ba62baf27817ed7840828eee4e3b0c5|`450ca63`> Bump version to 0.5.37 • <https://github.com/moment/moment-timezone/commit/95f1a9b5cd3a15b8c75bd36029152ff1b43a5136|`95f1a9b`> Build moment-timezone 0.5.36 • <https://github.com/moment/moment-timezone/commit/abba28c7b0e1faf7df8592806007fcb2753b3078|`abba28c`> Add changelog for 0.5.36 • <https://github.com/moment/moment-timezone/commit/ac6de03cf34610068185961613d719bc050c7d2b|`ac6de03`> Bump version to 0.5.36 • <https://github.com/moment/moment-timezone/commit/7a5cadf9cbece0a9c7b9da0ee244c21375eb33a6|`7a5cadf`> tests: Fix country tests for 2022c • <https://github.com/moment/moment-timezone/commit/6754c75f5be4fbb16e90e336c9decbad6b506388|`6754c75`> data: generate 2022c data+tests • <https://github.com/moment/moment-timezone/commit/f74a364b1aac2c96cedd0a8cf5c7188268b9bcde|`f74a364`> bugfix: Wipe tests/zones before generation • <https://github.com/moment/moment-timezone/commit/e850f9fa6d3b440c51ae0cda7d9d573627839167|`e850f9f`> grunt: do not bundle zone and contry tests • <https://github.com/moment/moment-timezone/commit/f13e22b069f9115eddad5294a4c0f5335c61590a|`f13e22b`> data: automatically create data/*/VERSION.json for latest • Additional commits viewable in <https://github.com/moment/moment-timezone/compare/0.5.34...0.5.37|compare view> <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-site/network/alerts|Security Alerts page>.

github2 14:20:32

<https://github.com/cofacts/rumors-site/pull/503#issuecomment-1232511069|Comment on #503 Bump moment-timezone from 0.5.34 to 0.5.37>

<https://coveralls.io/builds/52086675|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/a7979545bd4390da5f72758c3832f864399996b3|a797954> on dependabot/npm_and_yarn/moment-timezone-0.5.37* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.

github2 14:20:32

<https://github.com/cofacts/rumors-site/pull/503#issuecomment-1232511069|Comment on #503 Bump moment-timezone from 0.5.34 to 0.5.37>

<https://coveralls.io/builds/52086675|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/a7979545bd4390da5f72758c3832f864399996b3|a797954> on dependabot/npm_and_yarn/moment-timezone-0.5.37* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.

mrorz 16:45:13
今天沒有開會唷
下周 agenda:
https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg

g0v.hackmd.io

20220907 會議記錄 - HackMD

mrorz 16:45:13
今天沒有開會唷
下周 agenda:
https://g0v.hackmd.io/FYQIQOIgQ1evVfzG-33fwg
github2 17:31:49

<https://github.com/cofacts/design/issues/1#issuecomment-1232700545|Comment on #1 [Image-M1] Design: display image in Cofacts website / LIFF>

Article detail with transcript support here: <https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923|https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923>

github2 17:31:49

<https://github.com/cofacts/design/issues/1#issuecomment-1232700545|Comment on #1 [Image-M1] Design: display image in Cofacts website / LIFF>

Article detail with transcript support here: <https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923|https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923>