— Update ———

In your account preferences, "Show Read" is enabled by default. If you disable it, then any time a post is marked "read", you will no longer see it on your feed. The app I use is currently set to mark posts I've scrolled past as "read." I'm not sure how the Lemmy WebUI does it.

This is a great tool to make sure you don't repeatedly see the same read posts on your main feeds, but apparently it also applies when viewing a community directly.

— Original post below ———

I was able to see videos at https://lemmy.world/c/crazyfuckingvideos until just a few days ago. Now it says no new posts for a year and I can't see any new posts.

I've never posted or commented in that community. There are no modlog actions against me regarding that community or instance. I haven't blocked the community or instance. My instance hasn't blocked lemmy.world. I don't think my instance has blocked the community specifically because my alt on the same instance accesses it fine. This problem exists both within third party apps and the normal Lemmy WebUI.

Does anyone have any idea why I am not able to see the content from https://lemmy.world/c/crazyfuckingvideos while logged in?

Thanks.

I've setup Lemmy on a VPS with LetsEncrypt. When navigating to my domain, Lemmy just says "There was an error on the server. Try refreshing your browser. If that doesn't work, come back at a later time. If the problem persists, you can seek help in the Lemmy support community or Lemmy Matrix room."

I've checked both the Lemmy API and WUI instances, but no errors are reported: lemmy@ubuntu-s-1vcpu-2gb-sfo3-01:~$ docker compose logs postgres | postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization postgres | postgres | 2025-02-17 18:21:24.644 UTC [1] LOG: starting PostgreSQL 17.3 (Debian 17.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit postgres | 2025-02-17 18:21:24.646 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 postgres | 2025-02-17 18:21:24.647 UTC [1] LOG: listening on IPv6 address "::", port 5432 postgres | 2025-02-17 18:21:24.652 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" postgres | 2025-02-17 18:21:24.685 UTC [27] LOG: database system was shut down at 2025-02-17 18:21:15 UTC postgres | 2025-02-17 18:21:24.729 UTC [1] LOG: database system is ready to accept connections lemmy-ui-1 | Lemmy-ui v0.19.9 started listening on http://0.0.0.0:1234/ lemmy-ui-1 | 31 translation imports verified. lemmy-ui-1 | date-fns "zh" failed: unexpected format lemmy-ui-1 | 1 out of 94 date-fns imports failed. lemmy-ui-1 | 4 highlight.js imports verified. (Only testing 4 samples.) nginx-certs-1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration nginx-certs-1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ nginx-certs-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh nginx-certs-1 | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf nginx-certs-1 | 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf nginx-certs-1 | /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh nginx-certs-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh nginx-certs-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh nginx-certs-1 | /docker-entrypoint.sh: Configuration complete; ready for start up nginx-certs-1 | 106.75.133.150 - - [17/Feb/2025:18:21:43 +0000] "GET / HTTP/1.1" 301 169 "http://my.server.ip.addr/" "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36" nginx-certs-1 | 106.75.133.150 - - [17/Feb/2025:18:21:45 +0000] "GET /favicon.ico HTTP/1.1" 301 169 "http://my.server.ip.addr/" "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36" proxy-1 | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration proxy-1 | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ proxy-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh proxy-1 | 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf proxy-1 | 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf proxy-1 | /docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh proxy-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh proxy-1 | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh proxy-1 | /docker-entrypoint.sh: Configuration complete; ready for start up proxy-1 | 75.154.243.157 - - [17/Feb/2025:18:21:47 +0000] "GET / HTTP/2.0" 500 5284 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" proxy-1 | 75.154.243.157 - - [17/Feb/2025:18:21:47 +0000] "GET /manifest.webmanifest HTTP/2.0" 500 21 "https://mydomain.xyz/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" proxy-1 | 75.154.243.157 - - [17/Feb/2025:18:21:48 +0000] "GET / HTTP/2.0" 500 5284 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" proxy-1 | 75.154.243.157 - - [17/Feb/2025:18:21:50 +0000] "GET /service-worker.js HTTP/2.0" 304 0 "https://mydomain.xyz/service-worker.js" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" certbot-1 | Saving debug log to /var/log/letsencrypt/letsencrypt.log certbot-1 | Certbot doesn't know how to automatically configure the web server on this system. However, it can still get a certificate for you. Please run "certbot certonly" to do so. You'll need to manually configure your web server to use the resulting certificate. pictrs-1 | 2025-02-17T18:21:23.900781Z INFO pict_rs: Starting pict-rs on 0.0.0.0:8080 pictrs-1 | 2025-02-17T18:21:23.901363Z INFO actix_server::builder: starting 1 workers pictrs-1 | 2025-02-17T18:21:23.901410Z INFO actix_server::server: Tokio runtime found; starting in existing Tokio runtime lemmy-1 | Lemmy v0.19.9 lemmy-1 | 2025-02-17T18:21:25.386757Z INFO lemmy_db_schema::schema_setup: Running Database migrations (This may take a long time)... lemmy-1 | 2025-02-17T18:21:25.408878Z INFO lemmy_db_schema::schema_setup: Database migrations complete. lemmy-1 | 2025-02-17T18:21:25.493688Z INFO lemmy_server::code_migrations: Running user_updates_2020_04_02 lemmy-1 | 2025-02-17T18:21:25.515048Z INFO lemmy_server::code_migrations: 0 person rows updated. lemmy-1 | 2025-02-17T18:21:25.516901Z INFO lemmy_server::code_migrations: Running community_updates_2020_04_02 lemmy-1 | 2025-02-17T18:21:25.540687Z INFO lemmy_server::code_migrations: 0 community rows updated. lemmy-1 | 2025-02-17T18:21:25.541173Z INFO lemmy_server::code_migrations: Running post_updates_2020_04_03 lemmy-1 | 2025-02-17T18:21:25.551391Z INFO lemmy_server::code_migrations: 0 post rows updated. lemmy-1 | 2025-02-17T18:21:25.553517Z INFO lemmy_server::code_migrations: Running comment_updates_2020_04_03 lemmy-1 | 2025-02-17T18:21:25.571059Z INFO lemmy_server::code_migrations: 0 comment rows updated. lemmy-1 | 2025-02-17T18:21:25.572187Z INFO lemmy_server::code_migrations: Running private_message_updates_2020_05_05 lemmy-1 | 2025-02-17T18:21:25.576403Z INFO lemmy_server::code_migrations: 0 private message rows updated. lemmy-1 | 2025-02-17T18:21:25.578895Z INFO lemmy_server::code_migrations: Running post_thumbnail_url_updates_2020_07_27 lemmy-1 | 2025-02-17T18:21:25.681807Z INFO lemmy_server::code_migrations: 0 Post thumbnail_url rows updated. lemmy-1 | 2025-02-17T18:21:25.684992Z INFO lemmy_server::code_migrations: Running apub_columns_2021_02_02 lemmy-1 | 2025-02-17T18:21:25.693262Z INFO lemmy_server::code_migrations: Running instance_actor_2021_09_29 lemmy-1 | 2025-02-17T18:21:25.734984Z INFO lemmy_server::code_migrations: Running regenerate_public_keys_2022_07_05 lemmy-1 | 2025-02-17T18:21:25.743673Z INFO lemmy_server::code_migrations: Running initialize_local_site_2022_10_10 lemmy-1 | Federation enabled, host is mydomain.xyz lemmy-1 | Starting HTTP server at 0.0.0.0:8536 lemmy-1 | 2025-02-17T18:21:26.062209Z INFO lemmy_server::scheduled_tasks: Updating active site and community aggregates ... lemmy-1 | 2025-02-17T18:21:26.233668Z INFO lemmy_server::scheduled_tasks: Done. lemmy-1 | 2025-02-17T18:21:26.233702Z INFO lemmy_server::scheduled_tasks: Updating hot ranks for all history... lemmy-1 | 2025-02-17T18:21:26.263454Z INFO lemmy_server::scheduled_tasks: Finished process_hot_ranks_in_batches execution for post_aggregates (processed 0 rows) lemmy-1 | 2025-02-17T18:21:26.281667Z INFO lemmy_server::scheduled_tasks: Finished process_hot_ranks_in_batches execution for comment (processed 0 rows) lemmy-1 | 2025-02-17T18:21:26.289482Z INFO lemmy_server::scheduled_tasks: Finished process_hot_ranks_in_batches execution for community (processed 0 rows) lemmy-1 | 2025-02-17T18:21:26.289521Z INFO lemmy_server::scheduled_tasks: Finished hot ranks update! lemmy-1 | 2025-02-17T18:21:26.289527Z INFO lemmy_server::scheduled_tasks: Updating banned column if it expires ... lemmy-1 | 2025-02-17T18:21:26.310614Z INFO lemmy_server::scheduled_tasks: Clearing old activities... lemmy-1 | 2025-02-17T18:21:26.329883Z INFO lemmy_server::scheduled_tasks: Done. lemmy-1 | 2025-02-17T18:21:26.329909Z INFO lemmy_server::scheduled_tasks: Overwriting deleted posts... lemmy-1 | 2025-02-17T18:21:26.345925Z INFO lemmy_server::scheduled_tasks: Done. lemmy-1 | 2025-02-17T18:21:26.345960Z INFO lemmy_server::scheduled_tasks: Overwriting deleted comments... lemmy-1 | 2025-02-17T18:21:26.388678Z INFO lemmy_server::scheduled_tasks: Done. lemmy-1 | 2025-02-17T18:21:26.408661Z INFO lemmy_server::scheduled_tasks: Done.

Due to no errors showing up in logs, I'm unsure where to begin troubleshooting.

Here's my Nginx config: ``` events {

}

http {

limit_req_zone $binary_remote_addr zone=mydomain.xyz_ratelimit:10m rate=1r/s;

upstream lemmy { server "lemmy:8536"; } upstream lemmy-ui { server "lemmy-ui:1234"; }

server { listen 80; listen [::]:80; server_name mydomain.xyz; location /.well-known/acme-challenge/ { root /var/www/certbot; } location / { return 301 https://$host$request_uri; } }

server { http2 on; listen 443 ssl; listen [::]:443 ssl; server_name mydomain.xyz;

ssl_certificate /etc/letsencrypt/live/mydomain.xyz/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mydomain.xyz/privkey.pem;

ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256'; ssl_session_timeout 10m; ssl_session_cache shared:SSL:10m; ssl_session_tickets on; ssl_stapling on; ssl_stapling_verify on;

server_tokens off;

gzip on; gzip_types text/css application/javascript image/svg+xml; gzip_vary on;

add_header Strict-Transport-Security "max-age=63072000";

add_header Referrer-Policy "same-origin"; add_header X-Content-Type-Options "nosniff"; add_header X-Frame-Options "DENY"; add_header X-XSS-Protection "1; mode=block";

client_max_body_size 20M;

location / { set $proxpass "http://lemmy-ui/";

if ($http_accept = "application/activity+json") { set $proxpass "http://lemmy/"; } if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") { set $proxpass "http://lemmy/"; } if ($request_method = POST) { set $proxpass "http://lemmy/"; } proxy_pass $proxpass;

rewrite ^(.+)/+$ $1 permanent;

# Send actual client IP upstream proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }

location ~ ^/(api|feeds|nodeinfo|.well-known) { proxy_pass "http://lemmy/"; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";

limit_req zone=mydomain.xyz_ratelimit burst=30 nodelay;

proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }

location ~ ^/(pictrs) { # allow browser cache, images never update, we can apply long term cache expires 120d; add_header Pragma "public"; add_header Cache-Control "public";

proxy_pass "http://lemmy/"; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";

limit_req zone=mydomain.xyz_ratelimit burst=30 nodelay;

proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; }

location ~ /pictshare/(.*)$ { return 301 /pictrs/image/$1; } }

map $remote_addr $remote_addr_anon { ~(?P<ip>\d+\.\d+\.\d+)\. $ip.0; ~(?P<ip>[^:]+:[:]+): $ip::; 127.0.0.1 $remote_addr; ::1 $remote_addr; default 0.0.0.0; } access_log /var/log/nginx/access.log combined;

} ```

Docker-compose: ``` networks: lemmyexternalproxy: lemmyinternal: driver: bridge internal: true

services: proxy: image: nginx:1.27.4-alpine networks: - lemmyinternal - lemmyexternalproxy ports: - 443:443 volumes: - ./volumes/nginx/nginx.conf:/etc/nginx/nginx.conf:ro - ./volumes/certbot:/var/www/certbot:ro - ./volumes/letsencrypt:/etc/letsencrypt:ro restart: unless-stopped depends_on: - pictrs - lemmy-ui

nginx-certs: image: nginx:1.27.4-alpine ports: - 80:80 volumes: - ./volumes/nginx_certs/nginx.conf:/etc/nginx/nginx.conf:ro - ./volumes/certbot:/var/www/certbot:ro - ./volumes/letsencrypt:/etc/letsencrypt:ro restart: always

lemmy: image: dessalines/lemmy:0.19.9 hostname: lemmy networks: - lemmyinternal - lemmyexternalproxy restart: unless-stopped environment: - RUST_LOG=verbose,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info volumes: - ./volumes/lemmy-api/lemmy.hjson:/config/config.hjson depends_on: - pictrs - postgres

lemmy-ui: image: dessalines/lemmy-ui:0.19.9 networks: - lemmyinternal environment: - LEMMY_INTERNAL_HOST=lemmy:8536 - LEMMY_EXTERNAL_HOST=mydomain.xyz - LEMMY_HTTPS=true depends_on: - lemmy restart: unless-stopped

postgres: image: postgres:17.3 networks: - lemmyinternal container_name: postgres restart: unless-stopped environment: POSTGRES_USER: lemmy POSTGRES_PASSWORD: XXXXXXXXXXX POSTGRES_DB: lemmy volumes: - ./volumes/postgres:/var/lib/postgresql/data

pictrs: image: asonix/pictrs:0.5.16 hostname: pictrs networks: - lemmyinternal environment: - PICTRS__API_KEY=j9Dj3FxLxWL8mxMF user: 0:0 volumes: - ./volumes/pictrs:/mnt restart: unless-stopped

certbot: image: certbot/certbot:v3.2.0 volumes: - ./volumes/certbot:/var/www/certbot/:rw - ./volumes/letsencrypt:/etc/letsencrypt/:rw ```

And finally, Lemmy's config: ``` { setup: { admin_username: "lemmy" admin_password: "XXXXXXXXXXXXXXXX" site_name: "MYDOMAIN" }

hostname: "mydomain.xyz" bind: "0.0.0.0" port: 8536 tls_enabled: true

pictrs_url: "http://pictrs:8080/"

database: { database: "lemmy" user: "lemmy" password: "XXXXXXXXXXXXXXXXXXXX" host: "postgres" port: 5432 pool_size: 5 } } ```

Edit: the issue was cloudflare proxy. If you're using cloudflare for dns, turn off proxying if you're using lets encrypt.

I must be doing something wrong, because when i run the playbook I get an unconfigured nginx page at the ip of my server.

The instruction docs for ansible states:

Do not edit anything inside the {{ }} braces.

https://github.com/LemmyNet/lemmy-ansible/blob/main/examples/config.hjson

however that config file points to:

https://join-lemmy.org/docs/administration/configuration.html

Solution

The Lemmy server appears to have a database limit of 255 characters ^[2]; however, individual instances appear to put their own limits on username length though the frontend ^[3] and/or the API ^[4.1][4.2].

Original Post

If you know, please also provide relevant documentation.

UPDATE (2025-02-02T06:06Z): I did some brute-force testing, and, at least for sh.itjust.works, it seems that the maximum username length is 50, and the maximum password length is 60 ^[1].

---

By default Lemmy seems to be mirroring every link's preview image. Even when that link was originally posted on an external Lemmy instance. That can put quite a strain on small servers. Is there a way to disable this? Ideally I would have pict-rs just be used to host the images my users upload and nothing else.

Solved:

Add

pictrs: { image_mode: "None" }

to lemmy.hjson.

Solution

As was pointed out by @[email protected] ^[1], this feature was added in this pull request. It appears that the custom thumbnail field is only relevant for posts that share a URL: The "Thumbnail URL" field is used to specify a custom thumbnail to be used in place of what would've been automatically generated by the provided URL ^[2].

Original Post

I thought it would be for adding a custom thumbnail that appears for the post in the feed, but then that seems to be a duplicate of adding an image. At any rate, I tried adding an image link to it, and no image showed up for the post. So I'm not entirely sure what it's actually for.

EDIT (2024-11-30T22:22): Perhaps it's for the pre-expanded thumbnail for a post if it has an image? Does that mean that it only works if you have an image specified? Can it be used to override the thumbnail that's generated from a shared article? Does it work for a text post?

I was trying to edit my community, and I accidentally pressed the delete button. Is there any way to undo this?

New Lemmy admin here. I found the [Theming Guide] in the Lemmy docs, but it jumps directly to the 'After a theme is added' section without explaining how to add or create themes. I've searched for examples but couldn't find any configuration that includes these details.

I found [hanubeki-lemmy-themes], which actually contains some good themes. However, when I copied the 5 folder to my extra_theme folder, nothing happened. Can someone guide me on how to add these themes to my instance?

Update: You should put all your css file in the extra_themes folder, each .css is a theme. For [hanubeki-lemmy-themes] I put all the dist and src files in extra_themes and it works. I already done this before, but my browser was [caching lemmy-ui static files for 24 hours], so when I delete the cache it just works.

[Theming Guide]: https://join-lemmy.org/docs/administration/theming.html [hanubeki-lemmy-themes]: https://github.com/hanubeki/hanubeki-lemmy-themes [cashing lemmy-ui static files for 24 hours]: https://github.com/LemmyNet/lemmy-ui/blob/2b726b51b5a0a2751bc0e955c39b3179284a1695/src/server/middleware.ts#L48-L51

> Thank you Sami, it was a cash problem, I updated the post with more details

Sorry if this is the wrong community, not sure where else to post the question, and I'd rather avoid creating an issue over on Github.

Is there a way to check if a federated user is an administrator via the API? .get_person_details() will have the admin field set to false for all other than local admins and .get_community() only reveals the list of moderators.

I know I could scrape the admin list from the main page html, but scraping html is prone to errors if an instance uses an alternative frontend or the frontend is updated. Getting the data via the API should be a more stable solution.

Based on #3703 it seems like a decent chance that this information isn't currently exposed to federated instances though?

EDIT: It seems to have been fixed thanks to @[email protected]. Running analyze verbose; in postgres.

After updating to 0.19.5 from 0.19.3 my postgres is often using up 500%+ of CPU according to docker stats and often going to 100% CPU on most cores according to htop. Also noticed in the uptime monitor: !

htop shows one of the 5 postgres processes constantly on UPDATE. I think this might be part of the problem.

I'm not comfortable with postgres and am honestly completely in the dark how or where to mitigate or even pinpoint this issue.

Any help would be appreciated.

EDIT: After discussing this on Matrix, I believe the answer is in the mod logs. The author of the post in question was issued a temporary ban in another community on lemmy.ml, which I suspect is affecting the display of this user’s content across all of lemmy.ml even though the post in question is in a different community from the one that issued the ban (which is kinda screwy tbh).

Description of the problem

The last several months, I've been trying to build up the community over at [email protected]. It's going mostly well, but one thing that has me scratching my head lately is that when I'm browsing from lemmy.ml (i.e. <https://lemmy.ml/c/[email protected]>), which is 99% of the time, I can't see the most recent post. Oddly enough, the author is also from lemmy.ml, and I have previously interacted w/ the same user in the comments of older posts, so I know it's not a user-specific issue. I've double checked my profile settings and haven't blocked the community, instance, or user. This issue seems specific to lemmy.ml because I can see it when I browse to the community from other instances.

Any ideas why this could be happening and what I can do to resolve it? Thanks.

Steps to reproduce the issue

• Visit <https://lemmy.world/c/caps> and sort by Active or New. You'll see a post called "Thanks for the chats guys" with one comment.
• Visit <https://lemm.ee/c/[email protected]> - again, the post is visible.
• Now head over to <https://lemmy.ml/c/[email protected]> and look at the feed.

Actual result

The post is not there.

Expected result

The post should show up in the feed.

Answer

As mentioned by @[email protected], if only a username is shown, then that is the display name that the user has set. If there is a username and an instance, then that user has not set a display name.

---

Original Post

There appears to be no rhyme, nor reason to the inclusion of the instance in the poster's username. For clarity, I am referring to the format of @username@instance. I would have thought that the usernames that don't include the instance are from users that originate from one's local instance, but that appears not to be the case. The second idea was that maybe it was something to do with length, in that a longer username wouldn't include the instance, but that doesn't seem to be the case either.

Go to Settings > Scroll Down > Tick Show Read Posts > SAVE

Solution: !

-----------------------

!

!

---------------------

Without being logged in:

!

PS: I also have an account on sh.itjust.works and this shit just works over there.

I run a Lemmy instance at lemmy.sedimentarymountains.com. It has been working for some time. 6 days ago it stopped getting updates from communities it was federated with. If I view all posts by active there is nothing newer than 6 days old. I checked disk space on the server, there is plenty. I don’t appear to be running out of any other resource. I redeployed the ansible playbook which didn’t do anything other then reload some services. I rebooted the server with no change in behavior. I am running 0.18.4 on Ubuntu 22.04.2 LTS.

I did notice that when I searched for [email protected] it started to pull fresh posts, but only from this community. I tried manually searching for a few other communities and I got a one time update of fresh content from them. I’m not sure what has changed. Is there a log I can review for federation issues?

I originally tried to post this from my instance but it didn't ever show up here. I've created an account on lemmy.ml to post this.

[solved] Apparently, I had to type in [email protected] instead of just piracy and it does work. Now, I guess, that's one disadvantage of lemmy? !

---------------

[ORIGINAL POST]

!Lemmy.ml

!sh.itjust.works

sh.itjust.works just doesn't show c/piracy

Hi there,

I am in the process of migrating instances. I have been trying to add a bio and avatar to my profile, but when I press 'Save' at the bottom of my profile settings, I don't see any changes on my profile page.

I have tried this on both instances' profiles, and on desktop and mobile. I don't know if this is an error or perhaps I'm overlooking a necessary step.

Has anybody else encountered this? Any help would be appreciated.

Edit (SOLVED): Changes seemed to push through when I removed the link to my old profile from my bio. Either profiles don't support links, or I hit a character limit. Still not quite sure.

I shared a post about my instance.

Then I hit the cross-post button, chose the community, language and then submitted the form. Although new post created, there is no "cross-posted to" area on both original or target post.

For example here, you can see which communities the post cross-posted to. What am I doing wrong?

Update: looks like both posts should have same URL for crosspost to work. https://github.com/LemmyNet/lemmy/issues/3827

Hi.

i'm using ansible for installation and upgrading. My setup has an external nginx running which does the SSL part, so i want to remove the SSL and certbot parts of the /templates/nginx.conf file.

(i'm not sure if i have to edit the other nginx_internal.conf file) But with the below settings i get 'Bad gateway'.

Hoping someone can point me in the right direction. Thanks

``` limit_req_zone $binary_remote_addr zone={{domain}}_ratelimit:10m rate=1r/s;

changelog

2023-06-27 Merge remote #5246 and remove certbot and ssl

server { listen 80; listen [::]:80; server_name {{domain}};

location / { proxy_pass http://0.0.0.0:{{lemmy_port}}; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }

access_log /var/log/nginx/access.log combined; ```

As in, how do you mention someone in a comment, so they get a notification that they've been mentioned somewhere? Is it even possible yet? I've tried writing @ following by the username (not screen name, though I tried that too) but it didn't work. Problem is, I've seen people do this in comments before, just can't figure out how.

Edit: Solved.