Conversation

Notices

1. Embed this notice
   Sick Sun (sun@shitposter.world)'s status on Saturday, 28-Sep-2024 14:01:01 JST Sick Sun

   The thing about ActivityPub is, just because you used half a dozen W3C specs (or more!) to construct your project doesn't mean it will automatically work with anything else lol.

   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Saturday, 28-Sep-2024 14:04:00 JST Sick Sun

     in reply to
     The Fediverse thing I am working on currently is no longer compatible with any other system, only with itself. It has been determined that I shall build a thing that contains no legacy (read: Mastodon) compatibility, that will be added after it has basic features and can talk to itself.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 28-Sep-2024 15:35:19 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @sun Well after all W3C is pretty bad when it comes to designing for strong interoperability.
   • Embed this notice
     mothball蛾玉 (和文化研究部) (moth_ball@shitposter.world)'s status on Saturday, 28-Sep-2024 18:46:51 JST mothball蛾玉 (和文化研究部)

     in reply to
     @sun I'm actually really excited for whatever this turns out to be. I feel like I have a front row seat to something that will be very important later on.
     Sick Sun likes this.
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Monday, 30-Sep-2024 20:44:22 JST Sick Sun

     in reply to

     • Ignas Kiela
     @ignaloidas I looked it over and leveraging these specs only really means you don't have to spec what you're doing yourself as much, you just have to reference the specs. Just because you use a DID for identity doesn't mean anything that handles DID is going to understand when you link it to activitypub
   • Embed this notice
     Ignas Kiela (ignaloidas@not.acu.lt)'s status on Monday, 30-Sep-2024 20:44:24 JST Ignas Kiela

     in reply to

     @sun@shitposter.world tbh the more W3C specs you use, the less cross compatibility you're likely to get

   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Monday, 30-Sep-2024 20:46:43 JST Sick Sun

     in reply to

     • Ignas Kiela
     @ignaloidas I just realized you probably meant "compatibility with Mastodon." Yeah, I have decided to just go my own way and make something similar but not compatible.
   • Embed this notice
     Ignas Kiela (ignaloidas@not.acu.lt)'s status on Monday, 30-Sep-2024 20:48:07 JST Ignas Kiela

     in reply to

     @sun@shitposter.world I mean, my comment was more of a joke about how most W3C specs concern browser stuff, and the more complex stuff in browsers that you're doing, the more likely it is that it's not going to work with one of them

     Sick Sun likes this.
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Monday, 30-Sep-2024 20:57:29 JST Sick Sun

     in reply to

     • Ignas Kiela
     @ignaloidas
     so far using:
     
     did:web and did:key and foaf for identity
     JWK for keys
     JWT for authentication
     Solid Web Access Control for authorization
     JSON-LD representation for everything.
     
     ALL of this still permitted by the AP spec lol
   • Embed this notice
     Sick Sun (sun@shitposter.world)'s status on Monday, 30-Sep-2024 21:06:00 JST Sick Sun

     in reply to

     • Ignas Kiela
     @ignaloidas the person and I that are working on this want to do this, when we have more, I'll ping you. Most of the work on the activitypub part is just defining things better but it does have breaking changes.
   • Embed this notice
     Ignas Kiela (ignaloidas@not.acu.lt)'s status on Monday, 30-Sep-2024 21:06:02 JST Ignas Kiela

     in reply to

     @sun@shitposter.world tbh I would be tempted to create a new protocol and only provide mastodon style AP for backwards compat
     
     honestly feels like a decently well designed replacement could still propagate through the ecosystem