Software engineer @pneumasolutions, prolific open-source contributor, wannabe musician, and huge bookworm.
Blind, but I’ve seen more than most. Snarky and strongly opinionated, but friendly by default and always willing to help. Open to disagreement; closed to MAGA.
Views my own.
Antifascist, feminist, pro-choice, etc. Abolish ICE, decentralize power.
If you're a blind Claude Code user, put the following line in your settings.json:
"axScreenReader": true
restart Claude Code, and have your life changed forever. I can now properly review and resume old claude sessions, I don't get endless Unicode symbols spammed at me, I can review the output with my review cursor much easier... OMG this is so nice!
My final grades for the very last college class I ever had to take have now posted.
I'm done. I've graduated. Goodbye college!
RE: @TheQuinbox@dragonscave.space
It's honestly depressing how bad stock TTS APIs are across the board. Paperback on mobile has truly shown me this; I outline how the iOS side of this works in the quoted post, and Android is its own flavor of hacky: we synthesize ahead to temporary WAV files and chain MediaPlayer instances with setNextMediaPlayer() to kill the inter-paragraph silence put there with the stock player. On both platforms, getting a seamless reading experience means treating the system TTS purely as a text-to-speech renderer and building the player yourself.
Been testing document parsing on the evolve's hardware this afternoon. When throwing a massive file like Worm at it, Paperback parses and renders it in 2-3 seconds. Meanwhile, HumanWare's own Victor Reader application hangs for about 45 seconds trying to build out a heavy WebView2 DOM tree before completely choking and throwing a fatal null reference. Even on standard files that do load, the parsing engine in Victor Reader adds strange rendering artifacts: EPUB's and HTML documents get bloated with excess blank lines/indents and collapsed code blocks, while DOCX files drop text nodes entirely, rendering HumanWare's own user manuals as blank lines and empty bullet points. I guess Paperback must be doing something right.
The Second Coming looks a lot more practical than the prophecies suggested. From Uber Eats, no less.
"JESUS is in a Chrysler Town and Country"
Holy crap, turns out there is actually a very big difference between Claude Opus on Pro and Claude Opus on Max. Hot damn, I am actually impressed with Opus on Max, but on Pro it just wasted time. I guess that makes sense from a business perspective, but I wrote off Opus way too quick. I doubt I'll end up keeping Claude Max, I really do not need the 5x usage limits, but figured I'd try it for a month, see how well it works and what Fable's all about etc.
I've once again gotta hand it to HumanWare's technical support department. The USB-C end of my BrailleNote evolve's sharger snapped clean off in the port yesterday, leaving frayed wires atop a laptop charger's cable and a small metal component inside my back USB-C port. Managed to get the metal piece out and unplug the cable as to make it not a fire hazard on my carpet floor, and then I called humanware. Without asking any real probing questions, they had a new charger sent out to me within like 10 minutes. Of course, they asked my serial number, confirmed my address etc., but I expected them to ask me more questions than to just confirm that the top metal bit snapped off before sending me a new cable for free. Great support, not so great joints on the charger, it seems.
Thoughts/feedback wanted! Working through pricing for Paperback across platforms as 0.9.0 gets ever closer. My current thinking is:
- Windows & macOS direct downloads: Free as always from paperback.dev.
- Mac (and maybe Windows?) Stores: ~$10 (for auto-updates & covering dev fees).
- iOS and Android Stores: ~$20 one-time purchase (to support native mobile codebases & dev account costs). Paperback is very much a passion project, so asking even this for any of it feels weird/wrong somehow to me, even if I will be signing the Windows version, have already paid for Apple/Google dev accounts, etc., so want to get community thoughts before going further.
Just found an official Bass Bootcamp set uploaded in 32k mono. Any professional audio engineer who uploads a dubstep set like that deserves to have their master fader permanently locked at -40dB while a 96 kbps MP3 of Crazy Frog loops in their headphones until the end of time.
@twynn@mas.to @Tamasg@mindly.social @Jage@mas.to I love the little catch at the end there:
If Magnifier is running, Windows logo key + hyphen (-) will zoom out Magnifier instead of inserting an en dash.
how about:
We vibe code features in a vacuum and don't ever bother to consider accessibility most of the time, despite even having a new narrator and magnifier feature on this page.
FTFY.