The #Friends Tab seem to be broken on the #Mastodon session with #tweesecake as the tab opens, but nothing appears, even though I am only #following, well, not so many.
I've already had to re-authorize #Tweesecake for both my Mastodon accounts three times in just as many days. Every time I put the computer to sleep and come back to it the next day, reloading previous posts does nothing to catch me up, and my timelines refuse to update until I delete the session and re-add it. I had an issue at one point where switching screenreaders killed the client's ability to speak while in the invisible interface, which I think has gone away, but I sort of wonder if that's what's broken... if my switching screenreaders is still breaking things spectacularly but in a different fashion.

Cette semaine sur Oxytude, Podcast sonnette connectée #Blink et actu des nouvelles technologies et de l'#Accessibilité.

#SuperNova #BookWorm #Soundscape #Android #Slack #PiperTts #Pages #macOS #TweeseCake #Kindle #DRM #XChat #APIDV #ImpotsGouvFr

https://www.oxytude.org

Oxytude – Accessibilité, informatique et nouvelles technologies

What on earth? I just updated #Tweesecake, and now it doesn't read things to me, just their number, and even that is only put on my braille display.
There is quoted post support with #Tweesecake now. Why is it still that with some posts, I get something like "re: insert long URL here, person's comment" and then no reference post? Are there people manually posting in this format? Argh.

Can anyone tell me what on Earth is going on with the new TweeseCake? The update process was very strange. I hit enter, and instead of simply downloading and installing the update, it opened the Windows terminal! I had no idea what I was supposed to do next, since no commands were entered, nor did I hear anything about installation, so I just closed it. Now, it says I'm on the latest version, but most things in my timeline keep showing up as "list item" with nothing being read. This is the second time they made an update and I had to revert back to 0.18. I am genuinely confused as to why it's doing this.

#accessibility #blind #technology #TweeseCake

Oops? looks like #Tweesecake update just broke. I had to remove my account due to corrupted buffers and now I cannot re-add it as the authorization page keeps opening and the client won't accept the given code. I've seen this before wiht other mastodon accounts so not sure what's up. I'm writing from the site for now I guess.
Thanks folks @app especially for lists support! I've been missing it from my old good Twitter times! #Mastodon #Blind #TweeseCake
Not too long after I asked if #Tweesecake had been abandoned, it gets updated. Certainly intriguing, but the keymap used for composing a post in the invisible interface doesn't bring up the new post dialogue. It looks like Windows 11 is grabbing it because I get a notification that comes up which says, "New notification from File Explorer, Error generated while getting the trace." The keystroke I did use for that now changes the nickname for a particular user. I wish there were a way to assign keystrokes from within the app, as those who aren't tech savvy are going to have a really hard time figuring things out. I'm finding I have to use the actual interface more and more for things because of key conflicts with one thing or another, which kinda voids the purpose of having an invisible interface, which is a lot of what I like about TWC and similar clients.
clearing out over two years of irelevant liked mastodon posts, of which I had almost 900 in my favorites buffer. #FastSM is actually letting me do this without it re-buffering on me all the time, unlike #Tweesecake.