Hi,
I would be definitely for another messaging meetup as I missed the eff
speakeasy.
What time would suit you today (Monday)?

-- Franta

On Sun, Dec 28, 2014 at 8:25 PM, Ximin Luo <[email protected]> wrote:
> Hi!
>
> We did have a meetup, in Hall 13 then later some random floor space because 
> NoisySq was full. Sorry if you arrived after 3pm and couldn't find us!
>
> I personally could be up for another chat about it, but not sure if we could 
> gather enough people together for another session. Feel free to use the wiki 
> page to organise one, though.
>
> X
>
> On 28/12/14 19:46, [email protected] wrote:
>> Turmbar on the other side of the trainstation from CCH.
>>
>> EFF speakeasy starts is 20:00 to 22:00 today Sun Dec 28th.
>>
>> Happy to walk over if others want to join.
>>
>> https://www.eff.org/event/speakeasy-hamburg
>>
>> Please post a heads up. The EFF reservation policy is never strongly 
>> enforced.
>>
>> On Sun, Dec 28, 2014 at 7:37 PM, lilia <[email protected] 
>> <mailto:[email protected]>> wrote:
>>
>>     Interested. Perhaps at the eff speakeasy tonight at Turmbar?
>>
>>     On Dec 28, 2014 7:34 PM, "[email protected] <mailto:[email protected]>" 
>> <[email protected] <mailto:[email protected]>> wrote:
>>
>>         It appears the messaging meetup didn't happen.
>>
>>         Is there any interest in an informal get together?
>>
>>
>>
>>         On Dec 22, 2014 10:56 PM, "Jeff Burdges" <[email protected] 
>> <mailto:[email protected]>> wrote:
>>
>>
>>
>>
>>             On 22 Dec 2014, at 16:03, Nathan of Guardian 
>> <[email protected] <mailto:[email protected]>> wrote:
>>             > On Mon, Dec 22, 2014, at 03:58 PM, Jeff Burdges wrote:
>>             >> - Who wants to help us with writing an Android GUI for Pond?
>>             > I though TheGrugq (or someone working with him) already did?
>>             > https://twitter.com/thegrugq/status/522406147991425024
>>
>>             At present, I believe nobody has actually seen any code for that 
>> project.  Also, Google recently added better mobile support for Go that did 
>> not exist when they started that project : 
>> https://godoc.org/golang.org/x/mobile/app
>>
>>             I currently hope TheGrugq or whoever actually releases the code 
>> at 31c3, so that *I* don’t feel the need to do any GUI work.  If that 
>> doesn’t happen then we should start a public project that takes advantage of 
>> Google’s tools to avoid rewriting Pond’s client layer.
>>
>>             I would envision using the existing Pond client code in Go and 
>> writing a thin Android wrapper layer in Scala (but vanilla XML produced by 
>> Android Studio, not Scaloid).  I haven’t done *anything* on this so far 
>> except for studying existing work on running Scala and Go together, a bit of 
>> modularization of the Go code that was needed for other purposes, and 
>> working out that certain Android tools like data providers are a poor fit 
>> for Pond.  I know Pond's Go code fairly well from doing other stuff with it 
>> though, so it’s doable.
>>
>>             Anyway let’s hope that TheGrugq solves this first.  :)
>>             Jeff
>>
>>
>>             _______________________________________________
>>             Messaging mailing list
>>             [email protected] <mailto:[email protected]>
>>             https://moderncrypto.org/mailman/listinfo/messaging
>>
>>
>>         _______________________________________________
>>         Messaging mailing list
>>         [email protected] <mailto:[email protected]>
>>         https://moderncrypto.org/mailman/listinfo/messaging
>>
>>
>>
>>
>> _______________________________________________
>> Messaging mailing list
>> [email protected]
>> https://moderncrypto.org/mailman/listinfo/messaging
>>
>
>
> --
> GPG: 4096R/1318EFAC5FBBDBCE
> git://github.com/infinity0/pubkeys.git
> _______________________________________________
> Messaging mailing list
> [email protected]
> https://moderncrypto.org/mailman/listinfo/messaging
_______________________________________________
Messaging mailing list
[email protected]
https://moderncrypto.org/mailman/listinfo/messaging

Reply via email to