It's actually a standard called a Progressive Web App that's been around a while, but not often used. there was a post earlier discussing it as well.
Jamie
joined 2 years ago
After almost 24 hours, coming up on 662MB of images, and 371MB for the postegres database. Though, I could see the numbers fluctuating depending on how much stuff you're subscribed to. I'm currently subscribed to 31 communities, most of them fairly large.
My Lemmy instance is currently occupying about 350MB of RAM, but you can round that up to 400MB. A lot less than the 4GB for KBin.Technically it's a dual user instance now, since a friend wanted to join it and I said sure.
Mine still has 4 videos per row on my 1080p monitor. Maybe you got forcibly opped into a test? Did you make sure that you weren't zoomed in or anything?
I was starting to sweat a little because my instance, that only I use, already has 600MB of pictures after less than 24 hours. The server has more than enough space, but I still wouldn't like it. A week is far more swallow-able.
Nah, it's really topical and helps ease people into the community by having common ground to start off on. Plus, it's cathartic to slam them in a place where they have no power.
The thing he really talks about caring about is preventing LLMs from getting his data and using it to provide answers that reduce traffic to Reddit. Except LLMs weren't purely trained on Reddit, and the high majority of the internet where the training data did come from doesn't have a convenient API... so that makes it a little harder, I guess, but it really has no effect.
Then other times, he complains about the advertising revenue, but contradicts himself and says actually the 3rd party app userbase is 3% of all users and inconsequential but people just want to bandwagon the poor multi-hundred million dollar company. Yet it's such a big opportunity cost that can't be ignored and there's just no better way.
I can completely understand why that wouldn't be, it would put a big strain on any server with a large community count.
I think the top 25-100 communities could be reasonable, though. This could also be accomplished with a bot either managed by an instance interested in pulling that data, or a user wanting to automate subscriptions a bit.
*I originally posted this with an example that I immediately realized was incorrect, so I corrected that.
The 150MB metric was based on the documentation estimate. I would say that remains correct for my solo instance. The only caveat would be that postegres adds, at current, about 200MB of usage on top of that. Nginx and postfix add just about nothing memory-wise.
This may bloat up over time, or if I had a bunch of users I'm certain it would, but we're not really talking about hosting large communities in this case, so I'd say 512MB of RAM with no other software could probably do the trick as a bare minimum. For those hosting proper communities, 100% future proof and go bigger than that.
Are you talking about getting a list for yourself, or doing it in a federated way? Because for an individual instance, you can go to Explore Communities -> All to view the most popular communities for that instance, or click the local tab for only communities that they host.
I found a lot of my communities (including this one!) through Lemmy Explorer which aggregates it a bit.
I didn't mention the install process in my case, because the box I installed on already had Apache, which conflicted with nginx, and I couldn't get an equivelant apache config working correctly. So in my case, it took extra steps where I migrated everything from apache to nginx on the box, and stopped using apache. But I did the install using ansible to connect from my PC to the server, and the install process itself wasn't bad. Copy pasted the config files and made a few relevant changes like DB password, instance name, default admin credentials, and pointing to my existing SMTP mail service. For a personal instance, you could probably exclude that last step though. I already host email for my domain, so the effort to do the extra and make it work was miniscule.
After the config changes, I just put things where the lemmy-ansible repo asked, and ran it as directed. Aside from a few screwups on my part, which were mostly because I was trying to see if I could make Apache work, the install wasn't too bad. Ansible did the heavy lifting, and if I was installing on a fresh server, I have little doubt it would have given me trouble at all.
If you ever decide to go through with trying, feel free to reach out to me. I'll be happy to help as much as I can.
The arguments for are varied. I don't have to worry about any admins making decisions on federation, I can federate (or not) however I please. I have my own space that I can do what I want with in a familiar format, and I can make my username Jamie without it being taken.