Let's assume that I follow these #hashtags: #unix, #bsd, #netbsd etc. Then for the sake of argument I filter #freebsd. Now if a #toot contains the hashtags #netbsd and #freebsd should I see it in my timeline or not see it? Is there a #mastodon rule or is it a #client-rule?
Gosh though. People are really helping me add engine-level settings, that's exciting I guess. More settings, the better. The more we can expose through things people can tweak, great. I'll also be updating the phoneme editor later on because I like the idea of using a spin-edit box, and auto-defaulting paths, and a few things will be improved. It's also not considering rules when speaking text from language-specific data and that needs fixing. Bugs bugs.
oh good dear God. Now the SAPI wrapper isn't even compiling after I canged some pointer types, oh no. This so far is really a huge huge disaster. Claud to the rescue? ha.
Continue, or "try it now" a popup from Gmail now asks, offering to compose your next message with Gemini. I guess the tiny "x" is the "fuck no" button?
Yesterday I switched to Windows Terminal and PowerShell 7 from the old Windows Console Host and batch syntax, and I do somewhat feel like I've been asleep at the wheel for years.
Proper UTF-8 support, aliases, a profile to configure things at shell startup, command output capture, correct parsing of ANSI escape sequences... In short, things people should expect from a real shell.
Hopefully this doesn't prompt NVDA to start shitting the bed at every opportunity as it apparently does for many others.
It shat the bed for me using CMD, but did so less in terminal. I haven't fully switched though, feel like I know more old fashioned DOS commands than terminal stuff even now.
@FreakyFwoof I think Microsoft is working on it. I formatted 2 months ago and at that time I could not even use Codex interface with it, because it would get lost trying to focus on old lines. Now, it seems to work perfectly fine.
If you know me, you'll know that I'm not a friend of AI - but like the original Luddites I am not against the technology per se, but the use of it to drive an exploitative societal development.
@pluralistic has put it more eloquently than I ever could. So, read this:
Sigh. Since we added a new setting, have eurpod.com/synths/nvSpeechPlayโฆ - especially if you speak Portuguese, it might help. Or maybe it'll screw things up so bad your language won't sound the same. Who knows. Unlucky 13. Guess I wasn't supersticious enough to skip it. Ah well. it ever sounds like thereโs โno diphthong,โ itโs usually because the boundary gap or timing makes the two parts separate, or the glide is too quiet. We just added a setting to skip boundary gaps for vowel-to-vowel transitions, which is basically the diphthong smoother. Dedicated diphthong phonemes are optional and mostly for extra fine control. To use this for your language, toggle segmentBoundarySkipVowelToVowel: true (also default) or false. This should give folks even more control over gaps, and you can mess around with the others in default.yaml for a given language to see if they help change prosody.
Well, no NV Speech Sapi, for anyone. it just crashes when trying to speak, silently, no logs, no dumps, no nothin'. Haha. SAPI engines are hardest to debug. So no SAPI engine for anyone.
Paperback version 0.7.0 is out, with a huge changelog! * Added table support for HTML and XHTML-based documents! Navigate between tables using T and Shift+T, and press Enter to view one in a webview. * Added a basic web rendering feature! Press Ctrl+Shift+V to open the current section of your document in a web-based renderer, useful for content like complex formatting or code samples. * Added a Russian translation, thanks Ruslan Gulmagomedov! * Added a Clear All button to the All Documents dialog. * The update checker now displays release notes when a new version is available. * Updated Serbian translation. * Updated Bosnian translation. * Fixed restoring the window from the system tray. * Fixed Yes/No button translations in confirmation dialogs. * Fixed loading configs when running as administrator. * Fixed comment handling in XML and HTML documents. * Fixed TOC parsing in Epub 2 books. * Fixed navigating to the next item with the same letter in the table of contents. * Fixed the find dialog not hiding properly when using the next/previous buttons. * Fixed epub TOCs occasionally throwing you to the wrong item. * Fixed various whitespace handling issues in XML, HTML, and pre tags. * Fixed off-by-one error in link navigation. * Fixed some books having trailing whitespace on their lines. * Fixed various parser issues. * Bookmark-related menu items are now properly disabled when no document is open. * The elements list is now properly disabled when no document is open. * Improved list handling in various document formats. * Improved the translation workflow for contributors. * Many internal refactors, moving the majority of the applicationโs business logic from C++ to Rust for improved performance and maintainability. Download: paperback.dev/downloads/ Sponsor on GitHub: github.com/sponsors/trypsynth Donate to development through PayPal: paypal.me/tygillespie05 Enjoy!
Fully blind software developer who loves making their own tools to solve problems. Primarily known for Paperback, an accessible and lightning fast ebook/document reader.
I work as an audiobook quality controller. My employer uses ClickUp to manage tasks. Unfortunately, the web interface is unintuitive and inaccessible. It contains unnamed elements, menus that expand in all kinds of ways, and similar issues. I wrote to their developers, but even after years nothing has been fixed. Fortunately, ClickUp has an open API. So I used vibecoding and now I have my own minimalist HTML application that displays my tasks, start and end dates, comments, and attachments, and allows me to post comments. I still canโt change task statuses yetโweโll see if I manage to solve that with the help of GPT. Of course, this is not how a blind person should function in an ideal world, but it is still a way we can help ourselves. That said, I still need a server where my PHP scripts run; it could probably be done with Python as well, but PHP seemed simpler to me since itโs already running on my server. BTW it would be ideal if Clickup api documentation is one simple document which I can throw to gpt but it seems that chatgpt already know how to use it.
the whole ai-bro shtick about "ai democritizes art/programming/writing/etc" seemed always so bs to me, but i couldn't put it into words, but i think i now know how.
ai didn't democritize any of these things. People did. The internet did. if all these things weren't democritized and freely available on the internet before, there wouldn't have been any training data available in the first place.
the one single amazing thing that today's day and age brought us is, that you can learn anything at any time for free at your own pace.
like, you can just sit down, and learn sketching, drawing, programming, writing, basics in electronics, pcb design, singing, instruments, whatever your heart desires and apply and practice these skills. fuck, most devs on fedi are self taught.
the most human thing there is is learning and creativity. the least human thing there is is trying to automate that away.
(not to mention said tech failing at it miserably)
It democratizes it by making it available for the people who can't / don't want to / don't have the time for learning it.
We're already seeing non-programmers successfully create quite substantial coding projects with AI, to an extend which surprises even me, who was a huge proponent for AI in coding from the start.
Same applies to art, there are many people who need or want art (small business owners, hobbyist game creators, wedding organizers, school teachers), but don't have the budget for the real thing.
Of course, many artists and programmers don't want this to happen and try to invent reasons why this is a bad idea, just as phone operators didn't want the phone company to "force" customers to make their own calls, and just as elevator drivers tried to come up with reasons why driverless elevators were unsafe.
I see putting a prompt into AI and hoping that the generated code is correct as a bad idea, especially in complex apps that have long-term maintainability considerations, or when security / money / lives are at stake.
For throwaway projects (think "secret santa style gift exchange for a local community with a few extra constraints, organized by somebody with 0 CS experience", vibe coding is probably fine.
For professional developers, LLMs can still be pretty useful. Even if you have to review the code manually, push back on stupidity, and give it direction on how to do things, not just what to do (which is honestly what I do for production codebases), it's still a force multiplier.
I think we're painfully re-learning the lessons we learned in programming over the last 70 or so years with AI, just like crypto had to painfully re-learn the lessons that trad fi got to learn in the last five hundred years.
Yes, you can 20x your productivity with AI if you stop worrying at all about architecture and coding practices, just like you can 5x your productivity without AI if you do the same thing. Up to a point. Eventually, tech dept will rear its ugly head, and the initial gains in productivity will be lost due to the bad architectural decisions. Sometimes that
sometimes that's the right call, particularly when you want to find out what users like and you don't yet know what you're building. It very often isn't.
My guess is that, if I talk about agape with a Christian who voted for Donald Tramp, then they'll look at me a gape, and they'll have no idea what I'm talking about.
feld
in reply to arosano ๐ฉ๐ฐ ๐ฎ๐ฑ • • •this is an impossible problem to solve for everyone so it HAS to be configurable. Otherwise if you want to abuse people it's too easy.
*posts gore image*
#death #destruction #blood #murder #puppies
oh great someone wanted #puppies but not gore on their timeline, but now they get gore?