hacknlove
commented
4 years ago The thing about WSW is more like a S2S (site to site) protocol.
In ActivyPub you sign up in some server with many others, and you interact with people in your server and with people in other servers. It is decentralized,
in WSW every one has their own server like koo5.dev for instance, it's yours under your full control.
koo5.dev is your identity on WSW, you can use your site to authenticate yourself in any other site.
You publish on koo5.dev, and you also use koo5.dev to interact with other sites of the wsw
The goal is to replicate the whole social network experience, but with every user owning their own websites, and using those websites to publish, react, discover, authenticate, chat, everything.
I had been writing without blueprints for a while, but I realized that this time, for this project I needed to think it very carefully.
Regarding Humanifa, It is almost abandoned. There are some guys using it and taking care about the social media, but I am not developing new features. It was kind of a deception.
More or less I can say the same about crowdference. Even worse because nobody is using it.
I agree with this
Most of us would make our world better if we could. Or at least different.
That is what WSW is about, we need an alternative to centralized social networks, and I expect decentralized could give us the freedom we deserve.
People used to have blogs of their own, and all kind of crazy websites like in geocities, I think people will come back to that, when the sites can interact each other like users of a social network.
I would like to learn more about wsw. Is it intended to be a a regular microblogging protocol, like ActivityPub and a million others, or is it in fact a generalization of your earlier projects, perhaps to subsume the requirements of humanifest and crowdference?
I really like the idea of humanifest, see real value there. Please see https://github.com/koo5/koordinator2000/ .
Anyway. I'm mainly interested in crowdference, and in merging the crowdference extension with https://github.com/karlicoss/promnesia .
I think it's obvious. One add-on to install, one toolbar button, one way to notify the user. One method/code for:
In practical terms, we would start by extending promnesia to support multiple data sources, and teach it to query your api...