I am sorry for posting about this, since it’s a recurring issue, but I can’t do anything else about it.
I noticed that I was logged out today, and I think it’s because they installed a new release candidate (currently BE: 0.19.0-rc.13).
I just deleted my last comment which failed to federate, then re-commented, and it seems to work now. I confirmed on a few different instances that the comment is visible.
It seems that didn’t last very long.
Well crud. Still the same backend version, too.
Jerboa was just updated to support login on 0.19, but with the federation bug it’s kind of a moot point. Guess I’d better move to another instance until this blows over.
Yep. I just posted this exact same question on Privacy@lemmy.ml and Privacy Guides@lemmy.one and they sure don’t appear when visiting lemmy.ml or lemmy.one directly 🙁
You know what? I thought that was a glitch on SDF’s Lemmy server. But it’s never fixed. And the problem I have on SDF’s Matrix server also is never fixed. And the problem I had on SDF’s Peertube server took resetting my entire account to fix. And user support is basically permanently out to lunch at SDF.
I’m really starting to regret paying for my SDF account when apparently other free Fediverse services work much better. Like, really, REALLY regretting it now…
You are right with the issues you mention, but keep in mind that sdf is not a for-profit service and is therefore maintained as such. It is a huge operation keep afloat by a few people. I have had an account there for more than a decade and there are always issues with the different services, so if you want to follow a server that has nearly no downtime you will need to find some other place. Sorry about that.
It is huge operation keep afloat by a few people
Exactly what I regret paying for. Obviously they’re in over their head.
I don’t mind paying for a service. In fact, I believe in paying for what I use so much that it’s the very reason I chose to open an account with SDF to take my first steps on the Fediverse rather than open free accounts on bigger servers. But I do have a problem when whatever I paid for chronically doesn’t work properly. Had I been told SDF was understaffed and underfunded, I would have sought to pay for the same services from someone else - or even host my own instances.
I understand what you’re saying, SDF’s raison d’etre and philosophy totally resonates with my own set of values, and I sympathize with their staff. But the fact remains that I regularly spend 10 minutes posting something that disappears in the ether because some stupid bug no other (free) Lemmy instances seem to have doesn’t get fixed on the one instance I really really want to support.
After like the 5th time, and with the other problems I have, it gets to be supremely frustrating.
It’s not the money. If SDF asked me 10x the amount I paid, and do so yearly, I would still pay it for basic, fully functional services. It’s the really nasty feeling of trying to do the right thing and getting less than everybody else for my goodwill.
And even being understaffed and underfunded would at least be understandable, but some of these problems have been caused by the completely unnecessary upgrade of Lemmy to a non-stable branch.
That was possibly done to recover locked-out users. Lemmy 0.19.x switched to SHA-1 for 2FA from SHA256 and added TOTP verification for enabling 2FA. Since SHA256 isn’t supported by many authenticator apps, only generating invalid tokens, it left many users locked-out. Doing the upgrade disabled previously enabled 2FA. So it makes sense. lemmy.ml is also on RC, by the way.
lemmy.ml is also on RC, by the way.
Sure, but that is the instance specifically run by the Lemmy developers.
Sure, but it’s a regular instance. They do have one that’s primarily for testing, voyager.lemmy.ml.
Sure, but the idea of running, monitoring and supporting the (final) RC on lemmy.ml is to see how it performs under real life conditions, before letting it loose in the wild. And it was properly announced beforehand. This is quite different from what SDF did with this instance.
You’re making it sound like you actually had to pay. It’s like with other instances. You can donate, but you don’t have to. Unfortunately, I am unable to do so due to them using PayPal without allowing guest payments from Slovakia, so I am here for free. I wish they used OpenCollective.
But let’s snap back. Where exactly did you have to pay? I feel like you might have gotten scammed.
I did not have to pay in the sense that SDF offers the service for free.
I did have to pay because SDF provides a service I use, I have the means, and I know SDF does not monetize my data. That is a rare perl in this day and age. I pay a slew of other such rare concerns for that very reason, like the Well, the Calyx Institute or FUTO. Companies and individuals who treat me right get my money: it’s their only income since they don’t sell my data and I can afford it. So from a moral standpoint, I had to pay and I’m happy to.
I chose a $36 ARPA membership. It’s the only subscription that makes sense for me in the higher-tier, since I don’t need any of the features in the more expensive “plans”. But it’s a one-time subscription, so I plan on renewing it next year even if I don’t have to - if I keep using SDF services that is. I don’t have to, but I feel it’s the right thing to do.
Now don’t get me wrong: SDF provides me with a shell and a whole bunch of stuff I haven’t seen offered at anywhere near this price for decades. I was NOT ripped off.
All I’m saying is, when I see users of instances they paid $0 to join - be it Lemmy, Matrix or Peertube - seemingly using their free service without any of the trouble I’m experiencing, it’s not a very good feeling. I know I didn’t pay much, but it kind of stings a bit.
Ah, ok. Sorry. It just sounded like someone sent you a scam link and you didn’t notice that.
I attempted to get SDF’s attention about the issues with this lemmy instance via Mastodon. tl/dr: I got a brief response suggesting I talk to my lemmy app’s developers.
Yeah, that’s not super helpful. I’m using the web client SDF serves, federation is still periodically broken.
@SDF, you either need to stick with the stable version, or this instance is going to be broken. I don’t even know if this is going to reach you.
@SDF, just replying so you can see what’s going on now that we’re back online.
deleted by creator
At this point I’ve made another account elsewhere.
But I wouldn’t mind an SDF Lemmy for members but without federation that focused on SDF themes.
Let’s start a thread keeping track (so we don’t have to do as many test posts). Still out at 24 hours.
Or is there a better way?
4 days, still seems to be down.
Hey, it’s back! At least for Beehaw.
Seems to be broken again.
And it’s back, hopefully for good this time, since there’s been an actual upgrade with bug fix.
Yep. My backup instance (futurology.today) seems to be having a slightly different issue too, which sucks.
SDF’s lemmy instance does not even sync lemmy user profile changes to their own mastodon instance (mastodon.sdf.org).
It’s not still, it’s again. Seems like about 10 hours ago.
Checking the release notes: https://lemmy.ml/post/9347983
The outgoing federation got reworked. So it’s probably not issue of SDF. It seems lemmy.ml might also be having some issues with this at the moment.Hmm okay. I must admit, it’s the first time I hear about this problem happening to other instances. So maybe not a SDF problem after all…
Thanks for the heads-up!
Based on https://github.com/LemmyNet/lemmy/issues/4288 it seems Lemmy 0.19.1-rc.1 might fix this issue.
Oh interesting, 0.19 is finally released, and Lemmy.ml is on it. Probably better for SDF to upgrade now rather than stay on an old release candidate.
