Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
0
Comments
94
Joined
3 yr. ago

  • I think k8s is a different beast, that requires way more domain specific knowledge besides server/Linux basic administration. I do run it, but it's an evolution of a need, specifically when you want to manage a fleet of machines running containers.

  • Because the lxc way is inherently different from the docker/podman way. It's aimed at running full systems, rather than mono process containers. It has it's use cases, but they are not as common IMHO.

  • You have a bunch of options:

     
        
    kubectl run $NAME --image=$IMAGE
    
      

    this just creates a pod running the specific image. If you kill the pod, or it terminates, it won't be run again. In general though, you probably want to do some customization before running (maybe you need volumes, secrets, env, ports, labels, securityContext, etc.) and for that you can simply let kubectl generate the boilerplate YAML and then simply make some edit:

     
        
    kubectl run $NAME --image=$IMAGE --dry-run=client -o yaml > mypod.yaml
    # edit mypod.yaml
    kubectl create -f mypod.yaml
    
      

    You can do the same with a deployment or statefulset:

     
        
    kubectl create deployment $NAME -n $NAMESPACE [...] --dry-run=client -o yaml > deployment.yaml
    
      

    In case you don't need anything fancy, the kubectl create subcommand allows you to create simple workload, so probably that's the answer to your question.

  • I would say Docker. There is no substantial benefit in running podman, while docker is a widely adopted tool (which means more tooling in the ecosystem, easier to find answers to questions etc.). The difference is not huge tbh, and some time ago the biggest advantage for podman was being able to run rootless, while docker was stuck with a root daemon. This is not the case anymore (docker can run rootless), so I would say unless you have some specific argument to use podman, stick with docker.

  • They have millions in funding, they will always move at a faster pace. The question is in which direction they will move, I suppose.

  • I am curious about the details of that conversation, because I remember reading Dev's comments in some post on Lemmy where they mentioned this option.

  • One thing I have never understood and keep repeating in this context: Beehaw has >7k$ balance. If they really have a few issues that would solve 90% of the problems, why not putting a 500/1000/2000$ bounty of that feature.

  • This is a separate discussion, on which tbh I have not a strong opinion. I can understand the risks of children without proper sexual education consuming porn, but I also understand the pointless nature of trying to block it.

  • In fact I don't personally agree with doing it here, but I mean, there is no other way to do age verification. There are technically ways that can make sure the only data reaching the end customer (the porn site) is a boolean (minor or not), and the identity verification is generally done by another entity, but ultimately yes I agree, I wouldn't do it either and I personally think it's not worth in this case at all (I think proper sex education in school is probably what I would invest on).

    There is also another thing to consider though, which is that porn is different from -say- a gambling site (where you have to make identity verification) mostly due to religious/moral stigma on sex. This makes me a little bit conflicted because I would like a society in which sex is freed from stigma and shame, and where "associate yourself with a porn site" is not as bad as it is now. Definitely the age verification is not the way to pursue this objective, but overall this makes me ask questions like "why would I have not a problem doing the same for a gambling site but I would for porn? Does it align with my values or is it coming from cultural pressure I disagree with?

  • Many appliations do identity verification: financial platforms, crypto scams, roblox, car sharing platforms... It nowadays takes a couple of minutes and it's done once, associated with your account. I am not saying I agree with the idea of doing it here, but I think that many people wouldn't care to change platform. And if they do, some other platform will grow and eventually will have to do the same.

  • Yes, an exploitative thing that mostly consists of free labour for big orgs.

  • I am sure that for such small shops it's trivial to explain that resources are extremely limited, I don't see any data protection authority actually pursuing anyone based on the lack of privacy by design. The point is, nobody is forcing you to deploy the software as is, and technically anybody could write tools that bridge the gaps in the software. If the software does not offer data deletion, any instance admin could have identified this gap (a risk assessment for data collection is also needed technically) and wrote a script that would allow to satisfy data deletion requests or anything else that would have made them comply.

    That said, I agree that these features are important. I do not agree that they are what the devs should work on right now, or that at least it takes some convincing to convey the fact that these are important features for instance admins to be compliant and for users (in general).

    I also get the point about the "I am not taking your word for it" approach. Look how many people in this thread talk about GDPR without actually understanding who is the data controller/processor and who has to be compliant. I can only imagine the amount of uninformed people who open issues and waste time for already busy devs. We are seeing the couple of examples that the article picks, we are not seeing the rest of issues which justify this harsh approach.

    The way I see it, having certain features implemented in the Lemmy software is one way to ease compliance for admins, and they should just upvote the issue and explain why it's important for them, possibly even adding a bounty to the feature. OP's approach doesn't seem this and it's much closer to demand stuff, as if the compliance responsibility was on the devs and the donation were some sort of reason to make them work on what other people want.

  • To be precise, it's not devs that need to worry about GDPR, it's instance admins. I don't disagree with you, but I think it's an important distinction to make.

  • Oh no, I work for a financial company and unfortunately we are extremely limited in what we can run. That's the reason why I am hanging to my Linux box for as long as I can, not even Yabai is allowed on Mac. I follow the project on Mastodon though, it's really cool.

  • I could check with my fitness tracker, it has a "stress level". Might not be super accurate though.

  • Hey, that's actually a very nice project, and to be honest, I can kinda imagine that the saving is minimal if there at all, in terms of time. Partially, I think this is also due to the fact that we are talking about super small amounts of time anyway! Moving files around I think it's totally fast with a mouse, and in general I still do it like that. For me speed is really a secondary thing, it's about ergonomics and limiting my movements. Chances are, I am already writing on the keyboard when I want to do something, so it might not be faster to switch to browser with mod+2 and back to terminal with mod+1, but it's less movement to find the mouse, rotate the shoulder (my split kb is open at shoulder width) etc. Also I think I would argue that requires less focus because it's inherently more mechanic as an action compared to find a button and click, or dragging and dropping something. Either way, it's for sure something interesting to look at!

  • Oh no, I get it, I do have a work-issued macbook pro which I am currently not using in favour of a Linux machine. The main reason for me is ergonomics. My laptopt is closed in a vertical stand, and I cannot imagine myself moving the hands so much do to stuff. I do basically everything what the trackpad does with i3 keybindings, which I find not only faster, but also allow me to reduce movement of my arms and ultimately limiting wrist/arms stress.

    Obviously I completely agree that if one has or prefers to work with trackpads, apple ones are honestly great.

  • If there is already another reverse proxy, doing this IMHO is worse than just running a container and adding one more rule in the proxy (if needed, with traefik it's not for example). I also build all my servers with IaC and a repeatable setup, so installing stuff manually breaks the model (I want to be able to migrate server with minimal manual action, as I had to do it already twice...).

    The job is simple either way, I would say it mostly depends on which ecosystem someone is buying into and what secondary requirements one has.