That’s when you rotate the proxy. By default most residential proxies will give you a new proxy for each request unless you specify.

Pro-tip for webscrapers: using AI to solve captchas is a massive waste of effort and resources. Aim to not be presented with a captcha in the first place.

Worse is when its asking for crosswalks and its clearly a rumblestrip.

Manipulating vim.g.clipboard is the trick. I’ll have to write some command that sets the clipboard provider directly.

Thats for sure what’s happening. The remaining error message makes that clear but I couldn’t copy the full message

fwiw headscale is pretty easy to self host and has minimal system requirements.

Unironically try turning your computer off and on again.

Tmux settings are global and persistent. Just deleting your config files is insufficient. You have to kill the server and restart it. Uninstalling and reinstalling will not kill a running tmux server. tmux kill-server should work too.

Now if it persists across reboots, then there must be a file still lingering somewhere. If you are sure your home directory is clean you can try searching whatever you installed in /etc.

This is all assuming you’re trying to go back to a clean slate and failing. If the borked status bar is the result of your current .tmux.conf, then you’ll have to post that.

I spent like a week on this last month. Usually you use enumeration, but I wanted to allow client code to define their own strategies. I tried the Box<dyn MyTrait> pattern because some of my strategies were composed of other strategies, and I wanted to clamp down on generic types. But I kept running into weirder and weirder compiler errors. Always asking for an additional restriction on the base trait. X, must be Copy, must be Send, must be Sized, must be 'static. On and on. My experience is if I’m getting a bunch of those then I’m off the Golden Path. So I just embraced the verbosity of using generics and its easy. Yes its more code but its better code.

Its going installed binary is rg.

Who actually hates on declarative/immutable distros as a concept? Its always the actual usability of the specific implementations thats the problem. Stale packages, poor documentation.

We would easily be able to tell if an Alexa was constantly streaming audio data by monitoring its network traffic. It’d be just a wasteful inefficient implementation to stream everything 24/7. Makes much more sense to only start recording when it hears certain keywords that it can recognize locally beyond “Alexa”.

It can only recognize certain hotwords on its own, eg, Alexa. So its not recording 24/7 but it is listening 24/7 for hotwords. They could push additional words and start recording whenever they hear it.

Yeah I have no idea where that article is or even the title. “LogLog Rust” isn’t a good enough search term.

Its like if subroutine bar could say its going to execute at line N of routine foo. But if you were just reading foo then you’d have no clue that it would happen.

You can simulate this effect with bad inheritance patterns.

We let almost all manufacturing jobs go overseas just to cut labor costs and now we’re suffering the consequences and our government completely incapable of doing what’s necessary to bring that manufacturing capability back to the US. At this point basic Keynesians economic policy is tantamount to heresy for anyone but the far left. Its like we’ve adopted the economic policies we forced on third world nations, and found ourselves with a third world economy.

Being able to produce cheap drones as good as DJIs is far more important for national security than whatever espionage risk they pose. Cheap, easy to use, drones like the dji phantom are omnipresent in current wars. Banning them prevents us from learning via competition or basic reverse engineering.

This loony bullshit is why tankies go full useful idiot and parrot shit most of them know isn’t true. The right-wing disinfo about Tianamen square - or any other communist atrocity - is so widespread. Tankies think that the most ultra counter-narrative will somehow combat that even if its just as loony.

My method names are the same way but I aggressively sort things into modules etc so it comes out the other way.

But if I was staring down dozens of these methods and no way to organize them, I’d start doing the sorted names just for ease of editing. L

Its something like vim.nvim_api_set_hl

I’m very suspicious of the uses cases for this. If the compiled bash code is unreadable then what’s the point of compiling to bash instead of machine code like normal? It might be nice if you’re using it as your daily shell but if someone sent me “compiled” bash code I wouldn’t touch it. My general philosophy is if your bash script gets too long, move it to python.

The only example I can think of is for generating massive install.sh

No. Persistent Data Structures are not mutable. The memory space of an older version is not rewritten, it is referenced by the newer version as a part of its definition. ie via composition. It can only safely do this if the data it references is guaranteed to not change.

x = 2 :: 1 :: Nil -- [2, 1]
y = 3 :: x -- [3, 2, 1]

In this example both x and y are single linked lists. y is a node with value 3 and a pointer to x. If x was mutable then changing x would change y. That’s bad™ so its not allowed.

If you want to learn more about functional programming I suggest reading Structures and Interpretation of Computer Programs or Learn You a Haskell for Great Good