What the fuck? Why? Why block Blahaj of all instances? That really doesn't inspire confidence in this server or SDF.
I can understand blocking instances like lemmygrad or hexbear, but blahaj? Seriously? Why?
I'm glad they reversed it, but why was it done in the first place?
@SDF@lemmy.sdf.org Can you please explain? I really want to know the reasoning behind such a decision to block specifically lemmy.blahaj.zone, was it a bug with something automated? Something prompted by suspicious behavior from them? Please explain.
If you don't want to explain publicly you may shoot me a message at matrix or to my SDF email. I just want to know.
We is members of SDF, and I don't really believe that. But even if it were true. If their only merit to creating this instance is to have it be public facing without any of the anti-spam benefits of being SDF-Member only, then it probably isn't worth it.
After all their public Mastodon server mastodon.sdf.org has many upkeep issues and they don't seem to care much about it. Social.sdf.org is well taken care of, because it's made specifically for SDF members.
This instance should be given the same amount of care and attention that social.sdf.org is but the only way that's worth it is if they can be sure most people there are validated and trusted members.
It's very easy, you just register on the website and login to the TTY using your preferred SSH shell. Can be Termux, can be Putty, can be a Web SSH, doesn't really matter. It does require Shell access though.
To be Validated you need to Send at least $1 or €5 to SDF with your shell username written on the envelope or included in the transaction in some way. So yeah there is a membership fee but it's very cheap.
If they make the Instance SDF memeber-only that doesn't prevent people from joining or make it that less public. Anyone can become an SDF member, $1 or €5 to join is very reasonable and likely something anyone can afford if they want to, it's an inconvenience enough to deter spammers and assholes though.
I think it very likely was, similar to how mastodon.sdf.org was largely an afterthought. I say that because that server has had many maintenance issues in the past and I've seen people complaining about it while nothing gets done. Part of the reason I joined social.sdf.org instead.
Hell they managed to keep social.sdf.org up even when there was a power outage. They clearly care about that one a lot. Not Lemmy or the general Mastodon one though. These are just an afterthought because someone at SDF thought it would be really cool to get into the Fediverse.
One idea I had would be that they could require accounts to have SDF emails, that would basically require people to have Validated TTY accounts, I believe social.sdf.org does this. They could also accomplish the same thing by closing registration completely and having it be solely managed via the Maint command in the TTY shell.
I agree, they should freeze registration until they can get more people to volunteer to manage it, that is updates, maintenance, and especially moderation.
I've never done maintenance or updates on a Lemmy server and I wouldn't trust myself with something so dangerous, but I have done moderation and I would be happy to volunteer to help out in any way I could.
Another thing that could help is to make the instance SDF member only, by requiring the use of SDF email, or having your account be managed by the maint command in the Shell login.
I agree, this is stupid. Why should we settle for a server where the admin won't even apply updates on time or fix bugs in a timely manner. Let alone moderate their instance properly.
I barely even use this instance and I'm really only here for !sdfmc@lemmy.sdf.org, I couldn't imagine how much it would suck if this was my only account or only instance to access Lemmy from.
Edit: Glad to see they've been banned. Though it honestly doesn't really change much in my opinion if something doesn't seriously change when it comes to the instance management.
I agree, definitely a good time to start talking to instance admins about defederation, because even if they do address the problem at this point unless they can give assurances change will be made this WILL happen again, it's only a matter of time, and two days to squash out a neonazi troll is absolutely unacceptable.
Oh yeah it's not actually a big problem for me to access other things. It's more an issue that people won't be able to access the SDF Minecraft community anymore, and the communities already here will likely be toast as well.
I'd also be glad to help out too. Unfortunately we'd need the current Admins of SDF to get up off their ass and tend to the server that they're supposed to be managing and taking care of.
I mainly use SDF because of the services provided, specifically the MC server, though I admit I haven't been super active there lately. The culture here is also usually very nice. It's a shame this happened, and that the admins are just not here to fix the issue.
I wasn't able to do that even, Firefox with HSTS is dumb and goes against user freedom by failing to give a meaningful bypass method. Though I was able to get around it.
FYI people won't tell you how to disable HSTS enforcement, just delete the contents of the file SiteSecurityServiceState.txt then set permissions of it to read only and owned by root for good measure. Then the unbypassable warnings are able to be bypassed same as any other http warning on an https site.
There has been a recent uptick in new sign ups, so we'd like to get
in touch and welcome you as well as provide updates to existing
members.
Currently, the lemmy instance is running v0.18.5 and we're watching
0.19.x beta efforts. We do have testing on a smaller instance and
once there is a formal release, we plan to upgrade lemmy.sdf.org
For those who have set up 2FA there has been a reported issue where
a user can get "locked out" from their account. If you are in this
situation, please reply to this message from the email address you
signed up with and we can get you reset.
During the Summer there was a large "reddit exodus" and lots of folks
signed up with new instances. However, many of those instances have
either have become ghost towns or have disappeared all together.
We want to assure you that lemmy.sdf.org as well as our regional
instances are in for the long haul. SDF.ORG is celebrating 36 years
as a non-commercial community resource this year.
While financial support is not necessary, if you do wish to support
our efforts, please consider our "Not a Blue Checkmark Club" which
can be joined at https://sdf.org/support
If you have any issues or feedback, please get in touch and we'll
help you out as soon as possible.
Still seems very sudden to update the main instance to 0.19 considering there hasn't been a formal release and it is still very buggy as @GenderNeutralBro@lemmy.sdf.org pointed out the Instance block feature isn't even functional, but more importantly almost none of the Apps out there actually work with this version.
Also broke the inbox on desktop, was showing empty for me even though it shows the notifications. I had to manually go to the thread to see this message (lucky I keep tabs open).
I agree that this unannounced upgrade is quite the shock to the system and also lemmy 0.19 hasn't even officially dropped yet so it seems kind of strange to update to it now.
What the fuck? Why? Why block Blahaj of all instances? That really doesn't inspire confidence in this server or SDF. I can understand blocking instances like lemmygrad or hexbear, but blahaj? Seriously? Why?
I'm glad they reversed it, but why was it done in the first place?
@SDF@lemmy.sdf.org Can you please explain? I really want to know the reasoning behind such a decision to block specifically lemmy.blahaj.zone, was it a bug with something automated? Something prompted by suspicious behavior from them? Please explain.
If you don't want to explain publicly you may shoot me a message at matrix or to my SDF email. I just want to know.