tags: cofacts, meeting note GA: UA-98468513-3 —

20250224 會議記錄

:::info

:potable_water: Release pipeline

Carried over from last week

Internet archive logging
uploadMedia refactor
Gemini transcript https://github.com/cofacts/rumors-api/pull/359
Gemini model & location selection https://github.com/cofacts/rumors-api/pull/361
Badge related API

New

Header that bypasses Cloudflare proxy-read timeout mechanism (not tested) https://github.com/cofacts/rumors-api/pull/362

Carried over from last week

LINE bot - long response handling https://github.com/cofacts/rumors-line-bot/pull/401
- Fixed redis reply-token & batch handling

https://lin.ee/1QUzEX4nI

2/22 (Sat) 大松：https://g0v-jothon.kktix.cc/events/g0v-hackath65n
~~2/24 (一) Side-event 17:00~18:00 比鄰演講~~ 取消
2/25 (二) 9:00~10:00 NDI Panel
2/25 (二) 14:00 ~ 15:00 Cofacts 自己的 talk - ID # 23894 – “Crowd-sourced fact-checking in AI era - Lessons learned by Cofacts
- 地點：South Lobby of the 2nd floor
- 投影片：https://docs.google.com/presentation/d/1_FGSKvgP2jh9o_22FhKSuDWLI-cu4lY3u95PL5lVb9o/edit
2/26 (三) 早上擺攤
2/26 (三) 12:45-13:45 大平台 ~~(Promote 攤位)~~
2/27 (四) 11:30~12:30
- NiemanLab / Panel Discussion / Challenge around deepfake detection
2/27 (四) 12:45~13:45 ID # 25017 - Global Giants, Local Influence: The Role of International Social Media in Shaping National Discourse
- 地點：201E

~~2/23 (日) OCF sattlelite event~~
- 活動日期：2025/02/23
- 工作坊 14:00 – 17:30 如何使用 Tor 避開審查並匿名瀏覽
- 工作坊 18:00 – 19:00 如何使用 OONI 偵測與觀察網路審查狀況
- 演講座 19:30 – 21:00 Tor 在網路監控的世界中捍衛個人線上隱私權
~~2/23 (日) 3pm-6pm【工作坊】打造韌性網路：動手實作「不需海纜」的網路~~
2/26 (三) DWeb panel 10:15~11:15 (Promote 攤位)
2/24~2/27 OCF＆司改會一起擺攤
- 在餐廳外面

人

時間

空間

3F Networking Lounge https://www.rightscon.org/venue2025/#floor3 / https://www.ticc.com.tw/wSite/vr360/index.html
- 16 號
~~先在 1F Help Desk 報到，才知道在哪個 booth~~ 已報到
180 cm x 60 cm 桌子＋2 張折疊椅
牆上不能貼東西
不一定有電，延長線自備
沒有推車與幫手，進場撤場都是手搬

材料

https://drive.google.com/drive/folders/1U-etbZSOiFzpXgOr0GtBxkwYKk666nni

Errors and mitigations

LINE bot
- node-fetch connection ends prematurely
- may be caused by Cloudflare, because no error comes from rumors-api
- causes infinite waiting on user side –> add error handing https://github.com/cofacts/rumors-line-bot/pull/403
Cloudflare
- Proxy Read Timeout 100s
- Proxy Write Timeout 30s
- Not configurable in our account.
- Before Proxy Read Timeout, send an arbitrary header to pass the 100s read timeout: https://github.com/cofacts/rumors-api/pull/362
  - Tested by sleeping in POST /graphql; request still get cut on 100s even after a header is flushed on 90th second
- It is hard to find a video that needs to process for more than 100 seconds……
  - Tried to use ffmpeg to stretch a video to 5 mins long (LINE upper limit). It’s processed within 80 seconds.
nginx proxy
- proxy_read_timeout: Default 60s; production already at 240s
  - Causing 504 errors
  - ✅ Moved staging timeout from default to also 240s: https://github.com/cofacts/rumors-deploy/pull/33
- proxy_send_timeout: Defualt 60s; already bigger than Cloudflare’s write timeout.
rumors-api: ListArticles with transcript creation turned on
- Weird error from Vertex AI SDK

Other thoughts

Suggestions from Gemini: https://gemini.google.com/share/ebad8b428ac9
- Many of them are total rewrite of the transfer protocol
Bypass both nginx and LINE bot using docker-compose network
- On production, TW LINE bot & API is in the same docker-compose network
- On LINE bot may set API_URL to http://api:5000/graphql so that it connects directly through docker-compose
  - API_URL is only used on NodeJS
  - LIFF calls /graphql on LINE bot server, and LINE bot server connects to rumors-api via NodeJS as well (w/ schema stitching)
- –> ✅ Changed API_URL config near 2025/02/23 15:40 on production, LIFF & bot continued working, logging confirmed that requests come from docker network