[gopher] Firefox killing off plugins -- Future for Overbite?

[Cameron Kaiser]

> > What does this mean for Overbite's future?  Time to install forg from
> > the repositories?
> 
> I might be off here, but isn't Overbite an *extension*, rather than a
> *plugin*? (One is C++ written for NPAPI, those they want to get rid of;
> the other is JavaScript written for browser-specific APIs, those
> they'll likely keep forever...)

Correct, plugin != add-on

I banned plugins from TenFourFox ages ago, but most Firefox add-ons still
work (at "best effort" support only, but they generally do).

The biggest threat to OverbiteFF is Mozilla moving away from XUL/XPCOM
addons to WebExtensions, which lacks most of the direct socket functionality.
I've complained about this loudly and frequently, and we'll see what they do
about it.

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- I'd give my right arm to be ambidextrous. ----------------------------------