"#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 And I'm seeing more sites that push you to use only chrome for transactions on that site. Shades of Microsoft IE a decade or so back. Ugh.
@Kevin and just the other day, I used to check Gmail with Lynx!
@Kevin
changing #UserAgent to #Mozilla #Firefox's seems to circumvent this for now according to the #HackerNews thread: https://news.ycombinator.com/item?id=21765615
@Kevin
as mentioned in another thread, I wonder how related this is to this earlier issue which was confirmed by a #Google engineer to be an unintended regression: https://news.ycombinator.com/item?id=21626995
@Kevin "May not be secure", as opposed to Chrome that they made sure is not secure and will spy on you?
If you own a browser and you start to block other browsers you should get with an anti-trust lawsuit right in the face, at the bare minimum.
@Kevin ughh, the browser monopoly is such bad news for the internet
@Kevin only annoying,
#unsecured #datacontroller is g00g Le-
#dataservices himself!
@Kevin Filing DoJ antitrust complaint. See https://www.justice.gov/atr/citizen-complaint-center
@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.
@Kevin That is dumb.
The best part is that you could just fake your browser info with a plugin an pass the check.
@Kevin NOOOO! my precious Falkon! They can't ban Falkon, I hate it slightly less than every other browser I've tried!
@Kevin I think “not secure” here means that they won’t secure the smooth functioning of surveillance capitalism.