Not sure that is the correct approach. break frequently break often seems better (that’s what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).
notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.
Of course after version 1.0 there might be less breakage so it won’t be a be problem.
This isn’t what i had in mind. i meant more like changing the line to something like:
We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, donating money and helping find and fix bugs.
With “donating money” maybe replaced with “funding”.
We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs
I feel like people giving their hard earned money for lemmy also should get a show of appreciation.
That sounds like something could be improve. is there some sort of warning mechanism in place?
Say when using a lemmy client. the client either specifies its a production build. or if its not then the lemmy server reports where deprecated API’s are used.