Her sidder jeg, med mit hjerte brudt // Prøvede at skide, men slog kun en prut
Wow, I didn’t know that LineageOS has such long-term support! The original Pixel is still supported?! I’m using GrapheneOS and they offer support for the same lifetime as the official Google updates, so I assumed that the rest of the alternative OSes are the same.
Federated actions are never truly private, including votes. While it’s inevitable that some people will abuse the vote viewing function to harass people who downvoted them, public votes are useful to identify bot swarms manipulating discussions.
I considered buying the P3 or P4 because they’re said to have the best cameras and battery performance, but the end of security updates after 2022 and 2023 respectively turned me off and I got a P6A instead. What are you going to do with your P4A after the support for it ends this year?
And I’m sure it would also be more convenient to have it all under one roof, just like everything about Germany is under feddit.de, and people from elsewhere can still visit if they like.
I’m trying to advertise my country’s instance, feddit.nu (Sweden). feddit.de got a headstart with Germans by having been created before the Reddit migration and providing the first federated community discovery tool.
Instances that were created after the migration started on the other hand? It’s frustrating with Redditor behavior, because they expect the Lemmy community to share the same name as the Reddit community (/r/Sweden) and only subscribe to communities that use the same name.
If you don’t want your lemmy.world feed to be flooded with languages you can’t understand, please make sure to annoy their users about it as much as possible, in English, that they should move to the country-specific instances instead of centralizing on lemmy.world. It’s healthier for the Fediverse in general with everyone on many instances, in the long run.
It’s Estonian (.ee is the country code for Estonia) but it’s also a cool domain hack and the owner opened it to everyone.
Older than 30 nope, tech enthusiast yes, Linux user sort of, because my self-hosting servers run Linux but my personal daily driver is Windows. Windows native art programs have a lot of responsiveness problems and other random issues when running on Linux, and it’s annoying to have to boot up a separate OS to use specific programs.
Taking the extremely tech-unsavvy fanartist community as a reference, it’s not that federation and choosing a server is that difficult, that’s just a lame excuse. Their usual social media platforms do UI redesigns, A/B testing and introduce weird limitations all the time. They just learn to cope with it.
People who don’t care about tech don’t think about the websites they use at all. In their minds, websites are just omnipresent things that exist naturally, like the sun. They only care about whether the website is able to connect them to their friends and showcase their posts to other people. They will only pay attention to the website if it introduces a change that affects their daily usage of it negatively, just like how people don’t consciously think about the sun unless it inconveniences them.
That’s why I suggested Revanced with “disable recommendations” patches. It’s still Youtube and there is no new platform to learn.
I think it’s sad how so many of the comments are sharing strategies about how to game the Youtube algorithm, instead of suggesting ways to avoid interacting with the algorithm at all, and learning to curate content on your own.
The algorithm doesn’t actually care that it’s promoting right-wing or crazy conspiracy content, it promotes whatever that keeps people’s eyeballs on Youtube. The fact is that this will always be the most enraging content. Using “not interested” and “block this channel” buttons doesn’t make the algorithm stop trying to advertise this content, you’re teaching it to improve its strategy to manipulate you!
The long-term strategy is to get people away from engagement algorithms. Introduce OP’s mother to a patched Youtube client that blocks ads and algorithmic feeds (Revanced has this). “Youtube with no ads!” is an easy way to convince non-technical people. Help her subscribe to safe channels and monitor what she watches.
To where, if the big instance that everyone centralized on goes to shit? The internet itself is decentralized. Anyone can run a website, but no matter how enshittified corporate websites become, people are “somehow” still stuck on Google, Meta, Microsoft etc. websites and services.
I like anything that pulls users away from big instances and onto smaller ones. Guys, it’s not a DECENTRALIZED system if you’re all centralizing on one massive instance.
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.
Yes, it started from this terminology change at Twitter in 2020. They’re the reason that version control systems call the primary branch ‘main’ instead of ‘master’ by default, because ‘master’ comes from the master/slave terminology that is used in electronics hardware design.
There’s a comment here saying that master/slave in hardware design is being replaced by primary/secondary because of the software trend, which I think is stupid. Master/slave works much better in that context because the master device controls the slave device. Primary/secondary implies that the slave device is a fallback of the master device.
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).
It will continue to work if you’re the only user on your Teddit instance. Teddit (and Libreddit, and any of the Reddit alternative frontends) use the Reddit API un-authenticated and after July 1st, they will be rate-limited to 10 requests per minute. The limit is enough for the activity of one logged-out user but it will break the proxy instances that allow many users to combine their traffic under one IP.
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.
Is this like when they made the kilogram some function of the speed of light instead of the weight of a metal ball in a French museum?