Just taking a shot in the dark, but I’m assuming if people were making the needed third party apps for Reddit before, they can repeat this task for Lemmy.
Thing about Lemmy is, since its federated, and fully opensource, even if it doesn’t right now, adding an accessible interface is trivial. Be it through forks/pull requests, separate clients or frontends, or as a full-fledged federated peer focused on accessibility
You are absolutely correct. Lemmy’s federated nature basically guarantees that free / affordable API access will always be available to app developers.
Lemmy is open source and built by the community - the apps are all third party - with the exception of Jerboa, which is maintained by the same maintainers as Lemmy and lemmys default web interface.
So if the community want accessibility, they can do it themselves, submitting code to the maintainers for consideration or building their own interface based on the official and universal API that all interfaces use.
Essentially the official app is official only because of who maintains it - it has just as much privilege and the same access as the other apps and interfaces, and that’s why the app is not called “The Lemmy App” but rather “Jerboa for Lemmy”
Thee official web interface is official and named “Lemmy-UI” not only because of the maintainers but also because it’s bundled with the standard instance backend code - you set up a standard Lemmy instance package, it comes with “Lemmy-UI” as it’s basic interface, alongside thus it also includes additional tools and access for instance admins to use to administer the instance while it’s running. (Defederation and Federation settings, wether to enabled downvoted, 2FA and many other settings)
I’m not up-to-date with the latest in accessibility, but does lemmy cater for those who need assistive tech? (just curious)
Just taking a shot in the dark, but I’m assuming if people were making the needed third party apps for Reddit before, they can repeat this task for Lemmy.
(Please correct me if I’m wrong though.)
Thing about Lemmy is, since its federated, and fully opensource, even if it doesn’t right now, adding an accessible interface is trivial. Be it through forks/pull requests, separate clients or frontends, or as a full-fledged federated peer focused on accessibility
You are absolutely correct. Lemmy’s federated nature basically guarantees that free / affordable API access will always be available to app developers.
Lemmy is open source and built by the community - the apps are all third party - with the exception of Jerboa, which is maintained by the same maintainers as Lemmy and lemmys default web interface.
So if the community want accessibility, they can do it themselves, submitting code to the maintainers for consideration or building their own interface based on the official and universal API that all interfaces use.
Essentially the official app is official only because of who maintains it - it has just as much privilege and the same access as the other apps and interfaces, and that’s why the app is not called “The Lemmy App” but rather “Jerboa for Lemmy”
Thee official web interface is official and named “Lemmy-UI” not only because of the maintainers but also because it’s bundled with the standard instance backend code - you set up a standard Lemmy instance package, it comes with “Lemmy-UI” as it’s basic interface, alongside thus it also includes additional tools and access for instance admins to use to administer the instance while it’s running. (Defederation and Federation settings, wether to enabled downvoted, 2FA and many other settings)