I can’t unfortunately. They only feature I use is that fact I can access my ipv6 only server via an ipv4 only network.

Watch then deny it cos it will threaten their market capture lol

What good clients are their for piefed? I’ve been using eternity for lemmy. Preferably something on fdroid

Except I’m in rural Australia. Star link is objectively the best option.

Starlink gives me an ipv6 its not static as such but a dynamic DNS can solve that issue. My ISP issue is that my mobile provider doesn’t give me an ipv6 at all so I can’t route to my home server without a gateway to proxy.

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 cad isn’t where it need to be yet unfortunately

That’s what one would assume. But it would be legendary if they where brave enough to put steam os on it. It is the year of the Linux handheld.

The problem with all this cool hardware is they all have locked down boot loaders and u can’t put a truly foss os on em

I would be free from relying on a single google server for anything.

Mastodon has weird federation issues

Its not cos google pay needs to much access its cos google pay needs a special certificate to sign the operating system. The Google android devs love GrapheneOS as they push lots of security patches and bug fixes so they tried to get GrapheneOS signed. Google then ignored GrapheneOS and their own android devs and refuses to sign GrapheneOS. Its purely because google are assholes who don’t want it to work on GrapheneOS.

Probably hexbear and lemmygrad

Is this only for moving to a piefed instance can they not do such a thing for any other instance?

Imagine having google play services and not running a degoogled ROM.

Did u end up making it work?

OK let’s run through some debug steps.

Test to see if samba is working by using a docker volume instead of trying to mount a file path.

If that works we can then assume its purely a file permission issue. U can check/test that by opening a shell inside the docker container and doing investigation from their.

If from the container shell u have perm issues then u will probably need to use the docker parameter to specify the user id of the container to match that of ur host or alternativly set the filesystem to match that of the container (this will lock u out of ur servers user access to the filesystem as u will no longer be owner).

If the container shell has perms to do shit in the mounted volume then it’s a samba config issue. I’ve never done it myself but I’ve heard that samba is a bitch to configure.

Depends how u use it. They often stacked multiple people up and the guy at the bottom would get half chopped and be just suffering their for ages.

So domains are recursive tree structures. So u have node com which has a bunch of nodes below it of different domains which can have sub domains etc. Its like this cos that’s how DNS was designed.

Search engines gives scores to domains and pages. When u say that the content origin of ur page is some other domain the search engines will use that knowledge to adjust rating accordingly.

Say u have 2 domains site1.example.com and site2.example.com the search engine will have a rank for site1, site2, and example.com where the rating of both site1 and site2 effect the rating for example.com.

If the content origin for all federated content has the same origin say instance.fediverse.com then the rating for all federated content will be classified as part of fediverse.com and all content will be working together across all instances boosting the fediverse as a single entity.

It would have to be a common domain. So the content origin would have to be something like instance.fediverse.com the common domain needs to be the base level domain.