Hacker Newsnew | past | comments | ask | show | jobs | submit | ahsteele's commentslogin

> If you push for change long enough, and aren’t an asshole about it, just genuinely interested and motivated, there’s a chance you’ll see your vision for better culture materialize.

Throughout my career, I’ve described this as “polite persistence is how you effect change.”


Unpolitely breaching walls and doors is also how you effect change, but I prefer the polite persistence for a better long term effect as well.

"You can just do things"

Did you write this? Do you have a link to the entire essay? I enjoyed the excerpt.


Yes, I wrote this, and you can find an intro/context to the _UNFINISHED_[1] essay here (https://www.galacticbeyond.com/a-bridge-to-everywhere/), with a link to the PDF at the bottom.

[1]: what you see is the first 5% of the essay, based on the notes that never made it in. Many topics are untouched, such as cults, caves, imagination, conspiracy, paranoia, fear, wakefulness, blindness, hallucinations, altering consciousness, notations, etc. And other topics are mentioned but not explored deeply (taoism, buddhism, prophecy, trust+belief[2], mnemonics, dreams, metaphors, etc). So it's mostly setup, with planned payoffs and epiphanies in the latter unwritten parts[3]. And some of the transitions between topics are in need of deburring.

[2]: note that many languages use the same word for trust and belief. In Indo-European languages, the root is the same root as tree and true. Relevant to the unwritten parts of the essay.

[3]: so you'll just have to imagine the unwritten parts, until I actually get around to writing them ;)


very interesting. esp. The "imagine the unwritten parts" :) For a long-time not seen anything letting me such freedom

May i suggest two/3 more/other directions to glance at?

- Strugatsky brothers - in "Snail on the slope" [1], chapter 3, (about page 11 in original) Peretz talks about understanding... "Проще поверить, чем понять. Проще разочароваться, чем понять. Проще плюнуть, чем понять. " -- in my flaky translation, "it's simpler to believe than to understand. it's simpler to get disappointed than to understand. it's simpler to spit than to understand". Have a look

- Pirsig's MoQ metaphysics of quality

- the mean-ings of word "mean"

[1] https://en.wikipedia.org/wiki/Snail_on_the_Slope


Thank you, I will check these out!


It’s really hard to even comprehend how large IPv6 is. I have found that extreme examples tend to help people get there. Here are some I’ve used in the past.

There are enough IPv6 Addresses for 4.77 x 10^28 for every living person.

If each IPv6 address was a grain of sand…

That’s 2.39 × 10^18 of addresses per person, or roughly enough sand sized addresses to equal about 1.8 times the volume of earths ocean per person.

At sand scale all IPv6 addresses would take the volume of 12 sols.

Conversely, all the IPv4 addresses in this sand scale would slightly over fill an oil drum.

From “IPv6 Addresses: Big Numbers, Big Solutions”: https://www.osti.gov/servlets/purl/1365362


I think it's more useful to comprehend it as 64+64 though.

We can give every person a million local networks, with unlimited devices on each local network. That's more accurate and also easy to think about.


In current practice it's more like a global 61+64. We're all inside the globally routable /3 with ULAs on the side.


Chess has 1e100 possible games but the more practical metric is that the average game involves 40 black moves and 40 white moves.

Similarly, it’s better to think of the depth of a network’s topology. The size of the tree when full is immaterial, especially when the last 64 bits is intended to be so sparse that random address assignment is viable.


I missed the edit deadline and wanted to add:

So instead of talking about there being 2^128 addresses, it’s more useful to talk about there being 4k global regions (/12 RIRs), assigning /32s to ISPs in their region.

Each ISP can assign a /48 to each customer site, which can then subdivide into 256 buildings with 256 VLANs each (or some other balance of the these, eg 8 buildings with 64 floors each and 128 VLANs on each floor) with the hosts selecting randomly (or SLAACly) from the final 64 bits.

Some ISPs where customers are in a single dwelling will only give you a /56.


> It’s really hard to even comprehend how large IPv6 is.

But the allocations for a single device are so large that it's not actually as large as it seems to be. Kinda like usb N only working at N-2 speeds...


Hah - all of those examples use a planet as comparison. The first 16 bits of the address should be reserved to be used by the Planetary Internet Addressing Council (PIAC)

Allocating all addresses to Earth seems very shortsighted.

(Some sarcasm should be assumed.)

It doesn't really matter how you explain large-number math to people who are bad at large-number math (aka all of us) - there's always some bright-spark who misses the point.


Well we could argue that this support for trillions of IP addresses is nice, except that IPv6 does not technically work in interplanetary environments due to various hardcoded timeouts.

The first martians are likely to run their own local network and then use a VPN over DTN for their everyday communications by email (and appear coming from a single IPv6 address).

One good thing though: since most of the humanity’s knowledge is going to be packed in an LLM they won’t really actually need internet to learn about things. But lack of videos may be annoying.


I see only one IPv6 timeout, for fragmented packet reassembly, in other words between reception of fragments. So it's a bound on jitter not latency, and I see no reason it couldn't be increased for interplanetary links.


The moon can share with the earth, and anything further away needs special encapsulation to deal with hours or more of latency.


It's only minutes for the inner planets. But of course that's already enough to require special treatment.


One problem of ipv6 is proponents saying there are 2^128 addresses.

It's really hard to comprehend how many unusable ipv6 addresses are.

Having more than 2^16 hosts on a subnet is pretty much impossible. Sticking with "grain of sand" units, but using volumes all from wolfram alpha:

There's 2^80 usable IPs in the entire ipvv6 space, because of the /64 subnets. That's plenty. But for every subnet, that's 40 cubic metres unusable for every subnet, and a sphere 1mm wide of usable addresses.

My ISP give me a /48. I have under 30 addressable devices over 3 vlans. I'm using 40 cubic miles of space. A ratio of about 10 trillion:1

But that's nothing. The IP allocators are happy to give a bank a /16, or in your "grain of sand" measurements 30 times the volume of the moon.

To match my unused:used ratio of 10 trillion to one, chase manhattan would need 2^70 devices, which is billions of addresses per cell.

All the space that fanboys go on about is almost all unusable, so the extreme examples don't really help at all.


Do you have a link?


Not sure where I found it. I think it is this.

https://upload.wikimedia.org/wikipedia/commons/5/52/Falcon_H...


I discovered the DVD Journal website tonight and read their last entry. It serves as an excellent snapshot of technology trends as of late summer 2007. Notably, it doesn't mention smartphones, even though the iPhone was released earlier that summer, but iPods are discussed. Additionally, the website's design features, such as nested tables for layout, an image as a background, and the use of image alignment attributes, are notable.


Yes, exactly.


I’ve been using Google Voice this way too since 2011. Recently I have been considering porting my number out as the iOS app has become incredibly slow to the point of almost nonfunctional. Have you had a similar experience?


I'm on Android. The Android app has never been very snappy nor bug-free for me (I've also used older, low-end phones, for what that's worth), but I think it has generally gotten better over time.


What are some approaches have you used to measure your productivity?


I would include Command and Control on a list of essential nuclear history reading. Specifically US and post WWII but fascinating and enlightening.

https://wikipedia.org/wiki/Command_and_Control_(book)


I'm not sure why this is downvoted, but its a very good book.


There was also a 2016 movie made of it, but it mostly focused on one event from the book -- the 1980 Titan II missile explosion in Arkansas.

https://en.wikipedia.org/wiki/Command_and_Control_(film)


Not sure why you're being downvoted?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: