14:55:47 #startmeeting hubs-devel 14:55:47 Meeting started Tue Oct 17 14:55:47 2017 UTC. The chair is mizmo. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:55:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:55:47 The meeting name has been set to 'hubs-devel' 14:56:03 #chair sayan abompard shillman shaily jonatoni 14:56:03 Current chairs: abompard jonatoni mizmo sayan shaily shillman 14:56:30 So, last time we talked with sayan we devided the work to make the IRC widget 14:56:38 I'm looking into the frontend 14:56:53 and sayan works on the backend. Please correct me if I'm wrong sayan 14:57:31 I've spent a day or two implementing some of the frontend mockups 14:57:55 but it occurs to me that writing a frontend for a chat client is more complex than I though 14:58:11 as always the nominal case is easy and quick. 14:58:46 but there can be many issues: realtime updates, connection/disconnection, loading or previous messages without eating up the browser's memory, etc 14:59:23 and I don't know how I'm supposed to hook into the backend yet. 14:59:37 i wonder if there is a way - at the least for MVP - to have a flow to get users registered to riot.im and then just redirect any IRC links to riot 15:00:19 whether its hooking into riot.im or our own server 15:00:23 mizmo: yeah, I was thinking of how we could link with Riot.im. It has many more features than we ever will have (or want to have) 15:00:34 there's currently no way to "embed" Riot into a webpage 15:00:44 I've open a feature request on their tracker for that 15:00:59 but they closed it as duplicate, other people have asked for that too 15:01:11 but it doesn't seem to be a priority 15:01:22 ah do you have the main ticket handy? 15:01:34 they have some recent funding problems :( 15:01:34 https://github.com/vector-im/riot-web/issues/5301 15:01:37 https://matrix.org/blog/2017/07/07/a-call-to-arms-supporting-matrix/ 15:01:43 mizmo: yeah I saw that too 15:02:09 Maybe it's just that I'm misinformed, but I'm a bit worried by the fact that we've been working on this widget for months now and it's a bit elusive 15:02:17 the original ticket seems to suggest it's already possible 15:02:31 mizmo: except it's not exactly what is asked 15:02:55 mizmo: they want to "embed" as in "iframe" 15:03:26 i wonder what the p3 label means 15:04:04 i can ask, im a patreon, have access to the patreons only channel 15:04:37 mizmo: I suspect it's priority, they have p1 to 5 labels with color ranging from red to blue 15:04:49 yeh my guess was same 15:05:12 well 15:05:21 I'll ask more in the ticket but I think it was about something a bit different from what we want 15:05:28 in terms of MVP 15:05:46 i think we could do ok just linking out to it and not having the chat inside hubs itself - for MVP, if it was easy to just link out 15:05:54 maybe push a real, full widget off 15:06:29 it we wanted to deploy sooner rather than blocking on IRC 15:06:37 mizmo: the link to the chatroom in Riot.im could be in the hub's description widget 15:06:54 mizmo: Yeah I'm a bit worried about blocking on the IRC widget 15:07:36 abompard: thats one way. or we could have a chat widget, admin could configure to whatever channel, and for users would appear as a 'chat now' button for a team hub or for an individual person, and would launch in another tab a direct link to the channel / pm from fedora hubs 15:08:00 i believe as of this week the new release of riot has a nice intro workflow that walks you through getting registered / etc 15:08:07 mizmo: yeah that's cool too 15:08:26 so we wouldn't even have to handle that part 15:08:35 mizmo: great. 15:08:58 mizmo: would you have time to make some mockups for this version of the chat widget? 15:08:59 i just hope they stick around 15:09:02 its an important project 15:09:09 mizmo: agreed 15:09:20 Riot.im is the same folks of the matrix right? 15:09:42 I'll go sign up for their patreon 15:09:44 sayan: yep 15:09:54 abompard: sure thing 15:10:00 thanks 15:10:05 npp 15:10:40 the $10 level gets you supporter only chat room access + weekly live devel video call access and weekly vlog 15:10:43 so thats what i did 15:11:04 i wonder if itd be possible to fund development of embeddable widget with them, but thats a q over my head 15:11:37 that's a question for stickster ;-) 15:11:45 i will talk to him :) 15:11:57 :+1: 15:12:08 abompard: you didnt happen to look to see if there were other matrix clients that were embeddable? 15:12:10 * mizmo did a cursory look 15:12:37 mizmo: yeah there's something called Interlocutor 15:12:46 https://github.com/pik/Interlocutor 15:12:55 oooooooh its a web component 15:12:56 it's using Polymer 15:13:17 It would depend partly on the costs obviously 15:13:18 Yeah I've been reading on that this morning 15:14:06 stickster: i was thinking something like an outreachy internship, with a set scope and cost, but i dont know how the actual problem of making riot widgetizable is in terms of scope, it may or may not fit neatly into that 15:14:43 but it's not really a chat system, it's a comment system kinda like disqus 15:15:13 abompard: looks like interlocutor requires being regitsered to the server so we'd need to implmeent that registration workflow 15:15:16 mizmo: *nod. Would need to figure that out, so we don't have like a dangling project that doesn't fulfill the intern or us 15:15:39 But I think the idea of combining this with outreachy makes a lot of sense 15:15:42 stickster: i can talk to them and see what they think 15:16:01 that's probably easier to make happen than a random contract or something 15:16:42 that's what i was thinking - its something we've done before so there's already a path of sorts and a model to follow 15:17:40 abompard: ah you are right its comment focused 15:18:39 abompard: could we use this in the chat widget to provide a view of the room, and have the button to link people over to riot to chat? https://view.matrix.org/room/!cURbafjkfsMDVwdRDQ:matrix.org/ 15:19:04 mizmo: totally 15:19:20 mizmo: we only need to know how to get that room id 15:19:34 ok awesome. it'll work for team hubs but not users 15:19:45 abompard: maybe put that burden on the hub admins for now 15:19:59 abompard: admins fill the settings page 15:20:04 i can look them up manually in riot, eg this room is !pQKymaaQXBFBeuOxHn:matrix.org 15:20:05 I mean the matrix room id 15:20:30 that seems really doable 15:20:43 mizmo: yeah that's enough for a MVP, unless I find a magical API that gives me the answer easily 15:21:03 theres a js api for matrix, let me see if it lets you look up 15:21:54 mizmo: nope, you cannot do that using the js dsk 15:22:02 https://matrix.org/docs/api/client-server/#!/Room32directory/get_matrix_client_r0_directory_room_roomAlias 15:22:11 so the aliases are predictable, this should work 15:22:39 eg the alias for this room is #freenode_#fedora-hubs:matrix.org 15:22:50 so you take the base IRC room name, prepend #freenode_ and append :matrix.org 15:23:07 that's the alias that you put into this api call 15:23:08 mizmo: perfect 15:23:48 so we could just ask the hub admin for the irc channel name (as we were planning anyway), convert it to a matrix alias, then look up using the API call for the ID, and use that to pull in both the viewer and also to link over to riot 15:24:56 Yep! 15:25:59 \o/ 15:26:11 sounds cool :) 15:26:11 i think that'll be good enough for mvp 15:26:17 yeah I think so too 15:26:34 and it doesnt tie us too tightly either in case something happens 15:28:04 yeah 15:28:45 cool so ill work on those mockups today and if needed tommorrow with the aim of having something to show tomm afternoon my time 15:28:53 any other concerns re: irc generally? 15:29:10 BTW, it works: curl -X GET --header 'Accept: application/json' 'https://matrix.org:8448/_matrix/client/r0/directory/room/%23freenode_%23fedora-hubs%3Amatrix.org' 15:29:34 mizmo: no other concerns from me 15:29:58 \o/ 15:29:59 yay! 15:30:16 cool let's close it out then? 15:30:20 yeah 15:30:31 #endmeeting