Comments inside the docker-compose.yml files?

Firefox will be in a tight corner assuming every other browser vendor picks this up. They can decide to go against it but Firefox does not live in isolation.

https://hacks.mozilla.org/2014/05/reconciling-mozillas-mission-and-w3c-eme/

Yes. If it becomes a success on Chrome, other interested parties will pressure Firefox to adopt the standard as well.

They successfully went after Vanced 2 years ago so it’s shouldn’t be too far fetched for them.

Maybe give cloudflared a try. Works for me even with nextcloud’s ssl (don’t think there’s a way to start NC without the self-signed cert). Couldn’t get it to work with NPM (I admittedly don’t know much about nginx) so I brought in the big gun(s).

deleted by creator

Backblaze b2, borgbase.com. There are also programs like dejadup that will let you backup to popular cloud drives. The alternatives are limitless.

This sounds good just saying it but in practice it’s not possible for AI to fully replace these types of jobs.

Wonder why this wasn’t done earlier. Hopefully we’ll see less of the 404-type pages that has plagued this instance.

Major oof

Yes to all questions. Only drawback I can recall is my banking app refusing to pass Safetynet but the website works good enough.

No minimum requirements. And here you go:

#version: "3.8"
services:
  invidious:
    image: quay.io/invidious/invidious:latest
    restart: unless-stopped
    security_opt:
      - no-new-privileges
    container_name: invidious
    stop_grace_period: 3s
    ports:
      - 127.0.0.1:3000:3000
    environment:
      INVIDIOUS_CONFIG: |
        db:
          dbname: invidious
          user: invidious
          password: superstrongpassword491
          host: postgres
          port: 5432
        check_tables: true
        popular_enabled: true
        login_enabled: false
        statistics_enabled: true
        hsts: true
        hmac_key: *PICK-A-LONG-RANDOM-STRING*
        https_only: true
        external_port: 443
        use_quic: true
        database_url: postgres://invidious:superstrongpassword491@postgres/invidious?auth_methods=md5,scram-sha-256
        force_resolve: ipv4
        domain: *your.domain.com*
    healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw || exit 1
      interval: 30s
      timeout: 5s
      retries: 2
    depends_on:
      - postgres

  postgres:
    image: postgres:15-alpine
    container_name: postgres
    security_opt:
      - no-new-privileges
    restart: always
    # purposefully excluded volumes section
    # the database will reset on recreate
    environment:
      POSTGRES_DB: invidious
      POSTGRES_USER: invidious
      POSTGRES_PASSWORD: superstrongpassword491
    healthcheck:
      test: pg_isready -U invidious -d invidious
      interval: 10s
      timeout: 5s
      retries: 5

I’ve hosted invidious relatively easy for a while now. Simple UI and just works. If anyone needs my compose and config setup, reply and I’ll post it.

Haha. Said the hoader with tonnes of content he’s never going to finish watching.

deleted by creator

Maybe you should familiarize yourself with CentOS Stream and its purpose.

Backup $home and /etc. That should be good enough.

KDE Connect is better than anything these two juggernauts can conceive of.

They provide the best balance for efficiency. Not too powerful enough to be a workhorse and not to weak to run multiple simple applications/services. NUCs are great in that they come with hardware video acceleration tech that’s highly optimized for media transcoding.

You know what the worst part is. We, The people let them do this to us.