You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After reading http://decentralize.it again, I realized the idea of providing each app with its own CouchDB instance/subdomain/inbox email address might be a bit too generalized.
Not every app will be a web server/web app but instead maybe a Jabber/XMPP server.
These do not require different subdomains as different servers run on different ports.
Also, not every app needs a CouchDB database but maybe a MySQL database instead.
Maybe, we should offer an API to let each app request access to specific core features (subdomains, email addresses, databases, ports) and they will be provided to them as soon as the user accepts this - I don't think giving every app a set of features from the beginning is required.
Forcing the apps to be accepted by the user will also make sure an app can't collar 1000 different ports other apps might need. Instead, the user would have to accept that "the app wants to register a Jabber/XMPP server" (automatic mapping of standard ports) or something like that.
The text was updated successfully, but these errors were encountered:
After reading http://decentralize.it again, I realized the idea of providing each app with its own CouchDB instance/subdomain/inbox email address might be a bit too generalized.
Not every app will be a web server/web app but instead maybe a Jabber/XMPP server.
These do not require different subdomains as different servers run on different ports.
Also, not every app needs a CouchDB database but maybe a MySQL database instead.
Maybe, we should offer an API to let each app request access to specific core features (subdomains, email addresses, databases, ports) and they will be provided to them as soon as the user accepts this - I don't think giving every app a set of features from the beginning is required.
Forcing the apps to be accepted by the user will also make sure an app can't collar 1000 different ports other apps might need. Instead, the user would have to accept that "the app wants to register a Jabber/XMPP server" (automatic mapping of standard ports) or something like that.
—
Reply to this email directly or view it on GitHub.
After reading http://decentralize.it again, I realized the idea of providing each app with its own CouchDB instance/subdomain/inbox email address might be a bit too generalized.
Not every app will be a web server/web app but instead maybe a Jabber/XMPP server.
These do not require different subdomains as different servers run on different ports.
Also, not every app needs a CouchDB database but maybe a MySQL database instead.
Maybe, we should offer an API to let each app request access to specific core features (subdomains, email addresses, databases, ports) and they will be provided to them as soon as the user accepts this - I don't think giving every app a set of features from the beginning is required.
Forcing the apps to be accepted by the user will also make sure an app can't collar 1000 different ports other apps might need. Instead, the user would have to accept that "the app wants to register a Jabber/XMPP server" (automatic mapping of standard ports) or something like that.
The text was updated successfully, but these errors were encountered: