@bhaugen @KevinMarks @cwebber the main difference is that #IndieWeb (as I understand it) is designed around the idea of everyone having a self-hosted homepage, which implements a bunch of simple-as-possible protocols, allowing those homepages to form a social network. Obviously quite different from the assumptions behind AP (a federation of servers, each with one or more users, each with a web or native client) or #SSB (a #P2P network of native clients that may have intermittent net access)
@strypey @bhaugen @KevinMarks @cwebber Not an expert but I don't think it's *necessarily* (although very common) about being self-hosted, it's about owning your identity and your data. e.g. https://micro.blog provides hosted services that adhere to indieweb protocols (and principles).
In some ways its closer to Hubzilla than Mastodon, IMO.
The reason I mention that (and hope I'm correct in saying so) is that I think it's vital that indieweb does not expect everyone will self-host.
@cwebber @strypey @neil @bhaugen I don't think we disagree about goals, but about methods to some extent. Indieweb was founded after frustration with large complex federation efforts aimed at big companies, and refocusing on web-centric models that are small and simple to implement.
OStatus has a lot of these complexities included (webfinger and salmon being the most egregious). https://www.w3.org/wiki/Socialwg/AccountDiscovery has some of this.
Kevin, can you federate with all of the people in this message from an indie.web place-to-stand?
If not, what would it take to be able to do that?
Or conversely, what would it take for eg a one-person ActivityPub (which I got) to be able to federate with you communing from an indie.web place?
(Was that all clear?)
It should be possible for you to subscribe to an indieweb site via atom and webpub, but mastodon wants a lot of webfinger wrangling to do that.
I wonder if a federated system would ever beat out a decentralized vision. Mastodon instances come and go and data could be, will be, lost forever, somebody else besides you gets to decide the rules of the road.
Open systems can have closed leadership that does not gel well with the idea of putting users in control of their data,
Greg, I am missing something.
What's the diff in your mind between decentralized and federated? And what closed leadership do you have in mind in each case?
For example, if we do personal activitypubs (which we are doing) and then we federate them, is that decentralized or federated?
Or are you considering federation to mean only large sites with lots of members which federate with other large sites with lots of members?
Federated=open protocols allowing different instances to talk but still requires some central server, an admin and a bunch of users to call that admin a fascist nazi whenever they make a small change.
Decentralized=open protocols all run on individual instances with no concentrated power or loss of data if someone shuts down server
@jgmac1106 @bhaugen @KevinMarks @cwebber @neil the reality is, unless you engineer a protocol to be only capable of supporting single-user apps (if that's even possible), a decentralized network will have a mix of multi-user and single-user instances. It's up to each user to decide which to use. Ideally, at some point, individuals accounts will become totally portable between instances. This is already possible with Hubzilla (using Zot protocol).
... and you don't. That's the whole point of open, federated protocols like #OStatus and #ActivityPub (and even the Diaspora variant of OStatus). The apps that use these are not monocultures (in the #IndieWeb sense) and never have been. !groups exist in OStatus and in AP, but working implementations are still in progress.