seigo (Aaron Seigo)Disabled
Disabled

Projects (13)

User Details

User Since
Apr 12 2015, 12:47 PM (191 w, 1 d)
Roles
Disabled

Recent Activity

May 31 2017

seigo moved T1907: Group chat from Backlog to Ready on the Kolab Chat board.
May 31 2017, 3:37 PM · Kolab Chat
seigo renamed T2471: Perform clean up when room falls to zero users from Remove room invite bookkeeping on rooms that end up with zero users to Perform clean up when room falls to zero users.
May 31 2017, 12:20 PM · Kolab Chat
seigo added a comment to T2414: Join/Leave events in channels.

.. the server side should come for free in the form of presence diffs once Presence.track'ing is added to RoomChannel. Then it will just be the client-side display that is left.

May 31 2017, 12:12 PM · Kolab Chat
seigo closed T2465: Only open new rooms from the user list as Invalid.

After talking today with Alek, we'll move to a SPA directly after notifications and room metadata (the current topics we are working on) which will make this a moot point. So closing.

May 31 2017, 12:12 PM · Kolab Chat
seigo moved T2465: Only open new rooms from the user list from Review to Ready on the Kolab Chat board.
May 31 2017, 12:11 PM · Kolab Chat
seigo moved T2465: Only open new rooms from the user list from Ready to Review on the Kolab Chat board.
May 31 2017, 12:10 PM · Kolab Chat
seigo added a comment to T2471: Perform clean up when room falls to zero users.

have implemented leave and terminate functions in RoomChannel, but am now blocked by Alek's feature branch which also introduces an :after_join handler where Presence.track'ing can be placed.

May 31 2017, 12:10 PM · Kolab Chat
seigo added a comment to D443: More on channels management.

Looking really good already.. :)

May 31 2017, 11:23 AM
seigo moved T2471: Perform clean up when room falls to zero users from Ready to In Progress on the Kolab Chat board.
May 31 2017, 10:55 AM · Kolab Chat
seigo created T2471: Perform clean up when room falls to zero users.
May 31 2017, 10:55 AM · Kolab Chat
seigo created T2465: Only open new rooms from the user list.
May 31 2017, 10:43 AM · Kolab Chat
seigo moved T2405: Create mapping of channels for users from Ready to Review on the Kolab Chat board.
May 31 2017, 10:42 AM · Kolab Chat
seigo added a comment to T2405: Create mapping of channels for users.

implemented in the feature/room_perms branch

May 31 2017, 10:42 AM · Kolab Chat
seigo added a comment to T2450: invite users to existing channel.

implemented in the feature/room_perms branch

May 31 2017, 10:42 AM · Kolab Chat
seigo moved T2450: invite users to existing channel from Ready to Review on the Kolab Chat board.
May 31 2017, 10:42 AM · Kolab Chat
seigo added a comment to T2453: room persistence for user:user chats.

implemented in the feature/room_perms branch

May 31 2017, 10:41 AM · Kolab Chat
seigo moved T2453: room persistence for user:user chats from Ready to Review on the Kolab Chat board.
May 31 2017, 10:41 AM · Kolab Chat

May 29 2017

seigo created T2453: room persistence for user:user chats.
May 29 2017, 5:17 PM · Kolab Chat
seigo created T2450: invite users to existing channel.
May 29 2017, 5:14 PM · Kolab Chat
seigo created T2447: room info stored in ets.
May 29 2017, 5:14 PM · Kolab Chat
seigo added a comment to T2402: Add user authorization lists to channels.

This is now implemented in the feature/room_perms branch

May 29 2017, 5:11 PM · Kolab Chat
seigo moved T2402: Add user authorization lists to channels from Ready to Review on the Kolab Chat board.
May 29 2017, 5:11 PM · Kolab Chat
seigo created T2432: Do mnesia setup in the application.
May 29 2017, 10:37 AM · Kolab Chat

May 24 2017

seigo created T2414: Join/Leave events in channels.
May 24 2017, 2:00 PM · Kolab Chat
seigo added a comment to T2408: Files app shows file modified date not in user's timezone.

No, K16 is enough

May 24 2017, 1:46 PM · Chwala, Bug Reports, Roundcube Kolab Plugins
seigo added a comment to T2408: Files app shows file modified date not in user's timezone.

The issue with emails is a user-confusion issue: you get an email with an attachment, you save that attachment "to the cloud", and now the time is oddly different than the email. So it isn't that there is a bug with emails, but that the time differences cause problems for users.

May 24 2017, 1:31 PM · Chwala, Bug Reports, Roundcube Kolab Plugins
seigo added a comment to T1634: "IMAP Idle" through guam connections are dropped after 300 seconds.

I have pushed a commit to the feature/autodetect_ipv6 branch which turns on keepalive for the socket; there is a corresponding fix on the eimap (imap server connection code) side as well, though I'm not sure that is needed. Hopefully that will resolve the issue as it will try to keep the socket up as long as the other side is still there according to the OS settings for these timeouts. by default on Linux it is 2 hours, which should be plenty.

May 24 2017, 1:25 PM · Guam, Bug Reports
seigo updated subscribers of D437: attempt to autodetect when ipv6 is available.
May 24 2017, 1:14 PM
seigo created D437: attempt to autodetect when ipv6 is available.
May 24 2017, 1:14 PM
seigo created T2408: Files app shows file modified date not in user's timezone.
May 24 2017, 10:43 AM · Chwala, Bug Reports, Roundcube Kolab Plugins
seigo created T2405: Create mapping of channels for users.
May 24 2017, 10:29 AM · Kolab Chat
seigo created T2402: Add user authorization lists to channels.
May 24 2017, 10:28 AM · Kolab Chat
seigo moved T1901: 1:1 Chat from In Progress to Review on the Kolab Chat board.
May 24 2017, 10:27 AM · Kolab Chat
seigo closed T1901: 1:1 Chat as Resolved.

This is now working, minus authentication and persistence. I will create new tasks for this.

May 24 2017, 10:26 AM · Kolab Chat
seigo moved T1898: Notifications from Ready to In Progress on the Kolab Chat board.
May 24 2017, 10:26 AM · Kolab Chat
seigo moved T1898: Notifications from Backlog to Ready on the Kolab Chat board.
May 24 2017, 10:26 AM · Kolab Chat

May 23 2017

seigo added a comment to T2118: Rooms/Channels API design.

I have started a feature branch in feature/room_metadata

May 23 2017, 2:08 PM · Kolab Chat
seigo moved T1976: Spec out authentication from Ready to Backlog on the Kolab Chat board.
May 23 2017, 10:10 AM · Kolab Chat
seigo moved T1892: Authentication from In Progress to Backlog on the Kolab Chat board.
May 23 2017, 10:10 AM · Kolab Chat
seigo closed T2331: Port to Phoenix 1.3 as Resolved.
May 23 2017, 10:09 AM · Kolab Chat
seigo moved T2331: Port to Phoenix 1.3 from Review to Done on the Kolab Chat board.
May 23 2017, 10:09 AM · Kolab Chat

Apr 18 2017

seigo accepted D417: port to phoenix 1.3.
Apr 18 2017, 12:17 PM

Apr 8 2017

seigo created T2331: Port to Phoenix 1.3.
Apr 8 2017, 7:15 PM · Kolab Chat
seigo retitled D417: port to phoenix 1.3 from to port to phoenix 1.3.
Apr 8 2017, 7:14 PM

Mar 21 2017

seigo accepted D411: Fixed apply_ruleset_clientside return value argument order..

Tested and approved! Thanks, Christian, for catching this refactor booboo.

Mar 21 2017, 9:34 AM

Mar 20 2017

seigo added a comment to D405: Banged against guam until it works..

Is this with no ruleset in the config for a particular connection? Or when you connect with a client claiming to be /Kolab in the ident, or? Let's look at your guam config / setup when we are together next

Mar 20 2017, 11:26 AM

Feb 7 2017

seigo accepted rKCdc0565751e0f: Use Amnesia, get rid of Ecto.

Ah .. the differential associated with this is closed, but (for whatever reason?) phabricator was showing this item as still open/active, which i did not expect. sorry for the noise. :)

Feb 7 2017, 10:01 AM

Feb 6 2017

seigo added a comment to T2076: Commands are not handled individually when a client sends.

So same issue, with slightly different results: multiple commands sent together, which is allowed by the IMAP spec indeed, and then the client ends up waiting for responses that do not come as expected. Thanks for the report.

Feb 6 2017, 10:42 AM · Guam, Kolab 16, Bug Reports
seigo added a comment to rKCdc0565751e0f: Use Amnesia, get rid of Ecto.

This is already pushed into develop, no?

Feb 6 2017, 10:38 AM

Feb 3 2017

seigo added a comment to T2118: Rooms/Channels API design.

If I'm understanding you correctly, this is really about persistence: dealing with disconnections / reconnections etc. how do we manage notifications, invitations, permissions, etc.

Feb 3 2017, 11:05 AM · Kolab Chat

Jan 20 2017

seigo moved T1501: Implement WOPI Lock action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1502: Implement WOPI GetLock action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1503: Implement WOPI RefreshLock action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1504: Implement WOPI UnLock action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1505: Implement WOPI UnlockAndRelock action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1507: implement WOPI PutRelativeFile action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1509: Implement WOPI DeleteFile action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1508: Implement WOPI RenameFile action from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI
seigo moved T1514: Implement document_rename action for WOPI RenameFile from Backlog to Done on the WOPI board.
Jan 20 2017, 11:25 AM · WOPI, Chwala
seigo accepted D369: Use Amnesia, get rid of Ecto.

Those require statements look fine IMHO. Yes, it's a bit more verbose that one could imagine if it were placed somewhere central, but at least this way it is explicit: this code requires that API .. and so it says so right there. That kind of clarity makes that extra line worth it ... +1 from me.

Jan 20 2017, 10:55 AM

Jan 18 2017

seigo added a comment to T2115: Internal design considerations - users.

Amnesia is quite nice, and makes using mnesia rather more bearable from Elixir. Let's try it!

Jan 18 2017, 11:30 AM · Kolab Chat
seigo added a comment to D363: Better status/presence handling (T2109).
last status persistence.
Jan 18 2017, 11:29 AM
seigo added a comment to T2109: User presence persistence.

I have commented on D363 ... :)

Jan 18 2017, 10:47 AM · Kolab Chat
seigo added a comment to D363: Better status/presence handling (T2109).

Perhaps I'm missing something, but this simply shows the effective status of the user in the UserStatusWidget on the client, so if I have two connections in the same context with statuses as:

Jan 18 2017, 10:46 AM
seigo moved T2193: Endpoint for retrieving supported statuses and their relative weights from Backlog to Ready on the Kolab Chat board.
Jan 18 2017, 10:36 AM · Kolab Chat
seigo created T2193: Endpoint for retrieving supported statuses and their relative weights.
Jan 18 2017, 10:36 AM · Kolab Chat

Jan 17 2017

seigo added inline comments to D363: Better status/presence handling (T2109).
Jan 17 2017, 11:21 AM

Jan 16 2017

seigo added a comment to D363: Better status/presence handling (T2109).

One small comment above. Otherwise looks good. Will you merge the changes in my branch into this and push it all together into develop? I would +1 that.

Jan 16 2017, 2:41 PM

Jan 13 2017

seigo moved T1904: Single page chat web application from Backlog to In Progress on the Kolab Chat board.
Jan 13 2017, 1:05 PM · Kolab Chat
seigo moved T1901: 1:1 Chat from Backlog to In Progress on the Kolab Chat board.
Jan 13 2017, 1:05 PM · Kolab Chat

Jan 11 2017

seigo added a comment to T2115: Internal design considerations - users.

Sorry, I skipped some details. I was thinking about invitations in specific, and how we could use a Phoenix.Token as part of the invitation metadata to make authorizing the invitation when it is used easy/simpler. I may have actually put this in the wrong ticket even. Indeed, this belonged on T2118 *sigh*.

Jan 11 2017, 4:07 PM · Kolab Chat
seigo added a comment to T2109: User presence persistence.

Ah, one other "little" issue .. in the listBy() javascript function there is this:

Jan 11 2017, 3:59 PM · Kolab Chat
seigo added a comment to T2109: User presence persistence.

Ok, so FINALLY got time to look at this this afternoon :)

Jan 11 2017, 3:27 PM · Kolab Chat
seigo added a comment to T2109: User presence persistence.

Looking ...

Jan 11 2017, 10:27 AM · Kolab Chat

Jan 10 2017

seigo added a comment to T2115: Internal design considerations - users.

remembered Phoenix.Token just now -> https://hexdocs.pm/phoenix/Phoenix.Token.html

Jan 10 2017, 2:27 PM · Kolab Chat
seigo added a comment to T2115: Internal design considerations - users.

.. oh, and if we really need/want to, we can always migrate to a full SQL RDBMS in future. The storage/lookup code is not really so big. The reason for choosing mnesia in this use case if because it is largely ephemeral data, speed is nice, and fewer dependencies / setup routines is never a bad thing.

Jan 10 2017, 1:42 PM · Kolab Chat
seigo added a comment to T2115: Internal design considerations - users.

Key/value store should be enough for that. Mnesia (which comes with Elixir/Erlang) uses a tuple as the definition for a table, with an implicit primary key, you can index and search on any field in the tuple. So it is very much like an SQL database in that it has tables, primary keys and optional secondary keys. But it is built into the language and runtime itself, supports RAM-only and on-disk storage as well as clustering if desired. It's a very nice tool to use for "lightweight" database needs (e.g. I wouldn't necessarily try and map a dozen tables with complex relations / refint requirements, or a dataset that was expected to grow to dozens or more GB and require long term storage), as it is easy to use, fast, well integrated and means one less dependency.

Jan 10 2017, 1:40 PM · Kolab Chat
seigo added a comment to T2109: User presence persistence.

+1

Jan 10 2017, 1:26 PM · Kolab Chat

Jan 9 2017

seigo added a comment to T2124: User status.

The common set seems to be:

Jan 9 2017, 12:25 PM · Kolab Chat
seigo added a comment to T2118: Rooms/Channels API design.

This should be modeled so that we can reasonably expect to bridge XMPP to it, and perhaps even matrix.org federation.

Jan 9 2017, 12:06 PM · Kolab Chat
seigo added a comment to T2115: Internal design considerations - users.

I thin it would be very nice and interesting to see if we can run the chat functionality without a database connection at all. The authentication mechanism could be responsible for retrieving the username to show for a given login (defaulting to the login itself) along with "nice things" like the user's image to show, etc. This way, when we go to integrate with the larger Kolab stack, that user information does not need to be synchronized also to the chat database. Wherever they auth against would also give the chat service the user's metadata like username, picture, organization, location info, etc. This has obvious overlap with the user's addressbooks and identities; amazing would be allow the user to select from their identities as configured in Roundcube ... we can get their later, but should keep that kind of integration in mind now. Mostly so we don't end up duplicating that in the chat service directly.

Jan 9 2017, 11:50 AM · Kolab Chat
seigo added a comment to T2109: User presence persistence.
Remember the user status in database and don't reset it on logon nor any other operation, except system/set-status
Jan 9 2017, 11:42 AM · Kolab Chat

Jan 3 2017

seigo accepted D351: Websockets, auth tokens, presence, text chat.
Jan 3 2017, 10:22 AM

Dec 14 2016

seigo added a comment to D345: Store users in database.

Ah, yes, phoenix presence handles their status entirely. We need to do nothing for that (and should not .. it's a complicated thing, and they have implemented it fully).

Dec 14 2016, 2:30 PM
seigo added a comment to D345: Store users in database.

This will be used to store user auth tokens, e.g. to validate sessions? If so, should this use Phoenix.Token instead (https://hexdocs.pm/phoenix/Phoenix.Token.html)? Auth will be served by Kolab (e.g. LDAP), and presence managed by Pheonix Presence .... ?

Dec 14 2016, 1:21 PM

Dec 13 2016

seigo closed T1964: Configurable session security, a subtask of T1976: Spec out authentication, as Resolved.
Dec 13 2016, 2:15 PM · Kolab Chat
seigo moved T1964: Configurable session security from Review to Done on the Kolab Chat board.
Dec 13 2016, 2:15 PM · Kolab Chat
seigo moved T1892: Authentication from Ready to In Progress on the Kolab Chat board.
Dec 13 2016, 2:15 PM · Kolab Chat
seigo closed T1964: Configurable session security as Resolved.
Dec 13 2016, 2:15 PM · Kolab Chat
seigo closed T1889: Initial project framework as Resolved.
Dec 13 2016, 2:14 PM · Kolab Chat
seigo moved T1889: Initial project framework from In Progress to Done on the Kolab Chat board.
Dec 13 2016, 2:14 PM · Kolab Chat
seigo moved T1949: Internationalization from Review to Done on the Kolab Chat board.
Dec 13 2016, 2:14 PM · Kolab Chat
seigo moved T2018: Create authentication module plug w/dummy auth from Review to Done on the Kolab Chat board.
Dec 13 2016, 2:14 PM · Kolab Chat
seigo moved T927: Crash does not result in NO response from Backlog to Done on the Guam board.
Dec 13 2016, 2:12 PM · Guam
seigo moved T1028: Parse error for LIST command from Backlog to Done on the Guam board.
Dec 13 2016, 2:12 PM · Sprint 201608, Guam
seigo moved T1047: Guam to recognize the PyKolab issued ID from Backlog to Done on the Guam board.
Dec 13 2016, 2:12 PM · Guam, Sprint 201609
seigo moved T1063: Backport the groupware filters fix to Guam 0.7 and make a minor release with them from Backlog to Done on the Guam board.
Dec 13 2016, 2:12 PM · Kolab Enterprise 14 - Extras Audit, Guam, Kolab 16, Sprint 201609, Bug Reports
seigo moved T1305: Winterfell: guam has problem, bad argument in call to binary:match from Backlog to Done on the Guam board.
Dec 13 2016, 2:12 PM · Guam, Bug Reports
seigo moved T1065: Guam crashes frequently (might be SSL related) from Backlog to Done on the Guam board.
Dec 13 2016, 2:11 PM · Guam, Bug Reports
seigo moved T1317: guam crashes on port 143 at the first connection opened from Backlog to Done on the Guam board.
Dec 13 2016, 2:11 PM · Restricted Project, Guam, Kolab Enterprise 14 - Extras Audit, Bug Reports