Conversation

Notices

1. Embed this notice
   fiatjaf (3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub)'s status on Sunday, 25-Jun-2023 23:39:00 JST fiatjaf
   Today I learned that https://fed.brid.gy/docs#translate is supporting Nostr.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Sunday, 25-Jun-2023 23:38:59 JST Alex Gleason

     in reply to

     • Melvin Carvalho
     @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 @3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d I implemented the first draft of that. The second draft broke federation with Pleroma.
   • Embed this notice
     fiatjaf (3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub)'s status on Sunday, 25-Jun-2023 23:39:00 JST fiatjaf

     in reply to

     • Melvin Carvalho
     They also seem to understand the protocol much better than every other outsider.
     
     Do you know anything about it, @de7ecd1e?
   • Embed this notice
     Melvin Carvalho (de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645@mostr.pub)'s status on Sunday, 25-Jun-2023 23:39:00 JST Melvin Carvalho

     in reply to

     • Alex Gleason
     see also this:
     
     https://socialhub.activitypub.rocks/t/fep-fffd-proxy-objects/3172/25?u=melvincarvalho
     
     Possily @alex is going a similar route?
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 26-Jun-2023 00:55:51 JST Alex Gleason

     in reply to

     • Melvin Carvalho
     @3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 It's relevant. Bridges will want a way to represent proxy objects to prevent duplication.
   • Embed this notice
     fiatjaf (3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub)'s status on Monday, 26-Jun-2023 00:55:52 JST fiatjaf

     in reply to

     • Alex Gleason
     • Melvin Carvalho
     This is not what I was talking about, I think.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Monday, 26-Jun-2023 01:21:13 JST Alex Gleason

     in reply to

     • Melvin Carvalho
     @3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d @de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645 The original object has its own globally unique ID. Eg event.id on Nostr, object.id in ActivityPub.
     
     So you expose that ID to the bridged network, and implementations can combine objects that share the same proxy ID.
     
     For AP objects bridged to Nostr, it could look like:
     
     ["proxy", "activitypub", "https://gleasonator.com/objects/123"]
     
     Clients could combine events with the same proxy ID.
     
     There are obviously problems with trust (among other issues). But I think it will be necessary to solve this problem.
   • Embed this notice
     fiatjaf (3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d@mostr.pub)'s status on Monday, 26-Jun-2023 01:21:14 JST fiatjaf

     in reply to

     • Alex Gleason
     • Melvin Carvalho
     I don't see how to prevent duplication. Bridges are hacks.