cofacts

Month: 2021-12

2021-12-01

mrorz 13:56:15
今日會議記錄
主要更新 category review 與 user blocking 的進度
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FTEbULkjbSE-3GDyk-Whj2A
cai 21:25:24
廣告XD
https://cofacts.tw/article/2qxten4kau5sm
感謝
中午處理
`4KRgbn0BnX5-aOa4TGYG` , `朱婷`
zhengchun88 那個是之前已經阻擋的唷
已經處理完畢囉
https://cofacts.tw/article/1arrj5q55yey 奇怪,zhengchun88 不是擋過了,怎麼又浮上來

2021-12-02

github2 12:06:51

<https://github.com/cofacts/rumors-site/pull/433#issuecomment-984273812|Comment on #433 Bump lodash from 4.17.19 to 4.17.21>

<https://coveralls.io/builds/44697141|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/9e80aafee22822c8a6d6b636ce013abb1efc01dd|9e80aaf> on dependabot/npm_and_yarn/lodash-4.17.21* into *<https://github.com/cofacts/rumors-site/commit/20c9b0b611e46a18453c9aefb928bf9307735fc9|20c9b0b> on master*.

2021-12-03

mrorz 13:42:52
發現原來有食藥膨風廣告專區
打入關鍵字,果然看到令人熟悉的名字 wwwwwww
image.png
太好笑了😂
😆 2

2021-12-04

cai 00:16:38
紀錄一下,剛好google 到判決書,但是在cofacts上丟判決書會不會太誇張 😆
臺灣高等法院 臺南分院 109 年度上訴字第 1481 號刑事判決

https://cofacts.tw/article/2w6g9sk37gshe
https://cofacts.tw/article/3mmczh4159bkn
image.png
我覺得超有說服力!

「上一個聽信這種說詞的人,已經變成了被告,判決書在這。」
(不過其實量刑應該是每案不同啦,這一案看來是因為已經知道自己是車手,卻在犯後否認對方是詐騙集團,被法官認定犯後態度難謂良好)
不過也因為被告上訴、才有機會讓法官把更詳細的對話紀錄當成事證寫進判決書,也讓我們發現這套台詞,詐騙集團 2021 年還在拿來用⋯⋯
喔喔這個是把印章存摺交給對方的版本
第一層是這種人頭帳戶
第二層才是下面的車手
😮 2 1 3 3 1
github2 18:04:43

<https://github.com/cofacts/rumors-site/pull/458|#458 Handle SSG case>

<https://github.com/cofacts/rumors-site/actions/runs/1529029608|Previous image build> fails due to the server-side cookie logic introduced in <https://github.com/cofacts/rumors-site/pull/457|#457> . This PR fixes the build by properly handle SSG case, which will have undefined ctx.req.

:white_check_mark: All checks have passed

github2 18:06:31

<https://github.com/cofacts/rumors-site/pull/458#issuecomment-986002666|Comment on #458 Handle SSG case>

<https://coveralls.io/builds/44758658|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/7ef839a755b966fd49b5cdcd53a830f69a807a21|7ef839a> on fix-build* into *<https://github.com/cofacts/rumors-site/commit/20c9b0b611e46a18453c9aefb928bf9307735fc9|20c9b0b> on master*.

cai 20:26:50
https://cofacts.tw/article/1u1qxmpk4wlah 前幾天新聞不是才說新的社群交易詐騙是用line pay 現在變成求職寫用line pay付😆
165 詐騙line ID是有個很像的 fz20233
我開始在想
如果人會聽信這些「工作機會」是因為有工作需求
丟一些勞動部的就業服務之類的東西會不會有幫助 XD
是因為可以在家工作吧?
Hmmm 那這樣就難了

2021-12-05

nonumpa 16:25:59
發現有人送了十幾二十則無意義文章進資料庫..
以為回完了,結果往下看還有一堆😮‍💨
Screenshot_20211205-162422.png
不對,超過30則!
這情況至少有兩週了吧~
好奇 userId 是不是同一個
是的話就可以用古老的 blacklist 機制擋起來
發現找了一下,發現這個狀況有點複雜

這些確實是同一個 LINE 使用者(ID: `j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU` )送進資料庫的。

GraphQL playground 用這個 query 可以看他送進來的訊息,截至目前有 400 多篇:
```{
ListArticles(filter: {userId: "j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU"}, first: 200) {
edges {
node {
text
createdAt
}
}
totalCount
}
}```
但這個使用者同時也有對 78 篇回應按「覺得有用」
GraphQL playground 用這個 query 可以看他按讚的回應:
```{
ListArticleReplyFeedbacks (filter: {userId: "j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU"}, first: 200) {
edges {
node {
article {
id
text
}
reply {
text
}
score
comment
}
}
totalCount
}
}```
不知道大家有什麼想法呢 QQ
他大概把linebot 當成資安百科全書了吧
😮 1

2021-12-06

github2 02:02:42

<https://github.com/cofacts/rumors-api/pull/271|#271 Flow tag import script>

Discussion: "若水 ground truth" in <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FlYTN-n1xQyqlHB9oeaPvuQ|https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FlYTN-n1xQyqlHB9oeaPvuQ> This PR implements migration script, `importFlowAnnotation.js`, that imports ground truth data from Flow annotators (<https://github.com/cofacts/ground-truth/blob/main/20211204_14859.zip|https://github.com/cofacts/ground-truth/blob/main/20211204_14859.zip>) to database by: 0. Map 0~16 (Flow's annotation) to actual category ID used in database 1. Create (or update) app user ID=`category-reviewer` and user ID=`flow-annotator` in `users` index • `genCategoryReview` is also updated so that it will look for previous reviewer feedback using the ID in `users` index 2. add article category (using app `RUMORS_AI` and app user ID "flow-annotator") if the article category is not existed yet • If there exists a deleted matching article category, the article category status will become `NORMAL` and article category author will switch to `flow-annotator` -- this is the existing behavior of `createArticleCategory`. 3. add positive feedback (using app `RUMORS_AI` and app user ID `category-reviewer`) • so that the article-category will be selected by <https://g0v.hackmd.io/EcrdwfZrQOSTGX7yK6nn4w#Script-2-genBERTInputArticles-script-in-rumors-api|script 2> if no further downvotes exist This PR also does the following refactor: • Simplify `createArticleCategory()` argument: use article ID instead of article instance, since only ID is actually used • Extract `createOrUpdateArticleCategoryFeedback()` from the resolver so that migration script (and script 2 in the future) can call it

:white_check_mark: All checks have passed

github2 02:04:44

<https://github.com/cofacts/rumors-api/pull/271#issuecomment-986274548|Comment on #271 Flow tag import script>

<https://coveralls.io/builds/44767051|Coverage Status> Coverage increased (+0.5%) to 86.847% when pulling *<https://github.com/cofacts/rumors-api/commit/9c2f86c655fe1cad04ef9a7537d95b777b8a0bd6|9c2f86c> on flow-tag-importer* into *<https://github.com/cofacts/rumors-api/commit/3bfbac6a62c588e740e6aac52d23ff901f6e58e5|3bfbac6> on master*.

2021-12-07

cai 20:16:58
發現了個問題⁉️
我這篇是`不在查證範圍`,網頁上沒有顯示佐證
https://cofacts.tw/article/3crj7x264puuv

但是 linebot 會把我當初放在佐證資料那欄沒刪掉的送出去欸 😮
註解 2021-12-07 201400.png
確實應該算 bug XD
就是 UI 藏起來但實際上還是寫入資料庫惹

2021-12-08

isabelhou 14:32:13
cofacts的大家,之前有請大家預留12/18時間參加FtO,但因為12月活動實在太多,所以要延期至1月,非常抱歉。
1
cai 19:35:01
https://cofacts.tw/reply/IaSlmX0BnX5-aOa4CXYX 簡體字來講封鎖不特別嚴重😆

2021-12-09

github2 08:18:12

<https://github.com/cofacts/rumors-site/pull/459|#459 Bump next from 9.3.2 to 11.1.3>

Bumps <https://github.com/vercel/next.js|next> from 9.3.2 to 11.1.3. Release notes _Sourced from <https://github.com/vercel/next.js/releases|next's releases>._ &gt; *v11.1.3* &gt; &gt; See <https://github.com/vercel/next.js/releases/v12.0.5|https://github.com/vercel/next.js/releases/v12.0.5> for details about this patch. &gt; &gt; *v11.1.3-canary.105* &gt; *Core Changes* &gt; &gt; • Update swc-minify-enabled link: <https://github-redirect.dependabot.com/vercel/next.js/issues/30290|#30290> &gt; • Fix middleware header propagation: <https://github-redirect.dependabot.com/vercel/next.js/issues/30288|#30288> &gt; • Move outputFileTracing config up: <https://github-redirect.dependabot.com/vercel/next.js/issues/30295|#30295> &gt; • Track usage of swc features: <https://github-redirect.dependabot.com/vercel/next.js/issues/30297|#30297> &gt; • Ensure null bytes in resolved path are handled: <https://github-redirect.dependabot.com/vercel/next.js/issues/30313|#30313> &gt; • Improve deprecation errors for new middleware API: <https://github-redirect.dependabot.com/vercel/next.js/issues/30316|#30316> &gt; &gt; *Documentation Changes* &gt; &gt; • Add more docs.: <https://github-redirect.dependabot.com/vercel/next.js/issues/30320|#30320> &gt; &gt; *Example Changes* &gt; &gt; • Update image component example to use AVIF: <https://github-redirect.dependabot.com/vercel/next.js/issues/30294|#30294> &gt; &gt; *Credits* &gt; &gt; Huge thanks to <https://github.com/ijjk|`@​ijjk`>, <https://github.com/styfle|`@​styfle`>, <https://github.com/padmaia|`@​padmaia`>, <https://github.com/javivelasco|`@​javivelasco`>, and <https://github.com/leerob|`@​leerob`> for helping! &gt; &gt; *v11.1.3-canary.104* &gt; *Misc Changes* &gt; &gt; • Add necessary workflow job dependencies: <https://github-redirect.dependabot.com/vercel/next.js/issues/30291|#30291> &gt; &gt; *v11.1.3-canary.103* &gt; *Core Changes* &gt; &gt; • Warn when mutating res if not streaming: <https://github-redirect.dependabot.com/vercel/next.js/issues/30284|#30284> &gt; • Chore/publish all swc: <https://github-redirect.dependabot.com/vercel/next.js/issues/30289|#30289> &gt; &gt; *Credits* &gt; &gt; Huge thanks to <https://github.com/kara|`@​kara`> for helping! &gt; &gt; *v11.1.3-canary.102* &gt; *Core Changes* &gt; &gt; • Add warning when LCP image is missing `priority` prop: <https://github-redirect.dependabot.com/vercel/next.js/issues/30221|#30221> &gt; • New Middleware API signature: <https://github-redirect.dependabot.com/vercel/next.js/issues/30282|#30282> &gt; • Fix trace case with tsconfig/jsconfig baseUrl: <https://github-redirect.dependabot.com/vercel/next.js/issues/30286|#30286> &gt; &gt; *Documentation Changes* ... (truncated) Commits • <https://github.com/vercel/next.js/commit/ec1a0f7643172e5beba96e7be7d000471813cf69|`ec1a0f7`> v11.1.3 • <https://github.com/vercel/next.js/commit/4dc9bba59b5c4f1d49d9a7b2662c21f225cbd38e|`4dc9bba`> Add no-verify-access for lerna • <https://github.com/vercel/next.js/commit/e314019e987e9bfcc7c8cf6cb7bf6c005521a3f6|`e314019`> use correct token • <https://github.com/vercel/next.js/commit/1a40e71a5ef6b906a5871c1deab6c79b5118189a|`1a40e71`> fix lint • <https://github.com/vercel/next.js/commit/b01acc1b1a5ede2840023bfc3aaedd7415cb8aec|`b01acc1`> Update branch name to next-11 • <https://github.com/vercel/next.js/commit/66de88d9dc2e8f58d392a694eb8833bce7d43c80|`66de88d`> Use next-11 tag • <https://github.com/vercel/next.js/commit/303bc0f94d8f3bb809a1eed14ddcaf15bc915a14|`303bc0f`> Allow publishing on v11-patch branch • <https://github.com/vercel/next.js/commit/f59c82b53fabfb3a07184816d3949f9553aaf44d|`f59c82b`> Enable GitHub actions for v11-patch branch • <https://github.com/vercel/next.js/commit/48887132d12075dc8a8b6ac7ad3658d1a5088e88|`4888713`> Ensure invalid URLs respond with 400 correctly • <https://github.com/vercel/next.js/commit/97456e81ce9860ce8b4bb58931b8d723d312d389|`97456e8`> v11.1.2 • Additional commits viewable in <https://github.com/vercel/next.js/compare/v9.3.2...v11.1.3|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~vercel-release-bot|vercel-release-bot>, a new releaser for next since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-site/network/alerts|Security Alerts page>.

:white_check_mark: All checks have passed

github2 08:20:28

<https://github.com/cofacts/rumors-site/pull/459#issuecomment-989334349|Comment on #459 Bump next from 9.3.2 to 11.1.3>

<https://coveralls.io/builds/44867865|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/247941987441274172e2f60d667dcae4c74a321b|2479419> on dependabot/npm_and_yarn/next-11.1.3* into *<https://github.com/cofacts/rumors-site/commit/73063753bbf89b02cf8e58728a4213f156c3779b|7306375> on master*.

cai 14:26:52
佐證那欄 如果連結>5,連結預覽會變成一直轉圈圈?
跟數量無關耶
主要是看後面 url-resolver 是否有正常 resolve 出 URL
如果有 error 的話,就算連結數 <5 也會一直轉圈圈
github2 23:06:37

<https://github.com/cofacts/rumors-api/pull/272#issuecomment-989937781|Comment on #272 2nd script of category review>

Production execution result &gt; node_modules/.bin/babel-node -- src/scripts/genBERTInputArticles.js -s 1Y9FrI01in2hz5eiveGknH0HE081sr7gVuk0a7hqqKuc -o 20211128-production &gt; Writing feedbacks to database &gt; progress [========================================] 100% | ETA: 0s | 2989/2989 &gt; 2211 positive feedbacks &amp; 131 negative feedbacks have been written. &gt; Scanning through 14910 matching articles &gt; progress [========================================] 100% | ETA: 0s | 14910/14910

2021-12-10

github2 01:27:56

<https://github.com/cofacts/rumors-api/pull/272#issuecomment-990063257|Comment on #272 2nd script of category review>

Run again on production DB &amp; new review category to include Flow's ground truth labels added in 12/06. &gt; $ node_modules/.bin/babel-node -- src/scripts/genBERTInputArticles.js -s 1E6S_wYkRIEgItKKnZyaXVBejiwYCS67qvtJ4u3YoFq8 -o ../groundtruth/20211209-production &gt; Writing feedbacks to database &gt; progress [========================================] 100% | ETA: 0s | 476/476 &gt; 318 positive feedbacks &amp; 61 negative feedbacks have been written. &gt; Scanning through 17111 matching articles &gt; progress [========================================] 100% | ETA: 0s | 17111/17111

mrorz 11:08:06
letsencrypt cronjob 怪怪的
要檢查一下 cert 為啥沒更新
image.png
mrorz 11:08:43
cofacts.tw, cofacts.org 與 chatbot 不受影響
kiang 11:22:54
有人在聊憑證問題了
https://www.facebook.com/groups/rayforum/permalink/4588227991257323/

facebook.com

Log in or sign up to view

See posts, photos and more on Facebook.

mrorz 11:52:45
但我今天白天不在電腦前
晚上準備明天大松材料時抓時間研究一下 log
mrorz 11:58:16
是說 #status 的 status cake 原來不會報 cert error 嗎 @@
mrorz 20:27:27
恢復囉!結果是 nginx reload 問題。

剛才研究了一陣:
cofacts-api.g0v.twcofacts.g0v.tw 的 certbot & letsencrypt 都很正常的在每週六跑起來
• 最近一次的 cofacts-api.g0v.tw 換到了明年 3 月的 cert;cofacts.g0v.tw 則在 11 月的時候換到了明年 2 月的 cert。
• 不過,在我 reload nginx 之前,cofacts-api.g0v.tw 的 cert 是今年 12/31 到期,而 cofacts.g0v.tw 的則是今天已經到期。
• 可以得知問題在於 `nginx -s reload` 失敗。但是,我遍尋不著 nginx reload 失敗的 log。
• 我進 nginx 的 docker 跑 `nginx -t`,configuration 沒有 error 可以成功讀取。
• 我在 docker host machine 複製貼上 cronjob 裡 reload nginx 的指令執行,nginx reload 完全沒有 error,並且也成功地更新了 cofacts-api.g0v.twcofacts.g0v.tw 的 cert。
結果我現在還是不知道為啥 nginx 會重啟失敗。
我之前碰到一個情況是因為 nginx 分成 master 和 worker process, certbot 在停止 nginx 時沒有兩種都停止所以無法執行更新,不知道有沒有關聯。
喔喔但我們的 certbot 是在 docker 裡,nginx 是在另一個 docker
我是 cron job 裡在 certbot 跑起來 5min 後再 docker exec nginx nginx -s reload 之類
嗯嗯了解,這樣架構的話我就沒經驗了XD
😮 2
mrorz 20:30:26
Cronjob:
> 0 0 * * 6 cofacts.g0v.tw 更新ㄉ指令 >> /var/log/cron.log 2>&1
> 5 0 * * 6 cofacts-api.g0v.tw 更新ㄉ指令 >> /var/log/cron.log 2>&1
> 0 1 * * 6 cd /home/docker/rumors-deploy; /usr/local/bin/docker-compose exec nginx nginx -s reload >> /var/log/cron.log 2>&1
mrorz 20:54:43
是說 Cofacts 上有針對「公投綁大選」的訊息ㄇ
沒印象

2021-12-11

mrorz 12:04:12
發現找了一下,發現這個狀況有點複雜

這些確實是同一個 LINE 使用者(ID: `j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU` )送進資料庫的。

GraphQL playground 用這個 query 可以看他送進來的訊息,截至目前有 400 多篇:
```{
ListArticles(filter: {userId: "j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU"}, first: 200) {
edges {
node {
text
createdAt
}
}
totalCount
}
}```
但這個使用者同時也有對 78 篇回應按「覺得有用」
GraphQL playground 用這個 query 可以看他按讚的回應:
```{
ListArticleReplyFeedbacks (filter: {userId: "j4S8C_24YlntPNmT7oLyET-7Ae4rkjPnGyKnOS--HaDh7vGxU"}, first: 200) {
edges {
node {
article {
id
text
}
reply {
text
}
score
comment
}
}
totalCount
}
}```
不知道大家有什麼想法呢 QQ
github2 12:54:53

<https://github.com/cofacts/rumors-site/pull/460|#460 Fix editor RWD breakpoints #363>

edit breakpoints and css

:white_check_mark: All checks have passed

github2 13:04:01

<https://github.com/cofacts/rumors-site/pull/460#issuecomment-991465343|Comment on #460 Fix editor RWD breakpoints #363>

<https://coveralls.io/builds/44930739|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/7e76c3bafe785e42a36f10ec93bf7ee3107d7340|7e76c3b> on Young-TW:master* into *<https://github.com/cofacts/rumors-site/commit/73063753bbf89b02cf8e58728a4213f156c3779b|7306375> on cofacts:master*.

github2 13:19:00

Review on #460 Fix editor RWD breakpoints #363

Thanks a million for locating the root cause and fix the misaligned breakpoints! :tada: I found that the misaligned breakpoints also exist in `ReferenceInput` as well. *Desktop* <https://user-images.githubusercontent.com/108608/145664852-18e1f5ef-ed9a-4e9c-8de8-6f0d0dcfca48.png|圖片> *Tablet size (incorrect)* <https://user-images.githubusercontent.com/108608/145664922-61243f29-6706-44fc-932c-c9d6eab47310.png|圖片> Also the border of textarea is missing. With the information you give as you digging into this issue, I am able to fix the errors above real quick in a following PR. Kudos to <https://github.com/Young-TW|@Young-TW> for the analysis and the fix!

github2 13:48:55

<https://github.com/cofacts/rumors-site/pull/461|#461 NewReplySection border &amp; display fix>

Extends <https://github.com/cofacts/rumors-site/pull/460|#460> to fix reference input quirks &amp; textarea borders on tablet size. *Screenshot* <https://user-images.githubusercontent.com/108608/145665707-de40ba4a-db13-45bf-8297-f6c27c8c3282.gif|fix-border>

:white_check_mark: All checks have passed

github2 13:50:45

<https://github.com/cofacts/rumors-site/pull/461#issuecomment-991471804|Comment on #461 NewReplySection border &amp; display fix>

<https://coveralls.io/builds/44930924|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/787bfb6c9cbab5bb3428e512ddd9524588f59b64|787bfb6> on fix-border* into *<https://github.com/cofacts/rumors-site/commit/0d67a1fddc1e1142ab70f30f0069a483b5c01a91|0d67a1f> on master*.

github2 13:57:09

<https://github.com/cofacts/rumors-site/issues/462|#462 Add introductary youtube video to Tutorial page>

From: <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ|https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ> Put this <https://www.youtube.com/watch?v=WfdfB7GyqMY|https://www.youtube.com/watch?v=WfdfB7GyqMY> in this <https://cofacts.tw/about|https://cofacts.tw/about> <https://user-images.githubusercontent.com/108608/145665971-0615598b-2c9b-4a47-9ec9-f367580a1a33.png|圖片> Width: align with container Height: make it proportional (Around 16:9) across all sizes

github2 14:12:02

<https://github.com/cofacts/rumors-site/issues/463|#463 Tell editors to not reply other's reply>

From <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ|https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ> In the the article page, when there are already replies to the article, add a sentence in editor's textarea placeholder text. <https://user-images.githubusercontent.com/108608/145666203-162e0ee4-7769-40fa-8a7b-43cace07df6b.png|圖片> &gt; Note: Please write your reply in response to the reported message above, NOT to other editor's replies below! It is very likely that your audience will not read other's reply before reading yours. &gt; 注意:這裏不是討論區!請針對上面的「可疑訊息」撰寫回覆,不要去回覆下面的查核回應。若現有查核回應不夠好,請使用該篇回應下方的「倒讚」按鈕 &gt; (回應請附上可靠出處)

github2 15:06:36

<https://github.com/cofacts/rumors-site/issues/363#issuecomment-991500537|Comment on #363 Fix editor RWD breakpoints>

&gt; <https://github.com/MrOrz|@MrOrz> can close this issue? :ok_hand: :ok_hand: :ok_hand: <https://user-images.githubusercontent.com/108608/145667829-926bf7a6-8ae1-4061-b904-537d5e9baba3.png|圖片>

github2 15:29:04

<https://github.com/cofacts/rumors-site/pull/464|#464 [AppLayout][LandingPage] change forum links to tutorial>

Discussion: <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ|https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ> This PR replaces the original "Forum" link in app header &amp; app sidebar to tutorial. • Landing page: "Forum" link changed to "Tutorial" and point to how-to-check-rumors tutorial (`/tutorial?tab=check-rumors`) • Inside application: "Forum link" in app header &amp; sidebar changed to "Tutorial" pointing to fact-checking tutorial. • Add tutorial link to footer. (`/tutorial`) *Landing page* <https://user-images.githubusercontent.com/108608/145668429-86a822fb-0c76-4847-a66d-245e295be807.png|圖片> *Inside application* *Desktop header* <https://user-images.githubusercontent.com/108608/145668292-16afcbd7-8c28-405a-82f7-e8301e15f720.png|圖片> *Mobile sidebar* <https://user-images.githubusercontent.com/108608/145668306-d9789406-e961-4823-8d68-b61345305706.png|圖片> *Footer* <https://user-images.githubusercontent.com/108608/145668347-57910c8a-e4c6-4d2d-8222-da855c1f222e.png|圖片>

:white_check_mark: No checks have passed

github2 16:32:13

<https://github.com/cofacts/rumors-site/pull/464#issuecomment-991540537|Comment on #464 [AppLayout][LandingPage] change forum links to tutorial>

<https://coveralls.io/builds/44931563|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/0c0aeba0add7f87daf009033feed86bfcb8c7220|0c0aeba> on tutorial-link* into *<https://github.com/cofacts/rumors-site/commit/0d67a1fddc1e1142ab70f30f0069a483b5c01a91|0d67a1f> on master*.

Leopold緯哲 23:48:11
@chelee0510 has left the channel

2021-12-12

Teemo 00:24:13
@teemocogs has joined the channel
github2 23:32:29

<https://github.com/cofacts/rumors-site/pull/465|#465 Tell editors to not reply other's reply>

Fixes <https://github.com/cofacts/rumors-site/issues/463|#463> . *0 replies* No extra hint when there is no reply <https://user-images.githubusercontent.com/108608/145718428-93e6cc6d-252a-4382-a318-840cfef794b2.png|image> *Have existing reply* Hint user to not reply other's reply when there is another reply <https://user-images.githubusercontent.com/108608/145718442-8340fc69-e896-4ada-81a5-6172ad0c863d.png|image> This PR also translates the header text of comment section <https://user-images.githubusercontent.com/108608/145718626-6100caaa-55f7-4088-a36e-8979f297e5ae.png|image>

:white_check_mark: All checks have passed

github2 23:34:14

<https://github.com/cofacts/rumors-site/pull/465#issuecomment-991919065|Comment on #465 Tell editors to not reply other's reply>

<https://coveralls.io/builds/44939010|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/7abaf1ceddc19a54246e81d622528324f7d33de6|7abaf1c> on multi-reason-hint* into *<https://github.com/cofacts/rumors-site/commit/e4f24b2c3c9d22a85ff27a67e5f7d40aa78d5413|e4f24b2> on master*.

2021-12-13

cai 13:23:18
tutorial 還是英文
Screenshot 2021-12-13 at 13-21-49 Cofacts 真的假的 - 訊息回報機器人與查證協作社群.png
Will be fixed in this PRL:
Fix released yesterday 🚀
mrorz 21:42:32
關於那個很紅的 log4j RCE,我們有用到的是 elastic search 6

https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476
> Elasticsearch 6 and 7 are not susceptible to remote code execution with this vulnerability due to our use of the Java Security Manager. Investigation into Elasticsearch 5 is ongoing. Elasticsearch running on JDK8 or below is susceptible to an information leak via DNS which is fixable by the JVM property identified below. The JVM option identified below is effective for Elasticsearch versions 5.5+, 6.5+, and 7+. Soon we will make available Elasticsearch 6.8.21 and 7.16.1 which will set the JVM option identified below and remove the vulnerable Log4j component out of an abundance of caution.
>
看起來好像還好 ._.
我們的 ES 其實是 6 的一個比較舊的版本,我猜不用管那個 DNS info leak?
lucien 22:33:53
最近發現nifi似乎是個比較容易導入的ETL,auto label 跟 ocr flow 整理或許之後可以考慮
https://ithelp.ithome.com.tw/m/articles/10281489?sc=iThelpR

ithelp.ithome.com.tw

iT 邦幫忙::一起幫忙解決難題,拯救 IT 人的一天

iT 邦幫忙是 IT 領域的技術問答與分享社群,透過 IT 人互相幫忙,一起解決每天面臨的靠北時刻。一起來當 IT 人的超級英雄吧,拯救下一個卡關的 IT 人

👍 2
lotifv 23:52:54
@lotifv has joined the channel

2021-12-14