[-] cole 3 points 7 hours ago

your links are broken I think

[-] cole 1 points 3 days ago

Your submission, "Is there any solution available for controlling the volume without pressing the physical volume buttons ?" was removed for Rule 2: post these in !askandroid@lemdro.id.

[-] cole 2 points 4 days ago

do you really think that Hamas would stop launching rockets if Israel stopped intercepting them?

[-] cole 3 points 4 days ago

anybody gotten the find my device prompt yet? I'd like to enable that option to track my phone even when it runs out of battery. seems useful

[-] cole 2 points 5 days ago

Currently tracking this issue. I restarted the pictrs server for now which might fix the issue. Our pictrs is backed by S3 object storage which is effectively infinite. Additionally the pictrs database definitely has not run out of room, the root vol is only 822MB/3GB.

I'll look into this more this evening after work if it is still not resolved!

[-] cole 3 points 5 days ago

I actually run the infrastructure. Our pictrs is backed by S3 object storage so it should not be possible to run out of space. I'll have a look this evening

31
submitted 2 weeks ago* (last edited 2 weeks ago) by cole to c/lemdroid

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!

109
submitted 2 months ago by cole to c/android

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

71
submitted 2 months ago by cole to c/android
19
submitted 2 months ago* (last edited 2 months ago) by cole to c/lemdroid

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

9
submitted 2 months ago by cole to c/lemdroid

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!

95
submitted 3 months ago by cole to c/android

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

61
submitted 3 months ago by cole to c/android

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

16
submitted 3 months ago* (last edited 3 months ago) by cole to c/lemdroid

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.

[-] cole 41 points 4 months ago* (last edited 4 months ago)

Basically, the lemmy backend service for some reason marked every instance we federated with as inactive, which caused it to stop outbound federation with basically everyone. I have a few working theories on why, but not fully sure yet.

TL;DR lemmy bug, required manual database intervention to fix

This was a stressful start to a vacation!

For a more detailed working theory...

I've been doing a lot of infrastructure upgrades lately. Lemdro.id runs on a ton of containerized services that scale horizontally for each part of the stack globally and according to load. It's pretty cool. But my theory is that since the backend schedules inactive checking for 24 hours from when it starts that it simply was being restarted (upgraded) before it had a chance to check activity until it was too late.

theory:

  • scheduled task checks instances every 24 hours

  • I updated (restarted it) more than every 24 hours

  • it never had a chance to run the check

  • ???

  • failure

This isn't really a great design for inactivity checking and I'll be submitting a pull request to fix it.

8
Recent Downtime (self.lemdroid)
submitted 5 months ago* (last edited 5 months ago) by cole to c/lemdroid

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)

3
submitted 5 months ago by cole to c/lemdroid

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!

15
submitted 6 months ago by cole to c/googlepixel
[-] cole 33 points 7 months ago

this might be an improvement

[-] cole 26 points 7 months ago* (last edited 7 months ago)

If you support changing the default frontend to Photon, upvote this comment! If you don't support it, downvote this comment!

27
submitted 7 months ago* (last edited 7 months ago) by cole to c/lemdroid

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!

[-] cole 19 points 8 months ago

Freesync yes, HDR soon™

[-] cole 20 points 10 months ago

sure! take a look at this issue: https://github.com/LemmyNet/lemmy-ansible/issues/106

It is likely yours is fixed if you deployed recently

[-] cole 89 points 10 months ago* (last edited 10 months ago)

Edit: A fix has been deployed, and federation should work now. Unfortunately, kbin.social is taking its sweet time federating with us, it is probably overloaded. Lemdro.id is already accessible from other kbin instances such as fedia.io (https://fedia.io/m/android@lemdro.id)

Hello! Admin here at lemdro.id. This is the result of several problems in the lemmy default reference nginx config. I am working on resolving this right now and should have it fixed within the next 30 minutes!

view more: next ›

cole

joined 10 months ago
MODERATOR OF