Lol.

So at this point, I seriously think it would be good to find another name for the screen reader. Not only is it personally hard to remember for me and as such probably a good number of people, but apparently there are already a lot of big projects with the exact same name. This isn't like NVDA where it sounds really close to Nvidia, and sometimes has the same acronym. There are projects that have the exact same name and the exact same idea behind the name. If you look up Yggdrasil on Github, you will find multiple hits.
It's not a bad name. What's bad is when the name is so frustrating that it's easier to call it "That Screen Reader" or "That Linux Screen Reader" or "That Linux Screen Reader That Isn't Orca". I find myself doing that a lot. Plus, I don't think a huge company would be too happy to find out that someone's using their official name for their own product. Plus, from the perspective of a starter translator, that name is going to be a nightmare to try and translate or even pronounce in other languages.It's hard for me to pronounce and remember in English, which I'm a native speaker of.
Even YSR or LSR seems good enough. Like I said before, sometimes simple is just the way to go.

actually, we are seriously thinking about doing that, since we have problems getting a domain with yggdrasil, it's actually kinda expensive. We're doing the custom domain thingy because we want to be able to have an organisation email where people could contact us, plus not be restricted by the github pages static site thing, we will probably make it easier for us to post news and so on, plus the community will then be able to get notified, either through rss feeds, mail or whatever else. Plus, perhaps we're gonna have a forum one day, so this has to happen eventually.
I enabled github discussions on the prototype repo, be ready to vote soon, when it will appear.
btw, @Dan Gero, we included blab in there, though as an acronim, blind linux accessibility bridge, that seemns more cool than the other aspect of the word.

@bgt lover, I still think the name is what made the screen reader so special, and that you should give it some time, as it isn't even the second prototipe for people to start actually recognising the name and what it means.

Please don't change the name. I doubt anyone is going to file trademark disputes or anything like that. There are lots of projects on GH with the same name.

Actually, I just heard a cool suggestion that's even better than Blab. It's unique, it's not really taken on Github, it's short, it's easy to pronounce, and it'll be easier for me to translate into other languages such as Japanese since you usually write names in Katakana. The name suggestion was Vocem, which apparently is Latin for voice.

So I guess I'm in the minority here, but I do actually see their point, fallacious comparison of non-AT-related activities on other OS's aside. To be clear, what we have currently *is* terrible, you'll get no argument from me there. However, it would seem that at this point, figuring out how Orca works (and documenting it) would be a more productive use of time, rather than rewriting *everything* (including AT-SPI bindings!) in Rust right from the get-go. A rewrite of Orca may well be necessary, and if so, having a good understanding of how it works would put you in a great position to make a document/statement outlining exactly what needs to change, and why. You could then, presumably, have the (very few) other developers who work on Linux AT on board, which would be better for everyone. At the very least, it would be a learning experience, since you guys seem to be sort of winging it at the moment. Just my two cents, and I do wish you luck with the project if it continues.

thanks for your opinions, the pole will be up shortly, so everyone, please cast your votes. I will post here again when it becomes active. Or even better, follow the github discussion section of the yggdrasil-prototype to find about it first.
@65, it's not a reinventing of the wheel because we want, we think we discovered america and want to show it to the entire world or something. It happens because we believe rewriting it from scratch may be beneficial both from a performance standpoint and to the a11y stack itself, since we might discover fundamental issues with how things are done now, things orca took for granted all those years.
Actually, I'm giving this example a lot lately, but what's happening with YSR and orca is in many ways similar to what happened with commentary and talkback on android, jaws and nvda, etc, a necessary reinventing of the wheel.
Why I don't contribute to orca? Simple, first I don't understand orca's code and logic, things are undocumented enough and coded in such a way that I'd spend more time trying to piece it all together from orca source code than wandering on my own and trying things untill it works, that's why we decided it's best to try it our way, and only if we can't, read orca source code...if we can find the relevant section that is. We are more baffled by the source of orca than the atspi C api and documentation we have in the man pages, and that's saying something.
I mean, we would surely love to contribute to orca if the code was a bit more self-explaining and well structured, or if there would exist some kind of document describing the principles behind which the orca screen reader took form, we coded, prodded and pulled untill it worked is not a valid enough explanation. It would be enough if there were mentors telling us where we could find what parts of orca, what does a particular directory contain, how it relates to everything else. Hell, even a document describing that would be enough, but we don't have it.
So, in stead of either pane-stakingly figuring it out our selfs or waiting for someone to explain how it all works, we decided we'll try our hand at this and see what comes out, it appears to work so far.
again, the time of truth is now, we incourage everyone who wants their opinions to matter in the final decision to cast their votes, this hard crossing can't be taken without a bit of help from the community. Remember, the winner will have more of a weight in the final name than everything else.

Oh, and also…
イグドラシル
ボシム
For anyone who can read those Japanese words out loud, I invite you to do so, then come back here and tell me which word was easier to say. Might be because Japanese isn't my native language, but it took me like 5 seconds to read the first word. The second word was much easier to both speak and write.

@Dan Gero Because, Yggdrasil has an actual meaning behind it, other than just being a voice or another word for  the word talk. Blab is blind linux accessibility bridge, but on the surface, what do you think it means? The screen reader is speaking, talking, no, just blabbing to the user. It's like someone saw the name Yggdrasil, and just stripped compleet meaning from the screen reader.

I have a japanese voice for my NVDA and it can't read the words, sorry. Would love to give it a go, cause I am learning