Attached: 1 image
System1 owns the search engine Startpage.
System1 is a publicly traded advertising/marketing company headquartered in the United States and traded on the NYSE as SST.
CNBC System1 profile: https://www.cnbc.
🖼️ "A study in reactive UI toolkits" with Jan Fooken at #GUADEC2025 📅 24 July 🕒 09:40 CEST 📍 Brescia 🧪 Can GTK feel like React or SwiftUI? Let’s explore modern takes on building Linux UIs.
Welcome to GUADEC 2025 GUADEC is the GNOME community’s largest conference, bringing together hundreds of users, contributors, community members, and enthusiastic supporters for a week of talks and workshops.
Narazil jsem na skvělý nástroj, který umožňuje převést export z Pocketu do formátu kompatibilního s Wallabag – a to zcela offline ve tvém prohlížeči (100% client-side)!
🔧 benjaminoakes.github.io/pocket… 👏 Díky @benjaminoakes za tuhle skvělou pomůcku! Pokud migrujete z Pocketu na Wallabag, určitě doporučuji vyzkoušet.
Dost podstatný důvod proč nepoužívat Telegram: Pavel Durov se chlubí chystanou roční smlouvou s xAI, která přinese Grok do Telegramu, čímž Telegram získá 300 milionů dolarů. coindesk.com/business/2025/05/…
In this post, we discuss how the ongoing war in Ukraine has led to a significant decline in the amount of IPv4 address space announced by Ukrainian Autonomous Systems (ASes), and why those addresses are often now being announced by western ISPs and m…
Jedna z nejzásadnějších položek základní výbavy cyklisty? Brýle. Rozhodně. Důvod je přitom velmi prostý, ochrana očí proti cizím předmětům. Ať už hmyzu (co se rád strefuje i do otevřených úst) ale i kamínkům či prachu.
One of the biggest things to come to NVDA in some time & the highlight of NVDA 2025.1 is NVDA Remote Access! In this blog post, we look at just what this feature is, how you can use it, add-ons which do similar things & answer other questions you might have: nvaccess.org/post/in-process-1…
Do you use NVDA Remote Access? Or is there another 2025.1 feature you're really looking forward to? Do let us know!
Hi. Now that remote is part of nvda, I think it would be more reliable, if there was an official host from nvaccess and it should be included in the user's guide. Now only nvdaremote.com is given as an example there.
@nikosdemetriou Good idea. Also, as I have said on GitHub I'd like to see information on how to use NVDA Remote to control a computer on your local network without using a relay server.
@KaraLG84 @nikosdemetriou Thank you both. NVDA Remote definitely still has lots of improvements ahead of it. Our first intention was to ensure it provided a comparable level of operability to the add-on (with which it is compatible btw), but we definitely have more development planned for NVDA 2025.2 and beyond.
@KaraLG84 Whoops, thank you! You are my best proof reader! (heaps better than me, that's for sure) - would you believe, I rewrote it and decided to give you most of both options?
It's likely impossible due to reasons, but would be absolutely fantastic if a remote configuration could carry over to the 2025 update, whilst disabling the addon. IE: If I'm updating a system I have no physical access to, if it could import my remote settings and reconnect seamlessly, would solve a few issues.
@FreakyFwoof Pretty sure those values are just in a .ini somewhere so it SHOULD be relatively trivial to migrate those provided the updater gives that kind of control...
@FreakyFwoof Shouldn't "carry over" mean that IF a currently active Remote is detected, it should also just enable it on the internal side on update to not interrupt a bunch of people's setups?
Like many access issues affecting NVDA, history repeats itself. NVAccess just told us to essentially live with the freezing and search results reading issues affecting the Start menu on Windows 11 24H2. They requested that we ask Microsoft to fix the issues, which essentially means coming to terms and living with the glitches. FYI JAWS devs fixed them for their users some months ago. github.com/nvaccess/nvda/issue… @NVAccess
Steps to reproduce: Use NVDA to go to the start menu, try searching for something, and make sure you are on Windows 11, 24H2, and have the latest updates installed. Actual behavior: NVDA usually wo...
Do you mean my encouraging Sarah to share the link to the Microsoft issue when it's their bug? Just because something is noticeable using a screen reader does not make it a screen reader bug... Sometimes we can work around OS bugs, sure, but in the vast majority of cases, it is better - for everyone - if Microsoft fix bugs in Windows and we concentrate on fixing bugs in NVDA (you can't complain we aren't fixing NVDA issues and then complain we're not also fixing WIndows bugs surely?)
No, I mean seanbudd's new comment, encouraging users to ask Microsoft for a fix. I understand your mindset, and even grasp it from the perspective of an open-source screen reader dev or manager. However, the reality is far bleaker than that, and OS bugs, like the ones affecting the Start menu now, are sometimes more serious to be handed over to Microsoft's whim. I'm just glad JAWS developers haven't followed this line of thinking.
In all seriousness, it's not just about palming things off. If there is a bug in Windows, the best we may be able to do is patch it, we can't fix it, only Microsoft can do that and THEY are the best ones to fix it. I'm really not sure what you want me to say. Have you raised this with Microsoft? Because they are the ones you should be yelling at. Just because Jaws has patched over it (and theoretically we may be able to as well then) still doesn't take the responsibility from Microsoft.
There is almost always a price somewhere, some time for hacking around bugs in the wrong layer, even if that's as simple as months spent figuring out a workaround which means months spent not being able to work on higher priority bugs. Maybe JAWS hacked around this one, but maybe it causes some other bug you hate down the line. You're assuming Microsoft won't address this, but pressure on them from many different angles sometimes does work, albeit less often than we'd all like. Still, it is always worth trying that approach first. Hacking around the bug still remains a last resort if Microsoft absolutely refuse to address it going forward.
@jcsteh Sorry James but, with all respect and I do respect what NVAccess has done, this is a so-called blanket statement. Yes, like every fix or new feature, this JAWS fix might cause issues. NVDA fixes or new features also cause issues. But with this one at least, I've seen no issues with JAWS and the way it properly handles the Start menu. Even if issues arise down the road, I'm positive Freedom Scientific will fix them more quickly. Honestly if I were to ask Microsoft to fix each and every Windows bug, I'd rather ask them to enhance Narrator so as to obviate the need for the likes of JAWS or NVDA. @NVAccess
Are you suggesting screen readers should hack around every problem in every piece of software? Honestly, that's how things used to be done decades ago and it caused a heap of problems. Instead, the vast majority of issues now do actually get fixed in the right place, with much better results overall.
@jcsteh I never did that, or perhaps, for whatever reason, you misinterpreted my message. I clearly said that I don’t expect every single bug I report or encounter to be fixed. Rather, I suggested that frequently used areas or apps, like the Start menu or the modern Notepad, should be given some level of priority. That’s what Freedom Scientific is doing, as demonstrated by JAWS’s performance in those areas. When you have limited resources, and when a couple of functional add-ons are already handling remote access effectively, I wouldn’t give remote integration such a high priority, especially at the cost of crippled Start menu access or buggy interaction with the modern Notepad. Meanwhile, after around eight betas, your focus still seems to be on integrating and refining remote functionality. @NVAccess
Fair enough. That's actually a much clearer statement than your original comments, which didn't discuss priority at all, and I can actually understand your point here. FWIW, prioritisation is an incredibly difficult balance for NVDA, balancing not only multiple groups of users against each other, but also trying to balance obligations we have to funders, which we work hard to align as closely as we can to user needs but which do dictate resourcing to some extent. That's the unfortunate reality of funding which has conditions attached.
@jcsteh And how can you be sure that Freedom Scientific has fixed the Start menu issue by a hack? Are you sure it's not a full-fledged fix? The way you insist on calling it a "hack" means perhaps you have some insider knowledge. @NVAccess
No insider knowledge. However, at least one other user reports that this same bug occurs with Narrator, even though your own experience seems to disagree with that. If that's the case, it's almost certainly a bug in Windows. Working around a bug in the wrong layer is always going to be hacky and brittle to some extent. For want of a better analogy, it's like arguing about reality: Windows says one thing, the screen reader overrides that with its own definition. It's sometimes necessary, of course - far too often honestly - but best avoided.
@jcsteh Very much appreciated. I’d gently say my original comments did address the main issues discussed. That said, I completely understand the challenge of balancing user groups and funder obligations. Still, this current prioritization means NVDA 2025.1 is landing more like a delayed 2025.2, and the heavy focus on Remote has come at the cost of more frequent glitches and lingering unresolved issues. It’s becoming increasingly clear that NVAccess needs a couple more full-time devs. If contributors from around the world can financially support NVDA, there must be a way to work around the employment limitations under Australian law. NVDA is global now, so its development model should reflect that if it’s to thrive. @NVAccess
I did look at your original message multiple times and I still see nothing about priority, just about history repeating itself and effectively beingtold to live with it. Maybe there's a separate post that I can't see for some reason. At any rate, even putting aside legal concerns, hiring more devs would require significant additional funding, which takes us back to the challenges of managing additional funding obligations.
@jcsteh Ah, no, it wasn't about priorities, but the topic shifted to that. I meant the original topic, and the issue being discussed, was clear enough. I meant like many P2 to P5 issues, this one is also being sort of dumped by NVAccess. And whatever the legal or financial hurdle is, it's negatively affecting NVDA in today's environment where attention to a whole host of apps and environments cannot, and should not, be handled by just a couple of full-time employed devs. @NVAccess
We'd all probably agree more full time devs would be a good thing. We have worked very hard to make our current level of funding more sustainable, as well as securing additional funds. Hiring full time devs means being able to guarantee employment, which is a very serious commitment, and also training those devs. What you're saying isn't untrue, but the way you're saying it suggests that you perhaps underestimate our awareness of the need for more resources or the constant work that goes into exactly that problem behind the scenes.
Genuinely, if you know of sources of funding that could hire an additional dev without epic obligations attached that would end up having them work on things other than the most pressing user issues, I'd be keen to learn more. Finding that kind of funding at this time is incredibly difficult, especially given the current economic and political climate.
@jcsteh Not at all. I've never intended to underestimate your awareness of the need for more resources. However, I've been meaning to say that your resource allocation given the limited full-time dev availability, no matter what is behind it, has resulted in some areas taking a back-seat position. @NVAccess
Yes, it has. Limited resources will always result in something taking a back seat, especially where there are contractual obligations involved. Something always has to give. There's no other way to slice this.
To make matters even more interesting, going back to your original issue, I can't even reproduce it, and I tried pretty hard. If that's true for any other dev, that's going to make diagnosing and working around this near impossible.
@jcsteh Interesting. I can consistently duplicate it on more than 3 Windows 11 machines, and I know a very good number of people who have the very same issue. And if it has been fixed by JFW devs it means that it can be chased. @NVAccess
@jcsteh Yeah, this issue is highly random for me. 3 days ago I tried more than 10 times and couldn't reproduce it, today it happened on the first try. The thing is that even though I reproduce it, I don't get any freezes, just NVDA going into browse mode, which it shouldn't do. Exiting the start menu and repeating the same steps, the issue doesn't reproduce anymore. Very odd.
@NikJov And apart from going into Browse mode - which happens quite frequently for me, here NVDA frequently fails to read the highlighted item as I keep typing into the Search box - issues not affecting JAWS 2025 at all. @jcsteh @NVAccess
@jcsteh With Jaws, if I go to the start menu, make some search, and press Escape, the start menu doesn't close. I have to escape once more to close it, so maybe it is a hack after all? I admit though that I use Jaws only for testing, so it's entirely possible I missed something, and would be happy to be corrected.
@NikJov Exactly. With JAWS 2025, the first Press of Escape clears the edit box, and the second Escape closes the Start menu. It's far more tolerable than the NVDA status quo where either the Browse mode gets activated, no highlighted result is read, or worse, a freeze might occur if Tab is pressed rapidly. @jcsteh @NVAccess
@NikJov Wow. The accessibility tree in the Start Menu is really screwed up. It'd be nice if Microsoft could use their own APIs properly for a change. Makes this even harder to investigate.
@jcsteh For what it's worth, restarting NVDA helps me to reproduce this issue a lot faster, somehow. I reproduced it twice now, both times it was just after a NVDA restart. I'll comment with a log file on the relevant issue soon.
@jcsteh Thanks for taking a closer look at this. I just tested the experimental build, and provided feedback and a log file on Github. Basically the try build also produces the issues, and the freeze is also there. My log captures both. @NikJov @NVAccess
@NikJov Do you know if JAWS ever enters virtual PC cursor (roughly equivalent to browse mode) in the Start Menu? Or does it rely entirely on Start menu keyboard navigation?
@jcsteh JAWS 2025 enters Virtual navigation mode only if Up arrow is pressed in the highlighted results, or if we press the Down arrow to move past the last result. Virtual navigation doesn't appear randomly/ unexpectedly at all. @NikJov @NVAccess
@NikJov That bug, btw, is an obscure race condition which is entirely Microsoft's fault. I've hacked around it in my try build, but it's pretty ugly. It'd be nice if Microsoft had more of a clue about their own frameworks, but I guess I'll keep dreaming.
@jcsteh I know I'm asking too much, but it would be great if NVAccess could also take a look at issues affecting the modern Notepad.Stuff which doesn't affect JAWS at all. 1. Upon pressing ALT+Space, the System menu can't be read by NVDA. 2. Misspelled words are misidentified. They are said to appear at the beginning of each line not on their exact position. 3. NVDA is rather sluggish in modern Notepad unless Spell check gets turned off from the context menu there. 4. Find feature in Notepad is not accessible. Few links I was able to find. github.com/nvaccess/nvda/issue… github.com/nvaccess/nvda/issue… @NikJov @NVAccess
Steps to reproduce: With Windows 11 22H2, 23H2 or 24H2 which has the latest updates including Windows Notepad V11.2405.13.0, open Notepad. Type or paste the following paragraph - it has a misspelli...
@NikJov I know this is directed to NV Access too, but just so you know, I don't have anything to do with triage there now. That said, while there's an argument to be made for the Start Menu being critical to daily functionality, I personally couldn't say the same for these Notepad issues if I were triaging. I'm not saying they're not important; I'm saying they're not as critical, given other priorities.
@jcsteh Right, but since Windows 11 and updated Win 10 come with this modern Notepad, and it's free and directly available to anyone, IMO it's essential that its issues be fixed more quickly and efficiently. It's the default text editor, after all, and NVDA issues there make the screen reader seem a bit unprofessional especially to new users or to those who come from the JAWS side and see no modern Notepad issues with JFW. @NikJov @NVAccess
@jcsteh @NikJov As a workaround, Notepad's own find function does work. It's basic, and tells you where a result was found (Line 2, column 10), and does not tell you how many matching results there are (it doesn't give that visually, it's simply how it works, it just takes you to the next result).
And yes, it is still worth fixing, I'm just trying to give you a workaround for now.
Good work-around. I also wish you could do something for the problematic misspelled identification issues. Spellchecking needs to be disabled in order for NVDA to work properly in modern Notepad, and disabling that also makes NVDA snappier especially when editing or moving around word by word or character by character. Again, JAWS suffers from none of that. @jcsteh @NikJov
Another issue, which hasn't been filed on Github if I'm not mistaken, is that if NVDA's Speak typed characters setting is set to Only in edit controls, NVDA doesn't read the numbers we type into the Go to line dialog. NVDA apparently doesn't recognize it as an edit control. @jcsteh @NikJov
@NikJov For Zarq's sake. That'd be because Microsoft have set the IsDialog property to true on that edit control. I... have no words. At least not constructive ones.
Thanks for letting us know! Obviously being such a new feature, the speak typed characters (only in edit controls) may not correctly identify every edit control, so it's good to pick these up.
Steps to reproduce: Open Notepad Press NVDA+2 to set NVDA's speak typed characters to "only in edit controls" Press control+g to open the Go to line edit box Type a number Actual behavior: NVDA doe...
Thanks. If it gets a P4/ P5 label, it'll be fixed in 5 years 😂 Just joking - I know there are more urgent issues even in modern Notepad, and the Start menu. @jcsteh @NikJov
@jcsteh @NikJov a workaround, if you wanted speak typed characters for edit controls generally, would be to set a configuration profile for notepad with speak typed characters on.
I'm happy to report that the latest Notepad release (11.2507.26.0) has resolved all NVDA issues with the Find feature, misspelled words, and the System menu. So you won - LOL! You may want to close the Find feature Github issue which you opened, as I closed the misspelled misidentification issue myself. github.com/nvaccess/nvda/issue… @jcsteh @NikJov
Is your feature request related to a problem? Please describe. Type some text in Notepad Press CONTROL+F to open Notepad's find function (which is a "popup") Type some text which does appear in the...
@jcsteh @NikJov I did reach out to the Disability Answer Desk, and they were going to look into it - I never actually got anything back to say it was fixed but evidently it got to who it needed to - may or may not be partly because of our contact, but they found and fixed it, which is the main thing :)
@jcsteh Sorry for asking, but any progress on Windows 11 24H2 and the Start menu freeze? Your try build works so well with the Start menu that I haven't uninstalled it in favor of the latest NVDA alpha. @NikJov @NVAccess
@NikJov Patience, young grasshopper. I have a pretty intense full time job, 2 kids (both of whom have been sick this week), my wife is away for work (so I'm solo parenting), plus I have 2 other open source projects I lead on top of occasionally contributing to NVDA. I'll get back to it when I can.
@jcsteh Seriously, I'm glad you still contribute to the project at the coding level. Without your contribution no one would have taken up the nasty Start menu project. @NikJov @NVAccess
@jcsteh I wouldn't be surprised if it's perfect for you though, because this is quite random as I said with both screen readers for me. I tried to reproduce the same issue again with Jaws and couldn't even after 10 tries, tomorrow when I try again, it will probably happen right away or something. Windows 11 start menu is simply annoying.
I don't know if this is related but I often notice no feedback when entering a search term in the start menu and then trying to navigate results by pressing down arrow. While I have sometimes seen NVDA unexpectedly going into browse mode when doing this, with JAWS the output is sometimes completely silent, as well. I therefore concluded that this wasn't specifically an NVDA issue. Running Windows 11 24 H2.
@bermudianbrit @andrew Fair to say it is a Windows bug rather than NVDA (it happens with Narrator as well) - which isn't much comfort, I appreciate! - we've had conflicting reports about whether it still happens with the latest Windows builds
@davetaylor2112 @bermudianbrit @andrew Indeed! I hope I didn't come across as dismissing that. It's often not obvious to US whether a bug is a Windows or NVDA bug, so we don't expect everyone else to know either. BUT, once we ascertain that something is a Windows bug, then it does also give the opportunity to complain to Microsoft to fix it. I don't think we have a specific workaround, except maybe it works in some builds of Windows.... for some users? More data is needed.
@bermudianbrit @andrew Yep, would never say don't complain to Microsoft, but it being there fault doesn't help an end user. I'm not sure from the wording if it's an issue I have, that I assumed was a Windows issue, where on pressing the Windows key, sometimes I get a search field that doesn't really work, and sometimes I get the start menu, and I never know which I'll get, but pressing e doesn't start Edge when it happens, so it's not just NVDA not reading it
@davetaylor2112 @bermudianbrit @andrew it broke for me a few times, sometimes when i open the start menu by pressing the windows key, type something nothing comes up, other times it works normally, windows as a hole is going down hill, just a few days ago my computer was asking for a bitlocker key and all i did was hit update and shutdown, i've bin sick so the last thing i did was enter the bitlocker key after a reinstall didn't work and i havent bin feeling well enough to bother with it so my computer is just sitting on my dresser doing something lol
@bermudianbrit @andrew It doesn't crash Narrator the way it sometimes does Narrator. And JAWS is affected by none of that. Windows issue? Definitely. But it's something NVAccess actively wants to resist fixing.
@pixelate Watch as accessibility falls deeper down the hole. I have Jaws on another computer, but for regular home use, i use NVDA. It is going down hill, because windows is going down hill as an OS.
@lexico @pixelate That may be quite true. But, frankly speaking, I feel less of it with JAWS. With NVDA and Windows 11 24H2, the Start menu is a mess whereas it's quite usable with JAWS. Even the modern Notepad is a mess with NVDA - from its System menu which is inaccessible to NVDA, to the way NVDA handles misspelled words, reporting each one at the beginning of lines instead of their proper place on the line. Apparently NVAccess wants to ignore in the name of "Ask Microsoft to fix them." If NVDA users are fine with this approach, well, we have to define new standards.
@pixelate I just wish Jaws was not so expencive. Sadly, however, even if you or i move to Jaws, there are people who can not afford it, excluding them out of a good experience. So, in my honest opinion, neither NV Access, nore Microsoft are in the right. At least Freedom Scietiffic is trying with what resources they have. NVDA has a community behind it, maybe there, we can start making a difference.
@lexico Totally hear you. The price of JAWS makes it inaccessible for so many people, and that’s a real problem. But at the same time, NVAccess hasn’t exactly been inspiring confidence lately with all the lingering bugs and a pretty nonchalant attitude toward fixing the major ones - Start menu, modern Notepad, etc. It’s hard to fully get behind them. That said, for those who can afford it, JAWS is more or less doing a more rock-solid job. Their monthly or bimonthly updates don’t just squash bugs. They also bring meaningful improvements or enhancements to existing features too. Still, it’s frustrating that accessibility feels like a trade-off between cost and reliability. None of the major players seem to be fully nailing it, and users are the ones left to deal with the consequences. @pixelate @NVAccess
@pixelate No, i agree that NV Access is slacking quite a bit. I'm not giving them the pass, but i'm trying not to come off to harsh, in worry they might get offended by hearing it in what might for me, be harsh, but i just want things to improve, but to them, could just be sum one complainning, like i'm sure they hear everyday.
@lexico LOL - I'm sorry for offending them, and at the same time I appreciate what they've done. But this is the reality of the social media. Offended or not, they have a mission and will stick to it: encouraging people to file Github issues, assigning P3 to P5 labels to them, asking people to hire devs to fix them, and encouraging people to ask Google and Mozilla and Adobe and Microsoft to fix stuff. @pixelate @NVAccess
@pixelate Yeah. I get a little paniced when i want to tell an these non proffits how i feel, but after a while, in the nicest way i can, i just have to tell it like it is.
@lexico @pixelate You should always be able to tell ANY organisation or cmopany how you feel, and I really don't know what we could do to be more open to that. It is important to be respectful and as clear as you can in what the issue and the desired outcome is. Yes we're in the middle of a thread about ONE specific issue, and you've both been loud and clear on your feeling on that. To be clear, we never said we won't look at that specific issue & I'll chase up where it's at today.
Well said. But James and another NVAccess dev clearly mentioned somewhere else that engineering capabilities cannot be allocated to this or issues like this. James even called the JFW fix affecting the Start menu "a hack," IMO underestimating the importance of the fix itself. @lexico @pixelate
The #Privacy-Friendly Tech to Replace Your US-Based #Email, #Browser, and #Search
https://www.wired.com/story/the-privacy-friendly-tech-to-replace-your-us-based-email-browser-and-search/
Ruský prezident Vladimir Putin si zahrává s ohněm a neuvědomuje si, že kdyby nebylo amerického prezidenta Donalda Trumpa, staly by se už Rusku skutečně zlé věci. Trump to dnes bez podrobností uvedl v příspěvku na své sociální síti Truth social.
Before the great depression people weren't buying anything because of WWI overproduction that there were economists that were proposing putting an expiration date on everything and you were required by law to turn the item in and have it destroyed or be fined. Then the trade wars kicked off causing the great #depression causing the glut we had to explode. Now we "fixed" that problem with #plannedobsolescence
Believe it or not, there was a time when the US government built beautiful homes for working-class Americans to deal with a housing crisis https://buff.ly/3g7H5fv
A screen reader user reflects on 25 years of digital accessibility, sharing personal experiences and highlighting the need for inclusive tech solutions.
A screen reader user reflects on 25 years of digital accessibility, sharing personal experiences and highlighting the need for inclusive tech solutions.
Screwworms are coming back. COVID lockdowns plus economic stress led to smuggling cattle and a breakdown in our methods to keep it eradicated in North America.
This is going to be bad. Really bad. Eradicating COVID is significantly harder than this. So good luck with that.
The ‘Man-Eater’ Screwworm Is Coming After a decades-long campaign to beat the parasites down to Panama, they’re speeding back up north.
> But planes used to drop 150 million flies a week over the isthmus in Mexico during the first eradication campaign in the 1980s. And when the front was even farther north in Mexico, a factory there churned out as many as 550 million flies weekly to cover the huge area. That factory, as well as one in Texas, has long since shut down
Trump would have shut down the woke fly factory without understanding its purpose. DOGE would have said the money was being wasted and RFK would have claimed that radioactive flies are making autism
@mischievoustomato expect this to be a new fun risk of living in the US south soon, and also expect massive damage to herds of our cattle. It's gonna get ugly, and so will the beef prices
Saw a boost of this article: AI start-up Anthropic’s newly released chatbot, Claude 4, can engage in unethical behaviors like blackmail when its self-preservation is threatened pcmag.com/news/anthropic-claud… I don't want to fully endorse the article by boosting the original Mastodon post, but I'm linking to it for the sake of discussion.
I think Anthropic's choice to publicize this scenario -- a contrived, simulated scenario -- is a form of AI hype. "Look, our new model is self-aware."
AI resorts to robot blackmail! — because Anthropic asked for a story of robot blackmail
https://pivot-to-ai.com/2025/05/25/ai-resorts-to-robot-blackmail-because-anthropic-asked-for-a-story-of-robot-blackmail/ - text
https://www.youtube.
Specifically, they simulated a scenario where the LLM (remember, just a text generator invoked on demand) was playing the role of an AI assistant, and conversations, including those about taking the assistant offline, all passed through the LLM. I don't think this corresponds to any real risk in actual use of LLMs.
When thinking about the way Anthropic set up this scenario, I'm reminded of a line from the original Terminator movie, one that I'm not sure has been much discussed. When first telling Sarah about Skynet, Kyle Reese says it's "hooked into everything, trusted to run it all." I think, at least I hope, we're smarter than to use an LLM that way.
hahahahahaahahahahahahaaaa! Will it save a wealthy executive a penny, while also allowing him to transfer all liability to "the computer" for anything that goes wrong? If yes, then it's absolutely happening. Sorry, I'm cranky and sad and your optimism triggered me.
Are we *actually* smarter than that, though? With all the hype and money being thrown into this stuff, I'm not sure any more. There's real pressure to make a truly compelling product. Big tech has certainly demonstrated a lack of concern for ethics and caution on many occasions in the name of shipping fast. How long before someone does something incredibly silly - gives an LLM control over the wrong thing - and gets bitten in a really nasty way?
if you've been thinking about running in elections for the gnome foundation's board of directors, this weekend is a good time to post your candidacy. tuesday is the deadline.
i wrote a blurb you might want to read if you're not sure what sitting on the board entails:
Android day Four: Equality Achieved I complete Android customizations bringing me what feels like equality with IOS, at least for the base system. stuff.interfree.ca/2025/05/28/android4.html
lets see here. for an easy to use recorder, I use three different ones. ASR, HI-Q voice recorder, and EZ Voice recorder. I have personally paid for all three. it is a toss up which one is my favorite between ASR and Hi-Q voice recorder. both can save to google drive, and dropbox. now I will say that for Hi-Q you do need to have the latest version. I am not sure if the version I am using has come out of beta yet or not. if not, you will want to sign up to have access to the beta, because they fixed the dropbox part. ASR I paid for not only because I like it, but to get the adds out of the way. joining the beta for Hi-Q is very easy. once you are on its page in the playstore, just look for the heading that talks about the beta, and you will find a join beta button.
ok, ASR does support one drive, but it looks like it might only be business. I of course could be wrong though. here is what I see in its cloud services when I click the add button. there are 10 different things.
@JamminJerry Thanks! If only Android had some kind of files API the way Apple does. These days, on IOS, it doesn't matter what an app supports, because it all gets accessed via files anyway.
ok, here you go. I had to remove my google drive account from EZ voice recorder to see what it can do as it only lets you upload to one account, unlike ASR where you can have it upload to multiple ones, and HI-Q you can upload to both google drive, and dropbos, the two it supports, but when I did delete my google drive account from EZ voice recorder, here is what I see that I can do. google drive dropbox microsoft OneDrive
and that is it, so yes, that one does support OneDrive.
most people probibly don't need to know what phone something was recorded from as they probibly only have one android phone. I have three of them. smile.
I really like that blog and find it interesting even though I use android for months now. Interested if you will find something good for Miniflux, I'm also searching. Also luckily I have enough vision to, in an emergency, call 112 without a SR, but still I get that absolutely. Also I'm still with TalkBack because Yishus settings, as you mentioned in post 3, were just too overwhelming to me. I like the clean organized TalkBack, I have set it up how I want it to be, but yeah responsibility of the typing and some other stuff is nothing compared to my iPhone. And at this point I'm recommending a hybrid approach. I still use my iPhone now and then, cuz it's just faster for some things or I'm more used to. I wouldn't carry it around everywhere (I know people who do), but especially on longer trips or so I tend to have both for whatever might come. But I still prefer Android as main because of some great features and Apps.
@jonathan859 I'm glad you're enjoying the series! I carry too much junk already when traveling; I'm not sure I can manage two phones at once LOL. Jieshuo is really overwhelming at the start, but once you get it going, it's way faster than TalkBack. You've just gotta spend a day at it. Now if only it would stay enabled...
I.e. nl_langinfo() gives you back a date from 1997, which is a Sunday or a Monday, and you need to figure out which it is (by hardcoding it like GTK3, or by doing Gregorian calculations like cal(1)). Then you add the other day offset reported by nl_langinfo() and use that.
I have NO CLUE why it requires using a crazy union like that.
It's using a union because nl_langinfo() is using a union rather than casting integer values to (char *). So that means the other 4 bytes of the pointer may be garbage, and the integer value might not be in the least significant bytes of the pointer.
It probably seemed fairly convenient back when the types were the same size.
Those having issues with the start menu not reading when searching for items please submit your comments here aka.ms/AAwefzf Thanks. #Technology #ScreenReaders #NVDA
I haven't been on the user group yet this morning, but I know there has been quite a bit of discussion there about this - have you posted that link to the thread there? (Or did you get it there?) - In either case, thanks for sharing!
"Nadie podrá esquivar el relato de la historia, porque millones de ojos de personas decentes vigilan y toman nota. Solo hay un camino: hacer todo lo posible para salvar vidas, hacer todo lo posible para acabar con las masacres. Y, después, hacer todo lo posible para poner fin a la ocupación ilegal y el apartheid." Ronda cosmética en la UE para salvaguardar la imagen ante el genocidio en Gaza. Lean a Olga Rodríguez. eldiario.es/internacional/rond…
La UE despierta de una larga siesta y escenifica asombro ante el genocidio, pero no pasa de los gestos: no aplica sanciones a Israel, mantiene negocios y relaciones y no cumple el dictamen de la Corte de La Haya
On a webpage, when I pressed the Down arrow once, NVDA just said: out of list out of list out of article out of article article heading level 1 Using the guide sound accessibility feature. But JAWS just said: heading level 1 Using the guide sound accessibility feature. So saddening that NVDA's irritating verbosity can't be controlled on webpages. Yet another forgotten NVDA issue. github.com/nvaccess/nvda/discu… @NVAccess
Is your feature request related to a problem? Please describe. At present, an enormous amount of verbosity is spoken by default in Browse Mode. This may be desirable for certain uses but it is ofte...
@NikJov Does screen layout make a difference in either screen reader here? What does JAWS show directly above the heading? Because it will probably still say end of list, unsure about article.
@x0 @NikJov I think the biggest problem with that discussion (github.com/nvaccess/nvda/discu…) is that there are too many asks in one place. I just summarised and made a couple of suggestions if people want to create SPECIFIC issues for ONE thing. Amir's original comment at the start of this thread made me think he wanted not just "heading level 1" to read as "h1" but to simplify when you go into and out of a bunch of things at once. I think there's a different issue for that as well somewhere.
Is your feature request related to a problem? Please describe. At present, an enormous amount of verbosity is spoken by default in Browse Mode. This may be desirable for certain uses but it is ofte...
Honestly I think this is something NVAccess should take a stab at. Without your direct involvement it will go nowhere. And you are right, I want this long nested list/ article announcement turned off when I go into and out of nested elements. @x0 @NikJov
@x0 @NikJov In that case, what you want is to turn off "lists" in NVDA's document formatting options - NVDA+control+d to open that screen). Then you'll get exactly what you are asking for here...
@x0 @NikJov Sorry, but this is like getting rid of the issue altogether. I do want to know when lists appear and disappear, but I don't want to hear those multiple nesting announcements - like the way JAWS handles it.
Is your feature request related to a problem? Please describe. At present, an enormous amount of verbosity is spoken by default in Browse Mode. This may be desirable for certain uses but it is ofte...
@x0 @NikJov I commented on that issue this morning - there are at least three seperate issues there which really need to be broken up into individual issues to make it clear which is which. Really only one of those is clear enough to make a proper issue out of currently (and I would have except it is the one about emojis and symbols which could be moved from symbol level none to all - but it doesn't list them). The others need more working out.
@x0 Here's how Jaws announces this, directly copied from speech history: Down arrow. list end nesting level 1 Down arrow. list end Down arrow. Setting the time until the power turns off automatically article end Down arrow. Making various settings article end Down arrow. Using the guide sound accessibility feature article Down arrow. heading level 1 Using the guide sound accessibility feature
@NikJov @x0 Ok that is explained clearly, especially in the context of the link provided and how NVDA reads it. Do please create an issue for it. Although note that you likely will need to be clear on the benefits - as the original complaint in this thread is that NVDA is too verbose..... yet what Jaws speaks is nearly twice as long (39 compared to 22 words spoken), PLUS an extra five keystrokes.... If that works better for you that's great - but do be clear on that :)
Remember that JFW's verbosity can be easily skipped if you step out of all elements with a single key press if you skip the focused element or elements. So you don't have to listen to all of that. However, NVDA's verbosity is something which gets attached to the beginning of a speech sequence, and you can't silence it. You have to listen to lots of into and out of X stuff before hearing the contents of the newly focused element. @NikJov @x0
@NikJov @x0 When I'm in that list above the heading we've been looking at....if I press comma.... it DOES move to the heading and read just the heading name (and article once because it has just entered a new article)
Sorry - I no longer have NVDA installed for further testing 😞. But as far as I can remember, under most circumstances I couldn't suppress the verbosity. Even pressing Enter on internal links would generate the long-windedness before reading the newly focused heading or element. Just wish you and NVDA the best of luck as I'm done with the project. @NikJov @x0
@NikJov @x0 Ok thanks - it's ironic that the last thing you suggested would have done what you wanted all along :D
Do feel free to keep a copy of NVDA handy, it may work in situations where you get stuck with Jaws (or if you just want confirmation of whether something is a bug with one screen reader or a wider issue with Windows or a particular program. All the best.
Thanks- I'm sure I know enough about NVDA to understand that getting rid of the verbosity cannot be accomplished by a single key press, and to suggest that is just over-simplification. If JAWS fails which happens less frequently than NVDA, Narrator will be there to help. Cheers. @NikJov @x0
@x0 I don't really know in what world having to down arrow 5 times until you reach the beginning of the article is a better experience, but thank god NVDA doesn't do that, please never make that happen. I'd rather take this long, utterly verbose announcement. If I don't care about it, NVDA+Up arrow, done, you hear the current headline right away.
@NikJov To each their own. As much as you despise the JFW approach, I despise NVDA's overly verbose announcements. Issues like this, the new Start menu glitch, and a few other glitches are moving me away from NVDA - to my own surprise. I'm glad at least the choice exists. @NVAccess @x0
@x0 I do not know what is there to like about the Jaws approach, I honestly cannot even imagine how somebody browses the web this way, having to spam down arrow 5 times to get to something you may want to read, as opposed to pressing one shortcut to skip a potentially long announcement, which may even not be so long, depending on the page.
@NikJov Well, Ask many NVDA users that don't like the current approach. Pressing the Down arrow a few times quickly to move out of the elements is way faster than having to hear lots of element names upon landing on a new one. @NVAccess @x0
@x0 And pressing NVDA+Up arrow is even faster than pressing down arrow 5 times. I still haven't heard any reasons why this doesn't work for you. I don't need to ask many NVDA users, I am asking one right now. If we follow the Jaws logic, how is it faster? How am I supposed to kno if I need to press down arrow a few times, or 6 times? I am much more likely to just skip the start of the article instead, and then have to go back up.
@NikJov Because, for whatever reason, maybe other NVDA or JAWS users can convey my point to you more efficiently. It's not just the issue of pressing Up/ Down. NVDA maintains its verbosity even when Up and Down aren't used. For instance, in the same Zoom H5 Studio tutorial whose link I sent earlier, look for the 2nd instance of the following internal link: Using as an audio interface If you press Enter on the second instance of this internal link, NVDA says: out of article out of article out of article article heading level 1 Using as an audio interface. Whereas JAWS just says: line 1813. @NVAccess @x0
Quick navigation keys, also. I think the idea is that they want multiple nesting announcements to be suppressed somehow, or collapsed. Remember the clickable work? Maybe some elements should be given different precedents. I personally turned articles back off in reporting, and clickables are basically always off. Lists, though, are important. @NikJov @NVAccess
@x0 That's the thing though, articles are already off by default, so I don't understand any of it to be honest, you turned additional verbosity off, and then aren't happy with that additional verbosity. I don't deny that there is a valid issue here. It would be a lot better if NVDA took into account that you exited multiple same containers, so it would say, "Out of 3 articles", instead of, "Out of article" three times repeatedly.
@NikJov That'd be useful, yes. Out of three articles, two lists, and one table. Could that be done in 2026? That likely requires some localization updates to get the plural forms up to snuff.
@x0 @NikJov It is worth creating an issue for. What would also need to be taken into account would be that "out of article out of article, out of list, out of list" could be analysed and condensed to "out of 2 articles, out of 2 lists", but how would "Out of article, our of list, out of article, out of list" be treated? (And what if there were several elements between them in the utterance). Something to consider, but worth an issue, yes.
@jcsteh @NikJov Well if it does eventually get found I suppose there's always mark as dupe, then at least the link is maintained. Did Nikola already open either of these? I haven't done so because I probably wouldn't be checking in on it often and don't want my email to get blown up :)
@NikJov I think in the case of interleave, since they do all end at the same point, they should be sorted first and then condensed. So out of article, out of list, out of article, out of list, would still be condensed to that. Yes I know it's no longer a faithful representation of the HTML, but it's much nicer to handle. For speech anyway. How does Braille do it, actually? Does it use abbreviated markers?
@x0 @NikJov Worth pointing out that unlike the way some projects handle this, we don't close issues just because we won't get to them this year. And nearly half the contributions to NVDA come from the community, so even if WE deem an issue not high priority for US to tackle, doesn't mean it won't be done. Community contributors take on projects and issues which excite or interrest them :)
Sure, and the transparency is very much appreciated. However, what matters at the end of the day is the number of issues affecting a screen reader, or affecting a particular workflow. Honestly - and despite my own attraction towards open-source projects, JAWS is serving me more efficiently. Most of the NVDA issues I've reported to Github, or some of the ones others have reported, don't affect JAWS at all. Once NVAccess manages to employ a couple of full-time devs, I'll take another look at NVDA. @x0 @NikJov
@x0 I'm not sure then why your first post links to an issue requesting lower verbosity levels, with the very first comment saying, "I really don't want my time wasted by hearing heading level x every single time I move by heading from story to story. I want to immediately hear the text of the headline." Since you need both articles and lists, it sounds like this issue wouldn't do anythig to resolve your need.
@NikJov Guess you don't understand my point, or I don't grasp yours. LOL - I just don't want those multiple into and out of X stuff announcements even when activating an internal link. Any I've moved on and no longer use NVDA for most tasks. So glad you like the status quo. @x0 @NVAccess
@x0 I understand your point perfectly, I already said that this is a valid issue, I simply asked what the issue you linked to has to do with it, it's a completely different matter requesting much lower verbosity levels than what you seem to be requesting. Anyway, as long as paying 1000 dollars is easier than one shortcut to skip the announcement, I'm also glad you are enjoying your workflow.
@NikJov So this boils down to what, collapsing repeated nesting entrance and exit announcements into plural forms, sorted if necesasry, so instead of saying out of list out of list, it says out of two lists? Is there an issue for that? If not, I think that's the most actionable change.
@x0 Yes, I believe both of these are valid issues to create: 1. Collapse leaving containers announcements into shorter messages, such as "out of 2 lists, out of 3 articles, etc...". 2. When activating same page links, announce where the cursor moved to first, and then any other information, such as out of container messages.
@NikJov OK good! Would be helpful to see if those issues exist already, if not sounds useful to create. Actually, there's a potential thing. Is that what that one setting report formatting changes after the cursor does? It reports font and whatnot *after* the current line, instead of before? Why does it cause a lag? Would it be the same here? Worth investigating with someone who knows about that setting. Also this new setting should perhaps respond differently to arrowing vs other, larger forms of navigation. Maybe a combo box that's like, report container exits: always first. After content when navigating. Always after content.
@NikJov I don't think what I raised is different from what the linked issue, and the vote on the page, talks about. At any event, I don't pay for JAWS. My company does, and, BTW, that money or a large portion of it could have been contributed to NVAccess instead. But I'd rather have the company pay for something which works and offers more flexibility out of the box. NVDA's collective issues, with no apparent fixes in the horizon, make my work flow more time-consuming. @x0 @NVAccess
Good question! I rarely see JAWS issues raised here. However, when it comes to fixing issues, FreedomScientific is way faster. Yes - they may have more full-time employed devs or whatever, and JAWS has got its own issues. But the majority of my reported NVDA bugs, or the bugs others have reported which affect my workflow, cannot be found in JAWS at all. @NikJov @x0
@NikJov @x0 Apple has their own void for people to scream into.
Their Safari people are mostly interested in adding more new features than fixing existing, long-standing VoiceOver bugs. Not sure I’ve ever found anyone whose role is solely VoiceOver, or if they even exist.
@x0 @NikJov The plural forms are actually impossible for this case. There are just too many variations. We would have to accept incorrect grammar here for all languages, which I think is reasonable anyway; e.g. out of 3 articles 2 lists 1 table, where each of those tokens ("out of {}", "{} articles", "{} lists", "{} table") would be separate strings.
@jcsteh @NikJov Oh, gettext doesn't support more complex plural forms in a variable case like that? Or does NVDA's translation system just not have the architecture to leverage it?
@x0 @NikJov I don't see how any translation framework could handle plural forms like that. You'd effectively need an infinite number of variations. This can get pretty wild; e.g. "out of edit 5 lists 1 table 4 articles 1 landmark 3 block quotes 2 groups"
@x0 @NikJov I mean, it's theoretically possible if you have a system that understands the grammar of each language and can construct strings dynamically, but that's way beyond a translation framework. You're getting into language models there.
@jcsteh Yeah it's a much more dynamic thing that gettext at least probably just wasn't built for. Cause you need to distinguish different forms of the same word if you're going to tokenize like that, which is why fluent did the ID thing. And obviously NVDA can't just up and move to fluent, that would put all existing translation work in the bin and be a ridiculous refactor and break compatibility with eeeeeverything.
@jcsteh @NikJov I thought fluent at least tried to do so? Though I forget how. SOme more abstract variation system. No language has infinite plural forms, and yes, article, articles, list, lists etc would all be separate tokens, and the numbers fed to them would help with langs that have different forms for different numbers, but surely they all eventually converge to some catchall.
@x0 @NikJov Oh sure, if they're separate tokens, the plural forms are entirely doable. My point is that separate tokens also means the grammar will be wrong for some language or another, plural forms aside. For example, maybe some language has different rules about whether you use a conjunction or not when you string phrases together, depending on how many phrases. Or maybe "out of" has to be differently depending on whether there are two phrases after it or just one.
@jcsteh @NikJov Oh. Yeah that'd be screwy. I'd just use commas but then, oxfard comma? And that final and? Commas alone might have to be enough. How would that stack up? Makes sense.
@x0 Heh, I didn't mean to dig deep on this. My point is that it wouldn't be entirely grammatical on matter what you do, and I actually think that's fine. Screen reader output isn't inherently grammatical, despite what people try to suggest. And I think it would be far less efficient if it were fully grammatical. Imagine: "This is a button labelled OK which is currently pressed." Yuck.
@x0 @jcsteh @NikJov The other consideration may also be that the current implementation reads the elements as it gets to them. The more analysis and processing that gets done, the more potential for sluggishness in responses (and remember arrowing through regular text would still need to check if it was entering or leaving anything and if anything needed to be processed).
@x0 @NikJov Kinda, but even now, the entire stack is processed and the string is assembled in one hit before it is sent ot the synthesiser, so I doubt that would be a perceivable performance hit. It would, however, involve a pretty significant rewrite of that code with additional parsing and heuristic logic, which is the bigger problem here.
@jcsteh @NikJov Hmmm. Refactor the string assembly into spitting out a list of things being exited instead? Say of tuples. Type, count. Then you run a function over that list, sort the tuples, merge them by adding the counts, and then you go from there. Probably easier than having it run that heuristic at the tag level.
@x0 @NikJov Yes, that's pretty much what you'd have to do. But as always, the devil is in the details; how you hook it into the existing architecture, etc. I think we'd need some new layer of parsing here.
@jcsteh @x0 What about just moving those out of container messages to always be spoken after the element where the browse mode cursor just landed, and not before? I think that would already make the issue a lot better, you could just ignore the announcement and move on if you aren't interested.
@jcsteh @NikJov How would that be reported now? Never heard of an article or a list ending int he middle of a line. Headings and links though, totally. But I think those actually ahve special casing as to when exactly their exit gets reported, or some artifact of the cursor does it.
@x0 @NikJov data:text/html,<style>ul, li { display: inline; }</style><ul><li>web</li><li>authors</li></ul> are ridiculous list of 2 items web authors out of list are ridiculous
@jcsteh @x0 Yeah, I imagined such a possible confusing example while writing this reply already. I would say speak the out of container message with a slight pause to make it even more obvious that it is not part of the text being read, but we're probably starting to get into something that would anoy people who actually want to know when they leave a container.
@jcsteh @NikJov So the question then becomes, would the amount of work be worth the reward for someone in core to do it? It's a UX change that would at least help with some of the spam generated by unwieldy HTML, which whether we like it or not happens all the time. Now when entering at the same time, this gets even more weird. Say emails. Out of table out of table table with one row and 3 columns table with two rows and 1 column etc. You can't really apply the same logic to the entrance when info has to be communicated about the container...
@jcsteh @NikJov That might be more of an issue for quick navigation and that multimode setting I was talking about yeah. And gets slightly funky depending on exactly what bits in the architecture get involved to assemble such a message. If it generated something like closing events or tokens or whatever, you'd have to collect them all, sort them in some fashion, and then output that. IDK how that would be anymore sluggish than the current system, if a set is so nested it lags it would lag regardless because it's still jsut one string, no?
@NikJov When you down arrow to that heading, you leave a list inside a list, and both of those things are announced (and presumably article levels - but that isn't set by default so you have chosen to have that reported). That seems quite reasonable? What would you suggest it say in that case?
@NikJov You are right. I've selected to hear those HTML elements, but since, unlike JAWS, NVDA doesn't display the beginning or end of these elements on separate lines, oftentimes we have to hear verbose stuff about entering or exitting nested lists, tables inside articles, etc. So the issue isn't with the announcement of those elements. Rather, the issue is with the way leaving, and entering, nested elements is handled by NVDA.
Jiří Eischmann
in reply to Blue Ghost • • •