<center><font size=7 color=lightblue><b><span style="text-decoration:emboss">Loading Error. Please Reload.</span></b></font></center>



*Purpose*

Bouncing enables us to view the html code and url addresses that are used to create sigs for e-mail and posts. Remember, we bounce e-mail and posts; we source web pages.



Comment: Bouncing to learn how to code is fine. Bouncing to "snag" images that might have been manipulated and individualized by the sig owner is not. Ask permission!




*Four Methods*

1. "ALT+Z" METHOD



This and the XMP Method are fast and simple and need about the same number of key strokes. But this is the recommended method for important reasons:

  a. All urls in the bounced code are hyperlinks. Click them to see or hear the file.

  b. The bounced code is clean. There is no extraneous, foreign code added as there is with the XMP Method.


  • While viewing the email or post, hit "Send" on the keyboard

  • Click "Forward" on the slideup panel

  • Click "Remove signature"

  • Address the e-mail to yourself

  • Delete the subject line completely (cmd+delete key)

  • With the cursor in the now empty subject line, tap "Return" two times

  • With the cursor now in the body, type alt+z to make § (or alt+any key which produces a unique character)

  • With § in the body now, hit cmd+a (highlight) then cmd+x (cut)

  • Arrow up to the subject line and press cmd+v (paste) which puts § there (note that § then drops down into the message area)

  • Click "Send" and "Send message" on the slideup panel

Redlight! The email with the bounced code is in your inbox. If it does not arrive immediately, check the copy in "Sent Mail" to see the bounced code.


2. "XMP" METHOD


None of the urls are activated using this method, but the main problem is the superfluous WebTV code that is added throughout the bounced code block.

Table, font, and link tags, as well as romcache and spacer gifs - the underlying WebTV structural code for email and post pages - are everywhere within the bounced code, making it confusing exactly which code makes up the sig of interest.

Unless the alt+z method is disabled and we are desparate, this method is not recommended.


  • With the post or e-mail opened, hit "Send" on the keyboard

  • Hit "Forward" on the slideup panel

  • Click "Remove signature"

  • Address the e-mail to yourself

  • Arrow down to the body message area

  • Type <html><xmp>

  • Hit "Send" on the keyboard and "Send message" on the slideup panel


3. "TEXTAREA" METHOD


None of the urls in the bounced sig are hot links. And like the XMP Method the main drawback is the WebTV structural code that is included, making it confusing exactly which code makes up the sig.

But if not after the entire sig code...if just after a part of the code or a file url, this method is very useful and recommended.


  • With the post or e-mail opened, hit "Send" on the keyboard

  • Hit "Forward" on the slideup panel

  • Click "Remove signature"

  • Address the e-mail to yourself

  • Arrow down to the body message area and type or paste this code:

  • Hit "Send" on the keyboard and "Send message" on the slideup panel

  • The bounced code will be in a livebed textarea so that it is easy to CCP any part of it


4. "RETURN TO SENDER" METHOD


Email and posts with sigs are forwarded to some non-working email address. The forwards are returned undeliverable with the source code for the attached sigs revealed. The urls are clickable and there is no foreign code.

But the ethics of this method are questionable. It costs the host for every returned message and the loss mounts up when many people send. This method, therefore, is not recommended. In any case there is no known usable address; daemon@llnl.gov once worked but no longer does.

A WebTV user came up with a variation: fill up the mailbox at a web-based email server and bounce off that. Do not share the address with the entire WebTV public.


  • With the post or e-mail opened, hit "Send" on the keyboard

  • Hit "Forward" on the slideup panel

  • Click "Remove signature".

  • Address to a full web-based email server

  • Hit "Send" on the keyboard and "Send message" on the slideup panel

  • The forward will be returned as undeliverable and the code will be exposed



*Bounce Bugs*

Every once in a while, code bounced by the alt+z method arrives full of bugs...characters like 3D and A0 and = signs that were not put in the code by the writer. Click here to see a bounced sig that has the bugs.

There are usually only a few extra = signs. There can be more A0 characters and they are caused by using the alt+spacer bar when the code was written.

The most plentiful bugs are the 3D characters. They are caused by not putting quotation marks (" ") around every attribute, such as colors and sizes, and by spaces between such attributes, commands, and tags.

Before the bounced code can be used, all the bugs have to be deleted.


Code Cleaner Tool

If there are a great number of 3D and other bounce bugs to kill, this Bug Zapper tool can be a big help. Paste the bug infested code in the textarea and hit Clean Code and all bugs are zapped.

Manual Cleaning

The = signs and AO characters can be erased easily with the "Delete" key. To nuke the more abundant and scattered 3D bugs do this:

  • Copy and paste the code onto an email page or test bed.

  • Put 3D in the "Find" screen and click "Find on Page".

  • Click cmd+x to delete the first 3D and cmd+g to highlight the next one.

  • Then click cmd+x and cmd+g in rapid succession to nuke all of them.

  • A thumping sound when you hit cmd+x will indicate they are all gone.

  • Look for any gaps or spaces and close them up and the code is ready to be used.











Copyright © 1999 -   Ty_Tutes by Tyhart   All Rights Reserved