I think that’s a bit different. If all desktop OSs are affected by this law, Apple is in no better or worse position than their competitors. The mach kernel that macos is built around would still be available. TBH, I’m not even sure how reliant Apple still is on the mach source. If such a law were to effectively outlaw Linux, it would have massive implications for pretty much every company with a moderate or bigger enterprise footprint.

There’s a shirt that you could buy where a kid is asking his dad what clouds are made of. Dad replies, “Linux servers, mostly.” It’s no less true today than it was then.

Apple and Microsoft are both rather large Linux customers. On desktop, they sell their operating systems, but both of them use a lot of Linux in the enterprise. Apple more so, but Microsoft is no slouch.

From what I can tell, notes are stored in the DB, but can be exported as JSON, or I think markdown. It sure about markdown. I’ve only been able to export JSON, and it didn’t include the image I had embedded in the note. Whatever isn’t a note (images, movies, pdf, doc, etc.) is stored on the file system in a directory structure that files them under heap -> asset checksum. Thumbnails are included there if applicable. In that regard, it kind of forces you to use its folder structure.

Some notes:

• This can be self-hosted. My working compose.yml is below
• Free until August, and he has a discord for feedback, but I can’t find the invite. It was in the live-stream he did.
• He said in the stream that he’s open to open sourcing the project. Just not there yet.
• He admits the licensing is a little confusing. He stressed that self-hosting does not have a storage or block limit. Also, self-hosting is possible with all licenses (I think).
• Supports macOS, Linux, Windows, iOS, and Android (in beta I think)

My compose file:

services:  
  heaper-postgres:  
    image: ghcr.io/janlunge/heaper-postgres:latest  
    container_name: heaper-postgres  
    environment:  
      POSTGRES_USER: $POSTGRES_USER  
      POSTGRES_PASSWORD: $POSTGRES_PASSWORD  
      POSTGRES_DB: $POSTGRES_DB  
    ports:  
      - "5432:5432"  
    volumes:  
      - /path/to/heaper/postgres:/var/lib/postgresql/data  
    networks:  
      - heaper  
    healthcheck:  
      test: ["CMD-SHELL", "pg_isready -U heaper -d heaper || exit 1"]  
      interval: 10s  
      timeout: 5s  
      retries: 5  
      start_period: 20s  

  heaper:  
    image: ghcr.io/janlunge/heaper:latest  
    container_name: heaper  
    platform: linux/amd64  
    environment:  
      HOSTNAME: heaper.caruthers.us  
      ENABLE_INTERNAL_POSTGRES: "false"  
      DB_HOST: heaper-postgres:5432  
      DB_USER: $POSTGRES_USER  
      DB_PASS: $POSTGRES_PASSWORD  
      DB_NAME: $POSTGRES_DB  
    ports:  
      - "3000:443"  
      - "4499:80"  
    volumes:  
      - /path/to/heaper/config:/usr/src/app/config  
      - /path/to/heaper/thumbnails:/mnt/thumbnails  
      - /path/to/heaper/storage:/mnt/storage  
    networks:  
      - heaper  
    depends_on:  
      heaper-postgres:  
        condition: service_healthy  
    healthcheck:  
      # Docs show example health probes; adjust host/port if your container differs.  
      test: ["CMD-SHELL", "curl -fsS http://localhost/api >/dev/null || exit 1"]  
      interval: 15s  
      timeout: 5s  
      retries: 5  
      start_period: 30s  

networks:  
  heaper:  
    name: heaper  

I have the DB, config, and thumbnails on local NVME, and storage on NFS-mounted NAS. Working fine so far.

ETA: Correction in compose file.