stupid_asshole69 [none/use name]

  • 0 Posts
  • 44 Comments
Joined 8 months ago
cake
Cake day: March 3rd, 2025

help-circle


  • I was able to test out what you’re looking for on macos and its default out of the box terminal does copy and pasting with command-c/x/v just like everywhere else in the os. I haven’t tested Unicode, but rich text and other marked up text types get copied with their formatting between editors that support it and as ansi characters when pasted into the terminal. Option (alt) arrow keys jump to the first letter of each “word” and control arrow keys don’t do what you want because at the os level they’re the keys for switching workspaces. Which is really nice and reminds me I need to set up my windows image to do this instead of uhh win-ctrl or whatever it is.

    The default macos shell is zsh, so maybe with that shift-select extension you can get it the way you like.

    Might be time to switch to a mac!

    I’m really surprised that you couldn’t get alacritty working in Ubuntu, it’s been working fine on Debian stable for at least two major versions when installed through apt.




  • Yeah when I call them the Macintosh keys that’s because I’m almost 100% that the 84 Macintosh was the first thing to use them. Not just the keys specifically, but that operating model we I guess later called wysiwyg. I think it was command instead of control, but it occupies the same place on the keyboard. It’s certainly the oldest thing I’ve used that had them. Windows used to do it like old dos word processors did, with insert and delete etc.

    It’s the design and interface language of gui software for at least 40 years and everyone should know it.

    System wide clipboard would work fine in the terminal but it would be a downgrade, you’d have to give up all the lovely buffers that all your different editors use and are designed around. Even lowly less has a buffer select somewhere in there. Most of the time shift-ctrl-v lets me dump the whatever the system clipboard is out into the command prompt if I need to.

    If the idea of using a different modality for editing text bugs you so much, what do you think of the fact that you already use one? When you’re typing your fingers are on the home row and when you need to edit you switch your right hand to the arrow and function keys. It’s a lot like how editing in vim requires me to move my right hand one key over to the left.

    That way of thinking is how I was able to accept learning vi keys and vim about twenty years ago when I had the same thoughts as you about new shortcuts.

    An alternative might be using macos. I can’t remember if it uses the mac keys to cut and paste into its terminals but it might.


  • I do not hate selecting text with shift. I do not even oppose selecting text with shift. The Macintosh user interface model is the standard for gui operations. It’s good to know how to use the interface of gui applications because usually the majority of your time will be spent in them.

    The terminal has a different interface. It’s different for a lot of reasons. Some are historical, some are technical, some are based on interface standards and ideas.

    I’m trying to help you understand how learning to use the terminal as it exists will be a better solution than making the terminal behave in the way you’re already familiar with.

    The reason it’s a better solution is that using the terminal as it exists allows you to more easily communicate and learn & allows you to use a broad range of tools on any system without having to import a bunch of configurations, programs or environment variables.

    It’s easy to read my comments and come to the conclusion that wanting to use the Macintosh text selection keys is the thing I think is stupid, but what I’m trying to reiterate in every reply is that making the terminal use Macintosh text selection keys is the thing I think is stupid.

    Part of learning how to use a computer is developing a combination of skills and tools that you can use to solve the problems that communicating by doing mathematics really fast always entails. I am trying to convince you to learn the toolbox the computers terminal comes with before you start to weld a tire iron on to your ratchet wrench.


  • I am not trying to insult you, I am trying to help you to not do something stupid.

    I understand that you think everything working the same would be better, I was trying to explain how that’s not the case and you will ultimately be better off not doing the thing you’re suggesting.

    To butcher a car metaphor: a peterbilt has lots more controls and gauges than a camry and they’re in different places some of the time. Wouldn’t it be better to make all the controls the same? No, of course not. A low range gearbox, intercooler temperature gauge, gigantic steering wheel with a knob and all the other differences are necessary for effectively hauling freight. Those same controls are not useful in a sedan. Do truckers have massive problems driving the grocery getter when they’re not working? No, of course they don’t. Sometimes you might give the gear selector a pull in the wrong direction but that’s no big deal.

    Instead of making a mutant terminal and dealing with all the problems that could cause you, you will almost always find it’s better to learn screen or tmux (with one of their default bindings) because then you will have a fewer problems, an easy time communicating with people about the ones you do have, and a broader skillset.

    Again, I am not trying to insult you, I am trying to keep you from doing something stupid.


  • You Will Probably Need To Spend Money

    Get an external 2.5” sata usb enclosure. It costs about $10. here’s one on amazon

    Get a 2.5” sata ssd. 512gb is about $20 here’s a sata ssd on amazon

    Optional, but recommended: get a pair of 8gb sticks of ddr pc3 12800 laptop ram, it’s about $20. here’s a 16gb kit on amazon

    Turn the computer on, let it boot all the way up, turn off fast startup and bitlocker if they’re on and then restart, let it boot all the way up then shut it down using start -> power -> shutdown and let it power off normally. Doing this makes sure the computers disk is in a safe state to be read later.

    Take out the old hard drive, put it in the enclosure, install the ssd and if you got it, the ram.

    Now your old files are in the enclosure.

    Install whatever you like onto the laptop. I always recommend Debian. It will run perfectly fine on your computer especially with the ssd and ram.

    Now plug up your drive and make copies of your files. They’re all on the old drive in the enclosure and the drive could die at any time so do this as soon as you can.

    The benefit of this approach is that it doesn’t rely on the speed of the computer or old operating system, preserves everything so you don’t lose something you didn’t remember to grab and minimizes the possibility of error.

    You also have the option of just plugging the old drive into the computer when you do it this way.


  • zsh shift select is probably a good start. Zsh can most likely be rebound to do what you want with the possible exception of break.

    Don’t do what you want though. It’s stupid, will make you unhappy and cause you problems.

    Your terminal isn’t powershell. Your terminal emulator is an emulation of a terminal. There is a shell that it runs, probably bash, but it’s also an emulated terminal.

    Powershell (and shells that slough off compatibility for the sake of adapting newer ideas, like zsh) is cool, but its able to be the way that it is because it isn’t a terminal emulator.

    If you change a bunch of shit around to make zsh like powershell then you can break your terminal emulation.

    Instead, either use tmux or screen bound the way you want, with their defaults or just don’t use the terminal. You don’t need to. If you do need to then you’ll be exposed to funny things like “the terminal isn’t a wysiwyg editor” and “stdio includes function keys” which require a layer of abstraction in between you and the terminal like tmux or screen, which have existed for many years and are the mature, feature rich solution to your problem.

    The benefit of not doing what you want by making yet another mutant zsh and instead adopting one of the existing solutions is that your terminal will work like all the others, so when someone asks you to try something in order to troubleshoot a problem you’ll be able to instead of having to troubleshoot how your weird garbage is different from theirs.

    Another huge benefit of not creating a special, unique zsh to do what you want is that you will gain competency with every terminal you’ll ever encounter. Which means that instead of being lost when sat down at a terminal other than your own, you’ll be just fine.

    If you want to persist in the doomed world you have created, though, oh-my-zsh documentation will probably get you most of the way to the rest of what you want.


  • I’m pretty sure flatpaks don’t require that the source of any of the weird shit in them be open.

    It’s also probably worth it not to hold open source up above closed source in terms of security since neither of us is conducting a meticulous audit of the stuff we run.

    Regardless, my point was to figure out what works for you. When I ran Slackware I got comfortable doing manual dependency management so breaking Debian by doing a bunch of manual installs is fine for me.

    If you feel most comfortable with using flatpaks or appimages then use those.


  • This is not generally useful.

    Including legally questionable techniques like fingerprint and handwriting recognition as things to be worried about and not including the effects your recommended mitigation might have (one fantastic example is the reply about how a signal jammer will make you more suspicious and not less!) makes this seem like more of a post meant to confuse and sow fear as opposed to a post intended to help people make good decisions.

    The example that stood out to me most (they almost all made me raise an eyebrow but this one was beyond the pale) is where you suggest mitigating the threat of your anonymity being breached by not carrying Id to styme cops.

    When you don’t have id and the cops take you in, assuming you don’t identify yourself on a phone call out which is recorded, your lawyer doesn’t identify you or you don’t just crack under pretrial detention, you will be fingerprinted, photographed and searched against a wide ranging series of databases including id photos made for third party verification and private security camera records.

    Which makes it much more likely that fingerprint or handwriting evidence against you can be admissible because at that point you’re “known to law enforcement”, “in their system” and your “handwriting was on file”.

    This post falls broadly into the category of white noise at best.


  • My first recommendation was more geared towards nostalgia and control. In my own installs I break Debian all the time with outside packages and esoteric user tracked dependencies.

    I don’t like flatpaks or appimages because they broaden the web of trust the system relies on to an absurd degree. Appimages can be better as long as they’re compiled against stuff you have and the code they’re based on has decent ways of failing when you don’t. My trust is in the best practices of the maintainer there. Flatpaks are no better than downloading random docker images though.

    You can’t just trust people. The open source world relies on being able to ferret out infiltration and bad actors and exists at a time when millions of intelligence agents and assets are operating in service of the state and simply dumped out into the private sector.

    We are hoping the “wisdom of crowds” will counteract millions of highly trained operatives. It hasn’t worked out so far.




  • Dumb phones aren’t private. When asked how they compare to smartphones the interviewee says that the restriction on having apps might improve a users privacy through their behavior.

    Do not turn to dumb phones for privacy unless you’re willing to treat everything you ever say over text or voice as actionable information that will be used by intelligence services.

    I cannot stay in that mindset for more than a few minutes and I need significant preparation in order to do so.

    Unencrypted voice and text are available to anyone with a satellite dish. Unencrypted voice and text are available to anyone with access to the lawful intercept functionality of the American cellular and internet backbone.

    If you need to use a dumb phone to improve your mental health or change your coping mechanisms that’s fine, but recognize that it’s not making you more private.


  • You’re overthinking everything.

    Go to your router, turn on qos. I like the cake aqm built into some of the alternative firmwares. Whatever you have is fine though. Now your internet connection quality/speed doesn’t matter and you’ll still be able to use it while torrenting.

    Get a computer and put some drives in it. Or attach them to it. Use mergerfs and snapraid. Now you have a seedbox/nas in your house. You can use it with Jellyfin. If you’re worried about the power, use a device called a kill-a-watt to get real numbers, look at your bill and do the math or just trust me that it’s not expensive compared to a remote seedbox.

    Subscribe to a vpn service with port forwarding. This is not meant to be super private from the cops, but to obscure your torrenting from the isp/authorities. Windscribe and air are good cheap options.

    E: here’s why:

    If you had a free remote seedbox you’d still need qos to make your internet connection usable while you transfer files torrented on your seedbox into your computer so you can do something with em.

    If you had a free remote seedbox it would have a space limitation and you’d need some kind of mess of drives to plug into your computer or a nas to store all the files you transfer in from your seedbox.

    If you had a free remote seedbox you’d need some kind of a vpn service to obfuscate your connection to the known seedbox provider ip range from the isp and any other people looking.

    So just cut out the middleman. You can’t get a free remote seedbox anyway, they cost money per month. You’re also up against the fact that seedboxes are most commonly used for racing, taking advantage of very high bandwidth, low latency, fast storage datacenter space to get lots of upload and build ratio, not what you’re talking about so all the seedbox services are designed for either that or baby’s first time using qbittorrent.



  • Your only “good” option is yubikey. They’ve been around comparatively forever, have all the problems worked out and make durable hardware. All that matters because you don’t want to get something from a company that goes under in a few years and leaves you high and dry and you don’t want the dongle to break because that’s your authentication, now you’re locked out of your shit.

    I recommend against getting some doodad with a biometric reader. You’re adding complexity, attack vectors and not getting much out of it plus you’re locking yourself out of deniability and the possibility of handing a trusted person your dongle, telling them your password and having them act in your stead.