Just tried again today, even though I wasn’t expecting any different results from the last few Imagine my surprise! I’m pretty sure nothing happened on my end (Sync settings or instance).

¯\_(ツ)_/¯

  • @[email protected]
    link
    fedilink
    English
    28 months ago

    If only we could block entire instances instead of blocking comminity. I got 518 blocks some due to being nok english focused but probably 400 of them being porn i dont want to disable nsfw since not all nsfw is porn it could be gorey games or something

    • @[email protected]
      link
      fedilink
      English
      18 months ago

      You can set a default language in your lemmy account settings to filter non-English posts. As for non-porn NSFW. You could use keyword filters. It won’t be accurate but should be fine for a while. Until a good solution is found.

    • Mom Nom MomOP
      link
      fedilink
      English
      28 months ago

      Yeah, I think the language settings are going to help you out (in Lemmy itself, not the client). I haven’t needed to block any community due to language. You’ll probably want to keep undetermined, according to the warning:

      Warning: If you deselect Undetermined, you will not see most content.

    • Mom Nom MomOP
      link
      fedilink
      English
      28 months ago

      Yeah, I love my small instance as well! It is useful to go to bigger instances when looking for new communities, though, and not being able to do that was making me kinda sad.

      I don’t know why it wasn’t working (kinda glad it wasn’t just me tho - sorry guys, misery loves company and all that 😅) - and I don’t know why it started working again.

      But I am very grateful for it!

      • @[email protected]
        link
        fedilink
        English
        28 months ago

        The search is also searching all instances so sometimes I just search for something and see if any new communities pop up. Overall the experience is really smooth now. :)

  • andrew
    link
    fedilink
    English
    58 months ago

    This feels like a data issue then. Maybe one of the formerly top N instances had a weird unexpected Unicode character that caused a parse failure and it just fell out of the top N.