If by “down” you mean completely down, it’s probably just you; I don’t think I’ve ever seen a failure that didn’t go away after refresh.
Flakiness for specific features (often subscribe/block, and once notifications) have been more common.
I’m on here way too much during the work day and haven’t noticed any problems
okay interesting… a few days ago, for me, it showed the UI but no posts and said there was an error for like an hour; and a few hours ago my browser said that the website had no valid SSL certificate
hm. that’s very strange… you shouldn’t be getting those errors. we haven’t had any downtime longer than a few minutes. One thing that does seem to be happening is that moderator actions on ‘big items’ like banning a user, or removing all their posts seems to completely lock up the lemmy instance. It pegs the CPU at 100% and prevents all backend operations. No clue why. But I haven’t heard about this ‘no posts’ or errors like you are talking about. Can you send us a picture either here or in one of the other communication mediums (discord, matrix, mastodon) when you get an error again?
Damn, I presume there’s a GitHub issue open for that lockup problem… that’s pretty serious.
What is your local system clock; 16 seconds behind your NTP server? That, or OP just has a similarly inverted clock skew.
I guess OP could be posting from the future. Hey @akrz@programming.dev , what is the closing price of SMP 500 tomorrow? :P
It’s still early days and the devs are constantly working through bugs, server load from new users, and recently hacking attempts. It’ll take some time to be stable as any new project does.
Companies like Meta can build Threads in a more stable initial release because they already have the infrastructure and money to build out capacity. They can also reuse stable internal code that has had years of testing/improvements. But then you’re trading your privacy.
