Also serverica for hosting.

Personally, I’d like an open API so I could use it with foobar2000. Not OP but I long for the same thing. I’ve done it, and managing, storing, backing up, my music library costs more than Spotify. And assuming you don’t just pirate everything, add the cost of purchasing albums on top of that. And my time is worth minimum wage at least. I would happily pay someone to just handle this stuff.

Personally, I’d like an open API so I could use it with foobar2000. Not OP but I long for the same thing. I’ve done it, and managing, storing, backing up, my music library costs more than Spotify. And assuming you don’t just pirate everything, add the cost of purchasing albums on top of that. And my time is worth minimum wage at least. I would happily pay someone to just handle this stuff.

Personally, I’d like an open API so I could use it with foobar2000. Not OP but I long for the same thing. I’ve done it, and managing, storing, backing up, my music library costs more than Spotify. And assuming you don’t just pirate everything, add the cost of purchasing albums on top of that. And my time is worth minimum wage at least. I would happily pay someone to just handle this stuff.

Personally, I’d like an open API so I could use it with foobar2000. Not OP but I long for the same thing. I’ve done it, and managing, storing, backing up, my music library costs more than Spotify. And assuming you don’t just pirate everything, add the cost of purchasing albums on top of that. And my time is worth minimum wage at least. I would happily pay someone to just handle this stuff.

This has been broken for us on the entire 0.9 series. It works with iceshrimp, go to social, etc. just not mastodon. I think it has something to do with authorized fetch and signatures. But I haven’t tried to track it down as the way lemmy formats posts from mastodon was super ugly anyway.

Problem was that I usually only discovered the issue when I went to read the book lol

I like lire. It works with any of the popular feed syncing services, self-hosted, cloud-hosted, or it can just run locally on your phone. Also, when full text extraction works, it's a gamechanger. Unfortunately some websites (like bleeping computer) block it.

Based on the links you gave, it seems that captions default to off when new servers are created.

Ah, good to know! I don't use meeting platforms that aren't accessible by default for everyone. Looks like the problem, at least in Jitsi, is that enable captions defaults to off. It would need to default to on before I could use it.

How many of those support captions?

There were issues filed by screen reader users at the Lemmy-UI github, and a lot of them have already been fixed with pull requests. However, the 0.7 releases don't have grate accessibility. rblind.com, a community created by the moderators of /r/blind is in open alpha, and is running development code directly from the github, in order to get our community the most accessible Lemmy we can, as quickly as we can. We recognize this is terrible devops practice, and we intend to move onto stable releases when possible. In the meantime, we're taking regular backups, and warning our community to expect frequent bugs and issues. We've chosen Lemmy for our community, largely because the documentation and support around deploying an instance was better. While we hope blind folks will be welcomed at all instances across the fediverse, no matter what software they're running, it's important to us to have a place where the former /r/blind community can keep together, and we can begin making custom changes to the themes to create the most accessible Lemmy possible. We will, of course, make all of these changes open, and contribute them to the main version of Lemmy. But running our own instance frees us from waiting for other instance owners to make changes for us, while still allowing us to post to any community on any instance.