mastodon.ml — это один из многих независимых серверов Mastodon, которые вы можете использовать для участия в сети Fediverse.
Русскоязычный сервер социальной сети Mastodon. Зона общения, свободная от рекламы и шпионажа, теперь и на русском языке.

Управляется:

Статистика сервера:

758
активные пользователи

Cyrmax

I want to write my own cross-platform and accessible for blind users client.
There are no friendly clients for Linux (only some TUI software) and there are only one buggy and unstable proprietary client for Windows called .
I already know the stack I'll use but I have one problem.
I don't know Mastodon well enough to be sure that I implement every feature which is supported there.
For sure I can read the whole API reference but maybe there are easier ways, maybe some list of features, maybe some feature guide for developers, etc.

As a blind user I can't just install any popular and cool client and take all features from it... That's the problem: they are not accessible at all or not accessible enough for every day use.

So, maybe someone helps me with some sort of docs or I don't know :D

For sure I'll implement everything I already use or know that I want to use but can't because of current client limitations.
But what after? I mean I saw some features like ignoring specific tags, showing posts in only chosen languages, hidding posts by keyword filters, building a separate timeline from a combination of hashtags, etc.
But are these official features of Mastodon? Are they saved in my account and can be used in any client supporting them? Or they are custom, and every client does these things on client side?
Or users recommendations, which I have in tweesecake. Is this some kind of tweesecake feature or my home server decides who should be in this list, and every client just fetches this list?

So, yes, I defenitely need help :D

@cyrmax this is because web UI uses the same API as third-party clients

@cyrmax hey there.
I don't have answers ready but I really like your idea. Since I'm an educated programmer (but currently working as DevOps) I think I could maybe help you with being your eyes and researching your questions while having an informed view on the features.

Would you like to have a chat?

@lb1a
Thanks for being ready to help with this idea :)
About being my eyes I think I shouldn't bother you with such things because my screenreader does the job well enough (of course until I find some screenshots, illustrations or other graphical stuff).
But about features, yes, it would be very cool if you help.
And also it would be cool if you help at some point with basic design. I don't think that apps for blind should be completely invisible or ugly for sighted people.

@cyrmax FYI, tweesecake is beeing rewritten. That won't probably change the fact it's not cross platform, or at least not linux, not sure, maybe it's worth asking them, but at least the bugs will be gone.

@jonathan859
Yes, I saw your reply in Telegram regarding TweeseCake. Thanks btw.
But the problem is a bit bigger. I don't like this buffered interface tweesecake and twblue have. I want another concept, a bit closer to what we see in usual "sighted" apps, such as official Mastodon.
Or probably it would have some mechanics from Miranda as I used to it. But not this buffered thing.
I don't want to say that buffers are awful, but personally I don't like them :D

@jonathan859
Probably you've already saw my suffering with UI frameworks for dotnet.
Okay, I wanted a cross-platform thing but nobody prohibits me from trying more stuff and if fails, then get back to old but accessible WinForms, which are only for Windows but at least fully accessible.

@cyrmax There's also TW Blue, for which there are sources available: https://twblue.mcvsoftware.com/

Answering some of your questions: the language filtering happens at the preferences level, so if you set it on the preferences it will propagate to clients getting timelines through the API. Filters are an API thing (there are two types, client-side and server-side). User recs is also an API feature.

twblue.mcvsoftware.comTWBlueThe TWBlue official website

@modulux
Yep, it's true. But I'm not so experienced in WX to change something major in twblue source.
And also for me it is a kind of challenge - developing my own mastodon client.
Kind of a pet project important for my feeling as a developer and gaining some experience in desktop apps.

@cyrmax Oh, I think it's a great idea to make a new client. I was more suggesting that you might be able to get some notion of what's possible from TW Blue's sources.

@modulux
Ahaaa, now I got what you meant to tell.
Well you're absolutely right, and I guess I will look a lot into different sources while writing this thing :D

@cyrmax I have written a client based on the API docs and I've implemented the basic features from the web interface and added my own ideas.

So, sorry, I can't really point you in any direction about feature lists.

But, feel free to ask me questions if you need help with the API and I'll try my best...

@dec_hl
At least you did it and probably you use your product :D
So at least this is not a bad idea to do something similar (looking at the web interface and repeating as a desktop app).

@pvagner @cyrmax Actually, the Tuba client looks that it might be made into an accessible Linux client, except we might need to fix an Orca regression (reading complex list item rows and a11y labels together behaves weirdly), and we must definitely fix https://github.com/GeopJr/Tuba/issues/1164#issuecomment-2495579598

GitHub[Request]: When describing status item for screen reader users include the text content · Issue #1164 · GeopJr/TubaАвтор: pvagner