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.
Federation is the process that pulls content in from other servers (e.g. lemmy.world, beehaw.org, fedia.io, mastodon.social, etc.) All of these different servers can communicate and share content with each other.
If you turn federation off, you only see content from your "home" server, which in your case is kbin.social (in mine it's remy.city).
Well said, thanks for this info! I was in the camp of thinking "of course the money goes to Wikipedia's upkeep" but I never examined it closely enough.
There are ways to write links in such a way that they should keep you on your instance, but I'm not too familiar with them. I wonder if it would be possible to "precheck" links that load on a page, and if any point to content that can be federated, kick off the process of pulling that content in. Then when the user clicks that link, it would take them to the content on their home instance, where they can interact. That way users wouldn't need to deal with formatting links a certain way, it would just happen automatically (if your home instance software supports it).
That's the one--thanks!
The thing about federation is that every server basically copies any content that the users on it want to see. So if a comment/post is made on lemmy.world, lemmy.world sends out an update to every other server on which a user is subscribed to the thread/community/user. So each instance that has a subscribed user ends up having to process the new comment/post. If a Meta community came in with say, a million users, now every instance has to process the comments for all those users (that is, if folks on those instances want to see that Meta content).
It is a bit inefficient, but it's just the way a decentralized network has to function. I could see many people thinking that any time you open a thread, the data comes in from the originating instance, i.e. that your home instance doesn't store the data you are viewing. It is unfortunately, and I think it will be a problem in the future as communities grow.
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