Takhle vypadá root v robotickém vysavači. Motivace je nepustit ho do cloudu a nechat všechna data včetně záběrů z kamery a data z lidaru uvnitř. Zatím pecka.
monocles launches its crowdfunding campaign on StartNext today! 🎉
monocles offers the solution for European independence from big tech. Be it the end-to-end encrypted chat, the secure email service or the privacy-friendly smartphones with our own operating system. monocles creates a decentralized, fair and ethical digital ecosystem for everyone.
There are no known security issues with "Siacs OMEMO" / OMEMO v0.3¹ despite of what some very loud Signal fans would like you to believe. It has been audited by a third party² who took a longer look at it than all of the Signal fans combined.
Yes, #OMEMO v0.7+ (or TWOMEMO 😜) is a cleaner spec with more features (most notably Stanza Content Encryption). That’s why we wrote it. I’m a co-author. That doesn’t mean v0.3 is insecure.
Most of those Signal fans probably refer to a certain blog post by a certain hobby cryptographer. [edit to add: specifically not linked or named because that person doesn't like "evangelists" for messengers-that-aren't-Signal near them. I respect that.]
One argument there holds water, though: OMEMO use is opt-in, and with opportunities to opt-out.
That's different from what Signal offers, and a foot-gun that is way too simple to trigger. (On the down-side, Signal can't opt-out of data being processed in the US. Trade-offs! 🤷)
All the fluff about this-algorithm-or-that or dependency management in Conversations (their solution is dependabot, unvetted-updates-as-a-service. really?!?) is minor compared to that one aspect.
The expectation should be that stuff is E2EE, with carefully (and loudly announced) exceptions where reasonable (when using XMPP as an internal bus protocol, you might be able to get away without it; when running a client on retro gear, you might get better mileage without the crypto overhead, too - but these must be exceptions, not semi-automatic fallbacks)
That story began with a friend of mine that had got a XMPP group chat where they shared updates and pictures of their latest travel adventure. Now chat is rather ephemeral and they wanted to preserve those memories in an easy accessible format that is PDF. And so I put something together.
* actually any chat as long as you can get the raw data in the expected format
nice project. Any chance for some more direct integration with (your fork? of) ceb2json? I imagine that the type of user interested in such PDFs isn't super versed in using command line tools. So limiting that to one (ceb2pdf) would help.
I like your idea of packaging it all up in ceb2pdf. However because this was more like a use-once educational kind of project* I probably won't take the effort.
* Forking ceb2txt as ceb2json was part of it, yes.
About a year ago, my parents made the switch to Linux on their home machines because they really hated Win 10... Today I got a call from my mother to help her out with something, but I did not expect that "something" will be figuring out a sed pattern for a shell script she wrote to bulk rename files.
When I asked her why she didn't use some GUI program she said "I was an accountant in the DOS era, this makes more sense to me than a ribbon menu in Excel".
Metabraille ist im Make zine erwähnt worden 😎 , weil wir eine Open Source Hardware Certification bekommen haben und wir haben es erst jetzt, nach fast einem Jahr, bemerkt! 🤦 makezine.com/article/technolog…
make it compile again for android and attempt to make locales work
logs on android
hardcode locales on android
switch to esm modules for runtime and bundle.js
make locale loading ...
An excellent concise three minute overview demo of the features contained in the monarch version 1.2 update. And a great reminder that visual mode can be turned on with an external HDMI monitor to reflect what is on the tactile array. youtube.com/watch?v=DkSy8gRLoL…
Man, Joplin is so good. The issue is just remembering to use it! I'm just so used to opening notepad and writing random notes and saving them to a textfile somewhere and then losing the textfile.
I have always been satisfied with Framadate and derivatives for quick and accessible event planning when it comes to finding a date that fits everyone. Well, the Austrian government has a tool of its own which is as accessible and it also offers the ability to book appointments, similar to solutions like Calendly or Fantastical. It's called Termino and like all things run by European governments should, it's got its own accessibility statement. Apart from the table where the number of participants voted for a given date choice being tricky to read due to wrong header cells' association, it lives up to the promise of compliance. I have reported that issue and received a response that they will look into it. Some texts, including the email messages, are also in German. I hope they can smooth that one out but otherwise it's there for everyone to use. termino.gv.at/ #Accessibility #Blind
Unfortunatley, after clicking "CREATE MEETING POLL", I get an "Error message" heading and screen reader alert that says: "Sorry, this service is not available in your country."
😲 Sennheiser is taking over Dear Reality as part of Ambeo and making the following products for free without any time restriction. Sign up and get them for free. dearVR PRO 2, dearVR MIX, EXOVERB, EXOVERB MICRO, MIYA, dearVR SPATIAL CONNECT, dearVR MICRO, dearVR AMBI MICRO, dearVR UNITY #3dAudio #binaural #mixing #SpatialAudio #MusicProduction sennheiser.com/en-us/immersive…
Someone here suggested WERO, we read about it and have just activated it in our bank. It was very simple and took 2 or 3 clicks.
An all-in-one digital wallet solution:
Wero is a new European payment system designed to modernize the way we handle transactions across the continent. Launched in 2024, it aims to unify various national payment solutions into a single platform.
Wero is the brainchild of the European Payments Initiative (EPI), a consortium of 16 European banks. The initiative was born out of a need to create a sovereign and unified payment solution for Europe, reducing dependence on non-European payment systems like Visa & Mastercard.
With Wero, sending money to friends and family will be much easier because it allows you to send and receive $$ instantly using just an email address, phone number, or QR code. No more IBANS, 3 days of waiting to receive 💸 etc.
It's also a good alternative for Paypal 🇺🇸 and it is designed to replace several national payment solutions, including Giropay 🇩🇪, Paylib 🇫🇷, Payconiq 🇧🇪 🇱🇺 and iDEAL 🇳🇱 which not always work cross-borders.
The roadmap is full of features to be implemented like online and in-store payment.
For the moment, it's available only in Germany, France and Belgium.
If the document is in Word, you can use Word's own find feature to search for text of particularly colours (press control+h for find / replace, then alt+m for more, then alt+o for formatting, select font or paragraph etc and choose the formatting to search for. Press control+page down or control+page up to find the next or previous occurance of text with that formatting.
Uploaded from my Facebook account, this is a small video of me playing Forza Horizon 5 and starting a mission and finishing a mission. Blindness accessibility features have been enabled.
streamed yesterday: one-hour german #chaosradio @cccfr freiburg feature at @RDL with a deep-dive conversation about #deltachat origins, what it has and hasn't to do with e-mail, protection against server compromise, phone based compared to e-mail networking, how to conspire for baking cheese cakes, authoritarianism and sovereignty, protest and organization, how to arrange for shopping and checklists in chats ... and fun music :)
Tonight's weird tech question: Is there a DOM API/JavaScript hack of some sort I can use to track, save, and restore the screen reader's position in a relatively static HTML document? Say, for instance, you were reading a book in an HTML document with your screen reader, then closed the window. Now imagine that window was an app, and I wanted to make certain your position was restored when that app opened again. Is there an API I could hook into for that?
It's not quite focus, because that'd require tabindex. It probably isn't one of the text properties, right? Because you're not exactly in charted territory when you're arrowing through a paragraph not in a writable element like an input or textarea. Can I track that at all?
No. The closest thing to an automatic solution to that is probably tracking scroll position, and you may or may not be able to make that more granular by making the text quite big (I haven't tried). But even then, the best you're gonna be able to achieve is to track the closest element and put focus back there to restore the position, without character-level accuracy.
I know that Mozilla and NV Access have done some work to allow selection of text within the NVDA browse mode buffer to be communicated to the browser for on-page actions that require a selection. But: 1. That doesn't work across browsers; and 2. your use case seems targeted at reading, not selecting.
Thanks, that's what I was thinking. And just to check an assumption, setting the scroll position won't update the screen reader's position in the doc--I'd have to use focus shenanigans for that?
For context, this is my attempt at a document reader that saves/restores position when the document is closed/reopened. I don't think I need character accuracy, or even paragraph accuracy, if I can open books or longer documents to roughly where the reader closed out.
FWIW I'm not just being lazy and asking, I'm trying right now and it isn't working, which I suspected it wouldn't. It's also possible I'm using my web framework wrong or that something is behaving silly under Linux.
This is, as far as I know, the primary reason why QRead, Christopher Toth's book reading app for Windows, uses a rich edit and not a web view; the rich edit has a caret, so the application can save and restore its own cursor position. The screen reader's virtual cursor is invisible to the application.
You can sort of try and hack this by giving all your divs a negative tabindex and then calling .focus on them, we tried this a few years ago when thinking about QRead web, but the biggest problem is the inaccuracies. I'm okay with being a paragraph back in a book, but not a paragraph forward, and because of the nature of screen readers and the DOM we'd likely get the latter in a lot of cases.
There are some instances in which a webpage can move the scroll position without explicitly setting focus to the target element, and have the screen reader's reading position follow. But that can be less reliable, particularly if the target element is visually obscured, and setting focus is a more explicit/guaranteed way to do it.
Note that if you're setting focus to things like headings and paragraphs that aren't focusable by default, you'll need to dynamically inject a `tabindex="-1"` for the best results.
Perfect, thanks, thinking I'll just try grabbing the first visible element after the last-saved scroll position and do the tabindex dance to position the screen reader. Not character-perfect but good enough for my purposes.
UI Automation (UIA) is Microsoft’s recommended accessibility framework for Windows, replacing the earlier Microsoft Active Accessibility (MSAA) framework. De...
amazing overview, I guess it's a good reference on knowing how browser render page, particularly your cash the world article. also I love these *Must read* for web developers: how modern browsers work by Mariko Kosaka
A shortfin mako shark, the fastest-swimming shark in the world, was caught on camera with an octopus catching a ride on its back off the coast of New Zealand.
Closing in on the first big milestone of Exchange support in @thunderbird! One of the last major items on our list before the next big step is the ability to copy folders - including from outside an Exchange account into one - and I've just managed to get it to work locally. It's not fully done yet, and there's still more work needed elsewhere before everything is ready to test, but it's good progress regardless 😁
The colours in the video are a bit naff, I blame the screen recording tool.
I wrote a CLI tool wrapping the NVDA.zip API, so you can just run nvdl to download the latest NVDA version, nvdl alpha to download the latest alpha, etc. It works on all platforms, and on Windows you will be asked if you want to run the installer after downloading. You can also use -u or --url to get the download URL only, not actually download the installer. github.com/trypsynth/nvdl
Just last week, two people asked me if I could help them set up a #Nextcloud service and move their data off of the big US tech clouds. It may still be small, but the trend is real.✌️
@stooovie Hard to say. I don't cancel the accounts for them, but they usually pay for it and it wouldn't be very economical for them to keep it running.
@WoundClad @stooovie Getting it for free? Certainly not with the amount of data they have. I didn't mean Nextcloud installations on their premise. I do it for myself, but I don't think it's good every one, actually it isn't for most. By "setting up a Nextcloud service" I mean picking something like Hetzner Storage Share and setting it up the way it works for them like the old solution.
A few years ago, I wrote a web audio game based on an old Eureka A4 game called Aliens. The original version was purely audio. I just added some visualisation to see whether it would be potentially more engaging (and easier to learn) for sighted folks. Given that I'm totally blind and not particularly adept with CSS, the visualisation is kinda crappy, but I got my kids to help me check that it at least works. I haven't had anyone with sight test it on mobile, so it's likely completely broken there and thus I'd recommend desktop for now. Anyway, here it is if anyone's interested: files.jantrid.net/aliens/
@KaraLG84 Haha. They don't kill you though. If you miss them, you just miss out on bonus points. They can confuse you though when there are a lot of other things happening.
@KaraLG84 The original game had a slightly different sound for commanders. I might need to do something like that here, though I'm not sure it'd make things easier, just more interesting. What do you think?
Quick demo of a bizarre (not Japanese but Korean) text to speech synth known as JetTalk.
So bizarre it comes with it's own effects processor. Yes you heard that right. Your text to speech voice can have reverb and flanger effects applied to it.
Bummer. Last week our OpenTechFund contract was not signed but suspended along with OTF itself. Shit happening overseas.
However, we wouldn't deliver resilient messaging infrastructure and apps if we weren't a resilient and fun community. We never had much money to begin with, and are graced with great pro-bono contributions.
We are now looking for other public funding but it takes time. Meanwhile it'd be great to get intermittent help via a wealthy donor or small tips delta.chat/en/donate
Donate Money Help Delta Chat develop and grow as an independent project serving the people who use it: IBAN DE86100777770428658900, Account owner (please always specify): Björn Petersen, BIC NORSDE...
Haven't seen this widely talked about beyond the Ableton Access mailing list but having just tried this for myself this needs more recognition. For any Live users, we have what I think might be the first fully accessible Max4Live device, and it's a very useful one at that because it's a audio meter, which supports reading both true peaks and all of the Lufs values, either in realtime or by processing a file. It also supports normalising files, and after you turn it on the hotkeys are global so you can keep checking the levels IE wile you mix. The developer is also intending to release the libraries he developped that aid in communicating with screen readers which will no doubt be very helpful in making future Max4Live devices more accessible. youtube.com/watch?v=jGE4zHv-1k…
Download Flufs here https://iftah.gumroad.com/l/flufshttp://instagram.com/iftah.gabbaicheck out tim burgess herehttp://www.raisedbar.net00:00 - 01:23 - Intro...
Saw this on Reddit about a week ago and been meaning to download it. The Maxess externals have been released as well: maxforlive.com/library/device/… Now all that's left is for Max to become accessible so blind devs can jump in.
@ZBennoui Great, gonna bookmark this for future advocacy efforts :) In general there are still some M4L widgets that need to be made accessible for general users, like buttons, if those are even a thing - I haven't looked at the developer documentation. For example the new expressive chords device that was just released should have a button to import the selected clip as a set of chords but you can't find it with a screen reader, and I think that's more important to do first.
Oh yeah I noticed some devices seemed to be missing controls, but I just thought the devs were using something custom. Hope Ableton is working on that.
Have made my first ever experience with the package pickup stations of the Austrian post last weekend. They have been made accessible to the blind. The procedure is as follows: 1. You receive a physical notification about a package being dropped off at a station in your mailbox. 2. The notification has one of its corners cut off to make a tactile difference. This way you can tell where the code you need to scan is located. 3. You go to the pickup station. The tactile flooring inside will guide you to the stations. 4. You touch anywhere on the touch screen of the station. 5. You touch again, this time the area above a circle shape that can be touched on a strip below the screen itself. 6. The voice guide is activated and issues further instructions. 7. You place the code on your notification in front of the reader. 8. Assuming it has been scanned correctly, you proceed to signing the delivery confirmation on the touch screen. How you can do it without seeing the screen is still a mystery to me but I guess anything you draw is accepted by the system. 9. The locker opens and makes a ticking sound until you find it, remove your package and shut the door. I still find the way of opening it with a mobile app that some providers in other countries offer far easier but it's great those are ready for use even if you don't want or can't use a smartphone. #Accessibility #Blind
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.
@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)
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.
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.
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.
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.
🚀 Bringing a #1 hit back to life! 🚀This is my original 1996 chart-topping production of “Flava” by Peter Andre. After 30 years, I recovered the original Lo...
Jiří Eischmann
in reply to Jan Korbel 🐧 • • •Jan Korbel 🐧
in reply to Jiří Eischmann • • •Jan Korbel 🐧
in reply to Jiří Eischmann • • •