Did I just check lemmy right after the reboot? Good timing huh

Looks like it worked! Thanks for all you do @Ruud!

I sadly couldn't use the web version of lemmy.world at all cause of the websocket issues. 0.18+ is gonna be an amazing upgrade fore this instance! All the devs and staff who made this happen have my undying respect.

Slow, but working.

I don't know if we're slow because of the upgrade, or because of the July rush from Reddit losing 3rd party API access.

Good luck. This is my favorite instance so I will be eagerly awaiting. Lemmy has been incredible and strangely what I needed. I would doom scroll reddit and see the same posts and the same comment chains and just redundancy hell.

Lemmy feels so different and the community is so welcoming. Thanks again everyone for making this lost Redditor a found lemming (is that the correct term lol).

The last few minutes the site seems to be very fast! Let's hope it stays this way!

My lemmy server is also running the same versions are you are now. I was getting timeouts with lemmy.world federation so I recompiled lemmy_server with timeout changes:

diff --git a/crates/utils/src/lib.rs b/crates/utils/src/lib.rs
index e5d07db2c..e2c592d82 100644
***
a/crates/utils/src/lib.rs
+++ b/crates/utils/src/lib.rs
@@ -18,7 +18,7 @@ use std::time::Duration;

 pub type ConnectionId = usize;

-pub const REQWEST_TIMEOUT: Duration = Duration::from_secs(10);
+pub const REQWEST_TIMEOUT: Duration = Duration::from_secs(13);

 #[macro_export]
 macro_rules! location_info {
diff --git a/src/lib.rs b/src/lib.rs
index cc77ca48f..45c621a7c 100644
***
a/src/lib.rs
+++ b/src/lib.rs
@@ -37,7 +37,7 @@ use tracing_subscriber::{filter::Targets, layer::SubscriberExt, Layer, Registry}
 use url::Url;

 /// Max timeout for http requests
-pub(crate) const REQWEST_TIMEOUT: Duration = Duration::from_secs(10);
+pub(crate) const REQWEST_TIMEOUT: Duration = Duration::from_secs(16);

 /// Placing the main function in lib.rs allows other crates to import it and embed Lemmy
 pub async fn start_lemmy_server() -> Result<(), LemmyError> {

Tried to logout, website on mobile won't release my session, and when I tried to login on jerboa it said password incorrect, not sure if that's a ui issue or a lemmy.world issue though

Goodluck and thanks for the effort in all of this guys.

Wow, this is much faster now that caches are built.

Just looked. First 1/2 loads were slow but after that it's lighting fast! I think by not everyone establishing a Websocket connection and just loading once performance should increase a tad bit.

looking good so far, the instance is back, testing to post!

The progressive web app had ui issues after the update so I uninstalled it and now I can't figure out how to reinstall it 😕 tried wefwef but that doesn't load anything and can't log in. Happily staying patient though, hoping things smooth out!

yay, instance is back! trying to post timed out two times, this is the third try.

yay, instance is back! trying to post timed out two times, this is the third try.

Looks like the update is showing, but it's been slow since. Hopefully not permanent. Also having issues upvoting.

Muuuch faster now. Thanks for all the hard work guys!

Working for me currently on connect for Lemmy.

Thanks

Seems to have worked! Typed from Jeboa :)

I hope it works! I'm so over posts just spawning into a page that is already loaded.

Can't login anymore. I'll just use my .ca account for now while things get sorted. Not a big deal. These things take time.