20th July 2004
I believe that extensions like this have a significant role to play. Bugzilla’s Tech Evangelism project is overflowing with badly designed sites that through ignorance or choice refuse to work with standards compliant browsers, many of which have available patches just waiting to be implemented. Per-site extensions at least allow users to choose to fix the problem locally and route around the damage—and their use should send a powerful message to the sites in question.
This kind of extension also introduces some interesting questions. How will site owners react to their users tweaking their websites in this way? Is it ethical to modify a site without the user’s permission to improve functionality? What about to block irritating ads?
Pop-up blockers have only scratched the surface. Let’s see some innovation.
More recent articles
- Weeknotes: the Datasette Cloud API, a podcast appearance and more - 1st October 2023
- Things I've learned about building CLI tools in Python - 30th September 2023
- Talking Large Language Models with Rooftop Ruby - 29th September 2023
- Weeknotes: Embeddings, more embeddings and Datasette Cloud - 17th September 2023
- Build an image search engine with llm-clip, chat with models with llm chat - 12th September 2023
- LLM now provides tools for working with embeddings - 4th September 2023
- Datasette 1.0a4 and 1.0a5, plus weeknotes - 30th August 2023
- Making Large Language Models work for you - 27th August 2023
- Datasette Cloud, Datasette 1.0a3, llm-mlc and more - 16th August 2023
- How I make annotated presentations - 6th August 2023