Sorry about that. Our hosting provider went down.

At the moment our architecture looks roughly like this:

• Lemmy backed on a OneProvider VPS
• everything else hosted at Fly.io (we heavily rely on the private networking that fly.io provides, they rock!)

In the future, I'm planning on moving Lemmy backend and pictrs to live in my basement. I have a 1 gig symmetric connection with a backup failover, so I honestly think it'll be more reliable than these cheap hosting providers and it will be cheaper.

Just want to give a quick update on what's happened and how we'll fix it going forward!

Hi! I know lemdro.id has been a bit slower than usual lately. I'm working to move us to totally dedicated hardware to mitigate this.

Expect early January, although I will make efforts to speed us up on our existing hosting provider.

Captured these beauties near Olympic National Park

Retrieval of most pictures seems to not be currently working. I am still attempting to understand and resolve this.

Edit: This has been fixed

UPDATE DAY 2: backend has successfully been migrated onto new dedicated hosting after some pain. there should not be major downtime from here on. tomorrow I will be working on integrating a better backup solution and then I'll leave it alone for a little while.

UPDATE: I was able to deploy the database onto dedicated server hardware tonight, but have not finished moving over the other components I wanted to. You may notice a performance degradation due to increased database-backend latency (...or maybe it will just be better anyways, lol).

I will finish off work on this tomorrow!

Lemdro.id has been struggling with some performance issues lately, as you've likely noticed. This is due to changes made by our hosting provider that causes the database to run much slower. Tonight at 10pm PST, I will be putting lemdro.id into maintenance mode to migrate some parts of the infrastructure to a new dedicated server.

Thanks for your patience!

Hey all! I've done a lot of database maintenance work lately and other things to make lemdro.id better. Wanted to give a quick update on what's up and ask for feedback.

For awhile, we were quite a ways behind lemmy.world federation (along with many other instances) due to a technical limitation in lemmy itself that is being worked on. I ended up writing a custom federation buffer that allowed us to process activities more consistently and am happy to say that we are fully caught up with LW and will not have that problem again!

Additionally, on the database side of things, I've setup barman in the cluster to allow for point of time backups. Basically, we can now restore the database to any arbitrary point in time. This is on top of periodic automatic backups which also gets pulled to storage both on my personal NAS as well as a Backblaze bucket (both encrypted of course).

Today, I deployed a new frontend at https://next.lemdro.id/. This one is very early stages and experimental but is being developed by https://lemm.ee/ and seems promising!

If you live outside of the US and experience consistently long load times I want to hear from you! I am deploying the first read replica node to Europe soon, so if you live in that region you'll soon notice near-instaneous loading of content. Very exciting!

Finally, looking for feedback. Is there anything you want to see changed? Please let me know!

Google today announced a handful of wearable and navigation updates, starting with public transit directions in Google Maps for Wear OS.

cross-posted from: https://lemmy.zip/post/10370094

I am rolling out the Photon UI as a replacement to the default lemmy UI right now. Initially, only about 50% of requests will be routed to Photon, determined by a hash of your IP address and user agent (sorry for any inconsistencies...). As I determine that this configuration is stable I will be slowly increasing the percentage until Photon is the new default frontend for lemdro.id.

If you have any difficulties, please reach out. Additionally, the "old" lemmy frontend will remain available at https://l.lemdro.id/

Edit: I am aware of some problems with l.lemdro.id. It wasn't designed to run on a subdomain so I'll need to add a proxy layer to it to redirect requests. A task for tomorrow!

FINAL EDIT: https://l.lemdro.id/ is now fully operational, if you choose to use the old lemmy UI it is available there

Over the course of the last couple weeks, I managed to root cause and solve the problem causing stale sorting on lemdro.id. My apologies!

We typically like Pixel phones a lot, but we have some reservations about Google's quality control

Google Maps is changing with pretty significant redesigns across key surfaces, including when searching for directions...

Edit: Upgrade went off without much of a hitch! Some little tasks left to do but we are now running 0.19.3. Seems like a lot of the federation issues have been solved by this too.

You will have to re-login and 2FA has been reset.

This update is scheduled to take place this weekend. No specific day or time because I am infamously bad at following those. I will try to minimize impact by keeping downtime to lower-traffic periods.

Ideally, there will be no downtime, but if there is it is likely to only last an hour maximum. During this time I will add an "under maintenance" page so you can understand what we are up to.

Feel free to join our Matrix space for more information and ongoing updates! My apologies for how long this took - I was in the middle of a big move and a new job.

Additionally, there may be small periods of increased latency or pictures not loading as I perform maintenance on both the backend database and pictrs server in preparation for this upgrade.

There was a brief (~5 minute) period of downtime on lemdro.id recently. This occurred during a routine database upgrade when some strange issue caused a member of the cluster to become inconsistent and refuse to form quorum.

This locked the entire cluster into an invalid state which took some troubleshooting to fix. My apologies.

I will be rolling out read replicas for folks on the East coast of the US as well as those in Europe sometime in the next week, you should notice a pretty dramatic reduction in latency if you are from those areas. Additionally, other recent changes have increased reliability and decreased latency which may or may not be noticeable.

I will post another update before I start rolling out the read replicas since it is kind of a big change (and I will schedule a time for it)

I recently rolled out an infrastructure upgrade this last Monday (Dec 4) with the intent of reducing peak response times and removing occasional scaling errors.

Unfortunately, my metrics system showed slightly elevated error rates, so I've decided to rollback these changes for now. I will make another announcement before I roll them back out in the future. Thanks for your support!

Hey there everyone. I think the Photon project has matured enough to the point where I feel ready to replace the default lemmy frontend with it. Since this instance serves roughly 1000 people now, I figured this was worth holding a vote on!

Please check out Photon as currently hosted at https://p.lemdro.id/.

If you support changing the default frontend to Photon, upvote my comment on this post. If you don't support it, downvote that same comment.

Thanks!

RIP :(