Mastodawn

Quin Mar 3

@fireborn Out of curiosity, What LLM helped you compose this? Editing to be clear that I'm not against AI writing at all, but this is pretty obvious and I'm curious on your tools.

@TheQuinbox I used Claude 4.6 to grammer check and typo check, mostly because I was wviting on my phone. I did notice it stripped out my seperators, which I'm not thrilled about and clearly didn't proof read hard enough.

@fireborn @TheQuinbox huh. the whole flow feels very Claude, but that might just be convergence between your writing style and Claude's

@freya @TheQuinbox I was so incredibly pissed off at all these purely fundimental issues that I was experiencing. I was also tought, long before the advent of AI, that if you want to make a point and really make it understood, you lead with any possible counters or deflections.

I used to be far worse at appearing like an LLM, overuse of bold, ithealic, and blockquotes.

interesting observations though; maybe I should change up how I write to make people less wary of engaging with it.

@fireborn @TheQuinbox oh I'm not at all wary of engaging with it, mind, just observing.

@freya @TheQuinbox one nbof that things that people seem to forget is that AI is trained on a lot of journalistic writing, so anyone who has an appreciation for those styles and rhythms gets compaired to AI. I personally take it as a complement

Devin Prater :blind:Mar 4

@fireborn @GamingWithEars @TheQuinbox @freya So I can just write like ChatGPT and become as popular and cool as you are instantly? :)

@pixelate @GamingWithEars @TheQuinbox @freya Hmm. I'm trying to work out if there is an accusation or sarcasm here or what.

Ra (Freyja) (it/its)𒀭𒈹𒍠𒊩

@fireborn @pixelate @GamingWithEars @TheQuinbox also, random question: do you think I should look into crowdfunding an old pixel to try grapheneOS? Has android fixed the weird talkback lag issues?

@freya @pixelate @GamingWithEars @TheQuinbox It has not. scrolling is as unreliable as it has always been.

Gesture and tap delay has been improved though.

GrapheneOS also does not include a tts engine out of the box of any sort, they say it is coming soon.

@fireborn @pixelate @GamingWithEars @TheQuinbox huh, I never had much of a problem with scrolling, do a momentumised flick and tap when you get to the right point. y'know what has massive delays? fucking blackberry 10 screenreader. that shit is slooooow

@freya @pixelate @GamingWithEars @TheQuinbox The flick to item and then activate navigation method is still rather slow, but you can at least perform a flick right without feeling like it's fighting you.

@fireborn @pixelate @GamingWithEars @TheQuinbox hmm. so it still sorta feels like you;re fighting through sludge? what the fuck why is it like that, do you know, architecturally? is it just because it's using broadcast receivers and intents and stuff instead of having the screenreader just shove its face into the app or whatever like how voiceover does it? or does voiceover not do that

@freya @pixelate @GamingWithEars @TheQuinbox I really can't tell you, considering CSR doesn't have this problem at all, so it can't be an Android limitation. They also did manage to make it better somewhat, so i'd maybe hazard a guess that it has to do with waiting on timeouts or something, or the virtual screen buffer if one exists.

maia // magmaus3 Mar 4

@freya @fireborn @pixelate @TheQuinbox @GamingWithEars afaik graphene doesn't ship with a tts by default, which makes talkback unusable (until installed, which may be difficult without sight)

@maia @fireborn @pixelate @TheQuinbox @GamingWithEars yeah but apparently they have their own now, I just need to wait for it to get integrated into stock images

maia // magmaus3 Mar 4

@freya @fireborn @pixelate @TheQuinbox @GamingWithEars ah, thought it wasn't ready yet

@maia @fireborn @pixelate @TheQuinbox @GamingWithEars they've got it up on github afaik but it hasn't yet been integrated

Joshua Mar 4

@freya @fireborn @pixelate @GamingWithEars @TheQuinbox nope, it's still slow, it doesn't bother me, some people get really bothered by it witch i don't really understand, i'm just happy talkback focus is stable for the most part and doesn't jump or get stuck like voiceover

@J3317 @fireborn @pixelate @GamingWithEars @TheQuinbox talkback? stable? you what, mate?

Devin Prater :blind:Mar 4

@freya @J3317 @fireborn @GamingWithEars @TheQuinbox It bothers me less now that I have Termux and such working at least well enough for me, and Emacs and all that. But I feel like TalkBack is snappier on Samsung phones than Pixels. Also TalkBack's image descriptions are nice icing that I miss the taste of when I pull out the iPhone.

@pixelate @freya @J3317 @GamingWithEars @TheQuinbox purely from my experience and claiming no objective testing at all, I think you're probably right.

I do have to clarify, though, that I'm referring to using the latest version of Google TalkBack (from the Playstore) in both cases. SAMSUNG TalkBack doesn't have the new reduce delay settings, so is objectively worse.