3 ms·
What kind of Web do you want? + Promotes freedom + Inspires learning + Safeguards privacy + Is available to all + Creates opportunity + Puts me in
by seagreen 10y ago
What kind of Web do you want?
+ Promotes freedom
+ Inspires learning
+ Safeguards privacy
+ Is available to all
+ Creates opportunity
+ Puts me in control
This is a good question. My answers would be "inspires learning" and "puts me in control".
Sidenote: let's address the "enable JS" issue once and for all since it keeps popping up in these threads.
Imagine an alternate history where a book reading program went critical (we'll call it "Reader") and took over the world. (In the actual world of course it was a static document consumer -- the "Browser" -- that took over everything and eventually became its own operating system).
In this alternate history there are regular internet fights (occurring in Reader of course) over whether turning off ReaderScript in Reader is a reasonable thing to do.
One side says: it's dumb to turn off the programming language in your Reader and still expect it to function -- programming graceful degradation into every reader app in the world would cost billions of dollars and be a huge waste.
The other side says: that's true, but I just want to read the Quran without popups!
Happily synthesis is easy since both sides are right. You should never expect a readerapp to work without ReaderScript. You should always be able to expect a book to work without RS -- they should never have had access to it in the first place.
The path forward is clear. Readers should have clearly different modes for books (documents/sites in our world) and apps. We should maintain a community list of which URLs are which, and load that by default into Reader. This way apps can continue to run programs by default, but we don't get popups in our books.