OpenBCM V1.07b11 (WIN32)

Packet Radio Mailbox

DBO595

[LAU JN59RM]

 Login: GAST





  

NL2ZTM > BPQ32    05.02.16 21:23l 152 Lines 6754 Bytes #999 (0) @ WW
BID : 10098_NL3ZTM
Read: GAST
Subj: Fwd: Re: [BPQ32] Re: Reject Lists
Path: DBO595<BX0RBL<FRA199<FRA485<FRB001<NL3BSM<NL3ZZE<NL3ZTM
Sent: 160205/0812Z 10098@NL3ZTM.ZH.NLD.EU BPQ1.4.65




-------- Doorgestuurd bericht --------
Onderwerp: 	Re: [BPQ32] Re: Reject Lists
Datum: 	Thu, 4 Feb 2016 15:15:13 -0600
Van: 	charles brabham n5pvl@uspacket.org [BPQ32] <BPQ32@yahoogroups.com>
Antwoord-naar: 	BPQ32@yahoogroups.com
Aan: 	BPQ32@yahoogroups.com



That is a very good point about a BBS SYSOP being in much the same 
position, with the same obligations as a repeater control operator. If 
you cannot put a halt to illegal or obnoxious operation on your system, 
then of course your license (and/or pocketbook) could easily wind up in 
jeopardy. It is also true that each of us as SYSOPs are owners of our 
systems and as long as we hew to the regulations, nobody is entitled to 
tell any of us how to run our systems.

Having said that, after more than three decades of Packet BBS operation, 
I can only remember one occasion where I had to reject by callsign, and 
it was over a legal issue PLUS obnoxious behavior. - The fellow was 
posting messages to my board that included inappropriate content that a 
bad word filter could not address, and ignored calls to cease and 
desist. With some reluctance, I wound up rejecting his call in the end.

Matthew appears to believe that non-ham BBS SYSOPs will cease and desist 
upon being asked to. My experience does not support that theory. In 
fact, an attempt to discuss the issue here brings on immediate threats 
of moderation even though no misbehavior resulted from it. The very 
topic of operating without non-ham links was judged to be taboo.

73 DE Charles, N5PVL


On 2/4/2016 12:31 PM, KA9LCF ka9lcf@yahoo.com [BPQ32] wrote:
>
> I am pretty certain that amateur radio operators who go through the 
> trouble, expense and exposure of setting up a BBS do not have 
> intentions of rejecting anyone but the most offensive or, reasonably 
> so, illegal operators.  And with exception of the illegal operators, 
> those that border on violations of decorum, would not be excluded 
> without the SYSOP having first sent warnings or at least a reply to 
> state the reason(s) for the exclusion outright.  I am also fairly 
> certain that once that exclusion was implemented that if the excluded 
> party were to offer explanation or assurance to discontinue the 
> offenses for the exclusion, the SYSOP would reverse it.
>
> Part of what has been missing from this discussion on rejection, is 
> for everyone to remember that we are all guests of someone's station.  
> What might be okay for one system administrator, might be taboo for 
> another; there is no rule that says any station must operate at the 
> behest of another.  Repeater trustees have the authority to issue a 
> cease and desist order to any amateur of the system under their 
> trust.  The FCC has been quite clear on this and will back up the 
> repeater owner/trustee.  The same applies to BBS administrators.
>
> Just my two bits (used to be 2 cents, but rates have gone up).
>
> 73,
> Bradd - KA9LCF
>
>
> This brings us all back to remembering to have fun and enjoy, but to 
> also be mindful of your content so as to assure it is in keeping with 
> Amateur Radio decorum.
>
> On 2/4/2016 10:25 AM, charles brabham n5pvl@uspacket.org [BPQ32] wrote:
>>
>> We hear platitudes about how BBS SYSOPs who do or do not want to 
>> participate in non-ham links ought to be able to do so. - The only 
>> way to effectively do so however, requires an ability to isolate one 
>> type of network (ham) from the other (non-ham).
>>
>> I suspect this is the real reason why there has ever been any 
>> resistance to an ability to reject by callsign.
>>
>> 73 DE Charles, N5PVL
>>
>>
>> On 2/4/2016 12:17 AM, ag6qo@yahoo.com [BPQ32] wrote:
>>>
>>> John,
>>> I believe that times have changed and that in order to make it 
>>> reasonable to prevent illegal use of our stations, whether intended 
>>> or not, this sort of user lockout is valuable.
>>>
>>> To be effective, it has to work not only for BPQmail, but for the 
>>> node as well. For RF connections as well as AXIP.
>>>
>>> While there will always be some power-drunk sysops who would abuse 
>>> such a feature, I believe they would not readily attract users anyway.
>>>
>>> I'd much rather see a community of enabled amateurs encouraging each 
>>> other to provide connections, without worry of breaking some law.
>>>
>>> By the way, I am finding the L4 logging very useful already.
>>> Thanks again.
>>> Joe
>>> AG6QO
>>>
>>
>> <https://www.avast.com/sig-email> 	This email has been sent from a 
>> virus-free computer protected by Avast.
>> www.avast.com <https://www.avast.com/sig-email>
>>
>

<https://www.avast.com/sig-email> 	This email has been sent from a 
virus-free computer protected by Avast.
www.avast.com <https://www.avast.com/sig-email>

__._,_.___
------------------------------------------------------------------------
Posted by: charles brabham <n5pvl@uspacket.org>
------------------------------------------------------------------------
Reply via web post 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/messages/18796;_ylc=X3oDMTJyMWZqZnNlBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxODc5NgRzZWMDZnRyBHNsawNycGx5BHN0aW1lAzE0NTQ2MjQwNjM-?act=reply&messageNum=18796> 
	• 	Reply to sender 
<mailto:n5pvl@uspacket.org?subject=Re%3A%20%5BBPQ32%5D%20Re%3A%20Reject%20Lists> 
	• 	Reply to group 
<mailto:BPQ32@yahoogroups.com?subject=Re%3A%20%5BBPQ32%5D%20Re%3A%20Reject%20Lists> 
	• 	Start a New Topic 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/newtopic;_ylc=X3oDMTJmOGg0c2EzBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNudHBjBHN0aW1lAzE0NTQ2MjQwNjM-> 
	• 	Messages in this topic 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/topics/18755;_ylc=X3oDMTM3bXFjazE3BF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxODc5NgRzZWMDZnRyBHNsawN2dHBjBHN0aW1lAzE0NTQ2MjQwNjMEdHBjSWQDMTg3NTU-> 
(29)

Visit Your Group 
<https://groups.yahoo.com/neo/groups/BPQ32/info;_ylc=X3oDMTJmMTBtcGNvBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzE0NTQ2MjQwNjM-> 


  * New Members
    <https://groups.yahoo.com/neo/groups/BPQ32/members/all;_ylc=X3oDMTJnMWQ3ZGY4BF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2bWJycwRzdGltZQMxNDU0NjI0MDYz>
    9

Yahoo! Groups 
<https://groups.yahoo.com/neo;_ylc=X3oDMTJlNjdpMmhzBF9TAzk3NDc2NTkwBGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTQ1NDYyNDA2Mw--> 

• Privacy <https://info.yahoo.com/privacy/us/yahoo/groups/details.html> 
• Unsubscribe 
<mailto:BPQ32-unsubscribe@yahoogroups.com?subject=Unsubscribe> • Terms 
of Use <https://info.yahoo.com/legal/us/yahoo/utos/terms/>

..

__,_._,___





Lese vorherige Mail | Lese naechste Mail


 26.03.2026 20:48:25lZurueck Nach oben