This basically shuts my idea down

it’s not very difficult to modify the code for something like this… and closing off registration wont’ let anyone else login and create new content form your istance.

Personally the load on the major servers by having one more instance that subscribes to everything is why I think people should back off from creating more than the 1500 instances Lemmy network already has. Delivery of every single vote, comment, post 24 hours a day just so one person can read content for an hour or two a day.

That makes sense for email systems where all that content doesn’t have to be sent, but for Lemmy it’s a huge amount of overhead.

Keep in mind that you’re going to be retrieving and storing a huge amount of data running these scripts

And you are adding to the overload of lemmy.world, beehaw, lemmy.ml, etc who have all the popular content communities. Federation has a lot of overhead, as does having to distribute a community one vote at a time to 500 subscribed servers.

pend my time on Lemmy scrolling “All”, which I think is a pretty common thing.

There was a lot of advice handed out back in June that the answer to scaling Lemmy was to go create instances. The reason it works is because “All” is empty on a virgin system ;) With no data in the database, the logic Lemmy hands to PostgreSQL works real fast ;)

@Prefix@lemm.ee - maybe pin this for a while?

The real war is hate media memes and messages that trickle down to those obedient to voices from the clouds, electric voices these days. In the old days, books that said burning bushes gave out signals.

Cool to hear, have a great weekend

OK, solved my own issue

lemmy-ui bypasses the variable if it sees you running localhost 1234, it hard codes 8536

export default function getExternalHost() {
  return isBrowser()
    ? `${window.location.hostname}${
        ["1234", "1235"].includes(window.location.port)
          ? ":8536"
          : window.location.port === ""
          ? ""
          : `:${window.location.port}`
      }`
    : process.env.LEMMY_UI_LEMMY_EXTERNAL_HOST || testHost;
}

it has 40 comments total, but the problem is that when I request comments without specifying max_depth, and sort ordered by New, I receive only 10 comments, if I try to specify page, or limit, I get an error {“error”:“couldnt_get_comments”}.

What values are you sending for limit and page? Are you sure they just aren’t out of range?

without specifying max_depth

I think max_depth has a default, but I don’t recall at the moment. Are the 10 comments you do get all trunk level comments, directly on the post?

My intention is doing something similar to an user pressing “Comments” on front of a community, like calling the community URL

From what I understand, depth only comes into play when you are viewing the comments of a specific post. If you are just listing comments across multiple posts in a community… they are presented flat. At least that is how lemmy-ui does it when I view comments for a community… which I assuming is using API /comment/list. Am I following what you are attempting?

I have this post replicated to my own instance where I have direct SQL access: https://BulletinTree.com/comment/1318138

I’m looking at it and I see 2 deleted-by-creator that seem to be direct replies to the first comment in the branch that says 9.

The lemmy-ui I am running is off main, not the 0.18.0 branch, and I just updated it a couple days ago. But it obviously differs in exposing these, and so does my API.

EDIT: I updated my lemmy-ui to main just now again, it had changes, and still showing. Obviously my API is returning the deleted comments for not-logged-in users still… I wonder if that’s because I’m running main of lemmy_server and not the 0.18.4 tag branch and they differ in behavior.

I’ve been studying the underlying PostgreSQL content of path and how child_count gets done the last few days…

First off, is this consistent - as there are some questions about deleted comments, removed comments, personal blocking of users who create comments, banned from community person who created comments, etc. Your API with curl doesn’t have an auth on it, so personal blocking shouldn’t be a factor (not logged in).

max_depth=999 limit=999

I’m not sure how lemmy_server behaves when ranges are out of bounds here. limit on comments is 300 hard-coded in the Rust code AFAIK, and max_depth like around 15.

I think child_count is intended to mean all generations of children, not “direct replies to this comment” count. In your example:

  "path": "0.2157873.2158260",
  "id": 2158260,
  "content": "You just post questions as top-level replies to the stickied thread that day, and we'll be online to answer them.",
  "child_count": 6

The child_count looks correct, hand-counting I get 6 that are all originating off of 2158260.

  "path": "0.2157873.2158260.2229041.2231423",
  "id": 2231423,
  "content": "As the post mentions, it will be stickied to the top of lemmy.ml ",
  "child_count": 2

Also looks correct, I see a child and a grandchild, totaling 2 comments in the way I understand they intend to count.

  "path": "0.2157873",
  "id": 2157873,
  "content": "Really cool! I'm excited to learn more about you and the project!\n\nWhat's the format? Should we submit questions beforehand, or will you process questions that arrive at the start time? I've never participated in an AMA  😅 ",
  "child_count": 9

I would expect 7 given what you show. Are 2 reply comments deleted, removed?

I do KNOW that in version 0.18.4 - the SQL that updates comment_aggregates child_count does NOT look at deleted or removed. It suspect it always counts them as children, even if you as a non-moderator, non-administrator can not fetch them. The fetch policy has changed in 0.18.x releases, it used to be you could indeed load deleted comments and even see their content.

As I said first off, is this consistent? Can we find a 9-count comment tree that has all 9 where there are no delete or remove at play.

I use that periodically to compare feeds, and like I said sometimes a post or comment is missing, actually I often see a comment that looks like it’s responding to a another comment, but I cannot see the parent comment.

There have been bugs in Lemmy not sending comment deletes to all the instances. And lemmy.world and lemmy.ml were not communicating fro Saturday through Tuesday. Lemmy.world had some significant outages. It gets pretty tricky to track down and identify exact causes while things are unstable.

Nolan pushed the limit of IMAX projectors with Interstellar run time in 2014, he went out of his way to find out what the maximum that could be done with platter modifications, an extra 20 minutes.

cool, thank you

Sunday, lemmy.ml is performing better than I have seen it in 60 days. I did get errors on Saturday and significant lag. Not sure if activity is just today or what, but it’s really been fast in routine browsing.

Who are you? I am published author Stephen Alfred Gutknecht, an expert in messaging systems and operating systms. Do you have evidene and facts? (I do have brain damage)

Can you identify who you are?

Can you answer details about GitHub issue 2910 on Lemmy project and the date?

I am sorry to all the never-joined, never-stayed users of Lemmy in May, June, July 2023 “Tweet is X”, “Reddit is $API” ------ because I could not draw enough attention and developers to Github Issue #2910 avoidance. I failed entirely in my social effort I tried to do for 60+ days. I really failed, brain damaged fuck-up I am. The worst failure in my life, and it’s the end of the line.

I’m not sure if there’s a minimum Postgres version specified anywhere in the docs, I took a quick look but couldn’t find it.

I do not find it in the “From Scratch Install” documentation. I will work to revise those documents this weekend to warn people that 0.18.3 and later is incompatible. Thank you again for sharing.

docker compose down &&

Looks like the & parsing in code blocks is another bug in 0.18.3 like the post title one. I’ll add your comment to the GitHub issue.

Thank you for sharing.