Author: JunkMale
Date: 16-06-03 22:29
Joe Marcus Clarke wrote:
> I was curious from the standpoint of how much it would cost
> if I were to pay the fees.
<a href="http://www.bchosting.com/">BChosting</a> provide the machine, the bandwidth, and remote support should something go wrong which I cannot fix from here. I do about 45GB a month. The box in question also hosts freebsddiary.org, freshsource.org (and several of my other domains which have very little bandwidth compared to those already mentioned). The service provided by BCbosting corresponds to a very substantial and non-trivial value. Even if all other ads were removed, I'll still be displaying ads for them.
On top of this, I also display ads for other worthy causes (e.g. daemonnews.org)
I think it would take about US$1000-$1200 to get rid of all the non-paying ads, but it wouldn't get rid of ads altogether.
> > > > > and now, apparently do things like this.
> > > >
> > > > The ad problem may be the symptom, but we know the
> > problem is
> > > > browser specific.
> > >
> > > Yeah, but the browser affected is used by about 80% of the
> > > FreeBSD users. This bug affects Mozilla, Firebird/Phoenix,
> > > Galeon, and Epiphany. Between all of those, you're talking
> > > the bulk of your FreeBSD user base. For that reason alone,
> > > you should be concerned about using your user base.
> > For starters:
> >
> > - the problem affects only Mozilla browsers
>
> True.
>
> > - the problam appears to be related to one ad and one ad only
>
> True.
>
> > - the problem is not a Javascript issue. The reason the
> > problem does not occur when Javascript is disabled is because
> > it is a Flash ad, which is not displayed when Javascript is
> > disabled.
>
> Not 100% sure about this...
I thought it was a Flash-based ad, but it's an animated GIF.
> > Can anyone correct or add to the above?
>
> The problem also occurs on the non-Flash ad (i.e. the image
> ad). For example, if I launch straight Mozilla (which
> doesn't have the Flash plugin), I get the same ad, and the
> same behavior.
Good. So it's not Javascript.
See the other thread recently started where I've found it's not just us having the problem.
--
Dan Langille - webmaster
|
|