

Hey all,
I am very well aware of the slowness and timeouts that people are experiencing. I’m working on getting a few upgrade put into place to bring things back to where they need to be. Thanks for the patience!
Entrepreneur, developer, seasoned system and network engineer, aspiring hobbyist pilot, husband and father.


Hey all,
I am very well aware of the slowness and timeouts that people are experiencing. I’m working on getting a few upgrade put into place to bring things back to where they need to be. Thanks for the patience!


I plan on making a post to share all this information and more in the following weeks.
Thank you for your thoughtfulness and consideration!


I’ve been considering running it in parallel to a lemmy instance but it comes down to a few things:


This issue appears to have been fixed. Can anyone confirm whether they are still having any problems?


Hey all, I’m travelling at the moment but have been in discussions with the other admins about this issue. I return Friday oct 31st and will schedule to get us upgraded to 0.19.13 shortly after. I won’t be giving the typical 5 day official notice to not create any extra delays. The upgrade to 0.19.13 is minor and shouldn’t take us too long to run. Thank you for being patient.


Hi there,
We are not blocking any IP ranges. The server has had an increase in traffic over the last few months. I’m in the process of identifying new hardware to buy to make things speedy again.
I have cycled the services to see if that helps.
Let me know if things get better for you.


I’ve went ahead and updated and applied the update to our configuration files. This issue should be sorted now.
Thanks!


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 a 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.
edit: typo


There was a little hiccup this morning unrelated to the migration tonight. The Lemmy services like to be restarted every once in a while. Once we move to the new hardware I’ll be able to look into implementing a better logging system and hopefully be more proactive when situations like these happen.


The biggest consumer of storage on this instance is related to the image hosting which we use an external object storage provider for. The second is the database which is no were near the 2TB capacity. 1TB SSDs are cheaper than 2TB SSDs and I also didn’t want to spend more than I needed. As other mentioned if we need more space or IOPs in the future, I could accomplish this by adding more drives as a quick fix. This server does not support NVME unless I leverage its PCIe ports but I don’t plan on doing that. By the time this instance gets to the point where 10 SSD drives just isn’t cutting it anymore I’ll probably have come across another opportunities on getting a new server with better NVME support.


Hey all, I’m always excited to upgrade to the latest versions that become available. Unless the upgrade is related to security I will tend to wait a few days to give other instances a chance to share their experiences. Before upgrading I usually go over the issues that have been submitted to help understand the risks and solutions to mitigate them.
That being said the new version does bring in a whole bunch of performance gains (mostly related to the database) that i’m looking forward to.
Lemmy.world is due to upgrade later today and I plan on upgrading shortly after them (either Monday or Tuesday).
I will put up a notification up prior to the upgrade.
Thanks


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.


The vulnerability appeared to be from a custom emoji that they were running. SJW does not use any custom emoji so we should not be affected. In either case lemmy.world has now been restored and is back online. I’ll keep an extra eye on this instance until the patch gets released shortly.


This is a topic that i’ve been meaning to start a discussion about but haven’t had a chance due to the level of detail i’d like to provide.
I will also be posting the current logic of how vote counts are counted and also publish the code that i use for the counting.
Without going too much into detail today when votes are counted theres a few things that the logic accounts for.
In the future, and this is the part i’d like to discuss more in detail on another thread, is whether we factor in someone’s reputation. Lemmy currently collects a post and comment score for every user. This score is essentially = to how many upvotes your post or comments have gotten. Additionally the number of post and comments also get tracked. I’d like to see if there would be a method to use this data in order to determine if an account should have the ability to vote. This does alienate the lurkers but they don’t typically vote anyway unless its something that could affect them.
When I have some extra time i’ll post a detailed post on this so that those of you who have an overachiever mindset can provide your 2 cents.


Hi Nahvi.
Thanks for posting this well put together post. I can tell that you put some time and thought into this and I want you to know that I recognize that.
Regarding your concern, this is a topic that has been brought up numerous times over the past month. I’ve since moved towards being more community driven, letting users discuss and debate on topics that are important to them. These discussion move forward towards a vote over a 7 day period. This process will change over time as we come across flaws and look for ways solve them together.
One more thing I want to make clear regarding your tl;dr question Will I be blocking other instances for personal reasons? Short answer is no, I believe the community should determine what should or should not be blocked.
That being said I want to make myself clear that there are limitations, I will continue to defederate instances that openly promote or spreads hate speech, terrorism, CP, loli, trolling and instances that become bot instances. These shouldn’t be things that need to be justified, I think they fall under the “be a good human” category.
I hope this clarifies your concerns and you continue to make sh.itjust.works your home.


This issue has been resolved.
We have not upgraded yet but will be pushing the update this week.