Tuesday, November 30, 2010

macho-evolutionIRC download



MaviaIRCv0.2 download



NdozIRC download



BiNgGo--IRC.jar



BIRC_02

DOWNLOAD HERE








Download BIRC_02.jar irc application Jowo @ allnetwork Comunity use the Java language. Ad offerings from http://bintangjayareload.wen9.com


BIRC_01.jar

DOWNLOAD HERE







Download BIRC_01.jar applications jowo @ allnetwork irc community. Presentation of ad http://bintangjayareload.wen9.com, chating more friends and more money


XIXIXIXIRC.JAR

DOWNLOAD HERE












Download the IRC application xixixirc.jar is quite beautiful and naked


XIXIRC.JAR

DOWNLOAD HERE




Download xixirc.jar want to laugh I saw it. kwkwakwakwakw .............


DOWNLOAD MACHOIRC V05

 Download:



DOWNLOAD HERE





Download machoIRC v0.5 is worth a try. not so much extra that is in version ll far from perfect. hopefully there are some people who like it.


download machoIRC v32

DOWNLOAD HERE




Download v0.32. We recommend that advice should not be downloaded application ini.bila your hp low speed only, this application is very heavy.


Monday, November 29, 2010

MACHOIRC V04 DOWNLOAD

machoirc 04 download



KAbar gembira bagi orang jawa aplikasi ini di edit jadi pakai bahasa jawa yag gak bisa bahas.indonesia bisa pakek ini (padahal aku yo gak iso) applikasi ini aku dapat dri webnya mas jowo semoga bermanfaat ya teman teman


Friday, November 12, 2010

WILERES IRC client

WILERESIRS


The last, and
indeed the
best, IRC
Client I tried
was "Wireless
IRC" (9.99
from
Handango).

This was by
far the slickest IRC client i
used and is the client i now
use daily. It looks good, it
connects seamlessly, its
tabbed windows makes it easy
to navigate different chat-
rooms and since its not
freeware/shareware, it has
some customer support for
when you have problems. It
solves all the problems i had
with the other clients.

The UI
is more graphic and far more
user-friendly than either Virca
or WLIrc and it has far more
connection and setting options
than the free clients. The text-
input problem is also solved as
the text-input screen pops-up
at the bottom of the chat
window which allows you to
read other people messages
as you type your own. Text
can also be automatically
thumbed in without having to
press any other buttons to
open the input box. Another
great option is the Download
Tab which allows you to see
which files you are currently
downloading and how far
along they are, something
which isn't included in most of
the free clients.
Supports Symbian Series60
Phones Only.


VIRCA irc mobile client

 VIRCA
This first
client i tried,
which came
recommended
by the guys in
#mobitopia,
was Virca. It's
a J2ME based

IRC Client
which is free to use making it
a good place to start. Its a
very simple piece of software
with no frills. The interface is
text-based and very simple
and setting-up a connection is
easily done. My only
annoyance is the fact that you
can't just start thumbing in
messages but have to push in
the joystick first to open the
text-input screen. This also
means you can't see what
people are saying while you
are typing a message.

The
text-based interface also gets
very annoying and a more
structured interface would be
far more appropriate.
Supports any java-enabled
mobile phone.


K-IRC mobile client

K-IRC
(Mobile IRC
Client)
k-IRC is
totally free
java-based
mobile
application
(client) for
connecting
to any IRC
server.

It
will execute
on any
handheld
device or
mobile,
supporting
Java 2 Micro
Edition
(actually

CLDC1.0/
MIDP1.0). k-
IRC allows
you to login
to an IRC
server,
enter
multiple
channels at
the same
session, talk
in the
channels
and with
individuals
and receive
others'
messages
and easily
keep the
track of
active
channels
and switch
between
them.


WLirc mobile client

WLIRC is a IRC Client for Java
cell phones or any other
device who support java MIDP
1.0.
Download
To download the program to
your phone, simply write this
address in your wap browser:
http://wirelessirc.sourceforge.net/
WLIrc.jad (the address is
casesensitive)
or visit the download page

Features:
Runs on any J2ME device.
Support multiple windows.
Support connection througt an
http gateway for devices who
doesnt support sockets. (List
of available servers)
Saves configuration on the
phone for later use. that
means that you need only one
click to connect and join your
favorite channels.

Reported to work with:

Nokia: 2650(*), 3100(*),
3120(*), 3200(*),
3300(*),3410(*), 3510i(*),
3650(*), 5100(*), 5140, 6020,
6030, 6060, 6021, 6100(*), 6101,
6220, 6230, 6230i, 6230, 6255(*),
6260, 6280, 6610(*), 6610i, 6630,
6670, 6680, 6800, 6810,6820,
7210(*), 7250(*), 7260, 7600(*),
7610, 7710, 9300, 9500, ngage
(*), N70, N73, N80, E60

Sony Ericsson: T610(*), Z600(*),
Z1010(?), K500, K600i, K700,
k700i, k750i, S700i, V800,
W800i, W810i, W900i, Z520A,
Z530i

Siemens: S55, C55, C60, M50,
M55, MC60, M65, CF62, CX65,
ME45, S65, SL55, A65, SX1(*^)

Samsung: E100(?), SGH-E700,
X100,X426(*),
X450(*),C-100,SGH-
X640(?),SGH-D900

Motorola: T720(?),T721(?),V80,
V300(*), V535, V600(*),
V220,V280, Razr V3, C380(?),
C381(?), C550, C650, A630(?),
A768, A780, E1000, E398

Blackberry: 6230(?), 7230(*),
7280, 7290, 7510(?), 7520
(remove the startup channel
in the settings, and join
manually once on the server,
otherwise you get a
nullpointerexception)

Sharp: TM100(*), GX-15(*)

Alcatel: 735i(?)

lg: 6200, 8110(?),8130

Mitac Mio: 8380,
Nec: e616V

palmOne Treo: 600 (need to
download J2ME first)

Sanyo: RL-4920, SPC-5400,
MM-8300

Sharp: GX22(*)

Sagem: MyC5-2(*)

Panasonic: x800(?)



Emulators: suns wtk1.0
emulator(^)
* Can only connect through a
httpgateway
? not sure if they support
sockets (please tell me)
^ screenshot of model with
wlirc
Reported to not work with:
All models who not support
midp 1.0 (java)
Nokia: 6310i
Please tell me if you have an
model who is not in this list.
(also tell me if the phone
support sock ets). And it is
also nice if you send a picture
of you model with wlirc

*** If you have connection
problems you need to set up
an access point with direct
internet access, that doesn't
go through the WAP gateway,
and of course your account
will need to have permissions
to use this access point
(regular accounts normailly
don't). You should contact
your network operator and
ask them for the settings to
configure an internet access
point, or you could try this list.

*** Problems with ping timout?
set your gprs settings to never
disconnect or join a busy
chanel.
If you have any questions or
problems with the software
check http://groups-
beta.google.com/group/wlirc
or send a mail to
wlirc@googlegroups.com.

Version history:
v1.01 (2006-07-12)
New color display code (faster
and less buggy)
Show timestamps on messages
socket poll (fix disconnects
problems for some users)
Hide motd
v1.0 (2005-09-22)
Fixed scrollbar bug
v0.98 (2005-06-07)

Support central and eastern
europe charset (iso-8859-2)
charset (type central) thanks
to David Kreus for the code
Save favorites, thanks to
Tzavala Polina for some of the
code

Notifiers( sound,alert) on
channel, private messages
v0.97 (2005-01-07)
Support baltic charset (type
baltic)
Operator commands
(op,voice, kick)
Ctcp commands (ping, version)
Bug fixes
v0.96 (2004-10-06)
Support russian charset
(cyrillic and koi8r (type in
those names under config/
encoding))
Rewrote the parser of text
from server (made the client
a bit smaller and faster, and a
lot easier to read the code)
Also some minor bug fix in this
release
v0.95 (2004-09-08)
Faster login to irc server in
http mode
Saving of config is faster
Some bug fixes
v0.94 (2004-08-12)
Fixed string encoding in http
connection mode
Added a notify list (notifys you
when friends enters irc)
Added possibility to enter real
name

Added pageup/pagedown (key
3 and 9)
Shortcut for send message is
'*'
Added go to bottom of page
(key 7), top of page (key 1)
Posiible to clear window with
typing /clear
Minor bug fixes
Multiple channels on join and
multiple gateways are now
seperated with ' ' (a
chararcter)
v0.93 (2004-05-27)
Rewrote the socket
connection (faster and less
cpu intensive)
Fixed string encoding in socket
connection mode
Possible to specify multiple
gateways with ','
Windows buffer size is now
configurable
Minor bug fixes
v0.92 (2004-01-05)
Irc port is configurable
 

Easier to install the
httpgateway
Minor bug fixes
v0.91 (2003-21-12)
Added color support
Minor bug fixes
v0.90 (2003-09-15)
Initial release
Other irc midlets:
jmIrc
Virca


JMIRC mobile client


JMIRC - IRC MIDlet for mobile     
phones


jmIrc is a J2ME MIDlet allowing
ie. cell phone owners to use
IRC wirelessly. It should work
on any device supporting MIDP
1.0 and also supports
connecting through HTTP
proxy server on phones that
don't support the Java socket
API.
This project started as a fork
of Sverre Valskrå's WLIrc but
eventually led to be a
complete rewrite project. Its
aim is to be as small and
lightweight as possible still
trying to maintain the ease of
use and all needed features.
At the same time it tries to be
some kind of hybrid
implementing all the most
useful features from other
clients.
Some features
Should run on any J2ME device
Tries to be small and easy to
use (v0.95 is 34 kB, Virca is 33
kB and WLIrc 1.0 is 49 kB)
Supports multiple windows
and scrolling is easy with
pgup/pgdown and home/end
buttons.
Supports Russian codepages
KOI8-R and Windows-1251
natively
Supports UTF-8 autodetect,
native encoding/decoding and
fallback charset if decoding
fails
Supports connecting through
an HTTP proxy and provides a
standalone easy-to-set-up
proxy
You can add favourites for
most used phrases and send
them with few button presses
Full and working support for
mIRC colours (WLIrc has also
full but not always so working
support)
All files are free software and
thus GPL'd including the proxy
code


Tuesday, November 9, 2010

INTERNET RELAY CHAT HISTORY

IRC was born during summer 1988 when Jarkko "WiZ" Oikarinen wrote the first IRC client and server at the University of Oulu, Finland (where he was working at the Department of Information Processing Science).
Jarkko intended to extend the BBS software he administrated at tolsun.oulu.fi, to allow news the usenet style, real time discussions and similar BBS features. The first part he implemented was the chat part, which he did with borrowed parts written by his friends Jyrki Kuoppala and Jukka Pihl. It was initially tested on a single machine, and according to the words from Jarkko himself "The birthday of IRC was in August 1988. The exact date is unknown, at the end of the month anyways.". The first IRC server was named tolsun.oulu.fi.
Jyrki Kuoppala pushed Jarkko to ask Oulu University to free the IRC code so that it also could be run outside of Oulu, and after they finally got it released, Jyrki Kuoppala immediately installed a server (which later became irc.cs.hut.fi). This was the first "irc network".
Ari Lemmke's own words: "At the same time Jyrki installed ircd, I was at the same room and had nothing to do, so I decided to crack into tolsun (the irc server Sun machine at Oulu), and naturally ;-) got in through a new hole in sendmail. (At that time Jyrki was still the best cracker I knew...)"
Jarkko got some friends at the Helsinki and Tampere Universities to start running IRC servers when his number of users increased.
Other universities soon followed. Markku Järvinen helped improving the client. At this time Jarkko realized that the rest of the BBS features probably wouldn't fit in his program!
Jarkko got in touch with guys at the University of Denver and Oregon State University. They had got an IRC network running (they had got the program from one of Jarkko's friends, Vijay Subramaniam -- the first non-finnish person to use IRC) and wanted to connect to the finnish network. IRC then grew larger and got used on the entire Finnish national network - Funet - and then connected to Nordunet, the Scandinavian branch of the Internet. In November 1988, IRC had spread across the Internet.
In the middle of 1989, there were some 40 servers worldwide.
ircII was released 1989 by Michael Sandrof.
In July 1990, IRC averaged at 12 users on 38 servers.
In 1990, a new network was set up in order to develop a new version (2.6) of the ircd. The network named ChNet (about 25 servers and no users) existed a few months before disagreements among the programmers caused it to dissolve.


EFnet
In August 1990 the first major disagreement took place in the IRC world. The "A-net" (Anarchy net) included as server named eris.berkeley.edu. It was all open, required no passwords and had no limit on the number of connects. As Greg "wumpus" Lindahl explains: "it had a wildcard server line, so people were hooking up servers and nick-colliding everyone".
The "Eris Free network", EFnet, made the eris machine the first to be Q-lined (Q for quarantine) from IRC (wumpus' words again: "Eris refused to remove that line, so I formed EFnet. It wasn't much of a fight; I got all the hubs to join, and almost everyone else got carried along."). A-net was formed with the eris servers, EFnet was formed with the non-eris servers. History showed most servers and users went with EFnet. The name EFnet lived only shortly, as soon as ANet had died, the name EFnet became void too. There was one and only IRC left again.
TubNet was the next network to splinter off. It was created by a crowd of people in #hottub that grew tired of all the netsplits. It got 5 servers and around 100 users. It died again in September the same year.
One often-talked-about event in the history of IRC is the gulf war. In early 1991, live reports were available and more than 300 concurrent users were experienced for the first time.


Undernet
Another fork effort, the first that really made a big and lasting difference, was initiated by 'Wildthang' in USA October 1992 (it forked off the EFnet ircd version 2.8.10). It was meant to be just a test network to develop bots on but it quickly grew to a network "for friends and their friends". In Europe and Canada a separate new network was being worked on (by '_dl' and 'WIZZARD') and in December the french servers connected to the canadian ones, and in the end of the month, the .fr-.ca network was connected to the US one and the network that later came to be called "The Undernet" was born.
The "undernetters" wanted to take ircd further in an attempt to make it less bandwidth consumptive and to try to sort out the channel chaos (netsplits and takeovers) that EFnet started to suffer from. For the latter purpose, the Undernet implemented timestamps, new routing and offered the CService -- a program that allowed users to register channels and then attempted to protect them from troublemakers. (More or less a global defense bot.) The very first server list presented, from Febrary 15th 1993, includes servers from USA, Canada, France, Kroatia and Japan. On August 15th, the new user count record was set to 57 users.


RFC
In May 1993, the Request For Comments 1459, for the IRC protocol is out for the public. It has since been subject to many violations and extensions. More about that on other places.


Dalnet
During the summer (some sources mention July) 1994, the Undernet is itself forked. This time, the new Network is called Dalnet (named after its founder: dalvenjah), and they formed the new network for better user service and even more user and channel protections. One of the more significant changes in Dalnet already from the beginning is their use of longer nicknames (the original ircd limit being 9 letters). Dalnet ircd modifications were made by Alexei "Lefler" Kosut.
Dalnet was thus based on the undernet ircd server, although the dalnet pioneers were EFnet abandoners. According to James Ng the initial dalnet people were "ops in #StarTrek sick from the constant splits/lags/takeovers/etc".
Dalnet quickly offered global WallOps (IRCop messages that can be seen by users who are +w (/mode NickName +w)), longer nicknames, Q:Lined nicknames (nicknames that cannot be used i.e. ChanServ, IRCop, NickServ, etc.), global K:Lines (ban of one person or an entire domain from a server or the entire network), IRCop only communications: GlobOps, +H mode showing that an IRCop is a "helpop" etc.
Much of Dalnet's new functions were written in early 1995 by Brian "Morpher" Smith and allow users to own nicknames, channels, send memos and more.


oz.org
Undernet split (again) in March 1996 when the sole Australian server delinked from Undernet because of difficulties with the connection across the TransPacific Australian/United States network link. The first few months of oz.org's existance were primarily a trial delink from the Undernet because of the inability to maintain a link during peak usage hours. One of the two designers (chaos and seks) of the orginal Undernet X and W chanserv was Australian, and the same code was used for Oz.org's Z (the name of the chanserv). In June 2001, ozorg boasted peak usages of 4,000 simultaneous users.


IRCnet
In July 1996, after months of flame wars and discussions on the mailing list, there was yet another split due to disagreement in how the development of the ircd should evolve. Most notably, the "european" (most of those servers were in europe) side that later named itself IRCnet argued for nick and channel delays, where the EFnet side argued for timestamps. Most (not all) of the IRCnet servers were in Europe, while most of the EFnet server were in the US. This event is also known as "The Great Split" in many IRC societies. EFnet has since (as of August 1998) grown and passed the number of users it had then. In the autumn year 2000, EFnet has some 50,000 users and IRCnet 70,000.


Freenode - Open Projects Network
Yet another IRC network that opened its doors in 1998 named the Open Projects Network, and had about 100 users and less than 20 channels that year. In late 2001 it had grown to nearly 4,000 users and over 1,300 channels. The OPN uses the Dancer IRCD server, after having been using ircu the intial few years.
This network was later renamed to Freenode.


Other Networks
Of course, while internet is booming so does IRC. There exists hundreds of independent IRC networks today (like amiganet, linuxnet, galaxynet, bestnet, NewNet, AnotherNet, ChatNet, UpperNet, ZAnet, X-Net, GammaNet, SuperChat, IceNet, RedBrasil, GR-Net, AlphaStar, SorceryNet etc), but luckily there is "only" four of the main ones (this was the reality back in 1998) that keep develop their own version of the ircd server software.
Of course, as of 2002, lots of other networks have popped up and now numerous of them are developing their own customized versions of the IRC protocol.


Future
IETF-IRCUP was an initiative started in January 1998, to gather all the flavours of IRC servers to document a new RFC and possibly set a new standard for all networks to commit to. That project died.
CTCP/2 was an attempt, started in 1997 by Bjorn Reese, to develop and standardize the Client To Client Protocol that was never in the RFC. Clients have been known to extend and modify the original CTCP protocol without allowing non-compliant clients to filter the new codes. CTCP/2 was meant to define how codes and perhaps more important new codes should be introduced in order to let old clients remain functional. It was also meant to address the IPv6 problems the DCC intiating sequence has. The CTCP/2 project has died as well.
We'll just have to wait and see what the future of IRC has to show...


 
Design by Wordpress Theme | Bloggerized by Free Blogger Templates | coupon codes