I have deployed some significant upgrades and performance improvements under the hood — and ideally, you should not notice anything.
If something's weird, tweet!
To everyone affected lately - we're so sorry, we're not sure why some users were affected and others weren't. Plus, there have not been recent changes to that component that explain the issue 😖
Hi. There was an issue causing 500 errors for some users that had configured custom timezones.
We have reset everyone to use UTC to temporarily fix the issue, and will be working on a permanent fix over the coming days.
@juzzle that's strange! it should be nearly indefinite. Are you opening session in several computers at once? (hence flip-flopping, maybe? but it still shoudn't)
📢 showRSS update!
We just migrated to a new server with more cores & NVMe storage, so the website should hopefully feel snappier.
As with all migrations, things can go wrong. Please reach out if you find something strange.
@richat 419 generally happens because the user is not browsing through https, but the login should limit that. I'll look into it. Meanwhile please try here: https://t.co/kCy1zYK6bQ
📢 showRSS update!
We just migrated to a new server with more cores & NVMe storage, so the website should hopefully feel snappier.
As with all migrations, things can go wrong. Please reach out if you find something strange.