@dansup @nlnet @loops if i may ask, why not already?
@fossdd @nlnet @loops Because when you involve users in a beta, and admins, it can get complicated with outdated apis and ux.
I'm almost ready to ship the v1 of Loops, and finalize the API so we can open source everything.
I don't want 3rd party devs to waste time developing against an API that isn't final, thats the main reason.
@dansup @nlnet @loops hmmm, i think just making it official that the API is unstable and WILL change would be much better and transparent than developing it closed source
Gregory's Server
@fossdd @nlnet @loops Because when you involve users in a beta, and admins, it can get complicated with outdated apis and ux.
I'm almost ready to ship the v1 of Loops, and finalize the API so we can open source everything.
I don't want 3rd party devs to waste time developing against an API that isn't final, thats the main reason.