They don’t appear to have federation enabled yet.

Lemmy has mangled that script a bit.

Lemmy seems to mangle a lot of links that aren’t basic urls. SimpleX chat links break for some reason here too.

Thank you for the suggestions. At this point it seems the best option may be to just shutter this instance and start over with a fresh database instead of dealing with a bunch of nagging problems from previous experiments. I’ve done plenty of testing in production because for most of that time it was only me being affected by the consequences lol.

Very nice. Thank you for the continued work.

Yeah that would do it lol. Thanks for that info.

Apologies OP, I don’t keep up with who’s blocking who on Lemmy.

It could be that LBZ hasn’t discovered the community yet. If that’s the case you may have to try a couple times before it actually populates. One of many federation quirks. Here are some other links to try.

!mutual_aid@hexbear.net

https://hexbear.net/c/mutual_aid

There’s !mutual_aid@hexbear.net which I believe allow GoFundMe links.

@Sir_Kevin@lemmy.dbzer0.com carrying !loweffortmemes@walledgarden.xyz to the top this week.

Thank you!

Subscriber Growth

!weedtime@walledgarden.xyz, weedtime, 93 => 104, 92 posts (18 this week)

🙏

!gardengrooves@walledgarden.xyz represent

I’m not sure it’s been entirely solved. Our host is working through an unrelated hardware problem that hit in the middle of our last round of tuning but things have been behaving better aside from that.

The answer for us has been in adjusting the lemmy pool size to the database and tweaking the available resources to find a happy medium.

Can my humble, single-user instance handle it?

Maybe?

FWIW this information is based on the experience when using remote hosting not self hosting.

The main issue for us was tuning the database performance. The bot can beat your database to death sometimes and just throwing resources at it won’t necessarily solve it. related low effort meme Our experience was that the bot performance hit wasn’t really noticable immediately but it adds up as more and more communities are added to the database. There also seem to be bursts of database load at times, maybe that’s when new instances join the network? They seem to only last a short time though and haven’t really caused problems.

TLDR- Expect an eventual performance hit. If it’s too much you can always disable the bot or adjust what it does.

Seems a bit more normal today, cool.

Lemmy RN

walledgarden.xyz📢

Bot seems fine to me lololololol

!gardengrooves@walledgarden.xyz topping the list with the bot on the fritz, you love to see it.

Update to this-

After talking with my host some adjustments were made that should correct the curl error. I still don’t believe this has anything to do with the lost sync but it’s one less thing to worry about. Thanks for the information and help!

I saw your comment but I was mainly concerned with getting the instance to show up on lemmyverse at the time, which I suspected was the connection being blocked by our host (it was). Coincidentally since getting listed lemmyverse has been having its own problems so I put it on the back burner.

I’ll do some deeper digging into this and see what I can figure out. I don’t think it has anything to do with the communities falling out of sync since it’s never mattered before now and WG isn’t the sole instance being impacted, but it should work correctly either way.