PS- The “real” (non-joke) full guide for the Masto-curious is here.

  • poVoq
    link
    fedilink
    91 year ago

    Subscribe to hashtags that interest you, them based on the posts that come up through that follow users that seem to have related interests.

    • @kristoff@infosec.pub
      link
      fedilink
      11 year ago

      hi,

      The problem with hash tag-following is that it some on the messages that enter the instance in some way (either local or from the federation). This works great on big Instances and on specialised instances. However, on smaller less-special instances (like personal instances or -say-an instance for a mid-sized city with 50 members) … it works much less.

      But that is then where grup.pe and following public instances of remote instances comes in.

      Kr.

      • poVoq
        link
        fedilink
        21 year ago

        Smaller instances can subscribe to federation relays to ingest more messages. Works quite well, but does come at a higher server resource use.

        • @kristoff@infosec.pub
          link
          fedilink
          English
          11 year ago

          Hi, Correct. For you info. I co-manage a activity-pub relay for fediverse instances oriented towards hamradio. If you are interested in peering, feel free to send me a ping)

      • @HughJanus@lemmy.ml
        link
        fedilink
        1
        edit-2
        1 year ago

        Hello!

        Hard to make sense of what you’re saying here, but hashtags definitely work across instances.

        Sincerely,

        • HughJanus
        • @kristoff@infosec.pub
          link
          fedilink
          English
          1
          edit-2
          1 year ago

          Hi Hugh,

          To be clear. This is not about the tags itself. It’s about the system of tag-following and how it is implemented on the fediverse. It is due to how the fediverse (acitivtypub) works and how (or why) messages are routed from one instance to another.

          There is a major different on how following (people) and how tag-following work. (perhaps the simularity in name is not such a good choice)

          The basic idea of following (people) is this: Consider that you are me are on a different instances and I want to follow you; so I hit the “follow” buttom.

          What actually happens is this:

          • My instance sents an activitypub message to your instance. That message contains the information about me and you … and that way, your instance is aware that I (on my instance) want to follow you (on your instance)
          • when you then write / boost / … a post, your instance will then forward that post to my instance (based on the information received in step 1), which will then put it in my personal inbox stream.

          So far, so good. I am happy to read your (very interesting) posts, and you are happy as your messages gets forwarded to a lot of people who think you are an awsome guy!

          Tag-following however is based on a very different system.

          • you do a tag-follow request. What this does is that this tells your local instance that you are interested in all messages that contain the tag (say) “#caterday”

          • What this will do is this: If (in any way) a message enters your instance and that message contains the tag “caterday”, your instance will drop a copy of that message in your inbox steam, … which results in another post with a nice cat-image in your personal stream. Yeah!

          • What this does NOT do: Unlike the “following-people” system, tag-following is purely local thing. (“local” means “on your own instance”). So, what does NOT happen is that that your instance has started sending messages to all instances out there on the fedivere saying “hey … here is somebody who is interested in cats … please send me all these posts”.

          The main point here is that tag-following is only local between you and your own instance. Not more than then.

          In essence, … the important thing here is the first part of my message above: “If (in any way) a message enters your instance, and that message containts the tag …”

          So, then the question is: “what are the mechanisms so that a post enters an instance? (and -hence- be subject to tag-following)” This could happen in two ways:

          • because somebody local on the instance writes a post.
          • because somebody on a remote instance writes a post AND somebody on the local instances follows that person. As explained above, that message will get forwared by the remote host to your local instance.

          So, to put things together, Consider we are on different instances, I write a post with the #caterday tag, … but neither you or anybody else on your instance follows me, … the video of my cat attacking a ball of cotton will NOT reach you. (bad luck for you … you should have followed me :-p )

          Does this mean that tag-following is useless? No, not at all.

          When does tag-following work very well? To give a practicle example. I have an account on mastodon.radio (an specialised instance for amateur-radio) and overthere I do tag-following of #electronics.

          That works very well because

          • there are a lot of ham-radio people doing electronics
          • there are also lot of people on other instances who are into building electronics … but there is a very big chance that they are followed by at least one person on mastodon.radio. So their posts get forwarded to mastodon,radio … which will then also appear in my inbox due to tag-following. This really works very well, and provides me with a good stream of messages with a good signal-to-noise ratio.

          When does tag-following not work well?

          • if you have a personal instance as I also do.
          • if you are on a smaller instance and you have a less common interest. So, if you happen to be the only metalhead on (say) a 50 member instance that serves your local city, there is a very little chance that a tag-follow for your favorite all-female Japanese metal band will produce much content.

          What can you do if you are in the 2nd senario?

          If there exists an instance dedicated to your interest (that still accepts people)

          • get an account on that instance and use a multi-account app like fedilab

          • use an app like fedilab to remote-read the public feed of that instance, find interesting people, follow them with your current fediverse account you already have, and build up your list of interesting people to follow that way.

          • switch to lemmy or kbin :-) (as lemmy and kbin are by nature more community-based)

          • follow the lemmy/kbin community from within your mastodon/fediverse account.

          If you happen to be interested in something very specific and the other nerds are all spread out over a zillion different fediverse instances out there:

          A nice exercise to get a good feeling about this is to get both an account on a mid-side instance and set up your own personal instance. The different in how to approach the fediverse become apparent quite fast.

          Hope this helps :-)

      • @HughJanus@lemmy.ml
        link
        fedilink
        21 year ago

        Honestly the language problem is a huge one. Probably 50% of my feed I can’t even read. There are language filters so that you can set the language of your post but people do not use them. I joined an English-only instance but recently they were accused of being racists so they rolled that rule back.

      • poVoq
        link
        fedilink
        21 year ago

        Some instances have built in auto translation these days, works quite well in my experience.

        But if language filtering works everywhere except when following hashtags that sounds like a bug and you should probably see if there is an issue for it on the Mastodon bugtracker, and if not make one.

        • @HughJanus@lemmy.ml
          link
          fedilink
          11 year ago

          I haven’t seen any with auto translation. I have seen ones with a translation feature but, presumably to conserve resources, it only does it after you click the button, which makes it most pointless, in my opinion.