The Himalayan Blackberry produces untold numbers of very large fruits and it's still so aggressive you have to ruthlessly clear it before it grows under your foundations and into your driveway and walls. It takes over every patch of ground it gets access to and it will send runners down 20 or 30 foot concrete walls from the top of the freeway. I once saw it grow a runner up to the top of a 40-foot tree and then back down to the ground 10 feet away. The thorns are so thick it will penetrate everything but duck cotton. I have to wear welding gloves when I'm clearing it because it can go right through gardening gloves. It is a hell plant sent to torment us for our hubris.
If you've ever bought or eaten "marionberry" this plant is where it grows.
Kudzu's threat has been long overstated. It thrives especially near forest edgelands which are always visible on highways, so concern of prevalence was partially based on individual sampling error. In reality, its presence in southern forests is higher than desired but still not disastrous (~0.1% of southern forestland), which is a fraction of worse invasives: Japanese honeysuckle (4.4%) and Asian privet (1.4%).
> ~0.1% of southern forestland), which is a fraction of worse invasives: Japanese honeysuckle (4.4%) and Asian privet (1.4%).
Sample size of 1 here (I know), but I've spent a meaningful portion of my life outdoors in the south and I have _never_ seen swaths of the landscape covered with Japanese Honeysuckle or Asian Privet like I have Kudzu. It absolutely dominates _everything_ in areas where it's present here (not surprising when it can grow up to a 1 foot (0.3 m) a day.)
Not trying to say you're incorrect, just trying to get a better handle on this. The thought that there are more destructive invasive plants in the US south than Kudzu is kind of blowing my mind.
You won't see swaths of honeysuckle or privet because it grows in the understory throughout the entire forest, choking out natives. Part of their destructive power is that they bloom earlier than most natives in spring, essentially stealing the available sunlight in those golden weeks before the overstory leafs out and reduces sunlight in the understory.
I guarantee you that if you've spent a meaningful portion of your life outdoors in the south you have seen Japanese Honeysuckle at the least, it is everywhere. But it's not a dramatic/easily identifiable shower like kudzu.
The data I'm citing is from my textbook for my Ohio Citizen Volunteer Naturalist program I did in the Fall semester, it cites the US Forest report but doesn't give a link. I think it's from this report [PDF warning]: https://www.srs.fs.usda.gov/pubs/gtr/gtr_srs178/gtr_srs178_3...
I would say that it's more accurate to say that kudzu is not poisonous. I definitely would not say it tastes good. It's got that "green plant" taste that you get from just chomping on any ol' leaf you might find. I mean, if you're poor and starving you could maaaaaybe survive on Kudzu, but it will be rough, it's not very calorie dense, even for a leafy green. Goats won't even eat it unless there is literally nothing else to eat. This whole, "oh you, can eat kudzu!" thing is just crunchy-mom Instagram influencer bullshit.
I’ve proposed that someone open a restaurant of invasive species. You could make some decent dishes with lionfish, blackberries, golden oyster mushrooms, venison, etc
You could also 4x the resolution by using half- and quarter-block characters from the top half of the ASCII table (or it'd be the PETSCII one i C64 case).
Exactly. It's even how I taught myself extremely basic Pascal -- getting my BASIC Life program running in Pascal. With asterisks.
A taught a friend at uni, who was a much better programmer than me, how the algorithm worked. He did a pixel-by-pixel version in machine code, but it was a bit slow on a ZX Spectrum.
So he did exactly the quarter-character-cell version you describe. I wrote the editor in BASIC, and he wrote a machine-code routine that kicked in when told and ran the generations. For extra fun he emitted some of the intermediate state to the border, so the border flashed stripes of colour as it calculated, so you could see it "thinking". Handy for static patterns -- you could see it hadn't crashed.
I've been considering doing a quarter-cell Mandelbrot for about 30Y now. Never got round to it yet.
I like your comment, but it seems the author acknowledged this as a caveat to the algorithm.
>Many home routers try to preserve the source port in external mappings. This is a property called “equal delta mapping” – it won’t work on all routers but for our algorithm we’re sacrificing coverage for simplicity.
So to what percentage is this coverage sacrificed exactly? No idea. Not as useful if the percentage is high, as you are implying.
It’s the same assumption is required for any hole punching handshake (including STUN).
> This is a property called “equal delta mapping”
FWIW I’ve worked in computer networking for 20 years and have never heard it called this. This blog is the only source that comes up when I search for that exact term. I wonder where the author got it from.
> It’s the same assumption is required for any hole punching handshake (including STUN).
This is incorrect.
Hole punching requires being able to predict external port. That's it. If the port remains the same, it certainly simplifies things, but ports going up (or down) by 1 (or 2, or 5) with each new mapping is quite common, trivial to detect and to punch through.
I wonder how many new technical terms are going to be created by LLMs - not to say that this post was N
necessarily written by an LLM (but, who knows!)
It comes from academic papers on categorizing NAT behaviors which (trust me) is hardly the page turning research most people are used to. In these papers they talk about patterns NATs use between successive external port allocations -- which they call the "delta."
The name "equal delta" just means a type of NAT with a delta that tries to preserve the source port. Not to be confused with "preserving" type deltas (that preserve "the same numerical distance" between successive mappings -- e.g. a "preserving delta" type with a value of +1 means each successive NAT allocation is one more than the previous.)
My internet provider didn't even maintain the ip-address. They have a pool of egress routes and seems to route round-robin. Basically every new connection can be from any address in the pool.
I had to call them to make it stop since it tripped the VPN solution at work, that interpreted it as a MIM attack. They disabled it no questions asked as soon as I called, so I guess it mostly works for most people, but not all.
But on that note, isn't it basically time now for IPv6 so we can stop shit like this and go to directly addressable devices like everyone did in the early 90s.
Can't both sides just keep trying different ports until they get lucky? There's not that many of them, and even if it takes several minutes to get a match, that's better than nothing at all.
You raise an interesting counterpoint. What if the red light violation ticket issued by an automated camera remains a civil penalty, but it is very large, like 1,500 USD? At some point, the number gets so high that it effectively impacts your driving privilege. Of course, I would expect these new civil penalties to be challenged in court as being "dual purpose".
But they didn't say anything about refunding them and you can bet Trump will oppose that and ask the SCOTUS to decide on it. They of course have an option to take their time to render the decision and then just dismiss the case without a comment.
reply