lml

At least you got yourself into the contributing mindset. Tackle the next issue!

Don't they know not to use the window-git AUR package? It's a development build and could be unstable/unsafe.

Fawn-Napping (but not the kind this guy did) is a real problem affecting many small deer friends every year. https://www.wildlifecenter.org/baby-deer

I think that would be worth it, yeah. Of course if you are hosting it on your home network there will be some added security concerns (and that might make it better to only allow signups to friends/friends of friends/etc). The way I see it is that some instances are going to host the largest communities, and therefore those instances are going to need to handle all of the incoming/outgoing updates to posts in those communities. Right now they can't do that reliably and push updates out to all of their users' devices.

So in the long run I think having small/medium instances (say a couple hundred, not tens of thousands of users) will be the way to grow. These smaller communities can push updates to their smaller user count reliably, and then have more resources to handle federated content coming in and going out. I think scaling for the incoming/outgoing federation requests would be easier than for direct user activity. Federation stuff can be queued and then spread over time, but user requests cannot be.

Good point. Nothing against the larger instance owners of course. If my little instance got super popular somehow (like being recommended in guides on how to join lemmy/kbin), and thousands of users got in per day, I could see issues happening just like this. I don't know the ins and outs of tuning this software for performance at scale, and I know I couldn't learn it fast enough if my instance faced very fast growth like lemmy.world has.

I think admins are going to need to turn registrations off periodically, as they scale their hardware (and their knowledge) to run it for more users effectively.

This is the problem we are having with fast growth on a few select communities. The largest servers are being bogged down simply because the software has not been tuned for these large types of instances yet. ActivityPub works best (in it's current state) by spreading users over smaller/medium sized instances. Folks need to take a look at other instances (and I agree it is hard to find them for a newcomer). You can look at https://fedidb.org/ to look at instances that have been indexed running kbin, lemmy, and other software.

Joining a smaller instance means that your server is not being bogged down by tens of thousands of other users trying to pull updates at the same time. You can still see the content from other instances, and in many cases it is more reliable because your smaller instance actually has the resources to handle pulling in the posts you want to see. In the future I am sure instances like lemmy.world will be able to handle the traffic smoothly, but for now the best way to ensure stability is to join a smaller instance.

(Plug for my instance: https://remy.city, a general purpose Kbin instance. I set it up for personal use but anyone is free to join me in using it. I have defederated from the more alt-right communities like lemmygrad and exploding-heads, and from lemmynsfw.com because of content hosting concerns. I'm open to suggestions on others.)

Bummer. Yeah, I think kbin.social hasn't gotten those changes added in yet. I've just been pulling the new updates once/twice a day onto my instance. It has broken things a couple times though so I get why the larger instances are waiting for actual 'releases' of kbin.

In your browser, if you go into the menu there should be something like 'Install', 'Add to Homescreen', something like that.

On chrome it is add to homescreen, but there is also a pop-up at the bottom that gives an install button. The browser menu should be the easiest spot though.

It creates a shortcut on your homescreen and allows the site to run in full screen mode, so it acts like a native app.

Looks like that's been fixed actually (if your instance is up to date enough, that was merged in 5 hours ago). I had to reinstall the PWA for it to take effect.

That might be android only, I'm not sure. I remember seeing a pull request about it having to do with something in the PWA manifest.

That'll be slick!

Thanks for the great work on this @ernest, and every contributor who's dove in and made a PR.