I just saw some posts from beehaw.org and lemmy.world, looks like we’re back in business!

  • ernest@kbin.social
    10·
    3 years ago

    For now, I’m just preparing the groundwork, but first, I need to get some sleep :p

  • exscape@kbin.social
    1·
    3 years ago

    Indeed, pretty cool!

    First thing I noticed though is that I’d really like to know which instance a thread is actually on.

    For example, this post:

    Going back to Reddit feels bad (kbin.social)
    polygon, 2 hours ago to chat

    … is actually on [email protected], even though it says “kbin.social” and just “chat” below. Pretty confusing.

    EDIT:
    There’s at least one fix for this in the meantime – get this userscript:
    https://greasyfork.org/en/scripts/468612-kbin-enhancement-script

    • Kichae@kbin.social
      1·
      3 years ago

      I get what you’re saying – that the link source indicator should point to the instance that hosts the group – but it’s a quirk of how federation works that the thread is actually on kbin.social. And, well, any other site that’s following the thread.

      Everything is actually local on the fediverse. It’s just that not everything has to originate from the local website. Federation works via content mirroring, which is why the URL for any given Magazine you’re viewing still starts with kbin.social. You’re not viewing remote content, you’re viewing local content that was imported from a remote source. And the link indicator is telling you where kbin has been told the content resides.

      And that’s on kbin.social.

      I think maybe the link source indicator just shouldn’t render if the thread doesn’t have a link purposefully attached to it, and the Magazine name should show the full name@host indicator.

    • czech@kbin.social
      0·
      3 years ago

      Also: I think usernames from other instances should show which instance they’re from.

  • EnglishMobster@kbin.social
    0·
    3 years ago

    I’m still not able to subscribe to magazines on here from Lemmy, which is interesting. Maybe federation needs some time to catch up.

    • Attempted_Render@kbin.social
      0·
      3 years ago

      Same. I’ve tried searching for kbin from lemmy, but nothing ever pops up. Not sure if I’m doing something wrong or it just isn’t fully working yet.

        • Zana@kbin.social
          1·
          3 years ago

          What about for Lemmy from Kbin? Like on the Lemmy page it says to type [email protected] into your search to get the result, but when I enter that in the Kbin search bar it errors out.

            • Nepenthe@kbin.social
              0·
              3 years ago

              This would insinuate kbin is the only one requiring the whole URL, and it seems like that would severely hamper the discovery of only kbin magazines from non-kbin instances. Which is like. Most instances in existence. :/

              Unless you mean the discovery is fine and it’s only how you have to subscribe to them, which I can’t check because I have no interest in setting up other accounts atm

              • EnglishMobster@kbin.social
                1·
                3 years ago

                IMO, Lemmy is the one that’s incorrect by requiring the URL. Kbin does the same thing Mastodon does by having it use the @ instead.

    • Teali0@kbin.social
      1·
      3 years ago

      I mean seriously? This dude’s project has had hardly any downtime (like 100% inaccessible downtime) in the last few days during a massive migration. How impressive is that? He was able to find a solution with cloudflare where, sure things were a little slow to load and didn’t federate, but I never found myself unable to access kbin. On top of that, he’s communicating clearly and often. I hope this succeeds. @ernest has absolutely earned it.