• 4 Posts
  • 48 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle

  • You are right that something that most others will host for free are going to be censored since otherwise they might have some kind of responsibility legally. I learned this while trying to diagnose an issue with my cars door lock.

    At the end of the day, anything you ask some hosted llm is being recorded so if you actually want something uncensored or something that gives you a sense of freedom then the only real option is to self host.

    Luckily, it’s very simple and can even be done on a low spec device if you pick the right model. The amount and type of ram you have a will dictate how many parameters you can run at a decent speed.

    Here’s 3 options with increasing difficulty (not much however) written for Arch Linux: https://infosec.pub/comment/13623228





  • This is a very complex and nuanced issue seeing as plastics as a class of materials can vary greatly in its manufacturing process and if any coatings are used. Some materials have varing use cases, also new materials, coatings, and process combinations are created constantly. Additionally a material might not have noticeable effects on a person for 10+ years.

    The American government could pass legislation and studies could be done for both old and new materials and manufacturing process with an introduction of an approval and inspection process. However, did you know that worrying about what corporations do to Americans is “woke”?











  • In TBD, it’s not a “release” until its production ready. The methodology and philosophy doesn’t prevent you from developing multiple feature branches at once or even deploying a work in progress feature branch to a dev environment.

    All TBD requires in that case is once the feature branch is production ready, it’s merged to the trunk. You may need to add a feature toggle if there are multiple release like for different architectures. And you also might benefit from using git tags and deploying to production from a git tag instead of the most recent commit on a branch.

    Exactly what you need to do is going to depend on the project’s exact needs but TBD is totally possible in that example.








  • If you are dipping toes into containers with kvm and proxmox already, then perhaps you could jump into the deep end and look at kubernetes (k8s).

    Even though you say you don’t need production quality. It actually does a lot for you and you just need to learn a single API framework which has really great documentation.

    Personally, if I am choosing a new service to host. One of my first metrics in that decision is how well is it documented.

    You could also go the simple route and use docker to make containers. However making your own containers is optional as most services have pre built ones that you can use.

    You could even use auto scaling to run your cluster with just 1 node if you don’t need it to be highly available with a lot of 9s in uptime.

    The trickiest thing with K8s is the networking, certs and DNS but there are services you can host to take care of that for you. I use istio for networking, cert-manager for certs and external-dns for DNS.

    I would recommend trying out k8s first on a cloud provider like digital ocean or linode. Managing your own k8s control plane on bare metal has its own complications.