Alternative Title: “Bluesky pretty sure these leopards won’t eat their face.”

  • southsamurai@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    73
    arrow-down
    3
    ·
    28 days ago

    I’m way less worried about bluesky as opposed to threads. If anything, it serves as a healthy competitor to mastodon in terms of how it would require a bridge to interact. You have to go out of your way to make it happen.

    But threads is pulling a EEE, and it’s obvious that’s the goal.

    • hash@slrpnk.net
      link
      fedilink
      English
      arrow-up
      14
      ·
      28 days ago

      If they actually had legitimate interest in the fediverse they would be working towards making Instagram interoperable. But of course their established platforms aren’t necessary for EEE.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    40
    arrow-down
    1
    ·
    28 days ago

    Alternative Title: “Bluesky happy to use the standard playbook so long as there’s still bozos willing to contribute free labor for their profit.”

    TFTFY

  • Draedron@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    27 days ago

    I dont see the issue here. Series A investment is normal. I am glad to have a federated alternative to twitter. I know people here hate it but federation is just way more comfortable to use.

    • linearchaos@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      27 days ago

      I don’t like shareholders calling the shots. They just went from eventually needing to make enough money to keep the doors open and the staff paid to needing to make as much money as possible whenever the investors say it’s time.

    • The Hobbyist@lemmy.zip
      link
      fedilink
      English
      arrow-up
      34
      ·
      28 days ago

      From what I understand, bsky’s architecture seems to allow federation at multiple levels. On one side the individual profiles are actually websites and the app aggregates the content almost as an RSS reader. I do see some profiles which are independent like Jeff Gierling’s, so yes federation at the profile level seems to work.

      And this is really important because it is one way to prevent your data from being hostage by the service. Then there is another level of federation. I’m not entirely sure of the terminology here, but there is one aggregator aspect, which is quite compute intensive. And that one I don’t know if there is another instance of it. But functionally speaking, I’m quite impressed by the technical aspect of bsky. There has been a lot of thought put into it.

      And monetizing it is not the issue, the problem is mostly how. That they have some paid features is fine, it’s even important that there are ways to monetize it without milking their users of their privacy.

      Let’s hope this works out and becomes sustainable while respecting the users!

      • Sekoia@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        13
        ·
        28 days ago

        The aggregator is called the Relay, and I haven’t even found anything suggesting one could realistically selfhost it. Then you need to handle the massive stream of data coming through it with AppViews, which are tough to handle too (there are a few but not many iirc).

        That said, I am also impressed with the thought behind ATProtocol. It seems much more robust and defined than ActivityPub.

    • Sekoia@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      7
      ·
      28 days ago

      Bluesky’s federation model is actually quite interesting, they go for a very portable approach vs activitypub’s instance-basis. Unfortunately, there’s still a massive centralization point (the main relay, the only thing that can really handle the firehose), and identity is also centralized, albeit has mechanisms to be decentralized.

      • Sl00k@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        28 days ago

        Aren’t identities already decentralized by using domains you own as your identity? Ex. Incase you’re unfamiliar, my Bluesky @ is my domain I own.

        • Sekoia@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          2
          ·
          27 days ago

          I believe that’s your handle, not your identity. Your handle resolves to your identity, but your identity isn’t directly tied to it, in case you lose the domain.

          • Sl00k@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            27 days ago

            While they definitely do this for handles I’m pretty confident this is also done for DIDs (Decentralized identifiers) and it doesn’t provide a solution if you lose your domain. I think Bluesky (Appview) specifically gets around this by also tying your DID:web to your DID:plc, in case of domain loss. So I think it exists on the protocol but they don’t automatically utilize the decentralization for end-user experience(domain loss) but other appviews can. But I could be wrong.

            https://atproto.com/specs/did

            • Sekoia@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              2
              ·
              27 days ago

              Yeah, did:web exists, but I still called it centralized because it still relies on did:plc pretty much everywhere (though honestly domain name handles might actually be did:web, not sure). Didn’t know about that dual setup by Bluesky though!

    • Drunemeton@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      28 days ago

      FTFA: “Launched federation for self-hosters and developers. Now there are over 1,000 other personal data servers (PDS) outside of Bluesky.”

  • _NetNomad@fedia.io
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    28 days ago

    we here are bluesky are thrilled to accept Series A funding for Face-Eating Leopards, Inc. despite this we ensure that Leopards will not eat your face

  • drdiddlybadger@pawb.social
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    4
    ·
    28 days ago

    Pretty neat. I kind of wish they sold shares direct to users as well. Lemme hold some of the bsky biscuit bro

    • tormeh@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      8
      ·
      28 days ago

      That’s illegal, unfortunately. Only qccredited investors can invest into private companies. There should be a lower limit on that rule, say $100 or something, so naive investors could invest play sums in potentially shady stuff. But there isn’t, so you can’t.

    • Sl00k@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      28 days ago

      I truthfully don’t think this bridge will work long-term because it’s rather clunky for the end users. I think mastodon needs an integration built into their platform so instances can have the choice to turn on a two way atProto connection that creates accounts under the instance identity and writes and reads post to atProto.

      Bluesky doesn’t need to adjust anything as they’ll pick up anything written to atProto.

      • asudox@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        27 days ago

        Or they stop whining about how it would be very hard to contribute the ATProto features into ActivityPub and switch from ATProto to ActivityPub