GitHub

hyphacoop/configurations

Contribute to hyphacoop/configurations development by creating an account on GitHub.

• 🙌1

Libera Chat

Channel registration

A next-generation IRC network for FOSS projects collaboration!

• 🤔2

HackMD

g0v IRC 現況 - HackMD

# g0v IRC 現況 現在 g0v 主要的 IRC 頻道是 #<http://g0v.tw|g0v.tw> ，位在 freenode 這個 IRC 網路上。 ## 待處理事項 ### 是否取回 freenode 上的 IR

• 🙌1
• 👍1
• 1

• 2

• 6
• 1
• 1
• 2

freenode.net

Group registration - freenode

<http://freenode.net|freenode.net> - Supporting Free and Open Source Software Communities since 1998

• 3
• 4

• 1

fly 2021-05-27 10:48:10

#manifesto

• 😵4
• 💔3
• ⚠️4

chewei 哲瑋 2021-05-27 10:58:07

是否要來確認 Full Slack Export 是什麼..
https://g0v-tw.slack.com/archives/C01SHPD80UD/p1622083639017300?thread_ts=1622034205.006500&channel=C01SHPD80UD&message_ts=1622083639.017300

pm5 2021-05-27 11:31:34

要請 slack admins 幫忙確認囉

ronnywang 2021-05-27 11:33:13

應該是好幾年前我有用 slack 內建的 export 功能提供匯出檔給 @kevinliao，但我印象中預設的 export 檔是沒有 email 的，我剛剛也有試著匯出過一次裡面沒有（https://g0v-slack-archive.g0v.ronny.tw/ 裡面也沒有 email 資訊)

gugod 2021-05-27 16:00:26

看來我也是自動變成 zulip 那邊的 org owner，如果需要看什麼機密文件(?)的話可能我的畫面上有的看

gugod 2021-05-27 16:05:40

https://github.com/grundleborg/slack-advanced-exporter/blob/master/cmd_fetch_emails.go#L136

看來是有~校正回歸~事後補登 email addr. 的手段

gugod 2021-05-27 16:17:41

https://api.slack.com/methods/admin.users.list 這招

Kevin.

Roles and account information are imported over as part of the full Slack export.

• Forwarded from #bridge
• 2021-05-27 10:47:19

• 🙌1

• 🙌1

webdata/scripts/import-directory.php

``` &lt;?php include(__DIR__ . '/../init.inc.php'); $dir = $_SERVER['argv'][1]; if (!$dir) { throw new Exception("Usage: php import-directory.php [slack export directory]"); } else if (!is_dir($dir)) { throw new Exception("{$dir} is not a directory"); } try { Message::createTable(); Channel::createTable(); User::createTable(); ChannelUser::createTable(); } catch (Exception $e) { } // import channels if (!file_exists($dir . '/channels.json')) { throw new Exception("channels.json not found in {$dir}"); } $channel_info = json_decode(file_get_contents($dir . '/channels.json')); $channel_id_to_name = array(); $channel_name_to_id = array(); $db = Message::getDb(); $max_ts = 0; Message::getDb()-&gt;query("CREATE TEMP TABLE message_temp (LIKE message)"); $terms = array(); $c = 0; foreach ($channel_info as $channel) { try { $channel_id_to_name[$channel-&gt;id] = $channel-&gt;name; $channel_name_to_id[$channel-&gt;name] = $channel-&gt;id; Channel::insert(array( 'id' =&gt; $channel-&gt;id, 'name' =&gt; $channel-&gt;name, 'data' =&gt; json_encode($channel), )); } catch (Pix_Table_DuplicateException $e) { if (Channel::find($channel-&gt;id)-&gt;name != $channel-&gt;name) { // TODO: 看哪邊新... //throw new Exception("id = {$channel-&gt;id} 的頻道名稱是 " . Channel::find($channel-&gt;id)-&gt;name . ", 與 {$channel-&gt;name} 不吻合"); } } foreach (glob($dir . '/' . $channel-&gt;name . '/*.json') as $message_json) { $messages = json_decode(file_get_contents($message_json)); foreach ($messages as $message) { $max_ts = max($max_ts, $message-&gt;ts); $terms[] = sprintf("(%lf,%s,%s)", floatval($message-&gt;ts), $db-&gt;quoteWithColumn('data', $channel_name_to_id[$channel-&gt;name]), $db-&gt;quoteWithColumn('data', json_encode($message)) ); $c ++; if (count($terms) &gt;= 1000) { $db-&gt;query("INSERT INTO message_temp (ts, channel_id, data) VALUES " . implode(',', $terms)); $terms = array(); error_log("insert {$c} records"); } } } } if (count($terms)) { $db-&gt;query("INSERT INTO message_temp (ts, channel_id, data) VALUES " . implode(',', $terms)); $terms = array(); } $sql = "UPDATE message SET data = message_temp.data FROM message_temp WHERE message.ts = message_temp.ts AND message.channel_id= message_temp.channel_id AND (message.data)::text != (message_temp.data)::text RETURNING message.ts"; $res = $db-&gt;query($sql); $u = 0; while ($row = $res-&gt;fetch_array()) { $u ++; } error_log("一共變更 {$u} 筆訊息"); $sql = "INSERT INTO message SELECT * FROM message_temp WHERE (ts, channel_id) IN (SELECT ts, channel_id FROM message_temp EXCEPT SELECT ts, channel_id FROM message) RETURNING message.ts"; $res = $db-&gt;query($sql); $insert = 0; while ($row = $res-&gt;fetch_array()) { $insert ++; } error_log("一共新增 {$insert} 訊息"); foreach ($channel_info as $channel) { $c = Channel::find($channel-&gt;id); if ($max_ts &gt; $c-&gt;last_fetched_at) { $c-&gt;update(array( 'last_fetched_at' =&gt; $max_ts, 'last_updated_at' =&gt; $max_ts, )); } } ```

g0v.hackmd.io

Zulip 事件 - HackMD

• 1
• 👍1

ichieh 2021-05-27 16:48:53

@kevinliao 這邊

chihao 2021-05-27 16:56:56

kcjl 似乎也在增加內容 ++

kjcl 2021-05-27 16:59:04

我跟 Zulip 的通訊完全上傳到 Slack 了。

kjcl 2021-05-27 16:59:34

我把我個人的電子郵件，名字刪掉了。也把 Zulip 員工的名字也刪掉了

kjcl 2021-05-27 16:59:50

也把 API Key刪掉了

chihao 2021-05-27 17:01:12

@kevinliao 不太好讀，建議每一封 email 一個 `##` h2 如何？

kjcl 2021-05-27 17:01:42

先放那裡帶一會兒在整理我先寫一些其他的必要的東西

kjcl 2021-05-27 17:06:00

@ronnywang API Key 現在還有人在用嗎？

kjcl 2021-05-27 17:06:14

可以把他直接刪除掉把

ronnywang 2021-05-27 17:06:39

API Key 目前已經不能使用了

ronnywang 2021-05-27 17:06:49

應該是上週前不能使用的

kjcl 2021-05-27 17:07:41

是因為什麼原因而被禁止的? 想要把它放在 報告裡

ronnywang 2021-05-27 17:08:48

因為上週三開始 #g0v-slack 在討論 slack 治理機制，然後我看到 Slack API Tester 這個 app 我覺得應該沒有人在使用，我就把他刪除掉了，應該就會影響到當初的 API Key

kjcl 2021-05-27 17:09:08

了解，謝謝！

• 🥲1

• 1
• 👍2

• 🤔1

• 4
• 5
• 🎯2
• 1

• 👍2

• 1

• 1
• 👍2

• 1
• 👍4

• 👍4
• 🕳️5
• 1

• 🙌4
• 🎉2
• 😅3
• 🐛1

• 2
• 1

• 1

whenisgood.net

WhenIsGood: g0v Slack/Zulip 事件檢討會議

Plan the time to have your meeting or event by co-ordinating availability with all the particpants using this fuss-free online tool.

• 3
• 2

Chris Bobbe 2021-05-29 02:34:05

> just as himself a g0v participant, not representing his company
I think my role can appropriately be a mixture of the two. 🙂 I'm a Zulip engineer (I started on January 6, 2020), and naturally that influenced my incident response, which will be relevant to the discussion. For example, when privacy concerns were raised, I knew immediately that it was possible for admins to set email visibility to "nobody".

The important point I raised with @kevinliao is that I have never been directly involved in our data import support operations and I'm not well-positioned to speak authoritatively on Zulip's practices there. (I work almost exclusively on the mobile apps.) I know that https://github.com/zulip/zulip/issues/18622 is a high priority, and that the engineers who work in this area are discussing the incident. I'm hoping to collect other g0vers' feedback on the incident, as well as any other ideas about how we can improve Zulip. (g0vers can also contact support@zulip.com or post on Zulip's community server).

One important message I'd like to relay from the Zulip team is that we apologize for not discovering and fixing https://github.com/zulip/zulip/issues/18622 sooner.

Also, I personally feel bad that people's data didn't go the way they expected, and it occurs to me that my own email address might have been affected if things had gone just a little differently in December of 2018. At that time, @kevinliao knew I was a big fan of Zulip, even though I didn't work there, and he knew I had a connection to Taiwan. By chance, he didn't introduce me to g0v and ask me to join the Slack at that time, so my email address could never have been leaked. So, in keeping the privacy of my data, I consider myself lucky. I know that many of you weren't lucky, and I take that as a serious reminder to reflect on how to advance the cause of privacy in Zulip and in the world.

While I expect we may gather useful action items throughout the meeting, my hope is that they'll arise organically from a collaborative discussion where the purpose is to learn more about processes and systems, in situations where honest people were doing their best to use them. I would gently suggest that going straight to bullet-pointed action items might direct our curiosity away from that kind of exploration. And, given my position on the Zulip team that I mentioned above, please know that I won't have all the answers myself, and I'll be glad to relay questions to the team. 🙂

As a heads-up, I'll be absent this weekend for a long-planned vacation and won't be back until my Tuesday morning.

Chris Bobbe 2021-05-29 02:36:17

> 代表他自己（而不是他的公司）
我想我的角色大概是兩種都有。 🙂 我是2020年1月6日時加入Zulip的工程師，這當然影響了我對此事件的反應，而這點我稍後會提到。例如，當有人提出對隱私的疑慮時，我當下便知道管理人員是可以將 email能見度(Email visibility)設定成沒人能看見(nobody)。

我跟 @kevinliao 提到的重點是，我從未直接參與過我們支援資料輸入運作的部分，因此我也不適合以官方的角度來討論 Zulip 這部分的作法。(我基本上只負責行動應用程式的部分。)我知道 https://github.com/zulip/zulip/issues/18622 是個高優先權的案子，而相關領域的工程師也正在討論此事件。我希望能收集 g0v 使用者對此事件的回饋，還有任何其他能幫助我們改善 Zulip 的想法。(g0v 使用者也能寄信至 support@zulip.com 或在 Zulip's community server 上發文。)

我想轉達 Zulip 團隊的一則重要訊息，那就是我們很抱歉沒有更早發現並處理 https://github.com/zulip/zulip/issues/18622 這個案子。

此外，我個人很抱歉大家的資料並沒有依照個人預期的方式處理。我意識到，2018年12月時若處理事情的方式有些許不同，我自己的email也可能受到影響。 @kevinliao 知道，雖然當時我不在 Zulip 工作，但我已經是 Zulip 的大粉絲了。 @kclj也知道我跟台灣的關係(我的配偶是台灣人，也是他幫翻譯的 😆)。幸好他那時沒有告訴我 g0v 也沒有邀請我加入，所以我的 email 才沒有被公開。因此，我覺得我很幸運能保護我的個資。我知道很多人沒有那麼幸運，而我也將此視為重要的提醒，反思如何在 Zulip 和世界上增進隱私權的推廣。

雖然我預計在會議中能收集到有用的行動項目，但我希望這些項目是在合作討論中自然產生的。合作討論的目的為是要更了解這些程序和系統，並知道善意人士是盡其所能地在使用這些程序和系統。我真誠地建議，不要直接條列出行動項目，因為如此一來可能會使我們的討論失去那樣探索的過程。另外，根據上述我在 Zulip 團隊的角色，請諒解我自己可能無法回答所有問題，但我很樂意幫忙將問題轉達給我的團隊。 🙂

對了，美國這個周末有三天連假，因此我要台灣時間周二晚上後才會有空。

#18622 Slack import should respect Slack's counterpart of EMAIL_ADDRESS_VISIBILITY.

When <https://zulip.com/help/import-from-slack|importing data from Slack>, Zulip should respect the <https://slack.com/help/articles/228020667-Manage-email-display|Slack workspace's setting> of who can see email addresses, instead of defaulting to showing email addresses to any user (that default setting is applied to all projects, with or without a Slack import; see the <https://g0v.zulipchat.com/help/restrict-visibility-of-email-addresses#restrict-visibility-of-email-addresses_1|doc> on the setting). The setting should be applied before any users are imported. A large open-source org reports that the delay in getting the right setting applied was multiple years; the Zulip Cloud org was created from a Slack import, there was a long period of inactivity, and then when it regained activity, users saw email addresses they considered private and an owner applied the "nobody" setting.

• ❤️2

• ❤️5