Seth should have gotten the Cheyanne
gayhitler420
joined 1 year ago
Can you point me at the right wing propaganda on hexbear? Someone elsewhere in this thread said blahaj has downvotes disabled so that might be two.
It’s interesting to me that hexbear disabled downvotes because of downvoting campaigns against lgbt users, cultivated a culture of replying instead, federated with blahaj, broke with blahaj and now blahaj ostensibly removed downvotes.
Queer instance main sequence?
Nice! When did that happen?
“Just wait till my evil demon gets to amorally act with impunity!
What? He already is?”
There is no way the sc will rule that chief executives can be prosecuted for crimes committed while in office. Every former president would be drowned in lawsuits immediately. Discovery alone would subject so much information to FoIA that it would require additional staff.
That can be a struggle. There used to be a context menu option in maybe xterm or the kde terminal emulator that would copy the wd and maybe even the highlighted file but I might be gpt hallucinating that last one.
After fucking up bad copying from the internet into a terminal about fifteen years ago I have tried to review and understand what’s happening when copying from or to the terminal even in part. It would be bad for me if there weren’t the possibility of (at best) having shit not work when I use middle click with abandon.
I been thinking a lot about designing technology to discourage people from using it. For example it’s a serious mistake when wearable displays are made to look like wayfarers. The danger of people accepting them socially to the point of being manipulated into a state of flow, dissociating from their reality through a combination of sight and sound augmented reality, is too high. Good design of wearable displays should prioritize function over form 100% and make the user look like an insane freak that no one wants to be around, forcing people to remove them in order to maintain social interactions.
I think copying to and from the terminal is like that. When going between an interface which is a very high level mediator of interaction with the machine and one that’s a very low level mediator, we should be alert, on guard and proofreading everything twice. It’s good that we have to check ourselves before we wreck ourselves copying and pasting into the terminal.
I didn’t notice that part of your post. 🙏
The point I guess I was getting at was that even having “come up” with Slackware and a whole os that’s just 69 half baked scripts in a trenchcoat I adopted a more universal mindset and specific skill set when using scripts over ten years ago and find it hard to justify expecting sanitary inputs nowadays when it is harder and harder with Unicode and is a serious security threat to treat variables as passable strings.
I wasn’t trying to suggest that there isn’t a way to make a space in a filename cause an error, but that I can’t think of an example where allowing a space to affect things was a good or right way to do something.
In the specific example of the op, no spaces is a scene rule from the days of ftp and irc/usenet. The idea behind having only a subset of the ascii character set was to allow those services to work with the files and commands around them. There’s no reason to treat my own scripts and programs as if they’ll never encounter the galaxy of other characters that are flying around now and to be honest, theres no reason not to work in sane handling of non ascii characters in filenames even for code I only expect to touch scene stuff.
It used to be an unavoidable mistake when we dug up buried utilities. Now that there’s a number to call first it’s only the fault of the knucklehead with the shovel.
Please don’t read this as some kind of an argument. I think we basically agree and I’m not trying to get one over on you.
I’m not at a bash terminal, but I think “$f” fixes that. I’ll look tonight.
Escape characters and autocomplete exist.
It’s also really good practice to account for weird characters in programs and shell scripts you write because then you don’t have injection vulnerabilities or unicode problems.
Seriously, what’s an example of spaces in filenames causing a problem?
view more: next ›
It will never happen.
No one’s gonna buy a $30 cable rated for 100w and 120fps video to charge their phone. They’re gonna buy the $5 one at the gas station that’s only rated for low power charging.
No manufacturer is gonna put the hardware to safely deliver 100w in their phone charger. They’re gonna do the cheaper lower power option, and people already say the ones that do include this functionality are greedy price gougers for charging more than the $5 low power charger at the gas station.
How soon before manufacturers start stripping those high power delivering ports out of laptops because they raise the risk of permanent damage under a failure too high for the market/brand to bear?
It’s no fun to be laughing at the people who all wanted a usbc-only world and are now having to live in it but here we are.