BLG (Unite) Development

[DontCare4Free]

Come on devs, I feel you guys are really slacking on the development of this project. If you guys need help, I can help, it's no problem just let me know.

It's mostly my fault. I decided before to write the server in Scala/Akka which, to be honest, just bored me which made me very slow. I was able to rewrite the basic server (minus auth) in about 20-30 minutes with Twisted, which just "clicked" with me much more. I've shied away from Twisted in the past, but they now had a proper 64-bit Windows version, so I decided to give it a try.

[Ad Bot]

[Scout31]

I've been doing most of what I can on a client side, but I'm going to be leading the Glass Server now. I've only been home for 2 days in all of July, so that may be contributing to the problem.

[Greek2me]

A lot of the problem is that we're all very busy people.

[elm]

A lot of the problem is that we're all very busy people.

There is a lot of time in a day; utilizing that time is key. I'm sure you guys can set aside 20 minutes a day for development purposes.

[Scout31]

My schedule for the next two weeks:

9:00 - Wake up
9:00 - 11:00 - BLG/Computer (I spent today on asymmetrical encryption so that the whole project doesn't get shutdown)
11:00 - 12:00 - Practice Music
12:00 - 9:00 - Marching Band Practice (Mandatory)
9:00 - 11:00 - More development

So far today, that schedule has worked out. Does 4 hours suit your fancy?

[elm]

So what's been getting worked on lately and when are we do for an update.

[DontCare4Free]

So what's been getting worked on lately and when are we do for an update.

There are currently two candidate servers:

• The "official" one, just a skeleton for now, going for that "fat server" approach
  
• My proposal, has working auth and all, can inject messages sent to it over RabbitMQ (useful for setting up scheduling), aiming for a simple client for just the RC while the other stuff will be done separately from the "eval proxy"
  

For auth Jincux said he planned to use Blockland auth for the client and API tokens for the servers, while I plan on using a PKI for both encryption and authentication.

[elm]

Sounds intense, when should this be finished?

[Rub]

There are currently two candidate servers:

• The "official" one, just a skeleton for now, going for that "fat server" approach
  
• My proposal, has working auth and all, can inject messages sent to it over RabbitMQ (useful for setting up scheduling), aiming for a simple client for just the RC while the other stuff will be done separately from the "eval proxy"
  

For auth Jincux said he planned to use Blockland auth for the client and API tokens for the servers, while I plan on using a PKI for both encryption and authentication.

You like being really OTT don't you?

[Crêpe]

bump.
needs to be, it's too good to die

[Scout31]

We've been working, there's just nothing to post about.

[Scout31]

Today we created an encryption system for secure communication of confidential and abusable server control data between your client and server (with or without wrapper). Any information that you don't want us reading or having access to, we don't want to be held accountable for. All control over your server is now completely encrypted. The downside of this is that we were unable to implement asymmetrical keys, so you'll have to manually enter the 512-digit-key on your client, or just simply join the server you want to control, go in to the overlay, and press "Acquire Key".

[Kalphiter]

communication between your client and server

Why?

[Scout31]

Why?

Client <---> Glass Server <---> Server

Didn't describe that all the way I guess, sorry.

[Kalphiter]

For what?

Logging in to do something?