Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Amateur Radio Interest  <--  <--- Return to Home Page
   Networked Database  Amateur Radio Interest   [770 / 900] RSS
 From   To   Subject   Date/Time 
Message   Sean Dennis    All   My pet peeves   May 1, 2019
 7:11 PM *  

Hello All,

I though you all might get a kick out of this.  This is a static page on my 
blog...

===Cut===
- Stateside stations asking for SASEs for paper QSL cards: It is a pet peeve 
of mine to see stateside hams insisting on you paying for their hobby even 
though they have this expensive ham radio equipment on their desk but they 
won't spring for a fourty-nine cent stamp.  I figure that if you're going to 
have paper QSL cards, you should be prepared to spend the few cents to send it 
off in the States.  DX stations, however, are different and I can understand 
that their country's postal service postage isn't cheap like here in the 
States. I'll happily confirm a DX QSO with LotW for DXCC if a paper QSL card 
isn't possible.

- Using the term "73" incorrectly: "73" means "best regards".  Using "very 73" 
is fine.  Using "73s" is not.  You don't say "best regardses", do you?  So you 
shouldn't use "73s".   There is also "best 73s".  "Best best regardses" 
doesn't make any sense . . . but you should.

- Using "Q codes" or "10 codes" on a VHF/UHF repeater: As with the above "73", 
you don't go around saying to your boss, "I gotta get to the home QTH to go 
10-100!"  "Q codes" are acceptable on HF with SSB and CW (with the possibility 
of computer digital modes but that's another story), but when using nearly 
crystal-clear FM, you can use proper English and speak like a functioning 
human being.

- Saying "for ID" when using your callsign on a repeater: For God's sake, 
people, your callsign IS your ID!  Just giving your callsign identifies 
yourself.  When you say "for ID", you sound like an idiot.  Please, only your 
callsign.  You don't hear the repeater add "for ID" after it identifies 
itself, do you?

- Using only the suffix of your callsign to identify yourself while working a 
DX pileup: That's not only really impolite, it's illegal in the US.  Many a 
ham in the US really should read the DX Code of Conduct and live by it.

- Using an amplifier to make a short-distance contact: The US rules state that 
an amateur radio operator should use the minimum power necessary to maintain a 
contact.  Sometimes, I wonder if these guys are making up for other 
shortcomings in their life by doing this.
===Cut===

Later,
Sean

... WinErr 00E: Window open - Do not look inside
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Amateur Radio Interest  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0798 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_05an7m1am6874t9oki22tqbae6, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_05an7m1am6874t9oki22tqbae6, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_05an7m1am6874t9oki22tqbae6, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0