4 ms·
Indeed. I guess you're picturing two apps, where I'm picturing one app with much easier per-site settings, with much the same goal. My current plan is to make
by iguy 8y ago
Indeed. I guess you're picturing two apps, where I'm picturing one app with much easier per-site settings, with much the same goal.
My current plan is to make lots of Fluid-app browsers, for certain sites, and then leave JS off most of the time. But there are enough sites which don't work at all, yet I want to visit, to make this a bit of a pain.
- asark 8y agoOne major benefit of a separate program and network (network of hypertext, that is, not IP network or whatever) is that if you can overcome an initial usage hurdle (big if, I know) it'd provide an audience incentive to get current websites that could work just fine on it (which is lots of them) to provide a second experience on it. The way they do now with web+mobile app, but it'd obviously be cheaper to provide than either of those, by a long shot. Gaining the ability to access, banking, ecommerce, and government resources in particular through a hypertext network that's not also a spyware and application delivery platform would be huge for security.
- iguy 8y agoI wonder whether pushing accessibility is another way forwards. Maybe the simple-browser should present itself as a screen reader for the blind, and automatically send threats of ADA lawsuits if a site isn't usable. I know for instance that UK govt. websites are designed for such use first, which just means sticking close to the original spirit of hypertext. Bank websites I have little hope of... and anyway I trust my bank quite a lot! But commerce would be great.