The new version also reduces its reliance on websockete
From my understaind it's not a reduction, but a complete replacement.
An aside, the Astros are up 2-1 in the bottom of the 3rd.
There’s plenty of 0.17.4 instances that, despite other bugs, have no problem sending and receiving updates from other instances.
It's probably because of the absolute scale of dot world. This is what happens when you try to centralize ActivityPub, especially an implementation like Lemmy which did not previously have any of the scaling challenges the likes of Mastodon had before.
Everyone should've told people to pick different instances (there are STILL new guides written where step 1 is to "just register on dot world" [or shitjustworks, which isn't any better, really]) and admin should've locked registrations after 10-15k, maybe 20k users MAX, yet y'all got too greedy. Good fucking luck dealing with the aftermath.
I should probably go to bed, I'm getting grumpy.
In my opinion, we need to somehow solve the community centralization issue first. MultiCommunities, or some way to aggregate the dozens of large-ish groups like “news, technology, etc” and be able to subscribe to all of them in one fell swoop would allow people to spread out to other instances much more reliably.
I’ve brought this up as a suggestion elsewhere. People seem annoyed at the lemmy vs kbin idea of “communities vs magazines”. Maybe everything is changed to “communities” and “magazines” are officially adopted as community-maintained mega-lists of common communities.
An example. There’s a bunch of car manufacturers. Sure, maybe I could just select the “Honda” community on every instance I can find, or instead I subscribe to the magazine called “Honda” which auto-subscribes me to every single Honda community in the list… or even the magazine called “Cars” which would include all manufacturers and cars communities.
Then there could be a Magazine view for that Magazine which would allow all posts from those communities to be aggregated in one place.
Just spitballing ideas.
It's a known issue:
https://github.com/LemmyNet/lemmy/issues/3101
Seems to be growing pains from Lemmy having to scale up in a very short amount of time so hopefully they are able to find a workaround soon.
It's not happening everywhere and all the time but it happens enough for you to think a post or comment has no engagement when it does just not on your instance.
We really need some more developers... I wish I could really help, but it would take way more time than I have to do more than poke around.
That isn’t at all what is happening, the world admin team has been very engaged with the project on GitHub with a ton of back and forth and various code pushes to fix the captcha pullback that’s in 0.18. The issue you are seeing is known and the belief is it should get better with the update to 0.18.1 that the devs have said is coming in the next few days. It seems to be partly due to the size of the world instance and the problems with web sockets. You’re likely being downvoted for appearing to be authoritative about this and blaming the world admin team (it’s more than a single person) when they know this is a symptom and have a plan they think will fix it that a little more digging into the history of why they’ve chosen to forgo the 0.18.0 update would have answered your questions.
Is there any use to spinning up an instance, only allowing say 10 people max, then just keep it updated and let it run, to take the load of those ten people off the bigger instances? Is that too small time to be useful? I have pretty weak upload.
I think that would be worth it, yeah. Of course if you are hosting it on your home network there will be some added security concerns (and that might make it better to only allow signups to friends/friends of friends/etc). The way I see it is that some instances are going to host the largest communities, and therefore those instances are going to need to handle all of the incoming/outgoing updates to posts in those communities. Right now they can't do that reliably and push updates out to all of their users' devices.
So in the long run I think having small/medium instances (say a couple hundred, not tens of thousands of users) will be the way to grow. These smaller communities can push updates to their smaller user count reliably, and then have more resources to handle federated content coming in and going out. I think scaling for the incoming/outgoing federation requests would be easier than for direct user activity. Federation stuff can be queued and then spread over time, but user requests cannot be.
I find everything to show up pretty well. Have an example?
A post I sent 4 hours ago to lemmy.ml wasn't showing up. After I edited it once with no changes, it showed up as posted 1 minute ago. It's definitely an issue taking place. You can check to see if your posts are showing up at their destinations with the rainbow federation link button next to posts.
Yeah, take a look at my profile from the perspective of lemmy.world:
Then compare with the comment count compared to other instances:
https://lemmy.ca/u/liara@lemmy.world
https://lemm.ee/u/liara@lemmy.world
9 of my comments haven't federated and are visible only to lemmy.world
https://lemmy.ml/u/liara@lemmy.world
22 comments made it to .ml but that's still missing 6 comments
My bad, I’m an idiot lol
No, they’re not. I was only comparing that conversation because I thought it was a direct link to that comment chain, but in fact many other comments are missing.
This is the problem we are having with fast growth on a few select communities. The largest servers are being bogged down simply because the software has not been tuned for these large types of instances yet. ActivityPub works best (in it's current state) by spreading users over smaller/medium sized instances. Folks need to take a look at other instances (and I agree it is hard to find them for a newcomer). You can look at https://fedidb.org/ to look at instances that have been indexed running kbin, lemmy, and other software.
Joining a smaller instance means that your server is not being bogged down by tens of thousands of other users trying to pull updates to their devices at the same time. You can still see the content from other instances, and in many cases it is more reliable because your smaller instance actually has the resources to handle pulling in the posts you want to see. The server-to-server communications that make content federation possible are less resource intensive than pushing updates to user devices. Less users on an instance = more server resources to actually federate content. In the future I am sure instances like lemmy.world will be able to handle the user traffic and federation traffic smoothly, but for now the best way to ensure stability is to join a smaller instance.
(Plug for my instance: https://remy.city, a general purpose Kbin instance. I set it up for personal use but anyone is free to join me in using it. I have defederated from the instances with more extreme viewpoints userbase-wide (like lemmygrad and exploding-heads), and from lemmynsfw.com because of content hosting concerns. I'm open to suggestions on others.)
First, thanks for putting your instance out there! We need more open servers.
Second, lemmygrad is straight-up Marxist, which is about as far left as you can get - pretty much the opposite of "alt-right".
Also keep in mind that defederating (blocked instances) will prevent posts and comments from syncing between instances as well.
You can see blocked instances on lemmy.world here: https://lemmy.world/instances
sh.itsfu.cked
Lemmy.ca chcecking in. I had to scroll quite a ways to find out what instance you were complaining about.
OP, This highlights something else - I think the reason you are getting down votes is that most people seeing this thread are not on lemmy.world. The heading is a bit misleading (or potentially wrong) from the perspective of a federated user - which is most of us!
This has been discussed in an issues thread which @ruud@lemmy.world responded to, so we can assume he's aware, though I haven't seen an update.
being popular doesn't magically bestow the knowledge, resources, or willingness to handle issues
I would like that on a T-Shirt, please.
Good point. Nothing against the larger instance owners of course. If my little instance got super popular somehow (like being recommended in guides on how to join lemmy/kbin), and thousands of users got in per day, I could see issues happening just like this. I don't know the ins and outs of tuning this software for performance at scale, and I know I couldn't learn it fast enough if my instance faced very fast growth like lemmy.world has.
I think admins are going to need to turn registrations off periodically, as they scale their hardware (and their knowledge) to run it for more users effectively.
(ignore me) test post from sh.itjust.works account
Incoming works 98%, outgoing is more like 30-50%. Lemmy.world is a one-way lemmy-vacuum. Just the way the fediverse was meant to be. lol
Yeah this is so bizarre. Is it possible that sh.itjust.works is having trouble receiving, or is it confirmed that lemmy.world is dropping the ball on outgoing notifications?
Technically according to the new D&D movie, with the "right?" at the end it is
It'll get fixed. Right now this may be a swamped and baffled community, but it is also excited and highly motivated.
thanks for using Leebra!
go to feed...
Lemmy.world and some others have held back on the 0.18.0 back end update because the admin did not want to forego this Captcha integration, which broke in 0.18.0. Version 0.18.1 is expected to release soon, and address the regression with Captcha.
The new version also reduces its reliance on websockete, which should address a number of other quality-of-life problems on this instance, such as the random post bug (and hopefully the 404s/JSON errors I've been getting all afternoon).
Hopefully just a few more days and we'll be back to rights.
save