cofacts

#216 API can determine its concurrency using WEB_CONCURRENCY env var

*As-is* PM2 always spins up 2 instances of rumors-api *To-be* PM2 will respect `WEB_CONCURRENCY` env var to determine its concurrency. This can be helpful if we want to scale up / down API servers on production server.

Comment on #216 API can determine its concurrency using WEB_CONCURRENCY env var

<https://coveralls.io/builds/33134389|Coverage Status> Coverage remained the same at 88.582% when pulling *<https://github.com/cofacts/rumors-api/commit/784d6dcc70a4ed08f11c0f533a211c48163ec004|784d6dc> on web-concurrency* into *<https://github.com/cofacts/rumors-api/commit/a9a68b9d1d5a3b75a32b021c8b799dd58c1fb01c|a9a68b9> on master*.

image.png

台灣事實查核中心

台灣事實查核發展大躍進！ AI不實訊息快篩平台上線

記者何蕙安／報導

image.png

Comment on #213 Feature highlight searched text

I have some problem in highlighting hyperlink, details updated in the PR description.

g0v.hackmd.io

20200831 release thrashing issue - HackMD

Comment on #315 Initial implementation of LineChart

Actually I am not sure if `test()` is called first, or if `MockDate.reset()` is called first. Depends on how `initStoryshots` calls `test()`. Judging from `Info`'s snapshot change (`over 30 years` -&gt; `about 31 years`) I suspect that the mock is not in effect.

Review on #315 Initial implementation of LineChart

Comment on #315 Initial implementation of LineChart

you're right, I didn't think it through lol I've modified the test accordingly.

Comment on #315 Initial implementation of LineChart

This can be omitted because of the existence of `position: absolute`

Comment on #315 Initial implementation of LineChart

<https://user-images.githubusercontent.com/1817638/91658891-a344a880-eafe-11ea-9526-dc81860cb3ce.png|Screen Shot 2020-08-30 at 8 18 31 PM> <https://user-images.githubusercontent.com/1817638/91658894-a50e6c00-eafe-11ea-83d2-d158a22bf5be.png|Screen Shot 2020-08-30 at 8 18 52 PM> <https://user-images.githubusercontent.com/1817638/91658892-a475d580-eafe-11ea-9811-d21892d15af3.png|Screen Shot 2020-08-30 at 8 18 43 PM> <https://user-images.githubusercontent.com/1817638/91658895-a5a70280-eafe-11ea-8a23-e3cd296bfe4d.png|Screen Shot 2020-08-30 at 8 21 08 PM>

Comment on #315 Initial implementation of LineChart

Seems that `15` is the only place that implies `dataset` length in this component. How about using `dataset.length / 2` here?

Comment on #315 Initial implementation of LineChart

If we use absolute positioning for tooltip as well, we can use `left` or `right` to position `.tooltip.left` and `.tooltip.right` as well. In this way both `.tooltip.left` and `.tooltip.right` do not need to rely on actual tooltip width / height.

Comment on #315 Initial implementation of LineChart

Since `totalWebVisits` is not storing JSX elements, we can directly use <https://ttag.js.org/docs/tag-gettext.html|`t`> here, instead of <https://ttag.js.org/docs/jsx-gettext.html|`jt`>. The same goes to occurrences of `jt` below.

Comment on #315 Initial implementation of LineChart

Since we may change tooltip content in the future and its size may vary in different languages, I think we can should avoid fixed width / height here and rely on its content's size. We can add paddings to further adjust space around the text.

Comment on #315 Initial implementation of LineChart

It's pretty rare to see line-height smaller than font size :thinking_face: What would happen if we remove this line and let it inherit from `.tooltip` ?

Review on #315 Initial implementation of LineChart

The chart is looking pretty good! I have added some comments regarding some details of CSS and i18n.

Comment on #315 Initial implementation of LineChart

We can use <https://ttag.js.org/docs/ngettext.html|ngettext> to handle plural form. ``` c('LineChart').ngettext(msgid`${num} time`, `${num} times`, num) ```

Figma

[Wireframe] Pages

Created with Figma

#13 Bump googleapis from 32.0.0 to 39.1.0

Bumps <https://github.com/googleapis/google-api-nodejs-client|googleapis> from 32.0.0 to 39.1.0. Release notes _Sourced from <https://github.com/googleapis/google-api-nodejs-client/releases|googleapis's releases>._ &gt; *v39.1.0* &gt; &gt; 03-28-2019 16:17 PDT &gt; &gt; *This release has security fixes.*. Versions 36.0.0 =&gt; 39.0.0 have a potential <https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1594|vulnerability> where the scope of auth objects may be shared across different clients. This was addressed in <https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1660|#1660>, and is part of this minor release. All clients should be updated to the latest version. &gt; &gt; *Bug Fixes* &gt; &gt; • fix: move context from namespace to class scope (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1660|#1660>) &gt; &gt; *New Features* &gt; &gt; • feat: run the generator (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1659|#1659>) &gt; &gt; *Internal / Testing Changes* &gt; &gt; • fix: README should not be generated (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1657|#1657>) &gt; &gt; *v39.0.0* &gt; &gt; 03-26-2019 22:05 PDT &gt; &gt; *This release had breaking changes*. There have been a variety of TypeScript type changes. There have also been a variety of changes to the Google Plus API, and the OAuth2 API. Please take care! &gt; &gt; There are also some sweet new APIs: &gt; &gt; • cloudasset_v1 &gt; • cloudtasks_v2 &gt; • factchecktools_v1alpha1 &gt; • servicenetworking_v1 &gt; • websecurityscanner_v1beta &gt; &gt; *New Features* &gt; &gt; • feat: run the generator (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1653|#1653>) &gt; • feat: run the generator (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1644|#1644>) &gt; &gt; *Documentation* &gt; &gt; • docs: remove the plus samples (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1654|#1654>) &gt; • docs: Update typo in README.md (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1640|#1640>) &gt; • docs: fix typos in README files (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1642|#1642>) &gt; &gt; *Internal / Testing Changes* &gt; &gt; • chore(deps): update dependency tmp to ^0.1.0 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1652|#1652>) &gt; • chore: publish to npm using wombat (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1645|#1645>) &gt; • build: update npm token (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1641|#1641>) &gt; • chore(deps): update dependency hard-rejection to v2 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1643|#1643>) &gt; • build: use per-repo publish token (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1638|#1638>) &gt; &gt; *v38.0.0* &gt; &gt; 03-12-2019 14:00 PDT &gt; &gt; Greetings y'all! This release has some new APIs, says goodbye to a few older ones, and fixes a bunch of doc issues. Enjoy! &gt; &gt; _BREAKING CHANGES_: The following APIs have been _deleted_: &gt; &gt; • appengine_v1beta4 &gt; • appengine_v1beta5 Changelog _Sourced from <https://github.com/googleapis/google-api-nodejs-client/blob/master/CHANGELOG.md|googleapis's changelog>._ &gt; *v39.1.0* &gt; &gt; 03-28-2019 16:17 PDT &gt; &gt; *This release has security fixes.*. Versions 36.0.0 =&gt; 39.0.0 have a potential <https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1594|vulnerability> where the scope of auth objects may be shared across different clients. This was addressed in <https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1660|#1660>, and is part of this minor release. All clients should be updated to the latest version. &gt; &gt; *Bug Fixes* &gt; &gt; • fix: move context from namespace to class scope (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1660|#1660>) &gt; &gt; *New Features* &gt; &gt; • feat: run the generator (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1659|#1659>) &gt; &gt; *Internal / Testing Changes* &gt; &gt; • fix: README should not be generated (<https://github-redirect.dependabot.com/google/google-api-nodejs-client/pull/1657|#1657>) &gt; &gt; *v39.0.0* &gt; &gt; 03-26-2019 22:05 PDT &gt; &gt; *This release had breaking changes*. There have been a variety of TypeScript type changes. There have also been a variety of changes to the Google Plus API, and the OAuth2 API. Please take care! &gt; &gt; There are also some sweet new APIs: &gt; &gt; • cloudasset_v1 &gt; • cloudtasks_v2 &gt; • factchecktools_v1alpha1 &gt; • servicenetworking_v1 &gt; • websecurityscanner_v1beta &gt; &gt; *New Features* &gt; &gt; • feat: run the generator (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1653|#1653>) &gt; • feat: run the generator (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1644|#1644>) &gt; &gt; *Documentation* &gt; &gt; • docs: remove the plus samples (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1654|#1654>) &gt; • docs: Update typo in README.md (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1640|#1640>) &gt; • docs: fix typos in README files (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1642|#1642>) &gt; &gt; *Internal / Testing Changes* &gt; &gt; • chore(deps): update dependency tmp to ^0.1.0 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1652|#1652>) &gt; • chore: publish to npm using wombat (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1645|#1645>) &gt; • build: update npm token (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1641|#1641>) &gt; • chore(deps): update dependency hard-rejection to v2 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1643|#1643>) &gt; • build: use per-repo publish token (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/pull/1638|#1638>) &gt; &gt; *v38.0.0* &gt; &gt; 03-12-2019 14:00 PDT &gt; &gt; Greetings y'all! This release has some new APIs, says goodbye to a few older ones, and fixes a bunch of doc issues. Enjoy! Commits • <https://github.com/googleapis/google-api-nodejs-client/commit/f29dfd0495eb6b940f27eb3d043278cb756d2ceb|`f29dfd0`> Release v39.1.0 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1661|#1661>) • <https://github.com/googleapis/google-api-nodejs-client/commit/db5e0f25c64db76cb87c96b9515205b79e7e775e|`db5e0f2`> fix: move context from namespace to class scope (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1660|#1660>) • <https://github.com/googleapis/google-api-nodejs-client/commit/73eab9b6f20c1fba536b9ab2917eb56822d212b6|`73eab9b`> feat: run the generator (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1659|#1659>) • <https://github.com/googleapis/google-api-nodejs-client/commit/d69c92070e83ffb74550bd37f1c939b428c74ee1|`d69c920`> fix: README should not be generated (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1657|#1657>) • <https://github.com/googleapis/google-api-nodejs-client/commit/32279b5f6c89dd383146b0a9c9671cc4a26374be|`32279b5`> Release v39.0.0 (<https://github-redirect.dependabot.com/googleapis/google-api-nodejs-client/issues/1655|#1655>) • <https://github.com/googleapis/google-api-nodejs-…

#6 Prepare task (testdata) for new model

#7 Containerize BERT model

#8 Containerize BoW model

#4 Model API v1

#5 Task API v1

#9 README refinement

*To be added* • environment variables • Deployment guide

#327 Rollback apollo-client to 2.X

As discussed in <https://g0v.hackmd.io/c5wpuEPaQLWwM_5vxuo_Yw?both#-Released-to-production|meeting> we are rolling back apollo-client to 2.X to fix SSR thrashing issue.

dev.cofacts.org

Cofacts - Connecting facts and instant messages

Cofacts is a collaborative system connecting instant messages and fact-check reports or different opinions together. It’s a grass-root effort fighting mis/disinformation in Taiwan.

g0v.hackmd.io

20200826 會議記錄 - HackMD

#1 Post tags json data to AI API can not get correct response

#327 Rollback apollo-client to 2.X

#14 Bump lodash.merge from 4.6.1 to 4.6.2

Bumps <https://github.com/lodash/lodash|lodash.merge> from 4.6.1 to 4.6.2. Commits • See full diff in <https://github.com/lodash/lodash/commits|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|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>.

#2 Add 0904 incident

Review on #2 Add 0904 incident

#2 Add 0904 incident

#319 Articlereplyfeedbacks

#15 Bump handlebars from 4.5.1 to 4.7.6

Bumps <https://github.com/wycats/handlebars.js|handlebars> from 4.5.1 to 4.7.6. Changelog _Sourced from <https://github.com/handlebars-lang/handlebars.js/blob/master/release-notes.md|handlebars's changelog>._ &gt; *v4.7.6 - April 3rd, 2020* &gt; &gt; Chore/Housekeeping: &gt; &gt; • <https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1672|#1672> - Switch cmd parser to latest minimist (<https://api.github.com/users/dougwilson|@dougwilson> &gt; &gt; Compatibility notes: &gt; &gt; • Restored Node.js compatibility &gt; &gt; <https://github.com/wycats/handlebars.js/compare/v4.7.5...v4.7.6|Commits> &gt; &gt; *v4.7.5 - April 2nd, 2020* &gt; &gt; Chore/Housekeeping: &gt; &gt; • ~Node.js version support has been changed to v6+~ Reverted in 4.7.6 &gt; &gt; Compatibility notes: &gt; &gt; • ~Node.js &lt; v6 is no longer supported~ Reverted in 4.7.6 &gt; &gt; <https://github.com/wycats/handlebars.js/compare/v4.7.4...v4.7.5|Commits> &gt; &gt; *v4.7.4 - April 1st, 2020* &gt; &gt; Chore/Housekeeping: &gt; &gt; • <https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1666|#1666> - Replaced minimist with yargs for handlebars CLI (<https://api.github.com/users/aorinevo|@aorinevo>, <https://api.github.com/users/AviVahl|@AviVahl> &amp; <https://api.github.com/users/fabb|@fabb>) &gt; &gt; Compatibility notes: &gt; &gt; • No incompatibilities are to be expected &gt; &gt; <https://github.com/wycats/handlebars.js/compare/v4.7.3...v4.7.4|Commits> &gt; &gt; *v4.7.3 - February 5th, 2020* &gt; &gt; Chore/Housekeeping: &gt; &gt; • <https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1644|#1644> - Download links to aws broken on <http://handlebarsjs.com|handlebarsjs.com> - access denied (<https://api.github.com/users/Tea56|@Tea56>) &gt; • Fix spelling and punctuation in changelog - d78cc73 &gt; &gt; Bugfixes: &gt; &gt; • Add Type Definition for Handlebars.VERSION, Fixes <https://github-redirect.dependabot.com/wycats/handlebars.js/issues/1647|#1647> - 4de51fe &gt; • Include Type Definition for runtime.js in Package - a32d05f &gt; &gt; Compatibility notes: Commits • <https://github.com/handlebars-lang/handlebars.js/commit/e6ad93ea01bcde1f8ddaa4b4ebe572dd616abfaa|`e6ad93e`> v4.7.6 • <https://github.com/handlebars-lang/handlebars.js/commit/2bf4fc6fd3ae3d8f076d628653f284d85faebeb4|`2bf4fc6`> Update release notes • <https://github.com/handlebars-lang/handlebars.js/commit/b64202bc9197307bd785a58693e3820eb9bb41a8|`b64202b`> Update release-notes.md • <https://github.com/handlebars-lang/handlebars.js/commit/c2f1e6203178918569f085e12afdb762cae17fb0|`c2f1e62`> Switch cmd parser to latest minimist • <https://github.com/handlebars-lang/handlebars.js/commit/08e9a11a34c3ad8387a0b85b1334f97cab85191a|`08e9a11`> Revert "chore: set Node.js compatibility to v6+" • <https://github.com/handlebars-lang/handlebars.js/commit/1fd2edee2a12fb228061fcde807905c6b14339c4|`1fd2ede`> v4.7.5 • <https://github.com/handlebars-lang/handlebars.js/commit/3c9c2f5cf29cf10f54d5fe4daca6b24b65f0adcf|`3c9c2f5`> Update release notes • <https://github.com/handlebars-lang/handlebars.js/commit/16487a088e13f4d52c6fd6610b9ec71c4a51be8a|`16487a0`> chore: downgrade yargs to v14 • <https://github.com/handlebars-lang/handlebars.js/commit/309d2b49a11628d2a8f052c5587e7459968cd705|`309d2b4`> chore: set Node.js compatibility to v6+ • <https://github.com/handlebars-lang/handlebars.js/commit/645ac73844918668f9a2f41e49b7cb18ce5abf36|`645ac73`> test: fix integration tests • Additional commits viewable in <https://github.com/wycats/handlebars.js/compare/v4.5.1...v4.7.6|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~erisds|erisds>, a new releaser for handlebars since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|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>.

Review on #319 Articlereplyfeedbacks

Comment on #315 Initial implementation of LineChart

`right: 40px` should have similar effect, but using `right` could have no dependency on tooltip actual width.

Review on #315 Initial implementation of LineChart

I found that currently the red cursor will not align with the x-axis: <https://user-images.githubusercontent.com/108608/92321119-fcaa5b80-f059-11ea-90b8-cd01cef9806c.png|image> To make them aligned, there should be 11 x-axis ticks for 31 days. For example, for 9/6 the ticks should be: &gt; 8/7 8/10 8/13 8/16 8/19 8/22 8/25 8/28 8/31 9/3 9/6

Review on #213 Feature highlight searched text

LGTM overall, thanks for adding highlight function that we long wanted!

Comment on #213 Feature highlight searched text

This makes me notice that we <https://github.com/cofacts/rumors-db/blob/master/schema/replies.js#L8|forgot to use `cjk_url_email` analyzer> for `reference` field...... This is a bug that will affect reply search. I am adding a ticket for this.

Comment on #213 Feature highlight searched text

What would happen if we use the original setup?

#46 Reply reference field should use cjk_url_email analyzer

Current setting will mess up with reply search functionality. Modifying analyzer will need reindexing.

Comment on #213 Feature highlight searched text

Let's see the test case `ListReplies filters by moreLikeThis and given text, find replies with the said URL's content`: The original fixture `moreLikeThis2`(reference:barbar) should match, but it only matches `userFoo` and `rumor`.

Review on #216 API can determine its concurrency using WEB_CONCURRENCY env var

LGTM!

#288 Replace &lt;ArticleItem&gt; with more reusable card components

#216 API can determine its concurrency using WEB_CONCURRENCY env var

Comment on #315 Initial implementation of LineChart

Recently I have rolled back apollo client to version 2. Please also rebase the PR and change apollo-client 3 dependencies accordingly. More specifically, • `import { gql } from '@apollo/client'` should be `import gql from 'graphql-tag'` • `import { useQuery } from '@apollo/client'` should be `import { useQuery } from '@apollo/react-hooks'`

Screenshot_20200907-140548.png

Comment on #315 Initial implementation of LineChart

What does this `-0` for?

Review on #315 Initial implementation of LineChart

LGTM now :) Thanks for the fix and let's <https://github.githubassets.com/images/icons/emoji/shipit.png|:shipit:>

Comment on #213 Feature highlight searched text

I see, very interesting. Seems that using `fields: ['text', 'reference']` would concat the two field into one, which may cause `not being selected as representative terms [in` more_like_this` process](<https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-mlt-query.html#_how_it_works|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-mlt-query.html#_how_it_works>). Splitting into separate more_like_this should indeed fix this.

#51 Show related paragraphs in search result, instead of the first paragraphs

#213 Feature highlight searched text

#288 Replace &lt;ArticleItem&gt; with more reusable card components

List items part of the 2nd planned PR for <https://g0v.hackmd.io/h8rP0TOGTh2Clxi_Oi_QKw?view|`ArticleListPage` component revamp> <https://github.com/cofacts/rumors-site/issues/286|#286> . Originally, `&lt;ArticleItem&gt;` component is shared across all list pages including `/articles` , `/hoax-for-you`, `/replies` and `/search`; however, in each of these lists, the item looks different in mockup (see below). Original implementation adds a lot of props to `&lt;ArticleItem&gt;` and is not accurately reflecting to all these different visuals. This PR replaces monolithic `&lt;ArticleItem&gt;` with atomic, reusable components of these components. *Spec in Figma* *In <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=428%3A37|`/articles`>, <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=428%3A37|`/hoax-for-you`> and <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=585%3A273|searching articles in `/search`>* <https://user-images.githubusercontent.com/108608/92329007-38afe180-f097-11ea-81f4-8367c7a850e4.png|image> *In <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=79%3A9|`/replies`>* <https://user-images.githubusercontent.com/108608/92329021-511ffc00-f097-11ea-8068-fb13aa4c409c.png|image> *<https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=432%3A2727|Searching replies in `/replies`>* <https://user-images.githubusercontent.com/108608/92329078-bd9afb00-f097-11ea-9580-a567d1b11b68.png|image> *<https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=585%3A524|The "articles also used this reply" dialog>* <https://user-images.githubusercontent.com/108608/92329092-cbe91700-f097-11ea-9b62-a6317d47879b.png|image> *Refactor* • decompose `components/ListPageDisplays/ArticleItem` into `ListPageCards`, `ListPageCard` and original `ReplyItem` • `ListPageCards`: the list container for all card items • `ListPageCard`: basic card look, with RWD paddings matching the mockup <https://user-images.githubusercontent.com/108608/92329404-dc01f600-f099-11ea-89b0-10cf0d97ec75.png|image> • `ArticleCard`: the article card shared across `/articles`, `/hoax-for-you` and `/search`, built upon `ListPageCard` <https://user-images.githubusercontent.com/108608/92329418-ef14c600-f099-11ea-83df-2f06fb875a88.png|image> • `ReplyItem`: article reply item within each article card in `/replies` page. This component already exists, but its props are simplified in this PR. <https://user-images.githubusercontent.com/108608/92329441-0ce22b00-f09a-11ea-89cf-621c42f7d041.png|image> • adding `page` prop to `ArticlePageLayout` • The ultimate goal is to split `ArticlePageLayout` into each page components like `/articles`, `/hoax-for-you` and `/search` • However, this PR has already collected too much changes, removing `ArticlePageLayout` in this PR will be very difficult to review. • Therefore I added `page` prop to differentiate pages in `ArticlePageLayout`. This will help us splitting logic into respective pages in the future PR. • Introduce `&lt;ReplyCountInfo&gt;` for reply info with reply stats • It's only used in 2 places. However its calculation is a bit complicated, thus we are turning it into a component. *Others* • Lists 25 items per page (fixes <https://github.com/cofacts/rumors-site/issues/307|#307>)

g0v.hackmd.io

20200909 會議記錄 - HackMD

Comment on #315 Initial implementation of LineChart

`tick` could be a `number` or a `date`, `-0` remains the same if it's a number and converts `date` into epoch seconds otherwise. it's not necessary, just makes the `key` look cleaner

#314 implement line chart for Google analytics stats on Article page

#315 Initial implementation of LineChart

Comment on #315 Initial implementation of LineChart

I see. We could use <https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Unary_plus|unary `+`> to convert things to number, it's shorter ;)

#47 update analytics and users' schema &amp; write a migration to update mappings

Comment on #47 update analytics and users' schema &amp; write a migration to update mappings

<https://github.com/cofacts/rumors-api/issues/185|cofacts/rumors-api#185>

Comment on #47 update analytics and users' schema &amp; write a migration to update mappings

I think we can use `keyword`. 1. Previously we use `keyword` to store `url`: <https://github.com/cofacts/rumors-db/blob/master/schema/urls.js#L3|https://github.com/cofacts/rumors-db/blob/master/schema/urls.js#L3> 2. For longer data, we still use `keyword` but add `doc_values: false` also. <https://github.com/cofacts/rumors-db/blob/master/schema/urls.js#L11|https://github.com/cofacts/rumors-db/blob/master/schema/urls.js#L11>

Review on #47 update analytics and users' schema &amp; write a migration to update mappings

cofacts/opendata

Open data of Cofacts collaborative fact-checking database

#217 Ask user to turn on notification after submission

In <https://g0v.hackmd.io/eitM7s0bSSeS3kg-MAcpDw#20200812-%E6%9C%83%E8%AD%B0%E8%A8%98%E9%8C%84|20200812 meeting note>: &gt; 如果預設都關閉，我們都準備好之後再發個推播說有這個選項可以設定 &gt; 想說預設開啟的話，使用者可能會不知道如何關閉，就把我們封鎖了 &gt; [name=mrorz] &gt; 商業產品的話我會考慮預設開啟，但調整推播頻率 &gt; 我們這裡可以預設關閉，然後如果使用者送新訊息進來後，沒有得到回應，使用者又沒有開啟推播的話，可以多問一句要不要開啟 &gt; [name=lucien] Therefore we can • add a sentence after they successfully send a message asking the user to turn on notification if their notification setting is off. • If their notification setting is turned on, also states that they will receive notification after the message being replied.

#218 Feature highlight searched text

Highlight searched text using <https://github.com/cofacts/rumors-api/pull/213|cofacts/rumors-api#213> *Need to discuss* Highlight hyperlink.title and hyperlink.summary or not? Currently line bot doesn't show hyperlink.title and hyperlink.summary, but search-API may highlight them and return a null text field if the original message is a URL.

Comment on #218 Feature highlight searched text

若為 hyperlink.summary，一樣顯示 summary 的 highlight，但前面用稍小的灰字加上： `(Words found in the hyperlink)` 或 `（網址裡找到的字）` <https://user-images.githubusercontent.com/108608/92607845-422f8880-f2e7-11ea-91ee-a5983071da8e.png|image> Color palatte: <https://www.figma.com/file/Xr80rEWwCrNks1uFIrGCG4/Cofacts-Colors?node-id=22%3A76|https://www.figma.com/file/Xr80rEWwCrNks1uFIrGCG4/Cofacts-Colors?node-id=22%3A76>

#211 Entering article page from article list takes 2 back to go back to list page

Comment on #211 Entering article page from article list takes 2 back to go back to list page

Confirmed that it's fixed via <https://github.com/cofacts/rumors-site/issues/314|#314>.

Image from iOS

image.png

Comment on #218 Feature highlight searched text

*Pull Request Test Coverage Report for <https://coveralls.io/builds/33357881|Build 1109>* • *27* of *27* *(100.0%)* changed or added relevant lines in *1* file are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.6%*) to *84.691%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

#16 Bump node-fetch from 2.2.0 to 2.6.1

Bumps <https://github.com/bitinn/node-fetch|node-fetch> from 2.2.0 to 2.6.1. Release notes _Sourced from <https://github.com/bitinn/node-fetch/releases|node-fetch's releases>._ &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; See <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261|CHANGELOG> for details. &gt; &gt; *v2.6.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.6.0/CHANGELOG.md#v260|CHANGELOG>. &gt; &gt; *v2.5.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.5.0/CHANGELOG.md#v250|CHANGELOG>. &gt; &gt; *v2.4.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.1/CHANGELOG.md#v241|CHANGELOG>. &gt; &gt; *v2.4.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.4.0/CHANGELOG.md#v240|CHANGELOG>. &gt; &gt; *v2.3.0* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.3.0/CHANGELOG.md#v230|CHANGELOG>. &gt; &gt; *v2.2.1* &gt; &gt; See <https://github.com/bitinn/node-fetch/blob/v2.2.1/CHANGELOG.md#v221|CHANGELOG>. Changelog _Sourced from <https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md|node-fetch's changelog>._ &gt; *v2.6.1* &gt; &gt; *This is an important security release. It is strongly recommended to update as soon as possible.* &gt; &gt; • Fix: honor the `size` option after following a redirect. &gt; &gt; *v2.6.0* &gt; &gt; • Enhance: `options.agent`, it now accepts a function that returns custom http(s).Agent instance based on current URL, see readme for more information. &gt; • Fix: incorrect `Content-Length` was returned for stream body in 2.5.0 release; note that `node-fetch` doesn't calculate content length for stream body. &gt; • Fix: `Response.url` should return empty string instead of `null` by default. &gt; &gt; *v2.5.0* &gt; &gt; • Enhance: `Response` object now includes `redirected` property. &gt; • Enhance: `fetch()` now accepts third-party `Blob` implementation as body. &gt; • Other: disable `package-lock.json` generation as we never commit them. &gt; • Other: dev dependency update. &gt; • Other: readme update. &gt; &gt; *v2.4.1* &gt; &gt; • Fix: `Blob` import rule for node &lt; 10, as `Readable` isn't a named export. &gt; &gt; *v2.4.0* &gt; &gt; • Enhance: added `Brotli` compression support (using node's zlib). &gt; • Enhance: updated `Blob` implementation per spec. &gt; • Fix: set content type automatically for `URLSearchParams`. &gt; • Fix: `Headers` now reject empty header names. &gt; • Fix: test cases, as node 12+ no longer accepts invalid header response. &gt; &gt; *v2.3.0* &gt; &gt; • Enhance: added `AbortSignal` support, with README example. &gt; • Enhance: handle invalid `Location` header during redirect by rejecting them explicitly with `FetchError`. &gt; • Fix: update `browser.js` to support react-native environment, where `self` isn't available globally. &gt; &gt; *v2.2.1* &gt; &gt; • Fix: `compress` flag shouldn't overwrite existing `Accept-Encoding` header. &gt; • Fix: multiple `import` rules, where `PassThrough` etc. doesn't have a named export when using node &lt;10 and `--experimental-modules` flag. &gt; • Other: Better README. Commits • <https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab|`b5e2e41`> update version number • <https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334|`2358a6c`> Honor the `size` option after following a redirect and revert data uri support • <https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4|`8c197f8`> docs: Fix typos and grammatical errors in README.md (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686|#686>) • <https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a|`1e99050`> fix: Change error message thrown with redirect mode set to error (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653|#653>) • <https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b|`244e6f6`> docs: Show backers in README • <https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16|`6a5d192`> fix: Properly parse meta tag when parameters are reversed (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682|#682>) • <https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91|`47a24a0`> chore: Add opencollective badge • <https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1|`7b13662`> chore: Add funding link • <https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f|`5535c2e`> fix: Check for global.fetch before binding it (<https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674|#674>) • <https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22|`1d5778a`> docs: Add Discord badge • Additional commits viewable in <https://github.com/bitinn/node-fetch/compare/v2.2.0...v2.6.1|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~akepinski|akepinski>, a new releaser for node-fetch since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates|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>.

#328 Layout components for header

• Adjust page header's margins and font size so that it matches <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=79%3A9|the design> • `&lt;Tools&gt;` • hosts controls like `TimeRange` and `SortInput` • in mobile, all controls are stacked and have the same width • on desktop, all controls are laid out horizontally • `&lt;ListPageHeader&gt;` • layout title text and other items horizontally • adjust font size on mobile and desktop • Adjustments are made to `BaseTimeRange` and `BaseSortInput` so that they have same size and relax their width to work with `&lt;Tools&gt;` *Screenshots* *mobile* <https://user-images.githubusercontent.com/108608/92987245-521bb800-f4f3-11ea-8303-293356d23ba0.png|image> *Desktop* <https://user-images.githubusercontent.com/108608/92987274-a161e880-f4f3-11ea-8f33-fc829af4daaf.png|image> *`BaseTimeRange` and `BaseSortInput`* Their width are now controlled by its container, thus shows 100% width in storybook <https://user-images.githubusercontent.com/108608/92987412-b5f2b080-f4f4-11ea-908f-a8aad700dabd.png|image> <https://user-images.githubusercontent.com/108608/92987429-d1f65200-f4f4-11ea-8204-4470e4d4dfbc.png|image>

Comment on #328 Layout components for header

Desktop safari 上看起來超母湯 <https://user-images.githubusercontent.com/108608/92987550-fbfc4400-f4f5-11ea-8781-bd003d72f402.png|image> 但 iOS safari 好像還好 <https://user-images.githubusercontent.com/108608/92987540-e7b84700-f4f5-11ea-9be8-93bb16a54b71.jpeg|IMG_C3809E0AD43B-1>

#3 Add 0912 complaint

Review on #3 Add 0912 complaint

Review on #3 Add 0912 complaint

Review on #328 Layout components for header

#3 Add 0912 complaint

Review on #218 Feature highlight searched text

g0v.hackmd.io

[Spec] 可疑轉傳訊息 - HackMD

#217 Interface for connection related types

• Create `Node`, `Edge`, `PageInfo` and `Connection` interfaces and have similar object types inherit from them. • This helps components like `&lt;LoadMore&gt;` in rumors-site to create object-agnostic fragments that only retrieves common fields • Also defines more strict `NonNull` and `ID` so that their type is more rigorous. • When `resolveEdge` errors, the whole request (like `ListArticle`) would return `null` now, rather than return partially in the past. This makes more sense in terms of param error. • Upgrade graphql-js to get better error message regarding interfaces. see <https://github.com/graphql/graphql-js/pull/2513|graphql/graphql-js#2513>

Comment on #217 Interface for connection related types

<https://coveralls.io/builds/33419451|Coverage Status> Coverage increased (+0.04%) to 88.706% when pulling *<https://github.com/cofacts/rumors-api/commit/c12f235dce9715d1fab4b3df5300feab164748f9|c12f235> on interfaces-non-null* into *<https://github.com/cofacts/rumors-api/commit/869bfcb4f24791793781f9a89d546d830e614fad|869bfcb> on master*.

components/ListPageControls/LoadMore.js:77

``` fragment LoadMoreEdge on Edge { ```

#218 ListArticles categoryId filter fix

Currently `ListArticles(filter: {categoryId: [XXX]})` will include articles that has `XXX` even if • `XXX` has been deleted from the article, or • `XXX` receives more negative feedback than positive. This PR fixes the above scenario to make sure only `articleCategories` that is not deleted yet and has positive (or neutral) feedback are considered.

Comment on #218 ListArticles categoryId filter fix

<https://coveralls.io/builds/33420793|Coverage Status> Coverage remained the same at 88.666% when pulling *<https://github.com/cofacts/rumors-api/commit/952c06f2d7540eb7c17faf856037e497147d9ce8|952c06f> on fix-category-id-filter* into *<https://github.com/cofacts/rumors-api/commit/869bfcb4f24791793781f9a89d546d830e614fad|869bfcb> on master*.

#329 Show loading progress bar when apollo client is fetching query

Currently when changing filters, there is no loading state in UI. We would like `AppLayout` to show progress whenever apollo-client has pending network requests. This should be doable via this apollo-client link: <https://github.com/molindo/react-apollo-network-status|https://github.com/molindo/react-apollo-network-status>

#330 Remove ArticlePageLayout from /articles, /hoax-for-you and /replies

• `ListPageControls` • index • values • `LoadMore` fragments • `ListPageDisplays` • index • `/pages/articles`, `/pages/hoax-for-you` • `/pages/replies`

#331 Search page

This PR fixes <https://github.com/cofacts/rumors-site/issues/286|#286> . • Removes `ArticlePageLayout` and `ReplySearchPageLayout` completely -- This marks the end of article page refactor!! • `AppLayout` container boolean prop • `SearchPageJumbotron` • `/pages/search`

#291 Feedbacks from LINE bot is not shown in "show more" button dialog

#319 Reasons dialog in &lt;ArticleReplyFeedbacks&gt; component

#330 Remove ArticlePageLayout from /articles, /hoax-for-you and /replies

Review on #330 Remove ArticlePageLayout from /articles, /hoax-for-you and /replies

#331 Remove ArticlePageLayout from search page

#321 Track rss, and add utm_source to each url that generated from feed.js

Review on #331 Remove ArticlePageLayout from search page

#332 UI/UX enhancement for GA charts

• show unique users instead of numbers of visits (or add a toggle to switch datasets?) • enhance legends on smaller screens <https://g0v-tw.slack.com/archives/C2PPMRQGP/p1599708004074400|https://g0v-tw.slack.com/archives/C2PPMRQGP/p1599708004074400>

#166 Implement Google analytics stats field in Article

Comment on #166 Implement Google analytics stats field in Article

closing this issue as the feature is completed additional UI/UX enhancement will be tracked here: <https://github.com/cofacts/rumors-site/issues/332|cofacts/rumors-site#332>

#48 update db schemas to reflect the new user model

update schema files and write a migration script to update existing mappings in db

#49 create users from existing entities

☐ design collision handling? ☐ fetch all entities with `userId` and `appId` (`articles`, `replyrequests`, `articlereplyfeedbacks`, etc...) and create users for each unique (`appId`, `userId`) pair, where the new user id is `appId_sha(userId)` ☐ update `userId` for entities mentioned above ☐ `analytics` only has `docUserId` and no `appId`, need to refetch all data from `replies` ☐ unit tests

#219 implement name/avatar generator

<https://g0v.hackmd.io/7ERem43XREWJPOjjdE28SQ?view|https://g0v.hackmd.io/7ERem43XREWJPOjjdE28SQ?view> • use PlatoForum's <https://github.com/PlatoForum/PlatoForum/tree/2cdc807a6ec54f68e0479787ccb865f0e89aed50/utils/pseudonym_gen|pseudonym_gen> to generate names • use <https://github.com/CeamKrier/react-peeps|Open Peeps> for avatar generation • storing `props` as a json blob • should use non-uniform distribution for some fields (i.e. `none` should have higher probability of occurrence than any other glasses/facial hair styles)

#220 ad hoc backend user creation

when resolving `user` with `appId` and `userId`, aka backend user: 1. do a term query on `appId` and `appUserId` (could also query on id to be `appId_sha(userId)` but there might be collision) 2. if the user doesn't exist, create a new user with `id` being `appId_sha(userId)`[iii] and randomly generated name and avatar. 3. in case of collision, generate another id somehow (collision prevention mechanism TBD, should be the same as <https://github.com/cofacts/rumors-db/issues/49|cofacts/rumors-db#49>) unit tests

Review on #218 Feature highlight searched text

LGTM! I can't wait seeing this working on staging and production :rocket:

#218 Feature highlight searched text

#221 remove unused utils

Comment on #221 remove unused utils

<https://coveralls.io/builds/33451597|Coverage Status> Coverage decreased (-0.3%) to 88.379% when pulling *<https://github.com/cofacts/rumors-api/commit/e08f1d125959c80c7b4783d0cbe5074766a5aa48|e08f1d1> on cleanup* into *<https://github.com/cofacts/rumors-api/commit/869bfcb4f24791793781f9a89d546d830e614fad|869bfcb> on master*.

#288 Replace &lt;ArticleItem&gt; with more reusable card components

List items part of the 2nd planned PR for <https://g0v.hackmd.io/h8rP0TOGTh2Clxi_Oi_QKw?view|`ArticleListPage` component revamp> <https://github.com/cofacts/rumors-site/issues/286|#286> . Originally, `&lt;ArticleItem&gt;` component is shared across all list pages including `/articles` , `/hoax-for-you`, `/replies` and `/search`; however, in each of these lists, the item looks different in mockup (see below). Original implementation adds a lot of props to `&lt;ArticleItem&gt;` and is not accurately reflecting to all these different visuals. This PR replaces monolithic `&lt;ArticleItem&gt;` with atomic, reusable components of these components. *Spec in Figma* *In <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=428%3A37|`/articles`>, <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=428%3A37|`/hoax-for-you`> and <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=585%3A273|searching articles in `/search`>* <https://user-images.githubusercontent.com/108608/92329007-38afe180-f097-11ea-81f4-8367c7a850e4.png|image> *In <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=79%3A9|`/replies`>* <https://user-images.githubusercontent.com/108608/92329021-511ffc00-f097-11ea-8068-fb13aa4c409c.png|image> *<https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=432%3A2727|Searching replies in `/replies`>* <https://user-images.githubusercontent.com/108608/92329078-bd9afb00-f097-11ea-9580-a567d1b11b68.png|image> *<https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=585%3A524|The "articles also used this reply" dialog>* <https://user-images.githubusercontent.com/108608/92329092-cbe91700-f097-11ea-9b62-a6317d47879b.png|image> *Refactor* • decompose `components/ListPageDisplays/ArticleItem` into `ListPageCards`, `ListPageCard` and original `ReplyItem` • `ListPageCards`: the list container for all card items • `ListPageCard`: basic card look, with RWD paddings matching the mockup <https://user-images.githubusercontent.com/108608/92329404-dc01f600-f099-11ea-89b0-10cf0d97ec75.png|image> • `ArticleCard`: the article card shared across `/articles`, `/hoax-for-you` and `/search`, built upon `ListPageCard` <https://user-images.githubusercontent.com/108608/92329418-ef14c600-f099-11ea-83df-2f06fb875a88.png|image> • `ReplyItem`: article reply item within each article card in `/replies` page. This component already exists, but its props are simplified in this PR. <https://user-images.githubusercontent.com/108608/92329441-0ce22b00-f09a-11ea-89cf-621c42f7d041.png|image> • adding `page` prop to `ArticlePageLayout` • The ultimate goal is to split `ArticlePageLayout` into each page components like `/articles`, `/hoax-for-you` and `/search` • However, this PR has already collected too much changes, removing `ArticlePageLayout` in this PR will be very difficult to review. • Therefore I added `page` prop to differentiate pages in `ArticlePageLayout`. This will help us splitting logic into respective pages in the future PR. • Introduce `&lt;ReplyCountInfo&gt;` for reply info with reply stats • It's only used in 2 places. However its calculation is a bit complicated, thus we are turning it into a component. *Others* • Lists 25 items per page (fixes <https://github.com/cofacts/rumors-site/issues/307|#307>)

Comment on #321 Track rss, and add utm_source to each url that generated from feed.js

What would `&amp;utm_source=Others&amp;utm_medium=Subcribe` do?

Review on #321 Track rss, and add utm_source to each url that generated from feed.js

Thanks for the update, it's looking good! Some thoughts and questions appended.

Comment on #321 Track rss, and add utm_source to each url that generated from feed.js

I think we can use something like `Poll`, which better describes this action.

Review on #47 update analytics and users' schema &amp; write a migration to update mappings

LGTM, thanks a lot!

Facebook Groups

Facebook Groups

【Cofacts 真的假的】編輯交流天地 has 3,908 members. 【給編輯：真的假的闢謠平台】 <https://cofacts.g0v.tw/articles> 《貼文規範》 :ok_woman:?‍ 這裡歡迎各位闢謠編輯，在這裡交流各種闢謠經驗、假新聞或訊息的相關資訊。 :man-gesturing-ok: :warning: 不過這裡『不是』LINE bot 使用者的謠言解答區，『不歡迎』像這樣的伸手文： :u7981:「這真的假的？！（貼上連結）」...

Comment on #321 Track rss, and add utm_source to each url that generated from feed.js

It should be `&amp;source=Others` only, I forgot to remove `&amp;utm_source=Others&amp;utm_medium=Subcribe` after testing.

Comment on #321 Track rss, and add utm_source to each url that generated from feed.js

:ok_hand:

Review on #321 Track rss, and add utm_source to each url that generated from feed.js

#222 Tracking RSS usage

#321 Track rss, and add utm_source to each url that generated from feed.js

Review on #221 remove unused utils

Thanks for the fix!

#221 remove unused utils

#307 List 25 items per page in list page UIs

#288 Replace &lt;ArticleItem&gt; with more reusable card components

#219 Simplify state, return state only when we need it

Fixes <https://github.com/cofacts/rumors-line-bot/issues/177|#177> 1. Remove useless state assignment and return state only when we need it • `ASKING_REPLY_FEEDBACK` state is replaced by `input.startsWith(UPVOTE_PREFIX or DOWNVOTE_PREFIX)`. • In [handleInput], `context.state` is mainly used for postback message. But now it's also used to distinguish state `ASKING_ARTICLE_SUBMISSION_CONSENT` and `ASKING_REPLY_REQUEST_REASON` from `input.startsWith(SOURCE_PREFIX)`. Maybe we can use different prefixes for them in the future. 2. Move reason message handler from [initState] to [askingReplyRequestReason] • Merge reason message(original in `initState`) to `ASKING_REPLY_REQUEST_REASON`. Note: I don't update test in this PR, so we can see if there's fatal test fail after this refactoring. Will fix test in another PR.

#222 user id collision prevention

since this is a good-to-have per offline discussion, will track it separately in this issue

Screenshot_20200916-230410.png

Screenshot_20200916-230401.png

Screenshot_20200916-230354.png

#333 add cofacts colors as common colors in theme palette

adding colors common palette

g0v.hackmd.io

20200916 會議記錄 - HackMD

#223 pseudo name &amp; open peeps avatar gen

Comment on #223 pseudo name &amp; open peeps avatar gen

<https://coveralls.io/builds/33527062|Coverage Status> Coverage decreased (-0.4%) to 87.957% when pulling *<https://github.com/cofacts/rumors-api/commit/404c5b574d4a7bbb85c61ea0dbfcabce6c71dd98|404c5b5> on name-avatar-gen* into *<https://github.com/cofacts/rumors-api/commit/c2360819b7c9e5c1d4df32d95acdd7d2c584f650|c236081> on master*.

#48 update db schemas to reflect the new user model

#47 update analytics and users' schema &amp; write a migration to update mappings

#1 Post tags json data to AI API can not get correct response

Comment on #1 Post tags json data to AI API can not get correct response

Fix post bug by specifying headers when sending an array of dicts. ``` headers = {'Content-Type': 'application/json', 'Accept':'application/json'} post_response = <http://requests.post|requests.post>(post_task_site, json=result_task_payload, headers=headers) ```

Review on #333 add cofacts colors as common colors in theme palette

LGTM!

#333 add cofacts colors as common colors in theme palette

#220 TypeError: Cannot read property 'split' of undefined

*An article matches but there's no highlight* Should take a look at cofacts-api to see why it matches. <https://user-images.githubusercontent.com/6376572/93561350-95c06700-f9b6-11ea-90aa-0595cf65aabd.png|螢幕快照 2020-09-18 下午1 54 35> View details in Rollbar: <https://rollbar.com/mrorz/rumors-line-bot/items/283/|https://rollbar.com/mrorz/rumors-line-bot/items/283/> ``` TypeError: Cannot read property 'split' of undefined File "/app/build/webhook/handlers/utils.js", line 438, in createHighlightContents for (let highlightPair of text.split('&lt;/HIGHLIGHT&gt;')) { File "/app/build/webhook/handlers/initState.js", line 217, in &lt;unknown&gt; contents: (0, _utils.createHighlightContents)(highlight, text), File "&lt;anonymous&gt;", line unknown, in Array.map File "/app/build/webhook/handlers/initState.js", line 192, in initState const articleOptions = edgesSortedWithSimilarity.map(({ File "&lt;anonymous&gt;", line unknown, in runMicrotasks File "internal/process/task_queues.js", line 97, in processTicksAndRejections File "/app/build/webhook/handleInput.js", line 96, in async handleInput params = await (0, _initState.default)(params); File "/app/build/webhook/index.js", line 210, in async processText result = await (0, _handleInput.default)(context, { File "/app/build/webhook/index.js", line 128, in async singleUserHandler result = await processText(context, type, input, otherFields, userId, req); ```

#221 Adjust share text to promote LINE bot

*As-is* Currently when users share Cofacts results to others, the following text will be pre-filled: <https://github.com/cofacts/rumors-line-bot/blob/dev/src/webhook/handlers/askingReplyFeedback.js#L75|https://github.com/cofacts/rumors-line-bot/blob/dev/src/webhook/handlers/askingReplyFeedback.js#L75> <https://user-images.githubusercontent.com/108608/93563360-4da34380-f9ba-11ea-8a74-93baf7229432.png|image> *To-be* Refer to 疾管家，their share text contains link to chatbot: <https://user-images.githubusercontent.com/108608/93563402-61e74080-f9ba-11ea-9b89-2aecdb771b04.png|image> We can use the following wording: ``` Someone says the message “${articleText}” ${replyType}. 📝 Please refer to ${articleUrl} for more information, replies and references.` 🤖 Add Cofacts to look up dubious messages on LINE: <https://lin.ee/gZ4CCc0> ```

#222 Consult rule / example based agents (Dialogflow) before looking up text in database

*As-is* Currently for some common interactions like "Hello", "Hi", or "Thanks", we need to create an article and reply to teach users to use Cofacts lookup feature correctly. <https://user-images.githubusercontent.com/108608/93565398-e1c2da00-f9bd-11ea-9e28-1625a459532f.png|image> *To-be* We can integrate rule / example based agents for such interaction. More specifically, • We can build rule-based agents using Dialogflow, specifying examples and sample responses there. • When we detect new messages <https://github.com/cofacts/rumors-line-bot/blob/dev/src/webhook/handleInput.js#L65-L80|here> (or in <https://github.com/cofacts/rumors-line-bot/blob/dev/src/webhook/handlers/initState.js|initState handler>), we first consult rule-based agents • If the agent returns fallback, proceed to `ListArticles` rumors-api call as before • If the agent returns a preset response, use the response directly.

Review on #219 Simplify state, return state only when we need it

The code change looks reasonable and it works on my local machine / test accounts. Thanks a million for simplifying the code base! Looking forward to the fix of test cases.

Review on #223 pseudo name &amp; open peeps avatar gen

Thanks for the implementation! It's fun to have these pseudonyms and avatars. Some comments has been added regarding probability of separators &amp; decorators.

Comment on #223 pseudo name &amp; open peeps avatar gen

看到這兩個我以為是自己加的，原來本來的檔案裡就有這兩個人 XDDDD <https://github.com/PlatoForum/PlatoForum/blob/master/utils/pseudonym_gen/names.csv|https://github.com/PlatoForum/PlatoForum/blob/master/utils/pseudonym_gen/names.csv>

Comment on #223 pseudo name &amp; open peeps avatar gen

Though it's me that come up with these separators / decorators, I still think the use of separators and decorators are pretty 中二 lol I think for separators and decorators we can duplicate identity items (such as `${adj}${place}${name}` and `${joinedName}`) a couple of times so that most of the time there is no separators / decorators inside generated names.

#223 Improve README to document MongoDB and Redis

Current README did not mention that we need to spin up MongoDB to get chatbot server ready. This PR • Adds `docker-compose` command to dev instructions. • Although it's mainly used in unit tests, current docker-compose settings &amp; its combination with `.env.sample` is pretty suitable for development as well. • Moves env var setup to `Production Deployment` section.

Comment on #223 Improve README to document MongoDB and Redis

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

#334 Ribbon component

Implement component for ribbon-like visual display. Fixes <https://github.com/cofacts/rumors-site/issues/275|#275> . • Replace `AppLayout/Widgets/Level` with `&lt;Ribbon&gt;` and custom CSS • Remove unused `AppLayout/UserName` Figma: • App menu <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=138%3A26|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=138%3A26> • Mobile sidebar <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=236%3A51|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=236%3A51> • Article detail <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1236%3A1344|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1236%3A1344> *Screenshots* <https://user-images.githubusercontent.com/108608/93713218-f43f3e00-fb8c-11ea-902a-b556a9c23202.png|image> <https://user-images.githubusercontent.com/108608/93713274-4c764000-fb8d-11ea-8f79-81f4ebc87e17.png|image> <https://user-images.githubusercontent.com/108608/93713281-57c96b80-fb8d-11ea-938f-94da02aea3cf.png|image>

Review on #334 Ribbon component

#224 [User] Make profile page related fields publically available

This PR is for fields required in Profile page UI. • Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A385|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A385> • Spec: <https://g0v.hackmd.io/bbreV0ZqRDarHl4Zt5UpEw|https://g0v.hackmd.io/bbreV0ZqRDarHl4Zt5UpEw> Detail • Change `points` and `repliedArticleCount` from 'current-user only' to publicly available • Add `votedArticleReplyCount` to `User` • Add `GraphQLNonNull` when applicable

Comment on #224 Make profile page related fields in User object type publically available

<https://coveralls.io/builds/33588957|Coverage Status> Coverage decreased (-0.08%) to 88.299% when pulling *<https://github.com/cofacts/rumors-api/commit/474265d33fd4d533e22e5ae53efdf2fc8ef8394c|474265d> on profile* into *<https://github.com/cofacts/rumors-api/commit/c2360819b7c9e5c1d4df32d95acdd7d2c584f650|c236081> on master*.

#335 Level icon in Profile page

Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1678%3A510|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1678%3A510> <https://user-images.githubusercontent.com/108608/93717056-daf6bb80-fba5-11ea-9703-94e8772064b3.png|image> <https://user-images.githubusercontent.com/108608/93717072-fcf03e00-fba5-11ea-863c-f6585403dc98.png|image>

g0v.hackmd.io

20200916 會議記錄 - HackMD

#224 Update LIFF translation to match rich menu

Ref: <https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg?both#Rich-menu-%E4%BB%8B%E7%B4%B9|20200916 meeting note> • `/settings` 網頁標題要換成「設定」，內文要翻譯 • `/articles` 網頁標題要改成「問過的問題」

Comment on #332 UI/UX enhancement for GA charts

Related discussion <https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg#Analytics|https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg#Analytics>

#336 Differentiate comment section of article detail page

From <https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg#Detail-page|https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg#Detail-page> &gt; 在沒有回應的時候，使用者會把「我想補充」的那些留言當成是「結論」。這件事情王大師也誤會過唷 In the discussion we decide to add a title in front of comments.

#225 Fix simplify state test

Fixes <https://github.com/cofacts/rumors-line-bot/pull/219|#219> test

Review on #218 ListArticles categoryId filter fix

LGTM!

#218 ListArticles categoryId filter fix

Review on #225 Fix simplify state test

Review is 33% complete, let me submit my initial comments now

Comment on #225 Fix simplify state test

The test case is simulating the case when user scrolls back and choose another reply in the dialog to test if `postbackHandlerState` logic in `handleInput()` works. Since `ASKING_REPLY_FEEDBACK` does not exist anymore, I think we can test `postbackHandlerState` using `CHOOSING_ARTICLE` and `CHOOSING_REPLY` instead. That is, • Initially the context is in `CHOOSING_REPLY` state • The event has `postbackHandlerState` being `CHOOSING_ARTICLE` and the article id • Mocks `choosingArticle` and assert that it has been invoked • Expect `choosingReply` is not invoked

Comment on #225 Fix simplify state test

Seems that we are really downplaying the chatbot logic as a state diagram -- "next state" is not guaranteed in context anymore. Personally I think this is the right direction, because conversations has too many possibilities (users can reply previous chats) . Instead of modeling it using state diagrams (which limites the output), it is more suitable to identify intents (by events and / or `postbackHandlerState` that comes with an event) and react accordingly. (See: <https://g0v.hackmd.io/DjY6dVLxQFG6moNlM98_OQ#LINE-bot-state-diagram---gt-call-graph|call graph analogy>) However, currently the code itself looks like a state machine. This means that we are in a middle -- we are not going to implement state machine but the code still looks like a state machine. We may need another refactor in the future to remove the `state` analogy from chatbot codebase.

#217 Interface for connection related types

#328 Layout components for header

#330 Remove ArticlePageLayout from /articles, /hoax-for-you and /replies

#286 ArticlePageLayout refactor

#331 Remove ArticlePageLayout from search page

Comment on #328 Layout components for header

We should remove style `classes.filters`, it's already written in `Filters` component.

Comment on #328 Layout components for header

Thanks! It's removed in the PR that remove `ReplySearchPageLayout.js` entirely.

Comment on #225 Fix simplify state test

I'm considering removing `context.state`, it's currently only used to <https://github.com/cofacts/rumors-line-bot/pull/219/files#diff-edbf10895ae77fe1ea078801ac142377R69|distinguish state `ASKING_ARTICLE_SUBMISSION_CONSENT` and `ASKING_REPLY_REQUEST_REASON`>. If we use two different `SOURCE_PREFIX` to distinguish asking source of both `first submission article` and `not-yet replied article`, we can make sure state will <https://github.com/cofacts/rumors-line-bot/blob/a9826e4729897e97c613506fa54589979ff7f5f6/src/webhook/handleInput.js#L41|be overridden in `handleInput`> and then remove `context.state`. * * * *Reference* Current flows of `first submission article` and `not-yet replied article` in production <https://user-images.githubusercontent.com/6376572/93976318-68efc380-fdab-11ea-801a-2526cff44e3d.PNG|https://user-images.githubusercontent.com/6376572/93976318-68efc380-fdab-11ea-801a-2526cff44e3d.PNG> <https://user-images.githubusercontent.com/6376572/93976321-6b521d80-fdab-11ea-9192-bebfa429343b.PNG|https://user-images.githubusercontent.com/6376572/93976321-6b521d80-fdab-11ea-9192-bebfa429343b.PNG>

Review on #225 Fix simplify state test

100% reviewed. Thanks for the fix!

#177 Simplify __INIT__ handler by disconnecting inbound actions

#219 Simplify state, return state only when we need it

#225 Fix simplify state test

#337 URL filter params should be case insensitive (in lower case)

*Bug* <https://user-images.githubusercontent.com/1758453/94018290-02869780-fde3-11ea-9a69-06431b882724.png|截圖 2020-09-23 下午9 23 12> The filter params in the url should be in lower case. This change doesn't have to be backward compatible.

Review on #223 Improve README to document MongoDB and Redis

LGTM!

Review on #334 Ribbon component

Comment on #335 Level icon in Profile page

Need to add. ``` &lt;defs&gt; put your gradient definition here &lt;/defs&gt; ```

Review on #335 Level icon in Profile page

#223 Improve README to document MongoDB and Redis

#226 Settings page style &amp; translation

• Adjust look of settings page so that it looks more welcoming to new users. • Add translation that matches rich menu <https://user-images.githubusercontent.com/108608/94231445-9ddc5180-ff36-11ea-800b-037fb39bc2ca.png|image>

Comment on #226 Settings page style &amp; translation

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

Comment on #335 Level icon in Profile page

Nice catch! `&lt;defs&gt;` is now added and UI does not break after add. <https://user-images.githubusercontent.com/108608/94331203-33421900-fffd-11ea-8118-56624e89d1bd.png|image>

#275 Use SVG to implement ribbon tails

#334 Ribbon component

#219 implement name/avatar generator

#223 pseudo name &amp; open peeps avatar gen

#50 Features/backup db

#227 Remove context.state

1. Use different SOURCE_PREFIX to handle first submission article and not-yet replied article logic • Prefix [:one: I got the message from] for first submission article • Prefix [:information_source: I got the message from] for not-yet replied article • When `createAskArticleSubmissionConsentReply`, send a liff.source url with `article_submission=true` 2. Remove context.state

Comment on #227 Remove context.state

*Pull Request Test Coverage Report for <https://coveralls.io/builds/33748279|Build 1137>* • *16* of *16* *(100.0%)* changed or added relevant lines in *8* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.01%*) to *84.858%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

Figma

Cofacts LINE bot related

Created with Figma

Comment on #227 Remove context.state

I am wondering if it is possible for `should block incorrect prefix` to happen under the current action handling logic, since `SOURCE_PREFIX_NOT_YET_REPLIED` will be redirected to other state for now. If not, I think we can remove the logic that emits `ManipulationError` together.

Review on #227 Remove context.state

LGTM! This is a stepping stone PR that leads us away from state diagram towards future models. Thanks for the fix.

Comment on #227 Remove context.state

This is brilliant :+1: Cannot think of edge cases here. Let's test this in Wednesday.

#224 Make profile page related fields in User object type publically available

This PR is for fields required in Profile page UI. • Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A385|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A385> • Spec: <https://g0v.hackmd.io/bbreV0ZqRDarHl4Zt5UpEw|https://g0v.hackmd.io/bbreV0ZqRDarHl4Zt5UpEw> Detail • Change `points` and `repliedArticleCount` from 'current-user only' to publicly available • Add `votedArticleReplyCount` to `User` • Add `GraphQLNonNull` when applicable

#225 Similar replies API and revamp related artitle API

This PR adds `similarReplies` to `Reply` object type to display <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=894%3A85|similar reply section in reply page>. Given that replies are often copied over to another, this function should be useful when finding duplicated replies. Several refactors to `Article` object type's `relatedArticles` are also added, including: • Default to sort by score (high to low) • Add hyperlink title / summary matching • Test highlights are generated in unit tests

Comment on #216 On-boarding tutorial

English wording has been revised. Kudos to Jack for revisiting these words!

#338 Hyperlinks story

#335 Level icon in Profile page

Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1678%3A510|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1678%3A510> <https://user-images.githubusercontent.com/108608/93717056-daf6bb80-fba5-11ea-9703-94e8772064b3.png|image> <https://user-images.githubusercontent.com/108608/93717072-fcf03e00-fba5-11ea-863c-f6585403dc98.png|image>

#338 Add storybook to &lt;Hyperlinks&gt;

#224 Make profile page related fields in User object type publically available

#335 Level icon in Profile page

Review on #226 Settings page style &amp; translation

LGTM!

Review on #338 Add storybook to &lt;Hyperlinks&gt;

#224 Update LIFF translation to match rich menu

#226 Settings page style &amp; translation

Review on #227 Remove context.state

LGTM! Let's test it tonight :rocket:

#227 Remove context.state

#338 Add storybook to &lt;Hyperlinks&gt;

#339 Cofacts website redirect to Cofacts LINE bot

From: <https://g0v.hackmd.io/GhVhBlK_QwKT3E5clAfkJw#Owned-media-mitigation|https://g0v.hackmd.io/GhVhBlK_QwKT3E5clAfkJw#Owned-media-mitigation> • 用類似客服按鈕的方式黏在旁邊 • google 來大部分是手機使用者，所以用連結連到 <https://line.me/R/ti/p/@cofacts|https://line.me/R/ti/p/@cofacts> • 分享文案加入 Cofacts LINE bot • article detail「複製」按鈕 / share 功能的文字 • 在 Cofacts 複製文字時，加上 Cofacts 網站網址（如<https://www.ettoday.net/news/20200930/1821415.htm|ETToday>）