Conversation

Notices

1. Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Sunday, 27-Jan-2019 15:53:17 CET Alex L 🇮🇹 🇻🇪 🇸🇾

   Remote profile options...

   • Christopher Lemmer Webber

   @cwebber I made these diagrams, can you please tell me if my understanding is correct?

   • Christopher Lemmer Webber, maloki 🍵 and Polychrome :clockworkheart: repeated this.
   • Christopher Lemmer Webber (cwebber@octodon.social)'s status on Sunday, 27-Jan-2019 16:08:29 CET Christopher Lemmer Webber

     Remote profile options...

     @alexl That seems right to me.

   • Christopher Lemmer Webber (cwebber@octodon.social)'s status on Monday, 28-Jan-2019 08:38:49 CET Christopher Lemmer Webber

     Remote profile options...

     • Gadfly (-booq-)

     @gaditb @alexl No reason that can't be supported, and since we thought s2s would be "harder" than c2s, we figured that this would happen even

   • Tomas SA2TMS (tomas@social.umeahackerspace.se)'s status on Monday, 28-Jan-2019 09:37:57 CET Tomas SA2TMS

     in reply to
     @alexl You could think even bigger. There shouldn't be "Mastodon" or "PeerTube" native clients, but rather everything should be specified in RFCs such that entirely generic clients can be written. Then trouts could be applied to certain BDFLs until they actually implement said RFCs
     Diogo Cordeiro likes this.
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Monday, 28-Jan-2019 14:23:27 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @tomas there would be confusion, see XMPP clients... we need very different platforms (blogging, microblogging, newspapers, video and audio streaming, issue tracking, collaborative editing, ) each one with its own user experience but federating "actions" and "objects".

     For example I could use even a Mastodon client to reply to comments in a issue on GitLab but I would still need a native GitLab client to perform actions like pull request or fork.

   • maloki 🍵 (maloki@elekk.xyz)'s status on Monday, 28-Jan-2019 14:57:03 CET maloki 🍵

     Remote profile options...

     in reply to

     • Christopher Lemmer Webber

     @alexl @cwebber I still love this image. Every time I see it a little bit of happiness starts bubbling.

   • Tomas SA2TMS (tomas@social.umeahackerspace.se)'s status on Monday, 28-Jan-2019 21:32:23 CET Tomas SA2TMS

     in reply to
     @alexl Myes, but a lot of these things would need to be implemented in most clients anyway. Webtorrent for example, would be useful in all kinds of places, not just PeerTube. And if you have that in your generic AP microblogging client, and the client knows about banggroups, then it is effectively also a PeerTube client. But that said, branding can be a very useful and good thing.
     
     You know, the comparison to XMPP is apt. I've said before that AP will start having the same problems that XMPP has had to deal with. This always happens.
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Monday, 28-Jan-2019 23:46:11 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @tomas I disagree, it's not a matter of just branding, but having different platforms with different features for different people. If an actor is on another platform expect less interactions with one using the same platform or login in the other platform with the same account and enjoy it.

     XMPP approach was proven wrong and in fact anything else follow it so I don't know what you are referring to...

   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Monday, 28-Jan-2019 23:53:02 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @tomas *didn't follow it

   • Tomas SA2TMS (tomas@social.umeahackerspace.se)'s status on Tuesday, 29-Jan-2019 09:15:17 CET Tomas SA2TMS

     in reply to
     @alexl I dunno, to me "platforms" in a federated open system are the same as branding. I guess time will tell..
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Tuesday, 29-Jan-2019 11:25:21 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @tomas Mastodon and Pleroma target different users, same for Plume and Write.as. Different user experience, different hardware resources needed. Different developing models (community-driven etc). Different languages, frameworks and technologies.

     AP is intended to federate everything around the concepts of activities. How can you think an all-in-one social network would be better? We had Diaspora already. AP can be a totally new approach to Web not only social networks

   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Tuesday, 29-Jan-2019 13:33:34 CET MMN-o ✅⃠

     in reply to

     • xmpp
     @alexl what do you imply that !XMPP's approach was? And how does it differ from ActivityPub's approach?
   • Tomas SA2TMS (tomas@social.umeahackerspace.se)'s status on Tuesday, 29-Jan-2019 13:45:18 CET Tomas SA2TMS

     in reply to
     @alexl You know what? Sure. People are excited about federation again and that's good. It's not me who has to roll the boulder up the hill after all, and maybe the API incompatibility issue will be resolved in time
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Tuesday, 29-Jan-2019 17:08:08 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • MMN-o ✅⃠

     @mmn
     I'm not an expert but my understanding is:

     XMPP: trying to define spec per-feature, hope people implement XMPP servers and clients, assuming the user knows each client and each server which feature/spec support.

     ActivityPub: federating everything that involves actions, actors and objects, defining how communications happen and provide some example of actions etc for common use cases.

     Every platform can implement AP because is very abstract, see Mastodon.

   • 0x1C3B00DA (0x1c3b00da@edolas.world)'s status on Tuesday, 29-Jan-2019 17:24:43 CET 0x1C3B00DA

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @alexl @tomas

     Mastodon and Pleroma target different users, same for Plume and Write.as

     That’s not true. They’re targeting the same space and same users. They have different UX because they’re different projects built by different teams. These AP projects fall into buckets like (microblogging, macroblogging, video sharing) and any client made for one would likely work for another project in the same bucket. Specific features may be missing or only available on specific servers, but the overall experience should be the same.

   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Wednesday, 30-Jan-2019 06:29:46 CET MMN-o ✅⃠

     in reply to
     @alexl Right, I think you've managed to misunderstand both XMPP _and_ AP in this case.
     
     You might want to check out the well authored, established and implemented XEPs out there for XMPP and compare with AP where this doesn't exist for the most part. The AP base spec might be object agnostic, which I think you're using as the base argument?, but XMPP is too.
     
     They're not comparable in maturity.
     tuttle likes this.
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Wednesday, 30-Jan-2019 12:06:17 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • MMN-o ✅⃠

     @mmn XMPP totally failed, it was OK for very basic single chat ten years ago. Now clients for Android, desktop and Web implement different sets of features.

     With XMPP I can't say to someone "register to platform.com and download a client for your device". Instead Mastodon IS a platform and it has ITS OWN clients that offers consistent UX.

     XMPP can't be abstract as AP because they are protocols for totally different things. Matrix replaces XMPP.

   • Tomas SA2TMS (tomas@social.umeahackerspace.se)'s status on Wednesday, 30-Jan-2019 17:40:14 CET Tomas SA2TMS

     in reply to
     @alexl That's still just branding
   • Alex L 🇮🇹 🇻🇪 🇸🇾 (alexl@mstdn.io)'s status on Wednesday, 30-Jan-2019 20:00:57 CET Alex L 🇮🇹 🇻🇪 🇸🇾

     Remote profile options...

     in reply to

     • Tomas SA2TMS

     @tomas ...

   • MMN-o ✅⃠ (mmn@social.umeahackerspace.se)'s status on Thursday, 31-Jan-2019 00:13:16 CET MMN-o ✅⃠

     in reply to
     Hello brick wall.
     tuttle and Remember When™ News! like this.
   • tuttle (tuttle@santsenques.cat)'s status on Thursday, 31-Jan-2019 02:05:21 CET tuttle

     Remote profile options...

     in reply to

     • MMN-o ✅⃠
     • tuttle
     @alexl Yes, and even more, ActivityPub, XMPP and Matrix are different to each other in the sense they all are run SMTP under the hood. @mmn
     MMN-o ✅⃠, Zash and vaeringjar-highone like this.
   • tuttle (tuttle@santsenques.cat)'s status on Thursday, 31-Jan-2019 02:08:33 CET tuttle

     Remote profile options...

     in reply to

     • MMN-o ✅⃠
     • tuttle
     @alexl Well not completely, AP is written in node.js, the others aren't. @mmn