• 5 Posts
  • 127 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle








  • But the conversation is unique in each community. And each community may not have federated to every instance. This is the Fediverse, not a single site with sub communities.

    I do think it would be nice if a client/backend could:

    • Take any cross-post link from the main post
    • Query any description/comments for cross posts
    • Add to the currently displayed comments
    • Tack on descriptions as comment blocks with an @ to the cross posting OP to the displayed description
    • Mark cross-posts as read when main is read

    This would be easier in Lemmy, but could be done with a client, Thunder might be interested.









  • What?

    1. That blog entry is almost 7 years old. Sealed Sender came a long time ago.

    2. The literal quote you provide has a link on “exploring techniques” that you didn’t click. It takes you to another blog post for the launch of Private Contact Discovery, which takes you to a repo of the service, but because your cutting and pasting such old stuff even that’s been replaced by a V2.

    Please take a step back and read the technical docs, or at least more recent info.

    As ratcheting and chaining are used, messages are sent with rotating keys on ebery message as the sender/recipient identifiers for the messages, not the phone number. It would be way easier to tap Google for Firebase notifications to get to what you are talking about.

    And the capability argument is moot if it’s been proven in court to not be done today. You could say that about any service that uses push notifications that go through cloud providers.

    Tagging @onlinepersona@programming.dev