@atomicpoet @CommissarMatis this isn't the point. HTTP was essentially made up by one guy all by himself in CERN. As was HTML.
See the difference?
Top-level
@atomicpoet @CommissarMatis this isn't the point. HTTP was essentially made up by one guy all by himself in CERN. As was HTML. See the difference? 7 comments
@atomicpoet @CommissarMatis @evan I don't think a single thing was started at W3C, except PICS perhaps. And I'm all ears when it comes to improving ActivityPub. @rigo @CommissarMatis @evan Well, let’s start with something obvious: nomadic identity. @atomicpoet @rigo @CommissarMatis what do you mean by "nomadic identity"? @atomicpoet If you mean being able to move a public identity between implementations, that's what the URL- or Webfinger-based identity is supposed to let you do. You should be able to export data from a Mastodon server, import it to another system, change the DNS, and everything just keeps on working. I realise that's not how things work right now, but that's the intention of the protocol. Your identity is your Webfinger, and you can move it where you want. @evan I guess one of the frustrating aspects of ActivityPub is that it can do a lot of things “in theory”. But so much of its potential isn’t being fully utilized in practice. @atomicpoet @evan Personally I think ActivityPub is still in the early days. Give it time. Eventually we'll see full utilization of it's potential. |
@rigo @CommissarMatis And much of ActivityPub didn’t start at the W3C. It was an iteration of OStatus. And prior to that, work done by @evan with his startup identi.ca.
Now one thing I will say is that W3C validation was important, and was probably what created momentum for broad adoption.
Anyway, competition isn’t bad. If anything, AT protocol could be the kick in the pants to improve ActivityPub.