#cofacts
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
現在 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
現在 community builder 的 comment 列表可以看到其所 comment 的訊息以及連結
https://cofacts.github.io/community-builder/#/editorworks?type=2&day=7
mrorz
01:00:28
1:00 到囉
把網站拉下來 ing
把網站拉下來 ing
mrorz
01:00:28
1:00 到囉
把網站拉下來 ing
把網站拉下來 ing
mrorz
01:05:30
系統重新上線囉
mrorz
01:05:30
系統重新上線囉
github2
01:22:11
Migration report on production • Migration: 2022/7/1 1:11:53 ~ • Feedbacks matching criteria: 320,260 • Feedbacks cannot be migrated:
github2
01:22:11
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
*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
*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
民俗的詢問次數上升很快XDD
mrorz
2022-07-04 14:04:38
> 不管您信與不信,農曆六月初六,吃完午飯出來遛遛,在太陽下晾晾也是好事。
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
mrorz
2022-07-04 15:09:52
我家群組也收到了 XDDDD
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
cai
13:28:58
https://cofacts.tw/article/14vipb8g0tnal
民俗的詢問次數上升很快XDD
民俗的詢問次數上升很快XDD
mrorz
2022-07-04 14:04:38
> 不管您信與不信,農曆六月初六,吃完午飯出來遛遛,在太陽下晾晾也是好事。
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
mrorz
2022-07-04 15:09:52
我家群組也收到了 XDDDD
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
mrorz
14:00:19
感謝刊物
mrorz
14:00:23
勘誤
mrorz
14:04:38
> 不管您信與不信,農曆六月初六,吃完午飯出來遛遛,在太陽下晾晾也是好事。
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
結果台北下大雨
推出來淋雨剛好著涼
ㄏ
mrorz
15:09:52
我家群組也收到了 XDDDD
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
我覺得就是個讓人出來活動的契機問候訊息這樣
看不太出來有什麼立即的危害
雖然類似訊息有個回應,但好像對問候訊息有點嚴格
mrorz
23:35:38
gravatar 重複有點神奇
2022-07-05
github2
02:34:51
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
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
https://cofacts.g0v.tw/article/3bwsx449afn92
mrorz
2022-07-06 00:38:56
搜不到圖呢
感覺像是粉專貼文
感覺像是粉專貼文
傳到cofacts的訊息 大概要一兩天FB才會有圖
mrorz
2022-07-06 14:16:04
我在 LINE collected image 也沒看到
也可能不試圖而是影片之類
也可能不試圖而是影片之類
cai
23:24:10
繼石斑魚、雞蛋、豬肉、牛奶後,這次輪到了鳳梨
https://cofacts.g0v.tw/article/3bwsx449afn92
https://cofacts.g0v.tw/article/3bwsx449afn92
mrorz
2022-07-06 00:38:56
搜不到圖呢
感覺像是粉專貼文
感覺像是粉專貼文
傳到cofacts的訊息 大概要一兩天FB才會有圖
mrorz
2022-07-06 14:16:04
我在 LINE collected image 也沒看到
也可能不試圖而是影片之類
也可能不試圖而是影片之類
2022-07-06
mrorz
00:38:56
搜不到圖呢
感覺像是粉專貼文
感覺像是粉專貼文
cai
12:49:24
傳到cofacts的訊息 大概要一兩天FB才會有圖
mrorz
14:16:04
我在 LINE collected image 也沒看到
也可能不試圖而是影片之類
也可能不試圖而是影片之類
mrorz
14:29:38
2022-07-07
github2
07:18:18
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>._ > *2.29.4* > > • Release Jul 6, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex > > *2.29.3 <https://gist.github.com/ichernev/edebd440f49adcaec72e5e77b791d8be|Full changelog>* > > • Release Apr 17, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/5995|#5995> [bugfix] Remove const usage > • <https://github-redirect.dependabot.com/moment/moment/pull/5990|#5990> misc: fix advisory link > > *2.29.2 <https://gist.github.com/ichernev/1904b564f6679d9aac1ae08ce13bc45c|See full changelog>* > > • Release Apr 3 2022 > > Address <https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4|GHSA-8hfj-j24r-96c4> > > *2.29.1 <https://gist.github.com/marwahaha/cc478ba01a1292ab4bd4e861d164d99b|See full changelog>* > > • Release Oct 6, 2020 > > Updated deprecation message, bugfix in hi locale > > *2.29.0 <https://gist.github.com/marwahaha/b0111718641a6461800066549957ec14|See full changelog>* > > • Release Sept 22, 2020 > > 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/> > > *2.28.0 <https://gist.github.com/marwahaha/028fd6c2b2470b2804857cfd63c0e94f|See full changelog>* > > • Release Sept 13, 2020 > > Fix bug where .format() modifies original instance, and locale updates > > *2.27.0 <https://gist.github.com/marwahaha/5100c9c2f42019067b1f6cefc333daa7|See full changelog>* > > • Release June 18, 2020 > > Added Turkmen locale, other locale improvements, slight TypeScript fixes > > *2.26.0 <https://gist.github.com/marwahaha/0725c40740560854a849b096ea7b7590|See full changelog>* > > • 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
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>._ > *2.29.4* > > • Release Jul 6, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex > > *2.29.3 <https://gist.github.com/ichernev/edebd440f49adcaec72e5e77b791d8be|Full changelog>* > > • Release Apr 17, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/5995|#5995> [bugfix] Remove const usage > • <https://github-redirect.dependabot.com/moment/moment/pull/5990|#5990> misc: fix advisory link > > *2.29.2 <https://gist.github.com/ichernev/1904b564f6679d9aac1ae08ce13bc45c|See full changelog>* > > • Release Apr 3 2022 > > Address <https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4|GHSA-8hfj-j24r-96c4> > > *2.29.1 <https://gist.github.com/marwahaha/cc478ba01a1292ab4bd4e861d164d99b|See full changelog>* > > • Release Oct 6, 2020 > > Updated deprecation message, bugfix in hi locale > > *2.29.0 <https://gist.github.com/marwahaha/b0111718641a6461800066549957ec14|See full changelog>* > > • Release Sept 22, 2020 > > 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/> > > *2.28.0 <https://gist.github.com/marwahaha/028fd6c2b2470b2804857cfd63c0e94f|See full changelog>* > > • Release Sept 13, 2020 > > Fix bug where .format() modifies original instance, and locale updates > > *2.27.0 <https://gist.github.com/marwahaha/5100c9c2f42019067b1f6cefc333daa7|See full changelog>* > > • Release June 18, 2020 > > Added Turkmen locale, other locale improvements, slight TypeScript fixes > > *2.26.0 <https://gist.github.com/marwahaha/0725c40740560854a849b096ea7b7590|See full changelog>* > > • 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/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/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>![]()
mrorz
15:15:19
自然醫學來賣藥囉
github2
19:10:14
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
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>![]()
github2
19:12:46
<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://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 就是了)
line bot 應該都只會用得到 thumbnail variant。(LINE 也不支援 preview 的 webp 就是了)
- 1
mrorz
19:49:07
@acerxp511 staging 上放好新的測試用的圖與 API 囉!
line bot 應該都只會用得到 thumbnail variant。(LINE 也不支援 preview 的 webp 就是了)
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
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
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
https://youtu.be/mvt8jDs-SVs?t=2944
2022-07-11
github2
16:42:26
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 & 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
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 & 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>![]()
github2
16:44:00
<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://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*.
github2
17:58:13
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
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:59:56
<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://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
bil
18:03:16
昨天有百工日記,大學生唷
2022-07-13
mrorz
12:54:40
今天會議會在久違了的 Workis 舉辦唷
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
mrorz
12:54:40
今天會議會在久違了的 Workis 舉辦唷
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
議程:
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FAqvBLZNmS4uAGMmuNQSgVg
mrorz
13:49:20
Hopoo 太誇張⋯⋯
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
我懷疑有在洗
mrorz
2022-07-13 14:25:37
絕對有在洗唷,那個發布時間跟形式
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
mrorz
2022-07-13 16:47:29
清完囉
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
而且他們還會把詐騙的分類按否決欸
mrorz
2022-07-14 13:13:52
感謝分享,看來我要修改 block user script 把 article category feedback 也加入
要不要預設回覆 `改成含有錯誤訊息` 😆
mrorz
2022-07-14 13:22:25
Oh 這也是一招 XDDDDDD
mrorz
2022-07-14 13:22:36
之前會不在查證範圍是因為
以前確實滿多不在查證範圍的東西
以前確實滿多不在查證範圍的東西
mrorz
2022-07-14 13:23:02
不過隨著 chatbot 端送出流程設計變嚴格,亂傳的人變少了
他們真的好認真洗
mrorz
2022-07-15 13:51:01
他們真多開帳號的時間
mrorz
2022-07-15 15:37:40
今天的洗好像有點語無倫次
都在複製貼上洗些奇妙的股票相關東西
都在複製貼上洗些奇妙的股票相關東西
用程式跑的吧
https://cofacts.tw/article/2q5nf5c5s650k
看來在收尾了,這次換冒用台中警方跟金管會名義
看來在收尾了,這次換冒用台中警方跟金管會名義
簡體字跟中國用語露餡了
mrorz
2022-07-27 13:48:11
Wow 所以他們直接在群組做二次詐騙喔
令人瞠目結舌
令人瞠目結舌
mrorz
2022-07-27 13:48:24
無縫接軌到二次詐騙耶
https://cofacts.tw/article/1zyxjfvzx9ute
這兩天變成愛情交友在洗
這兩天變成愛情交友在洗
呂尚傑照片的兒子表示很困惑 ,看留言還有別的名字 張育恆https://www.facebook.com/yijing1/posts/pfbid02Pf1ZL5upbzzdh662UgboLrxQ2btDR9RxYz4CtCXBefgx2xEbPPvozKMUr9tM4vGpl
mrorz
13:49:20
Hopoo 太誇張⋯⋯
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
https://cofacts.tw/reply/IVMK9oEBZ4FY5vnAH8rd
我懷疑有在洗
mrorz
2022-07-13 14:25:37
絕對有在洗唷,那個發布時間跟形式
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
mrorz
2022-07-13 16:47:29
清完囉
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
而且他們還會把詐騙的分類按否決欸
mrorz
2022-07-14 13:13:52
感謝分享,看來我要修改 block user script 把 article category feedback 也加入
要不要預設回覆 `改成含有錯誤訊息` 😆
mrorz
2022-07-14 13:22:25
Oh 這也是一招 XDDDDDD
mrorz
2022-07-14 13:22:36
之前會不在查證範圍是因為
以前確實滿多不在查證範圍的東西
以前確實滿多不在查證範圍的東西
mrorz
2022-07-14 13:23:02
不過隨著 chatbot 端送出流程設計變嚴格,亂傳的人變少了
他們真的好認真洗
mrorz
2022-07-15 13:51:01
他們真多開帳號的時間
mrorz
2022-07-15 15:37:40
今天的洗好像有點語無倫次
都在複製貼上洗些奇妙的股票相關東西
都在複製貼上洗些奇妙的股票相關東西
用程式跑的吧
https://cofacts.tw/article/2q5nf5c5s650k
看來在收尾了,這次換冒用台中警方跟金管會名義
看來在收尾了,這次換冒用台中警方跟金管會名義
簡體字跟中國用語露餡了
mrorz
2022-07-27 13:48:11
Wow 所以他們直接在群組做二次詐騙喔
令人瞠目結舌
令人瞠目結舌
mrorz
2022-07-27 13:48:24
無縫接軌到二次詐騙耶
https://cofacts.tw/article/1zyxjfvzx9ute
這兩天變成愛情交友在洗
這兩天變成愛情交友在洗
呂尚傑照片的兒子表示很困惑 ,看留言還有別的名字 張育恆https://www.facebook.com/yijing1/posts/pfbid02Pf1ZL5upbzzdh662UgboLrxQ2btDR9RxYz4CtCXBefgx2xEbPPvozKMUr9tM4vGpl
cai
14:00:01
我懷疑有在洗
mrorz
14:25:37
Replied to a thread: 2022-07-13 13:49:20
絕對有在洗唷,那個發布時間跟形式
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
再請大家 approve
來一波送走他們
https://github.com/cofacts/takedowns/pull/79/files?short_path=efc9428#diff-efc942874be8bf4adfff5d30235e4026e884c93a22fd73108556023daae34d41
mrorz
16:47:29
Replied to a thread: 2022-07-13 13:49:20
清完囉
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
由於這些 Hopoo 的自問自答 CIB LINE 使用者,是唯一一個把該訊息送進來的人(濫用 Cofacts 拿來做 Q&A)
所以在清完之後就會出現「0 人回報」的特殊景觀 XDD
- 🌸2
chhsiao1981
21:30:04
@chhsiao1981 has joined the channel
2022-07-14
github2
01:55:11
<https://github.com/cofacts/rumors-site/pull/495|#495> was merged to incorrect branch. This PR fixes the merge target and try again.
github2
01:55:11
<https://github.com/cofacts/rumors-site/pull/495|#495> was merged to incorrect branch. This PR fixes the merge target and try again.
github2
01:57:10
<https://github.com/cofacts/rumors-site/pull/496#issuecomment-1183517522|Comment on #496 Retry #495><https://coveralls.io/builds/50841116|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/16ccf15a56fd5a4733c1f809ce28291d5baac255|16ccf15> on fix-current-user* into *<https://github.com/cofacts/rumors-site/commit/b2432e2e49588aa50d26ac32d0496502c1985ce9|b2432e2> on master*.
github2
01:57:10
<https://github.com/cofacts/rumors-site/pull/496#issuecomment-1183517522|Comment on #496 Retry #495><https://coveralls.io/builds/50841116|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/16ccf15a56fd5a4733c1f809ce28291d5baac255|16ccf15> on fix-current-user* into *<https://github.com/cofacts/rumors-site/commit/b2432e2e49588aa50d26ac32d0496502c1985ce9|b2432e2> on master*.
cai
12:44:21
Replied to a thread: 2022-07-13 13:49:20
cai
12:51:56
而且他們還會把詐騙的分類按否決欸
mrorz
13:13:52
感謝分享,看來我要修改 block user script 把 article category feedback 也加入
cai
13:21:45
要不要預設回覆 `改成含有錯誤訊息` 😆
mrorz
13:22:25
Oh 這也是一招 XDDDDDD
mrorz
13:22:36
之前會不在查證範圍是因為
以前確實滿多不在查證範圍的東西
以前確實滿多不在查證範圍的東西
mrorz
13:23:02
不過隨著 chatbot 端送出流程設計變嚴格,亂傳的人變少了
cai
13:29:16
超商麵包放半年FB找到的是 tiktok影片 https://www.tiktok.com/@dyboixb6ogy0/video/7119466254208896282
https://cofacts.tw/article/26svhokv40l2z
https://cofacts.tw/article/ca67b1i04fok
https://cofacts.tw/article/1pfkzdixgfnqq
https://cofacts.tw/article/12xi2qg96qqzf
https://cofacts.tw/article/26svhokv40l2z
https://cofacts.tw/article/ca67b1i04fok
https://cofacts.tw/article/1pfkzdixgfnqq
https://cofacts.tw/article/12xi2qg96qqzf
- 🌸1
這篇不知道能不能用 https://www.foodnext.net/life/lifesafe/paper/5593139879
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
mrorz
2022-07-14 13:31:18
喔這好多喔
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
mrorz
2022-07-14 13:31:42
如果包裝沒有拆開的狀況底下發霉了
那就代表黴菌一開始就在裡面
這才有問題吧
那就代表黴菌一開始就在裡面
這才有問題吧
mrorz
2022-07-14 13:32:06
小時候有個自然實驗
是要大家用麵包噴水之後靜置來養黴菌
是要大家用麵包噴水之後靜置來養黴菌
mrorz
2022-07-14 13:32:25
我的吐司噴水然後擺在角落很久
一直沒有發霉
我很難過 (?)
一直沒有發霉
我很難過 (?)
mrorz
2022-07-14 13:32:32
要發霉其實還滿不容易的
mrorz
2022-07-14 13:34:16
我覺得食力那篇滿精準的~~
mrorz
2022-07-14 13:34:58
提供了很不錯的解釋
不然看這個影片的人都只會想到防腐劑
不然看這個影片的人都只會想到防腐劑
mrorz
2022-07-14 13:35:14
不知道光是密封就能防止微生物進入
mrorz
2022-07-14 13:35:27
也不知道裡面殘留的微生物生長,外觀可能完全看不出來
cai
13:29:16
超商麵包放半年FB找到的是 tiktok影片 https://www.tiktok.com/@dyboixb6ogy0/video/7119466254208896282
https://cofacts.tw/article/26svhokv40l2z
https://cofacts.tw/article/ca67b1i04fok
https://cofacts.tw/article/1pfkzdixgfnqq
https://cofacts.tw/article/12xi2qg96qqzf
https://cofacts.tw/article/26svhokv40l2z
https://cofacts.tw/article/ca67b1i04fok
https://cofacts.tw/article/1pfkzdixgfnqq
https://cofacts.tw/article/12xi2qg96qqzf
這篇不知道能不能用 https://www.foodnext.net/life/lifesafe/paper/5593139879
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
mrorz
2022-07-14 13:31:18
喔這好多喔
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
mrorz
2022-07-14 13:31:42
如果包裝沒有拆開的狀況底下發霉了
那就代表黴菌一開始就在裡面
這才有問題吧
那就代表黴菌一開始就在裡面
這才有問題吧
mrorz
2022-07-14 13:32:06
小時候有個自然實驗
是要大家用麵包噴水之後靜置來養黴菌
是要大家用麵包噴水之後靜置來養黴菌
mrorz
2022-07-14 13:32:25
我的吐司噴水然後擺在角落很久
一直沒有發霉
我很難過 (?)
一直沒有發霉
我很難過 (?)
mrorz
2022-07-14 13:32:32
要發霉其實還滿不容易的
mrorz
2022-07-14 13:34:16
我覺得食力那篇滿精準的~~
mrorz
2022-07-14 13:34:58
提供了很不錯的解釋
不然看這個影片的人都只會想到防腐劑
不然看這個影片的人都只會想到防腐劑
mrorz
2022-07-14 13:35:14
不知道光是密封就能防止微生物進入
mrorz
2022-07-14 13:35:27
也不知道裡面殘留的微生物生長,外觀可能完全看不出來
cai
13:29:26
這篇不知道能不能用 https://www.foodnext.net/life/lifesafe/paper/5593139879
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
> 至於部分民眾表示超商麵包放置2星期仍不見其腐敗,其實細菌與黴菌的滋生,不一定能明顯地觀察出來,這些麵包表面看起來無恙,內部可能已經有微生物的滋生,因此若已過期太久仍不建議食用。
https://tw.news.yahoo.com/水分控制得宜超商麵包不壞-林杰樑-我們都太相信感官-034914687.html
2013年的新聞,但是原本的新聞網站找不到此篇
mrorz
13:31:18
喔這好多喔
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
感謝提供 reference
我的第一反應是
包裝沒有拆,黴菌是要從哪裡來 XDDD
mrorz
13:31:42
如果包裝沒有拆開的狀況底下發霉了
那就代表黴菌一開始就在裡面
這才有問題吧
那就代表黴菌一開始就在裡面
這才有問題吧
mrorz
13:32:06
小時候有個自然實驗
是要大家用麵包噴水之後靜置來養黴菌
是要大家用麵包噴水之後靜置來養黴菌
mrorz
13:32:25
我的吐司噴水然後擺在角落很久
一直沒有發霉
我很難過 (?)
一直沒有發霉
我很難過 (?)
mrorz
13:32:32
要發霉其實還滿不容易的
mrorz
13:34:16
我覺得食力那篇滿精準的~~
mrorz
13:34:58
提供了很不錯的解釋
不然看這個影片的人都只會想到防腐劑
不然看這個影片的人都只會想到防腐劑
mrorz
13:35:14
不知道光是密封就能防止微生物進入
mrorz
13:35:27
也不知道裡面殘留的微生物生長,外觀可能完全看不出來
2022-07-15
mrorz
11:23:26
mrorz
13:51:01
他們真多開帳號的時間
mrorz
15:37:40
今天的洗好像有點語無倫次
都在複製貼上洗些奇妙的股票相關東西
都在複製貼上洗些奇妙的股票相關東西
cai
18:00:24
用程式跑的吧
2022-07-16
github2
00:55:43
Bumps <https://github.com/sveltejs/svelte|svelte> from 3.47.0 to 3.49.0. Changelog _Sourced from <https://github.com/sveltejs/svelte/blob/master/CHANGELOG.md|svelte's changelog>._ > *3.49.0* > > • Improve performance of string escaping during SSR (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/5701|#5701>) > • Add `ComponentType` and `ComponentProps` convenience types (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/6770|#6770>) > • Add support for CSS `@layer` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7504|#7504>) > • Export `CompileOptions` from `svelte/compiler` (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7658|#7658>) > • Fix DOM-less components not being properly destroyed (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7488|#7488>) > • Fix `class:` directive updates with `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7521|#7521>, <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7571|#7571>) > • Harden attribute escaping during SSR (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7530|#7530>) > > *3.48.0* > > • Allow creating cancelable custom events with `createEventDispatcher` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/4623|#4623>) > • Support `{@const}` tag in `{#if}` blocks <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7241|#7241> > • Return the context object in `setContext` <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7427|#7427> > • Allow comments inside `{#each}` blocks when using `animate:` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/3999|#3999>) > • Fix `|local` transitions in `{#key}` blocks (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/5950|#5950>) > • Support svg namespace for `{@html}` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7002|#7002>, <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7450|#7450>) > • Fix `{@const}` tag not working inside a component when there's no `let:` <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7189|#7189> > • Remove extraneous leading newline inside `<pre>` and `<textarea>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7264|#7264>) > • Fix erroneous setting of `textContent` for `\<template>` elements (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7297|#7297>) > • Fix value of `let:` bindings not updating in certain cases (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7440|#7440>) > • Fix handling of void tags in `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7449|#7449>) > • Fix handling of boolean attributes in `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7478|#7478>) > • Add special style scoping handling of `[open]` selectors on `<dialog>` elements (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7494|#7495>) Commits • <https://github.com/sveltejs/svelte/commit/52153dbce0237f0c36e4ff36377398d7f95276ef|`52153db`> -> v3.49.0 • <https://github.com/sveltejs/svelte/commit/3798808e7484b7eeee6acb2860c45bb2e59d84bd|`3798808`> update changelog • <https://github.com/sveltejs/svelte/commit/0fa0a38d5168a1767843fdb0a43c00aa30b8670f|`0fa0a38`> [fix] export CompileOptions (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7658|#7658>) • <https://github.com/sveltejs/svelte/commit/a3ecb44b5346dbf116c5bec5dcf47cd7f459784d|`a3ecb44`> update changelog • <https://github.com/sveltejs/svelte/commit/7e1691cd62df0593882480d00eb7e9a7616bb029|`7e1691c`> [fix] support <https://github.com/layer|`@layer`> (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7514|#7514>) • <https://github.com/sveltejs/svelte/commit/4583b170842208bcafcbb095221c8ac12689f739|`4583b17`> Update CHANGELOG.md • <https://github.com/sveltejs/svelte/commit/02f60fbebf7cdb036472d1aec8dc9d9f8215cd7a|`02f60fb`> [fix]destroy empty component (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7492|#7492>) • <https://github.com/sveltejs/svelte/commit/31e5f8b5de24e2e058cb1a70467c0092e422ee5d|`31e5f8b`> [docs] "What's new in Svelte" July newsletter (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7637|#7637>) • <https://github.com/sveltejs/svelte/commit/6f575715073f4a1eb1abdd7a2d22a75ae6017cf7|`6f57571`> [feat] add convenience types ComponentType and ComponentProps (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/6770|#6770>) • <https://github.com/sveltejs/svelte/commit/2f562d9e2817d911d0eec437d2b0e45074ec8291|`2f562d9`> [docs] use npm create instead of npm init (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7641|#7641>) • Additional commits viewable in <https://github.com/sveltejs/svelte/compare/v3.47.0...v3.49.0|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
00:55:43
Bumps <https://github.com/sveltejs/svelte|svelte> from 3.47.0 to 3.49.0. Changelog _Sourced from <https://github.com/sveltejs/svelte/blob/master/CHANGELOG.md|svelte's changelog>._ > *3.49.0* > > • Improve performance of string escaping during SSR (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/5701|#5701>) > • Add `ComponentType` and `ComponentProps` convenience types (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/6770|#6770>) > • Add support for CSS `@layer` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7504|#7504>) > • Export `CompileOptions` from `svelte/compiler` (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7658|#7658>) > • Fix DOM-less components not being properly destroyed (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7488|#7488>) > • Fix `class:` directive updates with `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7521|#7521>, <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7571|#7571>) > • Harden attribute escaping during SSR (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7530|#7530>) > > *3.48.0* > > • Allow creating cancelable custom events with `createEventDispatcher` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/4623|#4623>) > • Support `{@const}` tag in `{#if}` blocks <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7241|#7241> > • Return the context object in `setContext` <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7427|#7427> > • Allow comments inside `{#each}` blocks when using `animate:` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/3999|#3999>) > • Fix `|local` transitions in `{#key}` blocks (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/5950|#5950>) > • Support svg namespace for `{@html}` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7002|#7002>, <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7450|#7450>) > • Fix `{@const}` tag not working inside a component when there's no `let:` <https://github-redirect.dependabot.com/sveltejs/svelte/issues/7189|#7189> > • Remove extraneous leading newline inside `<pre>` and `<textarea>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7264|#7264>) > • Fix erroneous setting of `textContent` for `\<template>` elements (<https://github-redirect.dependabot.com/sveltejs/svelte/pull/7297|#7297>) > • Fix value of `let:` bindings not updating in certain cases (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7440|#7440>) > • Fix handling of void tags in `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7449|#7449>) > • Fix handling of boolean attributes in `<svelte:element>` (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7478|#7478>) > • Add special style scoping handling of `[open]` selectors on `<dialog>` elements (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7494|#7495>) Commits • <https://github.com/sveltejs/svelte/commit/52153dbce0237f0c36e4ff36377398d7f95276ef|`52153db`> -> v3.49.0 • <https://github.com/sveltejs/svelte/commit/3798808e7484b7eeee6acb2860c45bb2e59d84bd|`3798808`> update changelog • <https://github.com/sveltejs/svelte/commit/0fa0a38d5168a1767843fdb0a43c00aa30b8670f|`0fa0a38`> [fix] export CompileOptions (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7658|#7658>) • <https://github.com/sveltejs/svelte/commit/a3ecb44b5346dbf116c5bec5dcf47cd7f459784d|`a3ecb44`> update changelog • <https://github.com/sveltejs/svelte/commit/7e1691cd62df0593882480d00eb7e9a7616bb029|`7e1691c`> [fix] support <https://github.com/layer|`@layer`> (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7514|#7514>) • <https://github.com/sveltejs/svelte/commit/4583b170842208bcafcbb095221c8ac12689f739|`4583b17`> Update CHANGELOG.md • <https://github.com/sveltejs/svelte/commit/02f60fbebf7cdb036472d1aec8dc9d9f8215cd7a|`02f60fb`> [fix]destroy empty component (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7492|#7492>) • <https://github.com/sveltejs/svelte/commit/31e5f8b5de24e2e058cb1a70467c0092e422ee5d|`31e5f8b`> [docs] "What's new in Svelte" July newsletter (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7637|#7637>) • <https://github.com/sveltejs/svelte/commit/6f575715073f4a1eb1abdd7a2d22a75ae6017cf7|`6f57571`> [feat] add convenience types ComponentType and ComponentProps (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/6770|#6770>) • <https://github.com/sveltejs/svelte/commit/2f562d9e2817d911d0eec437d2b0e45074ec8291|`2f562d9`> [docs] use npm create instead of npm init (<https://github-redirect.dependabot.com/sveltejs/svelte/issues/7641|#7641>) • Additional commits viewable in <https://github.com/sveltejs/svelte/compare/v3.47.0...v3.49.0|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
00:57:56
<https://coveralls.io/builds/50910509|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/cfbd5ad312e57df54c54478f82766abf766e90db|cfbd5ad> on dependabot/npm_and_yarn/svelte-3.49.0* into *<https://github.com/cofacts/rumors-site/commit/98eeac30007c2515c86820e6328f1804f34c4a9f|98eeac3> on master*.
github2
00:57:56
<https://coveralls.io/builds/50910509|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/cfbd5ad312e57df54c54478f82766abf766e90db|cfbd5ad> on dependabot/npm_and_yarn/svelte-3.49.0* into *<https://github.com/cofacts/rumors-site/commit/98eeac30007c2515c86820e6328f1804f34c4a9f|98eeac3> on master*.
2022-07-17
github2
10:27:28
Bumps <https://github.com/moment/moment|moment> from 2.29.3 to 2.29.4. Changelog _Sourced from <https://github.com/moment/moment/blob/develop/CHANGELOG.md|moment's changelog>._ > *2.29.4* > > • Release Jul 6, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex 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>) • See full diff in <https://github.com/moment/moment/compare/2.29.3...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-site/network/alerts|Security Alerts page>.
github2
10:27:28
Bumps <https://github.com/moment/moment|moment> from 2.29.3 to 2.29.4. Changelog _Sourced from <https://github.com/moment/moment/blob/develop/CHANGELOG.md|moment's changelog>._ > *2.29.4* > > • Release Jul 6, 2022 > • <https://github-redirect.dependabot.com/moment/moment/pull/6015|#6015> [bugfix] Fix ReDoS in preprocessRFC2822 regex 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>) • See full diff in <https://github.com/moment/moment/compare/2.29.3...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-site/network/alerts|Security Alerts page>.
github2
10:29:38
<https://coveralls.io/builds/50926183|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/70b4079219076e3be494b03d4ce836e1849dcdca|70b4079> on dependabot/npm_and_yarn/moment-2.29.4* into *<https://github.com/cofacts/rumors-site/commit/5dd239f03babb7021cfc307eb7b5228ea4c0af3e|5dd239f> on master*.
github2
10:29:38
<https://coveralls.io/builds/50926183|Coverage Status> Coverage remained the same at 75.605% when pulling *<https://github.com/cofacts/rumors-site/commit/70b4079219076e3be494b03d4ce836e1849dcdca|70b4079> on dependabot/npm_and_yarn/moment-2.29.4* into *<https://github.com/cofacts/rumors-site/commit/5dd239f03babb7021cfc307eb7b5228ea4c0af3e|5dd239f> on master*.
mrorz
17:17:10
Ekoo 是什麼呀好神秘
https://cofacts.tw/article/19vk3cozuad7h
https://cofacts.tw/article/19vk3cozuad7h
交友APP吧?
mrorz
2022-07-18 16:06:03
對,看起來有自 apple store 上架,所以有過審
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
mrorz
17:17:10
Ekoo 是什麼呀好神秘
https://cofacts.tw/article/19vk3cozuad7h
https://cofacts.tw/article/19vk3cozuad7h
交友APP吧?
mrorz
2022-07-18 16:06:03
對,看起來有自 apple store 上架,所以有過審
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
2022-07-18
cai
16:04:21
交友APP吧?
mrorz
16:06:03
對,看起來有自 apple store 上架,所以有過審
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
針對這個回報我則有點困惑,看起來在回報的時候它可能曾經是 Ekoo 後來又改掉
cai
16:27:06
動滋健身券今天開始登記,好多人問
這次使用範圍很小欸……
這次使用範圍很小欸……
cai
16:27:06
動滋健身券今天開始登記,好多人問
這次使用範圍很小欸……
這次使用範圍很小欸……
cai
16:32:11
上禮拜萬安演習也分蠻多篇問的,還沒回XD
cai
16:32:11
上禮拜萬安演習也分蠻多篇問的,還沒回XD
mrorz
16:51:44
原來有加碼
感謝提醒 XDDD
感謝提醒 XDDD
mrorz
16:51:44
原來有加碼
感謝提醒 XDDD
感謝提醒 XDDD
2022-07-19
github2
03:24:30
Bumps <https://github.com/thenables/thenify|thenify> from 3.3.0 to 3.3.1. Changelog _Sourced from <https://github.com/thenables/thenify/blob/master/History.md|thenify's changelog>._ > *3.3.1 / 2020-06-18* > > *fixes* > > • [<https://github.com/thenables/thenify/commit/0d94a24eb933bc835d568f3009f4d269c4c4c17a|`0d94a24`>] - fix: remove eval (<https://github-redirect.dependabot.com/thenables/thenify/issues/30|#30>) (Yiyu He ) Commits • <https://github.com/thenables/thenify/commit/1d054b4d60e72087f4e804565e540258ecee7f0b|`1d054b4`> Release 3.3.1 • <https://github.com/thenables/thenify/commit/0d94a24eb933bc835d568f3009f4d269c4c4c17a|`0d94a24`> fix: remove eval (<https://github-redirect.dependabot.com/thenables/thenify/issues/30|#30>) • See full diff in <https://github.com/thenables/thenify/compare/3.3.0...3.3.1|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
03:24:30
Bumps <https://github.com/thenables/thenify|thenify> from 3.3.0 to 3.3.1. Changelog _Sourced from <https://github.com/thenables/thenify/blob/master/History.md|thenify's changelog>._ > *3.3.1 / 2020-06-18* > > *fixes* > > • [<https://github.com/thenables/thenify/commit/0d94a24eb933bc835d568f3009f4d269c4c4c17a|`0d94a24`>] - fix: remove eval (<https://github-redirect.dependabot.com/thenables/thenify/issues/30|#30>) (Yiyu He ) Commits • <https://github.com/thenables/thenify/commit/1d054b4d60e72087f4e804565e540258ecee7f0b|`1d054b4`> Release 3.3.1 • <https://github.com/thenables/thenify/commit/0d94a24eb933bc835d568f3009f4d269c4c4c17a|`0d94a24`> fix: remove eval (<https://github-redirect.dependabot.com/thenables/thenify/issues/30|#30>) • See full diff in <https://github.com/thenables/thenify/compare/3.3.0...3.3.1|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-20
cai
14:07:17
你們可以拿去新北聚問
https://cofacts.tw/article/2ycz1llsfy645
https://cofacts.tw/article/2ycz1llsfy645
cai
14:07:17
你們可以拿去新北聚問XD
https://cofacts.tw/article/2ycz1llsfy645
https://cofacts.tw/article/2ycz1llsfy645
mrorz
14:21:01
mrorz
14:21:01
mrorz
15:09:40
也是一招 XDD
mrorz
15:11:08
2022-07-22
cai
00:45:03
紓困詐騙的網頁改版了欸,改成學衛福部那個關鍵決策網
mrorz
2022-07-22 14:56:51
.tw 網域感覺可以勒令下架
mrorz
2022-07-22 14:59:03
為啥第一個出處 防詐達人的那篇下架了 QQ
因為他標題改了...... 可以請它們網址用數字的嗎
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
mrorz
2022-07-22 16:40:27
喔他是 wordpress
mrorz
2022-07-22 16:40:29
所以應該有
mrorz
2022-07-22 16:43:54
cai
00:45:03
https://cofacts.g0v.tw/article/8ok30n6a6px4
紓困詐騙的網頁改版了欸,改成學衛福部那個關鍵決策網
紓困詐騙的網頁改版了欸,改成學衛福部那個關鍵決策網
mrorz
2022-07-22 14:56:51
.tw 網域感覺可以勒令下架
mrorz
2022-07-22 14:59:03
為啥第一個出處 防詐達人的那篇下架了 QQ
因為他標題改了...... 可以請它們網址用數字的嗎
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
mrorz
2022-07-22 16:40:27
喔他是 wordpress
mrorz
2022-07-22 16:40:29
所以應該有
mrorz
2022-07-22 16:43:54
mrorz
14:56:51
.tw 網域感覺可以勒令下架
mrorz
14:59:03
為啥第一個出處 防詐達人的那篇下架了 QQ
cai
16:36:01
因為他標題改了...... 可以請它們網址用數字的嗎
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
getdr.com/防疫註冊補助勞務補助又是一個假冒政府紓困4-0/
mrorz
16:40:27
喔他是 wordpress
mrorz
16:40:29
所以應該有
mrorz
16:43:54
2022-07-24
cai
00:15:53
https://cofacts.tw/article/1zc2906tqpdkb
yahoo新聞會引用其他家新聞這點也變成詐騙集團的工具了
yahoo新聞會引用其他家新聞這點也變成詐騙集團的工具了
mrorz
2022-07-24 01:59:44
yahoo 太瞎⋯⋯
cai
00:15:53
https://cofacts.tw/article/1zc2906tqpdkb
yahoo新聞會引用其他家新聞這點也變成詐騙集團的工具了
yahoo新聞會引用其他家新聞這點也變成詐騙集團的工具了
mrorz
2022-07-24 01:59:44
yahoo 太瞎⋯⋯
cai
00:33:15
https://cofacts.tw/article/2v773qmdg7pdx 為什麼會丟台酒闖關解謎的答案來問啦😆
mrorz
2022-07-24 01:59:03
驗證攻略的正確性 (?
cai
00:33:15
https://cofacts.tw/article/2v773qmdg7pdx 為什麼會丟台酒闖關解謎的答案來問啦😆
mrorz
2022-07-24 01:59:03
驗證攻略的正確性 (?
mrorz
01:59:03
驗證攻略的正確性 (?
mrorz
01:59:44
yahoo 太瞎⋯⋯
流星若風的烤肉屋
11:19:25
@skywind5487 has joined the channel
KMW
11:21:10
@kyf232001 has joined the channel
jerry
11:21:17
@jerry0625xd has joined the channel
coach-peter
11:21:31
@peter810805 has joined the channel
Olivia
11:21:32
@huangzirong41 has joined the channel
chai-yun lee
11:21:33
@erica1028tw has joined the channel
Patrick
11:21:41
@patrick.chung2003 has joined the channel
Prud
11:22:05
@peichingchen264 has joined the channel
Yining Huang
11:22:09
@karenynhuang has joined the channel
W易平
11:22:43
@pennyw0918 has joined the channel
楊絃筠
11:35:48
@xianyun1122 has joined the channel
Alvin Lin
13:33:17
@ooii8929 has joined the channel
Karen Lin
14:26:45
@karen901208 has joined the channel
洪心瑜
16:39:50
@s971088417 has joined the channel
wen
21:19:34
@xwen1201 has joined the channel
maxchiu1234
21:27:11
@maxchiu1234 has joined the channel
2022-07-25
mrorz
15:27:38
這個是移除隱私資訊的 request 唷
請大家看一下
請大家看一下
2022-07-26
cai
23:08:49
Replied to a thread: 2022-07-13 13:49:20
https://cofacts.tw/article/2q5nf5c5s650k
看來在收尾了,這次換冒用台中警方跟金管會名義
看來在收尾了,這次換冒用台中警方跟金管會名義
cai
23:09:42
簡體字跟中國用語露餡了
2022-07-27
faling
10:49:00
@faling.fan has joined the channel
mrorz
13:48:11
Wow 所以他們直接在群組做二次詐騙喔
令人瞠目結舌
令人瞠目結舌
mrorz
13:48:24
無縫接軌到二次詐騙耶
phil
20:00:12
@phil153351185 has joined the channel
2022-07-29
2022-07-30
cai
14:25:01
https://cofacts.tw/article/84kdex4sy2bk
這篇搭的影片有不少種,有bump的也有別的
這篇搭的影片有不少種,有bump的也有別的
github2
14:34:38
This PR depends on API PR <https://github.com/cofacts/rumors-api/pull/289|cofacts/rumors-api#289> . Fixes <https://github.com/cofacts/rumors-site/issues/485|#485> Implements LIFF breakdown • LINE visit in chart includes Cofacts chatbot, LIFF in tmcheck and meiyu • Breakdown is shown • Updates storybook and snapshot • Updates translation *Before* <https://dev.cofacts.tw/article/1kf4vrfen40rz|https://dev.cofacts.tw/article/1kf4vrfen40rz> <https://user-images.githubusercontent.com/108608/181878000-3e6d5ed3-2fb0-4c87-aa7c-affc2fb05ecf.png|image> *After* Same article <https://user-images.githubusercontent.com/108608/181877964-4a7ebf8f-89b3-4ecf-b2ea-49a51d45ba0e.png|image>![]()
github2
14:34:38
This PR depends on API PR <https://github.com/cofacts/rumors-api/pull/289|cofacts/rumors-api#289> Implements LIFF breakdown • LINE visit in chart includes Cofacts chatbot, LIFF in tmcheck and meiyu • Breakdown is shown • Updates storybook and snapshot • Updates translation *Before* <https://dev.cofacts.tw/article/1kf4vrfen40rz|https://dev.cofacts.tw/article/1kf4vrfen40rz> <https://user-images.githubusercontent.com/108608/181878000-3e6d5ed3-2fb0-4c87-aa7c-affc2fb05ecf.png|image> *After* Same article <https://user-images.githubusercontent.com/108608/181877964-4a7ebf8f-89b3-4ecf-b2ea-49a51d45ba0e.png|image>![]()
github2
14:37:51
<https://coveralls.io/builds/51284496|Coverage Status> Coverage increased (+0.2%) to 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/c41eb19829deb1f67f5d2140c4a04e2638ed324e|c41eb19> on liff-trend* into *<https://github.com/cofacts/rumors-site/commit/5dd239f03babb7021cfc307eb7b5228ea4c0af3e|5dd239f> on master*.
github2
14:37:51
<https://coveralls.io/builds/51284496|Coverage Status> Coverage increased (+0.2%) to 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/c41eb19829deb1f67f5d2140c4a04e2638ed324e|c41eb19> on liff-trend* into *<https://github.com/cofacts/rumors-site/commit/5dd239f03babb7021cfc307eb7b5228ea4c0af3e|5dd239f> on master*.
2022-07-31
github2
01:58:18
This PR initializes Typescript by turning a page component to tsx file to trigger <https://nextjs.org/blog/next-9#built-in-zero-config-typescript-support|Next.js 9's automated Typescript setup>. ☐ `*.tsx` in `rumors-site` can be typechecked correctly ☐ website can build and execute ☐ CI works ☐ Can generate type & specific useQuery using codegen ☐ Can type individual fragments Note: if you encounter issue regarding "JSX flag" in VS Code, please select Typescript with "workspace version". <https://user-images.githubusercontent.com/108608/181935828-03e62672-4690-461f-9ee8-74a2a739937a.png|image>![]()
github2
01:58:18
This PR initializes Typescript by turning a page component to tsx file to trigger <https://nextjs.org/blog/next-9#built-in-zero-config-typescript-support|Next.js 9's automated Typescript setup>. ☐ `*.tsx` in `rumors-site` can be typechecked correctly ☐ website can build and execute ☐ CI works ☐ Can generate type & specific useQuery using codegen ☐ Can type individual fragments Note: if you encounter issue regarding "JSX flag" in VS Code, please select Typescript with "workspace version". <https://user-images.githubusercontent.com/108608/181935828-03e62672-4690-461f-9ee8-74a2a739937a.png|image>![]()
chewei 哲瑋
06:41:01
2022 / 07 / 31
10:00 ~ 10:30
TR412-1 Open Source & AI
Cofacts 中的 LINE 轉傳訊息的自動分類
by ggm
https://coscup.org/2022/zh-TW/session/DVSRME?fs=e&s=cl
10:00 ~ 10:30
TR412-1 Open Source & AI
Cofacts 中的 LINE 轉傳訊息的自動分類
by ggm
https://coscup.org/2022/zh-TW/session/DVSRME?fs=e&s=cl
COSCUP 2022
Cofacts 是一個結合 LINE Bot 與事實查核的開放平台,這平台上存放許多透過 LINE Bot 收集的轉傳訊息,為了讓查證的編輯能夠更有效率的...
王憶萍
08:59:15
@wyipin has joined the channel
cai
21:28:42