this post was submitted on 12 Apr 2025
3 points (100.0% liked)

Lemmy Apps

6060 readers
7 users here now

A home for discussion of Lemmy apps and tools for all platforms.

RULES:

An extensive list of Lemmy apps is available here:

LemmyApps.com

or lemmyapps.netlify.app

Visit our partner Communities!

Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. [email protected]

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]

founded 2 years ago
MODERATORS
[email protected]
3
Mlmym (also known as old.lemmy) isn't maintained anymore, and features are starting to become unusable as instances are migrating to newer versions. Would someone be interested in forking the project? (lemmy.dbzer0.com)
submitted 3 weeks ago by [email protected] to c/[email protected]
19 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 3 weeks ago

Their justification is that pre v1.0, you can break whatever you want whenever you want.

They are not wrong. If you are developing an application against a backend that clearly states "we are following semver. This version is not 1.0, therefore no API is guaranteed to be stable", and you go on to write a client for it anyway, you don't get to complain later when they make breaking changes.

Alternatively, you can just stop relying on their ad-hoc APIs and push for them to implement Lemmy with focus on the ActivityPub API. That is already an standard and if you come up to them with issues against their AP implementation, they will be a lot more likely to listen to you.