Jump to content

Gaduzila 1.0: Private instant messeging

- - - - -

This topic has been archived. This means that you cannot reply to this topic.
12 replies to this topic

#1
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
Here is an experimental project I made some time ago. Gaduzila is a private IM messanger. It does not send text messages or emoticons, because it was designed to transfer files and screenshots. And it does that so easily that you might not believe it without seeing it yourself. I propose you watch the video. :)

http://forum.codecal...=1&d=1251909174

YouTube - Gaduzila demonstration

Say what you like or don't. Any suggestions will be nice, too. Gaduzila 2.0 is more or less underway in writing concept art so what you propose might actually become reality.

I thank all in advance.

Attached Files



#2
Guest_Jordan_*

Guest_Jordan_*
  • Guests
Wow, that looks very simplistic and very useful. I watched the video. Where are the files stored when the user is logged out? Where is the source? :)

#3
BlaineSch

BlaineSch

    Writes binary right handed and hex left handed

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 2,448 posts
Yes, I second seeing the source!

#4
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
Remember it was an experimental messenger. My goal was to see how easy can be using IM, like sending a file with one click. The other person automatically receives the file and it appears on their desktop. ^^

Major flaws are: It works only with two profiles (mine and Thistle). Also it does not work at all when the server application is not running on my pc, therefore you can't send without receiving. :P

Honestly, the code is so bloated that even I cannot maintain it. It uses TCP/IP connections, new one every few seconds, to check for new files to receive it. Gaduzila 2.0 will have completely new networking code, probably not TCP/IP at all.

Sorry Jordan and BlaineSch. I will not post the sources for that reason: GUI and usability are perfect, code is bloated like a poop. Showing code will only spread bad practices and idiotic design. Please give me some nice suggestions on how to improve usability and new features. :rolleyes:

#5
amrosama

amrosama

    Writes binary right handed and hex left handed

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 8,674 posts
wow, awesome!
i really like it
yo homie i heard you like one-line codes so i put a one line code that evals a decrypted one line code that prints "i love one line codes"
eval(base64_decode("cHJpbnQgJ2kgbG92ZSBvbmUtbGluZSBjb2Rlcyc7"));
www.amrosama.com | the unholy methods of javascript

#6
amrosama

amrosama

    Writes binary right handed and hex left handed

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 8,674 posts
when a user sends a file, that file is stored on the server till the other user logs in.
is that true?
if yes then i suggest sending files directly between clients(or at least allow sending when online), you can get lots of files on the server in no-time
yo homie i heard you like one-line codes so i put a one line code that evals a decrypted one line code that prints "i love one line codes"
eval(base64_decode("cHJpbnQgJ2kgbG92ZSBvbmUtbGluZSBjb2Rlcyc7"));
www.amrosama.com | the unholy methods of javascript

#7
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
Ah, you are very right Amrosama. Sorry, server can store files for future transfer. But the server app still has to be running of course.

It was a personal project for me and Thistle. I did not care back then. Also after long debugging I realized that Thistle has a dynamic IP. And he cannot open ports, or at least it did not work for me. This all led to the way it works now.

#8
Guest_Jordan_*

Guest_Jordan_*
  • Guests

ArekBulski said:

Honestly, the code is so bloated that even I cannot maintain it. It uses TCP/IP connections, new one every few seconds, to check for new files to receive it. Gaduzila 2.0 will have completely new networking code, probably not TCP/IP at all.

Your only other choice is UDP which wouldn't be very reliable for file transfer. I don't see how you are not going to use TCP.

ArekBulski said:

Sorry Jordan and BlaineSch. I will not post the sources for that reason: GUI and usability are perfect, code is bloated like a poop. Showing code will only spread bad practices and idiotic design. Please give me some nice suggestions on how to improve usability and new features. :rolleyes:

When can we expect version 2.0 with source and something to download/try?

#9
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts

Jordan said:

Your only other choice is UDP which wouldn't be very reliable for file transfer. I don't see how you are not going to use TCP.

I was thinking about using MySql database for example, and let Gaduzila 2.0 access it directly. I just don't want to use TCP streams directly, because inventing my own TCP-based protocol, like with MSN, would be like a nightmare.

Jordan said:

When can we expect version 2.0 with source and something to download/try?

I got some ideas in my mind, but that is all I can say for the moment. Maybe when I find some intriguing functionality suggestions then I will decide to drop everything else and start working on it.

Current phase: Planning functionality and usability features, or call it brainstorming. Even before writing a Concept Art document, actually.

#10
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
The discussion burned out, so let me try to heat it up. My question to everyone is... *drums*

What features do you expect in Gaduzila 2.0 for your own usage?

Those I am planning myself are: text messages with emoticons, sending files and screenshots, automatic import of contacts and emoticons from online profile (stored on the server).

I will definitely consider releasing the messenger into open beta and stable usage when we get to that point, of course. :)

#11
Guest_Jordan_*

Guest_Jordan_*
  • Guests
When you say "text messages" do you mean to a phone like SMS or do you mean like any other IM client. Is your intention a full-blown IM client or just a file transfer client?

I'd like to see some encryption, personally. I don't like the idea of people reading what I write.

#12
ArekBulski

ArekBulski

    Speaks fluent binary

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,376 posts
Well, sending SMS to cellphones is not easy and not a wanted feature at all. IM clients are meant to send text messages, and then files. That is the most needed part.

Encryption is not a problem, especially if it is done on client-level. Server may have no need nor ability to encrypt/decrypt messages. So the owner cannot read your private messages.

Now a real killer question: what would be best? A centralized network where all messages are routed through a server? Or maybe server would only store profiles, contact lists and authorize users (give certificates)? So all texting would go directly from client to client, only the message itself would be encrypted, and signed by a certificate. So you cannot send messages on someone's behalf he he. What do you think, Jordan?