this post was submitted on 25 Jun 2023
63 points (94.4% liked)

No Stupid Questions

35882 readers
2584 users here now

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)


Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.



Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.



Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.



Rule 4- No self promotion or upvote-farming of any kind.

That's it.



Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.



Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.



Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.



Rule 8- All comments should try to stay relevant to their parent content.



Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.



Rule 10- Majority of bots aren't allowed to participate here.



Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

founded 1 year ago
MODERATORS
 

Just in case anyone is using their account here to post to off-instance communities: those posts and comments seem to have a very high failure rate. There is a lot of activity and accounts on this instance. This is to raise awareness, not to pull people away or break up the lemmyverse. Quite the opposite really: there is a technical problem on this instance that might be preventing the lemmyverse from functioning as it should.

top 48 comments
sorted by: hot top controversial new old
[–] solidgrue@lemmy.world 53 points 1 year ago (3 children)

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.

[–] BrikoX@vlemmy.net 11 points 1 year ago (1 children)

The new version also reduces its reliance on websockete

From my understaind it's not a reduction, but a complete repalcement.

[–] solidgrue@lemmy.world 3 points 1 year ago (1 children)

You're probably right. I'm not a programmer and am not familiar with the code base so I was avoiding speaking in absolutes.

[–] daleus@lemmy.world 10 points 1 year ago

Sith vibe check passed

[–] Boiglenoight@lemmy.world 9 points 1 year ago

An aside, the Astros are up 2-1 in the bottom of the 3rd.

[–] mashhitmyself@lemmy.world 6 points 1 year ago (1 children)

I don't think it's a version issue. It could be, but testing I've done says otherwise. There's plenty of 0.17.4 instances that, despite other bugs, have no problem sending and receiving updates from other instances. I hope you're right. I don't run the instance so testing reveals mostly speculation.

[–] ShittyKopper@lemmy.w.on-t.work -5 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] acupofcoffee@lemmy.world 8 points 1 year ago (1 children)

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.

[–] mashhitmyself@lemmy.world -1 points 1 year ago (1 children)

That is an issue for sure, but probably better addressed at the ActivityPub level? IMO, an instance should be limited to a single community.

[–] acupofcoffee@lemmy.world 0 points 1 year ago

Yes, this would be a change to the underlying protocol. I think it’s definitely worth discussing how this problem can be solved by people who maintain ActivityPub. IMHO the Lemmy and kbin developers should also be a part of these discussions as well.

[–] Sami@lemmy.zip 12 points 1 year ago* (last edited 1 year ago) (1 children)

It's a known issue:

https://github.com/LemmyNet/lemmy/issues/3101

https://lemmy.ml/post/1453121

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.

[–] Sunrosa@lemmy.world 7 points 1 year ago (1 children)

What do you think is causing the failures? How are you seeing the fact that it's failing?

[–] mashhitmyself@lemmy.world 3 points 1 year ago (1 children)

Like you mentioned afterward. Comments and posts just plain failing to land on any other instance. Also I run an instance for testing and can see incoming connections. lemmy.world fails at a protocol level, not at the application level. It's a, IMHO, bandwidth issue. Hopefully the admin is aware and wants to fix it. I'd say he has a responsibility, but he doesn't. lol.

[–] Sunrosa@lemmy.world 1 points 1 year ago

That's not good

[–] Countmacula@lemmy.world 4 points 1 year ago (3 children)

I find everything to show up pretty well. Have an example?

[–] Sunrosa@lemmy.world 5 points 1 year ago

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.

[–] liara@lemmy.world 5 points 1 year ago

Yeah, take a look at my profile from the perspective of lemmy.world:

https://lemmy.world/u/liara

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

[–] mashhitmyself@lemmy.world 2 points 1 year ago (1 children)

This post can be an example. Check: https://sh.itjust.works/post/446063 Do you see our conversation?

[–] ndr@lemmy.world 0 points 1 year ago (1 children)

What is this supposed to prove? I see the same thing there and on lemmy.world

[–] mashhitmyself@lemmy.world 0 points 1 year ago (1 children)

Just to be clear: if you load these two pages: https://sh.itjust.works/post/446063 and https://lemmy.world/post/609080 that are identical?

[–] ndr@lemmy.world 2 points 1 year ago

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.

[–] smolgumball@lemmy.world 4 points 1 year ago (1 children)

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

[–] mashhitmyself@lemmy.world 2 points 1 year ago

Correct. I am not testing with any of those instances. You shouldn't expect that to work at all, but I guess some users might not know.

I saw this on lemmy.world, went to reply to a comment, realized I wasn't on my instance, flipped back and I can't find it, so sadly I fear you might be correct that there is something wrong.

[–] lml@remy.city 4 points 1 year ago

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 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. In the future I am sure instances like lemmy.world will be able to handle the 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 more alt-right communities like lemmygrad and exploding-heads, and from lemmynsfw.com because of content hosting concerns. I'm open to suggestions on others.)

[–] Tenthrow@lemmy.world 2 points 1 year ago (1 children)

So I’ve been thinking of spinning up a personal instance. I have the tech chops for most projects like this in a small scale but are there any reasons why I shouldn’t use Lemmy in that way?

[–] mashhitmyself@lemmy.world 4 points 1 year ago (1 children)

Do it. Be super aware of how federation works though. The more stuff your users subscribe to the more network traffic you will need to accommodate.

[–] Tired8281@lemmy.world 2 points 1 year ago (1 children)

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.

[–] lml@remy.city 1 points 1 year ago

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.

[–] neonfire@kbin.social 2 points 1 year ago

This isn't a question

[–] smolgumball@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago) (1 children)

(ignore me) test post from sh.itjust.works account

[–] zebus@kbin.social 1 points 1 year ago (1 children)

I’m on kbin.social and I can see this ;)

[–] mashhitmyself@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (2 children)

Hilarious. This comment doesn't show on sh.itjust.works, which makes total sense. lemmy.world is responsible for sending it to other federated servers. Maybe kbin > lemmy right now?

[–] Zerlyna@lemmy.world 4 points 1 year ago (1 children)
[–] mashhitmyself@lemmy.world 5 points 1 year ago

sh.it.works.sometimes

[–] Teppic@kbin.social 0 points 1 year ago (1 children)

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!

[–] mashhitmyself@lemmy.world 4 points 1 year ago

OMG. You're right! I just edited the title. Which, lol, will not show up everywhere.

[–] Zak@lemmy.world 0 points 1 year ago (1 children)

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.

[–] mashhitmyself@lemmy.world 2 points 1 year ago (1 children)

Fair enough. Keep in mind, being popular doesn't magically bestow the knowledge, resources, or willingness to handle issues.

[–] lml@remy.city 2 points 1 year ago

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.

load more comments
view more: next ›