First let me say, I have tried many Lemmy clients, and Voyager is by far my favorite.
For large text support, Voyager might be the best. But it could still do better.
I have posted some bug reports and issues, here in the lemmy coms and even created PRs on the Voyager github repo. Those PRs were never merged.
As a proof of concept or prototype, I have forked Voyager to fix many of the large text or accessibility related issues.
You can find this fork documented here along with the webapp.
If you scroll down to the “Compare” section, I think it will be very clear as to what the issues are.
Hopefully you will see this as a very comprehensive bug report which includes suggested code fixes.
Also many of these issues, like string truncation of user names and server instances, are general issues which impact all users regardless of visual acuity.
Will Voyager using a PieFed backend fix this? If so, then we are on the same page. But this doesn’t look like a backend protocol issue to me. This looks like a UI issue.
At first, I misread the post you are replying to; maybe you did the same. The poster was asking if your app supports PieFed, not because PieFed fixes the issues that you identified, but because that’s the site that poster uses.
In other words, they may want to use your app, but would need it to support PieFed since that’s the site they use.
Classic online discussion moment.
I really considered whether I wanted to comment, but my desire to procrastinate at work won out.
I sympathize.
classic piefed user. always making it about piefed.
It looks like you are missing the point. I asked you about Seevoy’s support for PieFed, not Voyager’s support for large text support.
In fact, I know it’s a UI issue, because I know the data is available. It’s just not styled correctly.
Do you think the backend protocol is returning “…” ellipses as part of a username???