Kubernetes uses cri-o nowadays. If you're using kubernetes with the intent of exposing your docker sockets to your workloads, that's just asking for all sorts of fun, hard to debug trouble. It's best to not tie yourself to your k8s clusters underlying implementation, you just get a lot more portability since most cloud providers won't even let you do that if you're managed.
If you want something more akin to how kubernetes does it, there's always nerdctl on top of the containerd interface. However nerdctl isn't really intended to be used as anything other than a debug tool for the containerd maintainers.
Not to mention podman can just launch kubernetes workloads locally a.la. docker compose now.
In various parts of the bible, unborn children range from being an object owned by the father to which any damage to the goods must be repaid with currency; to God himself aborting them.
The thing is though, the instance your create a community from only really affects who you interact with to recover your moderation team if everyone goes poof. Otherwise the instance essentially serves as a vanity domain for the community (think email). It doesn't matter if lemmy.world is down to me at all. I can still post to its cats community using my sh.itjust.works account just fine. Anyone that isn't on beehaw will see my posts with or without the origin instance of the community being online (because beehaw is defederated with my instance).
From the 2 developers and The volunteers... The same can be asked about a lot of foss software. Typically what stabilizes foss development though is when developers start getting paid to contribute to the project by a company they work for, however lots of foss software has made it purely through donations (easiest example being mediawiki and wikipedia)
Web hosting is definitely the harder question. In the grand scheme of things, lemmy instances and other fediverse tech will likely end up being pseudo-centralized with a handful of companies like email. Lemmy is very resource intensive as you guessed. The good news is that a very large amount of that resource consumption is storage, and storage is cheap. Though I know I've seen tehdude, the owner of the sh.itjust.works instance, another very stable one, comment on how CPU, networking and memory intensive a busy instance can get. A lot of the early 500s instances were seeing were definitely caused by resource constraints.
Google has a proven track record of being very insecure. Obviously if they implement this standard we should just implement the API on all of our sites to have it only block people using chrome, chromeos or a pixel device and purple who directed to or sites via a Google search.
You actually can, you just append @lemmy.world to the community name when accessing from another instance that's federated with lemmy.world and once lemmy.world comes back up your contributions will be there. Any instance that's federated with the instance your posting from will be able to participate in the discussion with you for that matter. The only thing you can't do with a community when the host instance is down is subscribe to it. It would still get added to your subscriptions though if you try, the hosting insurance just won't know until it comes back up and eats through the outboxes of federated instances to "catch up".
Edit
When it does come back up it'll also get any messages that are in federated outboxes as well so your posts will ultimately show up on the host instance, just posted by your alt account
Depends a little on what instance you're from. For example people from the one I'm on are sh.itheads. Besides that I've heard lemmings for lemmy and fedizens for the greater fediverse a lot. I've also heard karabiner for kbin users.
This happens because a lot of ordering systems default to ticketing teas as sweet tea and iced tea instead of something sane like sweet tea and unsweet tea
In the simplest models the bulk of wind is mostly caused by two major factors. The sun heating parts of the earth's atmosphere creating high pressure zones and the Earth's rotation displacing air.
The only observable effects we'd see in the conceivable future are that scaling wind energy utilization would decrease the effectivity of other technologies that rely on wind vs such as sails or wind turbines, as wind turbines locally disrupt airflow patterns.
The larger environmental cost of them like many green energy solutions would be the materials used in their manufacturing and the energy spent to haul them to their site of deployment.
I had a similar issue, but mine was caused by having a vlemmy account logged in on the app alongside others. Looks like if an instance closes it can freeze loading content from all other instances. This is probably a bit of a bug.
lutillian @ lutillian @sh.itjust.works Posts 0Comments 74Joined 2 yr. ago
Kubernetes uses cri-o nowadays. If you're using kubernetes with the intent of exposing your docker sockets to your workloads, that's just asking for all sorts of fun, hard to debug trouble. It's best to not tie yourself to your k8s clusters underlying implementation, you just get a lot more portability since most cloud providers won't even let you do that if you're managed.
If you want something more akin to how kubernetes does it, there's always nerdctl on top of the containerd interface. However nerdctl isn't really intended to be used as anything other than a debug tool for the containerd maintainers.
Not to mention podman can just launch kubernetes workloads locally a.la. docker compose now.