cofacts

Month: 2022-01

2022-01-02

github2 01:15:54

<https://github.com/cofacts/rumors-site/pull/467|#467 Show blocked content only for blocked users>

Depends on API: <https://github.com/cofacts/rumors-api/pull/262|cofacts/rumors-api#262> This PR implements M3: • In the new API it will not show blocked content by default • This PR allows blocked user to see blocked content (reply request, article reply, article category) on article page *Normal user* Note: there is 1 scammer comment in the image -- we forgot to ban the user previously. Block them here: <https://github.com/cofacts/takedowns/pull/35/files?short_path=bcf97d9#diff-bcf97d9ee9386930d59f50144c9d0d8d90dbbeb775a27af646d41729cc055c80|https://github.com/cofacts/takedowns/pull/35/files?short_path=bcf97d9#diff-bcf97d9ee9386930d59f50144c9d0d8d90dbbeb775a27af646d41729cc055c80> <https://user-images.githubusercontent.com/108608/147856084-a36276cf-24f9-41a1-8c3a-4296e92b8193.png|圖片> *Blocked user* All blocked contents are shown if and only if the browser is owned by a blocked user. <https://user-images.githubusercontent.com/108608/147856110-0dd604b5-bdbd-4928-b291-8046b1b8922b.png|圖片>

:white_check_mark: All checks have passed

github2 01:17:51

<https://github.com/cofacts/rumors-site/pull/467#issuecomment-1003588186|Comment on #467 Show blocked content only for blocked users>

<https://coveralls.io/builds/45317611|Coverage Status> Coverage remained the same at 75.363% when pulling *<https://github.com/cofacts/rumors-site/commit/cf550a0ca17a8b6b44f7839454b1758704e701c0|cf550a0> on load-blocked* into *<https://github.com/cofacts/rumors-site/commit/0edcdb9eda6e14c2d04cc63c1d1d9e20d4beea78|0edcdb9> on master*.

cai 13:16:08
https://cofacts.tw/article/1z4mfcu1f1dy1
https://cofacts.tw/article/37v1rhs7qwi4w
https://cofacts.tw/article/3kpl5ucl2s8j8
https://cofacts.tw/article/37egvhb6pxzwf
https://cofacts.tw/article/at7dlzb0erlf
https://cofacts.tw/article/s60ndd1lxxa7
https://cofacts.tw/article/2rfcramdl3lif
https://cofacts.tw/article/3ehcgvlb6ey02
https://cofacts.tw/article/1pwruw3gw1xo5
https://cofacts.tw/article/222uijnqk7e4g
這幾篇應該是講一樣的東西
解答應該如這篇講的是`青島電視塔AR燈光秀`,地標是對的,但是查不到相關新聞,新聞只有查到中國多地取消跨年活動
不錯的創作呀 XD
https://www.youtube.com/watch?v=MbvRMKxh5TQ
這個版本有最後的 logo
「市南區文化和旅遊局」
「金東數字雙翼」
但也沒在市南區文化和旅遊局的官方微博
我不懂中國的官方宣傳
https://weibo.com/u/2210514455
我有個大膽ㄉ想法
這是金東數字創意做給中國地方政府的提案
但沒有採用之類
但他們去年元宵也有做一份
到底
感謝 @iacmai ~~
感覺可以補上新回應,加入 TFC 查證作為佐證資料
😮 1
github2 16:02:32

<https://github.com/cofacts/rumors-db/pull/56|#56 Add articleType and attachment for non-text articles>

Stores non-text messages in separate articles Spec: <https://g0v.hackmd.io/aJqHn8f5QGuBDLSMH_EinA|https://g0v.hackmd.io/aJqHn8f5QGuBDLSMH_EinA> Make sure update schema before release ``` npm run reload -- articles ```

2022-01-03

github2 00:04:36

<https://github.com/cofacts/rumors-db/pull/56#discussion_r777227783|Comment on #56 Add articleType and attachment for non-text articles>

Question: will there be multiple attachments? If not, we can consider using `attachmentUrl` + `attachmentHash` instead.

2022-01-04

mrorz 11:22:55
我在準備 spreadsheet 來呈現資料庫裡的 blocked users & blocked reply requests
之前的 spam monitor 的做法是,會拿已有的最新資料時間點為基準,每次僅插入該時間點以後的新的資料。

但由於把資料設成 blocked 的時間可能會晚於建立時間,以往用最新時間掃 data to block 的機制,會掃不到較早建立但(因為回報較晚所以)比較晚被設為 blocked 的內容。

這樣一來,這種掃資料然後塞進 spreadsheet 的做法好像不太適合,或許改成放在 community builder ,在有人看的時候即時呼叫 API 列出來會比較合適這樣

cofacts.github.io

Community Builder

Web site created using create-react-app

github2 13:32:20

<https://github.com/cofacts/rumors-api/pull/273#discussion_r777832663|Comment on #273 Multimedia support phase 0>

Question: should we migrate all existing articles to have `articleType` = `TEXT` after deploying it? Seems that a simple curl command can do this.

github2 13:32:20

<https://github.com/cofacts/rumors-api/pull/273#discussion_r777831828|Comment on #273 Multimedia support phase 0>

nit: I think we can 1. Add a resolver that resolves to `TEXT` if `articleType` does not exist for the document 2. Add `GraphQLNonNull` to its type so that client can know it cannot be `null` 3. Remove `LINE` from description because we may collect `article` from other channels as well

github2 13:32:20

Review on #273 Multimedia support phase 0

Thanks for the implementation! I have not looked into `CreateMediaArticle`, but have some early nitpicking comments / comments over surrounding code changes.

github2 14:33:12

<https://github.com/cofacts/community-builder/pull/6|#6 Fix editor works pagination>

Fixes pagination of Feedbacks &amp; Comments page under Editor Works. • It is fixed by applying relay style pagination to `ListReplyRequests` and `ListArticleReplyFeedbacks`. • This consolidates `fetchMore` results into the same filter, causing `edges.length` to grow correctly after `fetchMore` returns • Hide pagination buttons when `fetchMore` so that `DataGrid`'s page stat can match component's max page loading state *Screenshot* List of feedback: can go to next page now. <https://user-images.githubusercontent.com/108608/148018720-7ad4df14-ddc9-45e7-9008-fc629a7141a8.gif|paginate> This also applies to "comments".

2022-01-05

github2 02:38:34

<https://github.com/cofacts/community-builder/pull/7|#7 GitHub actions>

Replace travis with github actions

:white_check_mark: All checks have passed

mrorz 13:19:37
今日會議記錄:小聚 rundown,以及測試「把 blocked reply request 藏起來」的功能
https://g0v.hackmd.io/RtKFTKRFRduJK0gz3St3lQ

g0v.hackmd.io

20220105 會議記錄 - HackMD

詐騙關鍵字: `財富自由`

避開垃圾訊息:關掉iMessage
https://www.ptt.cc/bbs/iOS/M.1640258161.A.AE0.html
https://www.dcard.tw/f/talk/p/237565415
有待iphone使用者見證?
會晚大概 10 分鐘開始唷
line挖礦那間有公司登記了,他把回應寫的錯誤都解了XD
療效產品 提告詐騙的
https://www.tellows.tw/num/0911511101 留言很精采
https://news.ebc.net.tw/news/society/286762 新聞有報過
https://law.moeasmea.gov.tw/ailt/modules/forum/details/?topic_id=32864
這篇回應說可以蒐集證據提告恐嚇XD

2022-01-06

github2 00:00:41

<https://github.com/cofacts/rumors-site/issues/468|#468 Cannot read property status of undefined/null expression>

View details in Rollbar: <https://rollbar.com/mrorz/rumors-site/items/1536/|https://rollbar.com/mrorz/rumors-site/items/1536/> ``` TypeError: Cannot read property 'status' of undefined File "/srv/www/.next/server/static/9Wf1MTRmgW4434AwlMHwg/pages/reply/[id].js", line 2750, in ReplyPage const isDeleted = originalArticleReply.status === 'DELETED'; File "/srv/www/node_modules/react-dom/cjs/react-dom-server.node.production.min.js", line 33, in c function Sa(a,b,d){function c(c,f){var e=ma(f,b,d),g=[],h=!1,l={isMounted:function(){return!1},enqueueForceUpdate:function(){if(null===g)return null},enqueueReplaceState:function(a,b){h=!0;g=[b]},enqueueSetState:function(a,b){if(null===g)return null;g.push(b)}},k=void 0;if(f.prototype&amp;&amp;f.prototype.isReactComponent){if(k=new f(c.props,e,l),"function"===typeof f.getDerivedStateFromProps){var t=f.getDerivedStateFromProps.call(null,c.props,k.state);null!=t&amp;&amp;(k.state=p({},k.state,t))}}else if(N={},k=f(c.props, File "/srv/www/node_modules/react-dom/cjs/react-dom-server.node.production.min.js", line 36, in Sa c(f,e)}return{child:a,context:b}} File "/srv/www/node_modules/react-dom/cjs/react-dom-server.node.production.min.js", line 41, in a.render D}else{var l=g.children[g.childIndex++],k="";try{k+=this.render(l,g.context,g.domNamespace)}catch(t){throw t;}finally{}f.length&lt;=this.suspenseDepth&amp;&amp;f.push("");f[this.suspenseDepth]+=k}}return f[0]}finally{Ja.current=c,X=b}};a.prototype.render=function(a,d,c){if("string"===typeof a||"number"===typeof a){c=""+a;if(""===c)return"";if(this.makeStaticMarkup)return M(c);if(this.previousWasTextNode)return"\x3c!-- --\x3e"+M(c);this.previousWasTextNode=!0;return M(c)}d=Sa(a,d,this.threadID);a=d.child;d=d.context; File "/srv/www/node_modules/react-dom/cjs/react-dom-server.node.production.min.js", line 41, in a.read D}else{var l=g.children[g.childIndex++],k="";try{k+=this.render(l,g.context,g.domNamespace)}catch(t){throw t;}finally{}f.length&lt;=this.suspenseDepth&amp;&amp;f.push("");f[this.suspenseDepth]+=k}}return f[0]}finally{Ja.current=c,X=b}};a.prototype.render=function(a,d,c){if("string"===typeof a||"number"===typeof a){c=""+a;if(""===c)return"";if(this.makeStaticMarkup)return M(c);if(this.previousWasTextNode)return"\x3c!-- --\x3e"+M(c);this.previousWasTextNode=!0;return M(c)}d=Sa(a,d,this.threadID);a=d.child;d=d.context; File "/srv/www/node_modules/react-dom/cjs/react-dom-server.node.production.min.js", line 53, in renderToString return b}(aa.Readable),Wa={renderToString:function(a){a=new Ta(a,!1);try{return a.read(Infinity)}finally{a.destroy()}},renderToStaticMarkup:function(a){a=new Ta(a,!0);try{return a.read(Infinity)}finally{a.destroy()}},renderToNodeStream:function(a){return new Va(a,!1)},renderToStaticNodeStream:function(a){return new Va(a,!0)},version:"16.8.6"},Xa={default:Wa},Ya=Xa&amp;&amp;Wa||Xa;module.exports=Ya.default||Ya; File "/srv/www/node_modules/next/dist/next-server/server/render.js", line 83, in render html = renderElementToString(element); File "/srv/www/node_modules/next/dist/next-server/server/render.js", line 406, in renderPage return render(renderElementToString, react_1.default.createElement(AppContainer, null, File "/srv/www/.next/server/static/9Wf1MTRmgW4434AwlMHwg/pages/_document.js", line 255, in Object.ctx.renderPage ctx.renderPage = () =&gt; originalRenderPage({ File "/srv/www/.next/server/static/9Wf1MTRmgW4434AwlMHwg/pages/_document.js", line 629, in Function.getInitialProps } = await ctx.renderPage({ ```

github2 00:16:28

<https://github.com/cofacts/rumors-site/issues/468#issuecomment-1005867982|Comment on #468 Cannot read property status of undefined/null expression>

*Steps to reproduce* • VIsit a reply detail page with all its article replies deleted: <https://dev.cofacts.tw/reply/_A44ZHEBrhVJn3LN9SdD|https://dev.cofacts.tw/reply/_A44ZHEBrhVJn3LN9SdD> *Root cause* 1. In the <https://github.com/cofacts/rumors-api/pull/262|new API>, The `articleReplies` resolvers will only return `NORMAL` article replies by default. 2. Reply detail page rendering logic expects there should be at least 1 article reply to function properly. It is the case when we return both `NORMAL` and `DELETED` reply, but is no longer the case in the new API. *Proposed fix* • Also query`DELETED` article replies so that original render logic would work • For future `BLOCKED` article replies, render a minimal reply detail page (so that blocked user will not notice &amp; for displaying this blocked content), but specify that the content should not be indexed by search engines (so that spams don't get boosted)

github2 00:33:13

<https://github.com/cofacts/rumors-site/pull/469|#469 [Reply] reply detail page should work for DELETED &amp; BLOCKED content>

See analysis in <https://github.com/cofacts/rumors-site/issues/468#issuecomment-1005867982|#468 (comment)> Fixes <https://github.com/cofacts/rumors-site/issues/468|#468> . *Screenshots* *Current* Reply detail page of deleted reply will trigger internal server error: <https://user-images.githubusercontent.com/108608/148253307-a2ac8051-0181-4488-bba6-0b2089e941ae.png|圖片> *Fixed* Deleted reply can be properly displayed <https://user-images.githubusercontent.com/108608/148253405-d594d69a-8934-4336-9b6a-e9dffdf49539.png|圖片> Blocked reply (spam content) can be displayed in a minimalist fashion for public display, but do not allow web crawler to index (Simulated by forcefully enter if statement) <https://user-images.githubusercontent.com/108608/148253590-b9edbda0-1504-405d-a044-5255c473adb1.png|圖片>

:white_check_mark: All checks have passed

信箱挖到了新 API 導致 deleted reply 的 reply detail 顯示不出來的問題
這個是 solution 唷煩請 review
mrorz 00:34:12
信箱挖到了新 API 導致 deleted reply 的 reply detail 顯示不出來的問題
這個是 solution 唷煩請 review
github2 00:50:28

<https://github.com/cofacts/rumors-site/pull/469#issuecomment-1005895429|Comment on #469 [Reply] reply detail page should work for DELETED &amp; BLOCKED content>

<https://coveralls.io/builds/45397637|Coverage Status> Coverage remained the same at 74.692% when pulling *<https://github.com/cofacts/rumors-site/commit/b79669d313261126125d47fa063a92ce2ab80f87|b79669d> on fix-reply-detail* into *<https://github.com/cofacts/rumors-site/commit/46a813bef8dee656e8504df0289919a400aec753|46a813b> on master*.

github2 13:26:53

Review on #273 Multimedia support phase 0

LGTM! The tests for CreateMediaArticle covers every aspect and looks pretty solid :muscle: Just 2 additional comments.

github2 13:26:54

<https://github.com/cofacts/rumors-api/pull/273#discussion_r779303247|Comment on #273 Multimedia support phase 0>

Since we actually don't parallelize anything here, we can do ordinary async await in this resolver to simplify stuff. ``` const articleId = await createNewMediaArticle(...); // This "await" here is optional. But it should not take more than a few milliseconds to wait for reply request creation.... await createOrUpdateReplyRequest({ articleId, user, reason }); return { id: articleId }; ```

github2 13:26:54

<https://github.com/cofacts/rumors-api/pull/273#discussion_r779297817|Comment on #273 Multimedia support phase 0>

nit: since the logic of search hit is much shorter, I think we can do early return for the search hit case to reduce the indent of code (which reduces the mental load of "there is an else branch" when reading the code) ``` if(matchedArticle.hits.total) { return matchedArticle.hits.hits[0]._id; } // The rest of code ```

cai 17:07:33
https://www.facebook.com/165bear/posts/4867501326642662
https://165.npa.gov.tw/#/article/news/460
165終於公布試住員是詐騙了

facebook.com

Log in or sign up to view

See posts, photos and more on Facebook.

2

2022-01-07

mrorz 13:02:20
預設把 blocked content 隱藏的 API,今天凌晨已經上線囉
現在還看得到的 spam,就是還沒回報過、被標為 blocked 的 spam XD
👍 1 1
cai 21:33:55
是不是有人固定丟 cofacts.org / reply 來問?
@andyy0216 有發現他是跟之前亂送關鍵字的是同一個人
https://old.cofacts.tw/articles?searchUserByArticleId=2kd7upbb3fsb0&filter=all&replyRequestCount=1

我想說放著不理他先,看起來十幾天會來發作一次 (?)
就跟VPN 文固定會有廣告一樣?
或是他單純覺得丟很多垃圾給編輯忙很好玩(?
cai 22:02:51
你們要把訊息選擇分類會很lag 嗎
4000 22:03:02
4000 22:04:01
不過不用等他 重整就會上去了
1 1 1
cai 22:04:01
那看來不是我網路問題,我還以為是我電腦又再跑windows更新
cai 23:02:26
https://cofacts.tw/article/1xe57cs1utbnv
https://cofacts.tw/article/31m49a57fz26p
這篇好像是簡書上的創作文....

简书

一个国家总统的恋爱悲剧

一个国家总统,和一个普通百姓秘密恋爱了五年,最后的结局令人心酸落泪。下面,我来讲这个恋爱的悲剧。 经过38年的努力,2013年2月25日,朴槿惠正式当选韩国历史上第一位女总统...

確實把朴槿惠與「高英男」寫在一起的,都是同一篇文章
所以是虛構故事沒錯呢
1

2022-01-08

cai 11:06:50
https://cofacts.tw/reply/SqTXNn4BnX5-aOa4wa-8
https://cofacts.tw/reply/SaTTNn4BnX5-aOa4Bq-2
奇怪的回應???
2017 的老訊息
https://cofacts.tw/article/AV_KDSDtyCdS-nWhujVO

但他發問在另外兩篇下面也是滿煩的,只好給 downvote
cai 12:33:07
去年初疫情消息混現在的消息好煩 😥
https://cofacts.tw/article/jsu8n2j9lndy
這則應該是去年混今年的
1. 最近的桃機群聚相關足跡的確有永和豆漿大王
2. 台北燈節延期跟年貨大街取消是2021/1/20
3. 新北這個到底要算今年還去年阿 :rolling_on_the_floor_laughing:
針對燈節跟年貨大街,確實應該是假訊息
但如果是我回的話,我會特別說「截至 2022/1/9」 政府尚未公告這樣
以防之後政府宣佈 XD
😢 3

2022-01-09

cai 13:30:39
https://cofacts.tw/article/jsu8n2j9lndy
這則應該是去年混今年的
1. 最近的桃機群聚相關足跡的確有永和豆漿大王
2. 台北燈節延期跟年貨大街取消是2021/1/20
3. 新北這個到底要算今年還去年阿 :rolling_on_the_floor_laughing:
mrorz 16:30:46
筆記 2:更新 API 後加分類,按下「新增標記」後好像不會再呈現在網頁裡了
應該是 bug QQ
aa39998 17:03:09
@aa39998 has joined the channel
👋 1

2022-01-10

2022-01-11

cai 12:59:08
https://cofacts.tw/article/1hwp30w1fa0l9
https://finance.ettoday.net/news/2165779
非公家機關的抽獎活動要算在正確訊息還是不在查核範圍 🤔
都可以 XD
選不在查證範圍(沒有出處框)的話,還是可以直接附連結在內文
cai 19:16:33
最近應該會需要這個,但是過陣子網址就會變所以僅供參考XDD
嚴重特殊傳染性肺炎(COVID-19)第二級疫情警戒標準及防疫措施裁罰規定(111年1月11日版)
沒戴口罩拍照被罰6萬我記得是老謠言,場景很多變化
我一開始想到的是二級不是規勸為主嗎,三級才是直接罰
罰6萬是三級期間的非營業場所5人以上群聚
傳染病防治法第 67 條第 l 項第 2 款規定,處新臺幣 6 萬元以上 30 萬元以下罰鍰。
因應 COVID-19 第三級疫情警戒相關措施及裁罰規定表 110.05.26 修正
新聞: https://news.ltn.com.tw/news/society/breakingnews/3656628
對對
上面這兩篇我回掉囉
雖然《嚴重特殊傳染性肺炎(COVID-19)第二級疫情警戒標準及防疫措施裁罰規定》有超多版本,但每個點進去的未戴口罩罰則都一樣(因為法源相同)所以我就不寫版本惹
我本來想貼這個新聞嚇嚇傳這個的人
「沒人因為沒戴口罩而罰 6 萬,但亂傳疫情假訊息最高罰 300 萬ㄛ」
https://www.ettoday.net/news/20210524/1989416.htm
想想還是不要好了我們很和善
1 1
mrorz 21:33:17
查核中心認證
https://www.facebook.com/216153715706427/posts/949919735663151/

facebook.com

Log in or sign up to view

See posts, photos and more on Facebook.

😆 1

2022-01-12

mrorz 03:18:27
本周議程
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FSETMQ8DaQDu3a5ZYnrvfpA

HackMD

Cofacts 會議記錄 - HackMD

# Cofacts 會議記錄 ## 2022 - [20220112 會議記錄](/SETMQ8DaQDu3a5ZYnrvfpA) - [20220105 會議記錄](/RtKFTKRFRduJ

對對,有說公開

2022-01-13

github2 13:17:55

<https://github.com/cofacts/rumors-fb-bot/pull/28|#28 Bump follow-redirects from 1.5.5 to 1.14.7>

Bumps <https://github.com/follow-redirects/follow-redirects|follow-redirects> from 1.5.5 to 1.14.7. Commits • <https://github.com/follow-redirects/follow-redirects/commit/2ede36d7c60d3acdcd324dcd99a9dbd52e4fb3a6|`2ede36d`> Release version 1.14.7 of the npm package. • <https://github.com/follow-redirects/follow-redirects/commit/8b347cbcef7c7b72a6e9be20f5710c17d6163c22|`8b347cb`> Drop Cookie header across domains. • <https://github.com/follow-redirects/follow-redirects/commit/6f5029ae1a0fdab4dc25f6379a5ee303c2319070|`6f5029a`> Release version 1.14.6 of the npm package. • <https://github.com/follow-redirects/follow-redirects/commit/af706bee57de954414c0bde0a9f33e62beea3e52|`af706be`> Ignore null headers. • <https://github.com/follow-redirects/follow-redirects/commit/d01ab7a5c5df3617c7a40a03de7af6427fdfac55|`d01ab7a`> Release version 1.14.5 of the npm package. • <https://github.com/follow-redirects/follow-redirects/commit/40052ea8aa13559becee5795715c1d45b1f0eb76|`40052ea`> Make compatible with Node 17. • <https://github.com/follow-redirects/follow-redirects/commit/86f7572f9365dadc39f85916259b58973819617f|`86f7572`> Fix: clear internal timer on request abort to avoid leakage • <https://github.com/follow-redirects/follow-redirects/commit/2e1eaf0218c5315a2ab27f53964d0535d4dafb51|`2e1eaf0`> Keep Authorization header on subdomain redirects. • <https://github.com/follow-redirects/follow-redirects/commit/2ad9e82b6277ae2104f7770e9ff1186cc6da29d4|`2ad9e82`> Carry over Host header on relative redirects (<https://github-redirect.dependabot.com/follow-redirects/follow-redirects/issues/172|#172>) • <https://github.com/follow-redirects/follow-redirects/commit/77e2a581e1d1811674b7b74745a9c20a5b939488|`77e2a58`> Release version 1.14.4 of the npm package. • Additional commits viewable in <https://github.com/follow-redirects/follow-redirects/compare/v1.5.5...v1.14.7|compare view> <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-fb-bot/network/alerts|Security Alerts page>.

github2 13:45:59

<https://github.com/cofacts/takedowns/pull/36|#36 Remove Alvagrado Alicia, wongkoona pimnipa and xiwieili>

赫然發現以前就放進 spam monitor 的忘記公告,所以一併處理 XDD
mrorz 13:58:10
赫然發現以前就放進 spam monitor 的忘記公告,所以一併處理 XDD
github2 14:36:14

<https://github.com/cofacts/takedowns/pull/32#issuecomment-1011839009|Comment on #32 Add 2 scammers>

Included in <https://github.com/cofacts/takedowns/pull/36|#36>

github2 14:58:27

<https://github.com/cofacts/takedowns/pull/37|#37 Block Yingtao Wan>

檢查的時候發現那四篇訊息裡面其實還有其他 VPN spam 囧
mrorz 17:46:11
才剛決定 deprioritize spam 然後就湧入一堆手動處理不完的 spam⋯⋯
https://cofacts.tw/article/h5kz65nt8r6y
😮 1

2022-01-14

cai 21:03:10
https://cofacts.tw/article/37r4s8i73gsd6 這個我有在IG限時動態發現廣告,會盜用勞動部的logo,忘記截圖了 😆
Nice catch!! 讚讚

2022-01-15

Katie Kurata 00:53:40
@ktchieko has joined the channel
cai 12:12:06
二次詐騙現在改往`台灣政治政黨`分類嗎
有按讚應該也是他自己按的,補充有可以按自己讚的bug
https://cofacts.tw/article/2cfs4rwqmpnsx
https://cofacts.tw/article/bor0dg2b9wf7
https://cofacts.tw/article/3ppeiqj59yffi
同一位,他留蠻多篇的,懶得全貼上來
😮 2

2022-01-16

Laura Stahl 12:59:46
@l.a.stahl has joined the channel
stella 23:37:25
@stella has joined the channel

2022-01-17

chihao 09:12:52
@mrorz 「需要有人幫忙顧平台」的例子的投影片,有可以引用的 (semi?) permalink 嗎?XD
https://docs.google.com/presentation/d/1ile4-0XKipAVC34n7Dm82QlloX_uGa9ypoLBplkGCeo/edit?usp=drivesdk

演講者備忘稿有放一些
不過把段落打進網站搜尋框就可以撈出一堆
最下面有些隱藏投影片
是我撈一撈覺得好像是隔壁棚的「接單員」
覺得好像跟「金融平台」的不太一樣所以就沒有講(時間也不夠)
\ open data / \ cofacts /
事實上各種詐騙樣態可以參考這裡的「詐騙型態介紹文」
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FRtKFTKRFRduJK0gz3St3lQ
啊,原來當然有撈到這篇
https://cofacts.tw/article/vagfgfyhlj2v
前天做投影片的時候沒有撈到
我想補充裡有所有東西 XDDD
mrorz ++ \o/
😆 1
isabelhou 09:47:05
u
cai 10:54:39
https://cofacts.tw/article/1cv9q3w8ge73u
這種型態的補充回應第一次看到 😱
這個補充是怎麼回事 @@
話說這種恐嚇的內容可以算是違法然後 takedown 嗎
不過這可能要當事人心生恐懼才算數
我現在心裡只有滿滿的問號
原來是網傳訊息原文貼進我想補充呀 XDDDD
為什麼不傳新訊息進來 XDDDD
這是某種仙人跳嗎
欸好像不算仙人跳
他連約都沒約到就先被騙了一筆點數 ._.
看完了不知道丟補充的是要玩梗還是其他用途
chihao 11:06:52
`到時候別怪我阿坤不講江湖道義` @@
ael 16:06:10
這種心路歷程真的好血淚
https://forum.gamer.com.tw/Co.php?bsn=60076&sn=81180985
我覺得感覺像是有人混進反疫苗群組裡面
想用化學方式減少反疫苗的人⋯⋯(汗)
跟以前那個騙人刪除 LINE 的惡作劇有點像
但這次是直接傷人

2022-01-18

mrorz 18:15:51
set the channel topic: Cofacts 真的假的訊息回報機器人與查證協作社群聊天室
mrorz 18:16:25
set the channel topic: Cofacts 真的假的訊息回報機器人與查證協作社群聊天室。寄信給 Cofacts 工作小組(Cofacts WG):cofacts@googlegroups.com
mrorz 18:16:33
set the channel topic: Cofacts 真的假的訊息回報機器人與查證協作社群聊天室。寄信給 Cofacts 工作小組(Cofacts WG): cofacts@googlegroups.com

2022-01-19

2022-01-20

cai 13:31:02
證券交易所要求改密碼到底是1/21還是24阿?累積超多篇 😆
我覺得最奇怪的是

我的元大沒要求我要改密碼 ._.
https://www.inside.com.tw/article/26397-otp-information-security-taiwan
「未完成登入及下載憑證雙因子認證(OTP)證券商,應採強制客戶全面更新密碼,高風險者優先處理」

所以如果已經有憑證下載的那種,就不用改密碼囉?
其實上述文章裡面
https://cofacts.tw/article/1ch8yy47ywl80
這篇有附所有的券商的公告
看起來可能有些券商已經有雙因子認證所以沒有說一定要改密碼
有些沒有的是在呼籲大家開啟之類的
結果我元大證券沒改密碼
今天可以下單還成交
喔喔喔所以看起來不是所有人,而是滿足特定條件的人
例如申請憑證的時候沒開 OTP 之類
那回應交給你們了 😆
表格很有用,回應完囉
有些新聞寫「千萬證券戶」應該是言過其實啦 XDDD
龍頭券商元大就不是每個人都要換了
cai 20:32:32
有姓氏,這是內部訊息吧 https://cofacts.tw/article/12y3t0pu7hgy0

我以前會寫很多什麼請大家不要獵巫呀、去的地方都消毒了呀之類的

現在看到這個
就是貼政府相關案號公告然後強調已經消毒惹
要選含有個人意見還是含有正確訊息就看訊息狀況
這種內部人外流的實在很煩
我想丟不在查核範圍XDD
我:才不告訴你咧
好想丟去衛生局fb說你們內部訊息不要外流阿
我猜不會是衛生局啦
但要執行防疫政策,訊息一定要傳到很多手跟腳(鄰里長、警察等等)
但手跟腳都有家人要關心
然後這些家人也有彼此的家人
就變成現在這個狀況~
https://cofacts.tw/article/339u8cmnxavox
然後這篇的足跡部分在1/28公布 但這篇是1/27發的 😅

2022-01-21

ichieh 16:11:37
嗨嗨~ 揪松收到 cofacts 會議室申請,不過目前 3/5 13:30 - 17:30 只有 4 樓會議室可以借,3/12 13:30 - 17:30 就有廚房,想問 cofacts 要哪天~~
好唷 3/12 很棒~~感謝感謝

另外想問 https://g0v.hackmd.io/BNHyH7ESSxSlu12BV2U9TQ#%E7%94%B3%E8%AB%8B%E6%96%B9%E5%BC%8F 的「日曆」好像關起來了
是正常的嗎
對欸!NPO HUB 調整觀看權限,那以後只好先送申請揪松再看,或是也可以先在 #jothon 詢問一下
@bil @mrorz 想跟你們討論一下空間~

因為 3/12 我們也考慮要辦基礎松,想說可以辦在一起,NPO HUB 二樓有一些新的空間,一個叫影響力工場(可容納 30 人)、一個是論壇(16-20 人),我們想借這兩個場地,工場給 cofacts 辦基礎松,論壇我們 hold 基礎松這樣~~~~

詳細的場地圖跟設備人數我們會再更新到共筆上,在二樓的好處是大家可以直接走一個樓梯上二樓,不會被門禁卡住
好唷唷好唷非常感謝
cai 19:46:04
二次詐騙
https://cofacts.tw/article/3j1beh8yp1nkp
怪哉,換帳號了嗎
https://cofacts.tw/article/29bxfsspd2t95
這次竟然是被廣告推上來 😆
😮 2

2022-01-22

github2 10:29:57

<https://github.com/cofacts/rumors-fb-bot/pull/29|#29 Bump node-fetch from 2.2.0 to 3.1.1>

Bumps <https://github.com/node-fetch/node-fetch|node-fetch> from 2.2.0 to 3.1.1. Release notes _Sourced from <https://github.com/node-fetch/node-fetch/releases|node-fetch's releases>._ &gt; *v3.1.1* &gt; *Security patch release* &gt; &gt; Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred &gt; &gt; *What's Changed* &gt; &gt; • core: update fetch-blob by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1371|node-fetch/node-fetch#1371> &gt; • docs: Fix typo around sending a file by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1381|node-fetch/node-fetch#1381> &gt; • core: (http.request): Cast URL to string before sending it to NodeJS core by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1378|node-fetch/node-fetch#1378> &gt; • core: handle errors from the request body stream by <https://github.com/mdmitry01|`@​mdmitry01`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1392|node-fetch/node-fetch#1392> &gt; • core: Better handle wrong redirect header in a response by <https://github.com/tasinet|`@​tasinet`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1387|node-fetch/node-fetch#1387> &gt; • core: Don't use buffer to make a blob by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1402|node-fetch/node-fetch#1402> &gt; • docs: update readme for TS `@​types/node-fetch` by <https://github.com/adamellsworth|`@​adamellsworth`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1405|node-fetch/node-fetch#1405> &gt; • core: Fix logical operator priority to disallow GET/HEAD with non-empty body by <https://github.com/maxshirshin|`@​maxshirshin`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1369|node-fetch/node-fetch#1369> &gt; • core: Don't use global buffer by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1422|node-fetch/node-fetch#1422> &gt; • ci: fix main branch by <https://github.com/dnalborczyk|`@​dnalborczyk`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1429|node-fetch/node-fetch#1429> &gt; • core: use more node: protocol imports by <https://github.com/dnalborczyk|`@​dnalborczyk`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1428|node-fetch/node-fetch#1428> &gt; • core: Warn when using data by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1421|node-fetch/node-fetch#1421> &gt; • docs: Create SECURITY.md by <https://github.com/JamieSlome|`@​JamieSlome`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1445|node-fetch/node-fetch#1445> &gt; • core: don't forward secure headers to 3th party by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1449|node-fetch/node-fetch#1449> &gt; &gt; *New Contributors* &gt; &gt; • <https://github.com/mdmitry01|`@​mdmitry01`> made their first contribution in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1392|node-fetch/node-fetch#1392> &gt; • <https://github.com/tasinet|`@​tasinet`> made their first contribution in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1387|node-fetch/node-fetch#1387> &gt; • <https://github.com/adamellsworth|`@​adamellsworth`> made their first contribution in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1405|node-fetch/node-fetch#1405> &gt; • <https://github.com/maxshirshin|`@​maxshirshin`> made their first contribution in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1369|node-fetch/node-fetch#1369> &gt; • <https://github.com/JamieSlome|`@​JamieSlome`> made their first contribution in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1445|node-fetch/node-fetch#1445> &gt; &gt; *Full Changelog*: <https://github.com/node-fetch/node-fetch/compare/v3.1.0...v3.1.1|node-fetch/node-fetch@v3.1.0...v3.1.1> &gt; &gt; *v3.1.0* &gt; *What's Changed* &gt; &gt; • fix(Body): Discourage form-data and buffer() by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1212|node-fetch/node-fetch#1212> &gt; • fix: Pass url string to http.request by <https://github.com/serverwentdown|`@​serverwentdown`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1268|node-fetch/node-fetch#1268> &gt; • Fix octocat image link by <https://github.com/lakuapik|`@​lakuapik`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1281|node-fetch/node-fetch#1281> &gt; • fix(Body.body): Normalize `Body.body` into a `node:stream` by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/924|node-fetch/node-fetch#924> &gt; • docs(Headers): Add default Host request header to README.md file by <https://github.com/robertoaceves|`@​robertoaceves`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1316|node-fetch/node-fetch#1316> &gt; • Update CHANGELOG.md by <https://github.com/jimmywarting|`@​jimmywarting`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1292|node-fetch/node-fetch#1292> &gt; • Add highWaterMark to cloned properties by <https://github.com/davesidious|`@​davesidious`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1162|node-fetch/node-fetch#1162> &gt; • Update README.md to fix HTTPResponseError by <https://github.com/thedanfernandez|`@​thedanfernandez`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1135|node-fetch/node-fetch#1135> &gt; • docs: switch `url` to `URL` by <https://github.com/dhritzkiv|`@​dhritzkiv`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1318|node-fetch/node-fetch#1318> &gt; • fix(types): declare buffer() deprecated by <https://github.com/dnalborczyk|`@​dnalborczyk`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1345|node-fetch/node-fetch#1345> &gt; • chore: fix lint by <https://github.com/dnalborczyk|`@​dnalborczyk`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1348|node-fetch/node-fetch#1348> &gt; • refactor: use node: prefix for imports by <https://github.com/dnalborczyk|`@​dnalborczyk`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1346|node-fetch/node-fetch#1346> &gt; • Bump data-uri-to-buffer from 3.0.1 to 4.0.0 by <https://github.com/dependabot|`@​dependabot`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1319|node-fetch/node-fetch#1319> &gt; • Bump mocha from 8.4.0 to 9.1.3 by <https://github.com/dependabot|`@​dependabot`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1339|node-fetch/node-fetch#1339> &gt; • Referrer and Referrer Policy by <https://github.com/tekwiz|`@​tekwiz`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1057|node-fetch/node-fetch#1057> &gt; • Add typing for Response.redirect(url, status) by <https://github.com/c-w|`@​c-w`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1169|node-fetch/node-fetch#1169> &gt; • chore: Correct stuff in README.md by <https://github.com/Jiralite|`@​Jiralite`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1361|node-fetch/node-fetch#1361> &gt; • docs: Improve clarity of "Loading and configuring" by <https://github.com/serverwentdown|`@​serverwentdown`> in <https://github-redirect.dependabot.com/node-fetch/node-fetch/pull/1323|node-fetch/nod…

2022-01-23

oldmon 16:50:54
@oldmon has joined the channel

2022-01-24

github2 00:49:03

<https://github.com/cofacts/rumors-site/pull/470|#470 Implement ActionMenu and refactor article replies>

• Extract `ActionMenu` (menu with vertical "⋯" button) from `ReplyActions` • We will be adding that to reply requests and article reply feedbacks, thus extracting them will be beneficial • Apperance adhere to <https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1019%3A89|https://www.figma.com/file/zpD45j8nqDB2XfA6m2QskO/Cofacts-website?node-id=1019%3A89> • Replace verbose props of `ReplyAction` to one single `articleReply` • Previously there is an insane prop drill of `actionText`, `disabled` &amp; `onAction` props from `CurrentReplies` &amp; `reply/[id]` all the way down to `ReplyAction` • However, all it needs to perform action is a article-reply instance. • Minor behavior change: after restoring a reply from "Deleted replies" dialog, the dialog will not close automatically if there are still other deleted replies. I think this behavior is OK for the users. • Remove unused props from components like `ArticleReply`, `DeletedItems` • They are not used in codebase at all...... *ActionMenu* <https://user-images.githubusercontent.com/108608/150688855-f3d83c6a-c793-4aa7-ba1a-f96c1fe74f25.png|圖片>

:white_check_mark: All checks have passed

github2 00:57:07

<https://github.com/cofacts/rumors-site/pull/470#issuecomment-1019524716|Comment on #470 Implement ActionMenu and refactor article replies>

<https://coveralls.io/builds/45859339|Coverage Status> Coverage decreased (-0.06%) to 74.628% when pulling *<https://github.com/cofacts/rumors-site/commit/8ada7da5d1fcfb026008c9cff3ae266147ee096d|8ada7da> on refactor-reply-action* into *<https://github.com/cofacts/rumors-site/commit/d10987d801e181c66c041906b6d0f9f1c0f57d9c|d10987d> on master*.

2022-01-25

oldmon 10:50:09
@oldmon has left the channel
github2 12:26:40

<https://github.com/cofacts/rumors-site/pull/472|#472 Make 真的假的 more prominant in zh locale>

As discussed in weekly meeting, we changed more Cofacts to 真的假的 in the Mandarin UI for better branding. <https://user-images.githubusercontent.com/108608/150910823-4db3e47d-a6ee-4cd6-a8dc-3c75d1bc1974.png|image> <https://user-images.githubusercontent.com/108608/150910547-b43f32f0-d102-4f06-b092-acfe19b1f831.png|image> <https://user-images.githubusercontent.com/108608/150910731-78aecf7f-3d68-47dd-b28b-660451d7eb06.png|image>

:white_check_mark: All checks have passed

github2 12:29:00

<https://github.com/cofacts/rumors-site/pull/472#issuecomment-1020800472|Comment on #472 Make 真的假的 more prominant in zh locale>

<https://coveralls.io/builds/45909282|Coverage Status> Coverage remained the same at 74.692% when pulling *<https://github.com/cofacts/rumors-site/commit/4ddbed588b925925ac40e5af714973cd9ff13c1b|4ddbed5> on mandarin-name* into *<https://github.com/cofacts/rumors-site/commit/d10987d801e181c66c041906b6d0f9f1c0f57d9c|d10987d> on master*.

mrorz 12:51:55
回報違規內容的功能現在在 Staging 上囉
可以回報的有「補充」、「回應」與針對回應的「feedback」
也需要先登入 Cofacts 才在 UI 上看得到這個功能
這次的變更改到滿多東西的,希望沒有弄壞其他功能,大家可以測看看~
https://dev.cofacts.tw/article/35s3oqkdq8qys
表單程式自動填寫部分能鎖起來不給編輯嗎?
沒辦法,但我在 spreadsheet 端有做驗證,item id, item type 與 user id 都要對才抓得到資料
ichieh 18:37:43
@bil @mrorz 想跟你們討論一下空間~

因為 3/12 我們也考慮要辦基礎松,想說可以辦在一起,NPO HUB 二樓有一些新的空間,一個叫影響力工場(可容納 30 人)、一個是論壇(16-20 人),我們想借這兩個場地,工場給 cofacts 辦基礎松,論壇我們 hold 基礎松這樣~~~~

詳細的場地圖跟設備人數我們會再更新到共筆上,在二樓的好處是大家可以直接走一個樓梯上二樓,不會被門禁卡住
👍 2

2022-01-26

cai 00:51:57
https://professorlin.com/2022/01/21/近九成染疫死亡者已完全接種疫苗?/
> 註2:台灣的《Cofacts真的假的》網頁裡有人在問《覺醒時刻》這篇文章的真實性,而有人回答《大致正確》
回正確的是哪篇啊?
找到的一篇是空的,另一篇是說錯誤
https://cofacts.tw/article/199afj82wynm8 的網友回報補充嗎
(broadly correct)
cai 00:51:57
https://professorlin.com/2022/01/21/近九成染疫死亡者已完全接種疫苗?/
> 註2:台灣的《Cofacts真的假的》網頁裡有人在問《覺醒時刻》這篇文章的真實性,而有人回答《大致正確》
回正確的是哪篇啊?
找到的一篇是空的,另一篇是說錯誤
https://cofacts.tw/article/199afj82wynm8 的網友回報補充嗎
(broadly correct)
github2 21:37:01

<https://github.com/cofacts/rumors-site/pull/473|#473 Shrink userId, itemId and url into 1 field only when reporting user>

Now only 2 pre-filled fields left. <https://user-images.githubusercontent.com/108608/151172654-3b6a1298-d783-4354-ae1f-abf1285284a0.png|圖片>

:white_check_mark: All checks have passed

github2 21:37:01

<https://github.com/cofacts/rumors-site/pull/473|#473 Shrink userId, itemId and url into 1 field only when reporting user>

Now only 2 pre-filled fields left. <https://user-images.githubusercontent.com/108608/151172654-3b6a1298-d783-4354-ae1f-abf1285284a0.png|圖片>

github2 21:41:04

<https://github.com/cofacts/rumors-site/pull/473#issuecomment-1022207279|Comment on #473 Shrink userId, itemId and url into 1 field only when reporting user>

<https://coveralls.io/builds/45966276|Coverage Status> Coverage decreased (-0.05%) to 73.942% when pulling *<https://github.com/cofacts/rumors-site/commit/675a861cb1abd49dbd0b94c22d1c4264b93a9fdf|675a861> on shrink-report-fields* into *<https://github.com/cofacts/rumors-site/commit/ebf9f1d4004c4c9d56beb780bb78066f7c4a0fc2|ebf9f1d> on master*.

github2 21:41:04

<https://github.com/cofacts/rumors-site/pull/473#issuecomment-1022207279|Comment on #473 Shrink userId, itemId and url into 1 field only when reporting user>

<https://coveralls.io/builds/45966276|Coverage Status> Coverage decreased (-0.05%) to 73.942% when pulling *<https://github.com/cofacts/rumors-site/commit/675a861cb1abd49dbd0b94c22d1c4264b93a9fdf|675a861> on shrink-report-fields* into *<https://github.com/cofacts/rumors-site/commit/ebf9f1d4004c4c9d56beb780bb78066f7c4a0fc2|ebf9f1d> on master*.

2022-01-27

cai 00:15:41
恩......刪回應壞掉了
https://cofacts.tw/article/vc8whxb2uhgn
送出才想到忘了加病名 😆
感謝回報 QQ 來修
Fixed
cai 00:15:41
恩......刪回應壞掉了
https://cofacts.tw/article/vc8whxb2uhgn
送出才想到忘了加病名 😆
感謝回報 QQ 來修
Fixed
😮 1
cai 08:51:17
為什麼去年6月的宜蘭訊息 這2天又一堆人問
假訊息總是可以找到去年沒有收到的人來傳 XD
cai 08:51:17
為什麼去年6月的宜蘭訊息 這2天又一堆人問
假訊息總是可以找到去年沒有收到的人來傳 XD

2022-01-28

cai 13:09:59
https://cofacts.tw/article/1en8thk9rlnvx
去年5/28的今天2人問 ?
到底是要算正確還是錯誤阿XDD
歐這有點難
因為搞不好其實是 OCR 之後中到這篇
因為每天發布的圖,文字都差不多(可能會 match),只有數字不一樣⋯⋯
cai 13:09:59
https://cofacts.tw/article/1en8thk9rlnvx
去年5/28的今天2人問 ?
到底是要算正確還是錯誤阿XDD
歐這有點難
因為搞不好其實是 OCR 之後中到這篇
因為每天發布的圖,文字都差不多(可能會 match),只有數字不一樣⋯⋯
johnson 14:04:54
@chnejohnson has joined the channel
cai 19:09:22
165的詐騙手法懶人包,附件檔案比較詳細。
https://165.npa.gov.tw/#/article/news/465
cai 19:09:22
165的詐騙手法懶人包,附件檔案比較詳細。
https://165.npa.gov.tw/#/article/news/465
1

2022-01-29

cai 20:42:47
`https://wishenger.com/hsar/zh/?f=` 為什麼這網址每到過年就開始狂出現啦 😆
cai 20:42:47
`https://wishenger.com/hsar/zh/?f=` 為什麼這網址每到過年就開始狂出現啦 😆
mrorz 23:43:40
新格式唷,是從檢舉內容生成的公告
請大家看看有沒有什麼想要補充的資訊~~

2022-01-30

2022-01-31

mrorz 23:57:24
爆竹一聲除舊歲,也除廣告帳號唷~~~
右邊有下架公告的這些,都已經從資料庫裡移除囉!
祝大家新年快樂~
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXk[…]7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml?gid=438362561&single=true
mrorz 23:57:24
爆竹一聲除舊歲,也除廣告帳號唷~~~
右邊有下架公告的這些,都已經從資料庫裡移除囉!
祝大家新年快樂~
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXk[…]7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml?gid=438362561&single=true