• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • Still has a lot of the same underlying issues discord has. It’s not indexable being the biggest. The reality is that services like stack overflow or an issue tracker like bugzilla, or your local git services issues section or discussion section, hell even something like discourse or even mailing lists, just work better. If someone made an im service that could be indexed by search engines and the like, now we’d be talking. Opensorce design and discussion doesn’t really benefit that much from closed ecosystems and end to end encryption in most cases.

    I guess though at least with matrix someone could make a service that acts as a client and indexes content from a list of channels or something…

    Discord, matrix, slack and telegram are where documentation goes to die in the current state of things though.



  • 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.



  • 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