cofacts

Month: 2022-07

2022-07-01

mrorz 00:25:48
LINE bot deployed successfully
mrorz 00:25:48
LINE bot deployed successfully
mrorz 00:42:41
API & community builder deployed
現在 community builder 的 comment 列表可以看到其所 comment 的訊息以及連結
https://cofacts.github.io/community-builder/#/editorworks?type=2&day=7
mrorz 00:42:41
API & community builder deployed
現在 community builder 的 comment 列表可以看到其所 comment 的訊息以及連結
https://cofacts.github.io/community-builder/#/editorworks?type=2&day=7

cofacts.github.io

Community Builder

Web site created using create-react-app

mrorz 01:00:28
1:00 到囉
把網站拉下來 ing
mrorz 01:00:28
1:00 到囉
把網站拉下來 ing
mrorz 01:05:30
系統重新上線囉
mrorz 01:05:30
系統重新上線囉
github2 01:22:11

<https://github.com/cofacts/rumors-api/pull/285#issuecomment-1171485812|Comment on #285 Record feedback target author and allow filtering by feedback authors>

Migration report on production • Migration: 2022/7/1 1:11:53 ~ • Feedbacks matching criteria: 320,260 • Feedbacks cannot be migrated:

github2 01:22:11

<https://github.com/cofacts/rumors-api/pull/285#issuecomment-1171485812|Comment on #285 Record feedback target author and allow filtering by feedback authors>

Migration report on production • Migration: 2022/7/1 1:11:53 ~ 1:26:13 • Feedbacks matching criteria: 320,260 • Feedbacks cannot be migrated: 2,848

Ryno Hsiao 14:54:01
@orz12399 has joined the channel

2022-07-03

github2 19:08:00

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

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50550970|Build 2604839024>* • *1* of *5* *(20.0%)* changed or added relevant lines in *3* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage decreased (*-0.2%*) to *85.487%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

github2 19:08:00

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

*Pull Request Test Coverage Report for <https://coveralls.io/builds/50550973|Build 2604842471>* • *1* of *5* *(20.0%)* changed or added relevant lines in *3* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage decreased (*-0.2%*) to *85.487%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

Lawrence 23:07:16
@a0952230635 has joined the channel

2022-07-04

cai 13:28:58
https://cofacts.tw/article/14vipb8g0tnal
民俗的詢問次數上升很快XDD
> 不管您信與不信,農曆六月初六,吃完午飯出來遛遛,在太陽下晾晾也是好事。
結果台北下大雨
推出來淋雨剛好著涼
我家群組也收到了 XDDDD

我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
cai 13:28:58
https://cofacts.tw/article/14vipb8g0tnal
民俗的詢問次數上升很快XDD
> 不管您信與不信,農曆六月初六,吃完午飯出來遛遛,在太陽下晾晾也是好事。
結果台北下大雨
推出來淋雨剛好著涼
我家群組也收到了 XDDDD

我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
cai 13:35:45
檢舉違規內容(回覆) 錯字?
image.png
感謝刊物
勘誤
cai 22:24:19
gravatar 應該不會重複吧?
有一位要觀察是不是分身帳號,只出現在同類型的文章
gravatar 重複有點神奇
cai 22:24:19
YRE == NF ❔🤔
gravatar 重複有點神奇

2022-07-05

github2 02:34:51

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

Website w/ enlarged font <https://www.figma.com/file/6yJZnwNYJciyH7mrhPvyZs/Cofacts-website-(Interview)?node-id=5081%3A1216|https://www.figma.com/file/6yJZnwNYJciyH7mrhPvyZs/Cofacts-website-(Interview)?node-id=5081%3A1216>

github2 02:34:51

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

Website w/ enlarged font <https://www.figma.com/file/6yJZnwNYJciyH7mrhPvyZs/Cofacts-website-(Interview)?node-id=5081%3A1216|https://www.figma.com/file/6yJZnwNYJciyH7mrhPvyZs/Cofacts-website-(Interview)?node-id=5081%3A1216>

cai 23:24:10
繼石斑魚、雞蛋、豬肉、牛奶後,這次輪到了鳳梨
https://cofacts.g0v.tw/article/3bwsx449afn92
搜不到圖呢
感覺像是粉專貼文
傳到cofacts的訊息 大概要一兩天FB才會有圖
我在 LINE collected image 也沒看到
也可能不試圖而是影片之類
cai 23:24:10
繼石斑魚、雞蛋、豬肉、牛奶後,這次輪到了鳳梨
https://cofacts.g0v.tw/article/3bwsx449afn92
搜不到圖呢
感覺像是粉專貼文
傳到cofacts的訊息 大概要一兩天FB才會有圖
我在 LINE collected image 也沒看到
也可能不試圖而是影片之類

2022-07-06

cai 13:25:24
謠言隨著查核報告更新 😅
06/30 還在大蛇
07/03 事實查核中心報告
07/06 變成巨蟒+隨意放生遭人棄養
蛇蛇謠言的變化.png
mrorz 14:16:56

*:loudspeaker: What role does civic tech play in confronting disinformation?* Digital disinformation continues to erode our democracies. Civic tech groups around the world have launched a flurry of efforts to mitigate this pervasive threat. *<https://codeforall.org/|Code for All>* and the *<http://ndi.org|National Democratic Institute>* have enlisted *<https://codeforall.org/2022/06/22/fighting-disinformation-with-matt-stempeck/|Matt Stempeck>* to learn and share how civic tech organizations can confront disinformation. *Head over to our blog and get to know more about his work! :bulb: If you would like to stay involved in this practitioner community as we get going, please reach out to *Matt* at *<mailto:info@civictech.guide|info@civictech.guide>* <https://g0v-tw.slack.com/archives/C02G2SXKX/p1657036416676189|View original message>

mrorz 14:16:56

*:loudspeaker: What role does civic tech play in confronting disinformation?* Digital disinformation continues to erode our democracies. Civic tech groups around the world have launched a flurry of efforts to mitigate this pervasive threat. *<https://codeforall.org/|Code for All>* and the *<http://ndi.org|National Democratic Institute>* have enlisted *<https://codeforall.org/2022/06/22/fighting-disinformation-with-matt-stempeck/|Matt Stempeck>* to learn and share how civic tech organizations can confront disinformation. *Head over to our blog and get to know more about his work! :bulb: If you would like to stay involved in this practitioner community as we get going, please reach out to *Matt* at *<mailto:info@civictech.guide|info@civictech.guide>* <https://g0v-tw.slack.com/archives/C02G2SXKX/p1657036416676189|View original message>

2022-07-07

github2 07:18:18

<https://github.com/cofacts/rumors-fb-bot/pull/37|#37 Bump moment from 2.22.2 to 2.29.4>

Bumps <https://github.com/moment/moment|moment> from 2.22.2 to 2.29.4. Changelog _Sourced from <https://github.com/moment/moment/blob/develop/CHANGELOG.md|moment's changelog>._ &gt; *2.29.4* &gt; &gt; • Release Jul 6, 2022 &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex &gt; &gt; *2.29.3 <https://gist.github.com/ichernev/edebd440f49adcaec72e5e77b791d8be|Full changelog>* &gt; &gt; • Release Apr 17, 2022 &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/5995|#5995> [bugfix] Remove const usage &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/5990|#5990> misc: fix advisory link &gt; &gt; *2.29.2 <https://gist.github.com/ichernev/1904b564f6679d9aac1ae08ce13bc45c|See full changelog>* &gt; &gt; • Release Apr 3 2022 &gt; &gt; Address <https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4|GHSA-8hfj-j24r-96c4> &gt; &gt; *2.29.1 <https://gist.github.com/marwahaha/cc478ba01a1292ab4bd4e861d164d99b|See full changelog>* &gt; &gt; • Release Oct 6, 2020 &gt; &gt; Updated deprecation message, bugfix in hi locale &gt; &gt; *2.29.0 <https://gist.github.com/marwahaha/b0111718641a6461800066549957ec14|See full changelog>* &gt; &gt; • Release Sept 22, 2020 &gt; &gt; New locales (es-mx, bn-bd). Minor bugfixes and locale improvements. More tests. Moment is in maintenance mode. Read more at this link: <https://momentjs.com/docs/#/-project-status/|https://momentjs.com/docs/#/-project-status/> &gt; &gt; *2.28.0 <https://gist.github.com/marwahaha/028fd6c2b2470b2804857cfd63c0e94f|See full changelog>* &gt; &gt; • Release Sept 13, 2020 &gt; &gt; Fix bug where .format() modifies original instance, and locale updates &gt; &gt; *2.27.0 <https://gist.github.com/marwahaha/5100c9c2f42019067b1f6cefc333daa7|See full changelog>* &gt; &gt; • Release June 18, 2020 &gt; &gt; Added Turkmen locale, other locale improvements, slight TypeScript fixes &gt; &gt; *2.26.0 <https://gist.github.com/marwahaha/0725c40740560854a849b096ea7b7590|See full changelog>* &gt; &gt; • Release May 19, 2020 ... (truncated) Commits • <https://github.com/moment/moment/commit/000ac1800e620f770f4eb31b5ae908f6167b0ab2|`000ac18`> Build 2.24.4 • <https://github.com/moment/moment/commit/f2006b647939466f4f403721b8c7816d844c038c|`f2006b6`> Bump version to 2.24.4 • <https://github.com/moment/moment/commit/536ad0c348f2f99009755698f491080757a48221|`536ad0c`> Update changelog for 2.29.4 • <https://github.com/moment/moment/commit/9a3b5894f3d5d602948ac8a02e4ee528a49ca3a3|`9a3b589`> [bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>) • <https://github.com/moment/moment/commit/6374fd860aeff75e6c9d9d11540c6b22bc7ef175|`6374fd8`> Merge branch 'master' into develop • <https://github.com/moment/moment/commit/b4e615307ee350b58ac9899e3587ce43972b0753|`b4e6153`> Revert "[bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>)" • <https://github.com/moment/moment/commit/7aebb1617fc9bced87ab6bc4c317644019b23ce7|`7aebb16`> [bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>) • <https://github.com/moment/moment/commit/57c90622e402c929504cc6d6f3de4ebe2a9ffc73|`57c9062`> Build 2.29.3 • <https://github.com/moment/moment/commit/aaf50b6bca4075f40a3372c291ae8072fb4e9dcf|`aaf50b6`> Fixup release complaints • <https://github.com/moment/moment/commit/26f4aef9ca0b4c998107bf7e2cf1c33c30368d44|`26f4aef`> Bump version to 2.29.3 • Additional commits viewable in <https://github.com/moment/moment/compare/2.22.2...2.29.4|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 07:18:18

<https://github.com/cofacts/rumors-fb-bot/pull/37|#37 Bump moment from 2.22.2 to 2.29.4>

Bumps <https://github.com/moment/moment|moment> from 2.22.2 to 2.29.4. Changelog _Sourced from <https://github.com/moment/moment/blob/develop/CHANGELOG.md|moment's changelog>._ &gt; *2.29.4* &gt; &gt; • Release Jul 6, 2022 &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex &gt; &gt; *2.29.3 <https://gist.github.com/ichernev/edebd440f49adcaec72e5e77b791d8be|Full changelog>* &gt; &gt; • Release Apr 17, 2022 &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/5995|#5995> [bugfix] Remove const usage &gt; • <https://github-redirect.dependabot.com/moment/moment/pull/5990|#5990> misc: fix advisory link &gt; &gt; *2.29.2 <https://gist.github.com/ichernev/1904b564f6679d9aac1ae08ce13bc45c|See full changelog>* &gt; &gt; • Release Apr 3 2022 &gt; &gt; Address <https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4|GHSA-8hfj-j24r-96c4> &gt; &gt; *2.29.1 <https://gist.github.com/marwahaha/cc478ba01a1292ab4bd4e861d164d99b|See full changelog>* &gt; &gt; • Release Oct 6, 2020 &gt; &gt; Updated deprecation message, bugfix in hi locale &gt; &gt; *2.29.0 <https://gist.github.com/marwahaha/b0111718641a6461800066549957ec14|See full changelog>* &gt; &gt; • Release Sept 22, 2020 &gt; &gt; New locales (es-mx, bn-bd). Minor bugfixes and locale improvements. More tests. Moment is in maintenance mode. Read more at this link: <https://momentjs.com/docs/#/-project-status/|https://momentjs.com/docs/#/-project-status/> &gt; &gt; *2.28.0 <https://gist.github.com/marwahaha/028fd6c2b2470b2804857cfd63c0e94f|See full changelog>* &gt; &gt; • Release Sept 13, 2020 &gt; &gt; Fix bug where .format() modifies original instance, and locale updates &gt; &gt; *2.27.0 <https://gist.github.com/marwahaha/5100c9c2f42019067b1f6cefc333daa7|See full changelog>* &gt; &gt; • Release June 18, 2020 &gt; &gt; Added Turkmen locale, other locale improvements, slight TypeScript fixes &gt; &gt; *2.26.0 <https://gist.github.com/marwahaha/0725c40740560854a849b096ea7b7590|See full changelog>* &gt; &gt; • Release May 19, 2020 ... (truncated) Commits • <https://github.com/moment/moment/commit/000ac1800e620f770f4eb31b5ae908f6167b0ab2|`000ac18`> Build 2.24.4 • <https://github.com/moment/moment/commit/f2006b647939466f4f403721b8c7816d844c038c|`f2006b6`> Bump version to 2.24.4 • <https://github.com/moment/moment/commit/536ad0c348f2f99009755698f491080757a48221|`536ad0c`> Update changelog for 2.29.4 • <https://github.com/moment/moment/commit/9a3b5894f3d5d602948ac8a02e4ee528a49ca3a3|`9a3b589`> [bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>) • <https://github.com/moment/moment/commit/6374fd860aeff75e6c9d9d11540c6b22bc7ef175|`6374fd8`> Merge branch 'master' into develop • <https://github.com/moment/moment/commit/b4e615307ee350b58ac9899e3587ce43972b0753|`b4e6153`> Revert "[bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>)" • <https://github.com/moment/moment/commit/7aebb1617fc9bced87ab6bc4c317644019b23ce7|`7aebb16`> [bugfix] Fix redos in preprocessRFC2822 regex (<https://github-redirect.dependabot.com/moment/moment/issues/6015|#6015>) • <https://github.com/moment/moment/commit/57c90622e402c929504cc6d6f3de4ebe2a9ffc73|`57c9062`> Build 2.29.3 • <https://github.com/moment/moment/commit/aaf50b6bca4075f40a3372c291ae8072fb4e9dcf|`aaf50b6`> Fixup release complaints • <https://github.com/moment/moment/commit/26f4aef9ca0b4c998107bf7e2cf1c33c30368d44|`26f4aef`> Bump version to 2.29.3 • Additional commits viewable in <https://github.com/moment/moment/compare/2.22.2...2.29.4|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>.

2022-07-08

github2 12:40:35

<https://github.com/cofacts/media-manager/pull/6|#6 Try separating integration bucket for different matrix param>

<https://github.com/cofacts/media-manager/commit/bbb3ab33771ab20761753bfa296d7a12d967f07e|Previously> we removed testing node v18 because our integration test would clear GCS bucket content under the specified prefix when setting up. This PR separates the bucket prefix used for each Github workflow run, attempt #, node version and target OS, so that each run will have their own prefix on GCS and thus does not interfere with each other. PR run #69 attempt 1: <https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/1|https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/1> Corresponding bucket content: <https://user-images.githubusercontent.com/108608/177917517-c9fae9b4-7311-40ba-8357-3a4c3428087f.png|image> PR run #69 rerun (attempt 2): <https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/2|https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/2> Corresponding bucket content: <https://user-images.githubusercontent.com/108608/177917789-b647c37d-1d7e-4d83-800d-6bdd4708c2d0.png|image>

github2 12:40:35

<https://github.com/cofacts/media-manager/pull/6|#6 Try separating integration bucket for different matrix param>

<https://github.com/cofacts/media-manager/commit/bbb3ab33771ab20761753bfa296d7a12d967f07e|Previously> we removed testing node v18 because our integration test would clear GCS bucket content under the specified prefix when setting up. This PR separates the bucket prefix used for each Github workflow run, attempt #, node version and target OS, so that each run will have their own prefix on GCS and thus does not interfere with each other. *Test result* PR run #69 attempt 1: <https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/1|https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/1> Corresponding bucket content: <https://user-images.githubusercontent.com/108608/177917517-c9fae9b4-7311-40ba-8357-3a4c3428087f.png|image> PR run #69 rerun (attempt 2): <https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/2|https://github.com/cofacts/media-manager/actions/runs/2633901046/attempts/2> Corresponding bucket content: <https://user-images.githubusercontent.com/108608/177917789-b647c37d-1d7e-4d83-800d-6bdd4708c2d0.png|image> *Others* On the GCS we can setup object lifecycle so that artifacts of old workflow runs are deleted automatically. <https://user-images.githubusercontent.com/108608/177918354-b0f21421-9137-44fa-8021-79925ee4aef0.png|image>

:white_check_mark: All checks have passed

github2 19:10:14

<https://github.com/cofacts/rumors-site/pull/493|#493 Support attachment variants>

Extends <https://github.com/cofacts/rumors-site/pull/490|#490> on task <https://github.com/cofacts/rumors-site/issues/483|#483> . Must merge after API PR <https://github.com/cofacts/rumors-api/pull/288|cofacts/rumors-api#288> is deployed. This PR: • Uses "thumbnail" variant for list • Uses "preview" variant for detail page • Constraints image height so that image articles does not take too much vertical space in lists • In article detail, add link to original file for logged in users Deployed to staging. *Screenshots* *Article list, desktop* <https://user-images.githubusercontent.com/108608/177980978-f3cb15c5-8c6e-4528-844c-18eb23d0b26d.png|image> *Article list, mobile* <https://user-images.githubusercontent.com/108608/177981067-33c3a3c1-d2a2-40c3-af99-2f53c9b96a02.png|image> *Reply list, desktop* <https://user-images.githubusercontent.com/108608/177981168-12361d87-6dd3-4e6d-89ff-db7ab37b6e06.png|image> *Reply list, mobile* <https://user-images.githubusercontent.com/108608/177981140-12a78fd0-22d9-49c0-86a1-cac41685f9c1.png|image> *Article detail, desktop* Note that only when user logs in, clicking the image in article detail would bring user to the original file <https://user-images.githubusercontent.com/108608/177980481-d692c7a5-d70b-489f-b3bf-7bd3886c56aa.png|image> *Storybook* *Article detail, mobile* <https://user-images.githubusercontent.com/108608/177980885-aee96402-7d1c-45ab-91d9-62e3dd1125e2.png|image>

github2 19:10:14

<https://github.com/cofacts/rumors-site/pull/493|#493 Support attachment variants>

Extends <https://github.com/cofacts/rumors-site/pull/490|#490> on task <https://github.com/cofacts/rumors-site/issues/483|#483> . Must merge after API PR <https://github.com/cofacts/rumors-api/pull/288|cofacts/rumors-api#288> is deployed. This PR: • Uses "thumbnail" variant for list • Uses "preview" variant for detail page • Constraints image height so that image articles does not take too much vertical space in lists • In article detail, add link to original file for logged in users Deployed to staging. *Screenshots* *Article list, desktop* <https://user-images.githubusercontent.com/108608/177980978-f3cb15c5-8c6e-4528-844c-18eb23d0b26d.png|image> *Article list, mobile* <https://user-images.githubusercontent.com/108608/177981067-33c3a3c1-d2a2-40c3-af99-2f53c9b96a02.png|image> *Reply list, desktop* <https://user-images.githubusercontent.com/108608/177981168-12361d87-6dd3-4e6d-89ff-db7ab37b6e06.png|image> *Reply list, mobile* <https://user-images.githubusercontent.com/108608/177981140-12a78fd0-22d9-49c0-86a1-cac41685f9c1.png|image> *Profile page, desktop* <https://user-images.githubusercontent.com/108608/177982049-390b7ded-0676-4cfb-9f24-a6203ae4b141.png|image> *Profile page, mobile* <https://user-images.githubusercontent.com/108608/177982098-3052b3c2-0382-48cc-bd36-97921e65ffec.png|image> *Article detail, desktop* Note that only when user logs in, clicking the image in article detail would bring user to the original file <https://user-images.githubusercontent.com/108608/177980481-d692c7a5-d70b-489f-b3bf-7bd3886c56aa.png|image> *Article detail, mobile* <https://user-images.githubusercontent.com/108608/177980885-aee96402-7d1c-45ab-91d9-62e3dd1125e2.png|image> *Create reply message tab, mobile* <https://user-images.githubusercontent.com/108608/177982871-391a80bf-275c-4d53-9244-5afe84f22fe3.png|image> *Related reply, desktop* <https://user-images.githubusercontent.com/108608/177983052-72022652-7ca5-4a9f-8fde-f732b46eb5dd.png|image> *Related reply, mobile* <https://user-images.githubusercontent.com/108608/177982979-dcbf3c17-a150-42da-b849-4033681472cd.png|image> *Storybook* <https://user-images.githubusercontent.com/108608/177981957-725db20f-e6cd-4917-8980-fc236edc9e1f.png|image>

:white_check_mark: 4 other checks have passed

github2 19:12:46

<https://github.com/cofacts/rumors-site/pull/493#issuecomment-1178865265|Comment on #493 Support attachment variants>

<https://coveralls.io/builds/50707454|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/dd36e9a265413e38af647c51f85f941938a36f9e|dd36e9a> on attachment-variants* into *<https://github.com/cofacts/rumors-site/commit/2ac82d9fa7f58327b198c5062dd0be0555d3cacb|2ac82d9> on master*.

github2 19:12:46

<https://github.com/cofacts/rumors-site/pull/493#issuecomment-1178865265|Comment on #493 Support attachment variants>

<https://coveralls.io/builds/50707235|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/4b6773f3883765ca7835bfde1e011e8c3d695991|4b6773f> on attachment-variants* into *<https://github.com/cofacts/rumors-site/commit/2ac82d9fa7f58327b198c5062dd0be0555d3cacb|2ac82d9> on master*.

mrorz 19:49:07
@acerxp511 staging 上放好新的測試用的圖與 API 囉!
line bot 應該都只會用得到 thumbnail variant。(LINE 也不支援 preview 的 webp 就是了)
1
mrorz 19:49:07
@acerxp511 staging 上放好新的測試用的圖與 API 囉!
line bot 應該都只會用得到 thumbnail variant。(LINE 也不支援 preview 的 webp 就是了)
mrorz 19:51:51
這個是我上傳時 URL 貼錯導致的壞檔
https://dev.cofacts.tw/article/SNas3IEBnoMYOwsgFdBf

傳壞之後,現在的 staging API 會先檢查檔案本身的 content type 是否跟 `CreateMediaArticle` 的 `articleType` 對應,沒對應的話(例如 URL 是 404,他的 content-type 就不會是 `image` 開頭)就會 error,也不會像這樣產出壞的 article
mrorz 19:51:51
這個是我上傳時 URL 貼錯導致的壞檔
https://dev.cofacts.tw/article/SNas3IEBnoMYOwsgFdBf

後來我改了 API,現在 `CreateMediaArticle` 會先檢查檔案本身的 content type 是否跟 `CreateMediaArticle` 的 `articleType` 對應,沒對應的話(例如 URL 是 404,他的 content-type 就不會是 `image` 開頭,也就不會與 `articleType: IMAGE` 符合)就會 error,也不會像這樣產出壞的 article
1

2022-07-09

mrorz 00:23:26
這裡 au 有 cue 到 Cofacts 作為數位素養入門的練習平台這件事情~
https://youtu.be/mvt8jDs-SVs?t=2944
mrorz 00:23:26
這裡 au 有 cue 到 Cofacts 作為數位素養入門的練習平台這件事情~
https://youtu.be/mvt8jDs-SVs?t=2944

YouTube

2022-07-05 中研院院士會議對談

👍 5 1

2022-07-11

github2 16:42:26

<https://github.com/cofacts/rumors-site/pull/494|#494 Improve filter, sort and count in profile page.>

Fixes <https://github.com/cofacts/rumors-site/issues/492|#492> • Add message count of filtered messages • Time filter and type filter should act on the users' article-reply, rather than any article replies in article. • Add a sort option that sorts by matching (user's) article reply. *Screenshots* Left: this PR; Right: staging, before this PR. *Search count &amp; filter* • The updated time filter will properly apply the logic on the user's article reply, rather than applying on any reply of the article. • Count of searched result is displayed below the filter. <https://user-images.githubusercontent.com/108608/178222915-f3869595-8d83-4b73-8182-663108b1da08.png|image> *Article reply type update* The updated type filter will properly apply the logic on the user's article reply, rather than applying on any reply of the article. <https://user-images.githubusercontent.com/108608/178223554-146f6f5b-a928-4322-b56b-6433b734e911.png|image> *New sort options* • Most recently applied: default. Sort by the profile page users article replies that matches the search criteria. • Most recently applied by any user: The original sorting method before this PR. Sort by any article reply in the matching article. <https://user-images.githubusercontent.com/108608/178223803-94de74ce-3651-4004-b3c0-dd620186f618.png|image>

github2 16:42:26

<https://github.com/cofacts/rumors-site/pull/494|#494 Improve filter, sort and count in profile page.>

Fixes <https://github.com/cofacts/rumors-site/issues/492|#492> • Add message count of filtered messages • Time filter and type filter should act on the users' article-reply, rather than any article replies in article. • Add a sort option that sorts by matching (user's) article reply. *Screenshots* Left: this PR; Right: staging, before this PR. *Search count &amp; filter* • The updated time filter will properly apply the logic on the user's article reply, rather than applying on any reply of the article. • Count of searched result is displayed below the filter. <https://user-images.githubusercontent.com/108608/178222915-f3869595-8d83-4b73-8182-663108b1da08.png|image> *Article reply type update* The updated type filter will properly apply the logic on the user's article reply, rather than applying on any reply of the article. <https://user-images.githubusercontent.com/108608/178223554-146f6f5b-a928-4322-b56b-6433b734e911.png|image> *New sort options* • Most recently applied: default. Sort by the profile page users article replies that matches the search criteria. • Most recently applied by any user: The original sorting method before this PR. Sort by any article reply in the matching article. <https://user-images.githubusercontent.com/108608/178224464-e7f51d2f-9cb4-4691-bd37-636fb504b61a.png|image>

:white_check_mark: All checks have passed

github2 16:44:00

<https://github.com/cofacts/rumors-site/pull/494#issuecomment-1180127332|Comment on #494 Improve filter, sort and count in profile page.>

<https://coveralls.io/builds/50743929|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/4ce1738566df82a686c5b601d13e0bde0bc56b76|4ce1738> on profile-filter-count* into *<https://github.com/cofacts/rumors-site/commit/6fe65df33537f0d8252c3e1c5036183906c61dfa|6fe65df> on master*.

github2 16:44:00

<https://github.com/cofacts/rumors-site/pull/494#issuecomment-1180127332|Comment on #494 Improve filter, sort and count in profile page.>

<https://coveralls.io/builds/50744090|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/eb4d12da1e16052c15deb1c8e897fb65f030ee45|eb4d12d> on profile-filter-count* into *<https://github.com/cofacts/rumors-site/commit/6fe65df33537f0d8252c3e1c5036183906c61dfa|6fe65df> on master*.

cai 17:24:49
今天有推廣活動?
昨天有百工日記,大學生唷
cai 17:24:49
今天有推廣活動?
昨天有百工日記,大學生唷
github2 17:58:13

<https://github.com/cofacts/rumors-site/pull/495|#495 Fix current user missing in Google Analytics>

The issue is found in <https://g0v.hackmd.io/UopCx5bcRb-gt_3SdVqRdQ#%E5%B0%8F%E8%81%9A%E7%B1%8C%E5%82%99|20220706 meeting> Currently on production, if the user is already logged in, starts their session on the landing page, and then goes to other pages, their user ID will not be sent in Google Analytics actions. This is because • We push current user to Google Tag Manager in `useCurrentUser`'s `onCompleted` callback <https://user-images.githubusercontent.com/108608/178239220-cac32f61-efd3-4458-8ee5-cd015a438257.png|image> • Before this PR, landing page uses its own way to load user, and thus does not use `useCurrentUser` • Landing page loads all fields that is required by `useCurrentUser`, so that when user enters other page from landing page, `useCurrentUser` hook will not invoke new GraphQL queries, thus not calling `onCompleted` callback at all. This PR fixes the issue by using `useCurrentUser` in landing page as well. *Screenshot* *Before* `CURRENT_USER` is not pushed to `dataLayer` even after the user logs in on landing page <https://user-images.githubusercontent.com/108608/178239130-072393a5-f81b-481e-93a0-d98858a97d2b.png|image> *After* Can see that `CURRENT_USER` is pushed to `dataLayer` as expected. <https://user-images.githubusercontent.com/108608/178238832-0a5e6bad-cd64-4e0e-9857-0836ea73032b.png|image>

github2 17:58:13

<https://github.com/cofacts/rumors-site/pull/495|#495 Fix current user missing in Google Analytics>

The issue is found in <https://g0v.hackmd.io/UopCx5bcRb-gt_3SdVqRdQ#%E5%B0%8F%E8%81%9A%E7%B1%8C%E5%82%99|20220706 meeting> Currently on production, if the user is already logged in, starts their session on the landing page, and then goes to other pages, their user ID will not be sent in Google Analytics actions. This is because • We push current user to Google Tag Manager in `useCurrentUser`'s `onCompleted` callback <https://user-images.githubusercontent.com/108608/178239220-cac32f61-efd3-4458-8ee5-cd015a438257.png|image> • Before this PR, landing page uses its own way to load user, and thus does not use `useCurrentUser` • Landing page loads all fields that is required by `useCurrentUser`, so that when user enters other page from landing page, `useCurrentUser` hook will not invoke new GraphQL queries, thus not calling `onCompleted` callback at all. This PR fixes the issue by using `useCurrentUser` in landing page as well. *Screenshot* *Before* `CURRENT_USER` is not pushed to `dataLayer` even after the user logs in on landing page <https://user-images.githubusercontent.com/108608/178239130-072393a5-f81b-481e-93a0-d98858a97d2b.png|image> *After* Can see that `CURRENT_USER` is pushed to `dataLayer` as expected. <https://user-images.githubusercontent.com/108608/178238832-0a5e6bad-cd64-4e0e-9857-0836ea73032b.png|image>

:white_check_mark: All checks have passed

github2 17:59:56

<https://github.com/cofacts/rumors-site/pull/495#issuecomment-1180200006|Comment on #495 Fix current user missing in Google Analytics>

<https://coveralls.io/builds/50746164|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/9cda37378685ee496654d2030d4de4898c330e0f|9cda373> on fix-current-user* into *<https://github.com/cofacts/rumors-site/commit/eb4d12da1e16052c15deb1c8e897fb65f030ee45|eb4d12d> on profile-filter-count*.

github2 17:59:56

<https://github.com/cofacts/rumors-site/pull/495#issuecomment-1180200006|Comment on #495 Fix current user missing in Google Analytics>

<https://coveralls.io/builds/50746164|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/9cda37378685ee496654d2030d4de4898c330e0f|9cda373> on fix-current-user* into *<https://github.com/cofacts/rumors-site/commit/eb4d12da1e16052c15deb1c8e897fb65f030ee45|eb4d12d> on profile-filter-count*.

2022-07-12

2022-07-13

mrorz 12:54:40
今天會議會在久違了的 Workis 舉辦唷
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
mrorz 12:54:40
今天會議會在久違了的 Workis 舉辦唷
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
mrorz 13:49:20
Hopoo 太誇張⋯⋯
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
我懷疑有在洗
清完囉

由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
而且他們還會把詐騙的分類按否決欸
感謝分享,看來我要修改 block user script 把 article category feedback 也加入
要不要預設回覆 `改成含有錯誤訊息` 😆
Oh 這也是一招 XDDDDDD
之前會不在查證範圍是因為
以前確實滿多不在查證範圍的東西
不過隨著 chatbot 端送出流程設計變嚴格,亂傳的人變少了
他們真的好認真洗
他們真多開帳號的時間
今天的洗好像有點語無倫次
都在複製貼上洗些奇妙的股票相關東西
用程式跑的吧
https://cofacts.tw/article/2q5nf5c5s650k
看來在收尾了,這次換冒用台中警方跟金管會名義
簡體字跟中國用語露餡了
Wow 所以他們直接在群組做二次詐騙喔
令人瞠目結舌
無縫接軌到二次詐騙耶
https://cofacts.tw/article/1zyxjfvzx9ute
這兩天變成愛情交友在洗
呂尚傑照片的兒子表示很困惑 ,看留言還有別的名字 張育恆https://www.facebook.com/yijing1/posts/pfbid02Pf1ZL5upbzzdh662UgboLrxQ2btDR9RxYz4CtCXBefgx2xEbPPvozKMUr9tM4vGpl
mrorz 13:49:20
Hopoo 太誇張⋯⋯
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
我懷疑有在洗
清完囉

由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
而且他們還會把詐騙的分類按否決欸
mrorz