• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • since the server validates everything anyway

    Oh you sweet summer child.

    The server doesn’t validate shit, because that takes up CPU cycles on THEIR hardware, which costs them money. A huge part of kernel level anticheat is forcing YOU to pay the cost for anticheat, so they can squeeze a few more pennies out of it. And if your computer gets owned because they installed insecure, buggy malware on your system…? Well, they’ll just deny. After all, it’s kernel-level, how are YOU going to prove anything?


  • Which is ignoring the problems inherant to auto insurance, which is fundamentally a greater force in the price/cost of car insurance than the danger of cars.

    Yes, cars can be dangerous, but that’s not why car insurance is expensive, it’s expensive because car insurance companies have a completely captive market in the US- one that must pay whatever the insurance comapny dictates.

    As a result, they set the price as high as they can get away with, and then refuse to actually pay it out anyway.

    Don’t make excuses for the insurance companies. The risk is the whole point, and certainly does not excuse their gouging.

    You’ll notice other countries do not, in fact, have to deal with this level of price gouging, which implies it’s nothing to do with the cars themselves- it’s just the insurance companies, and it always has been.







  • As someone who has strong opinions on this, and not only has a job but has a job related to exactly sort of thing… We use freebsd.

    Specifically to avoid shit like systemd, and other questionable choices forced down people’s throats by idiots who can’t stop touching things that work well because they didn’t invent it.


  • Except for the fact that it’s now invasive as hell and trying to monitor/sell everything on your computer after the rewrite. We had to ditch teams after the rework because it wanted to phone home to dozens of IPs with information about our computers and actions.

    The high score was blocking 112 outgoing requests with personal data in a single 1 hour call. (We have network connections locked down on our computers using Little Snitch).

    Absolute madness and frankly every single person involved in Microsoft Teams should be thrown in jail for espionage and stalking.





  • Not sure where you drive, but those cars aren’t spaced at all- they’re very close to bumper-to-bumper, which you can only do at extremely low speeds that unrealistic for travel. Meanwhile, the people that are bundled together ARE actually capable of moving like that, though the average american (who has a larger ‘personal bubble’ that other cultures) would probably not like it.

    Moreover, the car example could actually be worse than it appears- because they’re taking up all lanes of a road, so you’re assuming they’re coming AND going, which none of the other examples are assuming. If you did it properly, the line of cars would be two wide and twice as deep!


  • Honestly, these days it’s pretty simple. The thing you need to remember is that you do not need to know EVERYTHING all at once. Learn a little bit, use it, keep what you use, discard what you don’t, get it in muscle memory, and learn a bit more. Very quickly you’ll be zooming through vim.

    You can learn the basics, and go from there- the basics of vim (which imo everyone should know- vi is often the fallback editor), and then you can just casually learn stuff as you go.

    Here’s the basics for modern default/standard vim: Arrow keys move you around like you expect in all ‘modes’ (there’s some arguments about if you should be using arrow keys in the vim community- for now, consider them a crutch that lets you learn other things). There’s two ‘modes’- command mode, and edit mode.

    Edit mode acts like a standard, traditional text editor, though a lot of your keybinds (e.g. ctrl-c/ctrl-v) don’t work.

    Press escape to go back into command mode (in command mode, esc does nothing- esc is always safe to use. If you get lost/trapped/are confused, just keep hitting escape and you’ll drop into command mode). You start vim in command mode. Press i to go into edit mode at your current cursor position.

    To exit vim entirely, go to command mode (esc), and type :wq<enter>.

    ‘:’ is ‘issue command string’,

    ‘w’ is ‘write’, aka save,

    ‘q’ is quit.

    In other words, ‘:wq’ is ‘save and quit’

    ‘:q’ is quit without saving, ‘:w’ is save and don’t quit. Logical.

    Depending on your terminal, you can probably select text with your mouse and have it be copied and then pasted with shift-ins in edit mode, which is a terminal thing and not a vim thing, because vim ties into it natively.

    That gets you started with basically all the same features as nano, except they work in a minimal environment and you can build them up to start taking advantage of command mode, which is where the power and speed of vim start coming into play.

    For example ‘i’ puts you in edit mode on the spot- capital i puts you in command mode at the beginning of the line. a is edit mode after your spot- capital A is edit mode at the end of the current line.

    Do you need these to use vim? Nope. Once you learn them, start using them, and have them as muscle memory, is it vastly faster to use? Yes. And there’s hundreds of keybinds like that, all of which are fairly logical once you know the logic behind them- ‘insert’ and ‘after’ for i/a, for example.

    Fair warning, vim is old enough that the logic may seem arcane sometimes- e.g. instead of ‘copy and paste’ vim has ‘yank and put,’ because copy/paste didn’t exist yet, so the keybinds for copy/paste are y and p.