Lemmy

There are entire communities full of bad faith actors, spammers, and echo-chamber-enforcing mods. We as individual users downvote them with 0 effect. We can block and hide users/communities/instances but that does nothing for the community as a whole. Ignoring them and "not feeding the trolls" is simply not making them go away. Just try blocking UniversalMonk, we all know they have dozens of accounts with hundreds of downvotes across every comment and post and yet they keep going. Or any of the conservative communities who's total post score is in the red.

I've blocked so much garbage that my feed doesn't change very often. I barely check Lemmy once a day now. This does not make for a healthy online community.

Many of us came from reddit where there are many valid complaints for how they run things but one thing I'd like to see return is downvotes slowing down how often a user can post, comment, and vote in a community. If a single user's score drops too low within an instance or community, that user should be rate limited or maybe even auto-banned or maybe an entire third option I can't think of. But right now it's not even a slap on the wrist.

i just want to create a community to dump my gaming clips without using too much of lemmy.ml's capacity lol.. Any suggestions?

One thing that I miss from Tildes is the way I can block links/websites from being in my feed.

Is there is something similar at Lemmy?

Not sure this is the appropriate community to ask this, but anyway, here it is.

EDIT: Kind of self-serving on my part, I guess, since I'm new to Odoo and liking it, but not getting much support from the documentation or the forum . . . well, ok then!

If someone beats me to the bunch and creates the community before I do, no worries . . . a little apprehensive because I've never done this before, so here goes . . .

In the screenshot you can see that there is currently one rising community overloading my post feed. I assume this is happening to many users. I understand that I can block the community but that's not really what I want. I think that this problem could be solved by introducing a mechanism to dynamically limit the number of such posts based on user preferences. For example I could set this community to appear less often and an algorithm could apply this preference to my feed order. I know that the proverbial algorithms used by major social networks are frowned upon. That happens for a good reason - they are opaque, proprietary and often show signs of bad intention. They are used for political and social influence, to silence opposing voices and a whole array of other nefarious goals like playing of people's fear, outrage, etc. The thing I'm suggesting would have to be transparent by design and fully optional. That's a social media "algorithm" I'd like to use. I'd like to hear what other people think about this idea.

Pictures should be expanded by default on the post page because they provide important context for the post, so anyone who comments should have seen it first anyway.

It is already possible to limit search to a single community, but a search bar above the post list would be faster and more convenient.

This concept screenshot shows how it could be done.

Currently, URLs to posts have this format:

lemmy.ml/post/[number]

I suggest changing it to this so people can see the community immediately in shared URLs:

lemmy.ml/c/[community-name]/[post-number]

From mastodon to follow an account or a community on lemmy you use the @name@server format and there is no difference between a community name and a user-name

so i was wondering if anyone tried and checked what happened

cross-posted from: https://gregtech.eu/post/5084911

Essentially, I'd like to have pictrs delete all of the images that aren't uploaded by my users, because my storage usage was going through the roof, so I just disabled the proxying of images. Here is my config:

x-logging: &default-logging
  driver: "json-file"
  options:
    max-size: "50m"
    max-file: "4"

services:
  proxy:
    image: docker.io/library/nginx
    volumes:
      - ./nginx_internal.conf:/etc/nginx/nginx.conf:ro,Z
      - ./proxy_params:/etc/nginx/proxy_params:ro,Z
    restart: always
    logging: *default-logging
    depends_on:
      - pictrs
      - lemmy-ui
    labels:
      - traefik.enable=true
      - traefik.http.routers.http-lemmy.entryPoints=http
      - traefik.http.routers.http-lemmy.rule=Host(`gregtech.eu`)
      - traefik.http.middlewares.https_redirect.redirectscheme.scheme=https
      - traefik.http.middlewares.https_redirect.redirectscheme.permanent=true
      - traefik.http.routers.http-lemmy.middlewares=https_redirect
      - traefik.http.routers.https-lemmy.entryPoints=https
      - traefik.http.routers.https-lemmy.rule=Host(`gregtech.eu`)
      - traefik.http.routers.https-lemmy.service=lemmy
      - traefik.http.routers.https-lemmy.tls=true
      - traefik.http.services.lemmy.loadbalancer.server.port=8536
      - traefik.http.routers.https-lemmy.tls.certResolver=le-ssl


  lemmy:
    image: dessalines/lemmy:0.19.8
    hostname: lemmy
    restart: always
    logging: *default-logging
    volumes:
      - ./lemmy.hjson:/config/config.hjson:Z
    depends_on:
      - postgres
      - pictrs
    networks:
      - default
      - database

  lemmy-ui:
    image: ghcr.io/xyphyn/photon:latest
    restart: always
    logging: *default-logging
    environment:
      - PUBLIC_INSTANCE_URL=gregtech.eu
      - PUBLIC_MIGRATE_COOKIE=true
#      - PUBLIC_SSR_ENABLED=true
      - PUBLIC_DEFAULT_FEED=All
      - PUBLIC_DEFAULT_FEED_SORT=Hot
      - PUBLIC_DEFAULT_COMMENT_SORT=Top
      - PUBLIC_LOCK_TO_INSTANCE=false



  pictrs:
    image: docker.io/asonix/pictrs:0.5
    # this needs to match the pictrs url in lemmy.hjson
    hostname: pictrs
    # we can set options to pictrs like this, here we set max. image size and forced format for conversion
    # entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp
    #entrypoint: /sbin/tini -- /usr/local/bin/pict-rs run  --max-file-count 10  --media-max-file-size 500 --media-retention-proxy 10d --media-retention-variants 10d  filesystem sled -p /mnt
    user: 991:991
    environment:
      - PICTRS__STORE__TYPE=object_storage
      - PICTRS__STORE__ENDPOINT=https://s3.eu-central-003.backblazeb2.com/
      - PICTRS__STORE__BUCKET_NAME=gregtech-lemmy
      - PICTRS__STORE__REGION=eu-central
      - PICTRS__STORE__USE_PATH_STYLE=false
      - PICTRS__STORE__ACCESS_KEY=redacted
      - PICTRS__STORE__SECRET_KEY=redacted
      - PICTRS__MEDIA__RETENTION__VARIANTS=0d
      - PICTRS__MEDIA__RETENTION__PROXY=0d
      - PICTRS__SERVER__API_KEY=redacted_api_key
      #- PICTRS__MEDIA__IMAGE__FORMAT=webp
      #- PICTRS__MEDIA__IMAGE__QUALITY__WEBP=50
      #- PICTRS__MEDIA__ANIMATION__QUALITY=50
    volumes:
      - ./volumes/pictrs:/mnt:Z
    restart: always
    logging: *default-logging

  postgres:
    image: docker.io/postgres:16-alpine
    hostname: postgres
    volumes:
      - ./volumes/postgres:/var/lib/postgresql/data:Z
      #- ./customPostgresql.conf:/etc/postgresql.conf:Z
    restart: always
    #command: postgres -c config_file=/etc/postgresql.conf
    shm_size: 256M
    logging: *default-logging
    environment:
      - POSTGRES_PASSWORD=password
      - POSTGRES_USER=lemmy
      - POSTGRES_DB=lemmy
    networks:
      - database
  postfix:
    image: docker.io/mwader/postfix-relay
    restart: "always"
    logging: *default-logging

networks:
  default:
    name: traefik_access
    external: true
  database:

When browsing larger communities or the "all" feed, it would make sense to sort by "controversial" or "most comments", but with the time selector of top (1,3,6 hours...).

Am I the only one missing this sort option? I couldn't find any feature request regarding this aspect of sorting, please forgive me if I missed something.

As far as I know this isn't a feature that exists, but I know the protocol should make it fairly easy.

What I'm thinking is for Lemmy to basically have the option to inherit the comment thread when posting a URL to another fediverse service.

E.g. If crossposting a Lemmy thread, you get a tickbox saying "inherit comment section" or something and it makes the new thread effectively a symlink to the original.

This could also be used to bootstrap other fediverse services like pixelfed and peertube by enabling people to comment directly from their Lemmy instance.

So I know that there is Lemmy redirect and linksheet with which you could technically open Lemmy links in your preferred app, but there has got to be a better way. This should definitely be a feature that gets added since the possibility of your actually finding a post from your own instance on Google(or duckduckgo) is very slim. I can't imagine Lemmy gaining much of a following before flaws like this are ironed out.

What are best lemmy communities?

@lemmy

For you, what is the best Lemmy community/subreddit?

When viewing different instances, whether to copy a community link to make another instance aware of it & subscribe to it or otherwise, it would be nice to have a switch along the top bar to switch between admin-set light/dark mode themes.

That way you aren't either forced into being blinded by light mode or having to let your eyes adjust to dark mode. Admins could choose the variant of light or dark theme to have the switch toggle between, so in the case of more customized instances they could retain their distinct style.

For reference, see almost any site with a light/dark toggle, but for a closer example, see Piefed's approach.

I think I remember this became possible. I'd like to know how to do it and what the effects would be.

• Would I lose all post history?
• Would there be issues with the posts votes?
• Do I need a mod account from thr instance being moved to etc?

If anyone has seen a post with a guide I'd love a link or if you have experience I'd love to hear.

Thank you.

On Hexbear, moderators may factor upvote activity into moderation decisions.

Some users treat upvotes as a “mark as read” function, which weakens score reliability and therefore negatively impacts The Algorithm.

Please provide a separate mechanism for users to identify posts that they have already read, which will persist on later visits.

Hi! Another question about lemmy development.

Is lemmy working towards functioning more with discourse, flarum and nodebb federations?

I think that mastodon kinda fucked the fediverse and having a costellation of linked forums is much more powerful than microblogging so i'm interested in using lemmy as a forum more than a simple link aggregator

Just noticed that unlike mastodons join page, lemmy doesn't have a "join" or "create an account" button. It'd be nice to have one, it would be more straightforward to join.

Or perhaps there is a reason why it doesn't exist?

cross-posted from: https://lemmy.ml/post/22529967

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Changes

This is a small bugfix release with the following:

• Fixing cors origin wildcard. by @dessalines in #5194
• Fetch community mods synchronously by @Nutomic in #5169
• Move aggregates to replaceable_schema, fix error (fixes #5186) by @Nutomic in #5190

Full Changelog

• Lemmy Backend
• Lemmy-UI

Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over five years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive, and helps us grow our little developer co-op to support more full-time developers.

• Liberapay (preferred option)
• Open Collective
• Patreon
• Cryptocurrency

I'm not sure if this post should instead be put in !lemmy_support@lemmy.ml, rather than here; please let me know if this would be better suited there, and/or if it is out of the scope of this community. Also, please let me know if there is a different community, other than where it has already been posted, in which this post would be better suited.

Topics could include (this list is not intending to be exhaustive — if you think something is relevant, then please don't hesitate to share it):

• Moderation
• Handling of illegal content
• Server structure (system requirements, configs, layouts, etc.)
• Community transparency/communication
• Server maintenance (updates, scaling, etc.)