#cofacts

2021-12-01
mrorz 13:56:15
今日會議記錄
主要更新 category review 與 user blocking 的進度
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FTEbULkjbSE-3GDyk-Whj2A
github2 19:56:29
<https://github.com/cofacts/rumors-api/pull/265|#265 Review category>
github2 20:15:04
Review on #457 Blocked user's cookie setup
github2 20:15:21
Review on #265 Review category
github2 20:43:48
Review on #457 Blocked user's cookie setup
cai 21:25:24
廣告XD
https://cofacts.tw/article/2qxten4kau5sm
mrorz 2021-12-02 12:00:54
感謝
中午處理
`4KRgbn0BnX5-aOa4TGYG` , `朱婷`
mrorz 2021-12-02 13:19:30
zhengchun88 那個是之前已經阻擋的唷
mrorz 2021-12-02 14:20:19
已經處理完畢囉
cai 2021-12-03 18:52:05
https://cofacts.tw/article/1arrj5q55yey 奇怪，zhengchun88 不是擋過了，怎麼又浮上來
2021-12-02
mrorz 12:00:54
感謝
中午處理
`4KRgbn0BnX5-aOa4TGYG` , `朱婷`
github2 12:01:38
<https://github.com/cofacts/rumors-api/pull/269|#269 Expose user blockage information>
github2 12:02:10
<https://github.com/cofacts/rumors-api/pull/265|#265 Review category>
github2 12:02:47
<https://github.com/cofacts/rumors-site/pull/457|#457 Blocked user's cookie setup>
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*.
mrorz 13:19:30
zhengchun88 那個是之前已經阻擋的唷
github2 13:26:37
<https://github.com/cofacts/takedowns/pull/27|#27 Remove 2nd spammer>
github2 13:33:05
Review on #27 Remove 2nd spammer
github2 13:41:28
<https://github.com/cofacts/takedowns/pull/27|#27 Remove 2nd spammer>
  • 👌1
mrorz 14:20:19
已經處理完畢囉
2021-12-03
mrorz 13:42:52
發現原來有食藥膨風廣告專區
打入關鍵字，果然看到令人熟悉的名字 wwwwwww
image.png
  • 😆2
nonumpa 2021-12-03 14:17:03
太好笑了😂
nonumpa 14:17:03
太好笑了😂
cai 18:52:05
https://cofacts.tw/article/1arrj5q55yey 奇怪，zhengchun88 不是擋過了，怎麼又浮上來
2021-12-04
cai 00:16:38
紀錄一下，剛好google 到判決書，但是在cofacts上丟判決書會不會太誇張 😆
臺灣高等法院 臺南分院 109 年度上訴字第 1481 號刑事判決

https://cofacts.tw/article/2w6g9sk37gshe
https://cofacts.tw/article/3mmczh4159bkn
image.png
  • 😮2
  • 1
  • 3
  • 3
  • 1
mrorz 2021-12-04 01:54:33
我覺得超有說服力！

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

「上一個聽信這種說詞的人，已經變成了被告，判決書在這。」
mrorz 02:17:30
(不過其實量刑應該是每案不同啦，這一案看來是因為已經知道自己是車手，卻在犯後否認對方是詐騙集團，被法官認定犯後態度難謂良好)
mrorz 02:25:28
不過也因為被告上訴、才有機會讓法官把更詳細的對話紀錄當成事證寫進判決書，也讓我們發現這套台詞，詐騙集團 2021 年還在拿來用⋯⋯
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*.
github2 19:08:55
<https://github.com/cofacts/rumors-site/pull/458#issuecomment-986010266|Comment on #458 Handle SSG case>
Build pass &amp; works on staging, will directly merge
github2 19:08:59
<https://github.com/cofacts/rumors-site/pull/458|#458 Handle SSG case>
cai 20:26:50
https://cofacts.tw/article/1u1qxmpk4wlah 前幾天新聞不是才說新的社群交易詐騙是用line pay 現在變成求職寫用line pay付😆
cai 2021-12-04 23:07:34
165 詐騙line ID是有個很像的 fz20233
mrorz 2021-12-05 13:12:27
我開始在想
如果人會聽信這些「工作機會」是因為有工作需求
丟一些勞動部的就業服務之類的東西會不會有幫助 XD
cai 2021-12-05 13:30:20
是因為可以在家工作吧？
mrorz 2021-12-06 11:26:25
Hmmm 那這樣就難了
cai 23:07:34
165 詐騙line ID是有個很像的 fz20233
2021-12-05
mrorz 13:12:27
我開始在想
如果人會聽信這些「工作機會」是因為有工作需求
丟一些勞動部的就業服務之類的東西會不會有幫助 XD
cai 13:30:20
是因為可以在家工作吧？
nonumpa 16:25:59
發現有人送了十幾二十則無意義文章進資料庫..
以為回完了，結果往下看還有一堆😮‍💨
Screenshot_20211205-162422.png
  • 😮1
nonumpa 2021-12-05 16:29:33
不對，超過30則！
cai 2021-12-05 16:43:50
這情況至少有兩週了吧~
mrorz 2021-12-06 11:25:32
好奇 userId 是不是同一個
mrorz 2021-12-06 11:28:39
是的話就可以用古老的 blacklist 機制擋起來
mrorz 2021-12-11 12:04:12
發現找了一下，發現這個狀況有點複雜

這些確實是同一個 LINE 使用者（ＩＤ： `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
cai 2021-12-11 12:56:54
他大概把linebot 當成資安百科全書了吧
nonumpa 16:29:33
不對，超過30則！
cai 16:43:50
這情況至少有兩週了吧~
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*.
github2 10:33:50
Review on #271 Flow tag import script
mrorz 11:25:32
好奇 userId 是不是同一個
mrorz 11:26:25
Hmmm 那這樣就難了
mrorz 11:28:39
是的話就可以用古老的 blacklist 機制擋起來
github2 22:39:18
<https://github.com/cofacts/rumors-api/pull/271|#271 Flow tag import script>
2021-12-07
github2 17:35:21
<https://github.com/cofacts/takedowns/pull/28|#28 Remove 2nd scammer>
github2 19:30:39
Review on #28 Remove 2nd scammer
cai 20:11:50
https://cofacts.tw/article/2wyz4b01wavbb
這篇的劉佳佳那則 有放進廣告名單了嗎？
cai 2021-12-07 21:05:26
https://cofacts.tw/article/12sxpneo4yfss
line id 還故意取反詐165......
mrorz 2021-12-08 01:09:17
是新人唷
感謝
cai 2021-12-13 22:36:06
https://cofacts.tw/article/3d99rhuro3wfp
新人
看來也是每周一新增
mrorz 2021-12-14 12:36:49
感謝回報
等等處理
cai 20:16:58
發現了個問題⁉️
我這篇是`不在查證範圍`，網頁上沒有顯示佐證
https://cofacts.tw/article/3crj7x264puuv

但是 linebot 會把我當初放在佐證資料那欄沒刪掉的送出去欸 😮
註解 2021-12-07 201400.png
mrorz 2021-12-08 01:07:24
確實應該算 bug XD
就是 UI 藏起來但實際上還是寫入資料庫惹
cai 21:05:26
https://cofacts.tw/article/12sxpneo4yfss
line id 還故意取反詐165......
2021-12-08
github2 01:06:39
<https://github.com/cofacts/takedowns/pull/28|#28 Remove 2nd scammer>
mrorz 01:07:24
確實應該算 bug XD
就是 UI 藏起來但實際上還是寫入資料庫惹
mrorz 01:09:17
是新人唷
感謝
github2 01:18:18
<https://github.com/cofacts/takedowns/pull/29|#29 Delete 2nd scammer>
github2 01:20:49
Review on #29 Delete 2nd scammer
github2 01:29:09
<https://github.com/cofacts/takedowns/pull/29|#29 Delete 2nd scammer>
github2 14:12:23
<https://github.com/cofacts/rumors-api/pull/272|#272 2nd script of category review>
mrorz 14:15:05
今日議程
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F-G9Md9IyQauRoalIXJgenQ
isabelhou 14:32:13
cofacts的大家，之前有請大家預留12/18時間參加FtO，但因為12月活動實在太多，所以要延期至1月，非常抱歉。
  • 1
github2 14:33:09
Review on #272 2nd script of category review
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，連結預覽會變成一直轉圈圈？
mrorz 2021-12-09 17:31:56
跟數量無關耶
主要是看後面 url-resolver 是否有正常 resolve 出 URL
如果有 error 的話，就算連結數 <5 也會一直轉圈圈
mrorz 17:31:56
跟數量無關耶
主要是看後面 url-resolver 是否有正常 resolve 出 URL
如果有 error 的話，就算連結數 <5 也會一直轉圈圈
github2 22:52:53
<https://github.com/cofacts/rumors-api/pull/272|#272 2nd script of category review>
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 09:48:04
喔喔這個是把印章存摺交給對方的版本
第一層是這種人頭帳戶
第二層才是下面的車手
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.tw 與 cofacts.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.tw 與 cofacts.g0v.tw 的 cert。
結果我現在還是不知道為啥 nginx 會重啟失敗。
  • 😮2
ShuHuai（Whycat） 2021-12-17 11:12:57
我之前碰到一個情況是因為 nginx 分成 master 和 worker process， certbot 在停止 nginx 時沒有兩種都停止所以無法執行更新，不知道有沒有關聯。
mrorz 2021-12-17 12:03:46
喔喔但我們的 certbot 是在 docker 裡，nginx 是在另一個 docker
我是 cron job 裡在 certbot 跑起來 5min 後再 docker exec nginx nginx -s reload 之類
ShuHuai（Whycat） 2021-12-20 12:10:13
嗯嗯了解，這樣架構的話我就沒經驗了ＸＤ
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 上有針對「公投綁大選」的訊息ㄇ
cai 2021-12-10 21:02:40
沒印象
cai 21:02:40
沒印象
2021-12-11
mrorz 12:04:12
Replied to a thread: 2021-12-05 16:25:59
發現找了一下，發現這個狀況有點複雜

這些確實是同一個 LINE 使用者（ＩＤ： `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
cai 12:56:54
他大概把linebot 當成資安百科全書了吧
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:19:17
<https://github.com/cofacts/rumors-site/issues/363|#363 Fix editor RWD breakpoints>
github2 13:19:18
<https://github.com/cofacts/rumors-site/pull/460|#460 Fix editor RWD breakpoints #363>
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:05:18
<https://github.com/cofacts/rumors-site/issues/363#issuecomment-991499957|Comment on #363 Fix editor RWD breakpoints>
<https://github.com/MrOrz|@MrOrz> can close this issue?
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:19:04
Review on #461 NewReplySection border &amp; display fix
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*.
github2 22:51:58
<https://github.com/cofacts/rumors-site/issues/462#issuecomment-991670807|Comment on #462 Add introduction youtube video to Tutorial page>
`This comment was deleted`
cai 23:33:55
https://cofacts.tw/article/3hpyns95apj9m
這篇有人回覆是他家地址
cai 23:39:49
紀錄大里這串，這兩天看到好幾篇
Leopold緯哲 23:48:11
@chelee0510 has left the channel
2021-12-12
Teemo 00:24:13
@teemocogs has joined the channel
github2 01:50:02
<https://github.com/cofacts/rumors-site/pull/461|#461 NewReplySection border &amp; display fix>
github2 14:00:02
Review on #464 [AppLayout][LandingPage] change forum links to tutorial
LGTM!
github2 21:42:16
<https://github.com/cofacts/rumors-site/pull/464|#464 [AppLayout][LandingPage] change forum links to tutorial>
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
mrorz 2021-12-13 14:18:55
Will be fixed in this PRL:
mrorz 2021-12-17 17:58:09
Fix released yesterday 🚀
mrorz 14:18:55
Will be fixed in this PRL:
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
cai 22:36:06
https://cofacts.tw/article/3d99rhuro3wfp
新人
看來也是每周一新增
lotifv 23:52:54
@lotifv has joined the channel
2021-12-14
mrorz 12:36:49
感謝回報
等等處理
github2 13:09:35
<https://github.com/cofacts/takedowns/pull/30|#30 Add 2nd scam>
mrorz 13:09:56
Replied to a thread: 2021-12-07 20:11:50
https://github.com/cofacts/takedowns/pull/30/files?short_path=70c591b#diff-70c591b2a14cd68b471b744980e8d8f7a76d3e9b8a5df5407bfc2b42336cb0d2
github2 14:48:00
Review on #30 Add 2nd scam
github2 15:09:11
<https://github.com/cofacts/takedowns/pull/30|#30 Add 2nd scam>
  • 👌1
2021-12-15
mrorz 14:36:29
今日會議記錄
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FWEqAcqHwRAeiQywjdOu1Jw
2021-12-16
github2 10:59:18
<https://github.com/cofacts/rumors-site/pull/465#issuecomment-995394345|Comment on #465 Tell editors to not reply other's reply + translations>
Tested in <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FWEqAcqHwRAeiQywjdOu1Jw|meeting>, let's merge
github2 10:59:24
<https://github.com/cofacts/rumors-site/issues/463|#463 Tell editors to not reply other's reply>
github2 10:59:24
<https://github.com/cofacts/rumors-site/pull/465|#465 Tell editors to not reply other's reply + translations>
2021-12-17
ShuHuai（Whycat） 11:12:57
我之前碰到一個情況是因為 nginx 分成 master 和 worker process， certbot 在停止 nginx 時沒有兩種都停止所以無法執行更新，不知道有沒有關聯。
mrorz 12:00:53
掃了一下最近的 nginx log (含 API、chatbot 等等)
發現圖中的高原期是 7:30 ~ 22:30
看來使用者的生活滿規律的，跟我的作息不同 XD
image.png
  • 😆3
mrorz 12:03:46
喔喔但我們的 certbot 是在 docker 裡，nginx 是在另一個 docker
我是 cron job 裡在 certbot 跑起來 5min 後再 docker exec nginx nginx -s reload 之類
cai 14:09:04
廣告 https://cofacts.tw/article/AV6lkq2uyCdS-nWhugfg
https://cofacts.tw/article/AV7EdS9LyCdS-nWhugw8
  • 🙏1
mrorz 2021-12-17 17:59:18
原來是廣告，早上看到 RSS 訂閱
覺得不是公投就沒點開 XD
cai 2021-12-17 18:32:46
看到日期不對就點開看XD
mrorz 17:58:09
Fix released yesterday 🚀
mrorz 17:59:18
原來是廣告，早上看到 RSS 訂閱
覺得不是公投就沒點開 XD
cai 18:32:46
看到日期不對就點開看XD
cai 18:50:57
https://cofacts.tw/replies 有人在刷奇怪的東西.....
mrorz 2021-12-23 14:08:00
看大家是否有不同意見囉
沒意見的話就用與 yegogo 一樣的處理方式
https://www.facebook.com/groups/cofacts/posts/3162206937344447/
mrorz 18:58:29
是複製貼上小粉紅呢
https://cofacts.tw/reply/RqSwx30BnX5-aOa4eId2
mrorz 19:02:15
這在反串吧 wwwwww
https://cofacts.tw/article/vhp41lcenwu2
isabelhou 2021-12-17 19:03:08
wwww
isabelhou 19:03:08
wwww
kidstarkenny 19:06:16
大家針對錯假訊息的努力還被有心人士炒作真的很痛心
  • 😢2
mrorz 2021-12-17 19:09:20
同一群人還會說事實查核中心是金溥聰的人馬ㄛ
我猜 comment 那裡會有人這麼說（顯示為沒點開看）
cai 2021-12-17 19:12:00
央視那題在真的假的沒看到XD
mrorz 2021-12-17 19:18:27
那個我在 FB 有看到，尤其是在綠側翼的 reply section
mrorz 2021-12-17 19:18:43
該不會就是因為他們愛用的圖被 block 所以懷恨在心吧 XDDDD
mrorz 19:09:20
同一群人還會說事實查核中心是金溥聰的人馬ㄛ
我猜 comment 那裡會有人這麼說（顯示為沒點開看）
cai 19:12:00
央視那題在真的假的沒看到XD
mrorz 19:18:27
那個我在 FB 有看到，尤其是在綠側翼的 reply section
mrorz 19:18:43
該不會就是因為他們愛用的圖被 block 所以懷恨在心吧 XDDDD
2021-12-18
cai 10:54:43
今天才發現cofacts的meta content 是寫
> 「Cofacts 真的假的」是一套連結網路訊息與查證訊息的協作型系統，試圖對假訊息問題作出草根應對。
原以為會是寫像平常講的那種白話版 群眾協作的方式，開放大家一起來查證假訊息 🤔
註解 2021-12-18 105109.png
  • 1
mrorz 2021-12-18 11:49:51
現在的 meta content 太學術還是工程導向了嗎 XD
cai 2021-12-18 13:11:22
太文言讓人覺得進入門檻高，降低意願
mrorz 11:49:51
現在的 meta content 太學術還是工程導向了嗎 XD
cai 13:11:22
太文言讓人覺得進入門檻高，降低意願
github2 15:29:23
<https://github.com/cofacts/takedowns/pull/31|#31 Remove spam>
mrorz 15:30:03
Replied to a thread: 2021-12-17 14:09:04
刪除公告求 approve
https://github.com/cofacts/takedowns/pull/31/files?short_path=e253001#diff-e25300181d22373d248c5ca3d87b4fd41676c6f7ba81ddf1dd8b8b1d38892d31
github2 15:53:52
Review on #31 Remove spam
github2 20:08:51
Review on #31 Remove spam
github2 20:25:03
<https://github.com/cofacts/takedowns/pull/31|#31 Remove spam>
2021-12-19
cai 21:50:26
剛好撈到一篇有身分證字號跟地址的
https://cofacts.tw/article/238fyagsgmywq
mrorz 2021-12-20 00:16:25
這個身分證字號跟地址
是租帳號的詐騙集團的（假資訊）ㄅ
mrorz 2021-12-20 00:17:48
那我覺得這個應該可以等當事人來申訴再處理
2021-12-20
mrorz 00:16:25
這個身分證字號跟地址
是租帳號的詐騙集團的（假資訊）ㄅ
mrorz 00:17:48
那我覺得這個應該可以等當事人來申訴再處理
ShuHuai（Whycat） 12:10:13
嗯嗯了解，這樣架構的話我就沒經驗了ＸＤ
cai 12:38:45
https://cofacts.tw/article/3u6wb4x79byl9
這網頁瀏覽次數攀升
看來市場豬肉攤又要解釋到很煩
  • 😮1
cai 16:39:36
廣告
https://cofacts.tw/article/2o1csjbza3853

二次詐騙
https://cofacts.tw/article/1bhaeifdpsdum
https://cofacts.tw/article/2gx3gjjgs6wb1
https://cofacts.tw/article/klxufjd4q7tm
https://cofacts.tw/article/3bsmgzu5yz5q7
  • 🙏1
mrorz 2021-12-23 14:06:44
啊漏一個廣告
mrorz 2021-12-28 13:35:26
廣告真的好多喔囧

現況其實檢舉廣告，對檢舉人跟我們操作都滿麻煩的
1. 熱心檢舉人要把廣告出現的網址跟出現了什麼，手動貼給我們回報
2. 我要手動打 API 找出違規使用者 ID 與名稱
3. 為了要發 takedown 公告 (例)，我要打 API 列出目前違規使用的這個人的所有 reply request、手動貼到 sheet 如範例
4. 手動發 takedown 公告求 approve
5. 手動拼湊 block 指令去主機執行 block
我在想要不要做個檢舉機制，比較容易實作的方式如下：
1. 在「我想補充」與「回應」右邊多個「舉報」按鈕
2. 按下「舉報」時會帶使用者到 google form，裡面已經預填好一些欄位，如 user ID
3. 在 Google form 設定說有新舉報的時候寄信通知 cofacts googlegroups
4. 在該 form 的 response spreadsheet 開一個手動填寫的新 column 放我們是否有執行刪除。
a. 執行刪除就是之前寫的 block user script
b. 我可以在 Google sheet 自動用前面預填的欄位做出 block 指令，所以要執行就直接複製指令執行即可
5. 在 google spreadsheet 開一個新 sheet 把我們有執行刪除的人列出來，然後 publish 這個單一 sheet to HTML。這個 published URL 會被放進 cofacts/takedowns repo，我們就不針對廣告檢舉另外發 PR 與公告了。
以上 1, 2 是唯一會動到程式碼的部分；回報、執行與公告一氣呵成，不針對個案另行公告。
唯一有瑕疵的是在執行前大家看不到違規者的 spam 長什麼樣子，但之後可以用 script 撈出所有 BLOCKED content 供大家檢視說目沒 block 錯人。
cai 2021-12-28 18:46:57
希望像是youtube留言那樣，每則補充右邊多個 「 ⋮ 」，點下去有個「回報濫用」→ 跳出表單 → 單選廣告後送出
2021-12-21
cai 17:43:23
cofacts 固定被洗版的
週一是二次詐騙
週二是vpn
cai 19:47:01
https://cofacts.tw/article/3bv5zb3dyu782
這篇是講瘦肉精嗎？
今天有2篇是講瘦肉精的，查核中心那邊有報告了，以前的謠言拿出來的
https://cofacts.tw/article/9sfxdwwkhhc2
https://cofacts.tw/article/29s4qto3h1hwa
mrorz 2021-12-21 19:55:47
第一篇我剛才看到
不小心回掉了 XD
mrorz 2021-12-21 19:56:16
第二篇我看不懂，而且才一個人傳，也沒更多資訊，我就先放著囉
mrorz 19:55:47
第一篇我剛才看到
不小心回掉了 XD
mrorz 19:56:16
第二篇我看不懂，而且才一個人傳，也沒更多資訊，我就先放著囉
2021-12-22
mrorz 15:12:00
今晚會議記錄
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FO0pXnRocRuKoJwdC1_9wmA
mrorz 2021-12-23 13:25:38
好 XD
cai 18:49:28
Replied to a thread: 2021-12-17 18:50:57
https://cofacts.tw/article/24mftvgfozb3q
小粉紅又出現了
2021-12-23
mrorz 13:25:38
好 XD
github2 14:05:19
<https://github.com/cofacts/takedowns/pull/32|#32 Add 2 scammers>
mrorz 14:06:44
啊漏一個廣告
mrorz 14:08:00
看大家是否有不同意見囉
沒意見的話就用與 yegogo 一樣的處理方式
https://www.facebook.com/groups/cofacts/posts/3162206937344447/
2021-12-24
cai 16:29:49
https://cofacts.tw/article/36b2fwo1f42b1
https://cofacts.tw/article/1oi1bu9gsdgfl
印象負分是不會顯示到line ，為什麼還有這種亂數的按讚？
nonumpa 2021-12-24 17:11:42
負分回應因為考慮到簡便性、不打擾群組對話，不會在群組內回覆

但在跟 Cofacts真的假的 的一對一對話中，為了保有回應的多元性、不讓回應因評分操縱而消失（雖然評分會影響回應出現的順序），還是看得到的

還有沒記錯的話，使用者是無法在群組內對回應評分的（除非點開網址到網站評分）
nonumpa 17:11:42
Replied to a thread: 2021-12-24 16:29:49
負分回應因為考慮到簡便性、不打擾群組對話，不會在群組內回覆

但在跟 Cofacts真的假的 的一對一對話中，為了保有回應的多元性、不讓回應因評分操縱而消失（雖然評分會影響回應出現的順序），還是看得到的

還有沒記錯的話，使用者是無法在群組內對回應評分的（除非點開網址到網站評分）
nonumpa 17:22:48
https://www.facebook.com/251923422088376/posts/789509231663123/

這裡有群組功能上線時的小介紹
2021-12-26
cai 16:28:16
貼圖元旦還會再騙一波的樣子😅
2021-12-27
cai 19:12:33
Replied to a thread: 2021-12-20 16:39:36
廣告
https://cofacts.tw/article/2o1csjbza3853
2021-12-28
Edward Wilkinson 02:44:34
@edward.wilkinson6 has joined the channel
mrorz 13:35:26
Replied to a thread: 2021-12-20 16:39:36
廣告真的好多喔囧

現況其實檢舉廣告，對檢舉人跟我們操作都滿麻煩的
1. 熱心檢舉人要把廣告出現的網址跟出現了什麼，手動貼給我們回報
2. 我要手動打 API 找出違規使用者 ID 與名稱
3. 為了要發 takedown 公告 (例)，我要打 API 列出目前違規使用的這個人的所有 reply request、手動貼到 sheet 如範例
4. 手動發 takedown 公告求 approve
5. 手動拼湊 block 指令去主機執行 block
我在想要不要做個檢舉機制，比較容易實作的方式如下：
1. 在「我想補充」與「回應」右邊多個「舉報」按鈕
2. 按下「舉報」時會帶使用者到 google form，裡面已經預填好一些欄位，如 user ID
3. 在 Google form 設定說有新舉報的時候寄信通知 cofacts googlegroups
4. 在該 form 的 response spreadsheet 開一個手動填寫的新 column 放我們是否有執行刪除。
a. 執行刪除就是之前寫的 block user script
b. 我可以在 Google sheet 自動用前面預填的欄位做出 block 指令，所以要執行就直接複製指令執行即可
5. 在 google spreadsheet 開一個新 sheet 把我們有執行刪除的人列出來，然後 publish 這個單一 sheet to HTML。這個 published URL 會被放進 cofacts/takedowns repo，我們就不針對廣告檢舉另外發 PR 與公告了。
以上 1, 2 是唯一會動到程式碼的部分；回報、執行與公告一氣呵成，不針對個案另行公告。
唯一有瑕疵的是在執行前大家看不到違規者的 spam 長什麼樣子，但之後可以用 script 撈出所有 BLOCKED content 供大家檢視說目沒 block 錯人。
g0v.hackmd.io
Cofacts user blocking mechanism - HackMD
cai 18:46:57
希望像是youtube留言那樣，每則補充右邊多個 「 ⋮ 」，點下去有個「回報濫用」→ 跳出表單 → 單選廣告後送出
2021-12-29
github2 08:57:36
<https://github.com/cofacts/takedowns/pull/33|#33 Remove spammer>
github2 09:10:52
Review on #33 Remove spammer
github2 12:57:32
Review on #33 Remove spammer
cai 13:41:00
住警器也是老謠言了
github2 14:20:54
<https://github.com/cofacts/takedowns/pull/33|#33 Remove spammer>
mrorz 14:32:37
今日議程
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FSyl8le5xS22nLo8Vc56gmw
github2 14:59:23
<https://github.com/cofacts/takedowns/pull/34|#34 Block ads spammer>
mrorz 14:59:47
Replied to a thread: 2021-12-20 16:39:36
以上回報之廣告在這裡處理：
https://github.com/cofacts/takedowns/pull/34/files?short_path=8257a1c#diff-8257a1c60577c5e0692d6ce340f18cb90830d211a69589dbf01a0f380f11a2e1
  • 👍2
github2 15:41:00
Review on #34 Block ads spammer
github2 15:49:08
<https://github.com/cofacts/takedowns/pull/34|#34 Block ads spammer>
cai 17:26:16
https://youtu.be/SvIQmkm0v3o?t=737 cofacts 有跟國中小合作？是指零時小學校嗎？
YouTube
2021-12-15 高雄市國教輔導團座談分享
lucien 2021-12-29 22:19:25
原來是PDIS
mrorz 2021-12-30 00:03:32
Hmm 國中小確實有點難，其實我們的經驗是，高中都不太容易了 XD
isabelhou 2021-12-30 14:00:49
零時小學校只有到高中喔
cai 2021-12-30 14:52:00
那跟國中小合作到底是哪來的 😆
bil 20:01:17
咦有嗎
github2 21:47:56
<https://github.com/cofacts/rumors-site/pull/466|#466 Update landing page's Mandarin search snippet description>
Discussion: <https://g0v.hackmd.io/Syl8le5xS22nLo8Vc56gmw?both#Cofacts-search-snippet-%E4%BF%AE%E6%94%B9|https://g0v.hackmd.io/Syl8le5xS22nLo8Vc56gmw?both#Cofacts-search-snippet-%E4%BF%AE%E6%94%B9> <https://user-images.githubusercontent.com/108608/147668806-d9b5e50d-5e6a-4318-8dd4-43b11a0f8a6b.png|圖片>
:white_check_mark: All checks have passed
github2 21:50:27
<https://github.com/cofacts/rumors-site/pull/466#issuecomment-1002603745|Comment on #466 Update landing page's Mandarin search snippet description>
<https://coveralls.io/builds/45280269|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/221781469f124ef1580b6805feed254aaf03569a|2217814> on update-landing-description* into *<https://github.com/cofacts/rumors-site/commit/7bfd6b73000532614da6e3588f79ce0210a293ca|7bfd6b7> on master*.
github2 21:53:43
Review on #466 Update landing page's Mandarin search snippet description
lucien 22:19:25
原來是PDIS
github2 23:56:17
<https://github.com/cofacts/rumors-site/pull/466|#466 Update landing page's Mandarin search snippet description>
2021-12-30
mrorz 00:03:32
Hmm 國中小確實有點難，其實我們的經驗是，高中都不太容易了 XD
mrorz 00:44:31
NCC 正在準備數位通訊傳播法草案，裡面會規範到如 Cofacts 這樣的平台。

https://youtu.be/SoPCZFdTw_o?t=940
免責條件：平台沒有參與編輯的話，平台可以免責（馬尼拉中介者責任原則）
但如果我們有做 takedown 的管理這樣算免責ㄇ

使用者保護：聖塔克拉拉原則
登載義務沒有問題我們已經在做
但那個「資訊限制告知」的部分，我要告知 yegogo 說我每次都會把它文字下架 or 告訴那些 spammer 說我會把他的東西藏起來嗎囧
這我覺得不 OK⋯⋯
YouTube
1101229下午2:00 NCC第996次委員會議後例行記者會
mrorz 00:50:06
Oh 好像會排除小規模業者，但沒提到定義與怎麼排除
https://youtu.be/SoPCZFdTw_o?t=1176
YouTube
1101229下午2:00 NCC第996次委員會議後例行記者會
mrorz 01:06:46
違法（色情）直接走中介機構通知、平台靠自己的服務條款下架
而不實 / 爭議訊息這點如果真的要靠外部下架則需法院認證的精神我覺得不錯
chihao 08:19:06
`告訴那些 spammer 說我會把他的東西藏起來` 要怎麼告知⋯登報公告？XD
mrorz 2021-12-31 02:01:38
像 FB 那樣用自己的通知系統寫說「你的內容已經因為 XXX 所以被我們移除」就算通知了吧
isabelhou 14:00:49
零時小學校只有到高中喔
isabelhou 14:02:21
草案出來後，來好好檢視一下草案的可行性吧
  • 1
cai 14:52:00
那跟國中小合作到底是哪來的 😆
2021-12-31
mrorz 02:01:38
像 FB 那樣用自己的通知系統寫說「你的內容已經因為 XXX 所以被我們移除」就算通知了吧
cai 11:47:44
廣告 // 都同一位
https://cofacts.tw/article/1ohsmcv9n1uz6
https://cofacts.tw/article/1wasoa62inb8x
https://cofacts.tw/article/3bvt22cbwnpqp
mrorz 2021-12-31 11:56:24
清掉囉
感謝感謝
mrorz 2021-12-31 11:57:29
是老朋友 yegogo
食藥署碰風廣告專區那位
mrorz 11:56:24
清掉囉
感謝感謝
mrorz 11:57:29
是老朋友 yegogo
食藥署碰風廣告專區那位
github2 18:43:45
<https://github.com/cofacts/rumors-api/pull/262|#262 Apply status filter on resources>