I QUIT

NOT EURO” Choire Sicha will hereby be pimped, as he has contributed to the dead-tree book Never Threaten to Eat Your Co-Workers along with several Usual and Unusual Suspects.

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.23 10:05. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/23/choirepimping/

And speaking of relay services: If you hack Sprint’s astonishingly-noncompliant site, you can eventually watch ASL videos explaining the IP-relay process. It’s a rare case of subtitled online video: There’s no speech, only sign.

Now, what happens if you’re a woman and want a female relay operator? Let the nebbishy pipsqueak male actor fill you in!

‘When the operator receives the call, they will place a female agent on the call to be consistent with your gender’

And as a public service, here’s the full list of QuickTime videos, including one they don’t want you to see.

  1. Introduction
  2. Dialing Instruction
  3. Number to Dial
  4. Language Preference
  5. Connect to Relay Operator
  6. Connect to Customer Service
  7. Copy and Paste
  8. ASL Emoticons
  9. Background Color
  10. Clear
  11. Disconnect
  12. GA, SK and PLS HOLD
  13. Print
  14. Save
  15. Text Size and Color

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.23 08:00. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/23/relay-grrrlz/

An advantage of WordPress: Automatic syndication. What’s your poison?

  1. RSS 2.0
  2. RSS 0.92
  3. Atom 0.3
  4. XML-RPC pingback

Do with these what you will. They are also discoverable through the head element, if your device can read that.

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.22 19:43. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/22/rss-links/

As has been documented in a few places –

– our dear Nigerian friends are using the Web interfaces to relay services to call bookstores, computer retailers, and the like, and clumsily attempt to place fraudulent orders. (See the FCC homepage on relays, which is curiously underreported online.)

These IP relay services, as by MCI, Sprint, and AT&T, are not mandated by any law anywhere, let alone the United States, the only country I know of that has them. They’re entirely optional. They permit scammers to make “TTY”-to-voice calls within the United States at zero cost. If the scammers wanted to use the relay service the conventional way, they’d have to place an overseas call, and that would eat into profit margins.

I’ve used the IP relay services here and there. Usually they won’t let me call Canada. One operator admitted her system did not differentiate between calls originating from TTYs or from the Web. Well, that’s your first clue right there: Set a flag on every operator’s terminal.

But more importantly, this entire fraud problem could be eliminated overnight by shutting down the IP relay services, which would cause no inconvenience whatsoever to nearly every TTY user. It’s already a toll-free call to contact the relay service (nearly everywhere in the U.S., you just dial 711), and every legitimate user has a TTY already or can get one easily. You can use computer software, even on Macs. We don’t need IP relay.

I can imagine a rare case in which a deaf person with a dexterity impairment finds it easier to type on computer than on a TTY, but that would remain true with TTY software. In fact, it would be more reliable in that case. IP relay services are Web applications. Apart from violating the User Agent Accessibility Guidelines, they’re slow and buggy on every system I’ve used. The AT&T phone kiosks in Newark airport reliably crash 30 seconds into any call – and those are provided as the only way to make a TTY call at the airport. I can get some IP relays to work sometimes in IE and Safari, but never in Mozilla.

IP relay is a nice idea. A variation of same – video relaying, using sign language – is something I experienced firsthand a month or so ago, and it seems to work OK. But the pool has been sullied. We do not need IP relay to use the damned phone.

If that seems drastic, do what the Australians do and set up a registration system – for IP relay only. (I thought the British had a similar registration system, but both countries eliminated nearly all such registrations. I called them up to ask.)


Curious factoid: After reading yet another reiteration of the following shibboleth, I simply could not get EuroCory to accept that a chief function of a relay service is not, in fact, to enable a deaf person to “order a pizza.” Its chief function is to enable deaf, hard-of-hearing, and speech-impaired people to call anyone they want, and vice-versa, for any purpose for which voice calls can be used. Yes, that does indeed include phone sex in some places. (Others either prudishly prevent such calls or cannot bill them, as via 900 or 0876 numbers.) There is no killer app for relay services; relay services are the killer app.

In one example, some arsehole on the Captioning list defamed my commitment to improved captioning and accessibility. Wasn’t he surprised to find his TDD lighting up a few days later with me on the end demanding an apology, which I got. EuroCory dismissed this as an atypical use case. There is no typical use case – any more than there is such a thing for voice calls.

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.22 18:45. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/22/tty/

Bit o’ catching up to do.

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.22 17:31. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/22/b-links/

*** System shutdown message from [luke à mail.veldt.ca] ***
System going down at 16:30
Server is going down in 45 minutes.

It was indeed an exciting afternoon on March 24 as Master Luke euthanized the Veldt. We had a valiant run. We lived gloriously and by God we died gloriously. My esteemed colleague, who had hosted my sites for upwards of four years, will shortly be taken vigorously to dinner and thanked with extreme sanction.

One is now hosted by young Matt Müllenweg, a developer of WordPress, the content-management system all the hip kids are now starting to use. I’m neither hip nor a kid, but I’m glad to announce I have entered the 21st century: fawny.blog is no longer handrolled. (Neither is Axxlog, but that is old news.)

Yes, dear friends, that means:

  1. each posting can have its own page
  2. you need not load an entire month’s postings at a time because I failed to subdivide them into, say, weekly increments
  3. page anchors are largely done away with
  4. I’m using UTF-8 encoding, which simplifies typography
  5. categories and a functioning search engine (that will, of course, report search terms back to me for later publication)
  6. and, yes, ravening hordes, you finally get a goddamned RSS feed. You can get off my damned case

Certain layout features will continue to be improved, particularly the page footer. Also, anticipated additions are as follows:

  • Photographs
  • Blogroll: Yes, you finally may learn what sites I read (apart from the obvious response, “seemingly all of them”)
  • Better navigation, including morally-correct, semantic designer navbars
  • Possible declared WCAG AAA compliance, but this is dicey by definition

And wait till you see what Matt and I have up our sleeves for a future edition of WordPress. Let me put it to you this way: If you thought captions and both kinds of descriptions (long and audio) were too much of pain in the arse before, you’re about to be pleasantly surprised.

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.22 12:40. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/22/wordpressification/

This article is a placeholder for a test of Web standards.

The Nigerian TTY scam

As has been documented in a few places –

– our dear Nigerian friends are using the Web interfaces to relay services to call bookstores, computer retailers, and the like, and clumsily attempt to place fraudulent orders. (See the FCC homepage on relays, which is curiously underreported online.)

These IP relay services, as by MCI, Sprint, and AT&T, are not mandated by any law anywhere, let alone the United States, the only country I know of that has them. They’re entirely optional. They permit scammers to make “TTY”-to-voice calls within the United States at zero cost. If the scammers wanted to use the relay service the conventional way, they’d have to place an overseas call, and that would eat into profit margins.

I’ve used the IP relay services here and there. Usually they won’t let me call Canada. One operator admitted her system did not differentiate between calls originating from TTYs or from the Web. Well, that’s your first clue right there: Set a flag on every operator’s terminal.

But more importantly, this entire fraud problem could be eliminated overnight by shutting down the IP relay services, which would cause no inconvenience whatsoever to nearly every TTY user. It’s already a toll-free call to contact the relay service (nearly everywhere in the U.S., you just dial 711), and every legitimate user has a TTY already or can get one easily. You can use computer software, even on Macs. We don’t need IP relay.

I can imagine a rare case in which a deaf person with a dexterity impairment finds it easier to type on computer than on a TTY, but that would remain true with TTY software. In fact, it would be more reliable in that case. IP relay services are Web applications. Apart from violating the User Agent Accessibility Guidelines, they’re slow and buggy on every system I’ve used. The AT&T phone kiosks in Newark airport reliably crash 30 seconds into any call – and those are provided as the only way to make a TTY call at the airport. I can get some IP relays to work sometimes in IE and Safari, but never in Mozilla.

IP relay is a nice idea. A variation of same – video relaying, using sign language – is something I experienced firsthand a month or so ago, and it seems to work OK. But the pool has been sullied. We do not need IP relay to use the damned phone.

If that seems drastic, do what the Australians do and set up a registration system – for IP relay only. (I thought the British had a similar registration system, but both countries eliminated nearly all such registrations. I called them up to ask.)


Curious factoid: After reading yet another reiteration of the following shibboleth, I simply could not get EuroCory to accept that a chief function of a relay service is not, in fact, to enable a deaf person to “order a pizza.” Its chief function is to enable deaf, hard-of-hearing, and speech-impaired people to call anyone they want, and vice-versa, for any purpose for which voice calls can be used. Yes, that does indeed include phone sex in some places. (Others either prudishly prevent such calls or cannot bill them, as via 900 or 0876 numbers.) There is no killer app for relay services; relay services are the killer app.

In one example, some arsehole on the Captioning list defamed my commitment to improved captioning and accessibility. Wasn’t he surprised to find his TDD lighting up a few days later with me on the end demanding an apology, which I got. EuroCory dismissed this as an atypical use case. There is no typical use case – any more than there is such a thing for voice calls.

You have reached the target

The foregoing posting appeared on Joe Clark’s personal Weblog on 2004.04.22 12:33. This presentation was designed for printing and omits components that make sense only onscreen. (If you are seeing this on a screen, then the page stylesheet was not loaded or not loaded properly.) The permanent link is:
https://blog.fawny.org/2004/04/22/not-tty/

← Later entries

(Values you enter are stored and may be published)

  

Information

None. I quit.

Copyright © 2004–2026