Entrepreneur, developer, seasoned system and network engineer, aspiring hobbyist pilot, husband and father.
Thanks for bringing this to my attention.
I found that there were some changes to the nginx.conf file which can be seen here
it does look like its fixed in the 19.10 version of lemmy. I’ll do another deep dive later tonight to see if we can just update the nginx configuration without upgrading to 19.10 and if its the case will schedule another small maintenance window this week to get it pushed out.
Thank you
Hey!
Everything has been reviewed and we’re good to move over the 19.9. I’ll be posting an announcement in the coming days to give everyone a heads up. I’m aiming towards the end of this week.
I want to say that I’ve been blown away by the amount of support that’s I’ve received in the last 24 hours. You all have left me speechless. Thank you everyone who have donated and those who couldn’t, know that being a good member of this community already more than I could ask for. Thank you!
Hey there, I considered this at first but my understanding with tesseract is that this would mean we’d be proxying account credentials/tokens of other instances. I’m comfortable in doing this for our own instance but it doesn’t feel I’d be being responsible human to enable it for other instances. If there was a way to be more transparent to users using it for external instances I’d reconsider. I’m open to any feedback.
Absolutely. This is exactly why It’s important that we get a donation strategy put into place sooner rather than later.
This is odd. I did not upgrade pictrs (the service responsible for image hosting). There may have been an error for some specific tables rows during the database migrates. Another possibility could have been an error during the schema update that I believe the new version had to go through.
Would you be able to DM me links to other posts that you come across with broken images? I will look to see if I can identify any common trends that could tell us more.
Thank you
We sure are!
It’s coming. This instance is deployed using lemmy-ansible but with some slight modifications. I need to review a few things to make sure the transition is smooth. As you also pointed out, it’s also summer time which isn’t helping with my free time situation.
I have a long term solution that will speed up upgrades but I only expect to get it in place by the fall. In the meanwhile, I’m planning on getting this instance upgraded to 19.5 in the coming weeks.
Hey,
I’m due to make a post about the instances finances soon. I’ll get one posted in the next bit.
I’m still covering costs out of pocket but my goal has been to have this instance fully funded by its members. I want this instance to stay true to its members, the fediverse and be put in a position where it can continue to thrive transparently without me. The admin team has been doing an outstanding job keeping this instance safe and moderated for everyone. I don’t thank them enough but they are the true heroes of this instance.
As some may know, I’ve been working with a local non profit for the past 6 months to have them leveraged in accepting accepting donations for this instance. They have been slow to get things done but its progressing. I may end up doing what I was trying to avoid and create my own non-profit instead if that’s what it takes. That direction does have its own challenges and would add additional responsibilities to my plate.
In the meanwhile, while some of the costs of the services have gone up slightly, I get joy knowing that I can continue providing this instance to all of you. I’m OK paying the costs to keeping the lights on until we can transition to donations.
Yes, I’ll get this done
UPDATE: here you go https://oldsh.itjust.works/
The original rules of lemmy.comfysnug.space explicitly allowed for loli content to be posted. I associate loli content with pedophilia and therefore was the reason why I had defederated with them.
Honestly these type of scat spamming has been really discouraging on me. I spend time and money so that the community can have a reliable and nice instance to call home, only to have a few (not sure what to call them) people try to ruin it for everyone. If these people are reading this comment, just know that every time you make these kinds of unwanted posts you are taking my time away from my family and young kids to address the reports.
My nights lately have been mostly used for coding some extra moderation tools that will moderate these in the future.
I sincerely apologize for all of you who have been exposed to literal shit images over the last week. I’m working as fast as I can and will implement something soon.
In the meanwhile i’ve added a few new admins to help with this moderation.
Hey everyone, woke up this morning with this news. This news really comes at a surprise as I have not seen or heard of any trolling coming from members of this community. I also have not been approached by their admins to see how we could collaborate. In either case, I’ll be attempting to reach out to their admins and discuss a path forward together.
I’ll post an update with the details in the coming days.
Hey icy,
The decision to block the Lemmygrad instance was less a question of censorship, and more an issue of personal conviction. As a volunteer dedicating my personal resources and time to facilitating a space for users to create, discover, and discuss - not just on this instance, but across the Fediverse - I admit that this choice was made alone, selfishly, without the consent or thoroughly considering the collective opinion of the community. With the above said, sh.itjust.works has had the lemmygrad instance blocked from its first day.
I’d like to also point out that the lemmygrad instance has far more blocked instances than what is currently blocked here. Maybe you can create a post on that instance to see what that’s all about and report back?
I’ve went ahead and updated and applied the update to our configuration files. This issue should be sorted now.
Thanks!