"#Google is now banning the popular Linux browsers named Konqueror, Falkon, and Qutebrowser from logging into Google services because they may not be secure." 🤦♂️
@Kevin Hmmm, they'll block browsers because "Don’t support JavaScript or have Javascript turned off."?
This is funny because I consider JS to be a security hole. (Yes there's a sandbox, no I don't trust it)
@grainloom @jookia @Kevin The vision I want to illustrate with it is that we can create different browsers to present The Web in mediums. So if audio isn't the appropriate medium for you, use a different browser!
Though I will still support keyboard input on laptops/desktops.
@grainloom @jookia @Kevin You'd *really* have to go out of your way to write content that can be heard in Rhapsode but not viewed in, say, Firefox! I'm not concerned.
The content's ordinary HTML5 you can style differently for different mediums.
@jookia @grainloom @Kevin I haven't implemented the input side yet, but you'd need to frame it in terms of hyperlinks. Those'll become commands the user can trigger either typing or speaking them aloud, as indicated by a preceding beep. Otherwise the page will be entirely static.
For the dropdown menu case you could link to a "#id" and tell it to only read the menu when it's the ":target". Or you could use <details> which'll do the exact same thing.
@jookia @grainloom @Kevin And before you ask, I do plan to implement webforms probably late next year.
@jookia @grainloom @Kevin Great intuition!
@jookia @grainloom @Kevin They can absolutely share code!
There's plenty of XML (and to a lesser extent, HTML) parsers & HTTP clients already, and I made sure my CSS engine can be flexibly reused.
