Lemmy shouldn’t have avatars, banners, or bios

  • 1 Post
  • 26 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • This is already a thing that happens currently. Some admins/moderators don’t like being downvoted and ban people for “vote manipulation” because they vote on things in their feed.

    It is leading to exactly that, where people are worried that using the voting system as intended will lead to exclusion from participation in some communities.





  • WSL is pretty good these days. Dual boot with Windows is still a pretty risky move with how easily Windows will overwrite your boot loader. I usually recommend you pick one os or the other rather than dual boot, so I’m in favor of WSL or virtualbox. Personally, I have never cared for needing to reboot just to switch operating systems. I tend to stick with one and the second one does nothing but take up disk partition space.

    WSL lets you run both simultaneously without rebooting. Virtualbox lets you do the same with extra setup. Virtualbox makes it easier to do GUI setups than WSL does, and the network configuration is a little more obvious.

    The best option is to get a second machine so you can run both. If that’s not an option, virtualbox is the better choice for learning. If you just want a Linux environment on your existing setup (similar to using a Mac) then WSL is usually good enough










  • WSL has replaced my use of the command prompt in Windows for anything (and I used it more than most, I think).

    In my job, I develop Linux applications to support industrial automation, and WSL is capable of building and running most of what I make. It isn’t a full Linux machine, and can behave unexpectedly when trying to do things like changing certain network configurations.

    So it’s great for what it’s for, really. But if you want a full VM, this isn’t really for that.





  • I’ve never felt dependent on public code repos for my own career before,

    I hope you don’t actually believe this.

    I think you misunderstood me. We all use open source software or develop using open source libraries, and in the context of the question, I don’t care where they host their code, as long as I can find it. But that isn’t what I was talking about. I have never felt like my career depended on me publicly hosting my own code. I have found jobs and connected with people through other means, and they haven’t even asked to see my github profile in any interviews I’ve been in.

    which is why you should always open source your code unless there’s a specific reason not to. If you’ve ever made something that works, then your cube would be useful.

    Sure, I have a Python script running on a Raspberry Pi controlling my garage door opener. You want it, I’ll show it to you. I believe in open source software, but I’m not going out of my way to publicly host (and document, yuck!) every little thing I’ve made for myself, especially when they have often been tailor made for my home environment, or hacked together in 15 minutes and riddled with secrets.

    But my main reason is simply privacy. I don’t want to broadcast to the Internet what project I am working on right now, or reveal the architecture of my home network or smart home setup. There’s a lot you reveal about yourself when you show the world what you are doing, and I would prefer not to do that.


  • I don’t understand the question or the responses.

    It’s a host for code repos. I would “switch” from GitHub if the repos I need to interact with were hosted somewhere else.

    How do y’all use GitHub? Is everyone running their own open source project? None of my personal projects have ever been open source before. Very few of them were even useful for anyone but myself

    I’ve been a developer for 20 years, I’ve never felt dependent on public code repos for my own career before, and I would be uncomfortable if it happened. No employer has even asked for my public GitHub profile or to see my commit activity. Not even when the company hosted their code on GitHub



  • A couple of main points:

    • You are reading tutorials to help you get it up and running. Most of the time these are designed to walk you through setting things up on a fresh node, and most often just VMs on an isolated (trusted) network. When you are providing a guide to just get someone up and running, the first thing to do is establish a known baseline configuration to start from.
    • Kubernetes is a complex distributed application, and as such, the audience is generally expected to be relatively experienced. Meaning if you don’t know how to configure your firewall, people assume you aren’t going through this tutorial.

    Still, I feel your pain. When trying to get into these technologies, most people who have done the work are engineers, and we stink at writing documentation. I’m sure you’re familiar with it, we automate the solutions for issues we encounter, and then those tools or automatic configurations fail to make it to the end user.

    And I’m probably biased, but don’t use a video guide for this sort of thing. It’s just the wrong medium for a technical tutorial.