infras

Month: 2018-10

2018-10-05

Felipe 11:15:39
@phiven has joined the channel

2018-10-09

sdf611097 12:57:59
@sdf611097 has joined the channel

2018-10-13

patcon 00:30:50
@acechen :wave:
patcon 00:31:54
Ok, so if we'd like to, we can use matterbridge for all the syncing between tools, or at least between irc/telegram/slack.

Thoughts on that? Know who we'd need to consult with to make a call in that?
caasi 02:15:47
cc @gugod
gugod 02:15:50
@gugod has joined the channel
patcon 19:15:15
<!here> how do we create repos in the g0v github org? cc @kevinphy
patcon 19:16:47
is working on config for a irc/telegram test of the bridge
patcon 20:41:26
re: using matterbridge for telegram/irc
patcon 20:42:19
seems that this is the format that will show up for messages from telegram, which is a bit of a bummer:

https://imgur.com/DWTJA0b
patcon 20:43:16
the channel name in telegram is a number, but it can't be hidden in slack without also hiding the slack channel name that originate in slack :confused:
patcon 20:43:58
so we could either lose the channel reminder everywhere, or deal with confusing numbers on the odd time one of the 50 telegram users send a message
patcon 21:01:37
ok, got irc working too

slack view: https://imgur.com/e9pWQu4

telegram view: https://imgur.com/oBpbj4a

irc view: https://imgur.com/vUwc2xo
patcon 21:06:08
@gugod notes on testing are above.

main decision point is on how to display names in slack. options:

1. patcon (CHANNEL@ACCOUNT) <== where CHANNEL will be useful for slack/irc, but a numeric identifier for telegram. ACCOUNT will be the slack "team" or the protocol for non-slacks (irc or telegram)

2. patcon (ACCOUNT) <== ditch the channel due to confusing telegram thing, but now people won't know which language channel someone is speaking from, in case they want to check the original message
patcon 21:07:40
but otherwise, i feel this might be good to migrate, if we feel like it. lemme know.

happy to wait until the bridge is fully documented and maybe even on a platform with shared access before we move forward
patcon 22:10:51
@yutin so do you think we should actually create #general-jp and #general-kr? As in, are there people here who speak only those languages? (and even if not, there is prob reason to be pre-emptive, so that they feel welcome when they arrive :slightly_smiling_face: )
patcon 22:12:26
anyhow, happy to set that up if you'd like :slightly_smiling_face:
chihao 22:33:15
I’m conflicted!
pm5 17:14:49
the #general channel seems to be a better place to inquire (ironically in english) about this?
chihao 17:45:52
@pm5 +1 ping @patcon :slightly_smiling_face:
patcon 17:46:07
i'll clean up the bridge so that it preserved markdown formatting, then I'll make an ask in #general :slightly_smiling_face:
chihao 17:46:27
@patcon ++!
patcon 17:50:05
going to propose:
:small_blue_diamond: #general: no translations, just drops in messages as they were written in whatever langauge
:small_blue_diamond: #general-en messages in english (with translation when they're not)
:small_blue_diamond: #general-tw messages in chinese (with translations when they're not)
:small_blue_diamond: #general-ja #general-ko #general-LANG for any others ppl want (though technically, I'll prob make this a separate proposal, so as not to lump them together)

so that means #general will be an unmediated experience for the polyglots who can read everything -- it'll just look like everyone magically knows how to understand one another :slightly_smiling_face:
patcon 17:50:42
any suggestions for improving on this?
mrorz 10:50:43
As a person that reads English and a little bit Japanese, I think the proposal above looks nice :smiley:

I am more concerned about threads. Replies in threads would look out of context in translated channels. If rebuilding threads after translation is technically not possible, I think we would need to just ignore replies in threads (if we can distinguish thread replies from normal messages)
mrorz 14:31:20
I think if permalink to the original message can be implemented, then the thread context problem may be solved as well (since messages in threads do have separate permalink &amp; clicking link can bring the people back to context)
https://g0v-tw.slack.com/archives/C02G2SXKX/p1539583587000100
patcon 15:34:46
@mrorz ok sounds good. thanks so much for the thoughtfulness in your feedback! And I think down the road, we can perhaps we clever with quoting a bit of the original message in the thread as a hint (so ppl can be reminded what's being replied to without clicking the link).

Github issue here: https://github.com/42wim/matterbridge/issues/343

2018-10-14

patcon 17:50:05
going to propose:
:small_blue_diamond: #general: no translations, just drops in messages as they were written in whatever langauge
:small_blue_diamond: #general-en messages in english (with translation when they're not)
:small_blue_diamond: #general-tw messages in chinese (with translations when they're not)
:small_blue_diamond: #general-ja #general-ko #general-LANG for any others ppl want (though technically, I'll prob make this a separate proposal, so as not to lump them together)

so that means #general will be an unmediated experience for the polyglots who can read everything -- it'll just look like everyone magically knows how to understand one another :slightly_smiling_face:

2018-10-15

patcon 07:24:58
re: [translation] bridge. new features
patcon 15:09:48
- translation now works for an arbitrary number of localized channels
- most markdown formatting works (*bold* is the final hold-out, requiring an upstream library to be upgraded)
- as mentioned early, telegram and irc technically work and have been loosely tested by me in "test channels". we can decide to turn them on if we'd like
patcon 15:11:45
@yutin was asking about docs.
patcon 15:11:51
I've created docs to help people understand "bridges" before they have translation, and I wonder whether it would be best to 1) add to them, or 2) created new docs copied from them (for clarity)
patcon 15:33:49
This sort of thing might also be helpful: https://matterbridge-heroku-viewer.herokuapp.com/#organizing

(it's a little ugly, but parses the config file directly from github, so people can see the high-level bridging that's happening :slightly_smiling_face: )
patcon 15:14:55
The best-practice we'd adapted before (with bridges between slacks), was to have a clear "This channel is BRIDGED." mention in the channel topic, like so: https://imgur.com/Z7SuH1J

We could do the same here, in each channel, to explain?

imgur.com

Imgur

Imgur

patcon 15:40:55
@caasi re: me breaking your bridge! Sorry, that was my fault. I changed the nick format when testing telegram/irc bridging. Perhaps we could agree that the extra stuff in the nickname will always be in brackets? Like `patcon (general@g0v-tw)` or `patcon (@irc)` or whatever? Then you can regex match and I won't keep breaking it as we figure things out? :slightly_smiling_face:
caasi 15:42:59
It’s not your fault. I’m bad at RegExp.
caasi 15:44:03
Now I match it with `/ \(.*/`. :joy:
patcon 15:53:33
is there a place where we document pieces of g0v infra? (sorry, that feels like a silly or impossible question)
caasi 16:13:14
Here is the infras hackfoldr. https://beta.hackfoldr.org/g0v-infras/
caasi 16:13:29
But it has no index page. :joy:
hal 16:18:01
@hal has joined the channel
patcon 16:19:03
@hal pulled you in here, in case the conversation about chat bridges is helpful to your networking the Japanese brigades :slightly_smiling_face:
patcon 16:20:04
@patcon set the channel topic: Docs: https://beta.hackfoldr.org/g0v-infras

2018-10-22

idiotmax 11:37:51
@idiotmax has joined the channel
ttcat_OCF_jothon_staff 22:09:06
@ttcat971 has joined the channel

2018-10-23

hisa_x 20:36:31
@hisa_x has joined the channel

2018-10-28

patcon 00:54:05
hey all, can someone create a bot account for me, named something like "g0v matterbridge"? i think i found a bug with legacy tokens, and having a bot account (a more "blessed" way) would help me do sanity checks. thanks!

cc: @ronnywang @clkao
moon_c 16:56:21
@moon_c has left the channel

2018-10-29

patcon 19:17:39
heyo, just some updates on the translation bridge, for those interested:

:small_blue_diamond: I've got a PR in queue that will *preserve message threading* for relayed messages: https://github.com/42wim/matterbridge/pull/529
:small_blue_diamond: finalizing a small app that will make *creating translation bridges as easy as creating a new channel* with a language code appended: https://github.com/patcon/matterbridge-autoconfig#readme

these are both coming down the pipeline, and not yet done :wink:

GitHub

Opportunistically preserve threading between Slack instances by patcon · Pull Request #529 · 42wim/matterbridge

Is your feature request related to a problem? Please describe. Even with clear documentation and encouragement of work-arounds, unthreading of messages between slacks leads to confusion and misunde...

GitHub

patcon/matterbridge-autoconfig

App that generates a Matterbridge config file based on channel names. - patcon/matterbridge-autoconfig