mastodon - Link to source

When was the last time you went out for a few hours, without any device?

a worthwhile read about sitting alone somewhere without any connected devices candost.blog/the-unbearable-jo…

Since 10 years, i am also doing this weird thing where my mobile is mostly offline, only using WIFI here and there, but i am going to more often leave devices completely at home. It's really crazy how much this once normal situation is like a super-big deal these days.


The Unbearable Joy of Sitting Alone in A Café

Hunting timeless insights into humans and software and helping others on the way.
candost.blog

mastodon - Link to source
Sprechende Uhr, Kalenderwochenfehler

Sensitive content

in reply to Aleksander Pavkovič 🇸🇮

mastodon - Link to source

Marco Zehe

Sprechende Uhr, Kalenderwochenfehler

Sensitive content

in reply to Marco Zehe

mastodon - Link to source

Aleksander Pavkovič 🇸🇮

Sprechende Uhr, Kalenderwochenfehler

Sensitive content

@Marco Zehe
in reply to Daniel Gultsch

mastodon - Link to source

JTI

I also received Spam in the Fediverse. From multiple servers, large and small. The topic is important as the Fediverse will scale and complicated because of the implied decentralized nature of it.
Hence, I expected a thoughtful discussion and comparison of existing work, work in progress, current research questions and transferrable work between the two protocols.

What did I get: Absolutely thought free, cheap instances of tu quoque and demonstrations of incompetence about the subject being discussed. Do better.

Which brings us to one the most important tools to combat spam in the Fediverse at the moment: The block function.

mastodon - Link to source

Ich bin Fan vom Känguru und „VIEWS“ ist auch wirklich sehr gut.

Ich frage mich, ob Marc-Uwe Kling (@marcuwekling ) der Sache nicht mehr geholfen hätte, wenn er angekündigt hätte, ab morgen ausschließlich im #Fediverse zu posten.

Die meisten Nutzer folgen dem Content und nicht komplizierten moralischen Appellen.

#Mastodon #DiDay #DigitalIndependenceDay #DiDit

#fediverse #Mastodon #didit #diday #digitalindependenceday @Marc-Uwe Kling
in reply to Daniel Gultsch

mastodon - Link to source

Regezi

Aus eigener Erfahrung würde ich sagen, dass ein zu aprupter Wechsel selten von langfristigem Erfolg gekrönt ist...ich denke, wenn einige neue Nutzer hier (zeitweilig parallel) ihre Zelte aufschlagen, sollten wir ihnen einen möglichst warmen Übergang ermöglichen...
* es benötigt auch etwas eigene investierte Zeit, dieses Netzwerk besser zu verstehen und diesen "Mehraufwand" können wir nur anteilig mit Usability-Attraktivität wettmachen...

@marcuwekling

@Marc-Uwe Kling

mastodon - Link to source

I wrote Zig bindings to quickjs-ng with 96% API coverage (~240 exported C decls) with unit tests, examples, and doc strings on all functions in less than 6 total hours with AI assistance. I never want to hear that AI isn't faster ever again. github.com/mitchellh/zig-quick…

This isn't slop. I worked for those 6 hours.

I was reviewing everything it outputted, updating my AGENTS.md to course correct future work, ensuring the output was idiomatic Zig, writing my own tests on the side to verify its work (while it worked), and more. My work was split across ~40 separate Amp threads (not one mega session, which doesn't work anyways unless you're orchestrating).

I have a ton of experience writing bindings to libraries for various languages, especially Zig. I have never achieved this much coverage in so little time with such high quality (e.g. test coverage). My usual approach is to get bind just-enough of the surface area to do my actual work and move on. This time I thought I'd draw the whole owl, because it's a new world. And I'm very happy with the result.

Anyone with experience writing bindings knows that you do some small surface area, then the rest of the coverage is annoying repetition. That's why I usually stopped. Well, LLMs/agents are really, really good at annoying repetition and pattern matching. So going from 5% API coverage to 95% is... cake.

There is probably some corners that are kind of nasty still, but I've been re-reviewing every line of code manually and there is nothing major. Definitely some areas that can just use a nicer Zig interfaces over the C API, but that's about it.

I plan on writing a longer form blog showcasing my threads, but you can at least see the final AGENTS.md I produced in the linked repo.

github.com/mitchellh/zig-quick…


GitHub - mitchellh/zig-quickjs-ng: Zig build and bindings for quickjs-ng

Zig build and bindings for quickjs-ng. Contribute to mitchellh/zig-quickjs-ng development by creating an account on GitHub.
GitHub

mastodon - Link to source
Welcome to 2026! We have a lot planned for this year, including #LibreOffice 26.2, due in early February. Keep an eye on our blog for more updates: blog.documentfoundation.org #foss #openSource #freesoftware

TDF Community Blog -

The Document Foundation
#FreeSoftware #foss #opensource #libreoffice

mastodon - Link to source

Da vergüenza ajena que Pedro Sánchez sea incapaz de publicar su propio comunicado de condena a la invasión americana sin tener a un grupo de países al lado, como da vergüenza ajena que haya tenido que unirse al comunicado latinoamericano porque ningún otro país de la UE es capaz de criticar a los EE.UU. como sí hicieron con la invasión de Iraq.

#Venezuela #PedroSanchez #psoe #ue #eu #europe #trump

#Trump #EU #europe #PSOE #PedroSánchez #Venezuela #ue

mastodon - Link to source

🧵 We moved from Google Cloud to Hetzner and cut infrastructure costs by 80%. Here's what I learned:

Same workloads, same reliability, actually better performance for our use case. Main thing we lost: 47 GCP console screens to find a simple setting.

GCP isn't bad - it's powerful and right for many cases. But somewhere the industry decided "real" companies must use hyperscalers. That's marketing, not engineering.

1/2

mastodon - Link to source
@Tutanota [1/2] I was using tuta mail. It was logged into the tuta app on my phone. Whenever I open the tuta app it automatically takes me to the inbox. I was also able to access it from the web too. But from the day before yesterday I was not able to login, it shows "invalid credentials".I tried many times carefully checking my credentials but I am not able to login. Also it does not login to my app automatically anymore. It was my primary email for official communication attached with many org
@Tuta
This entry was edited (2 weeks ago)

mastodon - Link to source

Because of work, I haven't really made presentations since ~2016, and when I had to, I was basically forced into PowerPoint.

Back then, my conference & OSS talks were HTML+CSS for me (in Spanish, mostly). Markdown was just for Wikipedia.

Now I’m prepping a #FOSDEM 2026 talk for @badgefed and discovered #marp.
Markdown-based slides, and… wow. I'm having way more fun than I expected.

marp.app/


Marp: Markdown Presentation Ecosystem

Marp (also known as the Markdown Presentation Ecosystem) provides an intuitive experience for creating beautiful slide decks. You only have to focus on writing your story in a Markdown document.
marp.app
#fosdem #marp @The BadgeFed Project

mastodon - Link to source

Hi. I apologize in advance if my account becomes somewhat political. I am Venezuelan, and I want to talk about what is happening in my country. I will do so from my own beliefs and political position.
I am open to debate and to clarifying doubts for anyone who has them.

However, I am not open to insults, disrespect of any kind, or being called a traitor to my country. I only accept respectful dialogue here, and I thank in advance anyone who chooses to engage in that spirit.

mastodon - Link to source

Acabadico Babel, de Kuang. Uf, me ha flipado, genuinamente, me parece una maravilla de novela. sí, tiene sus cosas, como que la narradora es demasiado obvia a veces y tiene a explicar demasiado, confiando demasiado poco en el lector.

PERO, aún así, me ha flipado toda la novela de cabo a rabo. En tema, estilo y estructura. En general no leo libros tan largos (aunque ahora van a venir varios tochos seguidos...) y me imponía bastante. Sin embargo, me lo he bebido. Lo comencé el día 1, viajando a casapadres en tren, y me lo he acabado esta tarde.

Me encanta como el conocimiento de un campo muy concreto, la traducción, puede acabar no solo siendo un sistema de magia, sino un sistema de poder y relaciones. Que el propio sistema de magia que plantea sea en sí los vacíos del lenguaje... Mira, me flipa.

También es de los pocos sistemas de magia que he visto que, de verdad, está ahí para reforzar la trama y su mensaje anticolonial.

En fin, que recomiendo muchísimo #literaverso

#literaverso
in reply to Alcarendor

gotosocial - Link to source

modulux

Me gustó muchísimo también; y la forma en que se sistematiza la traducción como un recurso a utilizar y explotar es muy interesante. Personalmente, también hice una lecutra secundaria que no sé si es porque yo siempre pienso en estas cosas, o porque realmente estaba ahí; pero el tema de la centralización, de como se controlaba la traducción desde un solo centro y así había que renovar la suscripción de vez en cuando, me recordó un montón a todo el tema de la nube y el software como servicio; y el status de los traductores me hizo pensar en la posición de los estratos técnicos (ingenieros, arquitectos...), con privilegios materiales pero explotados y reproduciendo el sistema.

mastodon - Link to source
Ayer un señor me ayudó a subir al tren, me buscó asiento, me puso la mano en la cabeza y me dijo "que Dios te bendiga". Y Dios me bendijo. Y ahora no sé qué hacer con la bendición. ¿A alguien más le pasa? ¿Cómo se vive estando bendecido? Es que no estoy usando bien la bendición o algo, porque los problemas que tengo son los mismos y no he notado ningún cambio.

mastodon - Link to source
A new day, and a new accessible Telegram client for Windows, TAccess.
TAccess is a custom Telegram client built with Python and wxPython, specifically designed to be fully accessible for screen reader users (NVDA, JAWS, Narrator) on Windows.
github.com/mlapps88/t-access-a…

Release T-Access 1.0 · mlapps88/t-access-accessible-telegram-client

TAccess v1.0.0 - First Public Release We are proud to present the first stable release of TAccess, an accessible Telegram client designed from the ground up for efficiency and ease of use with scre...
GitHub
This entry was edited (2 weeks ago)

reshared this

writefreely - Link to source

The text mode lie: why modern TUIs are a nightmare for accessibility

The mythical, it's text, so it's accessible


There is a persistent misconception among sighted developers: if an application runs in a terminal, it is inherently accessible. The logic assumes that because there are no graphics, no complex DOM, and no WebGL canvases, the content is just raw ASCII text that a screen reader can easily parse.

The reality is different. Most modern Text User Interfaces (TUIs) are often more hostile to accessibility than poorly coded graphical interfaces. The very tools designed to improve the Developer Experience (DX) in the terminal—frameworks like Ink (JS/React), Bubble Tea (Go), or tcell—are actively destroying the experience for blind users.

The Architectural Flaw: Stream vs. Grid


To understand the failure, we must distinguish between two distinct concepts often conflated under “terminal apps”: the CLI (Command Line Interface) and the TUI.

  1. The CLI (The Stream): This operates on a standard input/output model (stdin/stdout). You type a command, the system appends the result below, and the cursor moves down. This is linear and chronological. For a screen reader, specifically kernel-level readers like Speakup, this is ideal.
  2. The TUI (The Grid): This treats the terminal window not as a stream of text, but as a 2D grid of pixels, where every character cell is a pixel. It abandons the temporal flow for a spatial layout.


Case Study: The gemini-cli Madness


Let's look at a concrete example: gemini-cli, a tool written in Node.js using the Ink framework. On the surface, it looks like a simple chat interface. But underneath, Ink is trying to reconcile a React component tree into a terminal grid.

When you use this tool with Speakup (Linux) or NVDA (Windows), the application doesn't just fail; it actively spams you.

Because the framework treats the screen as a reactive canvas, every update triggers a redraw. When the AI is “thinking,” the tool updates a timer or a spinner. To do this, it moves the hardware cursor to the timer location, writes the new time, and moves it back.

For a sighted user, this happens instantly. For a screen reader user, this is what you hear:“Responding... Time elapsed 1s... Responding... Time elapsed 2s... [Fragment of chat history]... Responding...”

It drives the screen reader mad. The cursor is teleporting all over the screen to update status indicators, spinners, and history. Speakup tries to read whatever is under the cursor at that exact millisecond. You end up hearing random bits of conversation mixed with timer updates, making it impossible to focus on what you are actually typing.

Worse, lets pretend that you've somehow managed well with speakup so far, but that you want to do some work with nvda. Maybe paste an error you're getting on windows. So you open your terminal, ssh into your linux box, attach to your screen session and paste your text.

The result is an immediate crash of the screen reader (NVDA) or massive system instability. Why? Every time you type a character or paste text, the application triggers a state change. The framework decides it needs to re-render the interface. Because the conversation history is part of that state, the application attempts to redraw or re-calculate the layout for thousands of lines of text instantly. The more messages you have in a conversation, the more this will happen. And no, you can't just avoid this by using insert+5, the key combo supposed to avoid announcing dynamic change of content.

The Lag Loop


Furthermore, frameworks like Ink running on single-threaded environments (like Node.js) suffer from massive performance degradation when the history grows. If you paste a large block of text, the system has to calculate the diff for thousands of lines.

This causes input lag. You press a key, and you wait. You can wait up to 10 seconds for a single character to echo back. The system is too busy calculating how to redraw the screen to actually process your input.

Why The “Old Guard” Works (nano, vim, menuconfig)


Sighted developers often ask: “If TUIs are bad, why do you use nano, vim, or menuconfig?”

The answer is not that these tools handle the cursor perfectly by default. The answer is that they allow you to hide the cursor entirely.

1. Hiding the Cursor (nano, vim)


In tools like nano or vim, usability depends on turning off features that track cursor position. If you run nano with options that show the cursor position (like --constantshow), or if you use vim without specific configuration, the experience is broken.

When the cursor is visible and tracking is active, Speakup prioritizes the cursor's location update over the character echo. Instead of hearing the letter “a” when you type it, you hear “Column 2”. You type “b”, and you hear “Column 3”.

These older tools succeed because they allow you to disable this noise. You can configure them to suppress the visual cursor or status bar updates, forcing the screen reader to rely on the character input stream rather than the noisy coordinate updates. Modern frameworks rarely offer a “no-cursor” or “headless” mode; they assume the visual cursor is essential.

2. Single Column Focus (menuconfig)


Tools like the Linux kernel's menuconfig work because they enforce a strict, single-column focus. Even though there are borders and titles, the active area is a vertical list. The cursor stays pinned to that list. It doesn't jump to the bottom right to update a clock, then to the top left to update a title. The spatial complexity is kept low enough that the screen reader never gets “lost.”

3. The Lost Art of Scrolling Regions (Irssi)


Irssi is the gold standard for accessible chat, but not because of luck. Irssi was built over 20 years with a custom rendering engine that utilizes VT100 Scrolling Regions.

When a new message arrives in Irssi: 1. It tells the terminal driver: “Define a scrolling region from line 1 to 23.”2. It sends a command: “Scroll up.” The terminal moves the bits up. 3. It draws the new text at the bottom of that region.

Crucially, it handles this in a way that minimizes interference with the input line. It relies on the terminal's hardware capabilities rather than rewriting every character on the screen manually. Modern frameworks ignore these hardware features in favor of “diffing” the screen state and rewriting characters, which is computationally heavier and hostile to accessibility.

The “Stale Bot” excuse: A Case Study in Neglect


Google and the maintainers of gemini-cli pretend to care about accessibility. “Pretend” is the operative word here. If you look at the repository, critical accessibility regressions like Issue #3435 and Issue #11305 have been left to rot. There is no discussion, no roadmap, and no fix. Even worse is the fate of Issue #1553, which was supposed to track these accessibility failures. It didn't get solved; it got silenced. It was closed automatically by a bot with this generic dismissal: > Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports. It looks like this > issue hasn't been active for a while, so we are closing it for now.”

This is unacceptable. Closing an accessibility report because the maintainers haven't touched it in months is not “tidying up”; it is hiding evidence. It effectively says that if a bug is ignored long enough, it ceases to exist. It boosts the project's “Closed Issues” metric while leaving the actual software unusable for blind users.

Conclusion


If you are building for the terminal and care about accessibility, stop using declarative UI frameworks that treat the terminal like a canvas.

The “modern” TUI stack has optimized for the developer's ability to write React-like code at the expense of the machine's ability to render text efficiently.

If you cannot guarantee that your application allows the user to hide the cursor, or if you rely on aggressive redrawing to show spinners and timers, you are building an inaccessible tool.

For the blind user, a dumb, linear CLI stream is infinitely superior to a “smart” TUI that lags, spams, and scatters the cursor across the screen.

#3435 #11305 #1553
in reply to André Polykanine

glitchsoc - Link to source

Casey Reeves

I unfortunately have not found any myself. The second your ssh connection lags even a tiny little bit, things kind of fall apart.

And cursor tracking seems hardcore in wsl for some reason? It's very weird. Or it's probably nvda not liking the windows terminal all that much... Let's be honest there too, nvda rather sucks for the terminal, as unfortunate as it is.

in reply to Marc Hoffmann

mastodon - Link to source

Jonathan

@McOi Basically any online dating app these days is a feed with suggested profiles, you swipe left and right to like/unlike, very generally. So that's where the swiping comes from. And well, as you can imagine 90% of that decision whether to like/not comes from looking at the images people put on their profile there. And then of course if you're a group or random bored young adults you can make a bunch of random weird/stupid and also racist comments about said pictures.
@Marc Hoffmann
⇧