Admin on the slrpnk.net Lemmy instance.

He/Him or what ever you feel like.

XMPP: [email protected]

Lemmy alt: @[email protected]

Avatar is an image of a baby octopus.

  • 1.77K Posts
  • 6.79K Comments
Joined 4 years ago
cake
Cake day: September 19th, 2022

help-circle








  • It’s not generally a bad idea, but you get very low grade heat if you want to keep the PV panels cool and in general you will quickly run into the issue what to do with all the heat on sunny days, while not having enough on cloudy days.

    I know this sounds trivial, but you need very little solar thermal surface area to cover all your domestic hot water needs so with the above solution you will run into a too much heat problem rather quickly and convertig it into something else is not feasible due to the very low grade of it (40°C or so).

    Maybe a solution for large public outdoor pools 🤷






  • This is not a cultural failing that can be fixed by asking people to be nicer, which was roughly Scott Jenson’s prescription. Nor is it resolved by pointing to the protocol’s openness, which was roughly the community’s response. Neither prescription reaches the actual problem, because Mastodon’s governance tools sit at the instance level and the community’s experience happens at the federation level. Mastodon was built as open infrastructure at the federation level and community at the instance level. The Jenson thread demonstrates that the community has long since reversed this: they experience the federation as their community, and the instance as an administrative detail. The software has not caught up, and until it does, the community will keep enforcing its boundaries the only way the federation layer allows: person by person, reply by reply.

    Thoughtful article overall, but I think what is describes is a design problem of Twitter like micro-blogging. There really is only a void to shout into, and I don’t really see how software can catch up to anything there. I also don’t really understand how this problem is specific to the Fediverse/Mastodon, with even the pre-Elon Twitter being famously toxic for very similar reasons.

    Lemmy and other “community” based Fediverse software has much less of this problem, because there is a venue i.e a community to post into which has a theme, rules and moderators.





  • This is the botPolicy.yaml that we use on slrpnk.net :

    bots:
      - name: known-crawler
        action: CHALLENGE
        expression:
          # https://anubis.techaro.lol/docs/admin/configuration/expressions
          all:
            # Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36
            - userAgent.contains("Macintosh; Intel Mac") && userAgent.contains("Chrome/125.0.0.0") # very old chrome?
            - missingHeader(headers, "Sec-Ch-Ua") # a valid chrome has this header
        challenge:
          difficulty: 6
          algorithm: slow
    
        # Assert behaviour that only genuine browsers display.
        # This ensures that Chrome or Firefox versions
      - name: realistic-browser-catchall
        expression:
          all:
            - '"User-Agent" in headers'
            - '( userAgent.contains("Firefox") ) || ( userAgent.contains("Chrome") ) || ( userAgent.contains("Safari") )'
            - '"Accept" in headers'
            - '"Sec-Fetch-Dest" in headers'
            - '"Sec-Fetch-Mode" in headers'
            - '"Sec-Fetch-Site" in headers'
            - '"Accept-Encoding" in headers'
            - '( headers["Accept-Encoding"].contains("zstd") || headers["Accept-Encoding"].contains("br") )'
            - '"Accept-Language" in headers'
        action: CHALLENGE
        challenge:
          difficulty: 2
          algorithm: fast
    
      - name: generic-browser
        user_agent_regex: (?i:mozilla|opera)
        action: CHALLENGE
        challenge:
          difficulty: 4
          algorithm: fast
    
    status_codes:
      CHALLENGE: 202
      DENY: 406
    
    dnsbl: false
    
    #store:
    #  backend: valkey
    #  parameters:
    #    url: redis://valkey-primary:6379/0
    

    I think I just took it over from Codeberg.org back from when they still used Anubis. Nothing really relevant to Lemmy specifically and it is only in front of the frontends, not the s2s federation API.

    It seems though like there are some crawlers that use 3rd party hosted alternative frontends to crawl (unintentionally?) through the federation API, so something in front of that would be useful I guess.