#cofacts
2021-04-02
Replied to a thread: 2021-03-31 22:49:52
時辰已到
開始維護
開始維護
@terry.f.wang has left the channel
維護完成囉
2021-04-03
之前的編輯小聚，有參與者想要看到自己按讚的成果
我想把 profile page「評價過的回應」做成像這樣，大家有沒有什麼想法呢～？
https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?node-id=2923%3A220
cc/ @stbb1025 @lucien
我想把 profile page「評價過的回應」做成像這樣，大家有沒有什麼想法呢～？
https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?node-id=2923%3A220
cc/ @stbb1025 @lucien
@adachang123 has left the channel
Currently slugs with characters will trigger infinite page reload. This PR modifies the reload detection mechanism so that it handles URL encoded paths correctly.
This PR fixes <https://github.com/cofacts/rumors-api/issues/242|#242> . The definition of "invalid slug": matches any of the following • empty, or contains just space • has trailing or leading space • contains URL components like `:` or `/` • is already taken by another user This PR • adds a query API `ValidateSlug` for UI to check if a slug is valid • blocks invalid slug in `UpdateUser`
<https://coveralls.io/builds/38509947|Coverage Status> Coverage increased (+0.06%) to 86.406% when pulling *<https://github.com/cofacts/rumors-api/commit/81d5065a1755983413246effe9e3c9367696bf13|81d5065> on validate-slug* into *<https://github.com/cofacts/rumors-api/commit/0c42992c82eb25851433f3f275b663eef84defab|0c42992> on master*.
<https://coveralls.io/builds/38510041|Coverage Status> Coverage decreased (-0.1%) to 86.207% when pulling *<https://github.com/cofacts/rumors-api/commit/1c61b1095b1f6f407f21f3e3d0899dd81fdf1adc|1c61b10> on update-schema* into *<https://github.com/cofacts/rumors-api/commit/0c42992c82eb25851433f3f275b663eef84defab|0c42992> on master*.
2021-04-04
Signin with Apple Need $$$ <https://developer.apple.com/account/resources/|https://developer.apple.com/account/resources/> <https://user-images.githubusercontent.com/6376572/113502281-f03da100-955d-11eb-8872-1b8c94c7bc69.png|截圖 2021-04-04 下午3 53 04>
Fixes <https://github.com/cofacts/rumors-api/issues/234|#234> *<https://developers.google.com/identity/sign-in/web/sign-in|Google sign-in>* Use <https://github.com/jaredhanson/passport-google-oauth2|passport-google-oauth2> *To get google OAuth credential* 1. <https://console.cloud.google.com/apis/credentials|Create> OAuth Client ID credential 2. Edit `Web client` and add `PUBLIC_URL/callback/google` to `Authorized redirect URIs` 3. Paste `Client ID` and `Client secret` to env *<https://developers.facebook.com/docs/instagram-basic-display-api/getting-started/|Instagram sign-in>* Use <https://github.com/huynhsang/passport-instagram-graph|passport-instagram-graph>. (<https://github.com/jaredhanson/passport-instagram/pull/26|passport-instagram> is out-of-date.) *To get Instagram OAuth credential* 1. <https://developers.facebook.com/apps/|Create> Facebook login application 2. Setup Instagram Basic Display 3. Add `PUBLIC_URL/callback/instagram` to `Valid OAuth Redirect URIs` 4. Paste `Client ID` and `Client secret` to env Tester should approve invitation <https://www.instagram.com/accounts/manage_access/|here>. Should submit your app for App Review when you are ready to switch it to Live Mode.
<https://coveralls.io/builds/38515751|Coverage Status> Coverage decreased (-0.5%) to 85.81% when pulling *<https://github.com/cofacts/rumors-api/commit/306587127848aa408c206ada130872b3b661fe3e|3065871> on new-login-methods* into *<https://github.com/cofacts/rumors-api/commit/0c42992c82eb25851433f3f275b663eef84defab|0c42992> on master*.
Thanks for adding Google & IG!
Thanks for supporting new signin methods! The setup instructions are super clear. I have also reloaded `users` index to `v1.2.0` on staging. I am concerned that when creating "Basic Display" IG API, Facebook says that my app review will be rejected if we use it to authenticate user. <https://user-images.githubusercontent.com/108608/113511479-91464f00-9592-11eb-8e0b-7ebe54170454.png|image> Can IG users login directly using FB?
> Can IG users login directly using FB? Maybe no. They always ask user to link IG and FB account together. I think if a IG user doesn't link FB, (s)he can't use Facebook login. > Facebook says that my app review will be rejected if we use it to authenticate user. Then we should add share (article/reply) to Instagram function to pass the review :p
2021-04-05
doc: <https://github.com/jaredhanson/passport-facebook/pull/234#issuecomment-456553856|jaredhanson/passport-facebook#234 (comment)> <https://user-images.githubusercontent.com/108608/113590908-d7201780-9665-11eb-85e0-77eb69ecd01a.png|image>
<https://coveralls.io/builds/38534990|Coverage Status> Coverage remained the same at 86.131% when pulling *<https://github.com/cofacts/rumors-api/commit/befb928e82d1e8a47572e7885fc70874a52e29ca|befb928> on upgrade-graph-api* into *<https://github.com/cofacts/rumors-api/commit/57958a2c1553fe250a8ab007987c1141affd49c4|57958a2> on master*.
2021-04-06
Deployed to staging. <https://dev-api.cofacts.org/callback/google|https://dev-api.cofacts.org/callback/google> should work.
2021-04-07
As <https://github.com/cofacts/rumors-db/pull/53|cofacts/rumors-db#53> merges, this should be fixed. Close for now.
今日會議紀錄
會盤點春假開發的東西
以及跑過上次檢討的新小聚 rundown
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FlYRkMMQNTqewpjDjpeqTiQ
會盤點春假開發的東西
以及跑過上次檢討的新小聚 rundown
https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2FlYRkMMQNTqewpjDjpeqTiQ
@acerxp511 今晚會測 google 登入嗎
可以啊，我有先“隨便”加了兩個測試登入按鈕在 site
可以今天測完再看要怎麼改
https://github.com/cofacts/rumors-site/tree/new-signin-methods
可以今天測完再看要怎麼改
https://github.com/cofacts/rumors-site/tree/new-signin-methods
@acerxp511 今晚會測 google 登入嗎
Show snack when edit profile dialog errors. <https://user-images.githubusercontent.com/108608/113817930-a77a2800-97a9-11eb-8a7a-20387cd61166.png|image>
這個小變更是單純顯示 `UpdateUser` 的 error message
希望晚上可以測到他，煩請 review
希望晚上可以測到他，煩請 review
Replied to a thread: 2021-04-07 14:01:17
這個小變更是單純顯示 `UpdateUser` 的 error message
希望晚上可以測到他，煩請 review
希望晚上可以測到他，煩請 review
Replied to a thread: 2021-04-07 13:34:52
可以啊，我有先“隨便”加了兩個測試登入按鈕在 site
可以今天測完再看要怎麼改
https://github.com/cofacts/rumors-site/tree/new-signin-methods
可以今天測完再看要怎麼改
https://github.com/cofacts/rumors-site/tree/new-signin-methods
Support Google sign-in. (IG temporarily hidden as it requires app review) <https://user-images.githubusercontent.com/108608/113865973-54bb6300-97df-11eb-82e2-67d2476a7399.png|image>
<https://coveralls.io/builds/38601875|Coverage Status> Coverage decreased (-0.05%) to 86.044% when pulling *<https://github.com/cofacts/rumors-api/commit/fbfd136b5a8c210832649c5045eae593eb76568a|fbfd136> on new-login-methods* into *<https://github.com/cofacts/rumors-api/commit/7e05f572452c9d00ce1df5ebcb78f28c972dadc1|7e05f57> on master*.
Fixed in <https://github.com/cofacts/rumors-site/pull/415|#415>, closing
Fixed in <https://github.com/cofacts/rumors-db/pull/53|cofacts/rumors-db#53>, closing.
Seems fixed, kudos to <https://github.com/playpool513|@playpool513> !
Fixed in <https://github.com/cofacts/rumors-site/pull/383|#383>, kudos to <https://github.com/ulayab|@ulayab> !
Closing this as it is fixed by <https://github.com/cofacts/rumors-site/pull/357|#357>
Personally I am having no issue using editor form on my Pixel 2 ever since <https://github.com/cofacts/rumors-site/pull/344|#344> is merged. Closing.
2021-04-08
We should show author of reply requests, as depicted in ffigma.
cofacts.tw
感謝 @acerxp511 ，Google 登入目前上 production 囉！
如果 Google 登入的 email 與之前登入 Cofacts 用的 email 一致，帳號會自動連在一起。
感謝 @acerxp511 ，Google 登入目前上 production 囉！
如果 Google 登入的 email 與之前登入 Cofacts 用的 email 一致，帳號會自動連在一起。
- ❤️3
- 🎉3
@zhangc546 has joined the channel
2021-04-09
@circles0309 has joined the channel
2021-04-10
@hangie921 has joined the channel
Hi 大給厚
- 👋3
@wowdy has joined the channel
Yooo we're having a potluck next Saturday at 5pm in Xinyi. If you're interested, react and I'll send you a fb invite or the address or something
- 🦒1
1
2021-04-11
iOS safari 14 works fine. However in v13: <https://user-images.githubusercontent.com/108608/114293260-3bf4cb00-9ac7-11eb-98f7-56ad82d16e5b.png|image> <https://user-images.githubusercontent.com/108608/114293288-79595880-9ac7-11eb-83b2-9344e4d26b17.png|image> *Solutions* <https://formatjs.io/docs/polyfills/intl-relativetimeformat/|https://formatjs.io/docs/polyfills/intl-relativetimeformat/> or other polyfill
2021-04-12
嗨嗨，想請專案坑主或長期參與者回答對於【坑主工作坊】的參與意願：
1️⃣ 有意願參與，4/15 前有時間填寫引導師訪問卷
2️⃣ 有意願參與，可以約時間與引導師線上訪談
3️⃣ 因為種種因素，可能無法參與
再麻煩大家幫我按 Emoji 回覆一下，感謝~~
--
【坑主工作坊】活動共筆：https://g0v.hackmd.io/@jothon/BJM33QfMd
訪談卷：https://docs.google.com/document/d/1lTWrkOuat9s6RRYJNIrhDFKveQ1zDv31rsf7VN-lSNI/edit?usp=sharing
1️⃣ 有意願參與，4/15 前有時間填寫引導師訪問卷
2️⃣ 有意願參與，可以約時間與引導師線上訪談
3️⃣ 因為種種因素，可能無法參與
再麻煩大家幫我按 Emoji 回覆一下，感謝~~
--
【坑主工作坊】活動共筆：https://g0v.hackmd.io/@jothon/BJM33QfMd
訪談卷：https://docs.google.com/document/d/1lTWrkOuat9s6RRYJNIrhDFKveQ1zDv31rsf7VN-lSNI/edit?usp=sharing
HackMD
# 跳起來！g0v 坑主工作坊 簡介 在 2020/02/02 g0v 揪松團邀請 g0v 社群比較長期的專案坑主，一起來分享討論，彼此專案遇到的問題，以及是否有哪些解法。而今年，我們將再次舉辦坑
Google's requirement: <https://developers.google.com/identity/branding-guidelines|https://developers.google.com/identity/branding-guidelines> Figma TBD
2021-04-13
@carmenkuo0628 has joined the channel
舉手發問。🙋🏻
請問「真的假的 Line Bot」
在Line上線，提供加入Line的人使用， 是幾年幾月開始的呢？
請問「真的假的 Line Bot」
在Line上線，提供加入Line的人使用， 是幾年幾月開始的呢？
我看了一下 statistics
應該是 2016 年 12 月
應該是 2016 年 12 月
🙇♀️🏻謝謝！
2016/10 有個 proof of concept 但後來我停用那個帳號了
程式大改
程式大改
2016 年 12 月版本的 chatbot 應該是 airtable 協作版
*As-is* Currently if the user does not provide slug when editing profile (for example, just changing display names), the operation will be rejected. *To-be* Change `UpdateUser` • When slug is exactly an empty string, clear the slug (For edit name dialog) • When slug argument is not provided at all, leave it as-is. (For avatar dialog)
2021-04-15
打開會有 0.5 秒是正常的然後就跳轉這個畫面了。使用會場 wifi 跟我自己的手機網路都無法打開網頁 QA
Zenfone4 ze551 chrome
@chiehg0v 感謝感謝
請問瀏覽 <chrome://version> 的話會看到的 Google Chrome 版本是多少呢
請問瀏覽 <chrome://version> 的話會看到的 Google Chrome 版本是多少呢
Google Chrome 70.0.3538.110 (正式版本) (32 位元)
感謝感謝
browserstack 的 Google Chrome 都升級到最新的 Chrome 88 了，難怪無法 reproduce QQ
browserstack 的 Google Chrome 都升級到最新的 Chrome 88 了，難怪無法 reproduce QQ
感謝提供版本，目前更新了這張票的敘述以及 browser compatibility 資料
https://github.com/cofacts/rumors-site/issues/426
我下午應該會想辦法處理 `Intl.RelativeTimeFormat` 不存在的問題，不過 `Intl.DateTimeFormat` 看起來可以放心用。
https://github.com/cofacts/rumors-site/issues/426
我下午應該會想辦法處理 `Intl.RelativeTimeFormat` 不存在的問題，不過 `Intl.DateTimeFormat` 看起來可以放心用。
好的好的！感謝 orz
Android 8.0
@mrorz 請幫幫他
打開會有 0.5 秒是正常的然後就跳轉這個畫面了。使用會場 wifi 跟我自己的手機網路都無法打開網頁 QA
Zenfone4 ze551 chrome
@chiehg0v 感謝感謝
請問瀏覽 <chrome://version> 的話會看到的 Google Chrome 版本是多少呢
請問瀏覽 <chrome://version> 的話會看到的 Google Chrome 版本是多少呢
Google Chrome 70.0.3538.110 (正式版本) (32 位元)
感謝感謝
browserstack 的 Google Chrome 都升級到最新的 Chrome 88 了，難怪無法 reproduce QQ
browserstack 的 Google Chrome 都升級到最新的 Chrome 88 了，難怪無法 reproduce QQ
Replied to a thread: 2021-04-15 08:54:49
感謝提供版本，目前更新了這張票的敘述以及 browser compatibility 資料
https://github.com/cofacts/rumors-site/issues/426
我下午應該會想辦法處理 `Intl.RelativeTimeFormat` 不存在的問題，不過 `Intl.DateTimeFormat` 看起來可以放心用。
https://github.com/cofacts/rumors-site/issues/426
我下午應該會想辦法處理 `Intl.RelativeTimeFormat` 不存在的問題，不過 `Intl.DateTimeFormat` 看起來可以放心用。
iOS safari 14 works fine. However in v13: <https://user-images.githubusercontent.com/108608/114293260-3bf4cb00-9ac7-11eb-98f7-56ad82d16e5b.png|image> <https://user-images.githubusercontent.com/108608/114293288-79595880-9ac7-11eb-83b2-9344e4d26b17.png|image> Also for Chrome < 70: <https://user-images.githubusercontent.com/108608/114813175-21329700-9de4-11eb-9bcd-336f7bbb06e4.png|image> *Analysis* <https://docs.google.com/spreadsheets/d/121Jql1JIF-fC8-uIgcLlK-PyofC2GMnqu6W1EO_dJ0o/edit|Cofacts browser statistics (Cofacts chatbot LIFF stats, conducted in April 2020)> *<https://caniuse.com/?search=Intl.RelativeTimeFormat|`Intl.RelativeTimeFormat`>* <https://user-images.githubusercontent.com/108608/114813682-30feab00-9de5-11eb-9755-f30f9a7db375.png|image> Supporting Chrome >= 71 only covers 90% of Android user session; and iOS does not have v14 in 2020 (when this analysis is conducted). Therefore, we should handle the case when `Intl.RelativeTimeFormat` is not supported. *<https://caniuse.com/?search=Intl.DateTimeFormat|`Intl.DateTimeFormat`>* <https://user-images.githubusercontent.com/108608/114813608-14627300-9de5-11eb-8d51-db5c3413d116.png|image> In Cofacts, 100% of android sessions and 99% iOS sessions have `Intl.DateTimeFormat`. We can safely assume `Intl.DateTimeFormat` always exists. *Solutions* Choose one from the following: 1. <https://formatjs.io/docs/polyfills/intl-relativetimeformat/|https://formatjs.io/docs/polyfills/intl-relativetimeformat/> 2. Change back to date-fns 3. other polyfill
好的好的！感謝 orz
⚠️ *Action required - upgrade app for g0v* ⚠️
Fixes <https://github.com/cofacts/rumors-site/issues/426|#426> *Chrome 70* <https://user-images.githubusercontent.com/108608/114820470-9c4e7a00-9df1-11eb-9ef8-9a6e4db80575.png|image> *Safari 13* <https://user-images.githubusercontent.com/108608/114820686-f8190300-9df1-11eb-9931-0a96f5e3e220.png|image>
dev.cofacts.tw 
可以！！！
讚讚 感謝感謝
> For example, to attract and retain new contributors, who might become the future workforce, projects could invest in promoting career, fun, kinship, and learning, which are particularly relevant for young contributors.
> Because over time altruism becomes more important to contributors, FOSS projects aiming to retain experienced contributors, who tend to be core members or maintainers, could invest in strategies and tools showing how their work benefits the community and society (altruism) and improve social interactions.
from: https://opensource.com/article/21/4/motivates-open-source-contributors
> Because over time altruism becomes more important to contributors, FOSS projects aiming to retain experienced contributors, who tend to be core members or maintainers, could invest in strategies and tools showing how their work benefits the community and society (altruism) and improve social interactions.
from: https://opensource.com/article/21/4/motivates-open-source-contributors
Opensource.com
The reasons people contribute to free and open source (FOSS) projects has been a topic of much interest. However, the research on this topic dates back 10 or more years, and much has changed in the world since then. This article shares seven insights from a recent research study that revisited old motivation studies and asked open source contributors what motivates them today.
Hi all `rumors-site` developers,
按照 4/7 會議討論的提案 https://g0v.hackmd.io/lYRkMMQNTqewpjDjpeqTiQ#Thought-on-branching
我要把 `rumors-site` 的 default branch 改回 `master` 並且移除 `dev` branch 囉
我們在採用 master/dev branch 的時候，還沒有 release tag，但現在我們每個 release 都有 tag 了。
再者，master 其實一直以來都只是 fast-forward 到 dev 所在的地方，然後又要等 docker build 同一個 commit hash 的東西。
最後，如果真的有 staging / production 不同的狀況，那麼也可以在 localhost checkout 特定 commit 來 build + push image。
按照 4/7 會議討論的提案 https://g0v.hackmd.io/lYRkMMQNTqewpjDjpeqTiQ#Thought-on-branching
我要把 `rumors-site` 的 default branch 改回 `master` 並且移除 `dev` branch 囉
我們在採用 master/dev branch 的時候，還沒有 release tag，但現在我們每個 release 都有 tag 了。
再者，master 其實一直以來都只是 fast-forward 到 dev 所在的地方，然後又要等 docker build 同一個 commit hash 的東西。
最後，如果真的有 staging / production 不同的狀況，那麼也可以在 localhost checkout 特定 commit 來 build + push image。
2021-04-17
@acerxp511 之前在開發 LIFF 的時候
是不是有遇到 LIFF ID token 過期的問題呀
要手動登出再登入，不然會一直拿到過期的 token QQ
是不是有遇到 LIFF ID token 過期的問題呀
要手動登出再登入，不然會一直拿到過期的 token QQ
好像沒有
印象中你好像有接一個 `liff.logout` 是用來解什麼問題的
但也可能是我記錯 >“<
但也可能是我記錯 >“<
好像沒有
印象中你好像有接一個 `liff.logout` 是用來解什麼問題的
但也可能是我記錯 >“<
但也可能是我記錯 >“<
2021-04-18
⚠️ *Action required - upgrade app for g0v* ⚠️
TODOs ☐ Cross resolve article ☐ Change codegen directory to somewhere outside `src` so that it works after build
*Pull Request Test Coverage Report for <https://coveralls.io/builds/38905924|Build 1302>* • *9* of *10* *(90.0%)* changed or added relevant lines in *4* files are covered. • No unchanged relevant lines lost coverage. • Overall coverage decreased (*-0.1%*) to *86.712%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
2021-04-19
⚠️ *Action required - upgrade app for g0v* ⚠️
Bumps <https://github.com/npm/ssri|ssri> from 6.0.1 to 6.0.2. Changelog _Sourced from <https://github.com/npm/ssri/blob/v6.0.2/CHANGELOG.md|ssri's changelog>._ > *<https://github.com/zkat/ssri/compare/v6.0.1...v6.0.2|6.0.2> (2021-04-07)* > *Bug Fixes* > > • backport regex change from 8.0.1 (<https://github.com/zkat/ssri/commit/b30dfdb|b30dfdb>), closes <https://github-redirect.dependabot.com/zkat/ssri/issues/19|#19> Commits • <https://github.com/npm/ssri/commit/b7c8c7c61db89aeb9fbf7596c0ef17071bc216ef|`b7c8c7c`> chore(release): 6.0.2 • <https://github.com/npm/ssri/commit/b30dfdb00bb94ddc49a25a85a18fb27afafdfbb1|`b30dfdb`> fix: backport regex change from 8.0.1 • See full diff in <https://github.com/npm/ssri/compare/v6.0.1...v6.0.2|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~nlf|nlf>, a new releaser for ssri since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) • `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language • `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language • `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language • `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the <https://github.com/cofacts/rumors-site/network/alerts|Security Alerts page>.
2021-04-21
@eugene2528 has joined the channel
⚠️ *Action required - upgrade app for g0v* ⚠️
這個 PR 是因為我們想在第三方 bot 使用 Cofacts LINE bot LIFF 而生的第一步：LIFF 可以直接透過 Cofacts LINE bot 呼叫到 Cofacts API
這裡用的是 GraphQL schema stitching （感覺比 federation 簡單，而且比較適合 Cofacts LINE bot 與 API 的非對稱結構）
這裡用的是 GraphQL schema stitching （感覺比 federation 簡單，而且比較適合 Cofacts LINE bot 與 API 的非對稱結構）
Replied to a thread: 2021-04-21 14:07:56
這個 PR 是因為我們想在第三方 bot 使用 Cofacts LINE bot LIFF 而生的第一步：LIFF 可以直接透過 Cofacts LINE bot 呼叫到 Cofacts API
這裡用的是 GraphQL schema stitching （感覺比 federation 簡單，而且比較適合 Cofacts LINE bot 與 API 的非對稱結構）
這裡用的是 GraphQL schema stitching （感覺比 federation 簡單，而且比較適合 Cofacts LINE bot 與 API 的非對稱結構）
@et284vu065k3 has joined the channel
We should put donation information on the index, article pages. Reference: <https://donate.wikimedia.org/|https://donate.wikimedia.org/>
We need to show our donation information when users query suspicious messages.
2021-04-22
I think one of the doable item is to add <http://cofacts.tw/impact|Cofacts impact page> at the footer area, which will guide user through a series of information and then goes to donation page. Another thing would be that we can replace or adjust the current footer image so that user can be redirected to either chatbot or donation page.
OCF Lab 開放實驗室
2020 年，Linux 基金會 ＆ 哈佛創新科學實驗室針對自由及開放原始碼軟體 (free and open source software; FOSS) 開發者進行調查，並公布調查結果。
2021-04-23
⚠️ *Action required - upgrade app for g0v* ⚠️
This PR implements an article & reply LIFF (<https://g0v.hackmd.io/0RX4MsjRRJmBqJSKVilWMA#article-amp-reply-LIFF|Previous proposal>) that functionally supports: • Show the article by `articleId` in URL param • If no reply, allow users to submit reply requests • Lists all replies or show only the reply specified by `replyId` in URL param • Upvote & downvote article replies • setup userArticleLink so that users can be notified via Cofacts chatbot when new replies are available • implements `setViewed` mutation in LINE bot GraphQL to support this • sends GA events
*Pull Request Test Coverage Report for <https://coveralls.io/builds/39053067|Build 1311>* • *3* of *3* *(100.0%)* changed or added relevant lines in *1* file are covered. • No unchanged relevant lines lost coverage. • Overall coverage increased (+*0.02%*) to *86.629%* * * * * * * *:yellow_heart: - <https://coveralls.io|Coveralls>*
https://www.figma.com/blog/about-figmas-new-starter-plan/
Figma 免費版規則更新
Team 只能有 3 個檔案、每個檔案 3 頁
但移除了編輯者 2 人的限制
Figma 免費版規則更新
Team 只能有 3 個檔案、每個檔案 3 頁
但移除了編輯者 2 人的限制
Figma 
- 😱2
@john989 has joined the channel
2021-04-24
之前我們討論過 Article LIFF：https://g0v.hackmd.io/0RX4MsjRRJmBqJSKVilWMA#article-amp-reply-LIFF
我排了一下 Article LIFF 的樣子，讓 LINE 使用者可以在 Cofacts chatbot 之外的任何地方都能對 message 下 comment、以及對回應下 feedback。目標是讓所有 LINE 使用者都能使用到 Cofacts chatbot 可以提供的功能，即使他們跟 Cofacts chatbot 之前不一定是好友。
Article LIFF Prototype: https://www.figma.com/proto/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?nod[…]672%2C0.4206191301345825&scaling=scale-down&page-id=3004%3A224
Figma: https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?node-id=3005%3A0
我排了一下 Article LIFF 的樣子，讓 LINE 使用者可以在 Cofacts chatbot 之外的任何地方都能對 message 下 comment、以及對回應下 feedback。目標是讓所有 LINE 使用者都能使用到 Cofacts chatbot 可以提供的功能，即使他們跟 Cofacts chatbot 之前不一定是好友。
Article LIFF Prototype: https://www.figma.com/proto/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?nod[…]672%2C0.4206191301345825&scaling=scale-down&page-id=3004%3A224
Figma: https://www.figma.com/file/DvmAQjMJCncuPORWKnljM1/Cofacts-website-MrOrz-s-copy?node-id=3005%3A0
Design considerations
• 內文字至少 16px，且避免橫向排版，給調大系統字體的使用者預留空間。
◦ LINE 使用者有回報，當網站傳給長輩的時候，長輩看不到。
◦ 其他 Fact checker 網站的內文字體，有些甚至到 18。
• 由於字要大，所以目前的版本把 card 左右與螢幕貼邊，省下橫向空間放更多字。
◦ 目前作法參考 FB mobile app 的外觀。
◦ 不過其實像 snope 網站在 mobile 上其實還是 card view 的樣子，所以如果有需要，還是可以試排一個更接近目前網站外觀的 card view。
• 資訊架構，按照 LINE 使用者需求來重構：
◦ 網站同時要滿足 fact checker 需求與查謠言的人的需求，而且有較大揮灑空間，所以資訊呈現上可以較豐富；但 LINE 使用者在認知能力上可能較為受限、更容易被其他東西 distract，所以設計上會拿掉網站有呈現的一些資料。
◦ 使用情境是，使用者看到一個謠言回應之後，下面有個「看詳細」按鈕。若訊息有回過，重點在 (1) 確認在問的訊息（但沒很重要） (2) 看回應、看出處 (3) 確保使用者會按 feedback
• 內文字至少 16px，且避免橫向排版，給調大系統字體的使用者預留空間。
◦ LINE 使用者有回報，當網站傳給長輩的時候，長輩看不到。
◦ 其他 Fact checker 網站的內文字體，有些甚至到 18。
• 由於字要大，所以目前的版本把 card 左右與螢幕貼邊，省下橫向空間放更多字。
◦ 目前作法參考 FB mobile app 的外觀。
◦ 不過其實像 snope 網站在 mobile 上其實還是 card view 的樣子，所以如果有需要，還是可以試排一個更接近目前網站外觀的 card view。
• 資訊架構，按照 LINE 使用者需求來重構：
◦ 網站同時要滿足 fact checker 需求與查謠言的人的需求，而且有較大揮灑空間，所以資訊呈現上可以較豐富；但 LINE 使用者在認知能力上可能較為受限、更容易被其他東西 distract，所以設計上會拿掉網站有呈現的一些資料。
◦ 使用情境是，使用者看到一個謠言回應之後，下面有個「看詳細」按鈕。若訊息有回過，重點在 (1) 確認在問的訊息（但沒很重要） (2) 看回應、看出處 (3) 確保使用者會按 feedback
- 👍2
2021-04-25
上面的 figma 補了
1. 若 LIFF URL 有帶 replyId，可以顯示單則回應的樣式
2. 沒有回應時的外觀
1. 若 LIFF URL 有帶 replyId，可以顯示單則回應的樣式
2. 沒有回應時的外觀
我媽說 figma 上的字太小看不到
慘
慘
但這已經比 slack 預設字大了
剩下的交由手機作業系統來修正吧 （眼神死）
剩下的交由手機作業系統來修正吧 （眼神死）
2021-04-26
@craig.bossley has joined the channel
⚠️ *Action required - upgrade app for g0v* ⚠️
@anna.marti has joined the channel
2021-04-27
⚠️ *Action required - upgrade app for g0v* ⚠️
2021-04-28
來回報一下超暴力的相關影片（會造成心理不適）
```美國是怎麼了!？在加州的黑人和白人...
他們毫無理由將一位中國人活活打死!
太可惡了!
我們政府卻還抱著美國大腿?
一一一一一
如此深仇大恨!頗不解?異疑点如下：
1，少數族群黑人數多於拉丁及亞裔,韓裔強勢又团結,只有找華裔下手?
2，美帝白人至上,利用兩岸矛盾，售軍火給台湾又可讓台民為他们挡子彈，何樂而不為?
3,全世界最笨即台民！```
https://cofacts.org/article/22wg1p6sh5ygj
```美國是怎麼了!？在加州的黑人和白人...
他們毫無理由將一位中國人活活打死!
太可惡了!
我們政府卻還抱著美國大腿?
一一一一一
如此深仇大恨!頗不解?異疑点如下：
1，少數族群黑人數多於拉丁及亞裔,韓裔強勢又团結,只有找華裔下手?
2，美帝白人至上,利用兩岸矛盾，售軍火給台湾又可讓台民為他们挡子彈，何樂而不為?
3,全世界最笨即台民！```
https://cofacts.org/article/22wg1p6sh5ygj
感謝提供影片，終於可以來查了（深吸一口氣
My god 他做了啥事要這樣打
確實沒有太多線索，也沒拍到臉，如果附近沒有監視器之類的東西，連檢調都很難偵辦起訴施暴者哀哀
現在不方便開聲音，可能要聽一下對話
現在不方便開聲音，可能要聽一下對話
根本不是英語呀⋯⋯
這也太難找，雖然說一聽就不是英文但是不知道怎麼查證這是在哪裡
mygopen 真的超猛
我其實有試過手機開 google translate app
自己瞎選語言、按下麥克風按鈕
並且把手機靠近電腦喇叭然後播放
但我選的每個語言他都沒有辨識出來 QQ
自己瞎選語言、按下麥克風按鈕
並且把手機靠近電腦喇叭然後播放
但我選的每個語言他都沒有辨識出來 QQ
Bumps <https://github.com/NodeRedis/node-redis|redis> from 2.8.0 to 3.1.1. Release notes _Sourced from <https://github.com/NodeRedis/node-redis/releases|redis's releases>._ > *V3.1.1* > *Enhancements* > > • Upgrade node and dependencies (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1578|#1578>) > > *Fixes* > > • Fix a potential exponential regex in monitor mode (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1595|#1595>) > > *v3.1.0* > *Enhancements* > > • Upgrade node and dependencies and redis-commands to support Redis 6 (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1578|#1578>) > • Add support for Redis 6 `auth pass [user]` (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1508|#1508>) > > *v3.0.2* > > No release notes provided. > > *v3.0.0* > > This version is mainly a release to distribute all the unreleased changes on master since 2017 and additionally removes a lot of old deprecated features and internals in preparation for an upcoming modernization refactor (v4). > > *Breaking Changes* > > • Dropped support for Node.js < 6 > • Dropped support for `hiredis` (no longer required) > • Removed previously deprecated `drain` event > • Removed previously deprecated `idle` event > • Removed previously deprecated `parser` option > • Removed previously deprecated `max_delay` option > • Removed previously deprecated `max_attempts` option > • Removed previously deprecated `socket_no_delay` option > > *Bug Fixes* > > • Removed development files from published package (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1370|#1370>) > • Duplicate function now allows db param to be passed (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1311|#1311>) > > *Features* > > • Upgraded to latest `redis-commands` package > • Upgraded to latest `redis-parser` package, v3.0.0, which brings performance improvements > • Replaced `double-ended-queue` with `denque`, which brings performance improvements > • Add timestamps to debug traces > • Add `socket_initial_delay` option for `socket.setKeepAlive` (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1396|#1396>) > • Add support for `rediss` protocol in url (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1282|#1282>) Changelog _Sourced from <https://github.com/NodeRedis/node-redis/blob/master/CHANGELOG.md|redis's changelog>._ > *Changelog* > *v3.0.0 - 09 Feb, 2020* > > This version is mainly a release to distribute all the unreleased changes on master since 2017 and additionally removes a lot of old deprecated features and old internals in preparation for an upcoming modernization refactor (v4). > > *Breaking Changes* > > • Dropped support for Node.js < 6 > • Dropped support for `hiredis` (no longer required) > • Removed previously deprecated `drain` event > • Removed previously deprecated `idle` event > • Removed previously deprecated `parser` option > • Removed previously deprecated `max_delay` option > • Removed previously deprecated `max_attempts` option > • Removed previously deprecated `socket_no_delay` option > > *Bug Fixes* > > • Removed development files from published package (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1370|#1370>) > • Duplicate function now allows db param to be passed (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1311|#1311>) > > *Features* > > • Upgraded to latest `redis-commands` package > • Upgraded to latest `redis-parser` package, v3.0.0, which brings performance improvements > • Replaced `double-ended-queue` with `denque`, which brings performance improvements > • Add timestamps to debug traces > • Add `socket_initial_delay` option for `socket.setKeepAlive` (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1396|#1396>) > • Add support for `rediss` protocol in url (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1282|#1282>) Commits • <https://github.com/NodeRedis/node-redis/commit/fc28860dd4d4baa0449078948bbb0cf1e77c587d|`fc28860`> Bump version to 3.1.1 (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1597|#1597>) • <https://github.com/NodeRedis/node-redis/commit/2d11b6dc9b9774464a91fb4b448bad8bf699629e|`2d11b6d`> fix <https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1569|#1569> - improve monitor_regex (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1595|#1595>) • <https://github.com/NodeRedis/node-redis/commit/7e77de84bc80b0742321939c59612dc27559bbff|`7e77de8`> Add Chat (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1594|#1594>) • <https://github.com/NodeRedis/node-redis/commit/5d3e99544147adba0c3d33dc5cab1c2898ea8576|`5d3e995`> Merge branch 'master' of <https://github.com/NodeRedis/node-redis|https://github.com/NodeRedis/node-redis> • <https://github.com/NodeRedis/node-redis/commit/b797cf28f5911e65269d43260b49a2961b7f626a|`b797cf2`> add user to README.md • <https://github.com/NodeRedis/node-redis/commit/79f34c22a45eb767e713d7b115970aa40e578b6c|`79f34c2`> Bump version to 3.1.0 (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1590|#1590>) • <https://github.com/NodeRedis/node-redis/commit/7fdc54ea2f1c08de5de63ba9cbccea044ae3801a|`7fdc54e`> fix for 428e1c8a7b2322c2650294638cb1663ac5692728 - fix auth retry when redis ... • <https://github.com/NodeRedis/node-redis/commit/09f0fe822862baf0f2a5d2b37537babffaae66d8|`09f0fe8`> "fix" tests • <https://github.com/NodeRedis/node-redis/commit/428e1c8a7b2322c2650294638cb1663ac5692728|`428e1c8`> Add support for Redis 6 `auth pass [user]` (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1508|#1508>) • <https://github.com/NodeRedis/node-redis/commit/bb208d0b9d7d4f4ce7677108f4d74459d842092a|`bb208d0`> Add codeclimate badge (<https://github-redirect.dependabot.com/NodeRedis/node-redis/issues/1572|#1572>) • Additional commits viewable in <https://github.com/NodeRedis/node-redis/compare/v.2.8.0...v3.1.1|compare view> Maintainer changes This version was pushed to npm by <https://www.npmjs.com/~leibale|leibale>, a new releaser for redis since your current version. <https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores|Dependabot compatibility score> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: • `@dependabot rebase` will rebase this PR • `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it • `@dependabot merge` will merge this PR after your CI passes on it • `@dependabot squash and merge` will squash and merge this PR after your CI passes on it • `@dependabot cancel merge` will cancel a previously requested merge and block automerging • `@dependabot reopen` will reopen this PR if it is closed • `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually • `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) • `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reope…
感謝提供影片，終於可以來查了（深吸一口氣
My god 他做了啥事要這樣打
確實沒有太多線索，也沒拍到臉，如果附近沒有監視器之類的東西，連檢調都很難偵辦起訴施暴者哀哀
現在不方便開聲音，可能要聽一下對話
現在不方便開聲音，可能要聽一下對話
根本不是英語呀⋯⋯
twitter.github.io 2021-04-29
這個介紹裡面，把很久以前的 timestamp highlight 出來我覺得不錯
https://matters.news/@szyeefun/%E7%94%A8%E5%8D%80%E5%A1%8A%E9%8F%88%E6%BA%AF%E6%BA%[…]%B6%E4%BA%8B-zdpuArs14BWQ71HRFh1mzPmRRpyAiCUZyCQJGba3bhPWn6sQF
例如說訊息如果距今 1 年以前回報的，就在時間上標一個顏色；如果更久以前，就底色 + 粗體之類。
https://matters.news/@szyeefun/%E7%94%A8%E5%8D%80%E5%A1%8A%E9%8F%88%E6%BA%AF%E6%BA%[…]%B6%E4%BA%8B-zdpuArs14BWQ71HRFh1mzPmRRpyAiCUZyCQJGba3bhPWn6sQF
例如說訊息如果距今 1 年以前回報的，就在時間上標一個顏色；如果更久以前，就底色 + 粗體之類。
Matters
向假新聞宣戰早已不是什麼新鮮事了。獨立檢證、協力查核、智能辨識⋯⋯無論手段新穎或傳統，在假訊息竄增的速度面前，似乎都顯得蒼白無力，一不小心還會惹禍上身。這不禁讓人想問：還有什麼辦法？難道真理終究戰不勝謊言？人類還有救嗎？如果你已經對於當今所有防堵假訊息的手法都感到失望，準備當個極...
2021-04-30
hmmm….我們要跟浪潮一波嗎
NFT 募資
必須說我沒什麼概念呢
@lucien 有興趣主導嗎
我研究了一下
fact-nft 這個平台流量似乎也沒有很大
TFC 這個買賣我覺得是象徵意義比較大
OpenSea
Do you know what happened to those eight 'disinformers' arrested by Chinese police forces for alerting Wuhan people about the new coronavirus? Did you know this fact check helped to bring 99 organizations to work together against
- 👍1
We should put donation information on the index, article pages. Reference: <https://donate.wikimedia.org/|https://donate.wikimedia.org/>
這樣說吧
要不要做 -> 市場對於事實查核的 nft 興趣
要不要跟他們合作 -> 掛一個 fact nft 聯盟
怎麼做 -> 挑有共鳴的題目，畫精美的圖卡
要不要做 -> 市場對於事實查核的 nft 興趣
要不要跟他們合作 -> 掛一個 fact nft 聯盟
怎麼做 -> 挑有共鳴的題目，畫精美的圖卡
我還覺得可以想想
一個直覺的脈絡是
現在有個全世界的大事件，大家都會有關注的謠言，我們跟上包裝一個精美的 nft ，這樣應該會賣得出去
其實也可以做成像是
捐款選項裡面有一個是 NFT，形式是你會得到我寫的某個 fact check 的精美圖卡這樣 (?)
捐款選項裡面有一個是 NFT，形式是你會得到我寫的某個 fact check 的精美圖卡這樣 (?)
這也是一種做法
像是一種捐款小禮物 (?)
那就要 nft 發行跟轉移的成本要小的情況了呢
可能就會是中心化的服務
因為現在鏈上操作的成本很貴
原來還是有成本的呀 QQ
我前幾天趁 gas （成本競價）低時發幾個交易
可以吃很好很好的 fine dinning 了呢
比如說之前長榮塞子都可以做成 nft 賣了
這也是一種做法
像是一種捐款小禮物 (?)
那就要 nft 發行跟轉移的成本要小的情況了呢
可能就會是中心化的服務
因為現在鏈上操作的成本很貴
原來還是有成本的呀 QQ
我前幾天趁 gas （成本競價）低時發幾個交易
可以吃很好很好的 fine dinning 了呢
⚠️ *Action required - upgrade app for g0v* ⚠️
• Implement `WonderCallEmbed` that loads iframe in a tooltip activated by a FAB • Shows loading until iframe is fully loaded • The FAB is not included in server-side rendering <https://user-images.githubusercontent.com/108608/116677068-580ace80-a9da-11eb-810b-3f6f805ac0df.gif|wondercall> Email: <https://user-images.githubusercontent.com/108608/116677113-65c05400-a9da-11eb-854e-eaada3fe28b1.png|圖片>