Usenet servers use static routing for their store-and-forward and thus taking out the most central hubs would create "islands" until the routing was changed to target servers that were still up.
True, but it's doubtful that any disaster or organization could take out most central hubs at the same time. Usenet administrators can adapt as needed. If a major node went down, providers could usually switch over to another node.
In the event of such an outage, we just won't have that instant gratification that everyone expects these days.
Usenet and IRC existed fine with these sorts of outages, and they were pretty common. For Usenet, it simply meant that messages might take a couple days to arrive, instead of a few minutes. Netsplits haven't killed of IRC, have they? We can deal with it, but maybe we just need to change our expectations.
In the 1990s, it wasn't uncommon for the NNTP/UUCP exchanges to only take place after hours. I remember a time when UC Berkeley, Stanford, UC Santa Cruz, the Well (Based in the SF Bay Area), etc. could all communicate with one another late at night, but communication with Organizations on the East Coast would be delayed for a day.
Usenet is one system. If i post something to one server, it propegates outward to the rest of them.
If you shut down usenet, you shut down usenet.....there is not "oh, well...lolz it will pop back up somewhere!"
Could you elaborate?
Usenet consists of thousands of nodes. If you shut down one usenet node, even a large one, the remaining nodes will continue to function. Affected nodes can eventually route their messages through connecting nodes. Messages can still be sent from one node, routed through the connecting nodes, and received by the remaining nodes.
Shutting down usenet would involve shutting down a majority of the nodes, which isn't practical.
Re:Wow. I'm about to comment on. . .
on
SCO Layoffs Begin
·
· Score: 1
I find it amazing that such a small group of people, 123, could cause so much trouble for so many years.
The lawsuits were mostly handled by the SCO group's legal team, which was probably run by an external lawfirm working on contact.
it proves you're one of the boys
You're speaking about certain executives within the SCO group.
Outside of the executive team, SCO Employees mostly maintained the legacy SCO products (Unixware, OpenServer), and probably had very little to do with the 'trouble'. Their mistake was not leaving SCO soon enough.
With the vindictiveness of your post, can you see why some of the employees want to remain anonymous? What, are you hoping to prevent the receptionist from getting a new job?
I say 'DNS name' out of habit, because I used to work with people who used the term 'domain' to refer to a different kind of computer system, and 'Domain name' just caused confusion.
Start? They never stopped.
on
SCO Layoffs Begin
·
· Score: 4, Informative
This isn't the beginning of the layoffs.
Not too long ago, the SCO Group (Caldera) had hundreds of employees in several offices in the US and overseas. The SCO Group has had many layoffs since 2001. Someone even went to the trouble of graphing the history:
AOL just needs to promote itself as a "Web 2.0" company.
AOL Executive #1: Hey, we came out with AOL 2.0 in 1995, wayyyy before Web 2.0. Didn't you receive the CD? If not, do you want one? Or do you want another one? I'll slip a couple in the mail just in case you need one.
AOL Executive #2: Me too.
---
In all seriousness, AOL announced their Web 2.0 initiative in late 2006: http://dev.aol.com/node/86 . Although, their blog is almost a year out of date, despite the fact that he says "soon!"
I'll be writing another post about Web 2.0 and AOL's new openness soon!
Submitted by kevinfarnham1 on November 7, 2006 - 8:25pm.
This is the first time that Facebook users can communicate with one another from directly within the Facebook application.
This is great! Someday, maybe this tool will allow Facebook users to communicate with users on other websites. Imagine the possibilities!
Right now, the web is fragmented into many different isolated islands. Each service requires a different registration, uses different protocols, and are generally incompatible with one another. It's difficult for UserA on Facebook to communicate with UserB on MySpace. Users on AOL Instant Messenger can't talk to users on Yahoo Instant Messenger!
My parents don't use Facebook, AIM or any other social networking technology. Let's think of a solution for them too!
I propose we connect all of these large websites and services, possibly using a series of interconnected networks, well defined common protocols. I think we should call it 'The Interweb'.
however it is a native American reservation so I'm not sure whether you need some kind of permission from the locals to go there by yourself or not.,/i>
The Navajo Nation has it's own Parks and Recreation department, with some special rules. Check in with the Visitors Center. The local tour companies in Kayenta may also provide information also:
Start at Kayenta Arizona, which is the largest town in the Navajo Nation, and functions as a regional capitol, of sort.
Bring a good car, several maps, one map which shows BLM Land. camping supplies, plenty of gas, food and water. You'll be in the middle of nowhere, so always make sure you have enough gas.
Head North on Highway 261, go through Monument Valley, head towards Natural Bridges National Monument. Monument Valley is one of the most famous places in the world, yet you can stand on the side of the road without seeing anyone for 30 minutes.
Drive 4000-feet up the side of a cliff on a crazy curvy old Uranium Road. This area is called the 'Gooseneck State Park. When you get to the top, stop and look back south over the valley--- you can see quite far.
Head north until you leave Gooseneck. This is BLM land. You can drive on any road, find a nice spot and camp. Wait until the nighttime, and check out the stars.
This is one of the most remote places in the US-- millions of stars. I remember it being so dark, and the stars were so bright that I could see faint shadows from the starlight.
I volunteered at the ACCRC a couple of days during the Suse 9.2 days.
One day I went out on a nice 5-hour bike ride up and down the shoreline trail. I stopped by the ACCRC at 5:00PM to volunteer for an install fest. In one evening we churned out 200 PCs with 5 people, SuSE autoyast and some shipping-plastic wrap.
I helped to carry the fridge up three flights of narrow stairs. Were you there for that?
Clearly you mean rec.aquaria ;)
Without rec.*, the sci.* folks would never would have had a moment's piece.
but rather a bottle of good tequilla
Isn't that a self perpetuating swear jar.
Swear -> Swear Jar -> tequilla -> Margaritas -> Swear -> Swear Jar -> tequilla -> Margaritas
Usenet servers use static routing for their store-and-forward and thus taking out the most central hubs would create "islands" until the routing was changed to target servers that were still up.
True, but it's doubtful that any disaster or organization could take out most central hubs at the same time. Usenet administrators can adapt as needed. If a major node went down, providers could usually switch over to another node.
In the event of such an outage, we just won't have that instant gratification that everyone expects these days.
Usenet and IRC existed fine with these sorts of outages, and they were pretty common. For Usenet, it simply meant that messages might take a couple days to arrive, instead of a few minutes. Netsplits haven't killed of IRC, have they? We can deal with it, but maybe we just need to change our expectations.
In the 1990s, it wasn't uncommon for the NNTP/UUCP exchanges to only take place after hours. I remember a time when UC Berkeley, Stanford, UC Santa Cruz, the Well (Based in the SF Bay Area), etc. could all communicate with one another late at night, but communication with Organizations on the East Coast would be delayed for a day.
Usenet is one system. If i post something to one server, it propegates outward to the rest of them.
If you shut down usenet, you shut down usenet.....there is not "oh, well...lolz it will pop back up somewhere!"
Could you elaborate?
Usenet consists of thousands of nodes. If you shut down one usenet node, even a large one, the remaining nodes will continue to function. Affected nodes can eventually route their messages through connecting nodes. Messages can still be sent from one node, routed through the connecting nodes, and received by the remaining nodes.
Shutting down usenet would involve shutting down a majority of the nodes, which isn't practical.
We have ways of finding your posts.
I find it amazing that such a small group of people, 123, could cause so much trouble for so many years.
The lawsuits were mostly handled by the SCO group's legal team, which was probably run by an external lawfirm working on contact.
it proves you're one of the boys
You're speaking about certain executives within the SCO group.
Outside of the executive team, SCO Employees mostly maintained the legacy SCO products (Unixware, OpenServer), and probably had very little to do with the 'trouble'. Their mistake was not leaving SCO soon enough.
With the vindictiveness of your post, can you see why some of the employees want to remain anonymous? What, are you hoping to prevent the receptionist from getting a new job?
I think "domain name" might be a little more accurate.
;)
ATM Machine. Here we go with the semantic arguments
If we can have a 'DNS name server', a DNS name space and a Reserved Top Level DNS Names, why can't we say 'DNS name'?
I say 'DNS name' out of habit, because I used to work with people who used the term 'domain' to refer to a different kind of computer system, and 'Domain name' just caused confusion.
This isn't the beginning of the layoffs.
Not too long ago, the SCO Group (Caldera) had hundreds of employees in several offices in the US and overseas. The SCO Group has had many layoffs since 2001. Someone even went to the trouble of graphing the history:
http://en.wikipedia.org/wiki/Image:SCO-2001-2006-headcount-by-department.jpg
http://en.wikipedia.org/wiki/SCO_Group#Charts
Don't confuse 'Usenet' with usenet.com. 'Usenet' is an internet-wide discussion system, with thousands of usenet nodes and of no central control.
Usenet.com provides paid access to Usenet newsgroups, and happened to land a nice DNS name.
AOL just needs to promote itself as a "Web 2.0" company.
AOL Executive #1: Hey, we came out with AOL 2.0 in 1995, wayyyy before Web 2.0. Didn't you receive the CD? If not, do you want one? Or do you want another one? I'll slip a couple in the mail just in case you need one.
AOL Executive #2: Me too.
---
In all seriousness, AOL announced their Web 2.0 initiative in late 2006: http://dev.aol.com/node/86 . Although, their blog is almost a year out of date, despite the fact that he says "soon!"
I'll be writing another post about Web 2.0 and AOL's new openness soon!
Submitted by kevinfarnham1 on November 7, 2006 - 8:25pm.
Shaaaaaaaaaaaun
Why do we keep putting crap in phones?
Really, we should stop calling them phones. They are becoming another beast entirely.
How about 'Tricorder'.
Bah. Moon elves-- they take your cheese, work for 28 days, and quit.
Personally, I think the Once-in-a-Blue-Moon Elves are even more useful. They only switch jobs every 2.72 years. But they are hard to find.
"Hey, let's have dinner tonight"
(Robotic Google voice) "May we suggest
Reservations at Chez Panisse without waiting 6 months? Unheard of.
This is the first time that Facebook users can communicate with one another from directly within the Facebook application.
This is great! Someday, maybe this tool will allow Facebook users to communicate with users on other websites. Imagine the possibilities!
Right now, the web is fragmented into many different isolated islands. Each service requires a different registration, uses different protocols, and are generally incompatible with one another. It's difficult for UserA on Facebook to communicate with UserB on MySpace. Users on AOL Instant Messenger can't talk to users on Yahoo Instant Messenger!
My parents don't use Facebook, AIM or any other social networking technology. Let's think of a solution for them too!
I propose we connect all of these large websites and services, possibly using a series of interconnected networks, well defined common protocols. I think we should call it 'The Interweb'.
Silly man. Everyone knows that Emacs is an operating system. It even runs VI.
Is Stairsteps the same as Grand Staircase National Monument?
You're ahead of your time.
however it is a native American reservation so I'm not sure whether you need some kind of permission from the locals to go there by yourself or not.,/i>
The Navajo Nation has it's own Parks and Recreation department, with some special rules. Check in with the Visitors Center. The local tour companies in Kayenta may also provide information also:
http://www.navajonationparks.org/htm/monumentvalley.htm
http://www.kayentatownship.com/ktctourist2003.html
Start at Kayenta Arizona, which is the largest town in the Navajo Nation, and functions as a regional capitol, of sort.
Bring a good car, several maps, one map which shows BLM Land. camping supplies, plenty of gas, food and water. You'll be in the middle of nowhere, so always make sure you have enough gas.
Head North on Highway 261, go through Monument Valley, head towards Natural Bridges National Monument. Monument Valley is one of the most famous places in the world, yet you can stand on the side of the road without seeing anyone for 30 minutes.
Drive 4000-feet up the side of a cliff on a crazy curvy old Uranium Road. This area is called the 'Gooseneck State Park. When you get to the top, stop and look back south over the valley--- you can see quite far.
Head north until you leave Gooseneck. This is BLM land. You can drive on any road, find a nice spot and camp. Wait until the nighttime, and check out the stars.
This is one of the most remote places in the US-- millions of stars. I remember it being so dark, and the stars were so bright that I could see faint shadows from the starlight.
I volunteered at the ACCRC a couple of days during the Suse 9.2 days.
One day I went out on a nice 5-hour bike ride up and down the shoreline trail. I stopped by the ACCRC at 5:00PM to volunteer for an install fest. In one evening we churned out 200 PCs with 5 people, SuSE autoyast and some shipping-plastic wrap.
I helped to carry the fridge up three flights of narrow stairs. Were you there for that?
Nice irony. Was that van powered by biodiesel?
I imagined a San Francisco bureaucrat, as opposed to a Berkeley bureaucrat,
This threat came from a State agency, who just happen to have an office in Berkeley--- not a Berkeley agency.
Sadly, I'm not sure if the City of Berkeley is doing anything to help the ACCRC.
Interestingly, James is asking voters to vote for the other folks:
"Vote for the gorillas. 25 grand and fame that id probably just piss away anyway is not worth a specie.".
Nice honest opinion from the Hero.
Hey, I'll be happy to take those 'bricks' off your hands. And I'll do it for FREE.
And now the video has been removed:
This video has been removed due to terms of use violation.
Would YOU volunteer for the Klingons? I thought not.
And plus, a translator doesn't achieve much glory and honor, do they.