The thing with Cadence is, you have gutters (gaps) between Braille Cells. Anyone owning the Monarch or DotPad can correct me if I'm wrong, but they do not do gaps between the cells going horizontally, that is, all cells are filled in equidistantly close together.
Cadence does divide them into 12 distinct blocks. This means, if you displayed a graphic, it can only go uninterrupted vertically, that is, going down.
This means that for motion-graphics, where it moves or changes in a specific region of the display, Cadence can work great. For graphics that are maps, drawings and need no column breaks, it just won't look like a graphic, or not a true one.
I believe DotPad and Monarch let you display Braille, but that they create virtual gutters. That is, waste pins to add the gap for you. Again, I might be wrong on this.
I purchased Cadence not exclusively for graphics, but multiline text, superb battery, and light weight for both. For seamless graphics I still do have an embosser, and that one can do graphic height too, something DotPad wouldn't anyway.
in reply to Jage

@Jage yeah but, thing is too, on those displays you can draw a full circle that's uninterrupted, I bet. and when all cells are up (display off), it looks like a straight grid of cells without any gaps. At least that's the perception I'm getting as far as how differences are. I just couldn't get behind 2.6 pounds of weight, which isn't horrifying like graphiti plus is 3.4 pounds and Monarch is over 4, but still the weight of an Asus ultrabook laptop. You could take it room to room well, but it's not a thing you're going to strap onto your body or put in a pocket to travel with, maybe in a backpack to use on a bus sure.
@Jage
in reply to Jage

@Jage but here's what's odd. Cadence doesn't put a gap at all going vertically down. Downside: It means if all your lines have highlighting, they would become unreadable. Upside: You can at least draw continuous lines, going down, without the 6MM gutter that's regulation Braille. From what I understand, Monarch has tighter pin spacing than DotPad, 60 pixels vs 96 pixels. So there could still be gaps in the circle where at the curves it wouldn't meet to the other side.
@Jage
in reply to Tamas G

Where are you seeing the different gap size in Monarch vs Dot? That's interesting. I know that Monarch and Dot both have 40 dots vertically. Dot is using this for 8 lines of 8-dot braille with a one row gap, Monarch is doing 10 lines of 6-dot braille also with a 1 line gap. The distance between pins, if you were to have them all raised, is the same in both directions as far as I know. Monarch is 96 pixels wide so 32 cells, Dot is 60 wide so 20 cells.
in reply to Jage

@Jage oh, I just looked at width. If a Monarch is roughly 10 inches wide, and dots are spaced at 2.5mm (0.1 inches), then ~10 inches / 0.1 = ~96-100 dots wide. But yes. 6-dot Braille. That's probably the dealio with Cadence. You cannot do 4 lines of 8-dot Braille, although it will let you, there's no restriction stopping you. It's just that the lines then will run together and touch. If you did 4 lines of 6-dot Braille, sure. Or a blinking cursor with dots 7-8, in one spot, it's not too annoying. So then you must lower it to 3 lines of 8-dot Braille, if you wanted to leave that same gap. Does DotPad X not make the lines run together like this?
@Jage
in reply to Jage

nah. If DotpPad decided to, say, do 10 lines of 8-dot Braille, it would look like the Cadence doing 4 lines of 8-dot Braille. What I'm saying is I bet DotPad and Monarch take care of this for you in software, that is, not allowing pins to run together vertically and become unreadable, say, if JAWS underlined every single line it was showing. Cadence just lets you do 4-lines of 8-dot Braille if you wanted to even if it was to your detriment
This entry was edited (2 weeks ago)
in reply to Tamas G

Ah gotcha. I think now they are doing things like underline in the dots 7/8 space. I know with Dot, because I've seen the SDK, that one could write a library now to display as 10 lines, 6 lines, etc. it just hasn't been done yet. Lines running together would not be ideal, but using dots 9 and 10, for lack of a better term, for underline is interesting. JAWS does ssplit braille formatting with one line of text and one line of formatting as an option as well.
in reply to Jage

@Jage oh yeah, I think in that instance it's probably easier to show formatting via Split Braille that way rather than highlighting the entire text. I know some people who would turn that off even on Single-line displays, to be honest though.
It could be that when Tactile Engineering was marketing it they were thinking 6-dot Braille as 4 lines. Which is very interesting to me because people often think of it as a 6-dot system but then with computers 2 extra dots can get added. I guess mistery solved! :D Really comes down to these little nuances they don't make clear on all the pages either. I think Monarch does say 6-dot Braille fairly up front, although that made me think it can't even display 8-dot in the first place! When in reality it could. If they wanted Monarch squished together I think max might be 12 lines of 5-pin Braille, that's 60. (4 pins + 1 pin gap.) But wouldn't be sure if they allow such a thing, I'm sure humanware limits to 10 lines either way.
@Jage
in reply to Jage

@Jage The way Jess is describing it is: "It's bigger than regular standard Braille, but smaller of a gap than Jumbo-Braille, in terms of horizontal spacing, on the Monarch." That's really interesting to me. I wonder how many neighboring dots they have to throw away for each cell of Braille then, presumably it couldn't be just a single dot alone but they had to make a big enough gap which has slightly larger spacing than standard Braille horizontal gaps do.
@Jage
in reply to Kate Hildenbrand (DE)

Ein nettes Beispiel wie GenKI wirkt hatte ich gestern. Es ging um eine Leitbildentwicklung in einem Workshop und die Ergebnisse wurden in unterschiedliche KIs eingebracht. Ergebnis war ein plausibel klingender Text, der dann komplett auseinander genommen wurde. Naja. Der Effekt war, das sich keiner der Teilnehmer mit den wirklich mit den Ausgangsdaten auseinandergesetzt hatte und die Ki-Ergebnisse Basis wurden. Seitdem verstehe ich, warum KI Produktivitätsverluste bewirkt.

#XMPP Community

User & developers are spread #world-wide in the XMPP community!
This is a call to show where you are! 🌍🌎🌏

Post a photo with the XMPP #logo and a nice view of your location 📷
Add city name and country, too.

#jabber #chat #rtc #standards #decentralization #federation #messaging

Nicoco reshared this.

I can't decide whether I want to keep this #NextCloud. While I like the general idea, the Windows Desktop client still has a bunch of unlabeled buttons, you don't seem to be able to just simply copy a public share URL from the context menu like with other solutions, and so on. I hear some blind people using it despite that. Are there any tweaks / #NVDA Add-Ons or anything else I could do to make it more accessible? Yes I could try and open GH issues but honestly the way how they treated the issue about the removal of the copy public link context menu thing makes me doubt anything productive will come out.
#Blind #Accessibility
This entry was edited (2 weeks ago)

#XSF Announcement

The 2025 annual meeting and #voting results for both #XMPP #Council and #Board of Directors are out: xmpp.org/2025/12/2025-annual-m…

Congratulations for the new period!

#jabber #chat #interoperability #rtc #xeps #standards #opensource #decentralization #federation #messaging

XMPP Extensions and Specifications

Read about the new #XMPP #extensions and #specifications changes and updates in November 2025:

xmpp.org/2025/12/the-xmpp-news…

#jabber #chat #interoperability #rtc #xeps #standards
#opensource #decentralization #federation #messaging

Well, "only" 12 updates today and no added apps, BUUUUT…

New milestone reached: 3 out of 5 apps at #IzzyOnDroid are now #ReproducibleBuilds 🥳

==> RB status: 758 apps (60%) <==

You can read more about what that means at our website: izzyondroid.org/about/security…

(and we hope to reach the "2 out of 3" (aka 66.666%) until FOSDEM 2026 🤞)

The more and more I use the Cadence, the more I realize how Mac OS and iOS treat it just as a standard HID display. Perhaps the reason my panning keys don't work is because the keys themselves are not seen as mappable ones in that standard driver. I'm saying this because under Mac OS 15, it treats it as a single-line display. That's right, only showing me 12 or 24 characters at a time at the top, leaving the rest blank. I do believe Mac OS 26 and iOS 26 must have been first to introduce multiline display support. If so, it explains things more: The standard HID driver now sees that the Cadence has 4 lines, but you cannot reorient them to either a vertically stacked 12-cell-by-8 line display nor reassign the thumbkey buttons. Perhaps iOS needs an official Cadence driver along with Mac, until that comes it works over Standard HID but not 100% well. That's the landscape with iOS
This entry was edited (2 weeks ago)
in reply to Tamas G

I'm almost tempted to try the IOS 26.2 RC to see if maybe quietly a new Cadence driver dropped, but since it's so close to release, may as well wait for it. I don't know. It's such a new display on the block that quite frankly I just think there's low awareness and OS vendors haven't done much. Of course, Cadence's own NVDA driver (github.com/tactile-eng/cadendu…) works really, really well. Panning's great, typing is amazing, all of it as I'd want, minus the reorienting to vertical stack from a horizontal one, all works. But they were the ones to build that add-on, of course it does. Ah well. I don't mind being an early adopter of it if it means being a voice that can help shape not only this multiline display's trajectory but also how multiline support comes along within various screen readers. Why the hell not. I expected pain points, don't color me surprised here for that one.

Re last: That's what I've been telling on and on and on to those, especially European people, who are yelling "Go! to Linux!! Right now!!! Gafam is evil, aaaah!"
Sorry, no. *First* you propose an accessible alternative or at least do something for it like sit down with accessibility experts, obtain grants and financing, so I could see I'm not forgotten at least, and *then* we'll think what to do next. #Accessibility
in reply to Kirill

@Yinshi Невыгодно — это точно. Налогов дохренища, GDPR грёбаный душит, ни посмотреть, что называется, ни пукнуть лишний раз как-то не так нельзя, иначе штраф-тюрьма-закрытие бизнеса. Отвратительный бизнес-климат, это правда. Но зато денежные люди, многие платят.
in reply to André Polykanine

Про GDPR знаю, да. К счастью не разрабатывал бэкенд с учётом требований, но общее представление имею. Особенно небольшим командам, кому и без того есть что делать, заморочек добавляет знатно, да и в целом для проекта. А ведь помимо есть же свои законы в каждой стране, вроде немецкого Bundesdatenschutzgesetz, что тоже надо исполнять. Во Франции наверное тоже какая-то своя подобная фигня существует.
This entry was edited (2 weeks ago)

The XMPP Newsletter for November 2025 is out!

Read about the latest updates in the #XMPP universe and our #standards!

xmpp.org/2025/12/the-xmpp-news…

Enjoy reading!

#jabber #chat #interoperability #rtc
#opensource #decentralization #federation #messaging #newsletter

Thought: if #open, #federated, and #distributed solutions were the most #accessible solutions, people with disabilities would be some of the biggest allies in pushing adoption. I already constantly have to get my friends, co-workers, etc, to switch tools for me. If we're working or playing together, the tool needs to be accessible if I'm involved. But unfortunately, that's almost never the case, and I find myself having to force my friends to switch away from open tools and into closed ones:
* Jitsi meet doesn't offer captions or transcripts, and still had an unlabeled button or two last I checked. So I usually have to force people working with me to switch to Zoom.
* github is still more accessible than Forgejo and codeberg, even with the recent regressions. So I won't contribute to projects that aren't on github.
* None of the existing Matrix clients offer good accessibility; they either lag, have unlabeled controls, the message list won't scroll, messages won't read as they come in, etc. So I have to force people onto Slack or Discord.
* Neither Only Office or Next Cloud offer a web interface that works for collaboration with screen readers, so I have to force people to use Google Docs.
* Linux accessibility remains a joke compared to Windows or mac.

And on and on it goes. #opensource#fediverse#federation

reshared this

USA kritisieren Europa und kündigen Einmischung an

In ihrer neuen Sicherheitsstrategie greifen die USA Europa scharf an und kündigen eine Einmischung zugunsten rechter Parteien an. Die US-Regierung wolle nun "Widerstand" in Europa kultivieren.

➡️ tagesschau.de/ausland/amerika/…

#USA #Europa #Trump #Sicherheitsstrategie