FYI: !lemmydev@lemm.ee
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;
}
So if a home server goes down will those posts disappear from the community server?
terminology wise, "home server of a community" and then there are remote-servers for that community. And Lemmy community/devs tend to call a "server" an "instance". To answer your question... if a user is on a remote instance from a community, they are reading copies of the content in a local database. If the community home instance goes down, the copies will still be there in the remote servers. However, they are now in an isolated island and none of the other servers will get the new post and comments - as the home instance of a community does distribution. There isn't any kind of warning indicator that you are on an isolated island.
Nothing disappears, but it is possible to have incomplete replication - have only some of the comments and posts and get an impression that nobody replied or that there isn't much content.
Lemmy is not showing replies
Here is an odd behavior.... if you view this link: https://lemmy.ml/comment/2119446
You will get 3 comments. The link on each of those 3 comments will be the same, you do not get the id number for their individual comments.
As of the time of this comment, now crashing
AGAIN Down
The quantity of users on Lemmy I still consider to be pretty low, the performance bugs need to be addressed on a big server. Bugs like not having a WHERE clause on an UPDATE hitting 1500 rows in a table (one row per server) instead of 1 single row... these need to be shaken out.
The errors of the overload themselves have been a way to throttle growth of the big servers. People were not able to insert new posts and comments into Lemmy.ml - reducing outbound federation activity too, and they went to other servers. This went on all of June and July.
subscribe to every community, and let federation load overwhelm your server.
Did that, takes lots of time to wait for the content to come in.... and there is no backfill. Plus I suspect that the oldest servers (online for several years) have some migration/upgrade related data that isn't being accounted for.
I've had to really adjust my thinking with this project. They want to do things a very particular way and it goes back 4 years, and a lot of the mistakes are just now getting noticed/attention. For example, comments were not deleting on all the servers, I was testing that after comparing server copies of the same communities and found they were not the same. It just didn't seem to have a lot of people spot-checking it for mistakes. I am learn to just "go with the flow" and face that it's more like how musicians would approach design and running a project. Media-focused systems can be that way.
3 underscores did not work in preview, I'll just leave it as is now, a clickable link (not rendered inline)
I don't think it works on an image?!
Having worked with lemmy_server code for months, I wouldn't trust it in practice. Unless someone produces a pretty through test to validate that it actually works as intended when out-of-band data delivery attempts are made. And for discussion sake, I am assuming comment and posting "messages", and not private messages... which is a whole different set of behaviors.
when a user homed on lemm.ee comments on a post where the community is hosted on lemmy.world, it would get delivered to lemmy.ml by lemmy.world, not the origin lemm.ee instance.
I don't think the actual message carries a signature from the origin instance, in this case lemm.ee - I could be wrong, because it may not unpack and repackage it before forwarding to subscribed instance servers. But there are some very short timeouts on these signatures and HTTP connections, and I think it does unpackage it and repackage a public comment message.
I think lemmy.ml would need to go fetch the profile for the then unknown user to be able to get the display name and other details of the lemm.ee comment creator to display on the comment. The signature for the comment I think would actually only validate lemmy.world to lemmy.ml - and if lemmy.ml already has the profile of the lemm.ee user stored locally it may not verify it (and could be an entirely different install with the same username). But I don't think many have ventured into study the code in these areas. The whole process hasn't been examined that much and I wouldn't be surprised at all if there are issues with post and comment getting dropped because servers aren't all reachable at the right times for these steps.