There has been a steady trickle of new users here today, and in the past little while, mostly due to the bad decisions that reddit is currently making.

Anyways, welcome! Feel free to look around, and if you have any questions about anything lemmy related, feel free to ask!

Also, if you feel up to it, introduce yourself in the comments below!

edit: Here’s a nice getting started guide for lemmy: https://tech.michaelaltfield.net/2023/06/11/lemmy-migration-find-subreddits-communities/

i should have added it here a while ago!

  • tunetardis@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Thanks.

    Well, here’s an example of what I’m talking about. The post contains nothing but a link but when you follow that, it says You must log in or register to comment.

    But I just noticed elsewhere it says I need to subscribe to !fediverse@lemmy.ml

    So I’ve gone through the motions of doing that, but when I look at Communities -> Subscribed, it now says Subscribe Pending under Fediverse@lemmy.ml.

    I’m going to assume that once approved, I can then comment?

    • Mars@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      What’s likely happening is that when you link through and see “You must log in or register to comment”, you aren’t accessing that post via the lemmy.ca instance. Your account is instance-specific, but as @Aawr said, you can interact with content from other instances (unless that instance or community has rules to the contrary or has blocked your instance).

      The way in which you can access that post via your “home” instance of lemmy.ca is either:

      Using these, I found my way here: https://lemmy.ca/post/626156

      • jnj@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        My big question is why can’t we have auto-generated links to the appropriate lemmy.ca page for communities on remote instances. It seems odd that following links to communities takes you to the host instance when you generally speaking you won’t be logged in there. Hopefully this feature will come in the future (or maybe it already exists but I haven’t found it)

        • Mars@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          That feature is actually partially implemented, but the client you’re using (web browser or mobile app) fights you a bit in interesting ways:

          On web, when typing in a Lemmy community like !fediverse@lemmy.ml the client will try to help you complete it, but it completes to a remote instance link: !fediverse@lemmy.ml

          If you change the markdown for that link to point relatively, then it follows standard URL conventions and works in your current instance: !fediverse@lemmy.ml (You can select view source on this comment to see how I modified this link) However, this same link will probably not work on mobile clients, as the operating system determines how to handle URLs.

          • jnj@lemmy.ca
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 year ago

            Thanks. I’m not sure that’s exactly what I’m imagining, because this still involves hard-coding an instance to the link. People from many different instances might be viewing the link, so I’d imagine a flow like: when you mouse-hover a link to a community, a little popup appears which provides a custom link based on your home instance. So whether !fediverse@lemmy.ml is a link to the lemmy.ml or lemmy.ca domain wouldn’t matter, ideally you’d always get the option of viewing the community from your home instance at a single click. Hope that makes sense, today is my first day after all.

            • Mars@lemmy.ca
              link
              fedilink
              English
              arrow-up
              5
              ·
              1 year ago

              I totally agree. That’s the behaviour I also expected from the default “!”-prefaced community links. Unfortunately it currently doesn’t work that way, but if I have time later this week I may take another look into the source code to see if an easy fix can be done.