681–690 of 777 posts
Earlier quoted context omitted.
I don't even know what DRM brings to the browsers apart from breaking external monitors and blacking out screenshots All the content behind it is still available day 0 on trackers
Because the same parties interested in DRM in browsers (and everywhere else) are slowly working on making torrenting more difficult.
Earlier quoted context omitted.
Bravo Andreas, and thanks for working on keeping the Internet neutral. It's a thankless, titanic effort against the Goliaths that want to make it their playground, and us their loyal subjects. Can't wait for the day I can drop Firefox and use Ladybird full time.
[flagged]
Earlier quoted context omitted.
Because the same parties interested in DRM in browsers (and everywhere else) are slowly working on making torrenting more difficult.
They were working on that years ago. After several decades with no success I think they've mostly given up and just profit from it now.
In what way do they directly profit from piracy?
Hello friends, Ladybird founder here! Here's a short video from Chris Wanstrath announcing our non-profit yesterday, and kicking things off with a $1M donation: https://www.youtube.com/watch?v=k9edTqPMX_k Happy to answer questions :)
Are you aiming for 100% compatibility with modern web standards or are you aiming for some sensible subset of it? It seems to me that a large volume of code in Blink deals with obscure features with relatively niche use cases (such as WebRTC, WebUSB,WebGL, WebAudio and so on and so forth), which would mean a large amount of programmer effort for very little user-facing gain. Additionally, in these areas, web standard…
WebUSB is a lot more common than one might think, but I mostly see it used in music gear. Companies like Novation use WebUSB to facilitate firmware upgrades, backups, patch management, etc with their synthesizers and workstations.
Its pretty much a necessity for me at this point so that I can remain OS agnostic and still manage my gear.
Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where integration with OS-specific accessibility architectures (UIA, AT-SPI2, etc.) are concerned? If not, it's a non-starter for quite a few people, and I'd rather know so I know to even keep up with this project or add it to the "user first but oh not actually all users first" pile :)
Here's a question, will accessibility be considered? I fully realize my HN contributions are a bit of a broken record but also, if I don't bring this up, it appears nobody does so here we are. Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where inte…
Here's a question, will accessibility be considered? I fully realize my HN contributions are a bit of a broken record but also, if I don't bring this up, it appears nobody does so here we are. Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where inte…
"User first" definitely doesn't mean targeting all 8 billions people on the planet.
Earlier quoted context omitted.
Don't know about oversized, it felt partly more that eg. Baker was mostly interested in Mozilla as a platform for activism, not in making a good tool for users. The new interim CEO seems to have breathed life into actual browser development.
The new interim CEO has been there for such a short time that she can't possibly have breathed life in anything (she managed to get sued by the former CPO for health based discrimination though, so there's that).
We'll see what happens as the lawsuit unfolds, but I'd be pretty surprised if there is proof that the discrimination was health-based and not due to the fact that he was the CPO who worked with Baker during whatever it was that made them decide to fire her.
[0] From the complaint:
> The board decision to removle Ms Baker was so abrupt that they did not conduct a search for a successor, resulting in the naming of one of their own board members, Ms Chambers, as interim CEO.
Here's a question, will accessibility be considered? I fully realize my HN contributions are a bit of a broken record but also, if I don't bring this up, it appears nobody does so here we are. Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where inte…
Earlier quoted context omitted.
[flagged]
I think you're grossly putting your own political viewpoint on this non-issue and frankly accusing someone of sexism based pro-nouns used in documentation. This is ridiculous. I can read documentation with "he" I can read it with "her". I am adult enough to know it's talking about a hypothetical reader. Fighting a culture war at every corner is just furthering the toxic environment we all live in.
It seems the author is taking an explicitly political stance by vehemently opposing something as simple as neutral pronouns in a README.