blinux list Re: Sonar GNU/Linux merges with Vinux

Linux for blind general discussion blinux-list at
Mon Apr 24 15:13:33 UTC 2017

It's not true that Red Hat did what they could do as quickly as they 
could do it. The spam problem went on for months before some of us 
finally started to make an issue of it. Even then it tooke a couple of 
weeks before anything was done. Secondly, they should have removed the 
spammer from the list instead of changing the list settings.  I got all 
kinds of pushback on my assertion that it was clearly a spam bot 
subscribed to the list. But, of course, that's been proven to have been 
true. I am sure now I'll get pushback on my assertion that you can 
figure out who the spammer was. Heck, it might be as easy as checking 
the list of subscribers.

Like I said when this first came up, I vote for taking it to 
I feel we all have a vested interested in promoting IAVIT. I am the 
Presidet of IAVIT but I'm just trying to provide a service for the blind 
community as a whole.

-- John Heim

On 04/24/2017 06:14 AM, Linux for blind general discussion wrote:
> Tony,
> First of all, as far as I've been able to deduce over the years, 
> everyone *cares* about accessibility. The problem is that no one 
> *knows how* to best address any issues with it. Red Hat certainly does 
> care. If they didn't care, they wouldn't ship Orca, or they wouldn't 
> implement the alt+super+s shortcut to turn on Orca in GNOME. Defaults 
> you say, maybe. But still, if they didn't care, why would they do so 
> much work to get their installer working with Orca? I don't think all 
> that work was an accident.
> With regard to yet another list, it's not necessary at all. We do 
> still have this list, and we can just put our names into our messages. 
> Kyle here .... In any case, if we don't want that, the FSF does have 
> an accessibility list as well.
> No sense making yet another Linux/free software accessibility list. 
> Either use this one, that one or both. In any case, we can't be 
> blaming Red Hat for the current state of this list. They did what they 
> could do as quickly as they could do it. Instead, if there is any 
> blame to throw around, we should be blaming the spammers that got us 
> here.
> ~Kyle
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at

More information about the Blinux-list mailing list