- cross-posted to:
- meta@sopuli.xyz
- cross-posted to:
- meta@sopuli.xyz
You must log in or register to comment.
Btw: 0.19.1, leading zero. It’s not yet at 1.0 for a reason.
Added the 0
I am not sure what you imply. Like Early Access it might be a descriptive factor, but it matters very little. Some use that label for finished products with full support adding new features, while others use it as a means they skipped quality control entirely or are prototyping heavily. In the end it still is a paid for software. In Lemmy’s case it is the first with its own financ model. It is highly usable and hopefully this bug sees the improvement in testing to avoid.
LibreOffice has a much higher version number, but as my small rant post on it, if I was responsible for QA I wouldn’t have let it release at all in the current state and am baffled what goes on internally to cause that.
This guy does not semantic version.
I think it’s more about the fact that Lemmy is going to be used as, and have expectations of, a finished product, whether they say it is or not. Any project, FOSS or not, that grows this quick goes through this stage.
I’m not saying those expectations are valid, I’m just saying the vast majority of people will not be able to comprehend how an issue like this can make it’s way through given the maturity that Lemmy has, since it works so well most of the time despite being alpha.
Edit: Clarity: I think the 0 should be in the title regardless.
I added it, hopefully the edit gets federated
Came through on my instance 😉
Amazing how nuclear people went on my post downvoting, because I don’t place enough value on version numbers. It is just a bug like many others.
I’m implying that the headline of the submission is wrong and the leading zero is not decorative.
Lemmy has been feeling pretty empty the past couple of days. That just really goes to show how important federation really is.
I noticed that as well, thought maybe things were just slowing down, but it’s good to know it was the software and not a sudden drop in community involvement. Since admins became aware of the bug and began restarting their servers as an ad-hoc fix, I’ve been seeing way more engagement on my instance.
Yes and no, if you have enough users you do not need federation for a server to not feel empty. But overall many servers do not have that many users, so federation with larger ones is essential.
Sounds like something a cardassian would say.
It took me a second to realize what cardassians you were talking about. I constantly forget the other ones are spelled with a K
Man, the one thing not to break. They broke it.
for the most part federation works just fine. there are occasional issues, yes, but it’s not like it can’t federate at all.
Does my comment reach anyone?
I would comment on this but since federation is broken…this won’t be seen until the instance admin restarts Lemmy and federation works once again.
Federation seems to be working fine from where I stand?
Edit:
Edit 2:
Even the edit federated out to your instance fine…
deleted by creator
I think it works for a while after restart of the server, and then stops working. Yesterday I was making comments that didn’t federate until 12 hours later when I assume the instance admin restarted the server.
My instance has been uo for over 3 days since 0.19.1 update with no issues - very little load though
Yeah it seems to work for some instances with 0.19.1 but Lemmy.today has issues and feddit.de as well, just from what I’ve heard. Probably plenty more.
A while ago, programming.dev had a problem where nothing from the instance federated for a week. Lemmy felt so empty
Am I little naive in wondering how this isn’t caught in unit, integration and E2E tests?
Edit: looks more involved than that, but it forced me to dig into how some of the components are tested. Educational.
I’m going to set up a cronjob to restart the Lemmy docker container every 6 hours. That seems to be around when stuff stops working usually.
Sheesh.
oof
Yup, absolutely nothing I posted from lemm.ee yesterday made it out into the wider world. In fact I’ll probably have to manually federate this comment too.
Hopefully they can get to the bottom of it. Maybe next year we need a rule about releasing anything in December when everyone’s too busy to bugfix 😅
Curious: what do you mean by “manually federating” a comment?
My other account is on .world so I can use search to forcibly pull things onto at least that server (search for the original URL of the unfederated post or comment and then wait a few seconds). Sometimes doing that will also encourage whatever it was to federate more widely to more servers, but that doesn’t seem to be happening as reliably either since the upgrade 🤷♀️
A restart of Lemmy seems to fix it temporarily according to admin of Lemmy.today.
But it’s inconsistent and stops working after a while it seems.
deleted by creator
I’m glad I’m not the only one then. 19.1 here
I’d say the bug seems to be slightly different from my observations, in that things are leaky rather than broken. Could be wrong though.
Edit: previously post was mobile keyboard mince meat:
I’d say the big seems to be slightly different from my observations, in that things are meant rather than broken. Could be wrong though.
