g0v.hackmd.io
Updated according to <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F6gLsmuTUQia3sjyYPPcFvQ|meeting discussion> <https://user-images.githubusercontent.com/108608/182918507-60654179-2925-4a2b-b327-51f9f4a83a91.png|image> <https://user-images.githubusercontent.com/108608/182918534-4dfccae9-45fd-49f3-a5fa-752f2883a845.png|image> <https://user-images.githubusercontent.com/108608/182918681-8a863e10-3541-4ca3-8c50-dc446618eadb.png|image> <https://user-images.githubusercontent.com/108608/182918712-7a231ec1-b654-4871-b803-4f3f312171e6.png|image>
Updated according to <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F6gLsmuTUQia3sjyYPPcFvQ|meeting discussion> <https://user-images.githubusercontent.com/108608/182918507-60654179-2925-4a2b-b327-51f9f4a83a91.png|image> <https://user-images.githubusercontent.com/108608/182918534-4dfccae9-45fd-49f3-a5fa-752f2883a845.png|image> <https://user-images.githubusercontent.com/108608/182918681-8a863e10-3541-4ca3-8c50-dc446618eadb.png|image> <https://user-images.githubusercontent.com/108608/182918712-7a231ec1-b654-4871-b803-4f3f312171e6.png|image>
cofacts.github.io
Web site created using create-react-app
arXiv.org
Ask to Know More: Generating Counterfactual Explanations for Fake Claims
Automated fact checking systems have been proposed that quickly provide veracity prediction at scale to mitigate the negative influence of fake news on people and on public opinion. However, most...
Ask to Know More: Counterfactual Explanations for Fake Claims source code
<https://github.com/cofacts/rumors-line-bot/pull/316|#316 Feature/image search>
1. Implement processImage 2. Remove old image related code: tesseract-ocr, GDrive 3. Extract postback event function as a standalone handler 4. Remove isSkipUser paramater by directly calling `handlePostback`
<https://github.com/cofacts/rumors-line-bot/pull/316|#316 Feature/image search>
*Changes* 1. Implement processImage, fixes <https://github.com/cofacts/rumors-line-bot/issues/304|#304> 2. Remove old image related code: tesseract-ocr, GDrive 3. Extract postback event function as a standalone handler • Input(text) -> `handleInput` -> return buttons that will trigger `handlePostback` • Input(image) -> `processImage` -> return buttons that will trigger `handlePostback` • Input(postback) -> `handlePostback` 4. Remove isSkipUser (only used in `initState`) parameter by directly calling `handlePostback` *Snapshots* <https://user-images.githubusercontent.com/6376572/183279240-d72dce87-c366-4050-b989-c3927a7bb100.png|https://user-images.githubusercontent.com/6376572/183279240-d72dce87-c366-4050-b989-c3927a7bb100.png> <https://user-images.githubusercontent.com/6376572/183279242-7a99b590-d773-4e0d-b764-479262af57ca.png|https://user-images.githubusercontent.com/6376572/183279242-7a99b590-d773-4e0d-b764-479262af57ca.png> <https://user-images.githubusercontent.com/6376572/183279246-e642c1ce-a2bd-4d5d-b29b-730bf6f41ea2.png|https://user-images.githubusercontent.com/6376572/183279246-e642c1ce-a2bd-4d5d-b29b-730bf6f41ea2.png>
:white_check_mark: All checks have passed
*Pull Request Test Coverage Report for <https://coveralls.io/builds/51470788|Build 2811714669>* • *83* of *106* *(78.3%)* changed or added relevant lines in *11* files are covered. • *4* unchanged lines in *2* files lost coverage. • Overall coverage increased (+*5.8%*) to *91.292%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
*Pull Request Test Coverage Report for <https://coveralls.io/builds/51470788|Build 2811714669>* • *83* of *106* *(78.3%)* changed or added relevant lines in *11* files are covered. • *4* unchanged lines in *2* files lost coverage. • Overall coverage increased (+*5.8%*) to *91.292%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
When back filling old analytics data, we found that the fetched LIFF stats are inconsistent with the numbers on Google Analytics. We can reproduce this on local machine, and found that the inaccuracy only happens when the data is sampled: <https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling|https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling> If we specify a shorter date range when running the script, the inconsistency will be gone. This PR adds a warning message when sampled data is detected from the Google Analytics Reporting API response. <https://user-images.githubusercontent.com/108608/183285758-e32e57a5-6533-48d3-96ad-c0e4e5b6bfbf.png|圖片>
When back filling old analytics data, we found that the fetched LIFF stats are inconsistent with the numbers on Google Analytics. We can reproduce this on local machine, and found that the inaccuracy only happens when the data is sampled: <https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling|https://developers.google.com/analytics/devguides/reporting/core/v4/basics#sampling> If we specify a shorter date range when running the script, the inconsistency will be gone. This PR adds a warning message when sampled data is detected from the Google Analytics Reporting API response. <https://user-images.githubusercontent.com/108608/183285758-e32e57a5-6533-48d3-96ad-c0e4e5b6bfbf.png|圖片> Sampling should only happens when we manually back-fill the data. The hourly cron job should not have that much of data that triggers Google Analytics samplng.
:white_check_mark: All checks have passed
<https://coveralls.io/builds/51471855|Coverage Status> Coverage increased (+0.01%) to 87.768% when pulling *<https://github.com/cofacts/rumors-api/commit/4aac44c901ef46b5e512909c22b5a492b74bca76|4aac44c> on warn-about-sampled* into *<https://github.com/cofacts/rumors-api/commit/985911c62e94f6d15e330f61d9bc1d05d9263480|985911c> on master*.
<https://coveralls.io/builds/51471855|Coverage Status> Coverage increased (+0.01%) to 87.768% when pulling *<https://github.com/cofacts/rumors-api/commit/4aac44c901ef46b5e512909c22b5a492b74bca76|4aac44c> on warn-about-sampled* into *<https://github.com/cofacts/rumors-api/commit/985911c62e94f6d15e330f61d9bc1d05d9263480|985911c> on master*.
:+1::+1::+1:
:+1::+1::+1:
<https://github.com/cofacts/takedowns/pull/84|#84 Create 0810-love-scam.md>
<https://github.com/cofacts/takedowns/pull/84|#84 Create 0810-love-scam.md>
HackMD
# Cofacts 會議記錄 ## 2022 - [20220810 會議記錄](/uZ3gouRWRamtrCFzKFrgnw) - [20220803 會議記錄](/6gLsmuTUQia3
Q: seems that we should delete these text related search from `processImage` test ?
Q: seems that we should delete these text related search from `processImage` test ?
I think we should not show "None of these messages matches mine" if there is a 100% match. Because if the user chooses this option and tries to submit the image, `MediaManager` will find that the uploaded file has 100% match and does not perform upload anyway.
I think we should not show "None of these messages matches mine" if there is a 100% match. Because if the user chooses this option and tries to submit the image, `MediaManager` will find that the uploaded file has 100% match and does not perform upload anyway.
Review on #316 Feature/image search
Thanks for the contribution! Although the PR is big, it's still understandable. The PR description and the weekly sync helped a lot :+1: Please find my comments below.
Review on #316 Feature/image search
Thanks for the contribution! Although the PR is big, it's still understandable. The PR description and the weekly sync helped a lot :+1: Please find my comments below.
Unused, suggest remove Suggested change
Unused, suggest remove Suggested change
Let's add a comment denoting the reason why we -1: Suggested change
Let's add a comment denoting the reason why we -1: Suggested change
The height of thumbnail image always does not exceed 240px (set <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/mutations/CreateMediaArticle.js#L67|in rumors-api>). Can we set the <https://developers.line.biz/en/docs/messaging-api/flex-message-layout/#box-max-height|maxHeight> of hero so that images don't get blurry?
The height of thumbnail image always does not exceed 240px (set <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/mutations/CreateMediaArticle.js#L67|in rumors-api>). Can we set the <https://developers.line.biz/en/docs/messaging-api/flex-message-layout/#box-max-height|maxHeight> of hero so that images don't get blurry?
Outdated comment. Hope we can fix the comment along with this PR XD Suggested change
Outdated comment. Hope we can fix the comment along with this PR XD Suggested change
Review on #317 docs: fix hyperlink
Thanks for the update!
Review on #317 docs: fix hyperlink
Thanks for the update!
*Pull Request Test Coverage Report for <https://coveralls.io/builds/51586704|Build 2838255119>* • *0* of *0* changed or added relevant lines in *0* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *85.487%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
*Pull Request Test Coverage Report for <https://coveralls.io/builds/51586704|Build 2838255119>* • *0* of *0* changed or added relevant lines in *0* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *85.487%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> LIFF article list (articles) and article page should support displaying images
From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> LIFF article list (articles) and article page should support displaying images
From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> *As-is* <https://user-images.githubusercontent.com/108608/185045067-dfd5fdb5-4f7c-47d8-baad-3037bb1fe2d4.png|image> *To-be* If there is no other people submitting reply request / comments, we should not show the second sentence. Just use the first sentence (thank the user).
From 20220810 test result: <https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|https://g0v.hackmd.io/uZ3gouRWRamtrCFzKFrgnw#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE> *As-is* <https://user-images.githubusercontent.com/108608/185045067-dfd5fdb5-4f7c-47d8-baad-3037bb1fe2d4.png|image> *To-be* If there is no other people submitting reply request / comments, we should not show the second sentence. Just use the first sentence (thank the user).
Q: is this expected that `processImage()` returns a context with `messageId` being `undefined`? Seems that the mock event in the test case is `{message: {id: '...'}}` but in `processImage` we store `event.messageId` in context. Which one is correct?
Q: is this expected that `processImage()` returns a context with `messageId` being `undefined`? Seems that the mock event in the test case is `{message: {id: '...'}}` but in `processImage` we store `event.messageId` in context. Which one is correct?
Review on #318 Feature/image submit
Thanks for the PR! Wordings look good to me, will deploy to staging and test. Please find my comments below.
Review on #318 Feature/image submit
Thanks for the PR! Wordings look good to me, will deploy to staging and test. Please find my comments below.
Oh! My test input is incorrect, it should have a `messageId` in the test input. I will update it! In `webhook/index.js`, I assign a `messageId` to `event`: `event = { messageId: otherFields.message.id, type, ...otherFields };`.
Oh! My test input is incorrect, it should have a `messageId` in the test input. I will update it! In `webhook/index.js`, I assign a `messageId` to `event`: `event = { messageId: otherFields.message.id, type, ...otherFields };`.
facebook.com
See posts, photos and more on Facebook.
Review on #316 Feature/image search
LGTM!
Review on #316 Feature/image search
LGTM!
Review on #318 Feature/image submit
Thanks, LGTM!
Review on #318 Feature/image submit
Thanks, LGTM!
<https://github.com/cofacts/rumors-line-bot/pull/318|#318 Feature/image submit>
<https://github.com/cofacts/rumors-line-bot/pull/318|#318 Feature/image submit>
<https://github.com/cofacts/rumors-site/pull/501|#501 Add articleTypes URL param without UI>
This PR adds a URL param, `articleTypes`, to rumors-site article list. • Currently we do not officially launch image support, so the UI of this filter is not implemented yet. • Users must *manually specify `articleTypes` in URL*, it is not accessible from UI. • `articleTypes` should be a comma separated list of `ArticleTypeEnum` (`TEXT`, `IMAGE`, `VIDEO`, `AUDIO`). • When not given, `articleTypes` is not specified in `ListArticles`. • If given, `articleTypes` is specified and thus would <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/queries/ListArticles.js#L513-L525|override `MEDIA_ARTICLE_SUPPORT` flag in rumors-api>. *Screenshot* *Only images* <https://user-images.githubusercontent.com/108608/186336655-06eccc25-366b-4ef7-84bc-2ba151bad949.png|image> *Only text* <https://user-images.githubusercontent.com/108608/186336735-0c53f560-6b84-440f-9633-800b66d20c6b.png|image> *Not specified* The result depends on if the API has turned on `MEDIA_ARTICLE_SUPPORT` flag. On staging it is turned on, so it does not limit the article type to just text. <https://user-images.githubusercontent.com/108608/186336888-e4f02d18-1fb3-49d0-9431-f656d851678b.png|image>
:white_check_mark: All checks have passed
<https://github.com/cofacts/rumors-site/pull/501|#501 Add articleTypes URL param without UI>
This PR adds a URL param, `articleTypes`, to rumors-site article list. • Currently we do not officially launch image support, so the UI of this filter is not implemented yet. • Users must *manually specify `articleTypes` in URL*, it is not accessible from UI. • `articleTypes` should be a comma separated list of `ArticleTypeEnum` (`TEXT`, `IMAGE`, `VIDEO`, `AUDIO`). • When not given, `articleTypes` is not specified in `ListArticles`. • If given, `articleTypes` is specified and thus would <https://github.com/cofacts/rumors-api/blob/8eb18c6202be8735e5d7fe31db4fee5acd7eee06/src/graphql/queries/ListArticles.js#L513-L525|override `MEDIA_ARTICLE_SUPPORT` flag in rumors-api>. *Screenshot* *Only images* <https://user-images.githubusercontent.com/108608/186336655-06eccc25-366b-4ef7-84bc-2ba151bad949.png|image> *Only text* <https://user-images.githubusercontent.com/108608/186336735-0c53f560-6b84-440f-9633-800b66d20c6b.png|image> *Not specified* The result depends on if the API has turned on `MEDIA_ARTICLE_SUPPORT` flag. On staging it is turned on, so it does not limit the article type to just text. <https://user-images.githubusercontent.com/108608/186336888-e4f02d18-1fb3-49d0-9431-f656d851678b.png|image>
:white_check_mark: All checks have passed
<https://coveralls.io/builds/51897634|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/e0130121d06d74d2a5bf7c4bcc9667fad9048c93|e013012> on article-type* into *<https://github.com/cofacts/rumors-site/commit/1808d09f411c313454f4214748a9c2dba0627225|1808d09> on master*.
<https://coveralls.io/builds/51897634|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/e0130121d06d74d2a5bf7c4bcc9667fad9048c93|e013012> on article-type* into *<https://github.com/cofacts/rumors-site/commit/1808d09f411c313454f4214748a9c2dba0627225|1808d09> on master*.
g0v.hackmd.io
ETtoday新聞雲
Kevin老師有急事找你!台中男誤信證券簡訊 遭吸乾1400萬 | ETtoday社會新聞 | ETtoday新聞雲
近期許多民眾都收炒股、投資等詐騙簡訊,對方假冒證券商、銀行等名義寄簡訊騷擾,還會裝熟抱怨民眾消失很久沒聯絡,或稱有急事要求人加通訊軟體。台中就有一名張先生收到一封簡訊,自稱Kevin老師能介紹飆股,結果誤信加入群組及對方設立的App操作股票,前後宛如鬼遮眼般匯出1400萬元,隨即被踢出群組及封鎖帳號,張先生怒向議員檢舉,也希望提醒其他人不要受害。
facebook.com
See posts, photos and more on Facebook.
<https://github.com/cofacts/media-manager/pull/9|#9 Allow query by ID>
This PR adds functionality to search similar media entries by media entry ID. ``` mediaManager.query({ id: mediaEntryId }); ``` Note that it is prohibited that `id` and `url` are used together.
<https://github.com/cofacts/media-manager/pull/9|#9 Allow query by ID>
This PR adds functionality to search similar media entries by media entry ID. ``` mediaManager.query({ id: mediaEntryId }); ``` Note that it is prohibited that `id` and `url` are used together.
Support image articles be displayed in the similar article section in article detail page. Depends on API <https://github.com/cofacts/rumors-api/pull/291|cofacts/rumors-api#291> *Storybook* Mobile <https://user-images.githubusercontent.com/108608/187089547-c315e151-9659-4629-b12f-7e3072ad91f7.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089552-1614b89c-2425-4b4f-a1ff-63d1cc73608d.png|image> *Real example* Mobile <https://user-images.githubusercontent.com/108608/187089493-baac15b3-a4fe-467d-ad3e-9fce860a9d9c.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089466-29347cc9-0ecc-4b81-a73a-c63f98e722ac.png|image>
:white_check_mark: All checks have passed
Support image articles be displayed in the similar article section in article detail page. Depends on API <https://github.com/cofacts/rumors-api/pull/291|cofacts/rumors-api#291> *Storybook* Mobile <https://user-images.githubusercontent.com/108608/187089547-c315e151-9659-4629-b12f-7e3072ad91f7.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089552-1614b89c-2425-4b4f-a1ff-63d1cc73608d.png|image> *Real example* Mobile <https://user-images.githubusercontent.com/108608/187089493-baac15b3-a4fe-467d-ad3e-9fce860a9d9c.png|image> Desktop <https://user-images.githubusercontent.com/108608/187089466-29347cc9-0ecc-4b81-a73a-c63f98e722ac.png|image>
:white_check_mark: All checks have passed
<https://coveralls.io/builds/52007988|Coverage Status> Coverage increased (+0.03%) to 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/217fde412537e6c0e5fae4b82144d347ee862239|217fde4> on related-media-articles* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.
<https://coveralls.io/builds/52007988|Coverage Status> Coverage increased (+0.03%) to 75.86% when pulling *<https://github.com/cofacts/rumors-site/commit/217fde412537e6c0e5fae4b82144d347ee862239|217fde4> on related-media-articles* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.
g0v.hackmd.io
Dcard
一開始,某人加了我賴,然後語音問我是不是在哪裡要找他買衣服的,我因為滿頭問號加上不認識,所以沒有理他,過了一段時間他又打字問了一次,最後說是個誤會,然後他就很直接的自我介紹、自己平常會做的事,說他當過 - 生活
<https://github.com/cofacts/rumors-fb-bot/pull/39|#39 Bump moment-timezone from 0.5.21 to 0.5.37>
Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.21 to 0.5.37. Release notes _Sourced from <https://github.com/moment/moment-timezone/releases|moment-timezone's releases>._ > *0.5.34* > > • Updated data to IANA TZDB `2021e` > > *Release 0.5.33* > > • Updated data to IANA TZDB `2021a` > > *Release 0.5.32* > > • Updated data to IANA TZDB `2020d` > > *Release 0.5.31* > > Fixed Travis builds for Node.js 4 and 6 > > *Release 0.5.28* > *`0.5.29` _2020-02-21_* > > Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@adgrace`>: > > • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country > • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone > • Added a method `moment.tz.countries()` to get all country codes > • And as you know `moment.tz.names()` already exists > > *Release 0.5.27* > *`0.5.27` _2019-10-14_* > > • Updated data to IANA TZDB `2019c > > *Release 0.5.26* > > • Updated data to IANA TZDB `2019b` > • Fix: stabilize Array.sort <https://github-redirect.dependabot.com/moment/moment-timezone/pull/762|#762> > > *Release 0.5.25* > > • Fix `moment.tz.dataVersion` to return `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/742|#742> > • Update path in bower.json > > *Release 0.5.24* > > • Updated data to IANA TZDB `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/737|#737> > • Start shipping both a 1970-1930 file and a rolling 10-year file <https://github-redirect.dependabot.com/moment/moment-timezone/issues/614|#614> <https://github-redirect.dependabot.com/moment/moment-timezone/issues/697|#697> > • Fixed bug where `_z` time zone name was not cleared with `.local()` or `.utcOffset(offset)` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/738|#738> > > *Release 0.5.23* > > • Fix minor issue with tz guessing in Russia <https://github-redirect.dependabot.com/moment/moment-timezone/issues/691|#691> > > *Release 0.5.22* > > • Updated data to IANA TZDB 2018g <https://github-redirect.dependabot.com/moment/moment-timezone/issues/689|#689> > • Fix issue with missing LMT entries for some zones, and fix data builds on Linux and Windows <https://github-redirect.dependabot.com/moment/moment-timezone/issues/308|#308> Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ > *`0.5.37` _2022.08-25_* > > • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> > > *`0.5.36` _2022.08-25_* > > • IANA TZDB 2022c > • improvements/fixes to data pipeline > > *`0.5.35` _2022-08-23_* > > • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> > • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> > > Thanks to the OpenSSF Alpha-Omega project for reporting these! > > *`0.5.34` _2020-11-10_* > > • Updated data to IANA TZDB `2021e` > > *`0.5.33` _2020-11-15_* > > • Updated data to IANA TZDB `2021a` > > *`0.5.32` _2020-11-14_* > > • Updated data to IANA TZDB `2020d` > > *`0.5.31` _2020-05-16_* > > • Fixed Travis builds for Node.js 4 and 6 > > *`0.5.30` _2020-05-16_* > > • Updated data to IANA TZDB `2020a` > • Fixed typescript definitions > > NOTE: You might need to un-install `@types/moment-timezone`. Check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/858|moment/moment-timezone#858> for more info > > *`0.5.29` _2020-05-16_* > > • Merged fix of es6 module loading issue <https://github.com/moment/moment-timezone/commit/1fd42349189b24e15c60f162dc8c40b42db79dfe|moment/moment-timezone@1fd4234> > • Merged PR with typescript declarations <https://github.com/moment/moment-timezone/commit/ed529ea6fbcc70315c0c3f6d7c7cb70eadf56b03|moment/moment-timezone@ed529ea> > • Merged fixes to changelog <https://github.com/moment/moment-timezone/commit/adb7d7b43c7328d814311ac1355bfeef88eab6e8|moment/moment-timezone@adb7d7b> > > *`0.5.28` _2020-02-21_* > > Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@adgrace`>: > > • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country > • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone > • Added a method `moment.tz.countries()` to get all country codes > • And as you know `moment.tz.zones()` already exists > > *`0.5.27` _2019-10-14_* > > • Updated data to IANA TZDB `2019c` > > *`0.5.26` _2019-06-06_* > > • Updated data to IANA TZDB `2019b` ... (truncated) Commits • See full diff in <https://github.com/moment/moment-timezone/commits/0.5.37|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-fb-bot/network/alerts|Security Alerts page>.
<https://github.com/cofacts/rumors-fb-bot/pull/39|#39 Bump moment-timezone from 0.5.21 to 0.5.37>
Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.21 to 0.5.37. Release notes _Sourced from <https://github.com/moment/moment-timezone/releases|moment-timezone's releases>._ > *0.5.34* > > • Updated data to IANA TZDB `2021e` > > *Release 0.5.33* > > • Updated data to IANA TZDB `2021a` > > *Release 0.5.32* > > • Updated data to IANA TZDB `2020d` > > *Release 0.5.31* > > Fixed Travis builds for Node.js 4 and 6 > > *Release 0.5.28* > *`0.5.29` _2020-02-21_* > > Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@adgrace`>: > > • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country > • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone > • Added a method `moment.tz.countries()` to get all country codes > • And as you know `moment.tz.names()` already exists > > *Release 0.5.27* > *`0.5.27` _2019-10-14_* > > • Updated data to IANA TZDB `2019c > > *Release 0.5.26* > > • Updated data to IANA TZDB `2019b` > • Fix: stabilize Array.sort <https://github-redirect.dependabot.com/moment/moment-timezone/pull/762|#762> > > *Release 0.5.25* > > • Fix `moment.tz.dataVersion` to return `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/742|#742> > • Update path in bower.json > > *Release 0.5.24* > > • Updated data to IANA TZDB `2019a` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/737|#737> > • Start shipping both a 1970-1930 file and a rolling 10-year file <https://github-redirect.dependabot.com/moment/moment-timezone/issues/614|#614> <https://github-redirect.dependabot.com/moment/moment-timezone/issues/697|#697> > • Fixed bug where `_z` time zone name was not cleared with `.local()` or `.utcOffset(offset)` <https://github-redirect.dependabot.com/moment/moment-timezone/issues/738|#738> > > *Release 0.5.23* > > • Fix minor issue with tz guessing in Russia <https://github-redirect.dependabot.com/moment/moment-timezone/issues/691|#691> > > *Release 0.5.22* > > • Updated data to IANA TZDB 2018g <https://github-redirect.dependabot.com/moment/moment-timezone/issues/689|#689> > • Fix issue with missing LMT entries for some zones, and fix data builds on Linux and Windows <https://github-redirect.dependabot.com/moment/moment-timezone/issues/308|#308> Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ > *`0.5.37` _2022.08-25_* > > • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> > > *`0.5.36` _2022.08-25_* > > • IANA TZDB 2022c > • improvements/fixes to data pipeline > > *`0.5.35` _2022-08-23_* > > • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> > • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> > > Thanks to the OpenSSF Alpha-Omega project for reporting these! > > *`0.5.34` _2020-11-10_* > > • Updated data to IANA TZDB `2021e` > > *`0.5.33` _2020-11-15_* > > • Updated data to IANA TZDB `2021a` > > *`0.5.32` _2020-11-14_* > > • Updated data to IANA TZDB `2020d` > > *`0.5.31` _2020-05-16_* > > • Fixed Travis builds for Node.js 4 and 6 > > *`0.5.30` _2020-05-16_* > > • Updated data to IANA TZDB `2020a` > • Fixed typescript definitions > > NOTE: You might need to un-install `@types/moment-timezone`. Check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/858|moment/moment-timezone#858> for more info > > *`0.5.29` _2020-05-16_* > > • Merged fix of es6 module loading issue <https://github.com/moment/moment-timezone/commit/1fd42349189b24e15c60f162dc8c40b42db79dfe|moment/moment-timezone@1fd4234> > • Merged PR with typescript declarations <https://github.com/moment/moment-timezone/commit/ed529ea6fbcc70315c0c3f6d7c7cb70eadf56b03|moment/moment-timezone@ed529ea> > • Merged fixes to changelog <https://github.com/moment/moment-timezone/commit/adb7d7b43c7328d814311ac1355bfeef88eab6e8|moment/moment-timezone@adb7d7b> > > *`0.5.28` _2020-02-21_* > > Merged pull request <https://github-redirect.dependabot.com/moment/moment-timezone/issues/410|#410> from <https://github.com/adgrace|`@adgrace`>: > > • Added a method `moment.tz.zonesForCountry(country_code)` which returns all timezones for the country > • Added a method `<http://moment.tz|moment.tz>(timezone_id).countries()` to get countries for some time zone > • Added a method `moment.tz.countries()` to get all country codes > • And as you know `moment.tz.zones()` already exists > > *`0.5.27` _2019-10-14_* > > • Updated data to IANA TZDB `2019c` > > *`0.5.26` _2019-06-06_* > > • Updated data to IANA TZDB `2019b` ... (truncated) Commits • See full diff in <https://github.com/moment/moment-timezone/commits/0.5.37|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-fb-bot/network/alerts|Security Alerts page>.
<https://github.com/cofacts/rumors-site/pull/503|#503 Bump moment-timezone from 0.5.34 to 0.5.37>
Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.34 to 0.5.37. Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ > *`0.5.37` _2022.08-25_* > > • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> > > *`0.5.36` _2022.08-25_* > > • IANA TZDB 2022c > • improvements/fixes to data pipeline > > *`0.5.35` _2022-08-23_* > > • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> > • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> > > Thanks to the OpenSSF Alpha-Omega project for reporting these! Commits • <https://github.com/moment/moment-timezone/commit/ffe6f340a6bdae6be1cbc1cbef4a4f2b87e2c63c|`ffe6f34`> Add changelog for 0.5.37 • <https://github.com/moment/moment-timezone/commit/450ca6304ba62baf27817ed7840828eee4e3b0c5|`450ca63`> Bump version to 0.5.37 • <https://github.com/moment/moment-timezone/commit/95f1a9b5cd3a15b8c75bd36029152ff1b43a5136|`95f1a9b`> Build moment-timezone 0.5.36 • <https://github.com/moment/moment-timezone/commit/abba28c7b0e1faf7df8592806007fcb2753b3078|`abba28c`> Add changelog for 0.5.36 • <https://github.com/moment/moment-timezone/commit/ac6de03cf34610068185961613d719bc050c7d2b|`ac6de03`> Bump version to 0.5.36 • <https://github.com/moment/moment-timezone/commit/7a5cadf9cbece0a9c7b9da0ee244c21375eb33a6|`7a5cadf`> tests: Fix country tests for 2022c • <https://github.com/moment/moment-timezone/commit/6754c75f5be4fbb16e90e336c9decbad6b506388|`6754c75`> data: generate 2022c data+tests • <https://github.com/moment/moment-timezone/commit/f74a364b1aac2c96cedd0a8cf5c7188268b9bcde|`f74a364`> bugfix: Wipe tests/zones before generation • <https://github.com/moment/moment-timezone/commit/e850f9fa6d3b440c51ae0cda7d9d573627839167|`e850f9f`> grunt: do not bundle zone and contry tests • <https://github.com/moment/moment-timezone/commit/f13e22b069f9115eddad5294a4c0f5335c61590a|`f13e22b`> data: automatically create data/*/VERSION.json for latest • Additional commits viewable in <https://github.com/moment/moment-timezone/compare/0.5.34...0.5.37|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-site/network/alerts|Security Alerts page>.
:white_check_mark: All checks have passed
<https://github.com/cofacts/rumors-site/pull/503|#503 Bump moment-timezone from 0.5.34 to 0.5.37>
Bumps <https://github.com/moment/moment-timezone|moment-timezone> from 0.5.34 to 0.5.37. Changelog _Sourced from <https://github.com/moment/moment-timezone/blob/develop/changelog.md|moment-timezone's changelog>._ > *`0.5.37` _2022.08-25_* > > • Re-publish npm package, because of extra folder present in 0.5.36, check <https://github-redirect.dependabot.com/moment/moment-timezone/issues/999|moment/moment-timezone#999> > > *`0.5.36` _2022.08-25_* > > • IANA TZDB 2022c > • improvements/fixes to data pipeline > > *`0.5.35` _2022-08-23_* > > • Fix command injection in data pipeline <https://github.com/moment/moment-timezone/security/advisories/GHSA-56x4-j7p9-fcf9|GHSA-56x4-j7p9-fcf9> > • Fix cleartext transmission of sensitive information <https://github.com/moment/moment-timezone/security/advisories/GHSA-v78c-4p63-2j6c|GHSA-v78c-4p63-2j6c> > > Thanks to the OpenSSF Alpha-Omega project for reporting these! Commits • <https://github.com/moment/moment-timezone/commit/ffe6f340a6bdae6be1cbc1cbef4a4f2b87e2c63c|`ffe6f34`> Add changelog for 0.5.37 • <https://github.com/moment/moment-timezone/commit/450ca6304ba62baf27817ed7840828eee4e3b0c5|`450ca63`> Bump version to 0.5.37 • <https://github.com/moment/moment-timezone/commit/95f1a9b5cd3a15b8c75bd36029152ff1b43a5136|`95f1a9b`> Build moment-timezone 0.5.36 • <https://github.com/moment/moment-timezone/commit/abba28c7b0e1faf7df8592806007fcb2753b3078|`abba28c`> Add changelog for 0.5.36 • <https://github.com/moment/moment-timezone/commit/ac6de03cf34610068185961613d719bc050c7d2b|`ac6de03`> Bump version to 0.5.36 • <https://github.com/moment/moment-timezone/commit/7a5cadf9cbece0a9c7b9da0ee244c21375eb33a6|`7a5cadf`> tests: Fix country tests for 2022c • <https://github.com/moment/moment-timezone/commit/6754c75f5be4fbb16e90e336c9decbad6b506388|`6754c75`> data: generate 2022c data+tests • <https://github.com/moment/moment-timezone/commit/f74a364b1aac2c96cedd0a8cf5c7188268b9bcde|`f74a364`> bugfix: Wipe tests/zones before generation • <https://github.com/moment/moment-timezone/commit/e850f9fa6d3b440c51ae0cda7d9d573627839167|`e850f9f`> grunt: do not bundle zone and contry tests • <https://github.com/moment/moment-timezone/commit/f13e22b069f9115eddad5294a4c0f5335c61590a|`f13e22b`> data: automatically create data/*/VERSION.json for latest • Additional commits viewable in <https://github.com/moment/moment-timezone/compare/0.5.34...0.5.37|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-site/network/alerts|Security Alerts page>.
<https://coveralls.io/builds/52086675|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/a7979545bd4390da5f72758c3832f864399996b3|a797954> on dependabot/npm_and_yarn/moment-timezone-0.5.37* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.
<https://coveralls.io/builds/52086675|Coverage Status> Coverage remained the same at 75.831% when pulling *<https://github.com/cofacts/rumors-site/commit/a7979545bd4390da5f72758c3832f864399996b3|a797954> on dependabot/npm_and_yarn/moment-timezone-0.5.37* into *<https://github.com/cofacts/rumors-site/commit/32f1d6c8ca266420122f7c7392ced6f859dc8a15|32f1d6c> on master*.
g0v.hackmd.io
Article detail with transcript support here: <https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923|https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923>
Article detail with transcript support here: <https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923|https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-LIFF-and-new-designs?node-id=4514%3A923>