CaptainGoodnight
Golden Member
- Oct 13, 2000
- 1,427
- 30
- 91
Originally posted by: Jero
Originally posted by: dquan97
anyone got a copy of that pic?
It's on my server. And it's staying there.
Where is that?
Originally posted by: Jero
Originally posted by: dquan97
anyone got a copy of that pic?
It's on my server. And it's staying there.
Originally posted by: CaptainGoodnight
Originally posted by: Jero
Originally posted by: dquan97
anyone got a copy of that pic?
It's on my server. And it's staying there.
Where is that?![]()
Originally posted by: Jero
Originally posted by: CaptainGoodnight
Originally posted by: Jero
Originally posted by: dquan97
anyone got a copy of that pic?
It's on my server. And it's staying there.
Where is that?![]()
On my linux box at home. Good luck getting through the security system =)
Originally posted by: jagec
Originally posted by: Jero
Originally posted by: CaptainGoodnight
Originally posted by: Jero
Originally posted by: dquan97
anyone got a copy of that pic?
It's on my server. And it's staying there.
Where is that?![]()
On my linux box at home. Good luck getting through the security system =)
I WANT TO RAPE YOUR FIREWALL AND FONDLE YOUR LINUCKS!!!1!
Originally posted by: Jero
I'm sorry but you can only rape a windows based firewall.
Please try again.
Originally posted by: jagec
Originally posted by: Jero
I'm sorry but you can only rape a windows based firewall.
Please try again.
now now, linux isn't 100% secure...just a lot more secure than windows when set up correctly.
Originally posted by: Jero
now now, linux isn't 100% secure...just a lot more secure than windows when set up correctly.
Originally posted by: jagec
Originally posted by: Jero
now now, linux isn't 100% secure...just a lot more secure than windows when set up correctly.
if your a competent system admin then it can be very secure
I only have a few ports open for select applications and make sure my open source software is constantly up to date to get rid of any potential security vulnerabilities.
Originally posted by: Jero
Originally posted by: jagec
Oh, of course. But I'm sure if all of anandtech contributed their CPU cycles for a brute-force password cracker...![]()
then all I would do is ssh to my box
su to root
shutdown -h 1
Goodbye trouble![]()
Originally posted by: jagec
Originally posted by: Jero
Originally posted by: jagec
Oh, of course. But I'm sure if all of anandtech contributed their CPU cycles for a brute-force password cracker...![]()
then all I would do is ssh to my box
su to root
shutdown -h 1
Goodbye trouble![]()
Spoilsport.
Originally posted by: TechnoPro
Back in the day, AT&T bought out MediaOne. In early 2002, the e-mail address transition from @mediaone.net to @attbi.com was set to occur.
Customers recieved self-help instructions on how to create the new addresses. It was not a given that if you had joesmith@mediaone.net you would by default get joesmith@attbi.com. So customers went to a website that gave instructions on setting up the new account, having mail forwarded, etc.
It was the forwarding part that confirmed my suspicions that people are stupid.
I was getting a deluge of calls that e-mails sent to the old @mediaone.net were NOT being forwarded, in fact they were being returned as undeliverable. My first suspicion was an operational glitch at AT&T. Ruled that out with a phone call.
Turns out, on the web page that let the user forward e-mails, the instructions were written something like this:
Enter the e-mail address(es) that you would like your MediaOne e-mails forwarded to. Type them in the text box like this: address1, address2, address3, etc.
...
People were typing in the word 'address1' as the address to have mail forwarded to.
The result being a returned e-mail like this:
This Message was undeliverable due to the following reason:
The following destination addresses were unknown (please check the addresses and re-mail the message):
SMTP <address1>
Please reply to <postmaster@mediaone.net>
if you feel this message to be in error.
Very hard to diplomatically tell people the error of their ways in a case like this.
Originally posted by: SagaLore
Originally posted by: TechnoPro
Back in the day, AT&T bought out MediaOne. In early 2002, the e-mail address transition from @mediaone.net to @attbi.com was set to occur.
Customers recieved self-help instructions on how to create the new addresses. It was not a given that if you had joesmith@mediaone.net you would by default get joesmith@attbi.com. So customers went to a website that gave instructions on setting up the new account, having mail forwarded, etc.
It was the forwarding part that confirmed my suspicions that people are stupid.
I was getting a deluge of calls that e-mails sent to the old @mediaone.net were NOT being forwarded, in fact they were being returned as undeliverable. My first suspicion was an operational glitch at AT&T. Ruled that out with a phone call.
Turns out, on the web page that let the user forward e-mails, the instructions were written something like this:
Enter the e-mail address(es) that you would like your MediaOne e-mails forwarded to. Type them in the text box like this: address1, address2, address3, etc.
...
People were typing in the word 'address1' as the address to have mail forwarded to.
The result being a returned e-mail like this:
This Message was undeliverable due to the following reason:
The following destination addresses were unknown (please check the addresses and re-mail the message):
SMTP <address1>
Please reply to <postmaster@mediaone.net>
if you feel this message to be in error.
Very hard to diplomatically tell people the error of their ways in a case like this.
Why didn't AT&T automate this process?![]()
Originally posted by: sm8000
My co-worker just had a call from some university's research lab. They had a powerful electron microscope lab (million dollar plus) being run off an old system running Windows 95. The system crashed, and they needed drivers for its TNT2.
Originally posted by: TechnoPro
Originally posted by: SagaLore
Originally posted by: TechnoPro
Back in the day, AT&T bought out MediaOne. In early 2002, the e-mail address transition from @mediaone.net to @attbi.com was set to occur.
Customers recieved self-help instructions on how to create the new addresses. It was not a given that if you had joesmith@mediaone.net you would by default get joesmith@attbi.com. So customers went to a website that gave instructions on setting up the new account, having mail forwarded, etc.
It was the forwarding part that confirmed my suspicions that people are stupid.
I was getting a deluge of calls that e-mails sent to the old @mediaone.net were NOT being forwarded, in fact they were being returned as undeliverable. My first suspicion was an operational glitch at AT&T. Ruled that out with a phone call.
Turns out, on the web page that let the user forward e-mails, the instructions were written something like this:
Enter the e-mail address(es) that you would like your MediaOne e-mails forwarded to. Type them in the text box like this: address1, address2, address3, etc.
...
People were typing in the word 'address1' as the address to have mail forwarded to.
The result being a returned e-mail like this:
This Message was undeliverable due to the following reason:
The following destination addresses were unknown (please check the addresses and re-mail the message):
SMTP <address1>
Please reply to <postmaster@mediaone.net>
if you feel this message to be in error.
Very hard to diplomatically tell people the error of their ways in a case like this.
Why didn't AT&T automate this process?![]()
Automate it how?
The user name assignment process could not be automated easily because user names coming from MediaOne may have already been taken by existing AT&T Broadband customers. As such, a manual user name change and verification was warranted. Mind you, most people were lucky and kept their original user names, but some had to change.
The forwarding was designed so that once you updated your e-mail client with the new ATTBI settings, e-mails addressed to MediaOne could be, at the customer's option, forwarded to other accounts during the final transition phase.
The underlying problem was that the web page designed to handle this was horribly designed. Very bad user interface, unclear writing, etc. Would have saved a lot of headache had it been well designed.
Originally posted by: PlatinumGold
wouldn't it have been easier on everyone just to maintain the @mediaone ??
Originally posted by: MisterJackson
Saw a guy who had tried to wedge a P4 processor into his Socket A board.
Had someone ask me what cable was needed to plug his Play Station 2 into the PC's PS2 port
And for some reason most people can never say "USB", it's always "UBS, UB2, etc..." or some variation. I've given up on correcting those.
Originally posted by: PlatinumGold
wouldn't it have been easier on everyone just to maintain the @mediaone ??
Originally posted by: TechnoPro
Originally posted by: PlatinumGold
wouldn't it have been easier on everyone just to maintain the @mediaone ??
Easier from a technical standpoint, sure. But from a marketing and brand identity perspective, no. AT&T felt the need to strengthen their branding, so to them, inconveniencing the customer was acceptable.
Also, the switch could have been a condition of the sale, stipulated by one or both parties.
I wish I had taken screen shots of that transfer web page. It was an abomination of design and user-friendliness.
hoping a month and a half later, he changes his mind....Originally posted by: sm8000
Sorry guys, conscience attack.
Besides, it's at home. I won't even see it until I get home from work tonight.