OPEN STANDARDS, NOT OPEN SOURCE

OPEN STANDARDS, NOT OPEN SOURCE

>>40
If standards do not effectively fall into marketing, government or safety, then what else can they be for you? In some way it ends up being marketing in the goal to self-enrich whether in money or ego.

If I'm making a video player with streaming ability, I'll eventually have to unveil it which is a fairly simple uncalculated act of promotion. For me to promote this video player it will need to implement things people want from it (even if its open source because nobody will do this for you anyway, people only do the bidding of famous people), which is already inherently DIY marketing. To get this done, I'll pick up on any BSD libs that I can, after that, I'll have to code up the rest, I'll find some RFCs and I'll find some standards documents in some alleyway 20 year old FTP site forgotten at some university.

I'm driven to find these things because in the end I want to make the first open source^TM streaming^TM music and video player with WebM^TM support which I support fully as I'm against the patents of the man^TM on the much anticipated Zapple iJuju^TM tablet and be showered with praise and donated money and become the new Lolzerberg.

>>39
There's one great thing about XMPP. The only implementation you'll find in the wild is ejabberd. It doesn't go down.

Also, a fair amount of the basics of the internet is held together by government or `government', that is, IANA / ARIN and the other RIRs / ICANN (aka department of commerce). ARPANET, again government, is responsible for a packet formalism of communication on the wire, the basic protocols were made from DARPA funding. Government is good at `standards', because its a bit of a technological tyranny. Everything of value on the link and transport layer is mainly government legacy. Everything below that is free market, everything above is free market and thus marketing driven.

The Web beat Gopher because Gopher was shit, but it wasn't because TBL just made a protocol, TBL made a web browser/editor hybrid and web server, it caught on at CERN and later CERN released libwww (library instead of standard right there!) and CERN HTTPd. And then libwww was used to implement various browsers like Mosaic, and the rest is history.

jews

>>43

I have no idea what you're blabbering about. IETF, like all good standards, is about *interoperability*. Not about marketing. Not about government. Not about safety. Interoperability.

>>45
"internet was made and legislated by Al Gore tirelessly working at a PDP-11"

>>46

High Performance Computing and Communication Act of 1991

>>38

RFC 1459 - Internet Relay Chat

Suck my cock, dude.