Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate backend and frontend, support Mastodon client-to-server API #212

Open
khimaros opened this issue Apr 28, 2019 · 1 comment
Open
Labels
A: Backend Anything related to the backend A: Frontend Anything related to the frontend A: Meta High-level metatickets (tracking issues, etc) C: Enhancement ✨ An issue which details an improvement to the software, not necessarily to fix a bug. P: Medium ☕ Medium priority ticket

Comments

@khimaros
Copy link

This would allow Rustodon to tap into the existing frontend availability and focus initially on the backend.

@barzamin barzamin added C: Enhancement ✨ An issue which details an improvement to the software, not necessarily to fix a bug. P: Medium ☕ Medium priority ticket labels Apr 29, 2019
@barzamin barzamin added A: Backend Anything related to the backend A: Frontend Anything related to the frontend A: Meta High-level metatickets (tracking issues, etc) labels Jul 23, 2019
@monomadic
Copy link

monomadic commented Oct 30, 2021

I second this. When approaching this project, one thing that turned me off is frontend and backend coupling. Are there any efforts underway to either port or split this codebase? It seems an obvious hindrance to adoption, I'd help out if there is anything going on (I'm an experienced rust programmer).

Writing a server as its own project would allow multiple frontends to be created in any language (including SPA applications) and server developers to focus on adding nice things like GraphQL etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Backend Anything related to the backend A: Frontend Anything related to the frontend A: Meta High-level metatickets (tracking issues, etc) C: Enhancement ✨ An issue which details an improvement to the software, not necessarily to fix a bug. P: Medium ☕ Medium priority ticket
Projects
None yet
Development

No branches or pull requests

3 participants