Self Proclaimed Internet user and Administrator of Reddthat

  • 161 Posts
  • 182 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle










  • I believe I’ve fixed it.

    A recent docker update no longer supports overriding hosts with hostnames. (I was telling mlmym that ‘reddthat.com’ is ‘lemmy-ui’. Which would make it request directly to the lemmy-ui container rather than going back out to CF and back again.

    (For others/if you want to know the nitty gritty). I was doing this:

        networks:
          lemmy_internal:
        extra_hosts:
          - "reddthat.com:lemmy-ui"
    

    Which did actually work, but now it doesn’t since I updated/installed docker compose v5.0.0. (Seems the correctly enforce the host:IP format now). So I had to do a work around.











  • For our application process, as we only require 1 piece of information which is easily scriptable from the API (if someone were to go into that level of automating). But there is at this time 1+ people who regularly signup wait a week+ and then use the account to post something , wait 2 hours and then delete the whole account. (Resulting in all links and history to be deleted).

    In the recent Lemmy update that fixed the exploit where even admins would no longer be able to view the account(s).

    The actual bots on the other hand are completely dumb and could be automated away, but at the end of the day, I don’t want to destroy someone’s account creation due to some LLM hallucination.
    And some are obvious bot names, (like “holidaydestination”) but still fill out the form correctly.

    Reports are case by case basis with a fair amount of leeway for reddthat users as just because I am from a specific country doesn’t mean I have the right to impose my biases on others.