| 14 Jun 2018 |
 Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek pushed to dev: separated utility functions from MatrixOlmWrapper - https://github.com/ajberchek/matrix-olm-cpp/commit/4ddc7f696426d5355ae8334b87a6dd4d475b81de | 04:56:19 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek pushed to dev: Began unit testing utility functions - https://github.com/ajberchek/matrix-olm-cpp/commit/f80438c49a88ecf1afc4f4da83086990f3700014 | 05:10:50 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek pushed to dev: Added tests for getting message info and fixed bug with obtaining key - https://github.com/ajberchek/matrix-olm-cpp/commit/013c2b1825bcdef2171c51f6155ca7a08647c63b | 05:54:57 |
| 18 Jun 2018 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek pushed to dev: Added tests to validate signing/verification. It can verify messages signed by this code, but cant verify the example message - https://github.com/ajberchek/matrix-olm-cpp/commit/329c2ba48dd5da672995558540aef5c79436535b | 03:05:26 |
| 20 Jun 2018 |
 anoa | You might want to make some more noise about this, not sure many people know stuff is going on here. Also room is lacking discussion :p | 17:14:12 |
 @mujx:matrix.org | true dat | 17:25:18 |
 ajberchek | Begins banging on a tin can | 18:27:20 |
| ajberchek | Would this be a good topic for the upcoming matrix hackathon? | 18:27:42 |
| ajberchek | Discussion point: Would more people want to contribute discussion or code wise, if I hashed out a more detailed roadmap and created issues on github for the features needing to be implemented still? | 18:28:45 |
| anoa | Yes, most definitely. | 18:36:26 |
| anoa | Also matrix sprint is currently going on, though pretty sure e2ee stuff was already covered today. | 18:36:45 |
| ajberchek | Great, I'll get going on the creation of the roadmap and hopefully have it finished up sometime this week. | 18:38:37 |
| ajberchek | It will mainly include the migration from c++ Olm to c Olm, utilizing the key query, key claim, and key sync endpoints, beginning sessions, and crypto ops for sessions. | 18:39:54 |
| ajberchek | Is there anything huge I am missing from that list? | 18:40:18 |
| ajberchek | Oh, neat, what came of the discussion? Any writeups available online yet? | 18:40:40 |
| * anoa doesn't quite remember the e2ee doc, so not sure | 18:41:26 |
| anoa | And I wasn't part of the convo on that one, but I'll expect something will come out of it soon if anything did come up. I imagine it was likely for cross-signing and other nice e2ee features. | 18:42:21 |
 @cadair:cadair.com |
Would this be a good topic for the upcoming matrix hackathon?
The upcoming what now?! | 23:20:43 |
| @cadair:cadair.com | A matrix hackathon sounds like great fun | 23:21:13 |
| 21 Jun 2018 |
| anoa | There's currently no such thing planned, but I agree that that would be quite awesome to host one. | 07:40:09 |
| ajberchek | @anoa, Okay, I'll check it out then and see what needs to be added in. Okay, I'll keep an eye out for that as well. | 18:31:27 |
| ajberchek | @Cadair oops, sorry about that, I guess I got the sprint mixed up with a hackathon lol. It would be really cool to have a matrix hackathon though. Are remote hackathons a thing, so people dont have to fly to the same geographical location? | 18:34:31 |
| 23 Jun 2018 |
| ajberchek | Should the client or the wrapper be the one to handle m.room.encryption state event? I feel like it should be the client since that message won't be encrypted AFAIK. Additionally, there will already be code to handle rooms in that client code, and if this responsibility were pushed down to the wrapper, then room state knowledge would need to be added. | 19:35:47 |
| ajberchek | Opinions? | 19:35:50 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek opened issue #8: Initialize New Session from content in m.room_key event [open] - https://github.com/ajberchek/matrix-olm-cpp/issues/8 | 19:42:17 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek opened issue #9: Download Device List for Users In the Room [open] - https://github.com/ajberchek/matrix-olm-cpp/issues/9 | 19:44:54 |
| ajberchek | I suppose there will need to be another callback provided by the client if the wrapper is to not handle the room events. Otherwise the client would need to be aware of when the wrapper is creating a new session and would need to be able to retrieve the necessary information to package into an event to send to that user they are starting the session with. | 19:49:36 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek opened issue #10: Create functionality to start an Olm session [open] - https://github.com/ajberchek/matrix-olm-cpp/issues/10 | 19:50:39 |
| ajberchek | Perhaps a better option would be to provide another wrapper function called to initialize a session, and that would return the pertinent event contents for the client to send to the room? | 19:54:17 |
| Github [@aberchek:matrix.org] (deprecated) | [ajberchek/matrix-olm-cpp] ajberchek opened issue #11: Start a Megolm session [open] - https://github.com/ajberchek/matrix-olm-cpp/issues/11 | 19:54:28 |
