I'm really not a fan of when features are teased as "coming to Android 14." There is absolutely no shot this gets upstreamed to AOSP.
Reading between the lines in the article, this is going to end up in an update to Google's launcher app, or maybe their wallpaper app. At most, their closed source flavor of SystemUI.
But for the growing number of us compiling AOSP from source and using it to get away from Google's spying, it's disingenuous to keep advertising these features as "coming to Android 14."
Heck - if this feature makes it in any of the apps like I said it might, then there's really no reason to lock it to Android 14. It could easily run on Android 12 and 13. But it won't, because Google wants you to buy a new phone.
Thanks! But I can't take all the credit. Calyx maintains the OTA updater and it's very configurable. Just change the domain name, make sure your webserver has all the right files, and you're off!
Been running CalyxOS for 3 years. Compile it myself from source with some extra tweaks and such. I've even got a nice build server going that automatically compiles builds monthly and pushes updates to my phone via OTAs. It was a little work to get set up, but now it doesn't feel any different from the stock Android experience.
It started because I was tired of all the unchecked spying Google does, and I wanted to get away from that. But now I can never go back to "regular" Android, because the vendor bloat in "stock" ROMs is incessant, and I am maintaining patches for quite a few features Google has either removed, or never supported in the first place (2-button navigation, AM/PM clock, automatic call recording).
Honestly, there hasn't been any drawbacks. The phone works perfectly, calls are fine, it runs great, and I haven't needed Google Play Services for basically anything. My banking app still works. I don't use Google Pay so I don't really care that it doesn't work. Android wearOS doesn't work, but at this point Google has dropped the ball so severely, I don't have the motivation to bother with a smartwatch.
Most of my paid apps continue to work without patches, and I get them from Aurora Store. For the ones that don't work, I just patch them myself to remove the license checks. I paid for them, so I should be able to use them regardless of what ROM I use.
We just need to find a librarian. Then they can access the secret network of librarians and ask about this story. We'll know what the tale was within 2 hours.
Just FYI, you could save about $5 a month and get 2x the performance if you moved that to a VPS not on AWS. $11 a month for t2.micro, especially if it's locking up, is basically you being scammed if I'm being honest 😅
AWS isn't really designed for long running tasks like this unless you get a long term commitment discount. It's intended for enterprises and priced that way. For a hobbyist like you, I'd definitely recommend Vultr or something.
Also, be careful about those bandwidth costs. Most of the time it's never free to serve data out like that. You may not be using a load balancer, but double check those bandwidth costs, I remember something about paying for bandwidth I didn't expect.
Definitely consider moving to a $5 or $10 instance on Vultr, they have block storage too. You could either save money, or spend the same for 3-4x the performance.
Yeah, I meant the comments that have been hidden previously made it seem like clearing it would be an issue, so I hesitated to clear it. Now that those comments have been edited, it looks like it won't break anything after all.
By the way, how are your costs on EC2? My understanding is that hosting on EC2 would be cost prohibitive from data transfer costs alone, not to mention their monthly rates for instances are pretty much always below the cost of a VPS.
Now if only someone could do this for the Postgres data. I wonder if S3FS would be able to handle the load of a running database, that would be a nice way to save costs.
I saw that issue, and then I saw people having problems after clearing it, so I'm just going to wait until they figure that out in a stable version. Looking forward to it though!
Pictrs 0.4 recently added support for object storage. This is fantastic, because object storage is dirt cheap compared to traditional block storage (like a VM filesystem). This helps a lot for image storage, which is a large part of the problem, but it's not the whole problem.
I know Lemmy uses Postgres for everything else, but they should really invest time into moving towards something more sustainable for long term/permanent hosting. Paid Postgres services are obscenely upcharged and prohibitively expensive, so that's not an option.
I'm armchair architecting here so I'm not sure what that would look like for Lemmy (Cloudflare KV? Redis?)
Still, even my own private instance has been growing at a rate of about 700MB per day, and I don't even subscribe to that many things. I can't imagine what the major instances are dealing with. This isn't sustainable unless we want to start purging old data, which will kill Lemmy long term.
EDIT: Turns out ~90% of my Lemmy data is just for debugging and not needed:
Where? If I click on my profile I only see messages I've posted.
Oh, it's the bell at the top left, I had no idea. Kinda the same ambiguous UX as on Lemmy, would be nice if it had a dedicated inbox tab on the bottom.
If you're not already, I recommend trying to host this on a cloud VPS service, such as Vultr, Linode, or DigitalOcean. This would give you a reliable, always online Lemmy instance, which means you won't miss any federation data. Even a cheap $5 VPS instance would be enough to get you started, though a $10 would give you more breathing room.
If you're hosting at home, it's generally not a good idea to do that, especially for an application like Lemmy. Most consumer grade network equipment at home might not be equipped to deal with the unrelenting 24/7 flood of data coming in due to federation. And if your power or internet ever goes out, you will be missing any comments, posts, or votes that were sent out during your downtime.
Hey there, please note that running behind a reverse proxy is not supported. You can do it if you want, but you are kinda on your own, sorry.
If it helps, you will probably need to disable Caddy's TLS in the config, and you will need to make sure that the request reaches Caddy via the correct host. You can't reverse proxy directly to port 80 over an IP, it needs to think it's coming from an actual domain.
You can also check out my advanced configuration page to learn how to override the Caddyfile template and roll your own config that is more compatible for your use case.
ubergeek77 @ ubergeek77 @lemmy.ubergeek77.chat Posts 3Comments 168Joined 2 yr. ago
Use pict-rs, it's what Lemmy uses for image storage, it supports MP4s and GIFs too:
https://git.asonix.dog/asonix/pict-rs