• 0 Posts
  • 53 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle






  • It doesn’t have to not include JavaScript, that would be quite difficult and unreasonable. Accessible sites are not about limiting functionality but providing the same functionality.

    I haven’t gone fully down the rabbit hole on this but my understanding is even something like Nuxt if you follow best practices will deliver HTML that can be interacted with and serve individual pages.

    That said, screen readers and other support shouldn’t require running without any JavaScript. Having used them to test sites that might be the smart approach but they actually have a lot of tools for announcing dynamic website changes that are built into ARIA properties at the HTML level so very flexible. There are of course also JavaScript APIs for announcing changes.

    They just require additional effort and forethought to implement and can be buggy if you do really weird things.


  • Also the EU and technically a lot of US sites that provide services to or for the government have similar requirements. The latter is largely unenforced though unless you’re interacting with states that also have accessibility laws.

    And honestly a ton of sites that should be covered by these requirements just don’t care or get rubber stamped as compliant. Because unless someone actually complains they don’t have a reason to care.

    I kind of thought the EU requirements that have some actual penalties would change this indifference but other than some busy accessibility groups helping people that already care, I haven’t heard a lot about enforcement that would suggest it’s actually changed.







  • really don’t care enough who you claim to be. You asserted pretty matter of fact who I was starting this discussion but ok.

    if a group of people are using the tools that he created in a way that he doesn’t like or want, is he not entitled to make a change to stop that from happening?

    In short no. At least not if you’re software is GPL, then you don’t have any say in how its used. Its the bargain we make when we choose an open license as it specifically grants the right to use software freely. So up to last year, he has no say in how its used. And honestly, If download and compile the CC version today he doesn’t get any say either. For the most part even proprietary software like Windows don’t get a lot of say in how things are used either if you pay for it.

    at that point the whole community could fork the repo and do their own thing. but no, entitled shitlord users want to post ragebait shitposts and call the dude an asshole for putting his foot down and drawing a line

    There are forks of the GPL code. They’re in the fork tab in github. Also a trip to google finds this version https://github.com/libretro/swanstation which appears to have been forked for 4 years now. There are also other PS emulators that seem more popular in things like retropie where it would be more widely distributed so not sure how much interest there actually is.

    because he’s had enough of entitled shitlord package managers. Genuine question, what did the package managers do that’s so “shitlord”? I can guess about bug reports or complaints about licensing(guess because issues are closed) but really don’t know what he’s mad about the packaging thing. There are some community aur’s but they seem fine.

    1. duckstation-git “most popular” clones the github source and compiles it locally. Its downloading the source directly so can’t be any more unmodified and allowed under the restrictive CC license.
    2. duckstation-qt-bin downloads the app image from the official github and extracts
    3. duckstation - Also builds from source but pinned to old gpl release. looks to patch and update some libraries for compatibility? GPL code so modifications fair game.
    4. duckstation-preview-latest-bin also just downloads app image and extracts

    So none of the aurs distribute anything built on arch infrastructure, its all unmodified versions exactly like his license and readme specify.

    the guy didn’t do anything wrong, because as the maintainer he has the sole responsibility and vision of where he wants to take his project

    Sure, he can do what ever he wants I guess. Accept what ever PR, commit what ever code. He can even delete everything tomorrow(I believe he’s done it before?) because he thinks neclimdul specifically is a jerk and was mean to him on lemmy and no other reason. That doesn’t make his decision good or reasonable or right. I mean you don’t seem to like me but I hope you get my point.

    But just to really be clear why I think this was a jerk move, https://github.com/stenzek/duckstation/blob/master/CMakeModules/DuckStationBuildSummary.cmake#L38

    This doesn’t block packaging, it blocks compiling on any arch system. Its a poison pill because he didn’t like some people using a specific distro and doesn’t really affect me but strikes me as pretty petty.