What I am missing, I would go into a decentralized
architecture with
this, is something which integrates nicely with Zeroconf. So that even
when there is no gateway and users are not technically skilled, they can
still connect to some common chat with Skype, iChat, Adium or some other
chat client with supports Zeroconf/Bonjour. Sadly, not many closed
source do (and also this support is limited, probably still requires
Internet access, haven't tried it yet).
Why would you implement something like this as a
centralized service? That
seems lazy. Decentralized networks should run decentralized services.
I tend to first implement something centrally, to even try if the idea
is good. And then distribute. But I know that we disagree on that. For
me, it is just a practical approach. Do I want to spend one year
implementing a framework to develop my distributed app running on nodes.
Or do I want to spend one year working on a app itself.
It just boils down to how many developers there is. I rather spend time
on something which can be used immediately and by everybody (so it has
to work as they people are used to).
But please, teach/show me how can be this done easier. Maybe I am just
an old school guy who has not yet grasped some new framework which
allows to do this. Is there a framework like
http://www.meteor.com/,
just distributed and would run on nodes themselves?
. the original creator
of the project was behind the late hook.io
(
) which had a lot of features for
running distributed nodes of a single app, so once we have the core
features implemented in big we will surely finish implementing the
distributed features. we're not yet ready for production so give us at
least half a year, maybe a year, maybe more. hopefully sooner i'll be
able to release some alpha apps like