• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle

  • It’s Yahweh’s laws but the mythology has it provided by Moses in his sermons to the Israelites. As for Christians ignoring bits of it, part of that is based on saying attributed to Jesus in the gospels (e.g. the bit from Mark I quoted above) and also the simple fact that most religions update themselves as society changes. If anything, I think the Catholic church was smart to have a leader who could receive “new revelations from God”. It lets them update canon, while maintaining the illusion that they aren’t just making shit up to stay relevant.





  • Deuteronomy is originally from the Hebrew Bible. According to Jewish mythology, the book is from the sermons of Moses. Though, it’s believed to be much more recent (something like a 1000 years) than the time period where the figure of Moses (or the person(s) he was based on) would have existed. But, even taking Jewish and Christian mythologies at their word, Jesus had nothing to do with that rule. Also, Jesus probably meant for this rule to end for adherents of Christianity.

    Mark 7:14-23:
    14 Again Jesus called the crowd to him and said, “Listen to me, everyone, and understand this.
    15 Nothing outside a person can defile them by going into them. Rather, it is what comes out of a person that defiles them.”
    17 After he had left the crowd and entered the house, his disciples asked him about this parable.
    18 “Are you so dull?” he asked. “Don’t you see that nothing that enters a person from the outside can defile them?
    19 For it doesn’t go into their heart but into their stomach, and then out of the body.” (In saying this, Jesus declared all foods clean.)
    20 He went on: “What comes out of a person is what defiles them.
    21 For it is from within, out of a person’s heart, that evil thoughts come—sexual immorality, theft, murder,
    22 adultery, greed, malice, deceit, lewdness, envy, slander, arrogance and folly.
    23 All these evils come from inside and defile a person.”

    So, feel free to boil a young goat in its mother’s milk. Jesus is A-ok with that.


  • Is it possible to move a windows install to a different drive and then install Linux on the main drive instead?

    It should be possible to clone the current drive to a different drive. First and foremost though, backup any data you care about to a safe place (e.g. an external drive). Data loss is a real possibility. I’ve been in a professional context explaining to a customer just exactly how fucked they were, because they screwed up in cloning a drive. That wasn’t fun for me and it was expensive for them. Don’t be that guy.

    If you have BitLocker enabled, I’d recommend disabling it. It shouldn’t cause problems; but, Microsoft software has a bad habit of giving you the middle finger when you least expect it.

    The last time I did something like this, I used Yumi to create a bootable USB drive and selected a CloneZilla ISO. Once booted, you will want to do a device-device operation (WARNING: be very, very certain about the direction you are copying. If you screw that up, you will lose data. You did make a backup, right?) clone the whole disk and not just the partition. You can expand the partition with the actual OS, if you want, but leave any EFI or recovery partitions alone. There may also be a small amount of free space left on the drive (MS does this by default), leave that free.

    Once the clone is complete, try booting and using it before you overwrite the old drive.

    Second doubt is if I’ll have many issues daily driving Linux if I have an Nvidia card

    I’m running an RTX 3080 myself and it’s been nearly flawless. That said, my next card (probably years off) is likely to be AMD just to avoid possible NVidia driver issues.







  • My list of items I look for:

    • A docker image is available. Not some sort of make or build script which make gods know what changes to my system, even if the end result is a docker image. Just have a docker image out on Dockerhub or a Dockerfile as part of the project. A docker-compose.yaml file is a nice bonus.
    • Two factor auth. I understand this is hard, but if you are actually building something you want people to seriously use, it needs to be seriously secured. Bonus points for working with my YubiKey.
    • Good authentication logging. I may be an outlier on this one, but I actually look at the audit logs for my services. Having a log of authentication activity (successes and failures) is important to me. I use both fail2ban to block off IPs which get up to any fuckery and I manually blackhole entire ASNs when it seems they are sourcing a lot of attacks. Give me timestamps (in ISO8601 format, all other formats are wrong), IP address, username, success or failure (as a independent field, not buried in a message or other string) and any client information you can (e.g. User-Agent strings).
    • Good error logging. Look, I kinda suck, I’m gonna break stuff. When I do, it’s nice to have solid logging giving me an idea of what I broke and to provide a standardized error code to search on. It also means that, when I give up and post it as an issue to your github page, I can provide you with some useful context.

    As for that hackernews response, I’d categorically disagree with most of it.

    An app, self-contained, (essentially) a single file with minimal dependencies.

    Ya…no. Complex stuff is complex. And a lot of good stuff is complex. My main, self-hosted app is NextCloud. Trying to run that as some monolithic app would be brain-dead stupid. Just for the sake of maintainability, it is going to need to be a fairly sprawling list of files and folders. And it’s going to be dependent on some sort of web server software. And that is a very good place to NOT roll your own. Good web server software is hard, secure web server software is damn near impossible. Let the large projects (Apache/Nginx) handle that bit for you.

    Not something so complex that it requires docker.

    “Requires docker” may be a bit much. But, there is a reason people like to containerize stuff, it avoids a lot of problems. And supporting whatever random setup people have just sucks. I can understand just putting a project out as a container and telling people to fuck off with their magical snowflake setup. There is a reason flatpak is gaining popularity.
    Honestly, I see docker as a way to reduce complexity in my setup. I don’t have to worry about dependencies or having the right version of some library on my OS. I don’t worry about different apps needing different versions of the same library. I don’t need to maintain different virtual python environments for different apps. The containers “just work”. Hell, I regularly dockerize dedicated game servers just for my wife and I to play on.

    Not something that requires you to install a separate database.

    Oh goodie, let’s all create our own database formats and re-learn the lessons of the '90s about how hard databases actually are! No really, fuck off with that noise. If your app needs a small database backend, maybe try SQLite. But, some things just need a real database. And as with web servers, rolling your own is usually a bad plan.

    Not something that depends on redis and other external services.

    Again, sometimes you just need to have certain functionality and there is no point re-inventing the wheel every time. Breaking those discrete things out into other microservices can make sense. Sure, this means you are now beholden to everything that other service does; but, your app will never be an island. You are always going to be using libraries that other people wrote. Just try to avoid too much sprawl. Every dependency you spin up means your users are now maintaining an extra application. And you should probably build a bit of checking into your app to ensure that those dependencies are in sync. It really sucks to upgrade a service and have it fail, only to discover that one of it’s dependencies needed to be upgraded manually first, and now the whole thing is corrupt and needs to be restored from backup. Yes, users should read the release notes, they never do.
    The corollary here is to be careful about setting your users up for a supply chain attack. Every dependency or external library you add is one more place for your application to be attacked. And just because the actual vulnerability is in SomeCoolLib.js, it’s still your app getting hacked. You chose that library, you’re now beholden to everything it gets wrong.

    At the end of it all, I’d say the best app to write is the one you are interested in writing. The internet is littered with lots of good intentions and interesting starts. There is a lot less software which is actually feature complete and useful. If you lose interest, because you are so busy trying to please a whole bunch of idiots on the other side of the internet, you will never actually release anything. You do you, and fuck all the haters. If what you put out is interesting and useful, us users will show up and figure out how to use it. We’ll also bitch and moan, no matter how great your app is. It’s what users do. Do listen, feedback is useful. But, also remember that opinions are like assholes: everyone has one, and most of them stink.