#340 Add instructions to add LINE as friend in article detail page

Closes <https://github.com/cofacts/rumors-site/issues/339|#339>.

mrorz 2020-10-01 17:06:22

目前是用 quick and dirty 的方式實作完了開會時提到的 https://github.com/cofacts/rumors-site/issues/339 ，並且趕在連假期間上線，看 own media 導流到 chatbot 的效果。

現在回頭看這個實作好像也沒啥可以優化的地方，因為字串的重複只有 2 處。
倒是希望可以有個英文版文案讓我能弄 i18n～

#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>）

#341 Trusted site

• ❔1
• 1
• ❓1

Comment on #341 Trusted site

Hi <https://github.com/Debyanshu|@Debyanshu> would you elaborate more about this issue?

#342 &lt;Card&gt; for detail pages

*Refactor* This PR introduces `&lt;Card&gt;`, a common layout that can be seen in <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1273%3A176|article detail>, and will be applied to <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A190|reply detail> and <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=912%3A385|profile page> in the future. <https://user-images.githubusercontent.com/108608/94900490-a8af5d00-04c7-11eb-8dc9-e721aede8e10.png|image> <https://user-images.githubusercontent.com/108608/94900528-ba910000-04c7-11eb-9295-f06ccd23c9fd.png|image> <https://user-images.githubusercontent.com/108608/94900553-c67cc200-04c7-11eb-913a-61b3e7cfa45a.png|image> Also I add I add `forwardRef` to `Card` and `Ribbon` because in future PRs we are going to need them.

#343 Adjust global border-radius and primary color palatte

This PR adjusts Material-UI theme used theme in Cofacts to better match <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=681%3A0|figma> <https://user-images.githubusercontent.com/108608/94903082-d1d1ec80-04cb-11eb-9659-eb476b6a55cf.gif|button> • Global border radius raised to 8px (default 4px) • This affects dropdowns, pop-overs, etc. • Remove incorrect primary dark / light color setup • The incorrect setup causes buttons in primary color turns grey when hovering on the button • Remove the color so that Material-UI can handle hovering color by themselves. • Set primary button text color in global CSS • Material-UI uses `rgba(0,0,0,0.88)` by default • Set to #fff to match <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=890%3A586|figma> • Apply app.css to Storybook to reflect this change • Use Material-UI `Button` in `ArticleReplyFeedbackControl` to see primary color setup

#344 Article detail revamp using &lt;Card&gt;

Rewrite Article detail page layout using `&lt;Card&gt;` and related components introduced in

Review on #342 &lt;Card&gt; for detail pages

Review on #343 Adjust global border-radius and primary color palatte

Bram.us

Prevent content from being hidden underneath a fixed header by using scroll-margin-top

MDN Web Docs

scroll-behavior

The scroll-behavior CSS property sets the behavior for a scrolling box when scrolling is triggered by the navigation or CSSOM scrolling APIs.

#344 Article detail revamp using &lt;Card&gt;

#18 Add categories data

#18 Add categories data

#226 migration script to create backend users referenced in the db

Review on #344 Article detail revamp using &lt;Card&gt;

#340 Add instructions to add LINE as friend in article detail page

#226 migration script to create backend users referenced in the db

Comment on #49 create users from existing entities

<https://github.com/cofacts/rumors-api/pull/226|cofacts/rumors-api#226>

Review on #340 Add instructions to add LINE as friend in article detail page

Figma

Cofacts website

Created with Figma

mrorz 2020-10-04 20:50:18

進階設定似乎沒有
所以我覺得放文字就好

nonumpa 2020-10-04 20:51:27

哦哦

Comment on #340 Add instructions to add LINE as friend in article detail page

我發現 article page copy-paste 在我撰寫的回應、在新回應區利用剪下貼上重新編排回應文字的時候，也會跑出 `在 LINE 看到可疑訊息？加「真的假的」好友，查謠言與詐騙` 我覺得滿惱人的，所以改成讓「文字插入剪貼簿」這件事情只會發生在訊息文字與已經回應的文字囉。

mrorz 2020-10-04 23:56:55

其實查證的時候會拿訊息文字去複製貼上到 FB 之類的地方

現在會加上那個 `在 LINE 看到可疑訊息？加「真的假的」好友，查謠言與詐騙` 也是挺煩的囧

大家覺得要拿掉ㄇ

lucien 2020-10-05 00:08:21

簽名檔我覺得從散播的角度，好像得留個

lucien 2020-10-05 00:08:37

可能可以嘗試更輕量的說法

mrorz 2020-10-05 14:14:26

後來在這個 PR 裡面
我把訊息文字的 `onCopy` 拔掉了，留下 reply 的 onCopy
https://github.com/cofacts/rumors-site/pull/344

因為
• 這要另外加 `<div>`
• 會複製謠言文字貼上的人，應該大多是正在查謠言的編輯，不想扯編輯後腿

#345 Similar messages side section in article detail

Rewrite "similar messages" side section. • Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=890%3A585|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=890%3A585> • Mobile / desktop differs a lot, thus `Card` cannot be reused here. • use explicit class name for each component in the similar messages section

mrorz 2020-10-05 01:12:40

這個理論上要跟 reply detail 重用
因為在 article detail 佔滿多行的，希望可以抽成 component
但我還沒想到乾淨的轉 component 的方法

#339 Cofacts website redirect to Cofacts LINE bot

#340 Add instructions to add LINE as friend in article detail page

#344 Article detail revamp using &lt;Card&gt;

Rewrite Article detail page layout using `&lt;Card&gt;` and related components introduced in <https://github.com/cofacts/rumors-site/pull/342|#342> • Mix the use of `&lt;Card&gt;`, `--card-px`, `&lt;CardHeader&gt;` `&lt;CardContent&gt;` to compose basic layout of the article detail page ("related article" section excluded) • Converts `button` to Material-UI `&lt;Button&gt;` to cut extra CSS styles &amp; provide better look &amp; feel for the buttons *Per-file / section summary* *`/page/article/[id].js`* • Apply `&lt;Card&gt;`, `&lt;CardContent&gt;` and `&lt;CardHeader&gt;` • Make margin / padding adjustments at page component level • More adhere to <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1236%3A1272|figma> • Similar to <https://mxstbr.com/thoughts/margin|'layout' component> • Each sub-component is adjusted to have 0 margin / padding to maximize their reusability • Add header to comments to that it does not confuse users -- Fix <https://github.com/cofacts/rumors-site/issues/336|#336> <https://user-images.githubusercontent.com/108608/94984787-8f1f1b80-0582-11eb-8a5d-b35d589038f7.png|localhost_3000_article_3fczhzr31y8ap> <https://user-images.githubusercontent.com/108608/94984792-a1995500-0582-11eb-9ff1-79b6169e8204.png|image> *`TrendPlot`* • Simply CSS • Make the left most label align left edge, the right most label align right edge <https://user-images.githubusercontent.com/108608/94961064-8d276f00-0526-11eb-949a-07e375c0a670.png|image> *`ReplyRequstReason`* • Simplify DOM • Use Material-UI `Button` to remove custom CSS <https://user-images.githubusercontent.com/108608/94962038-636f4780-0528-11eb-841e-b72a18594a2d.png|image> <https://user-images.githubusercontent.com/108608/94962028-5eaa9380-0528-11eb-8aa8-7e041c6a9ddb.png|image> *`CreateReplyRequestForm`* • Use different button for "Reply to this message" button for mobile &amp; desktop. This simplifies CSS logic a lot. • Remove avatar on mobile, as <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1236%3A1314|Figma> suggests. • Use <https://material-ui.com/components/textarea-autosize/|TextareaAutosize> for reason input • Remove focus logic and fix <https://github.com/cofacts/rumors-site/issues/310|#310> • Figma 裡面「<https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1019%3A0|碰到『送出』上緣就自動多一行>」根本做不出來啦（翻桌） 不做了不做了～ • Simplify "new reply" floating action button style • Now uses Material UI FAB style only • Move the pen icon to component/icons • Show button only for users that is logged in (so that it does not interfere with add new LINE FAB) <https://user-images.githubusercontent.com/108608/94961284-f0190600-0526-11eb-8f20-f75ca7feb2a2.png|image> <https://user-images.githubusercontent.com/108608/94961344-0b841100-0527-11eb-8c44-4f6ee2aec94c.png|image> <https://user-images.githubusercontent.com/108608/95045335-5911a100-0714-11eb-98ee-bfb787b12fa0.png|image> *`NewReplySection`* • Use `&lt;Card&gt;` for desktop and `&lt;Dialog fullscreen&gt;` for mobile • This may fix some issue <https://github.com/cofacts/rumors-site/issues/279|#279> since we are using Material UI `Dialog` • We are render this only on browser, thus we can use `useMediaQuery` here <https://user-images.githubusercontent.com/108608/94961688-b4327080-0527-11eb-9f4f-f1aadd6a5db0.png|image> <https://user-images.githubusercontent.com/108608/94961769-e6dc6900-0527-11eb-9ff7-3d19ca5e85b6.gif|new reply section> *`CurrentReplies`* • Use `&lt;CardHeader&gt;` for header to match <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1273%3A190|figma> • Each article reply is a `&lt;CardContent&gt;` • Fix deleted reply dialog <https://user-images.githubusercontent.com/108608/94984852-4025b600-0583-11eb-8c85-0f7cf3c361a7.png|image> <https://user-images.githubusercontent.com/108608/94984858-516ec280-0583-11eb-9b1b-2608c9549437.png|image> <https://user-images.githubusercontent.com/108608/94984860-57fd3a00-0583-11eb-8a0d-3c969eeaf73f.png|image> <https://user-images.githubusercontent.com/108608/94984877-76633580-0583-11eb-8546-92984e8be21b.png|image> <https://user-images.githubusercontent.com/108608/94984879-811dca80-0583-11eb-9088-8ba951249dc3.png|image>

#345 Similar messages side section in article detail

#346 Add favicon and article detail banner

• Add favicon that • uses dark-theme aware SVG by default • uses PNG with white background as fallback • Add banner to article detail that redirects user to LINE <https://user-images.githubusercontent.com/108608/95110867-3f527700-0771-11eb-82d5-28a46a6d5083.png|image> <https://user-images.githubusercontent.com/108608/95112122-21861180-0773-11eb-9d47-c27c338bd2cd.png|image>

Review on #346 Add favicon and article detail banner

#347 SEO for Mandarin content

In <https://g0v.hackmd.io/GhVhBlK_QwKT3E5clAfkJw#%E5%B0%8F%E8%81%9A%E8%A7%80%E5%AF%9F%E8%88%87%E6%AA%A2%E8%A8%8E|20200930 meeting note>, we found that "Cofacts" won't score the first in Google when the google language is set to Traditional Chinese (Taiwan); Medium with Mandarin content comes the first. 要看這個 <https://support.google.com/webmasters/answer/182192?hl=en|https://support.google.com/webmasters/answer/182192?hl=en> &gt; In addition, the crawler sends HTTP requests without setting Accept-Language in the request header. 可能要在 HTML 裡加上不同語言的 link <https://support.google.com/webmasters/answer/189077|https://support.google.com/webmasters/answer/189077>

#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

Review on #225 Similar replies API and revamp related artitle API

• 🙏1

#225 Similar replies API and revamp related artitle API

• 🐳1

• ❤️1

#341 Trusted site

#348 Add hash to new reply section &amp; each reply in article detail page

From slack discussion: <https://user-images.githubusercontent.com/108608/95320328-eba87080-08cb-11eb-96f0-d871a6384fba.png|image> Related material: • <https://www.bram.us/2020/03/01/prevent-content-from-being-hidden-underneath-a-fixed-header-by-using-scroll-margin-top/|https://www.bram.us/2020/03/01/prevent-content-from-being-hidden-underneath-a-fixed-header-by-using-scroll-margin-top/> • <https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-behavior|https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-behavior> Alternative: • Seems that scroll-margin also works for currently used `scrollIntoView()`: <https://stackoverflow.com/a/59611245|https://stackoverflow.com/a/59611245>

Comment on #216 On-boarding tutorial

「模擬傳訊息」`displayText` <https://developers.line.biz/en/reference/messaging-api/#postback-action|https://developers.line.biz/en/reference/messaging-api/#postback-action> max 300 characters &gt; 只要每天早上一杯地瓜葉牛奶。不僅有效降低三高，甚至連痛風也沒了；此外，地瓜葉牛奶的作法也很簡單，只要先將地瓜葉川燙過後，再加入鮮奶打成汁即可。 Reply: Use <https://cofacts.org/reply/QB6mgGMBSH_MLFhI2GNi|https://cofacts.org/reply/QB6mgGMBSH_MLFhI2GNi>

#342 &lt;Card&gt; for detail pages

#343 Adjust global border-radius and primary color palatte

#310 Reply request submission button jumps around when clicking

#336 Differentiate comment section of article detail page

#344 Article detail revamp using &lt;Card&gt;

#345 Similar messages side section in article detail

#346 Add favicon and article detail banner

helloeveryone.taipei

來我跟你說

群組裡晨昏定省的長輩圖總令你難以招架嗎？開口說愛其實沒這麼難，就讓最可愛有趣的晚輩圖產生器，陪你一起傳遞友善問候與溫柔宣言，分享彩虹多元平權價值觀點！心中有愛，晚輩圖就給他做起來！

• 👵1

Comment on #226 migration script to create backend users referenced in the db

We can add some text for this `<http://console.info|console.info>` so that we know what this number means when we see it in the terminal.

Review on #226 migration script to create backend users referenced in the db

Sorry it has been a week and I am still consuming `src/scripts/migrations/createBackendUsers.js`. Other files are reviewed and looks good to me :)

Comment on #226 migration script to create backend users referenced in the db

I am not familiar with painless. Can painless omit `return` ?

Comment on #226 migration script to create backend users referenced in the db

I think we can use camel case (`batchSize`) here

Comment on #226 migration script to create backend users referenced in the db

<https://www.elastic.co/guide/en/elasticsearch/painless/6.2/painless-syntax.html|https://www.elastic.co/guide/en/elasticsearch/painless/6.2/painless-syntax.html> It's not really well documented but from the look of the example and the fact it actually runs as expected, I think it does if the return type is not void.

Review on #226 migration script to create backend users referenced in the db

LGTM! The process is very well-written and clear. Thanks for the script! :+1: I will start arranging SOPs and apply it first on DB backups &amp; staging environments. Please help resolve the conflict then we can merge this PR.

#228 Hint user to turn on notification to get updates

• Tell the user that Cofacts can notify them if they turn on notification setting • Timing: after displaying a reply, and after submitting new reply requests • Adjust the wording of notification to be more clear and concise Closes <https://github.com/cofacts/rumors-line-bot/issues/217|#217>. *After displaying a reply* <https://user-images.githubusercontent.com/108608/95684283-30613e00-0c23-11eb-9614-b9e861b3f6ce.png|image> *After providing source* (This step also sends a reply request without reason) In this step, the priority should be: providing more reason &gt; turn on notification &gt; ask friends. <https://user-images.githubusercontent.com/108608/95684307-51299380-0c23-11eb-8482-2c59095cd4aa.png|image> *After providing reason* In this step, the priority should be: turn on notification &gt; ask friends &gt; update reason <https://user-images.githubusercontent.com/108608/95684319-60a8dc80-0c23-11eb-984f-9278ab841b1d.png|image>

• ❤️2

Comment on #228 Hint user to turn on notification to get updates

*Pull Request Test Coverage Report for <https://coveralls.io/builds/34095248|Build 1157>* • *9* of *9* *(100.0%)* changed or added relevant lines in *4* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.02%*) to *84.727%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

YouTube

LINE-ifttt

rockhung 2020-10-13 14:18:07

可以喔，雖然我看了兩遍才懂～

rockhung 2020-10-13 14:19:55

主要是這句「接起來之後，IFTTT 會在收到熱門訊息時主動通知」感覺少了點形容比較容易懂，例如加上「 透過你選擇的社交軟體通知你」

rockhung 2020-10-13 14:40:17

超過一百分

mrorz 2020-10-14 02:14:35

LINE - https://youtu.be/jKDllYf9bFQ
Slack - https://youtu.be/G5sUpDhzjR0
TG - https://youtu.be/PgsjQHgEnyQ

#349 Reply detail page and side section

#349 Reply detail page and side section

nonumpa 2020-10-15 15:46:12

提一個在這個 PR 發現，但跟這個 PR 比較無關的事
1. Reply 的 title 是不是忘記粗體了
2. Different opinion/Reference 的字型大小是不是給錯了
英文版特別明顯，第一眼看過去，會直接往 Different opinion 看

mrorz 2020-10-15 15:49:58

你的粗體好粗ㄛ

nonumpa 2020-10-15 15:53:23

firefox 跟 chrome 長得不太一樣@@

mrorz 2020-10-21 12:24:44

added in https://github.com/cofacts/rumors-site/issues/282#issuecomment-713292741

Comment on #226 migration script to create backend users referenced in the db

<https://coveralls.io/builds/34136730|Coverage Status> Coverage increased (+0.9%) to 88.156% when pulling *<https://github.com/cofacts/rumors-api/commit/865dc58dabafa214d838e7c46bea9f390e45e50b|865dc58> on createUsers* into *<https://github.com/cofacts/rumors-api/commit/77f009788e5f011eb1a8acf7a56d5d1ebc5a6208|77f0097> on master*.

#49 create users from existing entities

#226 migration script to create backend users referenced in the db

#227 index user if not existed and log last active time for user accessing apis via backend apps

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

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

<https://coveralls.io/builds/34136941|Coverage Status> Coverage decreased (-2.1%) to 85.923% when pulling *<https://github.com/cofacts/rumors-api/commit/4d92870af049290dd50d72e380818b43d7ff7e04|4d92870> on backendUsers* into *<https://github.com/cofacts/rumors-api/commit/c678c946517685dd8b0a6764a0bd9af295a71def|c678c94> on master*.

YouTube

在 LINE 接收 Cofacts 真的假的的熱門訊息

YouTube

在 Slack 接收 Cofacts 真的假的的熱門訊息

YouTube

在 Telegram 接收 Cofacts 真的假的熱門訊息

g0v.hackmd.io

20201014 會議記錄 - HackMD

#350 Don't insert friend link to clipboard for logged-in users

From <https://g0v.hackmd.io/CCecwMdhT_eTPQmNfzQTzQ#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|1007 testing feedback> In <https://github.com/cofacts/rumors-site/pull/340|#340> we insert add-friend link at the end of clipboard when user copies text from reply. However, for logged-in editors, it will interfere the fact-checking process, thus should be removed. We can safely assume that logged-in users are not the target of the add-friend link.

Comment on #282 Font size adjustments

Per <https://g0v.hackmd.io/CCecwMdhT_eTPQmNfzQTzQ?both#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|2020/10/07 testing feedback> The share button should have same height as reason buttons. Currently "Share" is slightly higher and its font is slightly bigger: <https://user-images.githubusercontent.com/108608/95948152-9b2c9800-0e22-11eb-9f2a-c26b27e3a52a.png|image>

#351 [RSS] Implement new IFTTT UI

Figma : <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=3146%3A351|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=3146%3A351> Discussion : <https://g0v.hackmd.io/GhVhBlK_QwKT3E5clAfkJw?view#Cofacts-Next-%E8%BF%BD%E8%B9%A4|https://g0v.hackmd.io/GhVhBlK_QwKT3E5clAfkJw?view#Cofacts-Next-%E8%BF%BD%E8%B9%A4> Screenshots : <https://user-images.githubusercontent.com/6376572/95965599-b1dfe880-0e3c-11eb-8a0a-f34fbfc26ed4.gif|ifttt>

Comment on #228 Hint user to turn on notification to get updates

Typo

• 1

Review on #228 Hint user to turn on notification to get updates

LGTM! Just some minor issues: 1. typo： `ㄌㄛ` 2. Some lines aren't covered by test : <https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingReplyRequestReason.js#L74|https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingReplyRequestReason.js#L74> <https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingArticleSubmissionConsent.js#L103|https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingArticleSubmissionConsent.js#L103>

Review on #349 Reply detail page and side section

Comment on #351 [RSS] Implement new IFTTT UI

We can move the definition of `CustomTab` and `CustomCopyButton` to outside of `DialogBody`'s render function

Comment on #351 [RSS] Implement new IFTTT UI

Wrapping `t` to Chinese characters will cause it to be used as translation keys when we extract translation in the future. Suggest remove `t` from these copies.

Review on #351 [RSS] Implement new IFTTT UI

Overall LGTM, thanks for the update! Some little suggestions before merge is appended.

Comment on #228 Hint user to turn on notification to get updates

&gt; LGTM! &gt; &gt; Just some minor issues: &gt; &gt; 1. typo： `ㄌㄛ` &gt; 2. Some lines aren't covered by test : &gt; <https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingReplyRequestReason.js#L74|https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingReplyRequestReason.js#L74> &gt; <https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingArticleSubmissionConsent.js#L103|https://coveralls.io/builds/34095250/source?filename=src/webhook/handlers/askingArticleSubmissionConsent.js#L103> Branches are covered in latest unit test case. Should be ready to merge now~

#217 Ask user to turn on notification after submission

#228 Hint user to turn on notification to get updates

#227 index user if not existed and log last active time for user accessing apis via backend apps

#228 untangle test dependencies

some fixtures aren't wiped properly, so db query will have different results depending on the order of the tests ran; this is introducing unnecessary dependencies and causing some tests to be flaky.

Review on #351 [RSS] Implement new IFTTT UI

LGTM! Thanks a million!

#351 [RSS] Implement new IFTTT UI

Comment on #216 On-boarding tutorial

Images: <https://www.dropbox.com/sh/y3mt06zvahge4cd/AACwWy77wDd9La0ICViOC56Ea?dl=0|https://www.dropbox.com/sh/y3mt06zvahge4cd/AACwWy77wDd9La0ICViOC56Ea?dl=0> • 1: Greeting • 2~5: Flex message carousel • 6: Thank you

Comment on #50 Features/backup db

<https://github.com/godgunman|@godgunman> Please move to rumors-deploy, thanks!

#349 Reply detail page and side section

• Implements reply detail • Figma: <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=894%3A0|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=894%3A0> • Adds "similar replies" side section as Figma suggests • Adds more info about each article that used this reply • Extracts `SideSection` from article detail page • Update `&lt;Infos&gt;` so that • It supports `className` props • It does not show `|` when first item is `null` *Screenshots* *Reply detail page* <https://user-images.githubusercontent.com/108608/95821650-dbc1de00-0d5c-11eb-8b83-ea0e92639c35.png|image> <https://user-images.githubusercontent.com/108608/95821201-15461980-0d5c-11eb-95db-8028091c6c6d.png|image> After deleting reply from its original article: <https://user-images.githubusercontent.com/108608/95821243-27c05300-0d5c-11eb-9e35-c2a9eaeabf78.png|image> *`SideSection`* <https://user-images.githubusercontent.com/108608/95821744-1deb1f80-0d5d-11eb-9754-afa7228119fd.png|image> <https://user-images.githubusercontent.com/108608/95821759-25122d80-0d5d-11eb-984d-66f52423cf88.png|image>

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

How about making the delete in the test case `creates new user if user does not exist`? In this way we can leverage `passportProfile.id` to clean up. We can do the cleanup before assertion so that assertion fail do not interfere with cleanup.

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

We may need to remove L8 to make this line work xd

Review on #227 index user if not existed and log last active time for user accessing apis via backend apps

Commit 3 comments here first, still under review QQ

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

Note: we may need a ticket for adding this to schema, making this field an ISO timestamp (date format)

HackMD

Cofacts 會議記錄 - HackMD

# Cofacts 會議記錄 ## 2020 - [20201021 會議記錄](/NmokGVB_Qsa1dIgGEsfoJQ) - [20201014 會議記錄](/R3TffjwOSXef

#349 Reply detail page and side section

Comment on #282 Font size adjustments

From 2020/10/15 <https://g0v-slack-archive.g0v.ronny.tw/index/channel/C2PPMRQGP/2020-10#ts-1602747972.042300|Slack discussion> (Firefox screenshot) <https://user-images.githubusercontent.com/108608/96673102-552e8180-1398-11eb-822d-33d87fe83c59.png|image> &gt; • Reply 的 title 是不是忘記粗體了 &gt; • Different opinion/Reference 的字型大小是不是給錯了 &gt; 英文版特別明顯，第一眼看過去，會直接往 Different opinion 看

#51 Sample article date display error

<https://www.youtube.com/watch?t=&amp;v=lQX_9BLpnx8|image> The message in video: <https://cofacts.g0v.tw/article/3abphmilm6try|https://cofacts.g0v.tw/article/3abphmilm6try> The erroneous article shown in video: <https://cofacts.g0v.tw/article/sample2-rumor|https://cofacts.g0v.tw/article/sample2-rumor> The article has `createdAt` &amp; `updatedAt` being `null`: <https://user-images.githubusercontent.com/108608/96673460-249b1780-1399-11eb-846f-ede69323dffe.png|image> Articles with id `sampleX-rumor` are seed items in the beginning of 真的假的 project, they do not have valid `createdAt` because they are not collected from chatbot. We can • find out how many articles are like this • discuss how to handle / display such articles

#229 Highlight improvements

From <https://g0v.hackmd.io/R3TffjwOSXefZBCFPkSrqA#Chatbot-highlight-amp-matching-improvement|20201014> and <https://g0v.hackmd.io/-j-fAX0tS62amv9LejshOg#-Chatbot|20200923> discussion, *Long snippet gets truncated out* <https://user-images.githubusercontent.com/108608/96676355-b6a61e80-139f-11eb-912c-7d093c3ea0e9.png|image> &gt; 因為 API 那裡可能會吐出很長的 snippet ，然後再 highlight 中間的部分，導致 highlight 的部分太後面 xD &gt; 這個可能要在 API 上多開欄位指定預計 snippet 長度來解，有些麻煩就是了，可以記下來，未來再想想怎麼做 *Better matching by increasing text* <https://user-images.githubusercontent.com/108608/96676447-e35a3600-139f-11eb-8877-e0198e7d19dc.png|image> &gt; 文字應該是 100% match &gt; 但 highlight 只有標出 more_like_this query 認為重要的那些 query。 &gt; 增加 more_like_this 要查的字，增加查詢時間但也增加 recall / sensitivity (敏感性) &amp; 更好的 highlight

Comment on #53 Revisit similarity measure

From <https://g0v.hackmd.io/R3TffjwOSXefZBCFPkSrqA#Chatbot-highlight-amp-matching-improvement|20201014 meeting note>, as we now support highlighting, users can identify similar messages more easily. We can directly lower the threshold of search hit.

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

haha, good catch. Actually, I think this might only be needed for test to pass locally. It doesn't seem to be timeout as easily on travis. I am actually thinking maybe we can make timeout value an environment variable to be set in .env and move this to setup since this is pretty much environment performance dependent (I don't know about everyone else, but they run way slower on my laptop than on travis :p)

awesomefigmatips.com

Ignore constraint settings while resizing a Frame - Awesome Figma Tips

Small but awesome tips to work faster in Figma.

stbb1025 2020-10-22 09:59:18

恍然大悟！！！大感謝！！！

Comment on #332 UI/UX enhancement for GA charts

TODO: 1. show aggregated `webUser`/`lineUser` stats instead of <https://github.com/cofacts/rumors-site/blob/dev/components/TrendPlot.js#L101-L102|`webVisit`/`lineVisit`> 2. move the description in the legend labels (i.e. web visit/line inquiry) to tooltips and leave only the color coded numbers (`theme.palette.info.main` for web, `theme.palette.primary.main` for chatbot) 3. apply the color coding to distinguish web visit and line inquiry in the tooltip shown when hovering over a certain date on the chart 4. replace `visits` with `users` as see fit

#230 create graphql object type for ISO timestamp

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

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

#352 Makeshift edit name function for the hackathob

Before the 10/24 hackathon I would like to add a very simple edit name function, so that editors can change their display name as they wish. <https://user-images.githubusercontent.com/108608/96909442-9fb31980-14d0-11eb-8ccc-45e8746e6a75.gif|change-name-desktop> <https://user-images.githubusercontent.com/108608/96909468-a93c8180-14d0-11eb-9b1e-18a1222a0c9a.gif|change-name-mobile> Also deployed to staging site for preview.

mrorz 2020-10-23 02:03:51

我在 staging 放上了編輯名字的功能，希望在大松之前可以進 code，這樣大松參與者就可以改名字了～

請大家過目：
https://dev.cofacts.org/articles

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

I think it's OK that we increase timeout directly. Increasing timeout does not impact time spent on test, but can save precious developing energy on problems that we can really solve.

Review on #352 Makeshift edit name function for the hackathob

#352 Makeshift edit name function for the hackathon

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

nit: adding snapshot name (`toMatchSnapshot`'s argument) when multiple `toMatchSnapshot` is used in one test case can help increase the readability of snapshot files.

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

I think we can assert `rollbar.error` is not invoked here to ensure that collision check does not trigger by accident. We should also reset `rollbar.error` mock before each test.

Review on #227 index user if not existed and log last active time for user accessing apis via backend apps

Thanks a million for looping in tests for index.js! This is the first time apollo server context logic can be included in tests. I am grateful for <https://github.com/ztsai|@ztsai> 's integration effort :woman-bowing: I am a bit confused how Apollo server context could interact with other middlewares like `checkHeaders`. We may need to check if the current logic works for web browser users. Lastly, I have some nitpicking suggestions are regarding snapshot names :P

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

Is `userId` being sent to `graphQLServerOptions` in real scenarios? When is it written?

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

Suggest adding snapshot name when multiple `toMatchSnapshot` is called in unit tests. The snapshot file would be more readable when `1, 2, 3` replaced with meaningful snapshot names :)

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

1. I cannot think of a case that `appId` is missing -- it should always be populated by `checkHeaders()`. If this is expected, maybe we can simplify the logic here by rejecting empty `ctx.appId` early. 2. Since we are invoking `createOrUpdateUser`, which will consult database anyway, I think we can consider • remove DB read operation in `passport.deserializeUser` in `auth.js` -- we can just return `userId` or `{passportUserId: userId}` in `passport.deserializeUser` to notify other middlewares about passport's login session. • we then no longer need to merge `ctx.state.user` with GraphQL context's user.

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

Does this work for `ctx.appId` is `WEBSITE` (browser app users) ?

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

this is a workaround since `createTestClient` doesn't let you provide `context` so overwriting `integrationContextArgument` for `graphQLServerOptions` is kinda like mimicking being called after `checkHeader` has been called and `appId` and `userId` has been included I will add a comment stating that. <https://github.com/apollographql/apollo-server/blob/main/packages/apollo-server-core/src/ApolloServer.ts#L939|https://github.com/apollographql/apollo-server/blob/main/packages/apollo-server-core/src/ApolloServer.ts#L939> I did a little bit of digging, and I think the official <https://github.com/apollographql/apollo-server/blob/main/packages/apollo-server-testing/src/createTestClient.ts|testing util> provided by apollo-server isn't really helpful. This is the workaround that I came up with to test the new functionalities, but to test the entire request cycle including auth flow and other middleware functions is even trickier, and will need to do some passport stubbing. Which is why I was concern and believe some manual testing is needed

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

oh, there's no `ctx.query.userId` for web users?

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

Nope. For web app users it relies on `ctx.state.user`, which is populated by `passport.deserializeUser` callback, which passport.js will call when de-serialize data (user id) in cookie to `ctx.state.user`. Ref: <https://g0v.hackmd.io/ZcoUOX_-RQSkJyl5xz4_Zg#Identifying-the-app-and-user|https://g0v.hackmd.io/ZcoUOX_-RQSkJyl5xz4_Zg#Identifying-the-app-and-user>

ken998993 2020-10-24 12:16:43

0PPP)p00

• 🦒2

cofacts.github.io

Community Builder

Web site created using create-react-app

Comment on #350 Don't insert friend link to clipboard for logged-in users

I can take a crack at this! :robot_face:

• 🙏1

#353 [#350] Don't insert friend link to clipboard for logged-in users

Addresses Issue <https://github.com/cofacts/rumors-site/issues/350|#350>. Manual test from <http://localhost:3000/article/AVx3hpeZyCdS-nWhuZ8c|this article>: When logged in the copied text is: ``` 消防局提醒民眾，除了打火機外，髮膠、芳香噴霧、防蟲噴霧等高壓縮罐產品，及可能含酒精的芳香劑、香水都不宜放在車內，以免遇高溫產生易燃氣體，造成氣爆或火燒車。 ``` When logged out the copied text is: ``` 消防局提醒民眾，除了打火機外，髮膠、芳香噴霧、防蟲噴霧等高壓縮罐產品，及可能含酒精的芳香劑、香水都不宜放在車內，以免遇高溫產生易燃氣體，造成氣爆或火燒車。 📋 節錄自 Cofacts 真的假的：<http://localhost:3000/article/AVx3hpeZyCdS-nWhuZ8c> 🤔 在 LINE 看到可疑訊息？加「真的假的」好友，查謠言與詐騙 ➡️ <https://line.me/R/ti/p/%40cofacts> ```

• 👍1

mrorz 2020-10-25 00:32:45

「已選擇」確實是滿隱晦的囧

#1 project init

☐ source code ☐ docker ☐ model-config.json

#8 Containerize BoW model

Comment on #8 Containerize BoW model

Use this issue <https://github.com/cofacts/rumors-ai-bow/issues/1|cofacts/rumors-ai-bow#1>

#10 Category mapping

☐ For AI-master Extract hardcoded string and create a JSON file ``` { "cofacts-category-id-0": "elasticsearch-id-0", "cofacts-category-id-1": "elasticsearch-id-1", "cofacts-category-id-2": "elasticsearch-id-2" } ``` ☐ For 3rd model Edit model register API for providing category mapping. Ref <https://github.com/cofacts/rumors-ai/issues/4|#4> `POST /v1/models/` ``` { "name": "my ai model", "realTime": false, "categoryMapping": { "model-self-define-id-0": "cofacts-category-id-0", "model-self-define-id-1": "cofacts-category-id-0", "model-self-define-id-2": ["cofacts-category-id-3", "cofacts-category-id-4"] } } ``` `PATCH /v1/models/{id}` ``` { "categoryMapping": { "model-self-define-id-0": "cofacts-category-id-0", "model-self-define-id-1": "cofacts-category-id-0", "model-self-define-id-2": ["cofacts-category-id-3", "cofacts-category-id-4"] } } ```

#2 Create a guide/pipeline for coming new categories

For adding main category For adding sub-category

#3 Apply category mapping

See <https://github.com/cofacts/rumors-ai/issues/10|cofacts/rumors-ai#10>

#4 Use gcp credentials file to create a GPU instance

#7 Containerize BERT model

Comment on #7 Containerize BERT model

<https://github.com/cofacts/rumors-ai-bert|https://github.com/cofacts/rumors-ai-bert>

#11 Use model via docker

<https://github.com/cofacts/rumors-ai-bert|https://github.com/cofacts/rumors-ai-bert> <https://github.com/cofacts/rumors-ai-bow|https://github.com/cofacts/rumors-ai-bow>

Review on #353 [#350] Don't insert friend link to clipboard for logged-in users

Thanks a million for the fix! Judging from the logic, it seems that when `currentUser` is falsy, the behavior of the application would be identical to built-in copy-paste. I am wondering if `onCopy={currentUser ? undefined : handleCopy}` on components would work. If it works it could be more readable (and `handleCopy` would change less) in my opinion. Also it would be nice if `npm run lint --fix` is run and the lint fix is being committed. That should turn the build green 🟢

#229 TypeError: undefined is not an object (evaluating 't[2][0].cursor')

Happens a few times a day, mostly on iOS. <https://user-images.githubusercontent.com/108608/97099115-3c87d980-16c0-11eb-9f28-5dfe3655370f.png|圖片> View details in Rollbar: <https://rollbar.com/mrorz/rumors-line-bot/items/289/|https://rollbar.com/mrorz/rumors-line-bot/items/289/> ``` TypeError: undefined is not an object (evaluating 't[2][0].cursor') File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in $n File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in Sn File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in ft File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in Tn File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in jn File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in p File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in K File "<https://rumors-line-bot.herokuapp.com/liff/bundle.994e30a1c2cc650ca34b.js>", line 2, in Y File "[native code]", line unknown, in promiseReactionJob ```

#230 [LIFF] Fix UserSetting page ux that shows switch ui after data loaded

Before: <https://user-images.githubusercontent.com/6376572/97142727-2fd8b380-179c-11eb-9140-e0453425a282.gif|https://user-images.githubusercontent.com/6376572/97142727-2fd8b380-179c-11eb-9140-e0453425a282.gif> After: <https://user-images.githubusercontent.com/6376572/97142743-3830ee80-179c-11eb-80ab-378213642278.gif|https://user-images.githubusercontent.com/6376572/97142743-3830ee80-179c-11eb-80ab-378213642278.gif>

Comment on #230 [LIFF] Fix UserSetting page ux that shows switch ui after data loaded

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

Review on #230 [LIFF] Fix UserSetting page ux that shows switch ui after data loaded

Thanks for the change! Reducing the button flicker looks much better!

Comment on #322 Excessive GraphQL calls on server side rendering

I seem to have a similar issue when setting up Material UI SSR + next-i18nnext SSR. The way Apollo detects SSR seems to be broken in certain scenarios when playing too much with React SSR, it might change some internal state

#231 On-boarding tutorial

Fixes <https://github.com/cofacts/rumors-line-bot/issues/216|#216> Text setup in rich menu to trigger tutorial should be: :book: tutorial (en) ~:book: 教學 (zh-tw)~

Comment on #231 On-boarding tutorial

*Pull Request Test Coverage Report for <https://coveralls.io/builds/34506376|Build 1177>* • *40* of *87* *(45.98%)* changed or added relevant lines in *5* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage decreased (*-3.7%*) to *81.315%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

nextjs.org

Next.js 10

Next.js 10 introduces Built-in Image Optimization, Internationalized Routing, Next.js Analytics, React 17 Support, and more!

lucien 2020-10-28 12:02:26

Image 會自己轉 webp

mrorz 2020-10-28 12:32:15

那個超神奇
但我們很少圖片 XDDD

我覺得對我們來說麻煩的東西有
• material-ui 肥肥，SSR 產生 stylesheet 不知道效能如何
• apollo-client 新版可能跟 SSR 有些水土不服，會產生多次 render 與 request （過去的 bug）
目前流量大多都是往文章頁面灌，landing page 等圖多的網頁比較少流量，所以 next10 的東西對我來說沒有太大吸引力

可能在技術上我想處理的問題，會是
• 文章頁面是否有機會可以 statically generated；若可以，那 search engine / crawler 可以超快拿到內容而不會耗 API 資源（但可能有些 outdated）；瀏覽器在 bootstrap 時也可以另外發 request 到 API 拿到最新內容。
• 目前不能 static generate 的最重要問題是 env vars 現在都是 runtime config。我們的 build process (docker cloud) 疑似無法提供 env file，所以無法產生不同 env file 的 auto-build；況且 build-time 決定 env 彈性也比較差

mrorz 2020-10-28 12:34:20

至於 i18n 與導致的 SEO 問題，看起來是應該要加掛 link tag 來解，next10 的那套對我們的 build-time i18n + 不同語言已經分不同 domain 的架構應該沒有太大助益

mrorz 2020-11-13 02:33:27

關於 SEO，我之前有個想法忘記在會議上提出。

大致上的概念是：既然 Google 搜尋不支援 accept-language 自動偵測，那我們一個 domain 就固定用一種語言好。

我提議我們改成
• `cofacts.org`, `cofacts.g0v.tw`, `zh.cofacts.org` 三個 domain 永遠 serve 中文版
• `en.cofacts.org` 永遠 serve 英文版
• 無論是哪個版本，都採用 google 建議，使用 `<link rel="alternate" hreflang="_lang_code_" href="_url_of_page_" />` 指向所有語言
• 在瀏覽器用 `navigator.language` 偵測瀏覽器語言，如果語言與 UI 不同，則顯示一個切換語言的 banner，顯示同一個頁面的不同語言 URL
這樣應該可以讓最長被使用的 cofacts.g0v.tw, cofacts.org 的 <html lang> 在 index 時是受眾最常用的中文，也解決中文首頁 SEO 的問題。

See: https://github.com/cofacts/rumors-site/issues/347#issuecomment-718878471

關於這個變更大家有什麼覺得不妥的嗎～

mrorz 2020-11-13 02:40:03

關於有三個版本都 serve 中文版這件事情，中文版可能要挑一個 URL 當作 canonical URL。

https://developers.google.com/search/docs/advanced/crawling/consolidate-duplicate-urls?hl=zh-Hant&visit_id=637408030503556838-3312092471&rd=1

目前 cofacts.g0v.tw 是被 index 最多的版本，如果換 canonical url 到 cofacts.org 的話，page rank 會掉嗎？

mrorz 2020-11-13 02:41:20

Ohh 原來有網址遷移工具
https://support.google.com/webmasters/answer/9370220?visit_id=637311129679866045-862453801&rd=1

mrorz 2020-11-13 21:33:37

無論是 canonical url 還是 language 都可以用 header 實作
這樣就只要改 rumors-deploy 的 nginx 就可以囉
(其實放 rumors-deploy 也合理，因為 domain 就是在)
不需要改到 rumors-site～

lucien 2020-11-13 21:53:38

會掉page rank吧

lucien 2020-11-13 22:00:02

原來可以用header好神奇，以為只能用meta

mrorz 2020-11-14 02:32:20

我發現 Google 其實不認為只翻譯 UI 字串的網站就多語網站。

> Translating only the boilerplate text of your pages while keeping the bulk of your content in a single language (as often happens on pages featuring user-generated content) can create a bad user experience if the same content appears multiple times in search results with various boilerplate languages.
https://developers.google.com/search/docs/advanced/crawling/managing-multi-regional-sites#make-sure-the-page-language-is-obvious

那我覺得我們還是
1. 把基於 http request header 的自動語言偵測功能拿掉；en.xxx server 英文 UI，其他一律 serve 中文 UI
2. 無論哪個版本的網址，canonical 一律使用 cofacts.org/xxx 避免重複爬取
3. 除了整頁都英文的 landing page 之外，其他頁面都不下 hreflang 標籤了，就通通當中文ㄅ

HackMD

Cofacts 會議記錄 - HackMD

# Cofacts 會議記錄 ## 2020 - [20201028 會議記錄](/n74W64y4RiWIKt1Noxn-Mg) - [20201024 大松](/IzcYlM1PQu-1He

Comment on #231 On-boarding tutorial

Since `Why setup permissions` is more than 20 characters, I suggest we just use `Why`

Comment on #231 On-boarding tutorial

We may need a better place for these images <https://user-images.githubusercontent.com/108608/97395795-a8687d00-1920-11eb-8731-d5239ed1b6c3.png|image>

• 🦒1
• 🐈1

Comment on #231 On-boarding tutorial

Nit: suggest using `reply` and `article` as argument names, and denote that their type is `Reply` and `Article` in rumors-api GraphQL, respectively.

Review on #231 On-boarding tutorial

I have not finish reviewing `handlers/tutorial.js`. Here are some early feedback.

Comment on #231 On-boarding tutorial

Hmm by permission settings I actually meant our existing `settings` page. That's why I also put welcome messages in settings LIFF.

#231 On-boarding tutorial

• ❤️3
• 👍1

Comment on #216 On-boarding tutorial

To wrap up, please finish your permission settings so that I can provide a smoother experience. 現在請你設定「如果你之後問的問題被查證了要回傳給你」，這需要經過你的同意喔！ Why setup permission?” --&gt; 為什麼要同意呢？這要設定什麼？ When I provide hoax-busting replies to you, I would like to ask you for any feedback on the crowd-sourced reply. In order to achieve that, I need to ask for your permission to "send your message to our chatroom". The permission will be used to send only this one message of yours back to this particular chatroom. You can still use Cofacts without granting me this permission. When we ask for feedback from you, the permission dialog will pop-up again. 當我把查到的闢謠回給你的時候，我會請你一起確認「這個機器人沒有答非所問」，有你的幫助與按讚:+1:確認，能讓我學習很多、查得更好。 不過我是個很有禮貌的機器人，我會徵求你的同意讓我傳訊息告訴你：「你剛剛問我的訊息，真的假的聊天機器人 查到了，答案是什麼」。 這個設定可以讓我在幫你查到新訊息的時候告訴你「剛剛你傳的訊息是真的還是假的。」 如果你選擇關閉這個設定，你還是可以問機器人那些別人有問過、或我已經幫別人查過的舊訊息。 如果之後 真的假的 機器人需要請求你的幫忙，再來問你喔！ 4. Thank-you 好喔我懂了！ ":stopwatch: Later" --&gt; 之後再設定吧！ OK. When we ask for feedback from you, the permission dialog will pop-up again. 好的，如果之後 真的假的 機器人需要請求你的幫忙，再來問你喔！ This is the end of the tutorial. Next time when you receive a suspicious message, don't hesitate to forward it to me! :hugging_face: 耶咿～教學結束囉！！ 下次收到可疑的訊息時，就轉傳分享給我幫你查吧！:blush:

#232 Update line content api domain

Reference: <https://developers.line.biz/en/news/2020/10/09/reminder-for-domain-name-change-transition-period/|https://developers.line.biz/en/news/2020/10/09/reminder-for-domain-name-change-transition-period/>

Review on #232 Update line content api domain

Thanks for the timely fix!

Review on #232 Update line content api domain

Comment on #232 Update line content api domain

*Pull Request Test Coverage Report for <https://coveralls.io/builds/34534780|Build 1183>* • *0* of *1* *(0.0%)* changed or added relevant line in *1* file are covered. • No unchanged relevant lines lost coverage. • Overall coverage remained the same at *84.968%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*

Comment on #216 On-boarding tutorial

&gt; In order to achieve that, I need to ask for your permission to "send your message to our chatroom". &gt; The permission will be used to send only this one message of yours back to this particular chatroom. 這兩句其實是在講 <https://github.com/cofacts/rumors-line-bot/issues/174|#174> 的「傳送訊息至聊天室」權限。 因為之前就有發生過<https://www.facebook.com/groups/cofacts/permalink/2672723192959493/|使用者問為什麼要這個「傳送訊息至聊天室」權限>，所以才會有這個說明文字。如果我們不用這個中文字，使用者會不知道我們在解釋什麼。 LINE UI 使用的英文是 "Send messages to chats"，而中文是「傳送訊息至聊天室」，這個部分的說明，英文與中文應該都要跟 LINE 的 UI 一致。 <https://user-images.githubusercontent.com/108608/97530444-1bd7c080-19ed-11eb-9d12-08147a9e374e.png|Screenshot_20201029-134319> <https://user-images.githubusercontent.com/44064051/80186988-790b4780-8641-11ea-8aa5-721316638211.jpg|https://user-images.githubusercontent.com/44064051/80186988-790b4780-8641-11ea-8aa5-721316638211.jpg>

Comment on #216 On-boarding tutorial

To wrap up, please finish your permission settings so that I can provide a smoother experience. 現在請你完成設定，讓機器人的事實查核順利進行喔！ Why setup permission?” --&gt; 為什麼要同意呢？這要設定什麼？ When I provide hoax-busting replies to you, I would like to ask you for any feedback on the crowd-sourced reply. In order to achieve that, I need to ask for your permission to "send your message to our chatroom". The permission will be used to send only this one message of yours back to this particular chatroom. You can still use Cofacts without granting me this permission. When we ask for feedback from you, the permission dialog will pop-up again. 當我把查到的闢謠回給你的時候，我會請你一起確認「這個機器人沒有答非所問」，有你的幫助與按讚:+1:確認，能讓我學習很多、查得更好。 要得到你的「:+1: 」，或是「這回得不好，機器人應該改成oxxxx」所以需要請你許可『傳送訊息至聊天室』。 如果不同意的話，還是可以使用其他功能喔！如果我們需要你幫忙，這個「請求同意」的對話會再次出現。

Comment on #216 On-boarding tutorial

This is the end of the tutorial. Next time when you receive a suspicious message, don't hesitate to forward it to me! :hugging_face: 耶咿～教學結束囉！！ 下次收到可疑的訊息時，就轉傳分享給我幫你查吧！:blush: To wrap up, please finish your permission settings so that I can provide a smoother experience. 現在請你完成設定，讓機器人的事實查核順利進行喔！ Why setup permission?” --&gt; 為什麼要同意呢？這要設定什麼？ When I provide hoax-busting replies to you, I would like to ask you for any feedback on the crowd-sourced reply. In order to achieve that, I need to ask for your permission to "send your message to our chatroom". The permission will be used to send only this one message of yours back to this particular chatroom. You can still use Cofacts without granting me this permission. When we ask for feedback from you, the permission dialog will pop-up again. 當我把查到的闢謠回給你的時候，我會需要跟你對話確認才不會誤會你的意思，所以請幫我選擇許可「傳送訊息至聊天室」 。 一樣只會在 真的假的 的好友帳號裡面，讓你可以查新的謠言。 如果不同意的話，還是可以使用其他功能喔！如果我們需要你幫忙，這個「請求同意」的對話會再次出現。

• 1

#232 Update line content api domain

#230 [LIFF] Fix UserSetting page ux that shows switch ui after data loaded

#5 Decouple rumors-ai-bert from rumors-ai

To see <https://github.com/cofacts/rumors-ai-bert/tree/master/GPU_host|https://github.com/cofacts/rumors-ai-bert/tree/master/GPU_host> <https://github.com/cofacts/rumors-ai-bert/blob/50705367faf152e6628fce705ab93a52e3a304ef/GPU_host/predict_ModelA.sh#L5|rumors-ai-bert/GPU_host/predict_ModelA.sh> Line 5 in &lt;/cofacts/rumors-ai-bert/commit/50705367faf152e6628fce705ab93a52e3a304ef|5070536&gt;

#6 Fix missing file task_handler2.py

`main.py` and `task_handler2.py` <https://github.com/cofacts/rumors-ai-bert/blob/50705367faf152e6628fce705ab93a52e3a304ef/CPU_host/Dockerfile#L30-L39|rumors-ai-bert/CPU_host/Dockerfile> Lines 30 to 39 in &lt;/cofacts/rumors-ai-bert/commit/50705367faf152e6628fce705ab93a52e3a304ef|5070536&gt;

#7 Remove &amp;test=1

<https://github.com/cofacts/rumors-ai-bert/blob/50705367faf152e6628fce705ab93a52e3a304ef/CPU_host/run-scripts/task_handler.py#L25|rumors-ai-bert/CPU_host/run-scripts/task_handler.py> Line 25 in &lt;/cofacts/rumors-ai-bert/commit/50705367faf152e6628fce705ab93a52e3a304ef|5070536&gt;

Comment on #347 SEO for Mandarin content

I have a bold idea: • Drop current `accept-language` detection mechanism: It's not supported by Google. • `<http://cofacts.org|cofacts.org>`, `<http://cofacts.g0v.tw|cofacts.g0v.tw>`, `<http://zh.cofacts.org|zh.cofacts.org>` always connects to Mandarin version; `<http://en.cofacts.org|en.cofacts.org>` always connects to English version. • On browser, when we detect the browser language did not match the currently viewed version, show a banner with a link to the version that their browser supports. • Implement `link` tag pointing to alternative languages In this way, • Google should be able to index Cofacts main site as Mandarin content • Existing URLs exists, so it does not loose page rank • Human users can be still directed to correct language when they follow the link in banner.

• 3

mrorz 2020-10-30 11:48:58

可能是 pycon 或 hitcon 吧

Comment on #227 index user if not existed and log last active time for user accessing apis via backend apps

frontend users are tested with logging in from development frontend, and backend users are tested with ``` curl "<http://localhost:5000/graphql?userId=$USERID>" -H 'Accept-Encoding: gzip, deflate, br' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'Connection: keep-alive' -H 'DNT: 1' -H 'Origin: <http://localhost:5000>' -H "x-app-secret:$SECRET" --data-binary '{"query":"query {\n GetUser{\n \tid\n \tname\n avatarUrl\n level\n }\n}"}' --compressed ```