Revisiting Plugins: NPAPI and the Plug-and-Play Web

An Era of Disappearing Plugins

In today's Chrome-based world, it may be difficult to imagine an era when browsers could be extended not just through extensions but also through plugins. While users of traditional Netscape-based browsers, such as Pale Moon, continue to utilize plugins, most web users have had to choose from increasingly restrictive extensions, with Google implementing Manifest V3. These security measures have led to a drastic reduction in options for expanding browser functionality, without addressing the need for executing code faster than the snail’s pace provided by JavaScript.

Challenges of Modern Web Technologies

Modern browsers, particularly those that do not support plugins, like Google Chrome, face issues when it comes to utilizing UDP datagrams. Although there are solutions such as WebRTC, the advanced use of networking features remains limited. The WASI Sockets proposal, which could become part of the WebAssembly standard, comes with many limitations and is subject to support from browsers.

Advantages of NPAPI Plugins

NPAPI plugins allow for even direct rendering on screen, eliminating the need for complicated configurations. This capability simplifies browser use for purposes such as discovering UDP-based services. Unlike current solutions, plugins provide more direct access to operating system functionalities.

Preserving NPAPI Documentation

It is tragic that a simple technology like NPAPI plugins has been destroyed and deemed dangerous in favor of more complex APIs. While modern browsers may not revert to plugins, it is essential that information about NPAPI is preserved. Documentation and source code are rapidly being deleted, and without archives, much could disappear entirely.