🇦🇺𝕄𝕦𝕟𝕥𝕖𝕕𝕔𝕣𝕠𝕔𝕠𝕕𝕚𝕝𝕖

  • 4 Posts
  • 207 Comments
Joined 1 year ago
cake
Cake day: March 20th, 2024

help-circle







  • Here is my searxng rocker compose:

    services:
      redis:
        container_name: redis
        image: docker.io/valkey/valkey:7-alpine
        command: valkey-server --save 30 1 --loglevel warning
        restart: unless-stopped
        networks:
          - local_bridge
        volumes:
          - ./data/reddis:/data
        cap_drop:
          - ALL
        cap_add:
          - SETGID
          - SETUID
          - DAC_OVERRIDE
        logging:
          driver: "json-file"
          options:
            max-size: "1m"
            max-file: "1"
    
      searxng:
        container_name: searxng
        image: docker.io/searxng/searxng:latest
        restart: unless-stopped
        networks:
          - local_bridge
          - proxy
        volumes:
          - ./data/searxng:/etc/searxng
        environment:
          - SEARXNG_BASE_URL=https://${SEARXNG_HOSTNAME:-localhost}/
          - SEARXNG_SECRET=${SEARXNG_SECRET}
        cap_drop:
          - ALL
        cap_add:
          - CHOWN
          - SETGID
          - SETUID
        logging:
          driver: "json-file"
          options:
            max-size: "1m"
            max-file: "1"
    
    networks:
      local_bridge: # local bridge with ipv6 internet access
        driver: bridge
        enable_ipv6: true
      proxy:
        external: true
    

    And my searxng settings:

    searxng/data/searxng/settings.yml
    # see https://docs.searxng.org/admin/settings/settings.html#settings-use-default-settings
    use_default_settings: true
    
    server:
      # base_url is defined in the SEARXNG_BASE_URL environment variable, see .env and docker-compose.yml
      limiter: false  # can be disabled for a private instance
      image_proxy: false
    ui:
      static_use_hash: true
      query_in_title: true
      infinite_scroll: true
      default_theme: simple
      theme_args:
        # style of simple theme: auto, light, dark
        simple_style: dark
    redis:
      url: redis://redis:6379/0
    
    
    search:
      safe_search: 0
      autocomplete: 'duckduckgo'
      default_lang: "en"
      formats:
        - html
        - json
    
    
    outgoing:
      # default timeout in seconds, can be override by engine
      request_timeout: 3.0
    
    
    enabled_plugins:
      - 'Hash plugin'
      - 'Basic Calculator'
      - 'Self Informations'
      - 'Tracker URL remover'
      # - 'Ahmia blacklist'
      - 'Hostnames plugin'  # see 'hostnames' configuration below
      - 'Open Access DOI rewrite'
    

    And the proxy network is just the docker network that nginx is connected to. Here is my nginx conf https://github.com/muntedcrocodile/nginxconf .












  • The biggest mistake the fediverse as a whole made was not having a standard account object.

    Their should also be universal handles. Like u should be able to do @someusername and that is a standard user across all federated services everyone all instances.

    So if we where to do fediversal account tags how would that work? What would a home instance mean? How could u trust that u don’t just have some random instance impersonating you?

    Well their is a solution for this. Ik I’m going to get lots of hate for suggesting this but please just hear me out. This is the exact issue that blockchain solves. U use the blockchain as a ledger that links a username to a public key. Then any activity signed by the associated private key coming from any instance is that user. Now to address the issues that everyone is gonna bring up from their instinctive dismissal of a blockchain. U would choose the objectively best blockchain XMR due to low fees, low environmental impact, scalability, etc. This means that registering an account or changing the usernames public key would cost (as of present) $0.001. How this fee is paid is to be decided but allocating donation money to it would work (to register every single user on lemm.ee would cost about $50).

    OK so what about the whole key pair thing that doesn’t sound very noob friendly. Well u just let an instance do it for you like most of the crypto exchanges do. This means that accounts would be portable across instance and even platforms.

    So how does a server know where to send data so u receive it. Well u still have a “home instance” that acts the same as Activpub does now. Just maintain a federated ledger where a user can change their “home instance” verified with their signature.