- cross-posted to:
- summit@lemmy.world
- boostforlemmy@lemmy.world
- cross-posted to:
- summit@lemmy.world
- boostforlemmy@lemmy.world
You must log in or register to comment.
Oof, lots of work to do for everyone.
If anyone can figure out all the non-mentioned API changes and write them here it would be useful for people like me to avoid having to reverse engineer things
I can say I was there when Lemmy 1.0 released!
Holy shit, it’s going gold!
A lot of these should not be called breaking changes. A new API is not a breaking change if the old API remains.
if
Yeah but those changes break clients as soon as they turn down the old API.
Indeed, dropping the old API would be the breaking change.
Rich Hickey did a fantastic talk on versioning, breaking changes, and dependencies.
Will the new lemmy ui be ready for 1.0?
Can’t give an ETA yet. I’ve got a few more back-end things to finish up, then @sleeplessone1917 and I will work on lemmy-ui.
Then I also gotta work on getting jerboa updated also. So much work and so few developers.
Yes we always release backend and frontend versions together.
Nice
Does this mean you renamed just the DB columns, but not the API keys?
They’re all renamed, that PR just hasn’t been deployed to voyager.lemmy.ml yet.
Ah, good to know before I start developing. Can you let me know when we can start the development as I don’t want to use the API and then discover it’s missing more PRs?
I can’t say yet, as we’re still adding things. If you’re not using lemmy-js-client, then as long as your types are generated from it’s main branch directly, then you should be fine.
I’m not using the js-client. I’m updating pythorhead so I need to make sure the API is at the final version before I can match it. And to match it I need the patches to be in so I can read the doc, and/or import the swagger.
I will do what I can in advance, but to do the pre-development you asked for, we do need the final version up somewhere.
The final api version would probably be in 1.0-beta.0, which will still take a few months. But at this time you can already start to adapt for the major changes like combined endpoints, and give feedback if anything else in the api needs changing.
The updated spec should be at https://join-lemmy.org/api/main , and it gives you an option to download the
.jsonfileOr you can use the lemmy-js-client main branch, and run
pnpm tsoato generate aswagger.jsonfile.
just passing by to congratulate you guys on the milestone!
wow! Huge, just when I am back to the saddle
1.0 would be the perfect time to have the code, bug tracker, etc. migrated off of Microsoft GitHub
Would lose a lot of visibility. Gotta pick your battles
Visibility to who? Normies? Search engines favoring corpo slop? You could make a readonly mirror if felt it necessary (it isn’t). If you have a modus operandi for you product or service, you would be better off choosing tools that align with those ideals. This instead says collaborator privacy/freedom is not our priority & we don’t actually follow our values.
I ran a large open source project, and when we switched to Gitlab the number of contributors dropped like a rock. Despite linking to our Gitlab repo everywhere, people weren’t finding it on Google or GitHub search, and those who did weren’t interested in creating a second account.
We went from probably getting a new contributor every month to maybe getting a couple a year. It significantly slowed down progress.
Why?
I know the knee jerk reasons of course.
However, GitHub is a fantastic ecosystem for an application to thrive. Contributions on other platforms are greatly reduced.
Then again, the actual Lemmy development is a bit of a mess.
Once it gains critical mass of engaged developers, that’s a good time to migrate off GitHub. Doing it earlier just slows the project down.
It really provides nothing special of note other than network effect (slow UI, nonrobust CI of YAML spaghetti, pull request model is broken, upselling AI shit in the UX, taking users code with that AI & selling it back to users despite it being our code in the commons, taking cuts from sponsors, etc.), but you can’t shift that without setting a good example—& getting folks to cross out of that closed, centralized, data sucking ecosystem.
One of the primary reasons for Lemmy’s existence is to get out of Reddit’s walled garden & AI nonsense onto a decentralized platform. Git (& other VCSs) does not have a restriction on centralized nonsense unless you buy into a platform that requires community member give up their data to a US company just to participate. Why would you value one thing for your users then have different values for developers (that are also users)—especially when there are gobs of alternatives? Screw Microsoft on all accounts—historically & presently. There is no reason to treat this like some startup/market thing for engagement when the platform & its core users want a different experience outside of corporate control (but if you must, just make a readonly mirror with issues disabled).
💪
Really excited for these changes; scheduled posts, donations, SSO, let’s goo
