It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
No need to create an issue, it’s a BE (backend) bug, fixed in 0.18.4, but our instance admins haven’t update to the latest BE version 🤷.
It’s not a Jerboa bug, it’s a BE bug, confirmed a few posts below. Lemmy.ml should be on 0.18.4, so should lemmy.dbzer0.com.
Yeah, that should be super easy, since In don’t speak any German 😒.
Nevertheless, I’ll try and see if they reply.
BE of my instance: 0.18.3.
0.0.42… that’s the version in the About section.
BE of my instance?
I’ll create one 👍. Just need more confirmations, a few more replies should do it.
Might be a SAS driver issue. Have you checked if the drives show up on a live distro, something more current, like let’s say Void or anything that has a 6.x kernel?
I’ve had issues like this with older Marvel SCSI controllers, some of them don’t have open source drivers for Linux, and the ones provided by the manufacturer (if there are any) are so old that you’d have to be runnig kernel 2.x in order for them to work. I just gave up in the end, disabled the SCSI controller in BIOS and just used the rigs on IDE/SATA.
I usually use 7z as well… mostly because of the higher compression ratio. I resend in zip if I get complaints, but if it’s a large file that barely fits in size on whatever hosting service I decide to share the file on, I just tell them to install 7zip or any other archiver that can open 7z archives. If they don’t how to do it, hey I also offer remote IT assistance 🤷.
Discovery is never gonna work on the fediverse. Info is too scattered. Sure, large servers will get discovered, but not smaller ones. They come and go, URLs change… it’s a mess.
You delete comments here as well?
Oh, yeah, makes sence in that case. Thought it was some other general information, like troubleshooting info.
I can get behind stuff like this, sure, but not with stuff like I posted 😒. There was valuable info there that could’ve solved my problem in an instant, but I just had to go the long way around 😒.
Could I ask why you would delete your own comments after a week of two?
I managed to get pointed in the right direction, but no thanks to that user 😒.
Doesn’t matter, I have no idea who the user is.
I did… zero replies 😒. And I asked on reddit as well. Didn’t get an exact answer, but at least I got pointed in the right direction.
Not affect anyone, it will affect search engines… but, not much nore than that.
And the protests proved inaffective, as I initially thought and said to many, just move, no need to protest, just leave for Lemmy and leave your accounts. That was all that was needed and no protest in the world is gonna beat reddit or the admins that will just overried your NSFW settings. Leaving the platform says way more than protesting this or that.
And no, if the point of the protest was to just delete all info from reddit, then I would’ve never been behind that protest. The delete everything idea was promoted by some extreme protesters and unfortunatelly, some users went allong with that.
That’s not the point… it was eight there… right there, no need to dig deeper… and it wasn’t like a 30GB bluray rip went missing, it was just a few lines of text, a few very valuable lines of text… but no, some people thought it’s more imoortant to protest than the freedom of information 😒… info that they once shared BTW, no one forced them to do it, but no, some of the protesters thought it was a good idea yo delete all of the content and their accounts… please explain how this is a good idea.
Didn’t know where to put it… just thought might pass as a meme…
It’s a BE (backend) bug. Our instance admins need to update the BE to version 0.18.4.