If you’re comparing stock Android against stock iOS, Apple has more privacy protections against tracking because of App Tracking Transparency.

I have two phones as daily drivers, one Android and one iPhone. Compared to Android, the iPhone is very restrictive and locked down. Adblockers don’t work and you’re forced to use whatever iOS interface it throws at you. Buttons and gestures move around with every update. There’s no way to view and manage internal files, no sideloading, lots of options that are just not accessible to normal users.

The positive side is that iPhones are very optimized and I can get similar performance to my Android phone despite the iPhone being older and having worse specs. The closed ecosystem also has its benefits, because it makes data very hard to get out, so I use the iPhone as a device to sandbox all the Meta crap that I’m forced to use.

Is renaming the instance domain without reinstalling Lemmy related to changing the WebFinger query? It’s the trick some instances use to have a different instance domain from their username domain, like @user@domain.com while the instance is mastodon.domain.com.

Hate speech laws in real life are also very ambiguous and rarely stand alone in court without another more easily proven charge.

Upvote to you too anyway, although I’m still guilty of using downvote as a disagree button.

I didn’t bother to check who it is because I’m not petty enough, but there’s a guy on my instance who downvotes everything. I think some people are using downvotes to “hide read posts” as voting counts as reading a post.

“Discussions became binary”. And yet you subscribe to the binary of “hateful vs. non-hateful opinion” as if it’s clearly identifiable.

Why do you have to use NGINX? Caddy does the proxying to the Lemmy containers for you. That docker-compose.yml file is my entire deployment, there is no hidden NGINX container or config file that needs to be added. Just remove your broken Lemmy deployment with docker compose down and delete the containers, then docker compose up my docker-compose.yml (after you edit the postgres variables) with config.hjson in the same folder.

Oh shit, I forgot that your Caddy would be running on a bridge network by default because mine is on the host network where all ports are already exposed to it! (It’s generally a bad idea to use the host network, so don’t do this if you’re only using Caddy with containers on the same network) I edited the Gist to expose 80 and 443 for HTTP/S on that container, the updated file uses the same Github link. Really sorry about that!

Ugh, that one is a problem with indentation because pasting the config into a Lemmy comment destroys the formatting. I uploaded it on Github to preserve the correct indentation.

Yeah, the config file on the documentation sucks. I had to poke through several discussions on /c/selfhosting to find a config that wasn’t the extremely minimal one linked in the documentation. Your config.hjson is fine from what I can tell, although I’m not sure why you censored the hostname there as it’s supposed to be lemmy.emphisia.nl and not anything confidential.

Honestly, I don’t have enough understanding of NGINX to debug its config, so I’ll just share my docker-compose.yml for leddit.danmark.party which worked correctly and federated out of the box, with a few adjustments to match your deployment. Note that you’ll have to tear down your existing deployment if you want to use this docker-compose.yml because they use the same ports.

version: "3.9"
x-logging:
  &default-logging
  options:
    max-size: '10m'
  driver: json-file

services:
  caddy:
    image: caddy:2
    volumes:
      - ./volumes/caddy:/data
      - ./volumes/caddy:/config
    # See Caddy's documentation for customizing this line
    # https://caddyserver.com/docs/quick-starts/reverse-proxy
    command:
      - /bin/sh
      - -c
      - |
        cat <<EOF > /etc/caddy/Caddyfile && caddy run --config /etc/caddy/Caddyfile
        
        {
          debug
        }
        
        (common) {
        	encode gzip
        	header {
        		-Server
        		Strict-Transport-Security "max-age=31536000; include-subdomains;"
        		X-XSS-Protection "1; mode=block"
        		X-Frame-Options "DENY"
        		X-Content-Type-Options nosniff
        		Referrer-Policy no-referrer-when-downgrade
        		X-Robots-Tag "none"
        	}
        }       
        
        # Lemmy instance
        lemmy.emphisia.nl {
          log
          import common
          reverse_proxy http://lemmy-ui:1234 # lemmy-ui
          
          @lemmy {
        		path /api/*
        		path /pictrs/*
        		path /feeds/*
        		path /nodeinfo/*
        		path /.well-known/*
        	}
         
         	@lemmy-hdr {
        		header Accept application/*
        	}
          
          handle @lemmy {
            reverse_proxy http://lemmy:8085 # lemmy
          }
          
          handle @lemmy-hdr {
            reverse_proxy http://lemmy:8085
          }
          
          @lemmy-post {
        		method POST
        	}
        
        	handle @lemmy-post {
        		reverse_proxy http://lemmy:8085
        	}
        }
        EOF
    lemmy:
      image: dessalines/lemmy:0.18.1-rc.9
      ports:
        - 8085:8536
      volumes:
        - ./lemmy.hjson:/config/config.hjson
      depends_on:
        - postgres
        - pictrs
      restart: always
      logging: *default-logging
      
    lemmy-ui:
      image: dessalines/lemmy-ui:0.18.1-rc.9
      ports:
       - 1234:1234
      environment:
        - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8085
        - LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236
      depends_on:
        - lemmy
      volumes:
        - ./volumes/lemmy-ui/extra_themes:/app/extra_themes
      restart: always
      logging: *default-logging
   
    postgres:
      image: postgres:15-alpine
      ports:
        - 5432:5432
      environment:
        - POSTGRES_USER=MyPostgresUser
        - POSTGRES_DB=MyPostgresDb
        - POSTGRES_PASSWORD=MyPostgresPassword
      volumes:
        - ./volumes/postgres:/var/lib/postgresql/data
      restart: always
      logging: *default-logging
      
    pictrs:
      image: asonix/pictrs:0.4.0-rc.7
      user: 991:991
      hostname: pictrs
      environment:
        - PICTRS__MEDIA__VIDEO_CODEC=vp9
        - PICTRS__MEDIA__GIF__MAX_WIDTH=256
        - PICTRS__MEDIA__GIF__MAX_HEIGHT=256
        - PICTRS__MEDIA__GIF__MAX_AREA=65536
        - PICTRS__MEDIA__GIF__MAX_FRAME_COUNT=400
      volumes:
        - ./volumes/pictrs:/mnt
      restart: always
      logging: *default-logging
	  
    postfix:
      image: mwader/postfix-relay
      environment:
       - POSTFIX_myhostname=lemmy.emphisia.nl
      restart: "always"
      logging: *default-logging

I don’t use NGINX as my proxy server, but it’s a bit strange that you would need two configs for this while mine runs perfectly with one config and two open ports (:8536 for Lemmy-BE and :1234 for Lemmy-UI). And why are you using different versions of Lemmy-BE (18.1-rc9) and Lemmy-UI (18.1-rc4)?

If you are using the default docker-compose.yml on the Lemmy repo, that part of the NGINX config uses https:// + the name of the Docker containers. And you always give NGINX the external port (the number on the right side of the colon defined in ports:, like 1234 in 1234:5678). The port on the left is only known to the container the port is defined for.

If it’s still broken after you correct the NGINX config, what are your docker-compose.yml and config.hjson like? There’s several versions of them floating around and you might have combined incompatible versions with each other.

“Suddenly”? This has been happening for a long time. If you click on outbound links from built-in Windows apps, they used to always open in Edge unless you used a tool named EdgeDeflector to redirect them to your preferred browser. In 2021, they killed EdgeDeflector by making it impossible to redirect links with the microsoft-edge:// protocol baked in, even if you go deep into the registry settings to change this. They will eventually do this to Outlook and Teams too and get away with it, just like they got away with restricting EdgeDeflector.

https://leddit.danmark.party, because it’s running a bot named Leddit that pulls content from Reddit. And, uh, Denmark Party, because I love Denmark and I thought it would be really funny to own a domain named this. I also wanted to split my serious and silly projects into different domains, so I bought this extra domain and use it for all of my silly projects now.

(Not posting directly from that instance so I can leave the bot in peace, but federation definitely works because posts from it are getting through to other instances)

On 0.18.0, there is only the “Only moderators can post” checkbox which stops regular users from creating new posts, but it doesn’t stop them from commenting on posts. I’m looking for a way to prevent both (instead of deleting comments after they have been posted).

I don’t use Reddit for the interaction, average Redditors are annoying to interact with. Reddit’s value to me is the amount of information it contains. It’s supposed to be like copy pasting a book that has DRM, so you can make use of the content without worrying that the book’s copyright holder will use it to screw you over eventually.

Nope, sorry. Just a memory of a Reddit thread with very out-of-context comments. Ironically, while trying to search for documentation of the thread, DuckDuckGo returned a lot of research papers about the analysis of bot content on Reddit starting from 2015, so there’s still proof that botting on Reddit goes way back.

I’m working on that one! Fork of lemmit.online, so it doesn’t need API access.

Don’t worry about it spamming instances. This bot posts so much that it will be automatically blocked from any instance that uses the default Lemmy rate limits, so all bot deployments will have to run on an instance that is specifically for them.

Source code for the bot will be released on July 1st if Reddit doesn’t introduce a breaking change on that day and if I don’t receive a good argument as to why this bot will destroy the Fediverse.

Reddit has been that way for a long time, after it lost the reputation of “niche forum for tech-obsessed weirdos” and became the internet’s general hub for discussion. The default subreddits are severely astroturfed by marketing and political campaigning groups, and Reddit turns a blind eye to it as long as it’s a paid partnership. There was one obvious case where bots in /r/politics accidentally targeted an AutoModerator thread instead of a candidate’s promotion thread and filled it with praise for that candidate.

It’s great that they’re going back to traditional, self-hosted forums instead of corporate social media for support and discussions, but damn, I don’t miss having to manage hundreds of accounts with unique logins for each forum. I understand that they want more control over forum moderation and the Fediverse’s “anyone can post there” system makes it troublesome. It would be great if there was more widespread adoption of decentralized, “one login to access everything” systems.

Chrome lost me completely when they announced the plan to change the browser’s framework so that it would no longer be possible to block ads. Google is currently delaying the release but it will come someday.