3 ms·
Since timeup is for free I think that a good way to go into that direction is to completely expose our API and make it publicly available. Than everybody who w
by timeup 11y ago
Since timeup is for free I think that a good way to go into that direction is to completely expose our API and make it publicly available.
Than everybody who wants can create addons for several kind of devices and other software. Right now the API is still very tiny and in my opinion it should stay like that. Only a very small selection of additional features will come.
So far our capacity (only 2 devs) is very very limited to support all kind of other software / devices in short time. (We're still students and doing timeup as a small side project - We saw the need of that tool when trying to organize meetings for learning groups)
Any other idea how to further support your idea?
- e12e 11y agoSomething related is going on with json and email with fastmail[1] -- a standard needs to bee free/open, and have a usable free/open implementation. That way people can pay you for the convenience of a service, and not be afraid to be left in the cold once you move on to other things/get hit by a bus/get bought by doodle and they decide to fold your service etc. Another example is Mozilla sync, which has a nice and viable self-hosting solution (both for the new and old sync)[2]. Not that Mozilla is charging for the sync service, but IMNHO they probably could - perhaps giving paying users a larger quota. Not that the free quota is a limit; more as a sensible way for users to support the project. [1] http://jmap.io/ http://jmap.io/ (Note that jmap is a reaction to a) the cruft that's been assimilated in IMAP, b) the need for webmail anyway (so rather than have what is essentially a http-to-imap proxy (squirrel, horde/imp) -- just have the mail server speak http). [2] https://docs.services.mozilla.com/howtos/run-sync-1.5.html https://docs.services.mozilla.com/howtos/run-sync-1.5.html