This is a repository of apps to be used with your F-Droid client. Applications in this repository are official binaries built by the original application developers, taken from their resp. repositories (mostly Github, GitLab, Codeberg).
Today I learned: If you use #Chrome and are annoyed by those "Sign in with Google" dialogs stealing keyboard focus on certain websites, you can disable it at the browser level.
In the address bar, type or paste in "chrome://settings/content/federatedIdentityApi" (without the quotes. You should land on the "Third-party sign-in" Settings page.
On that page, there'll be two radio buttons: "Sites can show sign-in prompts from identity services", and "Block sign-in prompts from identity services". Set it to the second one, and you should find that the problematic dialogs are no longer present.
@clv0 Yeah, it was not automatic, I had to set up some filter (or rule or whatever it's called) for this.
I can't remember exactly what I clicked on to set it up (lots of brain fog and memory problems!) but it works. I've seen others post about this solution, too.
@clv0 @ahimsa_pdx I *think* this should be blocked by one of AdGuard or Easylist Annoyances blocklist (i.e. both should work). I no longer see those banners at least.
a friend invited my wife and me to visit them… and we were invited to an event i’ve wanted to do since childhood
had to turn both down because they’re in states where i can’t use the bathroom, and if i had to go to the hospital they’d forcibly detransition me by stopping my HRT
It feels quite uncomfortable that cloudflare is somewhat openly admitting to analysing login credentials that are going through the reverse proxy, and providing aggregated stats on it (without explicit consent of the user it appears?)
Based on Cloudflare's observed traffic between September - November 2024, 41% of successful logins across websites protected by Cloudflare involve compromised passwords.
Don't get me wrong the results are actually pretty interesting, but I just cannot think of a ethical way of doing this, and it feels kind of jarring that they just "did that"
Nearly half of observed login attempts across websites protected by Cloudflare involved leaked credentials. The pervasive issue of password reuse is enabling automated bot attacks and account takeovers on a massive scale.
A Surviver’s Guide to Travelling in Canada, Audio and Text version In preparation for the visit of an American friend several years ago, I wrote this little primer, still relevant, and even more poignant today. My posts are available to anyone but new patrons are warmly welcomed. patreon.com/posts/44513550
A huge THANK YOU to everyone who contributed in any way - from testing and submitting bug reports through to designing, coding, fixing, packaging, testing some more, translating, documenting, hosting, administration, so many people, so much work, so much to be thankful for!
Denmark de facto ended the death penalty in 1892, although after World War II we did for a brief period reintroduce the death penalty and killed 46 people after 5 years of Nazi occupation.
But Republicans really like things old school, and the Republican state of South Carolina recently executed a man by a three man firing squad.
Future generations are going to look back at our time and be confused that this practice existed in our otherwise modern, educated times.
This month’s Windows updates are removing the Copilot app (accidentally) Copilot can be reinstalled from the Microsoft Store if it's something you want. arstechnica.com/gadgets/2025/0…
A very nice write up, I like the approach. I think the key is that he simply asked them for support. Lots of FOSS devs don't want to ask, I know that from myself. Asking for donations, or even nagging, is well know to work. Like Wikipedia. I wonder if it would be possible to eliminate the friction to donating so much that FOSS devs could make a living without having to learn how to run fundraising campaigns? Maybe it just isn't possible.
Long shot but worth it. I think I may have found my blocker for using #NixOS on my laptop/dev machines and am looking for help.
In short, I have multiple #Rust projects that build on the CLI just fine but not in VS Code/Rust Analyzer. I didn't spot this until very recently when I realized problems in my own code weren't being highlighted but compiled crates worked just fine.
Seems RA can't find some libraries but to the best of my abilities I've made those libraries available to the shell. I also launch code . from the terminal so it should have the environment set up correctly without need for Nix-specific extensions.
It's been suggested I not use the code-fhs Nix package, but that means starting from scratch and fixing existing extensions which work.
Please don't suggest abandoning VS Code or substantially changing my accessible workflows unless you also have 12 extra hours per day for me. Also please don't suggest abandoning Linux entirely--this issue is NixOS, not Linux.
Hey folks, seems like every time I think I’m starting to figure things out, I hit a new wrinkle. 🙂 I’ve been trying to move various projects to devshells.
just a shot in the dark, but... if I understood correctly your code builds fine in the dev shell, right? how do you make that dev shell available to vs code with all $PATH, etc? Unfortunately I have not much knowledge about Rust, but it appears that $PATH is somehow altered by vs code. if that was stupid, please ignore 😄
I just cd into the directory and run code . direnv takes care of the rest. Unfortunately, installing the direnv extension in VS Code doesn't appear to fix anything--adding that because someone just suggested it elsewhere. Thanks for the thoughts.
I'm not that familiar with vs code, but I believe that running code . from within the dev shell does not inherit the session itself, but I am not sure how you set up the dev shell.
I think direnv would read preconfigured .env/.envrc files and would not get the environment vars from the session. There seems to be an extension for vs code named "Nix Environment Selector" that would let you select the dev shell file for an environment.
Install the VS Code direnv extension so my existing direnv setup automatically works in VS Code (I.e. it automatically downloads dependencies, sets up the environment, etc. without needing to be launched from a terminal first.)
Start VS Code outside the project (I.e. from the myproject directory, cd .. && code myproject.
I guess my next question: is there a quick half-liner I can run to do something like nuke_it_from_orbit && code . to clear/reset the environment first? code . from the terminal is pretty thoroughly in muscle memory at this point.
Thanks to a meetup at our local hackerspace @metalab , I have learnt about a web-based, open source, highly accessible video downloader frontend you can fire up at cobalt.tools. Really easy how it works: 1. You open the site; 2. you paste the link into the edit box; 3. You press enter; 4. The standard "Save File" dialog comes up. All the extra stuff like formats and qualities can be set in the settings and a choice between a video, audio-only or video-only version is offered under a button below the link input. #Accessibility #Blind
Oops, the list of supported sites has no spacing to the virtual buffer, causing an absolutely huge blurb of nonsense to get thrown at the SR. I should open an issue about that.
Edit: This post is based on outdated information which is no longer relevant. I apologize for the confusion. NVDA Remote was merged into NVDA for the upcoming 2025.1 release. This sounds like something to be happy about, but read on.
Now every new feature and change has to go through NV Access to get approved, which is a lot more work than adding your feature to an addon.
Why not create a separate addon? As said in #17703, they plan to remove the ability for addons to run on secure screens in the future. If this happens, nothing like Remote can ever be created again without the blessing and cooperation of NV Access. Instead of empowering developers and users by allowing them to choose which addons are usable on secure screens, NV Access plans on disabling them. Merging this just gives NV Access more leverage to meeting this goal. Their reason might be something like now that Remote is merged, we don't need addons there anymore because the interaction time is so short.
You might say that NVDA is open source, so someone can just modify the features they don't like. That's true, but it has to be signed for UI Access to work correctly, so someone would have to pay quite a bit to fork it and do their own thing. You then also have the problem of a fragmented community between NVDA and the new one.
The advantage with Remote merged in is that the users will be able to use Remote without an extra download, but we're going to be stuck with whatever NV Access gives us. I guess we'll see what they turn it into.
2/2 We understand users may need to run add-ons on secure screens. We are also keenly aware that allowing arbitrary code to run on secure screens can be a risk. We are building a way to allow users to run add-ons in secure contexts safely. We are working to give users more options to customise their level of security & have no plans to stop add-ons running on secure screens. As always, we encourage feedback, particularly where we have announced something & may not have considered all use cases.
@alexchapman @meatbag We'd be happy to take any concrete feedback you have on exactly what has gone downhill? (Steps to repro, comparison with 2024.1, etc)?
@fireborn We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
Wow, not even synthesizers? Or what if there actually are Braille display driver add-ons? The infra for those exists, even if I haven't yet encountered any in the wild. Also speech history. I'll probably just keep using tele NVDA if their integration of this doesn't break any such add-ons.
@x0 We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
Now, if they do end up making a corporate version of NVDA which comes with add-ons hard disabled, I wouldn't object. Security departments are worried about arbitrary code execution and it isn't entirely unfounded. I wouldn't take it for a malware target but it might allow you to break out of a sandbox. A useful signing mechanism would be nice to bring in synth drivers and app modules approved by higher ups.
@x0 We ARE working on a corporate mode, and more secure add-on API to address these concerns AND allow users to still do everything they need. Please see fosstodon.org/@NVAccess/114187… for more information.
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@KyleBorah @x0 We regularly liaise with corporate IT departments using NVDA and haven't encountered a company or IT department in at least 10 years worried about NVDA because it's open source. If you can provide concrete details to us of specific organisations with concerns (privately) we'd be grateful. In the meantime, please see this section of our corporate pages which links to multiple international company & government policies encouraging open source: nvaccess.org/corporate-governm…
Government and corporate users have specific requirements around security and documentation. NV Access is pleased to work with organisations around the world. This page contains documentation and …
@KyleBorah Ah. Wait, they specifically don't trust FOSS things because the code is available as opposed to them paying for something propriotary? I know NVDA is a bit too big to audit, but if someone is concerned, isn't FOSS better for transparency than propriotary? Plus it isn't as if loads of modern corporate infra isn't built on it. I guess it jsut seems weird to me that an IT department would inherently distrust open source given how far it's spread into even the corporate world.
@x0 @KyleBorah We regularly liaise with corporate IT departments using NVDA and haven't encountered a company or IT department in at least 10 years worried about NVDA because it's open source. If you can provide concrete details to us of specific organisations with concerns (privately) we'd be grateful. In the meantime, please see this section of our corporate pages which links to multiple international company & government policies encouraging open source: nvaccess.org/corporate-governm…
Government and corporate users have specific requirements around security and documentation. NV Access is pleased to work with organisations around the world. This page contains documentation and …
@alexchapman @KyleBorah @x0 We regularly liaise with corporate IT departments using NVDA & haven't found a company or IT department in at least 10 years worried about NVDA because it's open source. If you can provide concrete details to us of specific organisations with concerns (privately) we'd be grateful. In the meantime, please see this section of our corporate pages which links to multiple international company & government policies encouraging open source: nvaccess.org/corporate-governm…
Government and corporate users have specific requirements around security and documentation. NV Access is pleased to work with organisations around the world. This page contains documentation and …
@x0 we might need to make our voices heard about that. I don't have that much knowledge on how this works, but while I think it's ok to think about being able to block it in some way that would be very difficult to get around on specific computers or user accounts, my own computer if I want to run add-ons in secure environments, then I should be able to.
@valiant8086 @x0 We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
This is bad news for Eloquence users who use Eloquence for secure screens. Luckily, I'm not one of such users. Usually, I use my default configuration. But I have a few friends who use Eloquence for everything, including their secure screens. I mean, porting IBMTTS into the core of NVDA would be a bit ridiculous, as I previously stated, I do not use Eloquence. I know some people who would say otherwise though.
@mckensie We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@BTyson Brandon, firstly thank you for tagging us in this thread. We are disappointed that this was created rather than asked privately where we could have cleared it up AND we weren't even tagged in it... So, we aren't disabling add-ons on secure screens. You'll have seen our original reply, but linked again here just in case it's useful: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@BTyson By the way, Which synthesizers do you know of which support languages eSpeak-NG / OneCore don't support (or don't support well)? Not doubting it - in fact the opposite and trying to keep track of resources which users may find useful.
@vol4life8657 @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187…
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@BTyson @NVAccess I fully concur with all the points mentioned. I will refrain from updating my version of NVDA should this transpire. Although integrating NVDA remote as a component of the primary NVDA package might seem beneficial, the resultant compromise is not advantageous for the end user. It is almost as if the argument is that they will be provided with NVDA remote and other crucial add-ons deemed important, but are restricted to downloading add-ons solely from the specified add-on store, and your only screen reader open to you is NVDA at startup. I acknowledge that the latter point is somewhat exaggerated, however, in my view, there should be no reason for users to be restrained from using their preferred speech synthesizer on the UAC screens or at startup. From a user's standpoint, even contemplating such an idea is illogical.
@patricus @vol4life8657 @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@vol4life8657 @BTyson @NVAccess yeah, are we turning NVDA into narrator now? please don't disable addons on secure screens, just don't! let me pick what addons I need, not some oh I'm going to restrict your freedom bullshit now!
@svenja @vol4life8657 @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@mckensie @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@jcsteelguitars @mckensie @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@mckensie @BTyson @NVAccess I'm not at all in favor of the plan to totally disable addons on secure screens. what if people use a particular speech synth that they prefer using and that's not built into NVDA? This is totally fucked and should be totally optional!
@Bruce @gocu54 @BTyson We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@LeonianUniverse @Bruce @gocu54 @BTyson Only sudden if it were true - and if it were, we'd announce it, officially, ourselves.... We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@Bruce @gocu54 @NVAccess @BTyson Yeah, this seems kinda sudden if you ask me, why would they restrict peoples' freedom like this all of a sudden? I'm glad I switched to Jaws for the most part, that's for sure.
@x0 @Bruce @gocu54 @BTyson No... because we're not quite sure where Tyler got this from... Rest assured we will continue to encourage community feedback about any change like this...
@x0 @Bruce @gocu54 @BTyson Ah well in that case, this must be documented in our Roadmap.... No... Our Blog? No.... Our own social media posts..... No? Hmmm.... Maybe .... just maybe.... this whole thing wasn't from us at all......
@jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson As previously mentioned, we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information; you can now sign up to updates like our blog via email: eepurl.com/iuVyjo
And for corporates wanting to block add-ons, they probably wouldn't allow add-ons with unclear licenses in any case.
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@fireborn @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson We aren't disabling add-ons on secure screens, and certainly not for users who don't want it. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@serrebi @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson Don't worry, we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@jackf723 @alexchapman @x0 @Bruce @gocu54 @NVAccess @BTyson Feels like that’s the point of all this. Hope someone forks it. I made portable versions of NVDA for a while, but I didn’t think I had the skills to deal with forking properly.
@alexchapman @serrebi @jackf723 @x0 @Bruce @gocu54 @BTyson If you want to fork it for your own interest, go ahead, but please don't do it based on unsubstantiated rumours. Also, if you would like to make contributions which would benefit the whole community, please do consider contributing them to the official NVDA project, that way they will benefit ALL users
@NVAccess @alexchapman @serrebi @jackf723 @x0 @Bruce @BTyson I honestly don't even understand the changes myself, nor do I knokw how to fork programs, as I don't even know what forking is.
@BTyson @x0 @Bruce @gocu54 As of now, we've seen one unsubstantiated rumour panic a heap of people on here, from someone who should know better and have approached us with their concerns first. The NV Access team have discussed this today and confirmed there are no plans even through 2026.x for anything this disruptive. If you have seen an issue which seems to state this, PLEASE share it as I am curious as much as anything now.
@x0 @Bruce @gocu54 @NVAccess The issue I was looking at for this said that the milestone is set for 2025.1, hence why I posted this now. My plan was to wait, but the milestone seemed to be set already.
@gocu54 @BTyson @x0 @Bruce Please see our initial response to this thread - we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@BTyson @x0 @Bruce @gocu54 I'm not sure why you didn't bring your concerns to us instead of creating a needless panic in the community - but please do share this issue as we are curious now?
@NikJov @stirlock @BTyson Mike is right - don't panic just yet - we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@stirlock @BTyson @NVAccess Or maybe wait until it happens and see how it transpires, and then provide your feedback? Personally, I can't imagine that there wouldn't be an exception for speech synthesizers/Braille display drivers, but let's wait and see. Other than that and kill NVDA in some cases, I don't really have any addons that absolutely must run for the 30 seconds that will take me to sign in/confirm UAC.
@Lino_JR @BTyson We could - even better, when someone has a concern about something they THINK we are doing, maybe bring it to us directly in the first instance, so we can respond, before taking it publically and needlessly scaring the community....
@evilcookies98 As long as you've got a workable screen reader & are happy. If you do switch between the two, our switching guide may be helpful: github.com/nvaccess/nvda/wiki/…
FWIW, we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@NikJov the point is it leaves your preferences mostly intact. It doesn’t switch back to eloquence on speed slow as a snail just because you pull up the sign in screen.
@NikJov if your preference is not using some cruddy built-in voices, yes, it is. I don’t think you’re hearing me here. This isn’t just for fancy functionality.
@evilcookies98 @NikJov If you want to use Jaws, go for it - but NVDA lets you easily use your preferred speech settings on the sign in screen. If that's your main concern, I'd be happy to walk you through addressing it (and in any case, we'd be happy to hear any other concerns you do have you feel warrant changing screen readers - feel free to write to us at info@nvaccess.org)
@evilcookies98 My preference is my speech rate. About custom voices, we'll see what happens when it happens. I have no need to switch my screen reader over something that may happen in a year, but maybe it won't even impact me in any way, for instance maybe synth drivers will be an exception. I don't see the need to instantly jump to the worst conclusion possible.
@NikJov just because that’s your preference doesn’t mean it’s everybody else’s. Think bigger here. Also, what about our braille display people? They’re getting screwed too.
@evilcookies98 Nobody is getting screwed because the change isn't even implemented yet. When it goes to alpha, that's the time to provide feedback if your points aren't already in consideration. So, I can't actually think bigger, because there's nothing to think about. It's only an item on the roadmap.
@NikJov @evilcookies98 Ah that's the problem.... Did we say that? Please do point out where it says on our roadmap we are going to disable add-ons on secure screens? You'll find it here: nvaccess.org/post/nvda-roadmap…
NVDA Roadmap This document outlines NV Access’s planned development roadmap for NVDA and its supporting infrastructure. Priorities are grouped into short, medium and long-term time-frames. Th…
@NikJov @johann @evilcookies98 Because the default is user hostile. At least have it be users choice. The default, allowing these add-ons on secure screens, of course. Businesses that want things to be secure. Can check the box, or enable it on install somehow. This does not need to be the default.
@serrebi @johann @evilcookies98 To be honest, I really don't know of many open, or close source apps that provide the ability to run whatever custom Python code on the Windows sign-in screen. To be clear, I fully agree that there needs to be a way for speech synthesizers and Braille display drivers to run, but other than that, almost no add-ons are needed during the minimal amount of time on secure screens.
@NikJov @johann @evilcookies98 I agree with that, of course. I think it is interesting timing that remote got put in with an inconvenient shortcut command that I have come around too, and now we are talking about blocking out speech synthesizers some people don’t like us using from the logon screen. Not a good look for MVDA.
@serrebi @NikJov @johann @evilcookies98 I think I've driven home the original point, but just wanted to pick up the keystroke - I can't recall if there was discussion on that, but do feel free to comment on the issue / give us feedback on it - and of course, you CAN change keystrokes in NVDA's input gestures, as described here: nvaccess.org/post/in-process-2…
We’re nearly at the stable release of NVDA 2024.2! While we prepare, we thought we’d try something new – a table of contents so you can quickly find out / jump to the various articles i…
@serrebi @johann @evilcookies98 It doesn't have anything to do with someone liking or not liking a certain synthesizer. As for the remote shortcut, that's a highly individual item, for me, taking over the F11 key on its own was way more inconvenient, and with no way to change it without editing the source code. I switched over to TeleNVDA just for that. At least now, you can choose your own preferred shortcut.
We’re nearly at the stable release of NVDA 2024.2! While we prepare, we thought we’d try something new – a table of contents so you can quickly find out / jump to the various articles i…
@NikJov @johann @evilcookies98 Yes, I know the reason the feature is coming about is really about security, and not about eloquence, but just the timing of it all. I don’t see why it isn’t a checkbox, and something that could be enabled on install, or silently on install if it means so much to some people.
@serrebi @johann @evilcookies98 That's the thing. We don't know yet how it will work, just that it is a plan. The feature isn't here yet, so its details aren't known. I don't know if there will be a way to override it for advanced users, or not. No special timing involved too, this has been on the roadmap for a while, check the first issue about it I saw in 2022 at github.com/nvaccess/nvda/issue…
Overview There is currently no way to ensure that add-ons are secure to run. This is especially concerning on secure screens. When config is copied to secure screens, all add-ons are also copied. T...
@NikJov @serrebi @johann @evilcookies98 Ways of ensuring security, yes, but this particular issue was closed two years ago. If there IS a current issue proposing NVDA unilaterally disable all add-ons on secure screens which is triaged and assigned a milestone release, please do link to it....
Hello, dear NVDA developers! I have a suggestion for you. Since NVDA has the option to copy the current settings for use on secure system screens, clicking on the corresponding button in the "Gener...
@asael @pvagner We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@cachondo We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@RyanF Good pickup Ryan - if this HAD come from us, there would be a link to an issue, a PR, an item in our roadmap..... We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@SeveraSnape Unfortunately (or acutally, fortunately) Tyler has the wrong end of the stick on .... wherever he got this from. We aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
@gocu54 @alexchapman @serrebi @jackf723 @x0 @Bruce @BTyson No need to try to make your own fork for this, we aren't disabling add-ons on secure screens. If @tspivey had raised any concerns with us, we could have explained, but please see our reply here: fosstodon.org/@NVAccess/114187… Please follow us for OFFICIAL information, and remember you can now also sign up to updates like our blog via email: eepurl.com/iuVyjo
Thanks to @BTyson for tagging us. We can't respond if we don't see a post. NVDA is a community driven project, and one of the roles of NV Access is to help ensure that people can trust the software. There are several projects currently underway that touch on this. We are working on a more customisable & secure corporate mode for enterprise users. We are also working on a comprehensive & secure add-on runtime & API (which will also help prevent yearly API breaking changes). 1/2
Ok, I can clarify again, we are NOT removing the ability to run add-ons on secure screens. It was a thought awhile ago, we have moved on from this considering how it would impact users. The 2025.1 milestone was a false automated tag when the issue was closed. It was closed as a duplicate of #6305 & #12879 which are both still open.
@NVAccess thanks for the clarification! This once again shows that noone is safe from falling for Misinformation. I'm sorry that you have to correct it in so many Conversations right now.
@NVAccess @Aryan @fireborn @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson I had a few reservations, said my bit and let the thread end. Not all of it was even about addons and secure screens. People took more out of it than I intended. I thought my original post was pretty clear that it was in the future, not a something to panic over right now thing, and I even included my source. Maybe it would've been better to wait until that actually showed up as a PR to comment.
@svenja And unfortunately there's only going to be more and more misinformation going around in future (not about us specifically, I hope - I just mean in general!)
@Aryan @fireborn @jackf723 @alexchapman @x0 @Bruce @gocu54 @BTyson You deliberately pulled a month old comment from an issue which was closed as a duplicate, ignored the referenced open issues & did not ask in the appropriate channels - ideally on the issue where the comment was made, or at least by email to us, or even tagging us. So no, I don't buy for a minute that you legitimately expressed a concern and let it be. You deliberately lit a fuse and waited for the fireworks. - Quentin
@NVAccess @x0 @Bruce @gocu54 In the original issue, Sean Budd states, "Note, we plan to remove the ability for add-ons to run on secure screens in the future," which was why I also wanted to tag NV Access.
@x0 @Bruce @gocu54 @NVAccess It was the one you posted, it said that it was added to the 2025.1 milestone, and so it was seeing that, plus that the issue was closed, that led to me posting this.
@BTyson @x0 @Bruce @gocu54 It looks like the way the issue was closed set the system thinking it was "completed" & added to the next milestone (2025.1). Though for THAT to be correct, it would need to have been closed by a pull request (addition of code actually addressing the sisue). The comment about future direction was, as noted, a thought at the time, which hadn't been at fleshed out yet. Since then we've changed that direction. It would only have taken a question to US to confirm.
@BTyson @x0 @Bruce @gocu54 And we are grateful you did, as the OP didn't bother - In fact, the best place to question that issue comment, if not the issue, would have been an email to US directly, not a public comment to everyone EXCEPT us. We had since considered the impact and alternatives and changed thinking, and would have been happy to confirm that if anyone had asked... (And yes, I've since commented on the issue to confirm that as well)
This photo captures the incredible feat of nature where young Boeing airplanes hatch from their eggs and begin to crawl onto land. They will stay this way until they can develop their wings.
I'm Loki, a neurospicy, anarchist artist, fan of buckwheat pancakes and who thinks he's a coypu, unless it's the other way round
I do digital art, linocuts, cyanotypes and letterpress printing. It's very often with angry animals and questionable puns, always with anarchist and progressive themes and vintage aesthetics.
As I'm an anarchist, I give digital version of my creations away for free. And because I like to eat and have a roof over my head, I also sell prints
You can find my portfolios, my free downloads, my shops and all my links at social.lokipropagand.art
Sharing pisses off fascists (and regenerates the follows after a slow migration)
📣 Do-It-Blind (DIB) online Besprechung am Montag, 17. März, um 19:00 Uhr. Du bist eingeladen! bbb.metalab.at/rooms/joh-szv-o… Wöchentlich am Montag um 19:00 besprechen wir neue Formen der digitalen und inklusiven Zusammenarbeit. Mach mit! 🛠️ #make #blind #inklusion
Learn using BigBlueButton, the trusted open-source web conferencing solution that enables seamless virtual collaboration and online learning experiences.
GIMP 3.0 Stable Being Released As Long-Awaited Update To Adobe Photoshop Alternative
After some 13 years of writing about GIMP 3.0 development, today is finally the day: GIMP 3.0 has been tagged and is in the process of being released... phoronix.com/news/GIMP-3.0-Tag…
Age Check-Survey for all my IT friends
How did you learn about RegEx?
[ ] Javascript
[ ] Python
[ ] Perl
[ ] vim
[ ] vi
[ ] sed/ed
[ ] Here, in this poll
[ ] I am Ken Thompson
I voted Perl/PHP, but I think my actual first exposure to regexes might have been the MOO programming language (LambdaMOO may be more searchable) in the late 90s or early 2000s. I'm in my mid 40s now.
Underappreciated benefits of giving blood include: the fact that if you're wildly depressed and generally despising yourself, you get 1 (one) day of feeling like your life had meaning and purpose.
You get free KitKats too, but everyone mentions those.
I don't think "disability advocacy" went wrong at all, this "differently abled" shit is from the 90s when wheelchair users had to crawl up the Capitol steps to get the ADA (Americans with Disabilities Act), when "nothing about us without us" became a slogan because it was such a common problem.
"Differently abled" and cripspiration came from abled people trying to manage their own fear of mortality and their own discomfort around the concept of disability. @inkican
- Multi-selection of layers - Proper high pixel density display support - Improved graphics tablets support - Wayland support - New soft-proofing toggle in the status bar - Initial UI for non-destructive layer effects - Reworked Align and Distribute tool - New "Outlined" and "Outlined and filled" options (text) - Redesigned and reorganized "Fill by line art detection" settings
"By establishing that data protection extends to gender identity and explicitly forbidding surgical requirements, the Court has created a powerful legal framework that transcends national barriers. This ruling provides both protection and recognition. It tells every trans person in the EU: your lived identity matters, and no government can erase it through bureaucratic obstacles."
Kohler added this is far from just a victory for refugees in Hungary - "it's a declaration that across Europe, your gender is yours to define, not the state's to dictate."
Prosody 13.0.0 is here! Farewell Zero-ver! This major release brings a number of exciting new features, including improved security, performance, and administration tools. Check it out: blog.prosody.im/prosody-13.0.0… #prosody #xmpp
Welcome to a new major release of the Prosody XMPP server! While the 0.12 branch has served us well for a while now, this release brings a bunch of new features we’ve been busy polishing.
@paulhutchinson Hi! No you can edit your signature, but for now this is limited to one signature that's editable. (We don't yet support multiple signatures)
@kubicek U nas si zlodeji pisu trestny zakonnik, nuz putin by si rad pisal vojenske a vyjednavacie konvencie.
(A ano, tym chcem naznacit, ze #SmerHlasMafia maju vela spolocneho s vrahom a vojnovym zlocincom. Aj ked niektori budu namietat, ze ti "nasi" "iba kradnu". Ale ja tvrdim, ze kedze kradnu zo statneho, tak o.i. zabijaju ludi v tom state.
Ale to uz som odbocil. Ano, ruzzko treba z Ukrajiny vykopat tak, aby ich presli chutky na dalsie zabijanie.)
@phanecak ono to má nejaký výraz keď to pôsobí nepriamo... zase ale o vyslaní jednotiek sa v poslednom čase hovorí. Moja predstava je, zastaviť boje a nahrnúť techniku a vojakov.
I already mentioned that we got funding from #Mobifree via @nlnet If you're curious what we're working on there, what we've already achieved, and what's in our pipeline, be welcome to visit the corresponding #IzzyOnDroid Dashboard at codeberg.org/IzzyOnDroid/-/pro…
it would help those of us who are unfamiliar with the project but curious if you had an elevator pitch saying what this is and why we should care. I couldn't find one within a minute of trying.
@fazalmajid It installs rbtlog and tools. That's what we use to verify whether apps can be built reproducible (i.e. byte-identical), thus confirming they were really built from the very source code they claim, with nothing added or taken away.
Apart from that, developers can also use this to just build their apps, ensuring they are always built from a clean tree at the specified commit, and thus making RB easier.
Summer 24 somewhere in Sweden. After a delicious dinner, we went for a digestive walk with the midnightsun and making some survey. Of course I used the Osmand app with Quick Action function, Streetcomplete and took pictures with Mapcomplete.
For our "automated builder setup", I've just prepared a PR adding support for RPM based systems. The PR is still marked WIP as I don't have any RPM test system at hand here – so I'm calling out for help:
Anybody willing to test the setup scripts on Fedora, RHEL, CentOS or the likes? 🙏
(more tests on Debian-based systems (Debian, Ubuntu, Mint …) are of course welcome, too)
Fixes #2
This adds support for installing the builder package on RPM based systems. Testing needed: someone running an RPM based system, please give it a try!
- Added a question if toilets are supervised and have handdrying facilities - Many bug fixes (e.g. the charge for specific objects in vending-machines now works again)
@april Under 'menu' -> 'download' there are various download options to further process the data; you can embed mapcomplete in an iFrame or create another mapcomplete theme which shows this layer together with other layers.
As usual, all the data is from/goes to #OpenStreetMap, so you are free to reuse the data.
nothing better than beer, gloves and Spen
🏳️⚧️ ✨
SuspiciousDuck
in reply to SuspiciousDuck • • •