#cofacts
2022-05-01
2022-05-03
Done in <https://github.com/cofacts/rumors-line-bot/pull/303|#303>
Done in <https://github.com/cofacts/rumors-line-bot/pull/303|#303>
只是想要有合理的理由買酒ㄅ (欸
只是想要有合理的理由買酒ㄅ (欸
2022-05-04
只是想要有合理的理由買酒ㄅ (欸
Personally I don't know why this would change XD For DOM elements, `{true}` and `"true"` are probably identical
Personally I don't know why this would change XD For DOM elements, `{true}` and `"true"` are probably identical
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
2022-05-05
@zhoulitong53 has joined the channel
Close by <https://github.com/cofacts/rumors-site/pull/484|#484>
Close by <https://github.com/cofacts/rumors-site/pull/484|#484>
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
<https://github.com/dependabot|@dependabot> rebase
<https://github.com/dependabot|@dependabot> rebase
<https://github.com/dependabot|@dependabot> recreate
<https://github.com/dependabot|@dependabot> recreate
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting `@dependabot rebase`.
right?
晚上否決分類一直碰到 `An unexpected error has occurred.`
週三晚上測試的時候好像也有遇到
好的我看看 local 是否可以重現
好的我看看 local 是否可以重現
我懷疑是 next.js 升級的問題
upvote / downvote 現在也會整個頁面閃爍
upvote / downvote 現在也會整個頁面閃爍
晚上否決分類一直碰到 `An unexpected error has occurred.`
週三晚上測試的時候好像也有遇到
好的我看看 local 是否可以重現
好的我看看 local 是否可以重現
我懷疑是 next.js 升級的問題
upvote / downvote 現在也會整個頁面閃爍
upvote / downvote 現在也會整個頁面閃爍
2022-05-06
我網路各種卡，這篇後續交給大家啦
https://cofacts.tw/article/3uxpz579mhtcr
https://cofacts.g0v.tw/article/11uhgg6jod1yr
目前查到是彰化的婦產科醫生，但我找不到原始影片 https://www.tiktok.com/@ok047260678
https://cofacts.tw/article/3uxpz579mhtcr
https://cofacts.g0v.tw/article/11uhgg6jod1yr
目前查到是彰化的婦產科醫生，但我找不到原始影片 https://www.tiktok.com/@ok047260678
他有換髮型ㄇ
沒有換，背景跟衣服都有找到，但是在tiktok 那頻道找不到跟被說是黃立民那部終局之戰相同的影片
https://www.tiktok.com/@ok047260678/video/7091815897383324955 直接用google搜尋找到了........
為什麼我從頻道翻找不到😅
太強了
我一直打錯字
我懶得改了（躺平
我懶得改了（躺平
@iacmai 找到原始影片真的很厲害 👍
我爸爸今天傳這個給我看XD
他傳的左上角有「台大兒童醫院院長」ㄇ
我覺得很扯啊，明明長得不像
有黃立民
LINE 轉傳者邏輯：男性粗框眼鏡有法令紋=黃立民
髮型不同？一定是有燙，反正就是黃立民
聲音不同？耳朵業障重，反正就是黃立民
事實查核中心有去找他
tiktok那邊也有
我網路各種卡，這篇後續交給大家啦
https://cofacts.tw/article/3uxpz579mhtcr
https://cofacts.g0v.tw/article/11uhgg6jod1yr
目前查到是彰化的婦產科醫生，但我找不到原始影片 https://www.tiktok.com/@ok047260678
https://cofacts.tw/article/3uxpz579mhtcr
https://cofacts.g0v.tw/article/11uhgg6jod1yr
目前查到是彰化的婦產科醫生，但我找不到原始影片 https://www.tiktok.com/@ok047260678
他有換髮型ㄇ
沒有換，背景跟衣服都有找到，但是在tiktok 那頻道找不到跟被說是黃立民那部終局之戰相同的影片
https://www.tiktok.com/@ok047260678/video/7091815897383324955 直接用google搜尋找到了........
為什麼我從頻道翻找不到😅
太強了
我一直打錯字
我懶得改了（躺平
我懶得改了（躺平
@iacmai 找到原始影片真的很厲害 👍
我爸爸今天傳這個給我看XD
他傳的左上角有「台大兒童醫院院長」ㄇ
我覺得很扯啊，明明長得不像
有黃立民
LINE 轉傳者邏輯：男性粗框眼鏡有法令紋=黃立民
髮型不同？一定是有燙，反正就是黃立民
聲音不同？耳朵業障重，反正就是黃立民
事實查核中心有去找他
tiktok那邊也有
週三晚上測試的時候好像也有遇到
好的我看看 local 是否可以重現
好的我看看 local 是否可以重現
他有換髮型ㄇ
沒有換，背景跟衣服都有找到，但是在tiktok 那頻道找不到跟被說是黃立民那部終局之戰相同的影片
https://www.tiktok.com/@ok047260678/video/7091815897383324955 直接用google搜尋找到了........
為什麼我從頻道翻找不到😅
太強了
我一直打錯字
我懶得改了（躺平
我懶得改了（躺平
@iacmai 找到原始影片真的很厲害 👍
我爸爸今天傳這個給我看XD
他傳的左上角有「台大兒童醫院院長」ㄇ
我覺得很扯啊，明明長得不像
有黃立民
LINE 轉傳者邏輯：男性粗框眼鏡有法令紋=黃立民
髮型不同？一定是有燙，反正就是黃立民
聲音不同？耳朵業障重，反正就是黃立民
Replied to a thread: 2022-05-05 22:52:29
我懷疑是 next.js 升級的問題
upvote / downvote 現在也會整個頁面閃爍
upvote / downvote 現在也會整個頁面閃爍
事實查核中心有去找他
tiktok那邊也有
2022-05-07
https://cofacts.tw/article/1dg6x88i6pd7m 這個縮網址點開是嚇人的圖片跟很大聲的音樂
https://cofacts.g0v.tw/article/2079ma0q52mwx
看樣子因為那詐騙比賽網站關了，人也被踢出群組，所以暴增
看樣子因為那詐騙比賽網站關了，人也被踢出群組，所以暴增
https://cofacts.g0v.tw/article/2079ma0q52mwx
看樣子因為那詐騙比賽網站關了，人也被踢出群組，所以暴增
看樣子因為那詐騙比賽網站關了，人也被踢出群組，所以暴增
想找紓困4.0 結束日期的資料找不到 🤔
三不五時出現拿去年新聞來亂的
三不五時出現拿去年新聞來亂的
官網沒有資訊嗎😮
想找紓困4.0 結束日期的資料找不到🤔
官網沒有資訊嗎😮
官網沒有資訊嗎😮
2022-05-08
2022-05-09
這個好難喔
到底是受害者還是詐騙集團
從看他回應、對其他人的 feedback (有在拉人加自己 ID) 與 comment 看不出來⋯⋯
https://cofacts.github.io/community-builder/#/editorworks?type=1&day=365&userId=6CbfdYABvUvLpBdg_Hz_&showAll=1
到底是受害者還是詐騙集團
從看他回應、對其他人的 feedback (有在拉人加自己 ID) 與 comment 看不出來⋯⋯
https://cofacts.github.io/community-builder/#/editorworks?type=1&day=365&userId=6CbfdYABvUvLpBdg_Hz_&showAll=1
cofacts.github.io 
ID 不存在可能是被檢舉刪掉了？
也有可能是被提醒之後關閉搜尋
很難
這個好難喔
到底是受害者還是詐騙集團
從看他回應、對其他人的 feedback (有在拉人加自己 ID) 與 comment 看不出來⋯⋯
https://cofacts.github.io/community-builder/#/editorworks?type=1&day=365&userId=6CbfdYABvUvLpBdg_Hz_&showAll=1
到底是受害者還是詐騙集團
從看他回應、對其他人的 feedback (有在拉人加自己 ID) 與 comment 看不出來⋯⋯
https://cofacts.github.io/community-builder/#/editorworks?type=1&day=365&userId=6CbfdYABvUvLpBdg_Hz_&showAll=1
ID 不存在可能是被檢舉刪掉了？
也有可能是被提醒之後關閉搜尋
很難
ID 不存在可能是被檢舉刪掉了？
也有可能是被提醒之後關閉搜尋
很難
https://cofacts.g0v.tw/reply/dCZJpoABvUvLpBdgMrdl
鹽水漱口這系列可能要觀察 🤔
一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
鹽水漱口這系列可能要觀察 🤔
一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
好奇妙喔
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
鹽水漱口說不定是類似的自然療法派
鹽水漱口是我爸的絕招欸XD 以前出什麼事情都要用鹽水漱口
鹽水漱口這說法在沒有疫情前就有了，就以前的偏方
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
天哪是超愛鹽水漱口的Mark Chen嗎
將近50篇
> 一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
他的回應裡面跟 COVID 相關的只有 India Times 那篇報導
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
怎麼這麼重口味，鹽水play欸
https://cofacts.g0v.tw/reply/dCZJpoABvUvLpBdgMrdl
鹽水漱口這系列可能要觀察 🤔
一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
鹽水漱口這系列可能要觀察 🤔
一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
好奇妙喔
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
鹽水漱口說不定是類似的自然療法派
鹽水漱口是我爸的絕招欸XD 以前出什麼事情都要用鹽水漱口
鹽水漱口這說法在沒有疫情前就有了，就以前的偏方
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
天哪是超愛鹽水漱口的Mark Chen嗎
將近50篇
> 一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
他的回應裡面跟 COVID 相關的只有 India Times 那篇報導
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
怎麼這麼重口味，鹽水play欸
好奇妙喔
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
是說推廣自然療法那的這個健康1+1
https://cofacts.g0v.tw/article/1iy8si8y368xr
看起來是大紀元系統的，主要在 channel 裡面推廣自然療法
一些自然療法論述+降低或拿掉對疫苗的批判，在台灣的言論市場就滿吃得開的樣子
鹽水漱口說不定是類似的自然療法派
鹽水漱口是我爸的絕招欸XD 以前出什麼事情都要用鹽水漱口
鹽水漱口這說法在沒有疫情前就有了，就以前的偏方
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
會注意到這串主要是因為有三個同時按同一系列讚
還是今天有cofacts的推廣活動嗎？
天哪是超愛鹽水漱口的Mark Chen嗎
將近50篇
> 一個人回完一連串系列文後（每篇都是單獨回），又出現多個沒看過的已登入帳號按讚按同一系列回答讚
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
在社團提報 coordinated inauthentic behavior 如何
協同的回應 + 按讚行為
2022-05-10
他的回應裡面跟 COVID 相關的只有 India Times 那篇報導
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
而背後的論文是這篇
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7528968/#bib0022
怎麼這麼重口味，鹽水play欸
三總謝醫師錄音檔
https://cofacts.tw/article/3610fr67urm0w
https://cofacts.tw/article/2zkb17rac7ezu
https://cofacts.tw/article/3a9lam6u7tt7a
https://cofacts.tw/article/3610fr67urm0w
https://cofacts.tw/article/2zkb17rac7ezu
https://cofacts.tw/article/3a9lam6u7tt7a
- 👍1
假冠名機率應該很大
同感
原來文字版是 5/1 就在傳了
三總謝醫師假冠名則是 5/5
三總謝醫師假冠名則是 5/5
內容不一樣欸
咦咦咦咦不一樣嗎
所以有兩種ㄇ
不同喔 這次的錄音是不要在外脫口罩跟內用
mygopen 的音檔是居家照護不給藥
而且 mygopen 的聲音檔有提到三總
還是不要內用的是 5/1 開始傳的那些文字版而已
三總那個是 mygopen 的音檔？
三總那個是 mygopen 的音檔？
`還是不要內用的是 5/1 開始傳的那些文字版而已`
`三總那個是 mygopen 的音檔？`
`三總那個是 mygopen 的音檔？`
@mrorz
`還是不要內用的是 5/1 開始傳的那些文字版而已`
看起來是
`三總那個是 mygopen 的音檔？`
？？？
`還是不要內用的是 5/1 開始傳的那些文字版而已`
看起來是
`三總那個是 mygopen 的音檔？`
？？？
就是 4000 提供的音檔
真的是跟著三總的文案在一起散佈的這樣嗎
真的是跟著三總的文案在一起散佈的這樣嗎
等等
https://www.facebook.com/permalink.php?story_fbid=pfbid0cV7k9bY1X3yjDHtKrgVxqUX8tkT6urGTYuHmA3CS119cKBuBdgqNPGRXQnbLSLCSl&id=100010996188784
這裡的截圖是 1:41 的音檔，跟 @andyy0216 的音檔一致
https://www.facebook.com/permalink.php?story_fbid=pfbid0cV7k9bY1X3yjDHtKrgVxqUX8tkT6urGTYuHmA3CS119cKBuBdgqNPGRXQnbLSLCSl&id=100010996188784
這裡的截圖是 1:41 的音檔，跟 @andyy0216 的音檔一致
而 MyGoPen 的截圖裡面也有長度，但是是 2:26 的版本
也就是說，真的有兩個音檔在傳
感謝提供
所以真的有兩份音檔囧
突然想起自己可能有加過一個有長輩的群組 果然沒令我失望XD
這兩天越南超級秘方的抖音也在裡面傳
越南超級秘方是啥 XDD
喝茶加檸檬治肺炎
https://cofacts.tw/article/1hv0gwyb6xtyv 這次換北市秘書處？
不知道～～
我努力在 media manager 加把勁好了，希望儘早可以收這些檔案進資料庫 QQ
我努力在 media manager 加把勁好了，希望儘早可以收這些檔案進資料庫 QQ
下次看到奇怪的交友網站網址有新聞可以當佐證了
https://news.ltn.com.tw/news/society/breakingnews/3919463
https://udn.com/news/story/7315/6297493
https://news.ltn.com.tw/news/society/breakingnews/3919463
https://udn.com/news/story/7315/6297493
什麼是位置2000電話5000🤔
開通費阿
對方所在地點2000 電話5000
對方所在地點2000 電話5000
了解哈哈
可以偽造的位置竟然還要2000金幣 😆
真好賺 隨便講就好了 我在月球XD
https://cofacts.g0v.tw/article/2cxbm4zpv2kr2
詐騙吸引人的理由越來越奇葩了
詐騙吸引人的理由越來越奇葩了
下次看到奇怪的交友網站網址有新聞可以當佐證了
https://news.ltn.com.tw/news/society/breakingnews/3919463
https://udn.com/news/story/7315/6297493
https://news.ltn.com.tw/news/society/breakingnews/3919463
https://udn.com/news/story/7315/6297493
2
2
什麼是位置2000電話5000🤔
開通費阿
對方所在地點2000 電話5000
對方所在地點2000 電話5000
了解哈哈
可以偽造的位置竟然還要2000金幣 😆
真好賺 隨便講就好了 我在月球XD
https://cofacts.g0v.tw/article/2cxbm4zpv2kr2
詐騙吸引人的理由越來越奇葩了
詐騙吸引人的理由越來越奇葩了
假冠名機率應該很大
同感
什麼是位置2000電話5000🤔
開通費阿
對方所在地點2000 電話5000
對方所在地點2000 電話5000
了解哈哈
可以偽造的位置竟然還要2000金幣 😆
真好賺 隨便講就好了 我在月球XD
https://cofacts.g0v.tw/article/2cxbm4zpv2kr2
詐騙吸引人的理由越來越奇葩了
詐騙吸引人的理由越來越奇葩了
2022-05-11
原來文字版是 5/1 就在傳了
三總謝醫師假冠名則是 5/5
三總謝醫師假冠名則是 5/5
內容不一樣欸
咦咦咦咦不一樣嗎
所以有兩種ㄇ
不同喔 這次的錄音是不要在外脫口罩跟內用
mygopen 的音檔是居家照護不給藥
而且 mygopen 的聲音檔有提到三總
還是不要內用的是 5/1 開始傳的那些文字版而已
三總那個是 mygopen 的音檔？
三總那個是 mygopen 的音檔？
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
image / text in article list 混排 v.s. 分開排
image / text in article list 混排 v.s. 分開排
`還是不要內用的是 5/1 開始傳的那些文字版而已`
`三總那個是 mygopen 的音檔？`
`三總那個是 mygopen 的音檔？`
@mrorz
`還是不要內用的是 5/1 開始傳的那些文字版而已`
看起來是
`三總那個是 mygopen 的音檔？`
？？？
`還是不要內用的是 5/1 開始傳的那些文字版而已`
看起來是
`三總那個是 mygopen 的音檔？`
？？？
就是 4000 提供的音檔
真的是跟著三總的文案在一起散佈的這樣嗎
真的是跟著三總的文案在一起散佈的這樣嗎
等等
https://www.facebook.com/permalink.php?story_fbid=pfbid0cV7k9bY1X3yjDHtKrgVxqUX8tkT6urGTYuHmA3CS119cKBuBdgqNPGRXQnbLSLCSl&id=100010996188784
這裡的截圖是 1:41 的音檔，跟 @andyy0216 的音檔一致
https://www.facebook.com/permalink.php?story_fbid=pfbid0cV7k9bY1X3yjDHtKrgVxqUX8tkT6urGTYuHmA3CS119cKBuBdgqNPGRXQnbLSLCSl&id=100010996188784
這裡的截圖是 1:41 的音檔，跟 @andyy0216 的音檔一致
而 MyGoPen 的截圖裡面也有長度，但是是 2:26 的版本
也就是說，真的有兩個音檔在傳
感謝提供
所以真的有兩份音檔囧
突然想起自己可能有加過一個有長輩的群組 果然沒令我失望XD
這兩天越南超級秘方的抖音也在裡面傳
越南超級秘方是啥 XDD
喝茶加檸檬治肺炎
Found in <https://g0v.hackmd.io/Y40dNpVBSbKF-NHqfmdGNQ#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|20220504 pre-release check> and can be reproduced easily on production.
Found in <https://g0v.hackmd.io/Y40dNpVBSbKF-NHqfmdGNQ#%E6%9C%AA%E7%AB%9F%E9%A0%85%E7%9B%AE|20220504 pre-release check> and can be reproduced easily on production. Related incident report on slack: <https://g0v-slack-archive.g0v.ronny.tw/index/channel/C2PPMRQGP#ts-1651762349.5851|https://g0v-slack-archive.g0v.ronny.tw/index/channel/C2PPMRQGP#ts-1651762349.5851>
2022-05-12
Cofacts 網站跟 chatbot 都仰賴 google 的 universal analytics
結果 ua 明年 7 月就不能用了囧
https://support.google.com/analytics/answer/11583528
結果 ua 明年 7 月就不能用了囧
https://support.google.com/analytics/answer/11583528
support.google.com
Last updated: March 16, 2022. Visit this page in the coming months for the latest information. Google Analytics 4 is our next-generation measurement solution, and it's replacing Universal Analytics.
- 😢1
- 😂1
先盤點了一下
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
Cofacts 網站跟 chatbot 都仰賴 google 的 universal analytics
結果 ua 明年 7 月就不能用了囧
https://support.google.com/analytics/answer/11583528
結果 ua 明年 7 月就不能用了囧
https://support.google.com/analytics/answer/11583528
先盤點了一下
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
https://cofacts.tw/article/1hv0gwyb6xtyv 這次換北市秘書處？
https://cofacts.tw/article/oavr50k4ep8r
為什麼5/6 回報的是3/12小聚XDD
為什麼5/6 回報的是3/12小聚XDD
https://cofacts.g0v.tw/article/1dcvnyd6hb4ee
這應該是問小聚的吧？
這應該是問小聚的吧？
再次丟機器人回應進來的也不少見
嚇死我
我還以為我們發錯
我還以為我們發錯
這個使用者大概兩個月來從來沒跟 Cofacts 說過話
所以兩篇公告連在一起
所以兩篇公告連在一起
https://cofacts.tw/article/oavr50k4ep8r
為什麼5/6 回報的是3/12小聚XDD
為什麼5/6 回報的是3/12小聚XDD
https://cofacts.g0v.tw/article/1dcvnyd6hb4ee
這應該是問小聚的吧？
這應該是問小聚的吧？
再次丟機器人回應進來的也不少見
嚇死我
我還以為我們發錯
我還以為我們發錯
這個使用者大概兩個月來從來沒跟 Cofacts 說過話
所以兩篇公告連在一起
所以兩篇公告連在一起
https://cofacts.g0v.tw/article/1dcvnyd6hb4ee
這應該是問小聚的吧？
這應該是問小聚的吧？
再次丟機器人回應進來的也不少見
嚇死我
我還以為我們發錯
我還以為我們發錯
這個使用者大概兩個月來從來沒跟 Cofacts 說過話
所以兩篇公告連在一起
所以兩篇公告連在一起
不知道～～
我努力在 media manager 加把勁好了，希望儘早可以收這些檔案進資料庫 QQ
我努力在 media manager 加把勁好了，希望儘早可以收這些檔案進資料庫 QQ
2022-05-13
<https://user-images.githubusercontent.com/108608/168217864-f5b29c87-be44-4278-9f16-ee41ccaa4a9c.png|圖片> Root cause TBA
<https://user-images.githubusercontent.com/108608/168217864-f5b29c87-be44-4278-9f16-ee41ccaa4a9c.png|圖片> Root cause TBA
Fixes <https://github.com/cofacts/rumors-site/issues/486|#486>. Root cause please see <https://github.com/cofacts/rumors-site/issues/486#issuecomment-1125673951|#486 (comment)> . I roughly checked other return value of `useQuery()`; other access of `data` prop are all properly guarded by `?.`. <https://user-images.githubusercontent.com/108608/168223209-bc464ec1-7532-4b9a-a4fe-bf17fd921593.png|圖片>
- 👌1
Fixes <https://github.com/cofacts/rumors-site/issues/486|#486>. Root cause please see <https://github.com/cofacts/rumors-site/issues/486#issuecomment-1125673951|#486 (comment)> . I roughly checked other return value of `useQuery()`; other access of `data` prop are all properly guarded by `?.`. <https://user-images.githubusercontent.com/108608/168223209-bc464ec1-7532-4b9a-a4fe-bf17fd921593.png|圖片>
<https://coveralls.io/builds/49091667|Coverage Status> Coverage remained the same at 75.531% when pulling *<https://github.com/cofacts/rumors-site/commit/149ab491ea6baeaaea6ab2bce701f21ec9b6bf7c|149ab49> on fix-downvote* into *<https://github.com/cofacts/rumors-site/commit/5326cca07fbc3aaae66850059b392bc31670c899|5326cca> on master*.
<https://coveralls.io/builds/49091667|Coverage Status> Coverage remained the same at 75.531% when pulling *<https://github.com/cofacts/rumors-site/commit/149ab491ea6baeaaea6ab2bce701f21ec9b6bf7c|149ab49> on fix-downvote* into *<https://github.com/cofacts/rumors-site/commit/5326cca07fbc3aaae66850059b392bc31670c899|5326cca> on master*.
Currently after up-voting or down-voting a reply, the whole article page will become "Loading...". It seems that in @apollo/react-hooks v3.1.5 the `loading` state behavior is slightly different from 3.0. This PR avoids "Loading..." page after an article is already displayed on screen. <https://user-images.githubusercontent.com/108608/168229724-520b5401-f69d-49d7-8cd8-82460e217918.gif|upvote-downvote>
這個再請大家看一下唷
希望今天可以上線 run 一天，明天小聚使用
希望今天可以上線 run 一天，明天小聚使用
Currently after up-voting or down-voting a reply, the whole article page will become "Loading...". It seems that in @apollo/react-hooks v3.1.5 the `loading` state behavior is slightly different from 3.0. This PR avoids "Loading..." page after an article is already displayed on screen. <https://user-images.githubusercontent.com/108608/168229724-520b5401-f69d-49d7-8cd8-82460e217918.gif|upvote-downvote>
這個再請大家看一下唷
希望今天可以上線 run 一天，明天小聚使用
希望今天可以上線 run 一天，明天小聚使用
<https://coveralls.io/builds/49092309|Coverage Status> Coverage remained the same at 75.531% when pulling *<https://github.com/cofacts/rumors-site/commit/1898fb0e0d4d1a8e631fbdd35f3415a3d8ac7f82|1898fb0> on avoid-flicker* into *<https://github.com/cofacts/rumors-site/commit/affe4651f733a16a9ffa165aa3d70411ef81399d|affe465> on master*.
<https://coveralls.io/builds/49092309|Coverage Status> Coverage remained the same at 75.531% when pulling *<https://github.com/cofacts/rumors-site/commit/1898fb0e0d4d1a8e631fbdd35f3415a3d8ac7f82|1898fb0> on avoid-flicker* into *<https://github.com/cofacts/rumors-site/commit/affe4651f733a16a9ffa165aa3d70411ef81399d|affe465> on master*.
This is deployed to staging: <https://dev.cofacts.tw/article/2889dua0k41ro|https://dev.cofacts.tw/article/2889dua0k41ro> Everyone can test it out on staging article page above. We can deliver it to production on Saturday to see if anything breaks. This should help the editor's meetup on Sunday as well.
This is deployed to staging: <https://dev.cofacts.tw/article/2889dua0k41ro|https://dev.cofacts.tw/article/2889dua0k41ro> Everyone can test it out on staging article page above. We can deliver it to production on Saturday to see if anything breaks. This should help the editor's meetup on Sunday as well.
Replied to a thread: 2022-05-12 01:44:54
先盤點了一下
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
• 目前用到 GA 的東西
• 升級 GA4 時要考慮的 mapping
放在共筆裡
https://g0v.hackmd.io/QRRlVa_URk-wT0QqahLN-w?view
目前是連到底要開幾個 GA4 property、幾個 data stream、chatbot 資料流怎麼接，都還沒有決定⋯⋯
2022-05-14
Replied to a thread: 2022-05-13 15:06:16
這個再請大家看一下唷
希望今天可以上線 run 一天，明天小聚使用
希望今天可以上線 run 一天，明天小聚使用
我發現這個修法有個副作用
https://github.com/cofacts/rumors-site/pull/488
就是如果我在 article page 從旁邊的相似可疑訊息裡面點選一篇
他在 load 新訊息的時候，不會進入 loading state
https://github.com/cofacts/rumors-site/pull/488
就是如果我在 article page 從旁邊的相似可疑訊息裡面點選一篇
他在 load 新訊息的時候，不會進入 loading state
我發現這個修法有個副作用
https://github.com/cofacts/rumors-site/pull/488
就是如果我在 article page 從旁邊的相似可疑訊息裡面點選一篇
他在 load 新訊息的時候，不會進入 loading state
https://github.com/cofacts/rumors-site/pull/488
就是如果我在 article page 從旁邊的相似可疑訊息裡面點選一篇
他在 load 新訊息的時候，不會進入 loading state
Currently after up-voting or down-voting a reply, the whole article page will become "Loading...". It seems that in @apollo/react-hooks v3.1.5 the `loading` state behavior is slightly different from 3.0. This PR avoids "Loading..." page after an article is already displayed on screen. <https://user-images.githubusercontent.com/108608/168229724-520b5401-f69d-49d7-8cd8-82460e217918.gif|upvote-downvote>
真煩 w
真煩 w
2022-05-15
1
1 --> 應該是協同
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
• https://cofacts.github.io/community-builder/#/editorworks?type=1&day=7&userId=iCZiwYABvUvLpBdg593j&showAll=1
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
https://cofacts.g0v.tw/article/AV2HK6GOyCdS-nWhudKS
1. 有點懷疑是上次講的協同舊文的分類可以按否決
1. 有點懷疑是上次講的協同舊文的分類可以按否決
1 --> 應該是協同
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
• https://cofacts.github.io/community-builder/#/editorworks?type=1&day=7&userId=iCZiwYABvUvLpBdg593j&showAll=1
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
1 --> 應該是協同
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
但情節還好，就是在一篇沒人問的東西下面回
我覺得刪除的回應是個不錯的平衡報導，刪除有點可惜
• https://cofacts.github.io/community-builder/#/editorworks?type=1&day=7&userId=iCZiwYABvUvLpBdg593j&showAll=1
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
• https://cofacts.github.io/community-builder/#/editorworks?type=0&day=7&userId=GSYJw4ABvUvLpBdgxuA-&showAll=1
關於以上兩者的事實：
1. `Alan` 與 `Mango` 在同一天先後註冊，均使用 Twitter 註冊
2. 兩個帳號的 email 前 7 字雷同
3. 一個帳號用 Android 手機、另一個帳號用 iOS 手機，IP 不同
SurveyCake
您好：為維護所有進出台北 NPO 聚落人員的安全，請協助填寫下列疫情調查表，並依據您的身份對應填寫問卷調查的時間：1. Hubber & Maker 調查時間：每月 05 號至 08 號2. 場租者、場租工作人員調查時間：場租活動前 3 天 ※建議接種 3 劑疫苗，以確保工作人員、會員和參加者有更健康安全的場地環境3. 場租活動參與者調查時間：活動當天進入會場前 ※建議至少接種 2 劑疫苗，以確保工作人員、會員和參加者有更健康安全的場地環境4. 參訪活動參與者調查時間：活動當天進入會場前 ※建議至少接種 2 劑疫苗，以確保工作人員、會員和參加者有更健康安全的場地環境如您或同住親友過去 14 天內有出國旅遊史者、出現發燒、咳嗽、呼吸困難等症狀或您有收到政府通報之檢疫、自主健康管理等通知，請立刻就醫，並與我們聯繫。※ 透過本問卷所蒐集、處理及利用之個人資料類別包含您的識別類個人資料、聯絡電話、個人健康狀況、旅遊史及活動與接觸史等資料，除上述防疫目的外不另作他用。若有任何問題，歡迎聯絡台北 NPO 聚落聯絡電話：02-2301-2160聯絡信箱：taipei.npo@impacthub.net
- 👍1
jserv 是那位大神嗎 😮
2022-05-16
Bumps <https://github.com/vercel/next.js|next> from 9.5.5 to 12.1.0. Release notes _Sourced from <https://github.com/vercel/next.js/releases|next's releases>._ > *v12.1.0* > *Core Changes* > > • Relay Support in Rust Compiler: <https://github-redirect.dependabot.com/vercel/next.js/issues/33702|#33702> > • fix eslint link-passhref rule: <https://github-redirect.dependabot.com/vercel/next.js/issues/33857|#33857> > • update webpack: <https://github-redirect.dependabot.com/vercel/next.js/issues/33831|#33831> > • Flush buffered vitals metrics on page mount: <https://github-redirect.dependabot.com/vercel/next.js/issues/33867|#33867> > • fix problem with HMR when middleware and page reference the same node_module: <https://github-redirect.dependabot.com/vercel/next.js/issues/33873|#33873> > • Refactor page component getter in web server: <https://github-redirect.dependabot.com/vercel/next.js/issues/33759|#33759> > • update NextResponse default redirect status to 307 to match docs: <https://github-redirect.dependabot.com/vercel/next.js/issues/33505|#33505> > • Bug fix: dynamic page should not be interpreted as predefined page: <https://github-redirect.dependabot.com/vercel/next.js/issues/33808|#33808> > • Group streaming experimental apis: <https://github-redirect.dependabot.com/vercel/next.js/issues/33878|#33878> > • Encapsulate routing and initial hydration: <https://github-redirect.dependabot.com/vercel/next.js/issues/33875|#33875> > • Optimize offline condition judgment: <https://github-redirect.dependabot.com/vercel/next.js/issues/33238|#33238> > • Ensure external beforeFiles rewrites are handled with next/link: <https://github-redirect.dependabot.com/vercel/next.js/issues/33888|#33888> > • Fix parsing params for i18n optional route in minimal mode: <https://github-redirect.dependabot.com/vercel/next.js/issues/33896|#33896> > • Ensure browserslist extends works properly: <https://github-redirect.dependabot.com/vercel/next.js/issues/33890|#33890> > • Fix image cache race condition: <https://github-redirect.dependabot.com/vercel/next.js/issues/33883|#33883> > • Add support for Relay projects without `artifactDirectory`: <https://github-redirect.dependabot.com/vercel/next.js/issues/33918|#33918> > • fix: handle jsxspreadattribute in inline-script-id eslint rule: <https://github-redirect.dependabot.com/vercel/next.js/issues/32421|#32421> > • feat(next-swc): Update swc: <https://github-redirect.dependabot.com/vercel/next.js/issues/33724|#33724> > • Update to latest version of amphtml-validator: <https://github-redirect.dependabot.com/vercel/next.js/issues/33967|#33967> > • Warn in dev mode when script tags are added with next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/33968|#33968> > • Ensure optional chaining in swc matches babel: <https://github-redirect.dependabot.com/vercel/next.js/issues/33995|#33995> > • Use `react-dom/server.browser` in Node.js: <https://github-redirect.dependabot.com/vercel/next.js/issues/33950|#33950> > • Ensure external middleware rewrite is handled correctly: <https://github-redirect.dependabot.com/vercel/next.js/issues/33962|#33962> > • Update Terser to v5.10.0, fix minification issues: <https://github-redirect.dependabot.com/vercel/next.js/issues/33045|#33045> > • Warn in dev mode when stylesheets are added using next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/34004|#34004> > • Use `ReadableStream` in `RenderResult`: <https://github-redirect.dependabot.com/vercel/next.js/issues/34005|#34005> > • Fix suffix ordering while streaming: <https://github-redirect.dependabot.com/vercel/next.js/issues/34011|#34011> > • Don't use yarn if a package-lock.json file is found: <https://github-redirect.dependabot.com/vercel/next.js/issues/31926|#31926> > • Do not warn when application/ld+json scripts are used with next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/34021|#34021> > • Babel & next-swc: Fix exporting page config with AsExpression: <https://github-redirect.dependabot.com/vercel/next.js/issues/32702|#32702> > • Detect per page runtime config for functions manifest: <https://github-redirect.dependabot.com/vercel/next.js/issues/33945|#33945> > • Add JSDoc to config options: <https://github-redirect.dependabot.com/vercel/next.js/issues/32915|#32915> > • Update font-stylesheet-gathering-plugin.ts: <https://github-redirect.dependabot.com/vercel/next.js/issues/30709|#30709> > • Add decoratorMetadata flag if enabled by tsconfig: <https://github-redirect.dependabot.com/vercel/next.js/issues/32914|#32914> > • fix: data url handling in css-loader: <https://github-redirect.dependabot.com/vercel/next.js/issues/34034|#34034> > • Place 'charset' element at the top of : <https://github-redirect.dependabot.com/vercel/next.js/issues/28119|#28119> > • Fix detection of anchor click events inside svg: <https://github-redirect.dependabot.com/vercel/next.js/issues/23272|#23272> > • Allow passing nothing as custom jest config: <https://github-redirect.dependabot.com/vercel/next.js/issues/32328|#32328> > • Fixes <https://github-redirect.dependabot.com/vercel/next.js/issues/31240|#31240>: Adding a recursive addPackagePath function in webpack-config: <https://github-redirect.dependabot.com/vercel/next.js/issues/31264|#31264> > • Require component rendered as child of `Link` to pass event to `onClick` handler: <https://github-redirect.dependabot.com/vercel/next.js/issues/27723|#27723> > • Allow scroll prevention on hash change: <https://github-redirect.dependabot.com/vercel/next.js/issues/31921|#31921> > • Add support for async fn / promise in next.config.js/.mjs: <https://github-redirect.dependabot.com/vercel/next.js/issues/33662|#33662> > • Fix `lazyRoot` functionality for `next/image`: <https://github-redirect.dependabot.com/vercel/next.js/issues/33933|#33933> > • Change SWC minify from beta to release candidate: <https://github-redirect.dependabot.com/vercel/next.js/issues/34056|#34056> > • Make `Router` state immutable: <https://github-redirect.dependabot.com/vercel/next.js/issues/33925|#33925> > • Stop exposing internal `render` and `renderError` methods from `next/client`: <https://github-redirect.dependabot.com/vercel/next.js/issues/34069|#34069> > • Add api-utils helper for testing: <https://github-redirect.dependabot.com/vercel/next.js/issues/34078|#34078> ... (truncated) Commits • <https://github.com/vercel/next.js/commit/8545fd1bb02244ced9e8dc9584a764aeae296cd0|`8545fd1`> v12.1.0 • <https://github.com/vercel/next.js/commit/1605f3059c7773a346998da5e1de416d106d8f32|`1605f30`> v12.0.11-canary.21 • <https://github.com/vercel/next.js/commit/69aedbd6667753f02b76563598342c8afa646dfa|`69aedbd`> Fix typo (<https://github-redirect.dependabot.com/vercel/next.js/issues/34480|#34480>) • <https://github.com/vercel/next.js/commit/f0f322c0d1655d722d133f963a84e575a61a5708|`f0f322c`> Remove deprecation for relative URL usage in middlewares (<https://github-redirect.dependabot.com/vercel/next.js/issues/34461|#34461>) • <https://github.com/vercel/next.js/commit/d4d79b2d9b9c43ed1061a3d3beeb3099368669a8|`d4d79b2`> Fix chunk buffering for server components (<https://github-redirect.dependabot.com/vercel/next.js/issues/34474|#34474>) • <https://github.com/vercel/next.js/commit/74fa4d4b93673a355d082473318562056571900f|`74fa4d4`> update webpack (<https://github-redirect.dependabot.com/vercel/next.js/issues/34477|#34477>) • <https://github.com/vercel/next.js/commit/b70397e770a0badfbafe9e2db8cb8bfeb1b06f9e|`b70397e`> Revert "Allow reading request bodies in middlewares (<https://github-redirect.dependabot.com/vercel/next.js/issues/34294|#34294>)" (<https://github-redirect.dependabot.com/vercel/next.js/issues/34479|#34479>) • <https://github.com/vercel/next.js/commit/42020114d2ada652ed9651675ad62791743e432f|`4202011`> Update font-optimization test…
Bumps <https://github.com/vercel/next.js|next> from 9.5.5 to 12.1.0. Release notes _Sourced from <https://github.com/vercel/next.js/releases|next's releases>._ > *v12.1.0* > *Core Changes* > > • Relay Support in Rust Compiler: <https://github-redirect.dependabot.com/vercel/next.js/issues/33702|#33702> > • fix eslint link-passhref rule: <https://github-redirect.dependabot.com/vercel/next.js/issues/33857|#33857> > • update webpack: <https://github-redirect.dependabot.com/vercel/next.js/issues/33831|#33831> > • Flush buffered vitals metrics on page mount: <https://github-redirect.dependabot.com/vercel/next.js/issues/33867|#33867> > • fix problem with HMR when middleware and page reference the same node_module: <https://github-redirect.dependabot.com/vercel/next.js/issues/33873|#33873> > • Refactor page component getter in web server: <https://github-redirect.dependabot.com/vercel/next.js/issues/33759|#33759> > • update NextResponse default redirect status to 307 to match docs: <https://github-redirect.dependabot.com/vercel/next.js/issues/33505|#33505> > • Bug fix: dynamic page should not be interpreted as predefined page: <https://github-redirect.dependabot.com/vercel/next.js/issues/33808|#33808> > • Group streaming experimental apis: <https://github-redirect.dependabot.com/vercel/next.js/issues/33878|#33878> > • Encapsulate routing and initial hydration: <https://github-redirect.dependabot.com/vercel/next.js/issues/33875|#33875> > • Optimize offline condition judgment: <https://github-redirect.dependabot.com/vercel/next.js/issues/33238|#33238> > • Ensure external beforeFiles rewrites are handled with next/link: <https://github-redirect.dependabot.com/vercel/next.js/issues/33888|#33888> > • Fix parsing params for i18n optional route in minimal mode: <https://github-redirect.dependabot.com/vercel/next.js/issues/33896|#33896> > • Ensure browserslist extends works properly: <https://github-redirect.dependabot.com/vercel/next.js/issues/33890|#33890> > • Fix image cache race condition: <https://github-redirect.dependabot.com/vercel/next.js/issues/33883|#33883> > • Add support for Relay projects without `artifactDirectory`: <https://github-redirect.dependabot.com/vercel/next.js/issues/33918|#33918> > • fix: handle jsxspreadattribute in inline-script-id eslint rule: <https://github-redirect.dependabot.com/vercel/next.js/issues/32421|#32421> > • feat(next-swc): Update swc: <https://github-redirect.dependabot.com/vercel/next.js/issues/33724|#33724> > • Update to latest version of amphtml-validator: <https://github-redirect.dependabot.com/vercel/next.js/issues/33967|#33967> > • Warn in dev mode when script tags are added with next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/33968|#33968> > • Ensure optional chaining in swc matches babel: <https://github-redirect.dependabot.com/vercel/next.js/issues/33995|#33995> > • Use `react-dom/server.browser` in Node.js: <https://github-redirect.dependabot.com/vercel/next.js/issues/33950|#33950> > • Ensure external middleware rewrite is handled correctly: <https://github-redirect.dependabot.com/vercel/next.js/issues/33962|#33962> > • Update Terser to v5.10.0, fix minification issues: <https://github-redirect.dependabot.com/vercel/next.js/issues/33045|#33045> > • Warn in dev mode when stylesheets are added using next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/34004|#34004> > • Use `ReadableStream` in `RenderResult`: <https://github-redirect.dependabot.com/vercel/next.js/issues/34005|#34005> > • Fix suffix ordering while streaming: <https://github-redirect.dependabot.com/vercel/next.js/issues/34011|#34011> > • Don't use yarn if a package-lock.json file is found: <https://github-redirect.dependabot.com/vercel/next.js/issues/31926|#31926> > • Do not warn when application/ld+json scripts are used with next/head: <https://github-redirect.dependabot.com/vercel/next.js/issues/34021|#34021> > • Babel & next-swc: Fix exporting page config with AsExpression: <https://github-redirect.dependabot.com/vercel/next.js/issues/32702|#32702> > • Detect per page runtime config for functions manifest: <https://github-redirect.dependabot.com/vercel/next.js/issues/33945|#33945> > • Add JSDoc to config options: <https://github-redirect.dependabot.com/vercel/next.js/issues/32915|#32915> > • Update font-stylesheet-gathering-plugin.ts: <https://github-redirect.dependabot.com/vercel/next.js/issues/30709|#30709> > • Add decoratorMetadata flag if enabled by tsconfig: <https://github-redirect.dependabot.com/vercel/next.js/issues/32914|#32914> > • fix: data url handling in css-loader: <https://github-redirect.dependabot.com/vercel/next.js/issues/34034|#34034> > • Place 'charset' element at the top of : <https://github-redirect.dependabot.com/vercel/next.js/issues/28119|#28119> > • Fix detection of anchor click events inside svg: <https://github-redirect.dependabot.com/vercel/next.js/issues/23272|#23272> > • Allow passing nothing as custom jest config: <https://github-redirect.dependabot.com/vercel/next.js/issues/32328|#32328> > • Fixes <https://github-redirect.dependabot.com/vercel/next.js/issues/31240|#31240>: Adding a recursive addPackagePath function in webpack-config: <https://github-redirect.dependabot.com/vercel/next.js/issues/31264|#31264> > • Require component rendered as child of `Link` to pass event to `onClick` handler: <https://github-redirect.dependabot.com/vercel/next.js/issues/27723|#27723> > • Allow scroll prevention on hash change: <https://github-redirect.dependabot.com/vercel/next.js/issues/31921|#31921> > • Add support for async fn / promise in next.config.js/.mjs: <https://github-redirect.dependabot.com/vercel/next.js/issues/33662|#33662> > • Fix `lazyRoot` functionality for `next/image`: <https://github-redirect.dependabot.com/vercel/next.js/issues/33933|#33933> > • Change SWC minify from beta to release candidate: <https://github-redirect.dependabot.com/vercel/next.js/issues/34056|#34056> > • Make `Router` state immutable: <https://github-redirect.dependabot.com/vercel/next.js/issues/33925|#33925> > • Stop exposing internal `render` and `renderError` methods from `next/client`: <https://github-redirect.dependabot.com/vercel/next.js/issues/34069|#34069> > • Add api-utils helper for testing: <https://github-redirect.dependabot.com/vercel/next.js/issues/34078|#34078> ... (truncated) Commits • <https://github.com/vercel/next.js/commit/8545fd1bb02244ced9e8dc9584a764aeae296cd0|`8545fd1`> v12.1.0 • <https://github.com/vercel/next.js/commit/1605f3059c7773a346998da5e1de416d106d8f32|`1605f30`> v12.0.11-canary.21 • <https://github.com/vercel/next.js/commit/69aedbd6667753f02b76563598342c8afa646dfa|`69aedbd`> Fix typo (<https://github-redirect.dependabot.com/vercel/next.js/issues/34480|#34480>) • <https://github.com/vercel/next.js/commit/f0f322c0d1655d722d133f963a84e575a61a5708|`f0f322c`> Remove deprecation for relative URL usage in middlewares (<https://github-redirect.dependabot.com/vercel/next.js/issues/34461|#34461>) • <https://github.com/vercel/next.js/commit/d4d79b2d9b9c43ed1061a3d3beeb3099368669a8|`d4d79b2`> Fix chunk buffering for server components (<https://github-redirect.dependabot.com/vercel/next.js/issues/34474|#34474>) • <https://github.com/vercel/next.js/commit/74fa4d4b93673a355d082473318562056571900f|`74fa4d4`> update webpack (<https://github-redirect.dependabot.com/vercel/next.js/issues/34477|#34477>) • <https://github.com/vercel/next.js/commit/b70397e770a0badfbafe9e2db8cb8bfeb1b06f9e|`b70397e`> Revert "Allow reading request bodies in middlewares (<https://github-redirect.dependabot.com/vercel/next.js/issues/34294|#34294>)" (<https://github-redirect.dependabot.com/vercel/next.js/issues/34479|#34479>) • <https://github.com/vercel/next.js/commit/42020114d2ada652ed9651675ad62791743e432f|`4202011`> Update font-optimization test…
Make site able to show image and reply *Snapshots* <https://user-images.githubusercontent.com/6376572/168525843-e964eb7d-2362-4b6e-a705-7f57e3d889ff.png|Screen Shot 2022-05-16 at 13 25 27> <https://user-images.githubusercontent.com/6376572/168525820-f346beb4-9628-4ff2-beab-0c2ed946eb4e.png|Screen Shot 2022-05-16 at 13 25 01> <https://user-images.githubusercontent.com/6376572/168525848-ac850614-d021-4320-890a-c9cc5ae3331b.png|Screen Shot 2022-05-16 at 13 26 03> <https://user-images.githubusercontent.com/6376572/168525853-7e2a6c56-3e44-4fbe-810f-d9bc903d8e64.png|Screen Shot 2022-05-16 at 13 26 44>
Fix <https://github.com/cofacts/rumors-site/issues/483|#483> ☑︎ Messages (Article List) ☑︎ Replies (Reply List) ☑︎ For you ☑︎ Search reply *Snapshots* <https://user-images.githubusercontent.com/6376572/168525843-e964eb7d-2362-4b6e-a705-7f57e3d889ff.png|Screen Shot 2022-05-16 at 13 25 27> <https://user-images.githubusercontent.com/6376572/168525820-f346beb4-9628-4ff2-beab-0c2ed946eb4e.png|Screen Shot 2022-05-16 at 13 25 01> <https://user-images.githubusercontent.com/6376572/168525848-ac850614-d021-4320-890a-c9cc5ae3331b.png|Screen Shot 2022-05-16 at 13 26 03> <https://user-images.githubusercontent.com/6376572/168525853-7e2a6c56-3e44-4fbe-810f-d9bc903d8e64.png|Screen Shot 2022-05-16 at 13 26 44>
<https://coveralls.io/builds/49136096|Coverage Status> Coverage increased (+0.03%) to 75.561% when pulling *<https://github.com/cofacts/rumors-site/commit/cc1906d7fef739321619d4e2674e76ee41ddc8eb|cc1906d> on feature/media-article* into *<https://github.com/cofacts/rumors-site/commit/47818e16ab7e415887829dc1a981d405a38ce120|47818e1> on master*.
<https://coveralls.io/builds/49136096|Coverage Status> Coverage increased (+0.03%) to 75.561% when pulling *<https://github.com/cofacts/rumors-site/commit/cc1906d7fef739321619d4e2674e76ee41ddc8eb|cc1906d> on feature/media-article* into *<https://github.com/cofacts/rumors-site/commit/47818e16ab7e415887829dc1a981d405a38ce120|47818e1> on master*.
這次被檢舉的兩位都在 10 多分鐘內貼了 40 多篇
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
這次被檢舉的兩位都在 10 多分鐘內貼了 40 多篇
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
Replied to a thread: 2022-05-16 21:47:42
這次被檢舉的兩位都在 10 多分鐘內貼了 40 多篇
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
我看了一下 `replyrequest` 的 `appId` ，是正常的 `WEBSITE` （代表有用 cookie 登入）
我猜是寫了 sikuli 或 selenium 這類的 e2e script 做的
- 😮1
新被回報的另外兩位我就不 code review 囉
明顯一樣是二次詐騙
明顯一樣是二次詐騙
另外兩位我就不 code review 囉
明顯一樣是二次詐騙
明顯一樣是二次詐騙
奇怪，最近這種協同突然變多？
https://cofacts.g0v.tw/article/s8n7zllc0py1
https://cofacts.g0v.tw/article/s8n7zllc0py1
感謝回報
這四個 upvote 的帳號都是 Google 登入
也都是 5/6 上午註冊
只有按這篇讚，沒其他活動
也都是 5/6 上午註冊
只有按這篇讚，沒其他活動
現在查 IP 好麻煩，之後想辦法簡化好了 QQ
查完了
回應者與按讚者 5 人的 IP 均不同
看起來比較像是呼朋引伴
回應者與按讚者 5 人的 IP 均不同
看起來比較像是呼朋引伴
分類修好了欸
- 👍1
修好的是否決分類那個
分類修好了欸
修好的是否決分類那個
感謝回報
這四個 upvote 的帳號都是 Google 登入
也都是 5/6 上午註冊
只有按這篇讚，沒其他活動
也都是 5/6 上午註冊
只有按這篇讚，沒其他活動
現在查 IP 好麻煩，之後想辦法簡化好了 QQ
查完了
回應者與按讚者 5 人的 IP 均不同
看起來比較像是呼朋引伴
回應者與按讚者 5 人的 IP 均不同
看起來比較像是呼朋引伴
2022-05-17
I think instead of changing individual requests, we can • use env variable in `rumors-api` to determine if APIs should return all `articleTypes` • staging API shows all `articleTypes`; production API only returns `TEXT` by default before we finish implementation • `rumors-site` does not specify `articleTypes`
I think instead of changing individual requests, we can • use env variable in `rumors-api` to determine if APIs should return all `articleTypes` • staging API shows all `articleTypes`; production API only returns `TEXT` by default before we finish implementation • `rumors-site` does not specify `articleTypes`
Thanks for the commit! I have some comments to discuss.
Thanks for the commit! I have some comments to discuss.
Same as above. I think `bannerImage` is a bit too wide (100% width) on desktop. I think we can set `max-width` & `max-height` on them, and use `<a>` to link to the original image instead. Suggested change
Same as above. I think `bannerImage` is a bit too wide (100% width) on desktop. I think we can set `max-width` & `max-height` on them, and use `<a>` to link to the original image instead. Suggested change
nit: since we may add text for images in the future, suggest we do this instead: Suggested change
nit: since we may add text for images in the future, suggest we do this instead: Suggested change
Replied to a thread: 2022-05-16 23:10:44
After adding a category, currently there is no any visual feedback that tells the user that the category is added. <https://user-images.githubusercontent.com/108608/162559676-022d4169-ba14-4525-a804-47b988fd6df0.gif|no-response> Current workaround: refresh the whole page Expected: UI should show that the category is added immediately (or shortly after API response)
修好的是否決分類那個
2022-05-18
Add MEDIA_ARTICLE_SUPPORT env to switch default articleTypes filter as discuss in <https://github.com/cofacts/rumors-site/pull/490|cofacts/rumors-site#490>
Add MEDIA_ARTICLE_SUPPORT env to switch default articleTypes filter as discuss in <https://github.com/cofacts/rumors-site/pull/490|cofacts/rumors-site#490>
<https://coveralls.io/builds/49203638|Coverage Status> Coverage remained the same at 87.473% when pulling *<https://github.com/cofacts/rumors-api/commit/0ca74bd9ededc86fefb7a3bfcec1bc3055c8c797|0ca74bd> on feature/env-media-article-support* into *<https://github.com/cofacts/rumors-api/commit/271bc9b210676f6390d4e03bf5f93165c48f2f05|271bc9b> on master*.
<https://coveralls.io/builds/49203638|Coverage Status> Coverage remained the same at 87.473% when pulling *<https://github.com/cofacts/rumors-api/commit/0ca74bd9ededc86fefb7a3bfcec1bc3055c8c797|0ca74bd> on feature/env-media-article-support* into *<https://github.com/cofacts/rumors-api/commit/271bc9b210676f6390d4e03bf5f93165c48f2f05|271bc9b> on master*.
LGTM, let's ship it <https://github.githubassets.com/images/icons/emoji/shipit.png|:shipit:>
LGTM, let's ship it <https://github.githubassets.com/images/icons/emoji/shipit.png|:shipit:>
Thanks for the timely update! I have deployed the current branch to staging: <https://dev.cofacts.tw/articles|https://dev.cofacts.tw/articles> and have some comments on the current status.
Thanks for the timely update! I have deployed the current branch to staging: <https://dev.cofacts.tw/articles|https://dev.cofacts.tw/articles> and have some comments on the current status. (Staging API also updated to <https://github.com/cofacts/rumors-api/pull/282|cofacts/rumors-api#282> and has `MEDIA_ARTICLE_SUPPORT` toggled on.)
Seems that 800 is a bit too high, vertical images can hit max-height first XD <https://user-images.githubusercontent.com/108608/168965648-bc9041ef-529c-4f9b-a11d-1f71c904094d.png|image> Suggest we `max-width` can be around 400, and we can remove `max-height` so that image height can be completely determined by image's apsect ratio.
Seems that 800 is a bit too high, vertical images can hit max-height first XD <https://user-images.githubusercontent.com/108608/168965648-bc9041ef-529c-4f9b-a11d-1f71c904094d.png|image> Suggest we `max-width` can be around 400, and we can remove `max-height` so that image height can be completely determined by image's apsect ratio.
Suggest that we can put a placeholder image so that the image shows up in Storybook, which helps development & maintenance in the future. Suggested change <https://user-images.githubusercontent.com/108608/168966985-45f1cb4e-c7d6-44ca-9619-8ca8596e1b1f.png|image>
Suggest that we can put a placeholder image so that the image shows up in Storybook, which helps development & maintenance in the future. Suggested change <https://user-images.githubusercontent.com/108608/168966985-45f1cb4e-c7d6-44ca-9619-8ca8596e1b1f.png|image>
Currently opened <https://github.com/cofacts/media-manager|https://github.com/cofacts/media-manager> • main branch: bootstrapped with <https://tsdx.io/|tsdx> • [WIP] MediaManager class implementation <https://github.com/cofacts/media-manager/pull/1/files|https://github.com/cofacts/media-manager/pull/1/files>
Currently opened <https://github.com/cofacts/media-manager|https://github.com/cofacts/media-manager> • main branch: bootstrapped with <https://tsdx.io/|tsdx> • [WIP] MediaManager class implementation <https://github.com/cofacts/media-manager/pull/1/files|https://github.com/cofacts/media-manager/pull/1/files>
HackMD
# Cofacts 會議記錄 ## 2022 - [20220518 會議記錄](/_HXxDu6OQPaK08WFwOshtg) - [20220511 會議記錄](/R_cEiQ8eRDmQ
2022-05-20
2022-05-21
API 疑似卡住，原因不明
server load 沒有很高，一切正常
nginx 針對 api 回傳 504
server load 沒有很高，一切正常
nginx 針對 api 回傳 504
Your site went down! *Code:* 0 - *Reason:* Timeout / Connection Refused
進 api 的 docker image 裡面下
喔好吧外面也是 31
記憶體用完了呢
CPU 先是 User 高一波
後面變成 system + wait
看起來像是進入 memory thrashing
後面變成 system + wait
看起來像是進入 memory thrashing
研究不出所以然
先來 restart elasticsearch
先來 restart elasticsearch
狀況解除
看來是 rumors-site memory leak 老問題
只是剛好遇到一些巧合然後萬劫不復
API 疑似卡住，原因不明
server load 沒有很高，一切正常
nginx 針對 api 回傳 504
server load 沒有很高，一切正常
nginx 針對 api 回傳 504
Your site went down! *Code:* 0 - *Reason:* Timeout / Connection Refused
進 api 的 docker image 裡面下
喔好吧外面也是 31
記憶體用完了呢
CPU 先是 User 高一波
後面變成 system + wait
看起來像是進入 memory thrashing
後面變成 system + wait
看起來像是進入 memory thrashing
研究不出所以然
先來 restart elasticsearch
先來 restart elasticsearch
狀況解除
看來是 rumors-site memory leak 老問題
只是剛好遇到一些巧合然後萬劫不復
進 api 的 docker image 裡面下
喔好吧外面也是 31
記憶體用完了呢
CPU 先是 User 高一波
後面變成 system + wait
看起來像是進入 memory thrashing
後面變成 system + wait
看起來像是進入 memory thrashing
研究不出所以然
先來 restart elasticsearch
先來 restart elasticsearch
狀況解除
看來是 rumors-site memory leak 老問題
只是剛好遇到一些巧合然後萬劫不復
2022-05-22
@johnson9294 has joined the channel
2022-05-23
@physics5372 has joined the channel
Jest 跟我抱怨 node-fetch 語法他看不懂
即使我設定 jest config 開啟 transform，jest 還是沒在動
https://github.com/cofacts/media-manager/runs/6549859066?check_suite_focus=true
不知道 @acerxp511 之前寫 rumors-api 有沒有遇過 QQ
即使我設定 jest config 開啟 transform，jest 還是沒在動
https://github.com/cofacts/media-manager/runs/6549859066?check_suite_focus=true
不知道 @acerxp511 之前寫 rumors-api 有沒有遇過 QQ
Jest 跟我抱怨 node-fetch 語法他看不懂
即使我設定 jest config 開啟 transform，jest 還是沒在動
https://github.com/cofacts/media-manager/runs/6549859066?check_suite_focus=true
不知道 @acerxp511 之前寫 rumors-api 有沒有遇過 QQ
即使我設定 jest config 開啟 transform，jest 還是沒在動
https://github.com/cofacts/media-manager/runs/6549859066?check_suite_focus=true
不知道 @acerxp511 之前寫 rumors-api 有沒有遇過 QQ
因為 node-fetch 改成 es module 了?
因為 node-fetch 改成 es module 了?
對耶 rumors-api 的 node-fetch 是 v2
非常和平
非常和平
對耶 rumors-api 的 node-fetch 是 v2
非常和平
非常和平
不過 media-manager 用的 tsdx
理論上遇到這種檔案應該要用 babel-jest 來 transform
babel 應該要認得才對
我回家弄一下 babel 設定好了
tsdx 的 config 藏在裡面有時候也是滿惱人的哀
理論上遇到這種檔案應該要用 babel-jest 來 transform
babel 應該要認得才對
我回家弄一下 babel 設定好了
tsdx 的 config 藏在裡面有時候也是滿惱人的哀
不過 media-manager 用的 tsdx
理論上遇到這種檔案應該要用 babel-jest 來 transform
babel 應該要認得才對
我回家弄一下 babel 設定好了
tsdx 的 config 藏在裡面有時候也是滿惱人的哀
理論上遇到這種檔案應該要用 babel-jest 來 transform
babel 應該要認得才對
我回家弄一下 babel 設定好了
tsdx 的 config 藏在裡面有時候也是滿惱人的哀
2022-05-24
媒體都沒報導 ❌
媒體都有報導，只是你沒看到 ⭕
媒體都有報導，只是你沒看到 ⭕
1
閉著眼睛的人看不到報導～
媒體都沒報導 ❌
媒體都有報導，只是你沒看到 ⭕
媒體都有報導，只是你沒看到 ⭕
閉著眼睛的人看不到報導～
閉著眼睛的人看不到報導～
2022-05-25
加上之前這個 case
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
1
加上之前這個 case
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
加上之前這個 case
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1652189202958809
似乎除了紀錄檔案之外，
還是要設計之前提到的 article group
請使用者把檔案前後搭配的文字一起轉傳進來讓我們紀錄
為啥最近三篇檢舉都是檢舉那些已經被 block 的人呀
理論上只有被 block 的人看得到這些內容耶
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXkQ0NjkzSXoSPETCFc7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml
理論上只有被 block 的人看得到這些內容耶
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXkQ0NjkzSXoSPETCFc7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml
做壞事良心不安，自己檢舉自己（❌
搶業績吧
為啥最近三篇檢舉都是檢舉那些已經被 block 的人呀
理論上看得到這些內容的人
也是被 block 的人捏
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXkQ0NjkzSXoSPETCFc7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml
理論上看得到這些內容的人
也是被 block 的人捏
https://docs.google.com/spreadsheets/d/e/2PACX-1vRdcwXdC36xfgXfSMSk527Zbel9A-__vwRXkQ0NjkzSXoSPETCFc7sI7SoaAFdPCfskugtQL-Md8JgH/pubhtml
做壞事良心不安，自己檢舉自己（❌
搶業績吧
搶業績吧
被停用的帳號裡有那個國外施暴的謠言影片嗎？
喔喔
裡面沒有影片耶
裡面沒有影片耶
都是圖
被停用的帳號裡有那個國外施暴的謠言影片嗎？
喔喔
裡面沒有影片耶
裡面沒有影片耶
都是圖
Replied to a thread: 2022-05-25 18:52:37
被停用的帳號裡有那個國外施暴的謠言影片嗎？
2022-05-26
喔喔
裡面沒有影片耶
裡面沒有影片耶
都是圖
2022-05-27
Resolved in <https://github.com/cofacts/rumors-site/pull/484|#484>
Resolved in <https://github.com/cofacts/rumors-site/pull/484|#484>
Storybook is <https://dev.cofacts.tw/storybook/index.html|online>, no actions left
Storybook is <https://dev.cofacts.tw/storybook/index.html|online>, no actions left
*As-is* A form with anonymous avatar is shown. However, the user will be asked to login afterwards, and the submitted text will be cleared. <https://user-images.githubusercontent.com/108608/170654279-909a0ea7-2abc-4fe3-b53a-4337daa77961.png|圖片> *To-be* Replace the form to something as simple as a string, like what we did for "write reply" <https://user-images.githubusercontent.com/108608/170654382-6e056b4f-de58-40b1-bdf1-5daba525c757.png|圖片>
*As-is* A form with anonymous avatar is shown. However, the user will be asked to login afterwards, and the submitted text will be cleared. <https://user-images.githubusercontent.com/108608/170654279-909a0ea7-2abc-4fe3-b53a-4337daa77961.png|圖片> *To-be* Replace the form to something as simple as a string, like what we did for "write reply" <https://user-images.githubusercontent.com/108608/170654382-6e056b4f-de58-40b1-bdf1-5daba525c757.png|圖片>
LGTM, let's ship it <https://github.githubassets.com/images/icons/emoji/shipit.png|:shipit:>
LGTM, let's ship it <https://github.githubassets.com/images/icons/emoji/shipit.png|:shipit:>
@acerxp511 關於檔案的 URL 呀，我在想或許 elasticsearch 的 articles index 裡面只要記 file ID 就好，需要 URL 的時候再去呼叫 `mediaManager.getInfo()` 來拿 URL，不要存一個永久的 public URL。
主要有兩個 concern
1. 我們未來可能會修改檔案存法，會改到 URL — 我在想未來可能要針對圖片增加縮圖、影片製作縮圖等等，所以現在設計的檔名可能會換，但 file ID 不變
2. 我不希望 URL 被存在其他第三方，讓大家無限期存取，但流量都算在我們頭上。如果是要用的時候才產生 URL，我們可以把檔案通通設成 private，然後給 signed URL 出去，該 URL 5 分鐘後就過期之類的。
主要有兩個 concern
1. 我們未來可能會修改檔案存法，會改到 URL — 我在想未來可能要針對圖片增加縮圖、影片製作縮圖等等，所以現在設計的檔名可能會換，但 file ID 不變
2. 我不希望 URL 被存在其他第三方，讓大家無限期存取，但流量都算在我們頭上。如果是要用的時候才產生 URL，我們可以把檔案通通設成 private，然後給 signed URL 出去，該 URL 5 分鐘後就過期之類的。
@acerxp511 關於檔案的 URL 呀，我在想或許 elasticsearch 的 articles index 裡面只要記 file ID 就好，需要 URL 的時候再去呼叫 `mediaManager.getInfo()` 來拿 URL，不要存一個永久的 public URL。
主要有兩個 concern
1. 我們未來可能會修改檔案存法，會改到 URL — 我在想未來可能要針對圖片增加縮圖、影片製作縮圖等等，所以現在設計的檔名可能會換，但 file ID 不變
2. 我不希望 URL 被存在其他第三方，讓大家無限期存取，但流量都算在我們頭上。如果是要用的時候才產生 URL，我們可以把檔案通通設成 private，然後給 signed URL 出去，該 URL 5 分鐘後就過期之類的。
主要有兩個 concern
1. 我們未來可能會修改檔案存法，會改到 URL — 我在想未來可能要針對圖片增加縮圖、影片製作縮圖等等，所以現在設計的檔名可能會換，但 file ID 不變
2. 我不希望 URL 被存在其他第三方，讓大家無限期存取，但流量都算在我們頭上。如果是要用的時候才產生 URL，我們可以把檔案通通設成 private，然後給 signed URL 出去，該 URL 5 分鐘後就過期之類的。
Google Cloud 
- 🤔1
- 1
2022-05-29
• Fixes <https://github.com/cofacts/rumors-db/issues/57|#57> • Fixes <https://github.com/cofacts/rumors-db/issues/58|#58> • Add automated test on the validity of the schema
• Fixes <https://github.com/cofacts/rumors-db/issues/57|#57> • Fixes <https://github.com/cofacts/rumors-db/issues/58|#58> • Add automated test on the validity of the schema
2022-05-30
@a.herait has joined the channel
@yachu.chung has joined the channel
2022-05-31
- 😆3