Asking because I get reports I make, it would seem rather silly to me if I can’t report misconduct because I’m on my own instance.

Edit: so the answer is yes, another user kindly helped me verify by reporting my test post in the community on my instance. It looks like it sends the report to the relevant people just also sends it to my local admin account for whatever reason lol.

  • @joe
    link
    95
    edit-2
    1 year ago

    You know, it’s surprisingly vague even in the official documentation.

    Let’s test it out. Create a post on your instance, and then make a comment on that post, and I’ll go report them both as “testing” and we’ll see if you get notified.

    Link them here so I can find them.

    • @tool
      link
      English
      81 year ago

      You know, it’s surprisingly vague even in the official documentation.

      You just described literally all of Lemmy’s documentation.

      I had to read the source code for Lemmy to find out what API endpoint to hit, how it worked, and what to expect on return for a script that I was writing. You need to do that for some documented API endpoints as well. Calling it “vague” is a nice way to put it.

    • @[email protected]
      link
      fedilink
      31 year ago

      I have no idea what reporting does. Not even if it is sent. I tried reporting some nudity content in a community, but it was broken en 2 apps, and took a very long time from the browser…

      • @joe
        link
        English
        41 year ago

        What do mean? On the standard lemmy site it should be the 3 dot menu, then the flag (aka, report) on any comment or post.

        What took a long time for you?

        • @[email protected]
          link
          fedilink
          4
          edit-2
          1 year ago

          Finding the report button wasn’t hard. Sending it was. It took like 30 seconds+ of loading to send it.

          • @joe
            link
            English
            11 year ago

            Ohhhh… Well that might be an issue with your specific instance being unresponsive. The reports I just did, however, worked pretty much how you would expect, so it’s not likely to be a lemmy-ui or backend bug.